From: Patrick Reynolds <reynolds@cs.duke.edu>
To: Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI and broken PCI IRQ sharing on Asus M5N laptop
Date: Mon, 10 May 2004 01:07:31 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.58.0405100054430.20030@shekel.cs.duke.edu> (raw)
In-Reply-To: <1084160004.12352.82.camel@dhcppc4>
On Sun, 9 May 2004, Len Brown wrote:
> On Sun, 2004-05-09 at 20:44, Patrick Reynolds wrote:
> > Booting with default parameters puts the i8042 psmouse channel, the
> > Intel
> > 8x0 sound card, and the Cardbus controller all on IRQ 12. The mouse
> try booting with "acpi_irq_isa=12"
That worked. The interrupts got redistributed like so:
6: 172 XT-PIC Intel 82801DB-ICH4, yenta
7: 3014 XT-PIC uhci_hcd, yenta, ndiswrapper
8: 4 XT-PIC rtc
9: 188 XT-PIC acpi
12: 1028 XT-PIC i8042
> I'd be interested to see your dmesg and /proc/interrupts from 2.6.1
It piles the sound and cardbus onto IRQ 5, along with a USB that I'm
actually using. For some reason it doesn't touch IRQ 6. Here are dmesg
and /proc/interrupts from 2.6.1, 2.6.6 w/ acpi_irq_isa=12, and 2.6.6 w/
your patch:
http://www.cs.duke.edu/~reynolds/acpi-notes
On Sun, 9 May 2004, Len Brown wrote:
> On the assumption that cmdline works, please try this patch
> (without any cmdline param).
>
> It simply tweaks the heuristic and makes IRQ12 less attractive compared
> to the others.
That also worked and produced the same IRQ mapping as acpi_irq_isa=12.
Thanks! If you want any more logs, etc, let me know.
--Patrick
next prev parent reply other threads:[~2004-05-10 5:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FAF0D@hdsmsx403.hd.intel.com>
2004-05-10 3:33 ` Len Brown
2004-05-10 5:07 ` Patrick Reynolds [this message]
2004-05-10 15:25 ` Franklin Marmon
[not found] <A6974D8E5F98D511BB910002A50A6647615FAF02@hdsmsx403.hd.intel.com>
2004-05-10 2:47 ` Len Brown
2004-05-10 0:44 Patrick Reynolds
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=Pine.GSO.4.58.0405100054430.20030@shekel.cs.duke.edu \
--to=reynolds@cs.duke.edu \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®