* printk problems
@ 2004-11-03 20:13 Arrigo Benedetti
2004-11-03 22:56 ` Benjamin Herrenschmidt
0 siblings, 1 reply; 3+ messages in thread
From: Arrigo Benedetti @ 2004-11-03 20:13 UTC (permalink / raw)
To: linuxppc-dev
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?
thanks much
-Arrigo
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: printk problems
2004-11-03 20:13 printk problems Arrigo Benedetti
@ 2004-11-03 22:56 ` Benjamin Herrenschmidt
2004-11-04 1:50 ` Arrigo Benedetti
0 siblings, 1 reply; 3+ messages in thread
From: Benjamin Herrenschmidt @ 2004-11-03 22:56 UTC (permalink / raw)
To: Arrigo Benedetti; +Cc: linuxppc-dev list
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 :)
Ben.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: printk problems
2004-11-03 22:56 ` Benjamin Herrenschmidt
@ 2004-11-04 1:50 ` Arrigo Benedetti
0 siblings, 0 replies; 3+ messages in thread
From: Arrigo Benedetti @ 2004-11-04 1:50 UTC (permalink / raw)
To: linuxppc-dev
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-11-04 1:50 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-03 20:13 printk problems Arrigo Benedetti
2004-11-03 22:56 ` Benjamin Herrenschmidt
2004-11-04 1:50 ` Arrigo Benedetti
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).