Firstly, apologies for a) the massive x-post and b) the time taken to get back to people... Please let me know where this is most appropriately dealt with and I'll keep it off other lists, considering the latest information;
Andrew - please note - this is not a problem exclusive to the -mm series, on testing various combos I found it in the stock series too. Stock kernels break for me starting with 2.6.17-rc4 (I tested all rcs and also .17 itself), rc3 works a treat for using USB. I suspect the following line missing in dmesg for rc4 is the reason; -PCI: Via IRQ fixup for 0000:00:11.1, from 255 to 11 See the following dmesg files for details; http://www.agotnes.com/kernelStuff/dmesg-2.6.17-rc3-working http://www.agotnes.com/kernelStuff/dmesg-2.6.17-rc4-not-working And the diff, for convenience; http://www.agotnes.com/kernelStuff/diff-rc3_rc4 I have a Via chipset motherboard (for my sins), further details available on request, again, for convenience, the lspci; http://www.agotnes.com/kernelStuff/lspci A couple of possible suspect patches introduced in the changelog for rc4 were (with the first one looking particularly interesting, the others less interesting as I go down the list); [PATCH] PCI quirk: VIA IRQ fixup should only run for VIA southbridges [PATCH] x86_64: avoid IRQ0 ioapic pin collision [PATCH] PCI: fix via irq SATA patch [ALSA] via82xx - Use DXS_SRC as default for VIA8235/8237/8251 chips [ALSA] via82xx: tweak VT8251 workaround [ALSA] via82xx: add support for VIA VT8251 (AC'97) I'm no kernel hacker, so I'm not sure how I'd isolate this one patch and reverse / modify it. Please let me know how I can progress testing this as I'm currently prevented from using USB with the latest set of kernels on my test server... I've got all kernels in the 2.6.17-rc1 through to .17 itself there, plus a variety of mm ones too, so patches against any of those I can very easily test. Please keep me cc'd as I'm not on all these lists, thanks :) :)Johny Johny Ågotnes wrote: > didn't go through due to missing vger. ... > > ------------------------------------------------------------------------ > > Subject: > Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues > From: > Johny <[EMAIL PROTECTED]> > Date: > Sun, 18 Jun 2006 21:37:00 +1000 > To: > Alan Stern <[EMAIL PROTECTED]> > > To: > Alan Stern <[EMAIL PROTECTED]> > CC: > Johny <[EMAIL PROTECTED]>, USB development list > <linux-usb-devel@lists.sourceforge.net>, kernel list > <linux-kernel@vger.kernel.org>, [EMAIL PROTECTED], [EMAIL PROTECTED] > > > All, > > I've now tested the following; > > 2.6.17-rc6-mm2 with the following patch applied; > --- > git-acpi.patch from > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc6/2.6.17-rc6-mm2/broken-out/ > > > --- > > With no difference to the end-result. > > Next I stripped out 802.11 generic support and acx111 drivers from the > kernel (including the acpi patches) to check if it clashes, but the same > errors occur.... > > Thirdly, I booted with acpi=off on the command line with two kernels, > the stock 2.6.17-rc6-mm2 (no acpi patch and including acx111) and the > one including the acpi patch and no acx111, the results were; > > acpi_patch; > works a treat, picks up USB devices as expected. > > stock; > works a treat, picks up USB devices as expected, and my acx111 card > works too :) > > > Now I'm looking for good suggestions again, this definitely looks like > it is related to ACPI, hence the cc' to that list too, as requested by > Andrew M. > > I'm happy to apply patches / config changes as appropriate and for those > who may ask for my .config files, please see; > > http://www.agotnes.com/kernelStuff/config-2.6.17-rc6-mm2 > > http://www.agotnes.com/kernelStuff/config-2.6.17-rc6-mm2git-acpi_patch > > Also, I left the output of lspci there for reference; > > http://www.agotnes.com/kernelStuff/lspci > > Cheers, > > :)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
