From: Len Brown <len.brown@intel.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
David van Hoose <david.vanhoose@comcast.net>
Subject: Re: Shared ACPI/USB IRQ working in 2.6 but not in 2.4
Date: 07 Nov 2003 06:03:36 -0500 [thread overview]
Message-ID: <1068203016.2684.976.camel@dhcppc4> (raw)
In-Reply-To: <Pine.LNX.4.44.0311060949340.7886-100000@logos.cnet>
The details of this issue are here:
http://bugzilla.kernel.org/show_bug.cgi?id=1283
Looks like the IOAPIC is in a different state in 2.4 and 2.6 before ACPI
programs it. Also 2.6 has sis_apic_bug code that 2.4 does not -- though
I don't know yet if it actually runs on this box.
cheers,
-Len
On Thu, 2003-11-06 at 07:05, Marcelo Tosatti wrote:
> Hi,
>
> David van Hoose started having problems with USB on 2.4.23-pre5. USB
> device and acpi were now using irq 20:
>
> host/usb-ohci.c: USB OHCI at membase 0xe081a000, IRQ 20
>
> /proc/interrupts:
>
> 20: 1 IO-APIC-level acpi, usb-ohci
>
>
> Which makes the USB device not work.
>
> With -pre4 the USB device was using interrupt 9, because acpi failed to
> find the correct IRQ:
>
> pci_irq-0302 [18] acpi_pci_irq_derive : Unable to derive IRQ for device 00:03.0
> PCI: No IRQ known for interrupt pin A of device 00:03.0
> host/usb-ohci.c: USB OHCI at membase 0xe081a000, IRQ 9
>
> Now 2.6 assigns interrupt 20 to acpi and usb-ohci just like in
> 2.4.23-pre5+, but the USB device works!
>
> Anyone has an idea why the interrupt sharing works with 2.6 but not with
> 2.4?
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2003-11-07 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 12:05 Shared ACPI/USB IRQ working in 2.6 but not in 2.4 Marcelo Tosatti
2003-11-07 11:03 ` Len Brown [this message]
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=1068203016.2684.976.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=david.vanhoose@comcast.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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