On 2012-10-02 00:45, Bjørn Mork wrote:
Per Foreby <p...@foreby.se> writes:
On 2012-10-01 23:29, Jonathan Nieder wrote:
Per Foreby wrote:
The debug logging from drm isn't forwarded via netconsole, so I suppose it
isn't supposed to?
Oh, that's because of the console_loglevel setting[1]. You can change
it by running "dmesg -n 8" (or by adding the word "debug" or a
loglevel= parameter to the kernel command line).
Ah, RTFM :)
However, it looks like the netconsole documentation and the dmesg man
page should be updated:
# dmesg -n 8
dmesg: unknown level '8'
Instead I tried
# dmesg -n debug
# dmesg -E
but still nothing at the remote end.
Yes, I vaguely remember having struggled with the same issue the last
time I use netconsole. Try
echo 8 >/proc/sys/kernel/printk
instead.
I believe the bug is in the dmesg utility. It should shift all values
by one. Setting "dmesg -n debug" will currently log all messages with a
level *higher* than debug.
You're probably right about the bug. I don't know what the four values
in /proc/sys/kernel/printk are, but the first value was 7, not 8:
# cat /proc/sys/kernel/printk
7 4 1 7
# echo 8 > /proc/sys/kernel/printk
# cat /proc/sys/kernel/printk
8 4 1 7
However, this did not affect the remote logging, so I'm back to the
remote syslog approach.
/Per
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/506a291a.20...@foreby.se
