Frank Mori Hess wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have a server that uses the shpchp driver for its pci bridges, and it looks
to me like its high speed 133MHz/64 bit bridge is being bottlenecked behind a
root bridge that is only running at 33Mhz/32 bits. The relevant output from
lspci -vv which shows this is below. Does this have anything to do with
shpchp, or is it a motherboard bios problem, or am I just misunderstanding
the whole situation? This is the shpchp driver from Debian Lenny
(2.6.26-2-amd64 kernel).
Hi,
The shpchp driver (standard hot-plug controller driver) configures
the bus speed only when an adapter card is hot-plugged to the slot
on bridge's secondary bus. Therefore I don't think shpchp relate
to this.
Thanks,
Kenji Kaneshige
00:01.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (prog-if 00
[Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64
Bus: primary=00, secondary=01, subordinate=02, sec-latency=64
I/O behind bridge: 0000a000-0000cfff
Memory behind bridge: ff200000-ff3fffff
Prefetchable memory behind bridge: 00000000f2a00000-00000000f6afffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=slow >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [90] PCI-X bridge device
Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD-
Freq=133MHz
Status: Dev=00:01.0 64bit- 133MHz- SCD- USC- SCO- SRD-
Upstream: Capacity=0 CommitmentLimit=0
Downstream: Capacity=0 CommitmentLimit=0
Capabilities: [a0] HyperTransport: MSI Mapping Enable+ Fixed-
Mapping Address Base: 00000000fee00000
Capabilities: [b0] HyperTransport: Slave or Primary Interface
Command: BaseUnitID=1 UnitCnt=3 MastHost- DefDir-
Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO-
<CRCErr=0
Link Config 0: MLWI=8bit MLWO=8bit LWI=8bit LWO=8bit
Link Control 1: CFlE- CST- CFE- <LkFail- Init- EOC+ TXO+
<CRCErr=0
Link Config 1: MLWI=8bit MLWO=8bit LWI=N/C LWO=N/C
Revision ID: 0.00
Capabilities: [d8] Subsystem: Gammagraphx, Inc. Device 0000
Kernel modules: shpchp
01:0d.0 PCI bridge: Broadcom BCM5785 [HT1000] PCI/PCI-X Bridge (rev c0)
(prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 64 bytes
Bus: primary=01, secondary=02, subordinate=02, sec-latency=64
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: ff200000-ff2fffff
Prefetchable memory behind bridge: 00000000f2a00000-00000000f6afffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-
Capabilities: [90] PCI-X bridge device
Secondary Status: 64bit+ 133MHz+ SCD- USC- SCO- SRD- Freq=conv
Status: Dev=01:0d.0 64bit+ 133MHz+ SCD- USC- SCO- SRD-
Upstream: Capacity=8 CommitmentLimit=8
Downstream: Capacity=8 CommitmentLimit=8
Capabilities: [88] Subsystem: Device ef00:9000
Kernel modules: shpchp
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqvudkACgkQ5vihyNWuA4UAMQCdE6tpyiNtPoKl/Yg8EPxO4qJz
jtEAoOoqUvSqJ4/y+hdccLAuuB7+I6Hg
=0nKM
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqv1MsACgkQ5vihyNWuA4XtHACfadj1jcCPEPAwcO0vivXdHvNm
Jg0AoOrMx6eenS6w6UYEtGIXt3d8I/Rd
=uY1x
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
