From: Con Kolivas <kernel@kolivas.org>
To: "Grover, Andrew" <andrew.grover@intel.com>,
"Zwane Mwaikambo" <zwane@linuxpower.ca>
Cc: "Paul P Komkoff Jr" <i@stingr.net>, <linux-kernel@vger.kernel.org>
Subject: Re: ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1)
Date: Tue, 3 Jun 2003 12:01:09 +1000 [thread overview]
Message-ID: <200306031201.09642.kernel@kolivas.org> (raw)
In-Reply-To: <200306031012.07832.kernel@kolivas.org>
On Tue, 3 Jun 2003 10:12, Con Kolivas wrote:
> On Tue, 3 Jun 2003 07:01, Grover, Andrew wrote:
> > I suspect this machine should be falling into one of the cases before
> > this last one, thus making ACPI not use C3, or check for bus-mastering.
> > I especially think this is the case because this appears to be a desktop
> > system. It should not have a C3 address or a plvl3_lat less than 1000,
> > yet it appears to, yes?
>
> Sorry Andy I have no idea what you're talking about. Are there some details
> specifically about this machine you want me to provide?
At least I can provide you with the acpi info from dmesg when it booted, and
I'll try Zwane's hack in the near future to see if it helps.
Jun 1 16:32:45 localhost kernel: ACPI: Interpreter enabled
Jun 1 16:32:45 localhost kernel: ACPI: Using IOAPIC for interrupt routing
Jun 1 16:32:45 localhost kernel: ACPI: System [ACPI] (supports S0 S1 S4 S5)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5
6 7 9 10 11 12 14 15)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5
6 7 *9 10 11 12 14 15)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5
6 7 *9 10 11 12 14 15)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5
6 7 *9 10 11 12 14 15)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5
6 7 9 *10 11 12 14 15)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5
6 7 *9 10 11 12 14 15)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5
6 7 9 10 11 12 14 15, disabled)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5
6 7 9 10 *11 12 14 15)
Jun 1 16:32:45 localhost kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
Jun 1 16:32:45 localhost kernel: PCI: Probing PCI hardware (bus 00)
Jun 1 16:32:45 localhost kernel: PCI: Ignoring BAR0-3 of IDE controller
00:1f.1
Jun 1 16:32:45 localhost kernel: Transparent bridge - Intel Corp.
82801BA/CA/DB PCI Bridge
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0._PRT]
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI1._PRT]
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Routing Table
[\_SB_.PCI0.PCI2._PRT]
Jun 1 16:32:45 localhost kernel: PCI: Probing PCI hardware
Jun 1 16:32:45 localhost kernel: ACPI: PCI Interrupt Link [LNKG] enabled at
IRQ 11
Jun 1 16:32:45 localhost kernel: IOAPIC[0]: Set PCI routing entry (2-16 ->
0xb1 -> IRQ 16)
Jun 1 16:32:45 localhost kernel: 00:00:1d[A] -> 2-16 -> IRQ 16
Jun 1 16:32:45 localhost kernel: IOAPIC[0]: Set PCI routing entry (2-19 ->
0xb9 -> IRQ 19)
Jun 1 16:32:45 localhost kernel: 00:00:1d[B] -> 2-19 -> IRQ 19
Jun 1 16:32:45 localhost kernel: IOAPIC[0]: Set PCI routing entry (2-18 ->
0xc1 -> IRQ 18)
Jun 1 16:32:45 localhost kernel: 00:00:1d[C] -> 2-18 -> IRQ 18
Jun 1 16:32:45 localhost kernel: IOAPIC[0]: Set PCI routing entry (2-23 ->
0xc9 -> IRQ 23)
Jun 1 16:32:45 localhost kernel: 00:00:1d[D] -> 2-23 -> IRQ 23
Jun 1 16:32:45 localhost kernel: Pin 2-18 already programmed
Jun 1 16:32:45 localhost kernel: IOAPIC[0]: Set PCI routing entry (2-17 ->
0xd1 -> IRQ 17)
Jun 1 16:32:45 localhost kernel: 00:00:1f[B] -> 2-17 -> IRQ 17
Jun 1 16:32:45 localhost kernel: Pin 2-16 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-17 already programmed
Jun 1 16:32:45 localhost kernel: IOAPIC[0]: Set PCI routing entry (2-21 ->
0xd9 -> IRQ 21)
Jun 1 16:32:45 localhost kernel: 00:02:09[A] -> 2-21 -> IRQ 21
Jun 1 16:32:45 localhost kernel: Pin 2-23 already programmed
Jun 1 16:32:45 localhost kernel: IOAPIC[0]: Set PCI routing entry (2-20 ->
0xe1 -> IRQ 20)
Jun 1 16:32:45 localhost kernel: 00:02:09[D] -> 2-20 -> IRQ 20
Jun 1 16:32:45 localhost kernel: Pin 2-23 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-20 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-21 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-23 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-20 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-21 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-20 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-21 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-23 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-21 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-23 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-20 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-18 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-19 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-16 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-17 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-20 already programmed
Jun 1 16:32:45 localhost kernel: Pin 2-23 already programmed
Jun 1 16:32:45 localhost kernel: PCI: Using ACPI for IRQ routing
Jun 1 16:32:45 localhost kernel: PCI: if you experience problems, try using
option 'pci=noacpi' or even 'acpi
=off'
Jun 1 16:32:45 localhost kernel: Linux NET4.0 for Linux 2.4
Jun 1 16:32:45 localhost kernel: Based upon Swansea University Computer
Society NET3.039
Jun 1 16:32:45 localhost kernel: Initializing RT netlink socket
Jun 1 16:32:45 localhost kernel: Starting kswapd
Jun 1 16:32:45 localhost kernel: devfs: v1.12c (20020818) Richard Gooch
(rgooch@atnf.csiro.au)
Jun 1 16:32:45 localhost kernel: devfs: boot_options: 0x1
Jun 1 16:32:45 localhost kernel: ACPI: Power Button (FF) [PWRF]
Jun 1 16:32:45 localhost kernel: ACPI: Processor [CPU0] (supports C1)
Jun 1 16:32:45 localhost kernel: ACPI: Processor [CPU1] (supports C1)
Con
next prev parent reply other threads:[~2003-06-03 1:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 21:01 ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1) Grover, Andrew
2003-06-03 0:12 ` Con Kolivas
2003-06-03 2:01 ` Con Kolivas [this message]
2003-06-03 4:03 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2003-05-31 11:53 Linux 2.4.21rc6-ac1 Alan Cox
2003-05-31 20:50 ` Andreas Haumer
2003-06-01 7:23 ` ACPI interrupt storm (was Re: Linux 2.4.21rc6-ac1) Paul P Komkoff Jr
2003-06-01 7:31 ` Con Kolivas
2003-06-01 7:23 ` Zwane Mwaikambo
2003-06-03 13:00 ` Con Kolivas
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=200306031201.09642.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=andrew.grover@intel.com \
--cc=i@stingr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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.