Hey, i've got a lockup issue that's not currently fixed by 2.6.10-rc3 that's kinda annoying me, but first a touch of background:
The abit kv7 uses the via VT82xxxxx hostbridge, with both usb 1.1 and usb 2.0 ports built into the motherboard: 0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 0000:00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81) 0000:00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) now, with the most recent bios firmware (and earlier, i think), the sodding thing has a nasty bug where the keyboard usually fails to operate while working with the bootloader (but not the bios, irritatingly enough), even if it's set for bios control of the keyboard. the only way to get past this is to plug the usb keyboard into the usb2.0 ports. Now, my keyboard is a happy hacker keyboard lite 2 (usb): input: USB HID v1.00 Keyboard [Chicony PFU-65 USB Keyboard] on usb-0000:00:10.3 -1.1 now onto the problem itself: If i have the keyboard plugged into one of the usb2.0 ports on boot, linux locks up when initialising one of the usb1.1 controllers (i suspect, the passthrough one for backwards compatability), because it locks up just after: uhci_hcd 0000:00:10.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2) I've got usb verbose debug messages turned on, so it should be showing things like: hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x501 after that, but it doesn't get up to that stage, it's locked hard at the line above. removing the usb keyboard once it's reached this state doesn't do anything, the machine is completely locked up, requiring a reset, sysrq fails. (uhci and ehci are both compiled into the kernel here) I'm going to try making the usb drivers modular and having them load on boot tomorrow to see if i can get around it, or get more info, but i'm interested in any insight anyone can give, and suggestions about where i should be looking to insert printk's to try and track down where it's locking up. if you need more info, let me know. thanks Andrew Pilley PS: please CC me, since i'm not subscribed. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
