From: Len Brown <len.brown@intel.com>
To: Stas Sergeev <stsp@aknet.ru>
Cc: Andrew Morton <akpm@osdl.org>,
Linux kernel <linux-kernel@vger.kernel.org>,
ACPI Developers <acpi-devel@lists.sourceforge.net>
Subject: Re: Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2)
Date: 23 Nov 2004 01:09:09 -0500 [thread overview]
Message-ID: <1101190148.19999.394.camel@d845pe> (raw)
In-Reply-To: <41990138.7080008@aknet.ru>
> ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15) *9
This is a common BIOS bug. It advertises that LNK1 is presently set
to IRQ9, but tells us that IRQ9 is actually illegal for that link;
so Linus has to choose a legal one. (no, we can't just leave it there,
as that breaks other systems). But apparently we choose poorly.
> Probing IDE interface ide1...
> hdc: ASUS CD-S500/A, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
IDE probes out and grabs its hard-coded IRQ15.
> ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 15
> PCI: setting IRQ 15 as level-triggered
> ACPI: PCI interrupt 0000:00:1f.4[C] -> GSI 15 (level, low) -> IRQ 15
> uhci_hcd 0000:00:1f.4: Intel Corp. 82801BA/BAM USB (Hub #2)
Here we assign LNK1 to IRQ15 for the benefit of USB,
which, of course, kills your IDE on IRQ 15. This
is a Linux bug -- but one I thought we fixed some time back.
> hdc: lost interrupt
----------
I'm surprised that you're just seeing this now in 2.6.10.
Did 2.6.9 work correctly? If so, can you send me the
2.6.9 dmesg?
Any difference with CONFIG_PNP=n?
thanks,
-Len
next prev parent reply other threads:[~2004-11-23 6:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 19:19 2.6.10-rc1-mm5 (and ide-cd) Stas Sergeev
2004-11-23 6:09 ` Len Brown [this message]
2004-11-24 18:12 ` Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2) Stas Sergeev
2004-11-24 22:44 ` Len Brown
2004-11-25 18:18 ` Stas Sergeev
2004-12-01 5:41 ` [ACPI] " Len Brown
2004-12-01 5:44 ` Len Brown
2004-12-02 16:52 ` Stas Sergeev
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=1101190148.19999.394.camel@d845pe \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.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