From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Stas Sergeev <stsp-D1TkPCJej5s@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
Linux kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Re: Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2)
Date: 01 Dec 2004 00:41:49 -0500 [thread overview]
Message-ID: <1101879708.8028.62.camel@d845pe> (raw)
In-Reply-To: <41A621DD.8060102-D1TkPCJej5s@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 134 bytes --]
Thanks for running the tests.
Please confirm that this patch make the problem go away in the
CONFIG_PNP_ACPI=y configuration.
-Len
[-- Attachment #2: pnp.patch --]
[-- Type: text/plain, Size: 612 bytes --]
===== drivers/acpi/pci_link.c 1.35 vs edited =====
--- 1.35/drivers/acpi/pci_link.c 2004-11-09 03:08:36 -05:00
+++ edited/drivers/acpi/pci_link.c 2004-12-01 00:38:18 -05:00
@@ -791,9 +791,16 @@
return 1;
}
+/*
+ * We'd like PNP to call this routine for the
+ * single ISA_USED value for each legacy device.
+ * But instead it calls us with each POSSIBLE setting.
+ * There is no ISA_POSSIBLE weight, so we simply use
+ * the (small) PCI_USING penalty.
+ */
void acpi_penalize_isa_irq(int irq)
{
- acpi_irq_penalty[irq] += PIRQ_PENALTY_ISA_USED;
+ acpi_irq_penalty[irq] += PIRQ_PENALTY_PCI_USING;
}
/*
next prev parent reply other threads:[~2004-12-01 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41990138.7080008@aknet.ru>
[not found] ` <41990138.7080008-D1TkPCJej5s@public.gmane.org>
2004-11-23 6:09 ` Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2) Len Brown
2004-11-24 18:12 ` Stas Sergeev
[not found] ` <41A4CF1C.6090503-D1TkPCJej5s@public.gmane.org>
2004-11-24 22:44 ` Len Brown
2004-11-25 18:18 ` Stas Sergeev
[not found] ` <41A621DD.8060102-D1TkPCJej5s@public.gmane.org>
2004-12-01 5:41 ` Len Brown [this message]
2004-12-01 5:44 ` Len Brown
2004-12-02 16:52 ` Stas Sergeev
2004-11-26 0:53 Li, Shaohua
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=1101879708.8028.62.camel@d845pe \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=stsp-D1TkPCJej5s@public.gmane.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