Skip to contentSkip to conversation

printk problems

DISCUSSION Arrigo Benedetti 2 participants 3 messages Nov 3, 2004 – Nov 4, 2004

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 10 lines · Arrigo Benedetti

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.

#2 lore raw
Quoted 8 lines · Benjamin Herrenschmidt
Quoted 5 lines · Arrigo Benedetti

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

Quoted 11 lines
Quoted 4 lines

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