kern/147824: [msk]: watchdog timeouts

[Brad Degnan]

The following reply was made to PR kern/147824; it has been noted by GNATS.

From: Brad Degnan <darb at edarb.com>
To: Ihsan Junaidi Ibrahim <ihsan.junaidi at gmail.com>
Cc: bug-followup at FreeBSD.org
Subject: Re: kern/147824: [msk]: watchdog timeouts
Date: Tue, 17 Aug 2010 16:57:03 -0700

 On 8/17/2010 11:29 AM, Ihsan Junaidi Ibrahim wrote:
 > 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.
 >
 
 I had to change the network interface to 100mbps half-duplex before the 
 watchdog timeouts disappeared.  It's definitely not optimal but works 
 for me in the mean time.  Full-duplex at 1000 and 100 and half-duplex at 
 1000 give me the watchdog timeouts and tx descriptor errors.  Hope that 
 helps
 
 > 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.
 
 I haven't seen this yet, but I'm still on 8.1-PRERELEASE.  I have no 
 idea if downgrading would help.  Do you have the latest bios?
 
 best,
 Brad