Date: Mon, 25 Mar 1996 14:49:49 -0800 (PST) From: Dave Walton <dwalton@psiint.com> To: "Andrew V. Stesin" <stesin@elvisti.kiev.ua> Cc: hardware@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Strange lockup problem Message-ID: <Pine.A32.3.91.960325141357.52196G-100000@vv.psiint.com> In-Reply-To: <199603212108.XAA03313@office.elvisti.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Mar 1996, Andrew V. Stesin wrote:
> [... kbd lockup when switching consoles ...]
>
> # Any idea what the underlying problem is, and what the cure might be?
>
> Strange hardware. I remember the rumours this has something
> to do with updating the state of kbd "status" LED indicators,
> and some brand of kbd controller chips on the MB which has
> problems with this. Another source of strange problems
> often is hidden in a slightly misconfigured BIOS.
>
> Probably the author of the driver can tell you more detais,
> I'm sending the copy to him.
>
> # > Sometimes re-plugging of kbd jack cures it (dangerous!)
> # > or a command kbdcontrol -r fast < /dev/ttyv0 (issued
> # > after coming into the box via telnet).
For the sake of completeness, here's a brief recap of the problem:
The first symptom appeared immediately after a fresh install of 2.1R,
with GENERIC kernel. Switching between vtys would often lock up the
keyboard. "kbdcontrol -r normal" reactivates the keyboard, so I set up
cron to run that once per minute. The keyboard still locks, but for no
more than a minute at a time.
I compiled a new kernel, containing psm0, and rebooted. Probing psm0
locks the keyboard, but when cron hits a minute after bootup (see above),
that is cleared up. Mouse and keyboard work properly in X.
While in X, the keyboard occasionally locks up. Not as repeatably as
when switching vtys, but with any key. I've seen it happen while using
cursor keys, as well as with other keys. When the keyboard locks up, the
mouse freezes as well. A minute later, cron (kbdcontrol) reactivates
both mouse and keyboard.
(The annoying part of all this is that we've never had a problem with
FreeBSD before on any system. And then this happens when we set up a
system to convince a client to go with FreeBSD instead of Interactive
Unix, which is the worst excuse for a Unix I've ever seen.)
> Sorry, David, I have no experience with bus mice and their
> possible interaction with kbd controller, still no ideas.
> I think that the _exact_ specs of your motherboard
> (manufacturer, model name, chipset, output of dmesg(8) after
> booting with '-v' switch to the loader) may give some
> helpful hints.
It's a Dell OptiPlex GXMT 5166
I'd love to give the chip number for the keyboard controller, but I have
no idea which chip that is.
dmesg output follows:
FreeBSD 2.1.0-RELEASE #0: Wed Mar 20 10:19:39 PST 1996
root@myname.my.domain:/usr/src/sys/compile/PSI
CPU: 166-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU)
Origin = "GenuineIntel" Id = 0x52c Stepping=12
Features=0x1bf<FPU,VME,PSE,MCE,CX8,APIC>
real memory = 16777216 (16384K bytes)
avail memory = 14721024 (14376K bytes)
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0: disabled, not probed.
ed1: disabled, not probed.
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio2: disabled, not probed.
sio3: disabled, not probed.
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
lpt1: disabled, not probed.
lpt2: disabled, not probed.
mse0: disabled, not probed.
psm0 at 0x60-0x63 irq 12 on motherboard
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <QUANTUM FIREBALL1080A>
wd0: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <DC5-E6/.2C0>, removable, accel, dma, iordis
wcd0: 1033Kb/sec, 256Kb cache, audio play, 256 volume levels, ejectable tray
wcd0: no disc inside, unlocked
wdc1: disabled, not probed.
bt0: disabled, not probed.
uha0: disabled, not probed.
ahc1: disabled, not probed.
ahb0: disabled, not probed.
aha0: disabled, not probed.
aic0: disabled, not probed.
nca0: disabled, not probed.
nca1: disabled, not probed.
sea0: disabled, not probed.
wt0: disabled, not probed.
mcd0: disabled, not probed.
mcd1: disabled, not probed.
matcdc0: disabled, not probed.
scd0: disabled, not probed.
ie0: disabled, not probed.
ep0: disabled, not probed.
ix0: disabled, not probed.
le0: disabled, not probed.
lnc0: disabled, not probed.
lnc1: disabled, not probed.
ze0: disabled, not probed.
zp0: disabled, not probed.
npx0 on motherboard
npx0: INT 16 interface
pcibus_setup(1): mode1res=0x80000000 (0x80000000), mode2res=0xff (0x0e)
pcibus_setup(2): mode1res=0x80000000 (0x80000000)
pcibus_check: device 0 is there (id=122d8086)
Probing for devices on the PCI bus:
configuration mode 1 allows 32 devices.
chip0 <Intel 82437 (Triton)> rev 2 on pci0:0
chip1 <Intel 82371 (Triton)> rev 2 on pci0:7
vga0 <VGA-compatible display device> rev 83 int a irq 9 on pci0:16
mapreg[10] type=0 addr=f8000000 size=4000000.
pci0: uses 67108864 bytes of memory from f8000000 upto fbffffff.
BIOS Geometries:
0:020e3f3f 0..526=527 cylinders, 0..63=64 heads, 1..63=63 sectors
1:01300311 0..304=305 cylinders, 0..3=4 heads, 1..17=17 sectors
0 accounted for
wd0s1: type 0xa5, start 63, end = 2128895, size 2128833 : OK
==========================================================================
David Walton Unix Programmer
PSI INTERNATIONAL, Inc. email: dwalton@psiint.com
190 South Orchard #C200 Fax :(707)451-6484
Vacaville, CA 95688 Phone:(707)451-3503
==========================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.A32.3.91.960325141357.52196G-100000>