Date: Tue, 23 Nov 2010 16:10:03 -0800 From: Garrett Cooper <gcooper@FreeBSD.org> To: Andrew Moran <amoran@forsythia.net> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, freebsd-questions@freebsd.org, Pyun YongHyeon <yongari@freebsd.org> Subject: Re: msk0 interface stops working when downloading Message-ID: <AANLkTimi3zDyQJwKqRaQ9toxvoy4h1Xz-ua0QpJNJzUH@mail.gmail.com> In-Reply-To: <7EA93980-478A-418A-8FB1-3249097A7011@forsythia.net> References: <7EA93980-478A-418A-8FB1-3249097A7011@forsythia.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 23, 2010 at 3:25 PM, Andrew Moran <amoran@forsythia.net> wrote: > > Hey guys, > > After banging my head against this for a few hours, I've decided to ask f= or help. =A0 =A0 =A0I installed FreeBSD 8.1 amd64 on a Shuttle J1 4100 syst= em (tech specs here http://us.shuttle.com/J1_4100.aspx). =A0 I installed fr= om DVD and the install went fine. > > I notice when I pkg_add -r anything, =A0the network stops responding. > > Some details: > > 1) I can reproduce it 100% by downloading a large file. =A0 =A0 low traff= ic like the SSH connection does not trigger it. =A0 I think it's being trig= gered by traffic above a certain rate. > 2) I can recover by restarting the network interfaces (/etc/rc.d/netif st= op; =A0/etc/rc.d/netif start) > 3) I see no errors in dmesg or /var/log/messages. =A0Nothing at all. > 4) I've tried the following in /etc/sysctl.conf: > net.inet.tcp.tso=3D0 > net.inet.tcp.inflight.enable=3D0 > > and in /boot/loader.conf: > hw.pci.enable_msix=3D"0" > hw.pci.enable_msi=3D"0" > hw.bce.tso_enable=3D"0" > > But the problem persists. > > The interface is identified as: > > mskc0: <Marvell Yukon 88E8057 Gigabit Ethernet> port 0xe800-0xe8ff mem 0x= febfc000-0xfebfffff irq 17 at device 0.0 on pci2 > msk0: <Marvell Technology Group Ltd. Yukon Ultra 2 Id 0xba Rev 0x00> on m= skc0 > msk0: Ethernet address: 80:ee:73:01:60:7d > miibus0: <MII bus> on msk0 > e1000phy0: <Marvell 88E1149 Gigabit PHY> PHY 0 on miibus0 > e1000phy0: =A010baseT, 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? =A0 = 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@pci0:2:0:0: class=3D0x020000 card=3D0x81f81043 chip=3D0x436411ab rev=3D0x12 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device =3D 'Yukon PCI-E Gigabit Ethernet Controller (88E8056)' class =3D network $ devinfo -v | grep -A 3 mskc0 mskc0 pnpinfo vendor=3D0x11ab device=3D0x4364 subvendor=3D0x104= 3 subdevice=3D0x81f8 class=3D0x020000 at slot=3D0 function=3D0 msk0 miibus0 e1000phy0 pnpinfo oui=3D0x5043 model=3D0xb rev=3D0x1 at p= hyno=3D0 $ uname -a FreeBSD orangebox.local 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r215607M: Sat Nov 20 21:22:34 UTC 2010 gcooper@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. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimi3zDyQJwKqRaQ9toxvoy4h1Xz-ua0QpJNJzUH>