Date: Wed, 07 Nov 2007 14:28:00 +0200 From: Oleg Lomaka <oleg.lomaka@gmail.com> To: pyunyh@gmail.com Cc: Oleg Lomaka <oleg.lomaka@gmail.com>, freebsd-stable@freebsd.org Subject: Re: any hope for nfe/msk? Message-ID: <4731AF50.5040403@gmail.com> In-Reply-To: <20071101090811.GE47075@cdnetworks.co.kr> References: <471F52DC.4080305@gmail.com> <20071025020637.GA16092@cdnetworks.co.kr> <47203EC3.4010203@gmail.com> <20071025083032.GE16092@cdnetworks.co.kr> <20071027030921.GC25452@cdnetworks.co.kr> <4726EE79.6050401@lomaka.org.ua> <20071030085831.GG38663@cdnetworks.co.kr> <47273920.8090003@gmail.com> <20071031033638.GC42371@cdnetworks.co.kr> <47299584.8080701@gmail.com> <20071101090811.GE47075@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Pyun YongHyeon wrote: > On Thu, Nov 01, 2007 at 10:59:48AM +0200, Oleg Lomaka wrote: > > Hello, > > > > Pyun YongHyeon wrote: > > >On Tue, Oct 30, 2007 at 04:01:04PM +0200, Oleg Lomaka wrote: > > > > > >[...] > > > > > > > I had RxFIFO overrun again :( > > > > from dmest: > > > > msk0: Rx FIFO overrun! > > > > > >[...] > > > > > >Please try attached patch again. Sorry for the trouble. > > >After applying the patch show me verbosed dmesg output related with > > >msk(4)/PHY driver. > > > > > >Thanks for testing. > > > > > pcib1: <MPTable PCI-PCI bridge> irq 16 at device 28.0 on pci0 > > pcib1: domain 0 > > pcib1: secondary bus 2 > > pcib1: subordinate bus 2 > > pcib1: I/O decode 0x2000-0x2fff > > pcib1: memory decode 0xd0100000-0xd01fffff > > pcib1: no prefetched decode > > pci2: <PCI bus> on pcib1 > > pci2: domain=0, physical bus=2 > > found-> vendor=0x11ab, dev=0x4352, revid=0x14 > > domain=0, bus=2, slot=0, func=0 > > class=02-00-00, hdrtype=0x00, mfdev=0 > > cmdreg=0x0007, statreg=0x4010, cachelnsz=16 (dwords) > > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > > intpin=a, irq=11 > > powerspec 2 supports D0 D1 D2 D3 current D0 > > MSI supports 2 messages, 64 bit > > map[10]: type Memory, range 64, base 0xd0100000, size 14, enabled > > pcib1: requested memory range 0xd0100000-0xd0103fff: good > > map[18]: type I/O Port, range 32, base 0x2000, size 8, enabled > > pcib1: requested I/O range 0x2000-0x20ff: in range > > pcib1: slot 0 INTA routed to irq 16 > > mskc0: <Marvell Yukon 88E8038 Gigabit Ethernet> port 0x2000-0x20ff mem > > 0xd0100000-0xd0103fff irq 16 at device 0.0 on pci2 > > mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0100000 > > mskc0: MSI count : 2 > > mskc0: RAM buffer size : 4KB > > mskc0: Port 0 : Rx Queue 2KB(0x00000000:0x000007ff) > > mskc0: Port 0 : Tx Queue 2KB(0x00000800:0x00000fff) > > msk0: <Marvell Technology Group Ltd. Yukon FE Id 0xb7 Rev 0x01> on mskc0 > > msk0: bpf attached > > msk0: Ethernet address: 00:1b:24:0e:bc:26 > > miibus0: <MII bus> on msk0 > > e1000phy0: <Marvell 88E3082 10/100 Fast Ethernet PHY> PHY 0 on miibus0 > > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49 > > mskc0: [MPSAFE] > > mskc0: [FILTER] > > > > So far all looks good to me. If you encounter watchdog timeouts > or Rx FIFO overruns let me know. > > Got it again: msk0: Rx FIFO overrun! I believe this is happening under heavy CPU usage. Now i have firefox compiling and watched pictures on remote windows box using rdesktop. And after few minutes got network freeze. But it looks i didn't get any packet lost :). Take a look at ping statistics... funny... tdevil% ping 10.1.1.254 PING 10.1.1.254 (10.1.1.254): 56 data bytes 64 bytes from 10.1.1.254: icmp_seq=0 ttl=64 time=35926.404 ms 64 bytes from 10.1.1.254: icmp_seq=1 ttl=64 time=34925.694 ms 64 bytes from 10.1.1.254: icmp_seq=2 ttl=64 time=33924.729 ms 64 bytes from 10.1.1.254: icmp_seq=3 ttl=64 time=32923.814 ms 64 bytes from 10.1.1.254: icmp_seq=4 ttl=64 time=31922.833 ms 64 bytes from 10.1.1.254: icmp_seq=5 ttl=64 time=30921.878 ms 64 bytes from 10.1.1.254: icmp_seq=6 ttl=64 time=29920.923 ms 64 bytes from 10.1.1.254: icmp_seq=7 ttl=64 time=28919.960 ms 64 bytes from 10.1.1.254: icmp_seq=8 ttl=64 time=27919.009 ms 64 bytes from 10.1.1.254: icmp_seq=9 ttl=64 time=26918.042 ms 64 bytes from 10.1.1.254: icmp_seq=10 ttl=64 time=25917.078 ms 64 bytes from 10.1.1.254: icmp_seq=11 ttl=64 time=24916.115 ms 64 bytes from 10.1.1.254: icmp_seq=12 ttl=64 time=23915.144 ms 64 bytes from 10.1.1.254: icmp_seq=13 ttl=64 time=22914.192 ms 64 bytes from 10.1.1.254: icmp_seq=14 ttl=64 time=21913.214 ms 64 bytes from 10.1.1.254: icmp_seq=15 ttl=64 time=20912.278 ms 64 bytes from 10.1.1.254: icmp_seq=16 ttl=64 time=19911.330 ms 64 bytes from 10.1.1.254: icmp_seq=17 ttl=64 time=18910.375 ms 64 bytes from 10.1.1.254: icmp_seq=18 ttl=64 time=17909.419 ms 64 bytes from 10.1.1.254: icmp_seq=19 ttl=64 time=16853.821 ms 64 bytes from 10.1.1.254: icmp_seq=20 ttl=64 time=15854.710 ms 64 bytes from 10.1.1.254: icmp_seq=21 ttl=64 time=14701.312 ms 64 bytes from 10.1.1.254: icmp_seq=22 ttl=64 time=13701.003 ms 64 bytes from 10.1.1.254: icmp_seq=23 ttl=64 time=12700.052 ms 64 bytes from 10.1.1.254: icmp_seq=24 ttl=64 time=11699.098 ms 64 bytes from 10.1.1.254: icmp_seq=25 ttl=64 time=10698.148 ms 64 bytes from 10.1.1.254: icmp_seq=36 ttl=64 time=0.463 ms 64 bytes from 10.1.1.254: icmp_seq=37 ttl=64 time=0.379 ms
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4731AF50.5040403>