From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Badness in iosapic_unregister_intr
Date: Tue, 01 Mar 2005 04:51:48 +0000 [thread overview]
Message-ID: <4223F4E4.2050109@jp.fujitsu.com> (raw)
In-Reply-To: <20050228180600.GB28741@parcelfarce.linux.theplanet.co.uk>
Hi Matthew,
Matthew Wilcox wrote:
> Not sure where the problem lies on this one ...
>
> On an hp rx4640, at shutdown of an unmodified 2.6.11-rc5 kernel, I get:
>
> Rebooting... ACPI: PCI interrupt for device 0000:a1:04.0 disabled
> iosapic_unregister_intr(4294967295) unbalanced
> Badness in iosapic_unregister_intr at arch/ia64/kernel/iosapic.c:636
> ACPI: PCI interrupt for device 0000:a1:04.1 disabled
> iosapic_unregister_intr(4294967295) unbalanced
> Badness in iosapic_unregister_intr at arch/ia64/kernel/iosapic.c:636
> ACPI: PCI interrupt for device 0000:a1:06.0 disabled
> iosapic_unregister_intr(4294967295) unbalanced
> Badness in iosapic_unregister_intr at arch/ia64/kernel/iosapic.c:636
> ACPI: PCI interrupt for device 0000:a1:06.1 disabled
> iosapic_unregister_intr(4294967295) unbalanced
> Badness in iosapic_unregister_intr at arch/ia64/kernel/iosapic.c:636
>
> Anyone else seeing it? I wonder if it only happens for devices behind
> a PCI-PCI bridge:
>
> 0000:a0:02.0 PCI bridge: IBM PCI-X to PCI-X Bridge (rev 02)
> 0000:a1:04.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (rev 01)
> 0000:a1:04.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (rev 01)
> 0000:a1:06.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (rev 01)
> 0000:a1:06.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (rev 01)
>
I think the following patch will fix this problem.
Could you try it?
Thanks,
Kenji Kaneshige
--
This patch fix the error check in acpi_pci_irq_disable().
Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
---
linux-2.6.11-rc5-kanesige/drivers/acpi/pci_irq.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff -puN drivers/acpi/pci_irq.c~fix_acpi_pci_irq_disable drivers/acpi/pci_irq.c
--- linux-2.6.11-rc5/drivers/acpi/pci_irq.c~fix_acpi_pci_irq_disable 2005-03-01 13:50:24.000000000 +0900
+++ linux-2.6.11-rc5-kanesige/drivers/acpi/pci_irq.c 2005-03-01 13:50:24.000000000 +0900
@@ -460,7 +460,7 @@ void
acpi_pci_irq_disable (
struct pci_dev *dev)
{
- u32 gsi = 0;
+ int gsi = 0;
u8 pin = 0;
int edge_level = ACPI_LEVEL_SENSITIVE;
int active_high_low = ACPI_ACTIVE_LOW;
@@ -487,10 +487,10 @@ acpi_pci_irq_disable (
* If no PRT entry was found, we'll try to derive an IRQ from the
* device's parent bridge.
*/
- if (!gsi)
+ if (gsi < 0)
gsi = acpi_pci_irq_derive(dev, pin,
&edge_level, &active_high_low);
- if (!gsi)
+ if (gsi < 0)
return_VOID;
/*
_
next prev parent reply other threads:[~2005-03-01 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 18:06 Badness in iosapic_unregister_intr Matthew Wilcox
2005-02-28 18:50 ` Grant Grundler
2005-03-01 4:51 ` Kenji Kaneshige [this message]
2005-03-01 13:01 ` Matthew Wilcox
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=4223F4E4.2050109@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=linux-ia64@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