Bug 4140 - USB broken on 2.6.10 after working fine in 2.6.9
Summary: USB broken on 2.6.10 after working fine in 2.6.9
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: Greg Kroah-Hartman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-31 22:27 UTC by Ben Jackson
Modified: 2005-02-17 08:57 UTC (History)
0 users

See Also:
Kernel Version: 2.6.10
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Ben Jackson 2005-01-31 22:27:17 UTC
Distribution: 
gentoo linux (2.6.10 vanilla or 2.6.10-gentoo-r6)

Hardware Environment:
gigabyte K8NF-9 NForce4 mainboard, (eg) ms intellimouse usb.

Software Environment:
(either)devfs or udev, xorg-x11, hotplug 20040923

Problem Description:
after upgrading to kernel 2.6.10 (for the SATAPI support), the back facing usb
ports on my mainboard stop working, although they appear to be detected. the 2
front facing ports continue to work fine. there is nothing of note in dmesg.

Steps to reproduce:
reboot using 2.6.10 kernel with gigabyte K8NF-9 mainboard
Comment 1 Ben Jackson 2005-01-31 22:31:48 UTC
forgot to mention that this is an x86_64, pci-e system if its relevant. 

this was also a problem on fedora core 3 with their supplied RPM packages. 
Comment 2 Andr 2005-02-14 00:44:15 UTC
Hello, 
 
I get the same problem. Now I have kernel 2.6.10 vanilla using at suse 9.2. 
Hotpulg is 0.45-21. When I boot I get this message about usb: 
 
<6>usbcore: registered new driver usbfs 
<6>usbcore: registered new driver hub 
... 
<7>ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) 
<6>ACPI: PCI interrupt 0000:00:07.4[D] -> GSI 10 (level, low) -> IRQ 10 
<6>ohci_hcd 0000:00:07.4: OHCI Host Controller 
<6>ohci_hcd 0000:00:07.4: irq 10, pci mem 0xeb000000 
<6>ohci_hcd 0000:00:07.4: new USB bus registered, assigned bus number 1 
<6>ohci_hcd 0000:00:07.4: AMD756 erratum 4 workaround 
<3>ohci_hcd 0000:00:07.4: init err (08700000 0000) 
<3>ohci_hcd 0000:00:07.4: can't start 
<3>ohci_hcd 0000:00:07.4: init error -75 
<6>ohci_hcd 0000:00:07.4: remove, state 0 
<6>ohci_hcd 0000:00:07.4: USB bus 1 deregistered 
<4>ohci_hcd: probe of 0000:00:07.4 failed with error -75 
<6>subfs 0.9 
 
I don't get any file at /proc/bus/usb and all devices connect to usb doesn't 
work. 
 
Comment 3 Ben Jackson 2005-02-16 18:24:58 UTC
i've just spotted the line 

PCI: cache line size of 64 is not supported by device 0000:00:02.1

in dmesg. could this be relevant? 4 of the broken ports are on that bus, though
2 of the remaining ports dont work, while 2 do.

from dmesg:

ACPI: PCI interrupt 0000:00:02.1[B] -> GSI 11 (level, low) -> IRQ 11
ehci_hcd 0000:00:02.1: PCI device 10de:005b (nVidia Corporation)
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: irq 11, pci mem 0xf0106000
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: USB 2.0 initialized, EHCI 1.00, driver 26 Oct 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 10 (level, low) -> IRQ 10
ohci_hcd 0000:00:02.0: PCI device 10de:005a (nVidia Corporation)
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: irq 10, pci mem 0xf0104000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 10 ports detected
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usb 2-1: new low speed USB device using ohci_hcd and address 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
input: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse<AE> Optical] on
usb-0000:00:02.0-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
Comment 4 Greg Kroah-Hartman 2005-02-17 08:57:09 UTC
Can you try 2.6.11-rc4 and see if it's still not working for you there?
If it isn't, please reopen this bug.

Note You need to log in before you can comment on or make changes to this bug.