From: Len Brown <len.brown@intel.com>
To: Darren Dupre <darren@dmdtech.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: irq 9: nobody cared! on 2.6.0-test9
Date: 23 Nov 2003 01:32:13 -0500 [thread overview]
Message-ID: <1069569132.3254.69.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE00184C9EB@hdsmsx402.hd.intel.com>
> ACPI: INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x3]
trigger[0x3])
This requests level/low for SCI on IRQ9
> IOAPIC[0]: Set PCI routing entry (2-9 -> 0x71 -> IRQ 9 Mode:1
Active:1)
This indicates that we set IRQ9 to level/low, as requested.
Though 2.6.0 lacks the print_IO_APIC patch, so you'd need to apply this
and re-collect dmesg to really confirm the IOAPIC is programmed
correctly:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/2.6.0-test9/
If you boot with pci=noacpi, does the system run properly (including
/proc/interrupts showing ACPI interrupts when you, say, press the power
button)
> http://bugme.osdl.org/show_bug.cgi?id=1352
Though I'd love to be wrong, I think this one is a different failure.
Please file a new one per below. Would also be good to verify that the
latest 2.4 kernel does the same thing.
thanks,
-Len
How to file a bug against ACPI:
http://bugzilla.kernel.org/
Category: Power Management
Component: ACPI
Please attach the output from dmidecode, available in /usr/sbin/, or
here:
http://www.nongnu.org/dmidecode/
Please attach the output from acpidmp, available in /usr/sbin/, or in
here
http://www.intel.com/technology/iapc/acpi/downloads/pmtools-20010730.tar.gz
Please attach /proc/interrupts and the dmesg output showing the failure,
if possible.
next parent reply other threads:[~2003-11-23 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE00184C9EB@hdsmsx402.hd.intel.com>
2003-11-23 6:32 ` Len Brown [this message]
2003-11-23 4:31 irq 9: nobody cared! on 2.6.0-test9 Darren Dupre
2003-11-23 4:58 ` Linus Torvalds
2003-11-23 5:49 ` Joshua Schmidlkofer
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=1069569132.3254.69.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=darren@dmdtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.