From: Jiri Kosina <jkosina@suse.cz>
To: "Szekeres István" <szekeres@iii.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel losing printk messages?
Date: Tue, 26 Feb 2008 22:35:17 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0802262233290.30955@jikos.suse.cz> (raw)
In-Reply-To: <f4fe1c2a0802261314i5c4c5738y2a3f0e1c8748ee60@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 661 bytes --]
On Tue, 26 Feb 2008, Szekeres István wrote:
> in 2.6.25-rc3 I'm trying to add support for an usb keyboard. While the
> hid-input driver dumps a lot of debugging messages, lines seem to be
> lost. Please see the lines shorter/longer than the average.
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?
> This is directly copied from /var/log/kern.log.
I guess in dmesg the output is also corrupted, right?
> Is this a bug or a feature? :)
It would be a sad feature indeed :)
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2008-02-26 21:35 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 [this message]
2008-02-26 21:44 ` Szekeres István
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=Pine.LNX.4.64.0802262233290.30955@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=szekeres@iii.hu \
/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®