linux-kernel - Re: PROBLEM: 3.8.0-rc4 keyboard failure at boot

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: <20130122140532.GB27683@16s.us>
Date:	Tue, 22 Jan 2013 09:05:32 -0500
From:	Brad Tilley <brad@....us>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
	linux-usb@...r.kernel.org
Subject: Re: PROBLEM: 3.8.0-rc4 keyboard failure at boot

On Tue, Jan 22, 2013 at 02:51:08PM +0100, Jiri Kosina wrote:
> On Tue, 22 Jan 2013, Brad Tilley wrote:
> 
> > > Could you please provide dmesg output from both working and non-working 
> > > case?
> > 
> > See attached. Two dmesgs from the same machine. One from 3.7.3, the 
> > other from 3.8-rc4 (with a ps2 keyboard). USB keyboards on this machine 
> > never work with 3.8, but always works with 3.7.
> > 
> > I used an old ps2 keyboard to enter the dm-crypt password. After that, 
> > the boot process continues and the USB keyboard and mouse become active 
> > and begin to work. However, USB keyboards do not work when the user is 
> > prompted to enter the dm-crypt decryption password early in the boot 
> > process. That's the primary issue.
> 
> Ah, I see, that's a very important piece of information. This might be 
> related to USB BIOS handoff then.
> 
> Do you happen to have "Legacy USB" option (or similar, such as "USB 
> emulation" the name is not consistent between different BIOS vendors and 
> versions) in your BIOS? Does toggling it change the behavior?

3.6 and 3.7 kernels on the same machine work with the standard BIOS settings. We did flash the BIOS to the latest revision when the issue was first noticed with 3.8 kernels. I do not see such a setting in the BIOS, and as I said, earlier kernels work just fine with the existing BIOS settings.

To me, this seems like a race condition. Sometimes USB keyboards work when the user is prompted to enter the dm-crypt password, other times they do not. The problem never occurs on single-core machines (that we have noticed), only occurs about 50% of the time on AMD multi-core machines and 100% of the time on Intel multi-core machines. And none of the machine have encountered the issue with 3.6 or 3.7 kernels.

The possibility of a race condition is just a guess on my part and may be incorrect. I did not mention it earlier as I did not want to misguide you.

Brad

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