2.4.0 bug in SHM an via-rhine or is it my fault?
Hi folks!
I searched the kernel archives for information on this at least half a yearback but I found only one article on the subject and that was never replied to:
I'm using a via-rhine chip (DFE-530TX) on a 10 Mbit network, I use 2.4.0 final, Athlon (classic) 1Gig, Abit-KA7 mobo (via KX133), Debian woody. whenever I try to get a file on my local network, meaning I get close to the 10Mbit barrier the network card hangs up. Traffic just stops. One ifdown/ifup and everything works fine again. (for about 10 seconds) this problem has persisted for some time now, I thought it would be fixed in the final, but, alas, it hasn't. It only happens during high traffic, too, at about 400k, no problem!
Something new that cropped up in prerelease:
My SHM stopped working!
everything was fine in test12, and after that all I got was "no space left on device".
Has anything changed that one should know about? I mounted shm like it's written in the help, and on a friends celeron SMP machine it works fine, I just don't know what I did wrong.
any ideas on any of the 2 problems?
TIA
Felix Maibaum
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 6 lines · Felix Maibaum
My SHM stopped working!
everything was fine in test12, and after that all I got was "no space left on device".
Has anything changed that one should know about? I mounted shm like it's written in the help, and on a friends celeron SMP machine it works fine, I just don't know what I did wrong.
You used a buggy version of powertweak which set kernel.shmall to 0 in /etc/sysctl.conf. Remove the offending line in /etc/sysctl.conf and either reboot the machine or "echo 2097152 > /proc/sys/kernel/shmall".
Ciao,
Nils
Signature · 9 lines
Nils Philippsen / Berliner Straße 39 / D-71229 Leonberg // +49.7152.209647 [email protected] / [email protected] / [email protected] The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offence. -- Edsger W. Dijkstra - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 1 line · Nils Philippsen
reboot the machine or "echo 2097152 >
/proc/sys/kernel/shmall".
now thats what I call a quick response, thanks, it did the trick.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · Felix Maibaum
I'm using a via-rhine chip (DFE-530TX) on a 10 Mbit network, I use 2.4.0 final, Athlon (classic) 1Gig, Abit-KA7 mobo (via KX133), Debian woody. whenever I try to get a file on my local network, meaning I get close to the 10Mbit barrier the network card hangs up. Traffic just stops. One ifdown/ifup and everything works fine again. (for about 10 seconds) this problem has persisted for some time now, I thought it would be fixed in the final, but, alas, it hasn't. It only happens during high traffic, too, at about 400k, no problem!
I just put a DFE-530TX in an AMD Duron/256MB system yesterday, which had been working fine with a DE-530 (de4x5.o) on a 10/100 MB switched network. I booted up the system with the new card, and noticed similar weirdness:
NFS from the client system (Duron - 2.4.0-ac4), hangs almost immediately when trying to contact a 2.2.18 NFS server. I get "nfs can't get task slot" errors, and "NFS server xxx.xxx.xxx.xxx not responding", especially after doing a "dd if=/dev/zero of=/home/user/nfstest bs=16k count=4096". After checking, the file /home/user/nfstest is 8192 bytes big. The client mount is a default NFS mount, with no rsize/wsize parameters.
I then replaced the DE-530 and tried the exact same scenario as above, and it works fine.
The other strangeness is that while the client complains about the NFS server having disappeared, I can ping it from the same client, transfer files using scp, and still get to the internet fine. So the card is still working, but never receives a response to any NFS traffic until a reboot. Other machines on the network can NFS mount from the server without problems as well.
Anyone have any ideas?
--
Adrian Chung
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines · Adrian Chung
NFS from the client system (Duron - 2.4.0-ac4), hangs almost immediately when trying to contact a 2.2.18 NFS server. I get "nfs can't get task slot" errors, and "NFS server xxx.xxx.xxx.xxx not responding", especially after doing a "dd if=/dev/zero of=/home/user/nfstest bs=16k count=4096". After checking, the file
/home/user/nfstestis 8192 bytes big. The client mount is a default NFS mount, with no rsize/wsize parameters.
I forced the module to load with options "full_duplex=1" and the card now seems to work fine. NFS transfers work perfectly at least.
--
Adrian Chung
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/