From owner-freebsd-net@FreeBSD.ORG Tue Aug 17 19:00:19 2010 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57F391065670 for ; Tue, 17 Aug 2010 19:00:19 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4715D8FC25 for ; Tue, 17 Aug 2010 19:00:19 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o7HJ0Jof073165 for ; Tue, 17 Aug 2010 19:00:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o7HJ0Jhk073159; Tue, 17 Aug 2010 19:00:19 GMT (envelope-from gnats) Date: Tue, 17 Aug 2010 19:00:19 GMT Message-Id: <201008171900.o7HJ0Jhk073159@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Ihsan Junaidi Ibrahim Cc: Subject: Re: kern/147824: [msk]: watchdog timeouts X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ihsan Junaidi Ibrahim List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2010 19:00:19 -0000 The following reply was made to PR kern/147824; it has been noted by GNATS. From: Ihsan Junaidi Ibrahim To: bug-followup@FreeBSD.org, darb@edarb.com Cc: Subject: Re: kern/147824: [msk]: watchdog timeouts Date: Wed, 18 Aug 2010 02:29:09 +0800 --0015174c0fe2fb030f048e091f88 Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm also having this issue on the same model of motherboard except that I'm running on a 100mbps network. I would get watchdog timeouts and TX descriptor errors more frequently then not even there is minimal network activity i.e. just SSH in the box. I'm running 8.1-RELEASE. mskc0: port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at device 0.0 on pci2 msk0: on mskc0 msk0: Ethernet address: 00:ea:01:15:c6:52 miibus0: on msk0 mskc0: [ITHREAD] msk0: link state changed to UP msk0: watchdog timeout msk0: link state changed to DOWN msk0: link state changed to UP Having TSO and MSI disabled in sysctl and loader respectively does not appear to have any improvement. Additionally the kernel would panic when booting, this happens 1 in every 2 tries: Aug 18 01:35:26 kernel: mskc0: port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at device 0.0 on pci2 Aug 18 01:35:26 kernel: msk0: on mskc0 Aug 18 01:35:26 kernel: msk0: Ethernet address: ff:ff:ff:ff:ff:ff Aug 18 01:35:26 kernel: msk0: No PHY found! ... Panic message ensues This happens regardless whether the cable is plugged or not. Normal booting would be like this: Aug 18 01:35:26 kernel: mskc0: port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at device 0.0 on pci2 Aug 18 01:35:26 kernel: msk0: on mskc0 Aug 18 01:35:26 kernel: msk0: Ethernet address: 00:ea:01:15:c6:52 Aug 18 01:35:26 kernel: miibus0: on msk0 Aug 18 01:35:26 kernel: e1000phy0: PHY 0 on miibus0 Aug 18 01:35:26 kernel: e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto Aug 18 01:35:26 kernel: mskc0: [ITHREAD] # ifconfig msk0 msk0: flags=8843 metric 0 mtu 1500 options=c011a ether 00:ea:01:15:c6:52 inet 192.168.2.10 netmask 0xffffff00 broadcast 192.168.2.255 media: Ethernet autoselect (100baseTX ) status: active -- Thank you for your time, Ihsan Junaidi Ibrahim --0015174c0fe2fb030f048e091f88 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I'm also having this issue on the same model of = motherboard except that I'm running on a 100mbps network. I would get w= atchdog timeouts and TX descriptor errors more frequently then not even the= re is minimal network activity i.e. just SSH in the box. I'm running 8.= 1-RELEASE.

mskc0: <Marvell Yukon 88E8056 Gigabit Ethernet> p= ort 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at device 0.0 on pci2
msk0: <Marvell Technology Group Ltd. Yukon EC Ultra Id 0xb4 Rev = 0x05> on mskc0
msk0: Ethernet address: 00:ea:01:15:c6:52
miibus0: <MII b= us> on msk0
mskc0: [ITHREAD]
msk0: link state change= d to UP
msk0: watchdog timeout
msk0: link state changed= to DOWN
msk0: link state changed to UP

Having TSO and= MSI disabled in sysctl and loader respectively does not appear to have any= improvement.

Additionally the kernel would panic = when booting, this happens 1 in every 2 tries:

Aug 18 01:35:26 =A0kernel: mskc0: <Marvell Yukon 88E= 8056 Gigabit Ethernet> port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq = 18 at device 0.0 on pci2
Aug 18 01:35:26 =A0kernel: msk0: <Mar= vell Technology Group Ltd. Yukon EC Ultra Id 0xb4 Rev 0x05> on mskc0
Aug 18 01:35:26 =A0kernel: msk0: Ethernet address: ff:ff:ff:ff:ff:ff
Aug 18 01:35:26 =A0kernel: msk0: No PHY found!
...
=
Panic message ensues

This happens regardless = whether the cable is plugged or not.

Normal booting would be like this:

=
Aug 18 01:35:26 =A0kernel: mskc0: <Marvell Yukon 88E8056 Gigab= it Ethernet> port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at devi= ce 0.0 on pci2
Aug 18 01:35:26 =A0kernel: msk0: <Marvell Technology Group Ltd. Yuk= on EC Ultra Id 0xb4 Rev 0x05> on mskc0
Aug 18 01:35:26 =A0kern= el: msk0: Ethernet address: 00:ea:01:15:c6:52
Aug 18 01:35:26 =A0= kernel: miibus0: <MII bus> on msk0
Aug 18 01:35:26 =A0kernel: e1000phy0: <Marvell 88E1149 Gigabit PHY&= gt; PHY 0 on miibus0
Aug 18 01:35:26 =A0kernel: e1000phy0: =A010b= aseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto=
Aug 18 01:35:26 =A0kernel: mskc0: [ITHREAD]

=
# ifconfig msk0
msk0: flags=3D8843<UP,BROADCAST,RUNN= ING,SIMPLEX,MULTICAST> metric 0 mtu 1500
=A0=A0 =A0 =A0 =A0opt= ions=3Dc011a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,VLAN_HWTSO,LINKSTATE>= ;
=A0=A0 =A0 =A0 =A0ether 00:ea:01:15:c6:52
=A0=A0 =A0 =A0 =A0= inet 192.168.2.10 netmask 0xffffff00 broadcast 192.168.2.255
=A0= =A0 =A0 =A0 =A0media: Ethernet autoselect (100baseTX <full-duplex,flag0,= flag1>)
=A0=A0 =A0 =A0 =A0status: active

--
Thank you for your time,
Ihsan Junaidi Ibrah= im
--0015174c0fe2fb030f048e091f88--