msk0 interface stops working when downloading
pyunyh at gmail.com
Wed Nov 24 20:36:16 UTC 2010
On Tue, Nov 23, 2010 at 04:10:03PM -0800, Garrett Cooper wrote:
> On Tue, Nov 23, 2010 at 3:25 PM, Andrew Moran <amoran at forsythia.net> wrote:
> > Hey guys,
> > After banging my head against this for a few hours, I've decided to ask for help. ? ? ?I installed FreeBSD 8.1 amd64 on a Shuttle J1 4100 system (tech specs here http://us.shuttle.com/J1_4100.aspx). ? I installed from DVD and the install went fine.
> > I notice when I pkg_add -r anything, ?the network stops responding.
> > Some details:
> > 1) I can reproduce it 100% by downloading a large file. ? ? low traffic like the SSH connection does not trigger it. ? I think it's being triggered by traffic above a certain rate.
> > 2) I can recover by restarting the network interfaces (/etc/rc.d/netif stop; ?/etc/rc.d/netif start)
> > 3) I see no errors in dmesg or /var/log/messages. ?Nothing at all.
> > 4) I've tried the following in /etc/sysctl.conf:
> > net.inet.tcp.tso=0
> > net.inet.tcp.inflight.enable=0
> > and in /boot/loader.conf:
> > hw.pci.enable_msix="0"
> > hw.pci.enable_msi="0"
> > hw.bce.tso_enable="0"
> > But the problem persists.
> > The interface is identified as:
> > mskc0: <Marvell Yukon 88E8057 Gigabit Ethernet> port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 17 at device 0.0 on pci2
> > msk0: <Marvell Technology Group Ltd. Yukon Ultra 2 Id 0xba Rev 0x00> on mskc0
> > msk0: Ethernet address: 80:ee:73:01:60:7d
> > miibus0: <MII bus> on msk0
> > e1000phy0: <Marvell 88E1149 Gigabit PHY> PHY 0 on miibus0
> > e1000phy0: ?10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> > mskc0: [ITHREAD]
> > Does anyone know what could be causing this or how I can resolve it? ? Any help is appreciated, thanks.
> 1. freebsd-stable is the proper list, not freebsd-current.
> 2. I have a similar chipset (not the same though) that hasn't had
> any issues for a while:
> $ pciconf -lv | grep -A 3 msk
> mskc0 at pci0:2:0:0: class=0x020000 card=0x81f81043 chip=0x436411ab
> rev=0x12 hdr=0x00
> vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
> device = 'Yukon PCI-E Gigabit Ethernet Controller (88E8056)'
> class = network
> $ devinfo -v | grep -A 3 mskc0
> mskc0 pnpinfo vendor=0x11ab device=0x4364 subvendor=0x1043
> subdevice=0x81f8 class=0x020000 at slot=0 function=0
> e1000phy0 pnpinfo oui=0x5043 model=0xb rev=0x1 at phyno=0
> $ uname -a
> FreeBSD orangebox.local 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r215607M:
> Sat Nov 20 21:22:34 UTC 2010
> gcooper at orangebox.local:/usr/obj/usr/src/sys/ORANGEBOX amd64
> Sorry for not grabbing the full dmesg output, but unfortunately I
> have BUS_DEBUG turned on for this test box, which blows out my syslog
> buffer at boot :).
> I've CCed yongari@ for comment.
It seems there are a couple of msk(4) issues on Yukon Ultra and
Ultra II controllers. Some revisions appear to work without
problems but others didn't work well. You may have noticed there
are a couple of msk(4) related PRs. Perhaps I have to sit down and
verify every register access patterns and check controller status.
For long time, one of the problem was lack of hardware access.
There is no standalone PCIe Yukon Ultra/Ultra II controllers in
market so it looks hard to get it in near future. :-(
More information about the freebsd-stable