Glitch in SLES8 United Linux SP3
(OK, I'm all bug reports. Hate me yet?-) I installed UnitedLinux SP3, and found one little bit of a glitch. An NFS client (a RedHat 7.3 pentium) had trouble talking to the updated SLES8 Opteron system. The network chip (in an HDAMB system) is a: 02:06.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702 Gigabit Ethernet (rev 02) Writes by the i386 system to an NFS directory on the SLES8 system tended to get stuck, with the i386 system apparently sending tons of fragments that the SLES8 system was rejecting. (Unfortunately, I didn't save a tcpdump log.) Revering to k_smp-2.4.19-256 fixed the problem and that is where I set now. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
Writes by the i386 system to an NFS directory on the SLES8 system tended to get stuck, with the i386 system apparently sending tons of fragments that the SLES8 system was rejecting. (Unfortunately, I didn't save a tcpdump log.) Revering to k_smp-2.4.19-256 fixed the problem and that is where I set now.
The report is not too useful. What would have been useful would have been tcpdump logs and netstat -s output (checking which error counters increase). Also you could try it with the tg3 driver instead of bcm5700 which you likely used. -Andi
Andi Kleen ak-at-suse.de |suse-amd64| wrote:
Writes by the i386 system to an NFS directory on the SLES8 system tended to get stuck, with the i386 system apparently sending tons of fragments that the SLES8 system was rejecting. (Unfortunately, I didn't save a tcpdump log.) Revering to k_smp-2.4.19-256 fixed the problem and that is where I set now.
The report is not too useful. What would have been useful would have been tcpdump logs and netstat -s output (checking which error counters increase). Also you could try it with the tg3 driver instead of bcm5700 which you likely used.
I know it wasn't too useful. I can kick myself for having not saved tcpdup logs of the failure. I only have sporadic instances of time where I can run tests like this, so my reports of this sort come in sporadically and it takes a while for the next instance of time to come around where I can act on these suggestions. Especially since this is not preventing me working. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep."
participants (2)
-
Andi Kleen -
Stephen Williams