From: Brad Tilley <brad@16s.us>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: PROBLEM: 3.8.0-rc4 keyboard failure at boot
Date: Tue, 22 Jan 2013 09:05:32 -0500 [thread overview]
Message-ID: <20130122140532.GB27683@16s.us> (raw)
In-Reply-To: <alpine.LNX.2.00.1301221449090.20374@pobox.suse.cz>
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
next prev parent reply other threads:[~2013-01-22 14:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 21:36 PROBLEM: 3.8.0-rc4 keyboard failure at boot Brad Tilley
2013-01-22 0:13 ` Dmitry Torokhov
2013-01-22 0:13 ` Dmitry Torokhov
2013-01-22 10:23 ` Jiri Kosina
2013-01-22 12:19 ` Brad Tilley
2013-01-22 12:42 ` Jiri Kosina
2013-01-22 13:46 ` Brad Tilley
2013-01-22 13:51 ` Jiri Kosina
2013-01-22 14:05 ` Brad Tilley [this message]
2013-01-22 17:22 ` Jiri Kosina
2013-01-23 16:51 ` Brad Tilley
-- strict thread matches above, loose matches on Subject: below --
2013-01-21 16:48 Brad Tilley
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=20130122140532.GB27683@16s.us \
--to=brad@16s.us \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.