PCI Bus Error Slot 0, Bus 0, Device 0, Function 0

[Adam Hunter]

Hi We have a DL360 G5 Proliant server frequently reporting this error in IML logs and causing the server to reboot/hang displaying a blue screen with "Hardware Malfunction" no mention of what the problem actually is.

We have had the system board replaced and the processors and all firmware and BIOS is fully up to data as are all drivers and support packs etc. 4 separate calls to HP and the issue is still not resolved. Beginning to lose the will to live to be honest. HP Support is terrible and useless.

Has anybody else had this problem and been able to resolve it?

Thanks

[Michael A. McKenney]

I would do a barebones install. Test with one CPU, 2 sticks of RAM, no controllers or adapters. See if it posts. You can boot smartstart CD/DVD and run a diagnostics.

[Suman_1978]

Hi,

The Slot 0, device 0, function 0 refers to the P400i/E200i controller installed in the server.

Thanks

[Adam Hunter]

Does this mean there is a fault with the controller itself or a failing hard drive. We have ran offline diagnostics and no problems are shown but then it's an intermittent fault that pops up in the IML logs and causes a server hang so I wouldn't expect it to find anything.

Is the controller part of the system board or is a separate component that can be replaced?

Thanks

[Michael A. McKenney]

If the onboard controller fails, you need to replace the server board again.

A few weeks ago, I upgraded to firmware 9.2. Took out the server board and two HBAs. In 5 days, HP replaced the server board 3x and HBAs 4x. They brought out flaky or dead hardware. If its still acting up, replace it again.

[Suman_1978]

HP ProLiant DL360 Generation 5 Server Maintenance and Service Guide
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00710376/c00710376.pdf
Refer to Page#45

Search for the card and remove/reseat or swap with another similar card if you have and test.

[Adam Hunter]

I'm tearing my hair out HP keep coming up with new issues relating to PCI bus error's but they are forgetting that the issue we are getting is pci bus error slot 0, bus 0, device 0 and function 0 not any other device or slot. They think its the memory now. I have run memory tests and offline diagnostics and the memory is A1.

They are shying away from replacing the system board again because it has been done once but all replacement components are refurbs are they not? so replacing it once doesnt always mean the replacement is good.

[CW_777]

I've been struggling with the exact same issue. Just replaced the PCIe/PCI-X riser about an hour ago, but had another ASR reboot following the 'PCI Bus Error (Slot 0, Bus 0, Device 0, Function 0) message.

I've got two Adaptec 39320A-R boards in the PCI-X slots, attached to Plasmon optical libraries.

Everything was working fine up until 3/17, which is when the first PCI error occurred.

[CW_777]

More info-

In Insight Diagnostics, here's the definition of the device at Slot 0, Bus 0, Device 0, Function 0:

PCI Device PCI standard host CPU bridge
Windows Device ID PCI\VEN_8086&DEV_25D8&SUBSYS_00000000&REV_B1\3&61AAA01&0&00
Bus 0
Device 0
Function 0
Slot Number 0
Class Code 06
Sub-Class Code 00
Revision ID B1h
Vendor Name (Standard system devices)
Vendor ID 8086
Device ID 25D8
Sub Vendor ID Not applicable
Subsystem ID Not applicable

[Michael A. McKenney]

I would remove all adapters and run diagnostics on the server. If clean for 24 hours. Install one adapter and retest. I would remove any non-HP adapter and replace it with the HP equivalent. It could be as simple as a BIOS conflict with the Adaptec board.

[PZel]

There were some issue's with the PCI-X riser board in the DL360G5. The one that has no problems -according to HP- has SPN 436912-001.
Is that the same you're using ??

[PatrickBurwell]

We have ~500 ProLiant xw2x220c Blade Workstations and we see these errors on some of them. Our System ROM is V04  11/02/2008.

[juanrm2112]

We had this issue happening in most of our Proliant Blades, and it ended up being the Smart Array firmware version which had some issues.

Here are the few things that most of the blades that have failed had in common:

Server:

HP ProLiant BL460c G6 (Blades)

Array:

Smart Array P410i

Firmware Version:

Anything lower than 5.06

OS:

SLES 11 SP1

...so far there have been no more crashes with the upgrade to 5.06.

[Spectroscopy]

This is a NMI case which has the following agenda to be followed through such as Datasheet inspection of Intel Chipset register ++ PIC SIG configuration mapping with Uncorrectable error mask and error severity which will take time to deduce

 Need to analysze AHS log . If AHS gives the following defination under Decode NMI then By looking at the file and the NMI Dump it has the following error : flow_control_protocol_error_mask , Also the error status register bit 15:1 if high that denotes the error status to be true and not pseudo. Find the screenshot attached.

On Reg 154h there is error code of 0006203 which gives us the trace for error severity. This takes us to the next level of troubleshooting which will point towards the Uncerrsrv from INtell datasheet register which will give the unplanned down for more info contact me