On Sun, Jan 08, 2006 at 01:58:24AM +0100, Francois Romieu wrote: > Marco Atzeri <[EMAIL PROTECTED]> : > [...] > > everything uploaded at > > > > http://www.geocities.com/marco_atzeri/sis190/ > uploaded again. The previous moved to subdirectory old_01
> > Can you add a '-x' to the main tethereal capture ? > If some data must not leak, you may want a filter like > tethereal -l -x 'arp or icmp and (host 192.168.1.2 or host 192.168.2.252)' > > Before the ftp, please issue: > for i in $(seq 1460 1478); do > ping -c 256 -qf -l 32 -s $i 192.168.1.252 > done done. But now the tethereal dump is very large 59 Mb, so it is bzipped and uuencoded to overcome the blocks of geocities. The ping sequence is from the ASUS 192.168.1.2 to the laptop 192.168.1.252, I tried also the reverse but due to a problem of ping under cygwin the log is too large > 1.5 GB; ping-cygwin sends more than 20000 packets per each sequences. All the other ping and the ftp are from the laptop In both the two directions I noted that from 1469 and over the loss is 100% > In the future, it could be useful to change: > CONFIG_DEBUG_KERNEL=y > # CONFIG_MAGIC_SYSRQ is not set > ^^^^^^^^^^^^^^^^^^ -> enable it > CONFIG_LOG_BUF_SHIFT=14 > ^^ -> low: dmesg gets truncated. > CONFIG_DETECT_SOFTLOCKUP=y > Both done. I increased to 17 > [...] > > I note now that eth1 shares the IRQ5 with other drivers while > > eth0 is alone > > > > 5: 392 XT-PIC ohci_hcd:usb2, ohci_hcd:usb4, ohci1394, eth1 > > 10: 21238 XT-PIC eth0 > > > > could be a reason for the hang ? > > None that I see but you can compile them out to see if it makes a difference. Tentative for the a next time > Is there any different reference for the motherboard ? I have not been able > to find any manual for the K8S-MV at Asus's site. Not that they miss a lot, > but... > The motherboard is used on a ASUS Vintage AE1 http://dlsvr02.asus.com/pub/ASUS/Barebone/Vintage-AE1/u2102_vintage-ae1_qsg.pdf I found a new effect after changing the PREEMPT to none, now when eth1 hangs also eth0 does the same. For few times is possible to recover the interfaces putting them down and then up; but after 3-4 tentatives every network interface hangs forever also 127.0.0.1, after that, a reboot is needed to recover the network. Regards Marco -- marco.atzeri at fastwebnet.it La prima delle Frequently Asked Questions: dove sono le FAQ ? it.faq - 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
