On Sat, 18 Aug 2007 06:59:08 -0700 (PDT) Kevin E <[EMAIL PROTECTED]> wrote:
> --- Willy Tarreau <[EMAIL PROTECTED]> wrote: > > > OK, in this trace, both controllers are on the same > > bus. The broken > > one has 'Capabilities: [100] Advanced Error > > Reporting' the other > > does not have, and the bridge to this bus has two > > more capabilities : > > 'Capabilities: [100] Virtual Channel' and > > 'Capabilities: [180] Unknown (5)'. > > > > I don't know whether it can jutify a different > > behaviour. Also, maybe this > > is caused by a minuscule difference in the BIOS > > setup ? > The working board has a different version of the Marvell chip: $ grep Marvell working-MB 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 14) $ grep Marvell broken-MB 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) Not sure if that completely explains the problem because the broken chip on my system is: 06:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 14) I don't know what the differences are between versions. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
