kern/147824: [msk]: watchdog timeouts
Ihsan Junaidi Ibrahim
ihsan.junaidi at gmail.com
Tue Aug 17 19:00:19 UTC 2010
The following reply was made to PR kern/147824; it has been noted by GNATS.
From: Ihsan Junaidi Ibrahim <ihsan.junaidi at gmail.com>
To: bug-followup at FreeBSD.org, darb at 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: <Marvell Yukon 88E8056 Gigabit Ethernet> port 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 bus> 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: <Marvell Yukon 88E8056 Gigabit Ethernet>
port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at device 0.0 on pci2
Aug 18 01:35:26 kernel: msk0: <Marvell Technology Group Ltd. Yukon EC Ultra
Id 0xb4 Rev 0x05> 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: <Marvell Yukon 88E8056 Gigabit Ethernet>
port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at device 0.0 on pci2
Aug 18 01:35:26 kernel: msk0: <Marvell Technology Group Ltd. Yukon EC Ultra
Id 0xb4 Rev 0x05> on mskc0
Aug 18 01:35:26 kernel: msk0: Ethernet address: 00:ea:01:15:c6:52
Aug 18 01:35:26 kernel: miibus0: <MII bus> on msk0
Aug 18 01:35:26 kernel: e1000phy0: <Marvell 88E1149 Gigabit PHY> 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c011a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,VLAN_HWTSO,LINKSTATE>
ether 00:ea:01:15:c6:52
inet 192.168.2.10 netmask 0xffffff00 broadcast 192.168.2.255
media: Ethernet autoselect (100baseTX <full-duplex,flag0,flag1>)
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,<div><br></div><div>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.<br clear=3D"all">
<br></div><div><div>mskc0: <Marvell Yukon 88E8056 Gigabit Ethernet> p=
ort 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 18 at device 0.0 on pci2</d=
iv><div>msk0: <Marvell Technology Group Ltd. Yukon EC Ultra Id 0xb4 Rev =
0x05> on mskc0</div>
<div>msk0: Ethernet address: 00:ea:01:15:c6:52</div><div>miibus0: <MII b=
us> on msk0</div><div>mskc0: [ITHREAD]</div><div>msk0: link state change=
d to UP</div><div>msk0: watchdog timeout</div><div>msk0: link state changed=
to DOWN</div>
<div>msk0: link state changed to UP</div><div><br></div><div>Having TSO and=
MSI disabled in sysctl and loader respectively does not appear to have any=
improvement.</div><div><br></div><div>Additionally the kernel would panic =
when booting, this happens 1 in every 2 tries:</div>
<div><br></div><div>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</div><div>Aug 18 01:35:26 =A0kernel: msk0: <Mar=
vell Technology Group Ltd. Yukon EC Ultra Id 0xb4 Rev 0x05> on mskc0</di=
v>
<div>Aug 18 01:35:26 =A0kernel: msk0: Ethernet address: ff:ff:ff:ff:ff:ff</=
div><div>Aug 18 01:35:26 =A0kernel: msk0: No PHY found!</div><div>...</div>=
<div>Panic message ensues</div><div><br></div><div>This happens regardless =
whether the cable is plugged or not.</div>
<div><br></div><div>Normal booting would be like this:</div><div><br></div>=
<div><div>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</div>
<div>Aug 18 01:35:26 =A0kernel: msk0: <Marvell Technology Group Ltd. Yuk=
on EC Ultra Id 0xb4 Rev 0x05> on mskc0</div><div>Aug 18 01:35:26 =A0kern=
el: msk0: Ethernet address: 00:ea:01:15:c6:52</div><div>Aug 18 01:35:26 =A0=
kernel: miibus0: <MII bus> on msk0</div>
<div>Aug 18 01:35:26 =A0kernel: e1000phy0: <Marvell 88E1149 Gigabit PHY&=
gt; PHY 0 on miibus0</div><div>Aug 18 01:35:26 =A0kernel: e1000phy0: =A010b=
aseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto=
</div>
<div>Aug 18 01:35:26 =A0kernel: mskc0: [ITHREAD]</div></div><div><br></div>=
<div><div># ifconfig msk0</div><div>msk0: flags=3D8843<UP,BROADCAST,RUNN=
ING,SIMPLEX,MULTICAST> metric 0 mtu 1500</div><div>=A0=A0 =A0 =A0 =A0opt=
ions=3Dc011a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,VLAN_HWTSO,LINKSTATE>=
;</div>
<div>=A0=A0 =A0 =A0 =A0ether 00:ea:01:15:c6:52</div><div>=A0=A0 =A0 =A0 =A0=
inet 192.168.2.10 netmask 0xffffff00 broadcast 192.168.2.255</div><div>=A0=
=A0 =A0 =A0 =A0media: Ethernet autoselect (100baseTX <full-duplex,flag0,=
flag1>)</div><div>=A0=A0 =A0 =A0 =A0status: active</div>
</div><div><br></div>-- <br>Thank you for your time,<br>Ihsan Junaidi Ibrah=
im<br>
</div>
--0015174c0fe2fb030f048e091f88--
More information about the freebsd-net
mailing list