amd64/73360: sk0: watchdog timeout

Simson L. Garfinkel simsong at acm.org
Sun Oct 31 13:20:13 PST 2004


>Number:         73360
>Category:       amd64
>Synopsis:       sk0: watchdog timeout
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Oct 31 21:20:12 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Simson L. Garfinkel
>Release:        5.3-RC1 FreeBSD  amd64
>Organization:
MIT
>Environment:
FreeBSD r3.nitroba.com 5.3-RC1 FreeBSD 5.3-RC1 #0: Sat Oct 30 13:05:38 EDT 2004     simsong at r3.nitroba.com:/usr/src/sys/amd64/compile/R3  amd64
      
>Description:
I have an AMD64 machine with an ASUS motherboard and an on-board syskonect gigabit ethernet. The syskonect is periodically going mute. It still receives packets but will not transmit. This happens in both gigabit and 100BaseT modes. 

It started happening a lot when I made the machine an NFS server.

Using a plug-in Intel etherexpress makes the problem go away.

>From reviewing the freeBSD mailing lists,this is a known problem.

sk0: discard frame w/o leading ethernet header (len 0 pkt len 0)
sk0: discard frame w/o leading ethernet header (len 0 pkt len 0)
sk0: discard frame w/o leading ethernet header (len 0 pkt len 0)
sk0: watchdog timeout
sk0: watchdog timeout
sk0: watchdog timeout
sk0: watchdog timeout


I wanted you to know that the problem hasn't gone away.      
>How-To-Repeat:
      
>Fix:
Don't use a syskonect.      
>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-amd64 mailing list