From: Arrigo Benedetti <arrigo@vision•caltech.edu>
To: linuxppc-dev@ozlabs•org
Subject: Re: printk problems
Date: Wed, 03 Nov 2004 17:50:20 -0800 [thread overview]
Message-ID: <41898ADC.5080707@vision.caltech.edu> (raw)
In-Reply-To: <1099522581.31629.84.camel@gaston>
Benjamin Herrenschmidt wrote:
>On Wed, 2004-11-03 at 12:13 -0800, Arrigo Benedetti wrote:
>
>
>>For some reason I can't get printk() to work on a YDL 4.0 system. I have
>>followed all the instructions, like
>>setting the correct log level in /proc/sys/kernel/printk, killing klogd
>>and then
>>
>>cat /proc/kmsg
>>
>>but I do not see any message from printk. The printk is in a new kernel
>>system call that I wrote.
>>Any ideas?
>>
>>
>
>Are you sure you are reaching your syscall at all ? Besides, why are you
>adding a syscall in the first place ? (just curious ... it's usually the
>wrong solution :)
>
>
>
I'm pretty sure that the syscall is called, in fact at some point there
was a bug in the code which
froze the system... I made a syscall just to do some quick timing tests.
I agree that a module is a
better solution, and in fact I have just posted a message about that...
-Arrigo
prev parent reply other threads:[~2004-11-04 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 20:13 printk problems Arrigo Benedetti
2004-11-03 22:56 ` Benjamin Herrenschmidt
2004-11-04 1:50 ` Arrigo Benedetti [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41898ADC.5080707@vision.caltech.edu \
--to=arrigo@vision$(echo .)caltech.edu \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox