Date: Mon, 7 Dec 2009 10:56:06 -0800 From: Pyun YongHyeon <pyunyh@gmail.com> To: Chris Cowart <ccowart@timesinks.net> Cc: freebsd-net@freebsd.org Subject: Re: msk link problems on 8.0 Message-ID: <20091207185606.GD1366@michelle.cdnetworks.com> In-Reply-To: <20091207021746.GA86085@marvin.timesinks.net> References: <20091207021746.GA86085@marvin.timesinks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 06, 2009 at 06:17:46PM -0800, Chris Cowart wrote:
> Hello,
>
> I recently upgraded my home router box to 8.0. Since doing so, I've had
> some problems with the msk driver.
>
> On startup, I'm experiencing the behavior that seems to be documented in
> kern/139093. Specifically, during network initialization, rc displays
> the message that it's "Waiting 30s for the default route interface". If
> I physically flap the link at this point, the system continues booting
> (when missed, the rest of the system doesn't do so well starting up, but
> I can flap the link at any future point to get it working).
>
> Before and after flapping the link, ifconfig reports the same thing:
>
> | % ifconfig msk0
> | msk0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 2290
> | options=118<VLAN_MTU,VLAN_HWTAGGING,TSO4>
> | ether 00:16:cb:ae:5b:1f
> | inet6 fe80::216:cbff:feae:5b1f%gige0 prefixlen 64 scopeid 0x1
> | media: Ethernet autoselect (1000baseT <full-duplex,flag0,flag1>)
> | status: active
>
> This interface is configured as a trunk for several VLANs.
>
> | % dmesg | grep msk
> | mskc0: <Marvell Yukon 88E8053 Gigabit Ethernet> port 0x1000-0x10ff mem
> | 0x50200000-0x50203fff irq 16 at device 0.0 on pci1
> | msk0: <Marvell Technology Group Ltd. Yukon EC Id 0xb6 Rev 0x02> on mskc0
> | msk0: Ethernet address: 00:16:cb:ae:5b:1f
> | miibus0: <MII bus> on msk0
> | mskc0: [FILTER]
> | % dmesg | grep e1000
> | e1000phy0: <Marvell 88E1111 Gigabit PHY> PHY 0 on miibus0
> | e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
>
> | % pciconf -lv
> | mskc0@pci0:1:0:0: class=0x020000 card=0x532111ab chip=0x436211ab rev=0x22 hdr=0x00
> | vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
> | device = 'Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller (88E8053)'
> | class = network
> | subclass = ethernet
>
> | % uname -a
> | FreeBSD gw.ccowart.com 8.0-RELEASE-p1 FreeBSD 8.0-RELEASE-p1 #0: Sun
> | Dec 6 14:43:41 PST 2009 root@gw.ccowart.com:/usr/obj/usr/src/sys/ROUTER
> | amd64
>
> I have the following in my /boot/loader.conf as a workaround that I
> believe dates back to 7.0:
>
> | hw.msk.msi_disable="1"
>
> I also have "-txcsum" in the interface configuration to address an
> earlier bug (both of these may have been resolved at this point; I just
> haven't been daring enough to test it).
>
> Having read the PR, I copied sys/dev/{msk,e1000} from HEAD into the
I think the PR has nothing to do with this issue.
> 8.0-p1 source tree and installed the resulting kernel. The behavior did
> not change. If anyone has any alternative patching I could do, either
> against 8.0 or HEAD for these drivers, I'd be more than willing to try
> them out.
>
There was a similar report on missing link state change and I think
I committed fix. Are you sure you used latest if_msk.c(r199413) in
HEAD? See if you have the following patch.
http://svn.freebsd.org/viewvc/base/head/sys/dev/msk/if_msk.c?r1=199012&r2=199413&view=patch
> On a related note, last night, when the system did boot, I would also
> run into a problem where the following message would be logged: "msk0:
> Rx FIFO overrun!". Once logged, the NIC seemed to be completely wedged
At least this indicates you didn't use latest msk(4) in HEAD
because the message was removed there.
> and unusable. Doing ifconfig down/up did not help things. At the time, I
> hadn't discovered the physical down/up workaround, so I can't speak to
> whether that would have helped (and this error condition hasn't
> recurred (knock on wood)). I don't know if the issues are related or
I think it would be different issue, let's fix link state issue
first.
> separate, but if you have any ideas, I'd like to be prepared if it comes
> up again.
>
> Thanks for the help,
>
> --
> Chris Cowart
> http://www.timesinks.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091207185606.GD1366>