From: Len Brown <len.brown@intel.com>
To: Jes Sorensen <jes@trained-monkey.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
ACPI Developers <acpi-devel@lists.sourceforge.net>,
Jesse Barnes <jbarnes@sgi.com>
Subject: Re: [patch] 2.6.1-mm3 acpi frees free irq0
Date: 26 Jan 2004 15:30:31 -0500 [thread overview]
Message-ID: <1075149023.2484.4.camel@dhcppc4> (raw)
In-Reply-To: <16390.43574.867869.286685@gargle.gargle.HOWL>
Accepted.
thanks,
-Len
On Thu, 2004-01-15 at 09:56, Jes Sorensen wrote:
> Hi,
>
> There is a bug in the ACPI code found in 2.6.1-mm3 where if it can't
> find the interrupt source for the ACPI System Control Interrupt Handler,
> it end up trying to free irq 0.
>
> Included patch fixes the problem.
>
> Cheers,
> Jes
>
> --- linux-2.6.1-mm3/drivers/acpi/osl.c~ Wed Jan 14 05:00:25 2004
> +++ linux-2.6.1-mm3/drivers/acpi/osl.c Thu Jan 15 06:43:28 2004
> @@ -257,13 +257,13 @@
> return AE_OK;
> }
> #endif
> - acpi_irq_irq = irq;
> acpi_irq_handler = handler;
> acpi_irq_context = context;
> if (request_irq(irq, acpi_irq, SA_SHIRQ, "acpi", acpi_irq)) {
> printk(KERN_ERR PREFIX "SCI (IRQ%d) allocation failed\n", irq);
> return AE_NOT_ACQUIRED;
> }
> + acpi_irq_irq = irq;
>
> return AE_OK;
> }
> @@ -271,12 +271,13 @@
> acpi_status
> acpi_os_remove_interrupt_handler(u32 irq, OSD_HANDLER handler)
> {
> - if (acpi_irq_handler) {
> + if (irq) {
> #if defined(CONFIG_IA64) || defined(CONFIG_PCI_USE_VECTOR)
> irq = acpi_irq_to_vector(irq);
> #endif
> free_irq(irq, acpi_irq);
> acpi_irq_handler = NULL;
> + acpi_irq_irq = 0;
> }
>
> return AE_OK;
next prev parent reply other threads:[~2004-01-26 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 14:56 [patch] 2.6.1-mm3 acpi frees free irq0 Jes Sorensen
2004-01-26 20:30 ` Len Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 17:19 Brown, Len
2004-01-15 22:01 ` Jes Sorensen
2004-01-18 6:29 Yu, Luming
2004-01-19 7:59 ` Jes Sorensen
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=1075149023.2484.4.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=jbarnes@sgi.com \
--cc=jes@trained-monkey.org \
--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