mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Szekeres István" <szekeres@iii.hu>
To: "Jiri Kosina" <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel losing printk messages?
Date: Tue, 26 Feb 2008 22:44:32 +0100	[thread overview]
Message-ID: <f4fe1c2a0802261344xdbee78j730c9011b8b63aa7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802262233290.30955@jikos.suse.cz>

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

  reply	other threads:[~2008-02-26 21:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f4fe1c2a0802261309s17aaf082w14525c1e2f3af2f@mail.gmail.com>
2008-02-26 21:14 ` Szekeres István
2008-02-26 21:35   ` Jiri Kosina
2008-02-26 21:44     ` Szekeres István [this message]
2008-02-26 21:59       ` Jiri Kosina

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f4fe1c2a0802261344xdbee78j730c9011b8b63aa7@mail.gmail.com \
    --to=szekeres@iii.hu \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®