lkml.org 
[lkml]   [2008]   [Feb]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: kernel losing printk messages?
Hi,

> I don't see this on 2.6.25-rc3. Does this happen only on boot? What if you
> do
>
> rmmod usbhid
> rmmod hid
> modprobe hid debug=1
> modprobe usbhid
>
> on already booted system?

Actually I did it the same way. I have no info about the output on boot.

> I guess in dmesg the output is also corrupted, right?

Interesting. Even after a dmesg -c -s 1000000 it contains only the end
of the story. This is the beginning of the dmesg output:

rusalka:~% dmesg | head
input.c: Mapping: Consumer.0230 ---> IGNORED
[85080.775297] drivers/hid/hid-input.c: Mapping: Consumer.0231 ---> IGNORED
[85080.775302] drivers/hid/hid-input.c: Mapping: Consumer.0232 ---> IGNORED
[85080.775308] drivers/hid/hid-input.c: Mapping: Consumer.0233 ---> Key.ScrollUp
[85080.775314] drivers/hid/hid-input.c: Mapping: Consumer.0234 --->
Key.ScrollDown

So the first line is corrupted. In the remaining of the output
(total=220 lines) I cannot see the evidence of corruption.

Regards,
Istvan


\
 
 \ /
  Last update: 2008-02-26 22:47    [W:0.093 / U:0.136 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site