[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f4fe1c2a0802261344xdbee78j730c9011b8b63aa7@mail.gmail.com>
Date: Tue, 26 Feb 2008 22:44:32 +0100
From: "Szekeres István" <szekeres@....hu>
To: "Jiri Kosina" <jkosina@...e.cz>
Cc: linux-kernel@...r.kernel.org
Subject: Re: 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists