Date: Sat, 11 Aug 2001 17:28:44 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Sean Kelly <smkelly@zombie.org> Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Random Lockups Message-ID: <200108110828.RAA21659@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Sat, 11 Aug 2001 01:39:59 EST." <20010811013959.A588@edgemaster.zombie.org> References: <20010807234645.A573@edgemaster.zombie.org> <20010809032027.A99813@xor.obsecurity.org> <20010810174521.A681@edgemaster.zombie.org> <200108110241.LAA20110@zodiac.mech.utsunomiya-u.ac.jp> <20010810221944.A90165@edgemaster.zombie.org> <200108110627.PAA21155@zodiac.mech.utsunomiya-u.ac.jp> <20010811013959.A588@edgemaster.zombie.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>> When this lockup happens if you try to switch between two vtys, does
>> the screen show the first vty (from which you are switching away) or
>> the second (to which you are switching to)?
>
>It makes it to the new vty, but the keyboard is locked. I just found yet
>another thing that locks it:
>edgemaster# kbdcontrol -r fast
~~~~~~~~~~~~~~~~~~
>*keyboard dies*
>
>> When switching between two plain (non-graphical) vtys, the only
>> keyboard I/O taking place is for setting LEDs on the keyboard.
>I haven't tried a graphical switch yet, I'll have to compile X.
>I am seeing no LED lights. Attempts to turn Numlock on kills the keyboard.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>However, using the same keyboard in W2K and all is well.
Ok, I am getting the picture. I think the keyboard driver is thinking
it has done the right thing to the keyboard (to turn LEDs on, setting
the repeat rate, etc), and is not in the infinite loop. This is
the reason why this is a keyboard lock-up rather than system lock-up.
I guess that the way our keyboard driver talks to the keyboard
seems to put the keyboard or the keyboard controller on the motherboard
somehow in a wrong state in yor case ;-(
So, we have two possiblities: we have compatibility problem with your
keyboard, or we have compatibility problem with the keyboard
controller on your motherboard. (We have experienced both problems in
the past. There are so many varieties of keyboard and keyboard
controllers in the market. Some of them are not very compatible...)
They both can be nasty timing problems :-< Did you by any chance
change HZ?
What brand of keyboard is this? Model number? Do you have a spare
keyboard? Does it show the same problem?
The strange thing is, according to your dmesg output, we have no
problem when talking to the keyboard during the device probe phase,
during which the keyboard is reset and the keyboard ID is obtained.
Kazu
>> Keyboard I/O shouldn't loop inifinitely, as it will timeout if
>> necessary I/O operation cannot be completed for some reasons.
>>=20
>> Would you boot this kernel by giving "boot -v" at the loader prompt,
>> and send me dmesg's output?
>
>I did that, but I see nothing keyboard-related. Sending to you anyway.
>
>Also note that I tried a USB keyboard, and it has *NO* problems.
>
>dmesg follows:
[...]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108110828.RAA21659>