From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Vlasov Subject: Re: [linux-usb-devel] [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Date: Tue, 20 Jun 2006 16:09:37 +0400 Message-ID: <20060620120937.GR3206@master.mivlgu.local> References: <44953B4B.9040108@agotnes.com> <4497DA3F.80302@agotnes.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PY8tzLeNxmyMVNR3" Return-path: Received: from mivlgu.ru ([81.18.140.87]:63644 "EHLO master.mivlgu.local") by vger.kernel.org with ESMTP id S932606AbWFTMJk (ORCPT ); Tue, 20 Jun 2006 08:09:40 -0400 Content-Disposition: inline In-Reply-To: <4497DA3F.80302@agotnes.com> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Johny Cc: Andrew Morton , USB development list , kernel list , linux-usb-users@lists.sourceforge.net, linux-acpi@vger.kernel.org, Alan Stern , Chris Wedgwood --PY8tzLeNxmyMVNR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 20, 2006 at 09:21:35PM +1000, Johny wrote: [...] > Stock kernels break for me starting with 2.6.17-rc4 (I tested all rcs=20 > and also .17 itself), rc3 works a treat for using USB. I suspect the=20 > following line missing in dmesg for rc4 is the reason; >=20 > -PCI: Via IRQ fixup for 0000:00:11.1, from 255 to 11 Well, not exactly this line (0000:00:11.1 is the IDE controller, which is in legacy mode and therefore does not use its PCI interrupt), but the next similar line is for the USB 2.0 (EHCI) controller: -PCI: Via IRQ fixup for 0000:00:10.3, from 5 to 10 > See the following dmesg files for details; >=20 > http://www.agotnes.com/kernelStuff/dmesg-2.6.17-rc3-working > http://www.agotnes.com/kernelStuff/dmesg-2.6.17-rc4-not-working >=20 > And the diff, for convenience; >=20 > http://www.agotnes.com/kernelStuff/diff-rc3_rc4 Try as root: setpci -s 00:10.3 INTERRUPT_LINE=3D0a (this matches "ehci_hcd 0000:00:10.3: irq 10, ..." in dmesg). If after doing this USB works again (you will need to replug USB devices), the missing VIA IRQ quirk is definitely the problem. > I have a Via chipset motherboard (for my sins), further details=20 > available on request, again, for convenience, the lspci; >=20 > http://www.agotnes.com/kernelStuff/lspci You seem to have also the builtin audio and Ethernet on this board - these devices may have the same problem, if you tried to use them. > A couple of possible suspect patches introduced in the changelog for rc4= =20 > were (with the first one looking particularly interesting, the others=20 > less interesting as I go down the list); >=20 > [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) >=20 > I'm no kernel hacker, so I'm not sure how I'd isolate this one patch and= =20 > reverse / modify it. Please let me know how I can progress testing this= =20 > as I'm currently prevented from using USB with the latest set of kernels= =20 > on my test server... >=20 > I've got all kernels in the 2.6.17-rc1 through to .17 itself there, plus= =20 > a variety of mm ones too, so patches against any of those I can very=20 > easily test. >=20 > Please keep me cc'd as I'm not on all these lists, thanks :) >=20 > :)Johny >=20 > Johny ?gotnes wrote: > > didn't go through due to missing vger. ... > >=20 > > ------------------------------------------------------------------------ > >=20 > > Subject: > > Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues > > From: > > Johny > > Date: > > Sun, 18 Jun 2006 21:37:00 +1000 > > To: > > Alan Stern > >=20 > > To: > > Alan Stern > > CC: > > Johny , USB development list=20 > > , kernel list=20 > > , linux-acpi@kernel.org, akpm@osdl.org > >=20 > >=20 > > All, > >=20 > > I've now tested the following; > >=20 > > 2.6.17-rc6-mm2 with the following patch applied; > > --- > > git-acpi.patch from=20 > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17-rc= 6/2.6.17-rc6-mm2/broken-out/=20 > >=20 > > --- > >=20 > > With no difference to the end-result. > >=20 > > Next I stripped out 802.11 generic support and acx111 drivers from the= =20 > > kernel (including the acpi patches) to check if it clashes, but the sam= e=20 > > errors occur.... > >=20 > > Thirdly, I booted with acpi=3Doff on the command line with two kernels,= =20 > > the stock 2.6.17-rc6-mm2 (no acpi patch and including acx111) and the= =20 > > one including the acpi patch and no acx111, the results were; > >=20 > > acpi_patch; > > works a treat, picks up USB devices as expected. > >=20 > > stock; > > works a treat, picks up USB devices as expected, and my acx111 card=20 > > works too :) > >=20 > >=20 > > Now I'm looking for good suggestions again, this definitely looks like= =20 > > it is related to ACPI, hence the cc' to that list too, as requested by= =20 > > Andrew M. > >=20 > > I'm happy to apply patches / config changes as appropriate and for thos= e=20 > > who may ask for my .config files, please see; > >=20 > > http://www.agotnes.com/kernelStuff/config-2.6.17-rc6-mm2 > >=20 > > http://www.agotnes.com/kernelStuff/config-2.6.17-rc6-mm2git-acpi_patch > >=20 > > Also, I left the output of lspci there for reference; > >=20 > > http://www.agotnes.com/kernelStuff/lspci > >=20 > > Cheers, > >=20 > > :)Johny > >=20 > > 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= =20 > >>>>> if there is > >>>>> anywhere else this should go. > >>>> ... > >>>> > >>>>> Johny ?gotnes wrote: > >>>>>> All, > >>>>>> > >>>>>> My USB hub isn't recognised with the latest -mm series, whereas wi= th > >>>>>> 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= =20 > >>>> (and > >>>> leave it unplugged), what shows up in /proc/interrupts for both=20 > >>>> 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=20 > >>>> problem. > >>>> > >>> I guessed USB due to the number of USB changes in the -mm series and,= =20 > >>> obviously, my USB devices stopped registering, however, I'd not know= =20 > >>> one from the other ;) > >> > >> What happens if you boot with "acpi=3Doff" on the boot command line? > >> > >> Alan Stern --PY8tzLeNxmyMVNR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFEl+WBW82GfkQfsqIRAjBMAJ0S8JRa3Uo7cWkvHnwbiaqQX8tM8wCeOoT4 s1TGuCj+WYGA4PxxWL0JPeg= =dXL9 -----END PGP SIGNATURE----- --PY8tzLeNxmyMVNR3--