>>> 3. On the first reboot after installing, the keyboard was in a funny
>>> state.
>
>> Urk, can't reproduce it. I need a reproducible sequence of operations
>> before we'll have any hope of tackling this one.
>
>>> Control-alt-del definitely didn't work, so I had to power off and
>>> reboot. This hasn't repeated itself.
>
>> Same here.
>
>I have on a number of occasions had my laptop boot with a
>non-functional keyboard. Sometimes the keyboard is just locked; other
>times it generates garbage. Never managed to isolate the
>circumstances in which this happened (but it didn't happen with a
>kernel from last September or there-abouts). Haven't had it happen on
>a desktop or server yet.
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.
Kazu
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
