Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Oct 2007 17:12:44 +0300
From:      Oleg Lomaka <oleg.lomaka@gmail.com>
To:        pyunyh@gmail.com
Cc:        freebsd-stable@freebsd.org
Subject:   Re: any hope for nfe/msk?
Message-ID:  <471F52DC.4080305@gmail.com>
In-Reply-To: <20071024084934.GF11234@cdnetworks.co.kr>
References:  <E1IkakO-0005BS-CZ@cs1.cs.huji.ac.il> <20071024084934.GF11234@cdnetworks.co.kr>

next in thread | previous in thread | raw e-mail | index | archive | help
Pyun YongHyeon wrote:
> On Wed, Oct 24, 2007 at 09:33:48AM +0200, Danny Braniss wrote:
>  > Hi,
>  > 	these drivers don't work under 7.0
>  > As soon as some mild preasure is applied, they start loosing interrupts, and
>  > in my case the hosts come to a total stand-still, since they are diskless
>  > and rely on the network.
>  > This happens at 1gb and at 100mg.
>  > 
>  > Maybe the problem is with the shared interrups?
>  > 	
>  > 	irq16: mskc0 uhci0               3308351         13
>  > or
>  > 	irq21: nfe0 ohci0                1584415         24
>  > 
>  > but I have no idea how to uncouple this
>  > 
>
> If you see watchdog timeout errors on your console, shared interrupt
> would be culprit.
> For msk(4) set hw.msk.legacy_intr="1" in loader.conf or use kenv(1)
> to set it before loading msk(4) kernel module.
> For nfe(4) you can switch to polling(4).
>
>   
I have some msk troubles too. On my laptop (acer travelmate 2483wxmi) 
under heavy cpu & network load msk periodically stops working for few 
minutes.
sysctl -a|grep msk
<118>msk0: no link ...
<118>DHCPREQUEST on msk0 to 255.255.255.255 port 67
<118>DHCPREQUEST on msk0 to 255.255.255.255 port 67
<118>DHCPDISCOVER on msk0 to 255.255.255.255 port 67 interval 3
<118>DHCPREQUEST on msk0 to 255.255.255.255 port 67
<118>msk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 
mtu 1500
msk0: watchdog timeout (missed Tx interrupts) -- recovering
msk0: watchdog timeout (missed Tx interrupts) -- recovering
msk0: Rx FIFO overrun!
msk0: watchdog timeout (missed Tx interrupts) -- recovering
msk0: watchdog timeout (missed Tx interrupts) -- recovering
msk0: watchdog timeout (missed Tx interrupts) -- recovering
dev.mskc.0.%desc: Marvell Yukon 88E8038 Gigabit Ethernet
dev.mskc.0.%driver: mskc
dev.mskc.0.%location: slot=0 function=0
dev.mskc.0.%pnpinfo: vendor=0x11ab device=0x4352 subvendor=0x1025 
subdevice=0x0110 class=0x020000
dev.mskc.0.%parent: pci2
dev.mskc.0.process_limit: 128
dev.msk.0.%desc: Marvell Technology Group Ltd. Yukon FE Id 0xb7 Rev 0x01
dev.msk.0.%driver: msk
dev.msk.0.%parent: mskc0
dev.miibus.0.%parent: msk0

Not sure if it is connected to previous issue.

 uname -a
FreeBSD tdevil.lomaka.org.ua 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Mon Oct 22 
18:32:01 EEST 2007     
root@tdevil.lomaka.org.ua:/usr/obj/usr/src/sys/TDEVIL-7.kernconf  i386




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?471F52DC.4080305>