netdev - forcedeth kernel panic with nForce 630a on 100Mbps FD network

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <97246d0e0802281239t43d9167dwe2740ed11d1300e0@mail.gmail.com>
Date:	Thu, 28 Feb 2008 15:39:58 -0500
From:	"m. allan noah" <kitno455@...il.com>
To:	netdev@...r.kernel.org
Subject: forcedeth kernel panic with nForce 630a on 100Mbps FD network

Have two Asus M2N-VN DVI motherboards, Athlon 64 X2 5000+, 8 gigs of
ram, both running Fedora 8. with updated distro kernel
(2.6.23.15-137).

When RXing large amounts of data on a 100Meg network, i start seeing
RX errors almost immediately, seemingly always equal numbers of
rx_frame_error and rx_frame_align_error (according to ethtool -S).

Soon afterwards, the network speed drops pretty drastically, and then
stops altogether. no ping, etc. rmmod and insmod forcedeth seems to
fix things again, but if i let the scp continue against the dead card,
it will eventually kernel panic.

there is nothing unusual in syslog, and none of this happens if i
connect the two machines directly with crossover cable at 1000Meg

I have just upgraded one of the machines to vanilla 2.6.24, and i
still see the ethtool errors, and eventually the slow downs, but no
network freeze or kernel panic yet, so it looks a little better?

The machines are not going into production for a few weeks, so i
wondered if there was any use in getting you guys some debugging info,
or any hope of an updated driver to try?

allan
-- 
"The truth is an offense, but not a sin"
--
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