linux-kernel - Re: keyboard stopped working after de9ce703c6b807b1dfef5942df4f2fadd0fdb67a

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d120d5000707160749r1084ab4ex8d2c4e89e6134d41@mail.gmail.com>
Date:	Mon, 16 Jul 2007 10:49:28 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Christoph Pfister" <christophpfister@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: keyboard stopped working after de9ce703c6b807b1dfef5942df4f2fadd0fdb67a

Hi Christoph,

On 7/13/07, Christoph Pfister <christophpfister@...il.com> wrote:
> 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).
>

Could you please boot with "i8042.debug log_buf_len=131072" and send
me full dmesg?

Thanks!

-- 
Dmitry
-
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/