From: Christoph Pfister <christophpfister@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Dmitry Torokhov <dtor@insightbb.com>
Subject: Re: keyboard stopped working after de9ce703c6b807b1dfef5942df4f2fadd0fdb67a
Date: Fri, 13 Jul 2007 23:04:30 +0200 [thread overview]
Message-ID: <200707132304.30795.christophpfister@gmail.com> (raw)
In-Reply-To: <200707132249.26106.christophpfister@gmail.com>
Am Freitag, 13. Juli 2007 22:49 schrieb Christoph Pfister:
> Hi,
>
> After a kernel update I recognised that my keyboard sometimes didn't work
> after booting up. I found out that the issue appeared quite reliably after
> a cold reboot and not pressing any key (for example not selecting stuff at
> the bootloader) till the machine fully booted up.
> Because git head (4eb6bf6bfb580afaf1e1a1d30cba17a078530cf4) didn't solve
> the problem I did a bisect and your commit was found to be the culprit (the
> second last build succeeded 5 of 5 times during my tests and the last build
> failed 2 of 3 times).
>
> Can anybody please shade light on this?
>
> Thanks,
>
> Christoph
Forgot to mention dmesg: "input: AT Translated Set 2 keyboard
as /class/input/input0" is shown in both (working / failing) cases (no
additional / related lines nearby).
Christoph
next prev parent reply other threads:[~2007-07-13 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 20:49 keyboard stopped working after de9ce703c6b807b1dfef5942df4f2fadd0fdb67a Christoph Pfister
2007-07-13 21:04 ` Christoph Pfister [this message]
2007-07-16 14:49 ` Dmitry Torokhov
2007-07-17 19:01 ` Christoph Pfister
2007-07-17 19:52 ` Dmitry Torokhov
2007-07-18 8:41 ` Christoph Pfister
2007-07-28 20:55 ` Vojtech Pavlik
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=200707132304.30795.christophpfister@gmail.com \
--to=christophpfister@gmail.com \
--cc=dtor@insightbb.com \
--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