[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200707132304.30795.christophpfister@gmail.com>
Date: Fri, 13 Jul 2007 23:04:30 +0200
From: Christoph Pfister <christophpfister@...il.com>
To: linux-kernel@...r.kernel.org
Cc: Dmitry Torokhov <dtor@...ightbb.com>
Subject: Re: keyboard stopped working after de9ce703c6b807b1dfef5942df4f2fadd0fdb67a
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
-
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