Date: Sat, 11 Aug 2001 03:28:31 -0500 From: Sean Kelly <smkelly@zombie.org> To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> Cc: current@freebsd.org Subject: Re: Random Lockups Message-ID: <20010811032830.A2017@edgemaster.zombie.org> In-Reply-To: <200108110828.RAA21659@zodiac.mech.utsunomiya-u.ac.jp> 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> <200108110828.RAA21659@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
--tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 11, 2001 at 05:28:44PM +0900, Kazutaka YOKOTA wrote: >=20 > >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 keyboa= rd. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~= ~~~ > >However, using the same keyboard in W2K and all is well. >=20 > 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. >=20 > 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 ;-( Funny, since it used to work... > 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? No. Nothing has changed. No new keyboard, no new KVM, no new mouse, no new motherboard. > What brand of keyboard is this? Model number? Do you have a spare > keyboard? Does it show the same problem? IBM Model No# KB-8923 Power Rating: 5V 200mA S/N: 1121153 Date: 98-26 Fru P/N: 76H3284 REV: CO1 Made in Thailand > 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. After the boot finishes and I'm given a login prmopt on ttyv0, the keyboard is dead. So post-boot, not pressing any keys or changing any ttys, and the keyboard is already dead. Though that could be due to rc.conf having keyrate=3D"fast", thus executing the kbdcontrol above that causes lockup. --=20 Sean Kelly | PGP KeyID: 77042C7B smkelly@zombie.org | http://www.zombie.org For PGP key, send e-mail with subject "send pgp key" --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) iD8DBQE7dOyu2aukpHcELHsRAvsKAJ90sI5CObfsXvo4pwtrTvmzgrBmXwCfeeWY 2MhlF0u21nAFAmZlTU/13FY= =1Qp7 -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT-- 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?20010811032830.A2017>