On Thu, Mar 19, 2009 at 11:15:36AM -0700, Matt Carlson wrote:

quoted text
> > Would switching the uplink connection to eth1 (and not use eth0 in
> > Linux) give some more clue as well?
> Sure, let's try that.  Maybe this is the better way to go anyways.  I just
> learned that disabling iLo2 doesn't necessarily disable the management
> firmware on the network device.
> 
> For this to be a meaningful test though, we need to verify that the
> driver sign-on messages have a line that reads "ASF[0]" on eth1.  Can
> you confirm?

Yes:

[1186598.218205] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1]
WireSpeed[1] TSOcap[1]
[1186598.281314] eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0]
WireSpeed[1] TSOcap[1]

I'll keep the traffic on eth0 now until it breaks again, hopefully
spewing out more debugging info with your patch and then I'll switch to
eth1.

Bernhard
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html