Kazutaka YOKOTA wrote:
>
> I have had reports on similar lockup in both 4.0-CURRENT and 3.X.
> I personally have not been able to reproduce it, but now my new sand box
> machine exhibits this problem occasionally.
>
> The I/O access to the AT keyboard by the atkbd driver have not changed
> much for the last couple of years, despite massive source tree
> reorganization. And yes, problem reports started to pop-up since
> sometime around the last summer.
>
> I have not been able to track down the cause of the problem, but
> am suspecting possibility of the clock/timer problem.
It happens with me from time to time. It is NOT related to kernel, since
it happens between boot0 and boot2. It will happen when I'm typing
something during boot, so it's probably some sort of race. Symptons
include keys having weird mappings, and some keys not mapping to
anything at all, after boot. At boot2/loader, no keypress is recognized
at all.
Very rare.
--
Daniel C. Sobral (8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"2 b or not to b" meaning varies depending on whether one uses the 79
or the 83 standard.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
