From: Johny <kernel@agotnes.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Johny <kernel@agotnes.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb-users@lists.sourceforge.net,
linux-usb-devel@lists.sourceforge.net, stern@rowland.harvard.edu,
Chris Wedgwood <cw@f00f.org>,
sergio@sergiomb.no-ip.org, vsu@altlinux.ru
Subject: Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]
Date: Wed, 21 Jun 2006 20:50:04 +1000 [thread overview]
Message-ID: <4499245C.8040207@agotnes.com> (raw)
In-Reply-To: <20060620044003.4287426d.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 4718 bytes --]
Andrew,
Success :)
I've attached the patches used vs 2.6.17-rc4 (stock) and 2.6.17-rc6-mm2
(as the VIA include lists were different). I simply made the change
manually, based on your and others' inputs (it seemed the simpler option).
Both kernels now boot, and all USB devices are recognised correctly.
Sergio, you can find attached lspci -n output as requested, and indeed,
I run in XT_PIC mode for interrupts.
I did NOT run the setpci command as requested by Sergey, let me know if
that helps anyone considering the fix sorted this out.
Where to from here I'll leave with you guys, an entry in the quirks.c
file certainly is warranted for my motherboard...
I'm happy to test further patches if required on this, for now I'm on
rc6-mm2 with my attached patch to have both ACX111 networking and USB
working good :)
Cheers!
:)Johny
Andrew Morton wrote:
> On Tue, 20 Jun 2006 21:21:35 +1000
> Johny <kernel@agotnes.com> wrote:
>
>> 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.
>
> Thanks for persisting with this.
>
>> 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
>
> yes, that looks suspicious.
>
>> 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
>
> This one, I'd expect.
>
>> [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)
>>
>
> You could try a `patch -R' of the below.
>
> commit 75cf7456dd87335f574dcd53c4ae616a2ad71a11
> Author: Chris Wedgwood <cw@f00f.org>
> Date: Tue Apr 18 23:57:09 2006 -0700
>
> [PATCH] PCI quirk: VIA IRQ fixup should only run for VIA southbridges
>
> Alan Cox pointed out that the VIA 'IRQ fixup' was erroneously running
> on my system which has no VIA southbridge (but I do have a VIA IEEE
> 1394 device).
>
> This should address that. I also changed "Via IRQ" to "VIA IRQ"
> (initially I read Via as a capitalized via (by way/means of).
>
> Signed-off-by: Chris Wedgwood <cw@f00f.org>
> Acked-by: Jeff Garzik <jeff@garzik.org>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index c42ae2c..19e2b17 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -642,13 +642,15 @@ static void quirk_via_irq(struct pci_dev
> new_irq = dev->irq & 0xf;
> pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);
> if (new_irq != irq) {
> - printk(KERN_INFO "PCI: Via IRQ fixup for %s, from %d to %d\n",
> + printk(KERN_INFO "PCI: VIA IRQ fixup for %s, from %d to %d\n",
> pci_name(dev), irq, new_irq);
> udelay(15); /* unknown if delay really needed */
> pci_write_config_byte(dev, PCI_INTERRUPT_LINE, new_irq);
> }
> }
> -DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
> +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686, quirk_via_irq);
> +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686_4, quirk_via_irq);
> +DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686_5, quirk_via_irq);
>
> /*
> * VIA VT82C598 has its device ID settable and many BIOSes
>
>
> If you have trouble getting it to apply, just manually replace all the
> DECLARE_PCI_FIXUP_ENABLE lines at the end of quirk_via_irq() with the
> single line
>
> DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
>
[-- Attachment #2: via.patch-rc4stock --]
[-- Type: text/plain, Size: 634 bytes --]
--- usb/drivers/pci/quirks.c 2006-06-21 20:18:56.000000000 +1000
+++ linux-2.6.17-rc4/drivers/pci/quirks.c 2006-06-21 20:13:15.000000000 +1000
@@ -648,9 +648,7 @@
pci_write_config_byte(dev, PCI_INTERRUPT_LINE, new_irq);
}
}
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686_4, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686_5, quirk_via_irq);
+DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
/*
* VIA VT82C598 has its device ID settable and many BIOSes
[-- Attachment #3: via.patch-rc6-mm2 --]
[-- Type: text/plain, Size: 995 bytes --]
--- usb/drivers/pci/quirks.c 2006-06-21 20:25:41.000000000 +1000
+++ linux-2.6.17-rc6-mm2/drivers/pci/quirks.c 2006-06-21 20:25:08.000000000 +1000
@@ -662,13 +662,7 @@
pci_write_config_byte(dev, PCI_INTERRUPT_LINE, new_irq);
}
}
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C586_0, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C586_1, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C586_2, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C586_3, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686_4, quirk_via_irq);
-DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C686_5, quirk_via_irq);
+DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq);
/*
* VIA VT82C598 has its device ID settable and many BIOSes
[-- Attachment #4: lspci-n --]
[-- Type: text/plain, Size: 360 bytes --]
00:00.0 0600: 1106:3205
00:01.0 0604: 1106:b198
00:08.0 0280: 104c:9066
00:10.0 0c03: 1106:3038 (rev 80)
00:10.1 0c03: 1106:3038 (rev 80)
00:10.2 0c03: 1106:3038 (rev 80)
00:10.3 0c03: 1106:3104 (rev 82)
00:11.0 0601: 1106:3177
00:11.1 0101: 1106:0571 (rev 06)
00:11.5 0401: 1106:3059 (rev 50)
00:12.0 0200: 1106:3065 (rev 74)
01:00.0 0300: 1106:7205 (rev 01)
next prev parent reply other threads:[~2006-06-21 10:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 11:38 [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Johny Ågotnes
2006-06-20 11:21 ` Johny
2006-06-20 11:40 ` Andrew Morton
2006-06-20 13:22 ` Sergio Monteiro Basto
2006-06-21 10:50 ` Johny [this message]
2006-06-22 0:36 ` who I do know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Sergio Monteiro Basto
2006-06-22 0:47 ` Randy.Dunlap
2006-06-22 1:04 ` how I " Sergio Monteiro Basto
2006-06-22 4:08 ` Randy.Dunlap
2006-06-22 11:56 ` Sergio Monteiro Basto
2006-06-22 21:29 ` Randy.Dunlap
2006-06-22 22:46 ` Sergio Monteiro Basto
2006-06-22 22:54 ` Chris Wedgwood
2006-06-23 1:00 ` Sergio Monteiro Basto
2006-06-23 1:39 ` Randy.Dunlap
2006-06-23 1:50 ` Sergio Monteiro Basto
2006-06-23 2:02 ` Randy.Dunlap
2006-06-28 1:08 ` [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergio Monteiro Basto
2006-06-23 1:40 ` how I know if a interrupt is ioapic_edge_type or ioapic_level_type? [Was Re: [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues]] Johny
2006-06-22 23:25 ` Randy.Dunlap
2006-06-23 1:30 ` Sergio Monteiro Basto
2006-06-23 15:31 ` [linux-usb-devel] who I do " David Brownell
2006-06-20 12:09 ` [linux-usb-devel] [Fwd: Re: [Linux-usb-users] Fwd: Re: 2.6.17-rc6-mm2 - USB issues] Sergey Vlasov
2006-06-20 13:30 ` Sergio Monteiro Basto
2006-06-20 13:59 ` Sergey Vlasov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4499245C.8040207@agotnes.com \
--to=kernel@agotnes.com \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=sergio@sergiomb.no-ip.org \
--cc=stern@rowland.harvard.edu \
--cc=vsu@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox