All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Paul Surgeon <surgpub@telkomsa.net>
Cc: linux-acpi@vger.kernel.org
Subject: Re: ACPI screwing up USB ehci_hcd with kernel 2.6.16.18
Date: Wed, 31 May 2006 00:57:08 +0100	[thread overview]
Message-ID: <1149033428.2881.24.camel@localhost.portugal> (raw)
In-Reply-To: <200605302226.52705.surgpub@telkomsa.net>

[-- Attachment #1: Type: text/plain, Size: 2365 bytes --]

Hi,
Some of yours hardware have same IDs than mine 

you have as relevant ;
cat /usr/include/linux/pci_ids.h  |  grep 3189
#define PCI_DEVICE_ID_VIA_8377_0        0x3189
#define PCI_DEVICE_ID_VIA_82C586_1      0x0571
#define PCI_DEVICE_ID_VIA_82C586_2      0x3038
#define PCI_DEVICE_ID_VIA_8237          0x3227
#define PCI_DEVICE_ID_NVIDIA_GEFORCE4_TI_4800_8X    0x0281

I have 
PCI_DEVICE_ID_VIA_82C586_1 
PCI_DEVICE_ID_VIA_82C586_2
PCI_DEVICE_ID_VIA_8237_SATA 

On kernel 2.6.16.17 enter this patch which, if you don't use kernel-rc
version doesn't change nothing :D
http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%
2Fv2.6%2Fincr%2Fpatch-2.6.16.16-17.bz2;z=12

if you compile your kernel, you could try remove this 2 lines, 
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); 
to see if ACPI IRQ routing works better: 

Well, this can be done like this 
cd drives/pci
edit and delete the lines on quirks.c
cd ../..
make bzImage
(backup mv /boot/vmlinuz-2.6.16.18 /boot/vmlinuz-2.6.16.18.orig)
mv arch/x86_64/boot/bzImage /boot/vmlinuz-2.6.16.18)
and reboot 

My question which is not meaningfully, because I made a little
confusion, but is if you has used other version of kernel before ?  

Maybe the best is open o bug in bugzilla with a complete dmesg and one
lspci -n , etc.

I am little curious, why your interrupts are XT-PIC and not IO-APIC

Thanks for the report ,
On Tue, 2006-05-30 at 22:26 +0200, Paul Surgeon wrote:
> On Monday 29 May 2006 14:11, Sergio Monteiro Basto wrote:
> > and before ?
> > can you send lspci -n ?
> 
> I can send you a lot more than that.  :)
> I attached a zip file containing 10 log files which hopefully won't be an 
> issue with the mailing list. (a single uncompressed dmesg log is 15KB so 
> hopefully an 18KB zip file won't be a problem)
> 
> There are two versions of each log file. One before I added acpi=noirq to the 
> boot options and one after I added acpi=noirq to the boot options.
> 
> logs :
> dmesg (dmesg after bootup - USB storage device not plugged in)
> dmesg-usb-plugin  (dmesg output after plugging in USB storage device)
> interrupts
> lspci
> lspci-n
> 
> Hope that helps a bit
> Paul

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]

  parent reply	other threads:[~2006-05-30 23:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28 19:50 ACPI screwing up USB ehci_hcd with kernel 2.6.16.18 Paul Surgeon
2006-05-29 12:11 ` Sergio Monteiro Basto
     [not found]   ` <200605302226.52705.surgpub@telkomsa.net>
2006-05-30 23:57     ` Sergio Monteiro Basto [this message]
2006-06-05 16:45 ` Bjorn Helgaas
2006-06-09 21:34   ` Bjorn Helgaas
2006-06-10  9:05     ` Paul Surgeon

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=1149033428.2881.24.camel@localhost.portugal \
    --to=sergio@sergiomb.no-ip.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=surgpub@telkomsa.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.