Hi This is with the 20050630-2.6.13-rc1-sis190-test.patch driver
scp ... same as always dmesg gives "eth0: pad error. status = 012005eb" scp text [EMAIL PROTECTED]: [OK] scp [EMAIL PROTECTED]:text . [STALL] scp text blah@<otherhostoninternet> [OK] scp blah@<otherhostoninternet>:text . [OK] Hmm, this might help ping -s 1469 PING 192.168.1.1 (192.168.1.1) 1469(1497) bytes of data. 1477 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.88 ms 1477 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.740 ms 1477 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.731 ms 1477 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.734 ms 1477 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.799 ms ping -c 5 -s 1470 192.168.1.1 5 packets transmitted transmitted, 0 received, 100% packet loss dmesg gives "eth0: pad error. status = 012005eb" /Lars ---------------------------------------------------------------------- Ok. If you have not already tested 20050630-2.6.13-rc1-sis190-test.patch, can you give the attached patch a try ? It is the "official" 20050630-2.6.13-rc1-sis190-test.patch wherein I have commented out some noisy printks. If you test it, please triple check that you are using the right patch in the right tree as the results ought to give me a serious hint regarding the issue. You do not need to collect any log for this one. You can simply issue the usual ssh command. No need to hurry: I'm about to go to bed. -- Ueimor ---------------------------------------------------------------------- Hi I've collected some data for you to analyse, have fun... The scp or ssh session "stalls", but I can make new connections and internet access is working. I'm using the 20050704-2.6.13-rc1 driver http://lingonpaj.com/~erior/sis190/sis190_hang.tar.gz /Lars -------------------------------------------------------------------------------- Från: Francois Romieu [mailto:[EMAIL PROTECTED] Skickat: ti 2005-07-05 09:11 Till: Lars Vahlenberg Ämne: Re: SV: SiS190 driver 20050701-2.6.13-rc1-sis190-test.patch Lars Vahlenberg <[EMAIL PROTECTED]> : [...] > I tried with you new driver, I have the same issue but now I don't get > anything to the log... Ok. When the ssh is stalled, can you proceed normally with new ssh connections or is the whole networking dead ? > I have a full 100FD network, and I copy files with scp, > if I try to copy from the SiS190 computer it works, > if I try to copy to the SiS190 computer it "stalles" > > The driver before gave me > > Rx status = c0000000 > > status = 00000040 > > Rx status = 76042110 > > Rx PSize = 012005eb > > pad error. status = 012005eb > > The sis190-000.patch doesn't say anything to the log but stalles all the same, > my computer is still workable it doesn't hang, but the scp doesn't recover > or continues. Ok. Can you send: - the .config for your kernel - ifconfig, lsmod, cat /proc/interrupts after the driver has stalled - lspci -vx - a full dmesg (from boot, parts may be stored under /var/log if 'dmesg' does not include the very first lines ). A tcpdump -x taken at the remote computer which initiates the scp could help too. It may help if you could trigger the issue with simple icmp ping packets (of various sizes, with/without preload/flood) but there is no emergency. I'll look at the issue after the day work. > I can do a "ssh " to the remote machine and it works mostly, I can "trigger" > the "stall" there also. ( but not so often ) > > ethtool -v -v doesn't regognize "-v" on my computer so I did a ethtool eth0, > it's the info.txt -v -v eth0 should be used with mii-tool (if your system includes this utility of course). -- Ueimor - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
