From: Len Brown <len.brown@intel.com>
To: Patrick Reynolds <reynolds@cs.duke.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI and broken PCI IRQ sharing on Asus M5N laptop
Date: 09 May 2004 22:47:25 -0400 [thread overview]
Message-ID: <1084157245.12359.51.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FAF02@hdsmsx403.hd.intel.com>
On Sun, 2004-05-09 at 20:44, Patrick Reynolds wrote:
> I posted yesterday about how the built-in psmouse in my Asus M5N
> (M5200N)
> laptop is broken under recent 2.6 kernels. I believe I have tracked
> the
> problem down to broken IRQ sharing. It's broken under 2.6.2 through
> 2.6.6-rc3-bk11, but it works fine under 2.6.1.
>
> Booting with default parameters puts the i8042 psmouse channel, the
> Intel
> 8x0 sound card, and the Cardbus controller all on IRQ 12. The mouse
> is
> almost unusable, sampling 3-4 times per second. The sound works
> fine. In
> /proc/interrupts I get
> 12: 310 XT-PIC i8042, Intel 82801DB-ICH4, yenta
> The interrupt count goes up when I play MP3s, but not when I move the
> mouse.
try booting with "acpi_irq_isa=12"
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 12
There are 3 BIOS bugs here:
1. LNKB is marked disabled, yet referenced
Linux handes this
2. Current Setting for LNKB is not in possible setting list
Linux handles -- though apparently this fixes some systems
and breaks others.
3. IRQ12 marked as a viable IRQ for sharing sound and mouse
Linux falls for this hook, line, and sinker.
I'd be interested to see your dmesg and /proc/interrupts from 2.6.1
thanks,
-Len
next parent reply other threads:[~2004-05-10 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FAF02@hdsmsx403.hd.intel.com>
2004-05-10 2:47 ` Len Brown [this message]
[not found] <A6974D8E5F98D511BB910002A50A6647615FAF0D@hdsmsx403.hd.intel.com>
2004-05-10 3:33 ` ACPI and broken PCI IRQ sharing on Asus M5N laptop Len Brown
2004-05-10 5:07 ` Patrick Reynolds
2004-05-10 15:25 ` Franklin Marmon
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=1084157245.12359.51.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reynolds@cs.duke.edu \
/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