On 2007/11/29 22:23, NetOne - Doichin Dokov wrote: > Two weeks ago i bought an Intel Pro/1000MT dual Gbit NIC because i was gonna > soon be in need for more ports in one of our 1U systems,
Change the PCI jumper, which is currently probably on auto, to 64 bit 66MHz. You probably need to remove the PCIX card to reach it (unless they changed much of the design between the H8SSL and -I2, which I doubt). > which has 2 onboard bge(4)s which are working quite nice. the 5704C bge(4) on my H8SSL are all disabled because of Ierrs in netstat -ni, maybe you are luckier :-) > everything from it quite nice, fetch remote sites, etc. Suddenly the SSH > connection was dropped with a message I've never seen before - Corrupted MAC > header. Been there, done that. If you use plaintext protocols (ftp or so) over the interface, you'll see random corruption visible in the data (e.g. directory listings). At 133MHz there's some corruption between motherboard and card. Disappears at 66MHz. Normally this would be masked by TCP checksums (you'd get packet loss, but it would mostly be corrected rather than pass corrupt packets up the stack), but the em(4) does offload TCP checksum processing to the card, so the checksum no longer covers the transfer over the PCI bus, hence the wierd protocol errors. > dmesg errors during the problems with em(4)s devices: > ======================================= > em1: watchdog timeout -- resetting > em1: watchdog timeout -- resetting > pckbcintr: no dev for slot 1 > pckbcintr: no dev for slot 1 > > dmesg bge(4) timeouts which happen from time to time: > ===================================== > bge0: watchdog timeout -- resetting > bge1: watchdog timeout -- resetting mickey posted some diffs on tech@ relating to watchdog problems with bge and em, they might be worth a look.
