recap since this is an old thread: an amd x86_64 motherboard manufactured by MSI has two on-board tg3's, which are attached at 100mhz/64-bit. if you boot with i386 kernel, it will work fine, keep your configs and reboot the system on an x86_64 kernel, and you will fail to get link. the dumb problem, which i have been staring at without even considering, is that the on-board tigons are detected in reverse order when on an x86_64 kernel. eth0 is really eth1. why? i dunno, it's probably some world domination conspiracy. i only finally noticed this when i upped eth1 in order to get some baseline values i could compare with my debugs from eth0...to see what values were different, and hope to get an idea of where to look from there. imagine my frustration when eth1 got link. imagine the bloodcurdling scream i let out when i was able to ping out across it. anyway, i know at least one other person has stumbled across this. hope it turns out to be the same dumb thing. and thanks for giving me a kick in the butt to look at this again. i dunno if this is a bug or intentional x86_64 weirdness, but it *is* sounding like not-a-linux-net-problem. and thanks to davem for tolerating me. -- David W. Hankins "If you don't do it right the first time, Network Engineer you'll just have to do it again." -- Jack T. Hankins
Attachment:
pgp00127.pgp
Description: PGP signature
