I just noticed, on a second glance, that I've got my WLAN device on interrupt 11 too;
> 11: 1940 XT-PIC-level uhci_hcd:usb2, uhci_hcd:usb3, wlan0 My wlan device is using the ACX111 driver, which is my reason for using the -mm series on this test server as it hasn't yet made it to mainline... I'll try both without ACPI and without the card enabled and see what the results are. Just for reference though, the .16-mm kernel series worked fine for both USB and the ACX111 card (it is a Netgear WG311v2), so a change introduced in one of the .17-mm caused this to break... I'll do some further digging here and find out which kernel breaks it, and also see if I can get USB working properly in the current series by switching off ACPI and/or the ACX driver... This won't happen until late this weekend, so if people have suggestions for switches to try, email me and I'll give them a whirl Sun or so.. :)Johny Alan Stern wrote: > [Moved to linux-usb-devel in the hope of getting additional help] > > On Thu, 15 Jun 2006, Johny wrote: > >> Alan, >> >> See comments interspersed, thanks for your assistance :) >> >> Alan Stern wrote: >>> On Tue, 13 Jun 2006, Johny wrote: >>> >>>> Is this best suited to this mailing list? >>> It's appropriate. >>> >>>> I tried the kernel list with zero responses (so far ;), let me know if >>>> there is >>>> anywhere else this should go. >>> ... >>> >>>> Johny Ågotnes wrote: >>>>> All, >>>>> >>>>> My USB hub isn't recognised with the latest -mm series, whereas with >>>>> 2.6.16 vanilla it is picked up & used immediately. >>>>> >>>>> The error I get in dmesg is; >>>>> >>>>> hub 4-0:1.0: USB hub found >>>>> hub 4-0:1.0: 2 ports detected >>>>> usb 1-4: new high speed USB device using ehci_hcd and address 3 >>>>> ehci_hcd 0000:00:10.3: Unlink after no-IRQ? Controller is probably >>>>> using the wrong IRQ. >>> That last line is a clue. What interrupt numbers are assigned under >>> 2.6.16? If you unplug the SonyEricsson DCU-11 Cable before booting (and >>> leave it unplugged), what shows up in /proc/interrupts for both versions >>> of the kernel? >> See attached, both with the DCU-11 cable disconnected. > > From 2.6.16: > CPU0 > 0: 16101 XT-PIC timer > 1: 148 XT-PIC i8042 > 2: 0 XT-PIC cascade > 7: 0 XT-PIC parport0 > 9: 0 XT-PIC acpi > 10: 151 XT-PIC ehci_hcd:usb1, uhci_hcd:usb4 > 11: 0 XT-PIC uhci_hcd:usb2, uhci_hcd:usb3 > 12: 138 XT-PIC i8042 > 14: 172 XT-PIC ide0 > 15: 2458 XT-PIC ide1 > NMI: 0 > ERR: 0 > > From 2.6.17: > CPU0 > 0: 35651 XT-PIC-level timer > 1: 129 XT-PIC-level i8042 > 2: 0 XT-PIC-level cascade > 6: 3 XT-PIC-level floppy > 7: 0 XT-PIC-level parport0 > 9: 0 XT-PIC-level acpi > 10: 0 XT-PIC-level ehci_hcd:usb1, uhci_hcd:usb4 > 11: 1940 XT-PIC-level uhci_hcd:usb2, uhci_hcd:usb3, wlan0 > 12: 162 XT-PIC-level i8042 > 14: 171 XT-PIC-level ide0 > 15: 4251 XT-PIC-level ide1 > NMI: 0 > ERR: 0 > > There's nothing obviously wrong. > >>> Most likely this is a problem with the ACPI subsystem, not a USB problem. >>> >> I guessed USB due to the number of USB changes in the -mm series and, >> obviously, my USB devices stopped registering, however, I'd not know one >> from the other ;) > > What happens if you boot with "acpi=off" on the boot command line? > > Alan Stern > _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
