| 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
| ||
|
Date: Mon, 13 Apr 2009 15:13:05 -0700 (PDT) From: "Yan Seiner" <yan@...ner.com> To: linux-kernel@...r.kernel.org Subject: mcp55 forcedeth woes I have a few Asus M2N-SLI deluxe mobos. These mobos have the MCP55 chipset and two 1gb ethernet ports. Occasionally, and for no reason that I can figure out, these ports will die. There are various ways to try and fix these; they seem to be about 50% effective, and approach something akin to voodoo. Based on this discussion here: http://patchwork.kernel.org/patch/16212/ I've gotten the ability to turn the ports on and off somewhat. For port 0, ethtool -s eth0 autoneg off speed 10 duplex full turns on the link, and gets me half-duplex, 10mb/sec. Not much, granted. ethtool -s eth0 autoneg off speed 100 duplex full causes the link to go up and down on about a 2 second cycle. ethtool -s eth0 autoneg on causes the link to drop. For port 1, the behavior is similar, except that I can get a stable 100 mbit connection. So the problem is in the autoneg code. It's a driver issue as this is reported widely to work under windows of various flavors. I'm running 2.6.29.1; I'm ok with patching and building kernels, but I'm not a kernel hacker. What, if anything, can I provide and do to fix this? -- Yan Seiner, PE Support my bid for the 4J School Board http://www.seiner.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists