* Linus Torvalds (torvalds@transmeta.com) [000130 05:47]:
>
> Ok, one final suggestion:
>
> [...]
> Could you who see the keyboard hang please do
> - tell me what kind of computer you have. Model, manufacturer, whatever
> seems relevant. I'd like to see if there is some pattern to it.
This particular piece of hardware is a Dell Inspiron 7000 laptop.
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 02)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 02)
00:03.0 Multimedia video controller: M-Pact, Inc.: Unknown device 0020 (rev 01)
00:04.0 CardBus bridge: Texas Instruments PCI1220 (rev 02)
00:04.1 CardBus bridge: Texas Instruments PCI1220 (rev 02)
00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
00:08.0 Multimedia audio controller: ESS Technology ES1968 Maestro 2
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage LT Pro AGP-133 (rev dc)
04:00.0 Ethernet controller: 3Com Corporation 3c575 [Megahertz] 10/100 LAN CardBus (rev 01)
CPU0
0: 320495 XT-PIC timer
1: 2364 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 5758 XT-PIC eth0
5: 0 XT-PIC ESS Maestro 2
8: 1 XT-PIC rtc
13: 1 XT-PIC fpu
14: 7709 XT-PIC ide0
15: 3 XT-PIC ide1
NMI: 0
ERR: 0
When psaux is open it gets allocated interrupt 12.
> - comment out the check for "kbd_exists" at the top of "send_data()" in
> drivers/char/pc_kbd.c (you can leave all the other references active,
> just remove the line that says
>
> if (!kbd_exists) return 0;
>
> which will disable that particular logic completely.
>
> If that fixes it, then we have another clue.
This makes unfortunately absolutely no difference.
Opening the psaux device causes the keyboard lockup and no interrupts are
beeing received by the psaux device. Closing the device also unlocks the
keyboard.
The only test that so far had any impact was the suggestion to
disable the toshiba workaround. With the workaround enabled I get the
"Timeout - AT keyboard not present ?" warning after starting gpm.
If it is disabled, I do not hit this code path.
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:25 EST