| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1184866465.10854.45.camel@dell> Date: Thu, 19 Jul 2007 10:34:25 -0700 From: "Michael Chan" <mchan@...adcom.com> To: "patric" <pakar@...erialnet.org> cc: "Neil Horman" <nhorman@...driver.com>, "netdev" <netdev@...r.kernel.org> Subject: Re: tg3 issues On Thu, 2007-07-19 at 15:24 +0200, patric wrote: > > Just a hypothetical question. If the 2 network cards starts the > autonegotiation would it be possible that they get into a loop where > they are chasing each others state? Maybe a fix could be to add a sleep > of a random length that would enable them to catch up? Maybe you know if > any of the fiber-cards so support running without flowcontrol too since > the cards don't seem to be able to get a link with flowcontrol turned > off at least in this setup. > > The old 5701 fiber NICs do not support autonegotiation in hardware so it is done "by hand" in the driver. It is not the most robust way of doing autoneg and what you described is totally possible. You might want to try disabling autoneg to see if it works any better. There is only one possible speed in fiber and autoneg is really only used to negotiate flow control. Some switch ports will not link up if the link partner does not do autoneg though. You have to use ethtool in initrd to turn off autoneg or just modify the driver to disable autoneg. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists