and it would die randomly, then I discovered it was mostly happening during compilation (heavy use of memory, disk ?) - compiling fltk-1.3.0 (cheers hamei - I've been secretly compiling dillo) is by far the easiest way to crash the machine.
Code: Select all
BRIDGE ERR_STATUS 0x4000000
ALERT: PCI BRIDGE ERROR: int_status is 0x4000000 for /hw/node/xtalk/15/pci
Dumping relevant BRIDGE registers for each bit set...
26: Incoming response xtalk command word error bit set or invalid sideband
Bridge Response Buf Error Addr Reg: 0x800007b8a7400
dev-num 0 buff-num 8 addr 0x7b8a7400
PANIC: PCI Bridge Error interrupt killed the system
) - and I tested that XBOW with FOUR Motherboards in various configurations.
I've tested this XBOW with FOUR different motherboards with the same results - all would die with the same error.
The same FOUR MB's do not crash in a fully working chassis with the same XBOW version.
I suspected it might have been related to PCI cage I got, or RAM, or even suspected SCSI controller - but 4 MB's (each had own ram) kind of disprove MB's fault...
Technically it's weird the machine would be "partially" broken - but who knows what other functions XBOW has besides switching XIO...
I don't think there's much I can do anymore nor do I have time to play with it.
It's free if anybody wants it for surgery/experiments/whatever (appropriate post is under hw for sale/trade with more details on pickup/shipping etc)...