From: Roland Dreier <rdreier@cisco.com>
To: linux-kernel@vger.kernel.org
Cc: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>,
Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: The change "PCI: assign ioapic resource at hotplug" breaks my system
Date: Mon, 02 Oct 2006 10:28:34 -0700 [thread overview]
Message-ID: <adafye6wrst.fsf@cisco.com> (raw)
In-Reply-To: <adar6xqwsuw.fsf@cisco.com> (Roland Dreier's message of "Mon, 02 Oct 2006 10:05:43 -0700")
One piece of information that might be useful is that lspci shows a
difference in the configuration of the PCI bridge IOAPIC. In the good
(working) case, the IOAPIC memory region 0 is disabled, while in the
bad case it is enabled.
Here are full details: first, the good/working case:
04:01.1 PIC: Advanced Micro Devices [AMD] AMD-8132 PCI-X IOAPIC (rev 12) (prog-if 10 [IO-APIC])
Subsystem: Advanced Micro Devices [AMD] AMD-8132 PCI-X IOAPIC
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at <ignored> (64-bit, non-prefetchable)
00: 22 10 59 74 06 00 00 02 12 10 00 08 00 00 00 00
10: 04 e0 af fe 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 59 74
30: 00 00 00 00 50 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 03 00 00 00 04 e0 af fe 00 00 00 00
Then the bad (non-working e1000) case:
04:01.1 PIC: Advanced Micro Devices [AMD] AMD-8132 PCI-X IOAPIC (rev 12) (prog-if 10 [IO-APIC])
Subsystem: Advanced Micro Devices [AMD] AMD-8132 PCI-X IOAPIC
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Region 0: Memory at e2100000 (64-bit, non-prefetchable) [size=4K]
00: 22 10 59 74 06 00 00 02 12 10 00 08 00 00 00 00
10: 04 00 10 e2 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 22 10 59 74
30: 00 00 00 00 50 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 03 00 00 00 04 00 10 e2 00 00 00 00
I have no idea whether there's any significance to this.
- R.
next prev parent reply other threads:[~2006-10-02 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 17:05 The change "PCI: assign ioapic resource at hotplug" breaks my system Roland Dreier
2006-10-02 17:28 ` Roland Dreier [this message]
2006-10-03 12:32 ` Kenji Kaneshige
2006-10-03 17:51 ` Roland Dreier
2006-10-03 18:02 ` Stephen Hemminger
2006-10-04 5:46 ` Kenji Kaneshige
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=adafye6wrst.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=gregkh@suse.de \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=muneda.takahiro@jp.fujitsu.com \
--cc=takeuchi_satoru@jp.fujitsu.com \
/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