From nobody@FreeBSD.org  Fri Jun 11 05:09:46 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9A1D816A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 11 Jun 2004 05:09:46 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7D32443D41
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 11 Jun 2004 05:09:46 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i5B59fWs096331
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 11 Jun 2004 05:09:41 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i5B59f3A096329;
	Fri, 11 Jun 2004 05:09:41 GMT
	(envelope-from nobody)
Message-Id: <200406110509.i5B59f3A096329@www.freebsd.org>
Date: Fri, 11 Jun 2004 05:09:41 GMT
From: Adam Dawson <adenergy@hotmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Marvell if_sk driver watchdog timeout issue on asus p4p800 motherboard
X-Send-Pr-Version: www-2.3

>Number:         67818
>Category:       i386
>Synopsis:       [sk] driver watchdog timeout issue on asus p4p800 motherboard
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bz
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 11 05:10:11 GMT 2004
>Closed-Date:    Wed Dec 28 09:40:14 GMT 2005
>Last-Modified:  Wed Dec 28 09:40:14 GMT 2005
>Originator:     Adam Dawson
>Release:        5.2.1-RELEASE
>Organization:
Home
>Environment:
FreeBSD host 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:45:55 GMT 2004     root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
      sk0 network interface stops passing traffic during high traffic load. Occasionally a "sk0: watchdog timeout" error is sent to console,messages but not always.
Tried unplugging/reconnecting network cable - no go
Tried ifconfig sk0 down; ifconfig sk0 up - no go

Sometimes it returns after about a minute or 2, most times requires a reboot.

From the server I can use FTP to get a large file from another server OK. Breaks if I try to put a large fle to another server.

Using a 2.8Ghz processor with hyperthreading enabled on an asus p4p800 motherboard. The interface is built into the motherboard.

Interface still appears to be recieving packets eg. tcpdump sees traffic such as ping requests but no replies are sent.

Using IPFW but tried with ipfw disabled and it is still a problem.



CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2798.66-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf25  Stepping = 5
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C
MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Hyperthreading: 2 logical CPUs
real memory  = 1072889856 (1023 MB)
avail memory = 1032847360 (985 MB)
ACPI APIC Table: <A M I  OEMAPIC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0: Changing APIC ID to 2
ioapic0 <Version 2.0> irqs 0-23 on motherboard
Pentium Pro MTRR support enabled

..

skc0: <Marvell Gigabit Ethernet> port 0xd800-0xd8ff mem 0xfeafc000-0xfeafffff irq 22 at device 5.0 on pci2
skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
sk0: Ethernet address: 00:0e:a6:94:b8:fd
miibus0: <MII bus> on sk0
e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto


>How-To-Repeat:
      Standard FreeBSD 5.2.1 install on hardware specified above. Transfer alot of traffic. Appears to be high outbound traffic that causes the problem.

>Fix:
      Dont know one.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-i386->freebsd-bugs 
Responsible-Changed-By: simon 
Responsible-Changed-When: Sat Jun 12 08:13:18 GMT 2004 
Responsible-Changed-Why:  
Reassign misfiled PR (does not sound particular i386 specific). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67818 

From: "Martin Lui" <bigfoot@martian111.net>
To: <freebsd-gnats-submit@FreeBSD.org>, <adenergy@hotmail.com>
Cc:  
Subject: Re: i386/67818: Marvell if_sk driver watchdog timeout issue on asus p4p800 motherboard
Date: Wed, 25 Aug 2004 01:02:30 -0700

 I have the same problem with my card, though I have a Linksys EG1032
 Gigabit Ethernet card.  It is installed on my router and fileserver.
 The watchdog timeout occurs when I try to get large files from the
 server.  Also, I noticed that during high traffic in general, not
 limiting to downloading large files from it.  However, I did not try to
 upload a large file to that server.
 
 I'm not really sure, but it seems like either a problem with the chipset
 or driver.  I have a Soyo Dragon Plus motherboard with an Athlon XP
 1500+ processor.  Here's some extra hardware info to help out whoever is
 trying to fix this:
 
 uname -a:
 FreeBSD samba.* 4.10-RELEASE-p2 FreeBSD 4.10-RELEASE-p2 #1: Sun Jul 18
 20:21:40 PDT 2004
 martian111@simba.*:/usr/obj/home/extra1/servers/FreeBSD/4.10-RELENG/src/
 sys/MLUI-2004071801  i386
 
 dmesg -a:
 Timecounter "i8254"  frequency 1193182 Hz
 CPU: AMD Athlon(tm) XP 1500+ (1330.01-MHz 686-class CPU)
   Origin = "AuthenticAMD"  Id = 0x662  Stepping = 2
  
 Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,C
 MOV,PA
 T,PSE36,MMX,FXSR,SSE>
   AMD Features=0xc0480000<MP,AMIE,DSP,3DNow!>
 real memory  = 402587648 (393152K bytes)
 
 ...
 
 skc0: <Linksys EG1032 Gigabit Ethernet> port 0xb400-0xb4ff mem
 0xe8020000-0xe8023fff irq 10 at device 9.0 on pci0
 skc0: SK-9521 10/100/1000Base-T Adapter
 sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
 sk0: Ethernet address: 00:0c:41:e5:4a:54
 miibus1: <MII bus> on sk0
 e1000phy0: <Marvell Semiconductor 88E1000* gigabit PHY> on miibus1
 e1000phy0:  1000baseTX-FDX, 100baseTX-FDX, 100baseTX, 10baseTX-FDX,
 10baseTX, auto
 
 
 My Solution:  Get a new gibabit card.  This worked for me.  I got a hold
 of a Dell gigabit Ethernet Card that came with a computer I just bought.
 It was an extra card so I pulled it out and put it in my server.  WORKS
 PERFECTLY.  It uses the bge driver, not sk.  Here is the dmesg for it:
 
 bge0: <Broadcom BCM5705 Gigabit Ethernet, ASIC rev. 0x3001> mem
 0xe8020000-0xe802ffff irq 10 at device 9.0 on pci0
 bge0: Ethernet address: 00:10:18:0c:44:b3
 miibus1: <MII bus> on bge0
 brgphy0: <BCM5705 10/100/1000baseTX PHY> on miibus1
 brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
 1000baseTX-FDX, auto
 
 and pciconf -l -v for it:
 
 bge0@pci0:9:0:  class=0x020000 card=0x86531028 chip=0x165314e4 rev=0x01
 hdr=0x00
     vendor   = 'Broadcom Corporation'
     device   = 'NetXtreme Gigabit Ethernet'
     class    = network
     subclass = Ethernet
 
 Hope this helps and hope that the sk problem gets fixed soon.
 

From: Palle Girgensohn <girgen@pingpong.net>
To: freebsd-gnats-submit@FreeBSD.org, adenergy@hotmail.com,
	obrien@FreeBSD.org, jmg@FreeBSD.org
Cc:  
Subject: Re: i386/67818: Marvell if_sk driver watchdog timeout issue on asus
 p4p800 motherboard
Date: Fri, 12 Nov 2004 17:18:37 +0100

 Hi!
 
 I see the same thing here with both 4.10 and 5.3b7. Is there any way to fix 
 this? I have a bunch of these mobo:s, bought them because they got great 
 reviews, but none of the NICs work in FreeBSD. :(
 
 /Palle
 
State-Changed-From-To: open->feedback 
State-Changed-By: bz 
State-Changed-When: Sat Nov 20 13:05:58 GMT 2004 
State-Changed-Why:  
Patches have been committed to HEAD. 
Please give them a try and let us know if the problems persist? 

If you are running 5.3 or newer RELENG_5 simply copying over 
if_sk.c (r1.92) and if_skreg.h (r1.24) from HEAD to 
your local tree should be fine for testing. 


Responsible-Changed-From-To: freebsd-bugs->bz 
Responsible-Changed-By: bz 
Responsible-Changed-When: Sat Nov 20 13:05:58 GMT 2004 
Responsible-Changed-Why:  
I'll handle this. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67818 

From: "Allan Zhang" <zhangliangsd@hotmail.com>
To: <freebsd-gnats-submit@FreeBSD.org>
Cc:  
Subject: Re: i386/67818: Marvell if_sk driver watchdog timeout issue on asus p4p800 motherboard
Date: Sun, 2 Jan 2005 13:53:18 -0500

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_0008_01C4F0D2.69C0ADD0
 Content-Type: text/plain;
 	charset="gb2312"
 Content-Transfer-Encoding: quoted-printable
 
 Freebsd 5.3 has the same problem. It crashed the sk0 to transfer a big =
 file using scp. It seems that a strange file name will crash it also. I =
 do not spend a lot of time to debug this issue.
 
 Allan
 ------=_NextPart_000_0008_01C4F0D2.69C0ADD0
 Content-Type: text/html;
 	charset="gb2312"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META http-equiv=3DContent-Type content=3Dtext/html;charset=3Dgb2312>
 <STYLE></STYLE>
 
 <META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR></HEAD>
 <BODY id=3DMailContainerBody=20
 style=3D"PADDING-LEFT: 10px; FONT-WEIGHT: normal; FONT-SIZE: 10pt; =
 COLOR: #000000; BORDER-TOP-STYLE: none; PADDING-TOP: 15px; FONT-STYLE: =
 normal; FONT-FAMILY: Verdana; BORDER-RIGHT-STYLE: none; =
 BORDER-LEFT-STYLE: none; TEXT-DECORATION: none; BORDER-BOTTOM-STYLE: =
 none"=20
 leftMargin=3D0 topMargin=3D0 acc_role=3D"text" CanvasTabStop=3D"true"=20
 name=3D"Compose message area"><!--[gte IE 5]><?xml:namespace =
 prefix=3D"v" /><?xml:namespace prefix=3D"o" /><![endif]-->
 <DIV>Freebsd 5.3 has the same problem. It crashed the sk0 =
 to&nbsp;transfer a big=20
 file using scp. It seems that a strange file name will crash it also. I =
 do not=20
 spend&nbsp;a lot of time to debug this issue.</DIV>
 <DIV>&nbsp;</DIV>
 <DIV>Allan</DIV></BODY></HTML>
 
 ------=_NextPart_000_0008_01C4F0D2.69C0ADD0--

From: "Bjoern A. Zeeb" <bz@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/67818: Marvell if_sk driver watchdog timeout issue on asus
 p4p800 motherboard
Date: Sun, 2 Jan 2005 19:10:39 +0000 (UTC)

 5.3-RELEASE is known to be broken and won't help you.
 
 Please update to HEAD or RELENG_5 and let me know if
 you see any more problems.

From: "Bjoern A. Zeeb" <bz@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc: Adam Dawson <adenergy@hotmail.com>
Subject: Re: i386/67818: Marvell if_sk driver watchdog timeout issue on asus
 p4p800 motherboard
Date: Thu, 31 Mar 2005 10:11:27 +0000 (UTC)

 More patches got applied to HEAD and RELENG_5 and will also be
 included in upcoming 5.4-RC1. Could you please test?
 
 It would also be interesting to know if this a MP/HTT system
 if the problem can still be seen.
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Wed Sep 14 00:07:05 GMT 2005 
State-Changed-Why:  
Feedback timeout (> 4 months). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67818 
State-Changed-From-To: closed->open 
State-Changed-By: bz 
State-Changed-When: Wed Sep 14 05:26:22 GMT 2005 
State-Changed-Why:  
The problem (watchdog timeout) still exists. 
I have reports that it happens on other boards but now 
continues to run and no longer needs reboots. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67818 

From: James Risner <risner@stdio.com>
To: bug-followup@FreeBSD.org,  adenergy@hotmail.com
Cc:  
Subject: Re: i386/67818: [sk] driver watchdog timeout issue on asus p4p800
 motherboard
Date: Sat, 29 Oct 2005 03:32:09 -0400

 I still have this problem.
 
 I have had this problem since 5.0-RC.
 I have been checking it every release since 5.0 and I can also say that 
 I get the watchdogs now but the
 server doesn't reboot and seems to always recover in slightly longer 
 than it takes ssh to close the connection.
 
 FreeBSD akira.stdio.com 5.4-STABLE FreeBSD 5.4-STABLE #0: Wed Oct 12 
 02:44:58 EDT 2005     
 risner@akira.stdio.com:/usr/src/sys/i386/compile/AKIRA  i386
 
 /usr/src/sys/pci/if_sk.c:__FBSDID("$FreeBSD: src/sys/pci/if_sk.c,v 
 1.83.2.10 2005/08/05 18:12:17 bz Exp $");
 /usr/src/sys/pci/if_skreg.h: * $FreeBSD: src/sys/pci/if_skreg.h,v 
 1.20.2.5 2005/03/28 16:21:16 bz Exp $
 
 pci bus 0x0002 cardnum 0x05 function 0x00: vendor 0x10b7 device 0x1700
  3Com Corporation 3c940 1000Base?
  CardVendor 0x1043 card 0x80eb (Asustek Computer, Inc., Card unknown)
   STATUS    0x02b0  COMMAND 0x0117
   CLASS     0x02 0x00 0x00  REVISION 0x12
   BIST      0x00  HEADER 0x00  LATENCY 0x40  CACHE 0x04
   BASE0     0xfeaf8000  addr 0xfeaf8000  MEM
   BASE1     0x0000d801  addr 0x0000d800  I/O
   MAX_LAT   0x1f  MIN_GNT 0x17  INT_PIN 0x01  INT_LINE 0x16
   BYTE_0    0x00  BYTE_1  0x00  BYTE_2  0xb0  BYTE_3  0x05
 
 Oct 29 03:23:23 akira kernel: sk0: watchdog timeout
 
 skc0: <3Com 3C940 Gigabit Ethernet> port 0xd800-0xd8ff mem 
 0xfeaf8000-0xfeafbfff irq 22 at device 5.0 on pci2
 skc0: 3Com Gigabit LOM (3C940)
 sk0: <Marvell Semiconductor, Inc. Yukon> on skc0
 sk0: Ethernet address: 00:0c:6e:37:a0:43
 miibus0: <MII bus> on sk0
 e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus0
 e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 
 1000baseTX-FDX, auto
 
 sk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet .* netmask 0xffffff00 broadcast .*
         ether 00:0c:6e:37:a0:43
         media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
         status: active
 
 Timecounter "i8254" frequency 1193182 Hz quality 0
 CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (2605.92-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
   
 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,
 SSE,SSE2,SS,HTT,TM,PBE>
   Hyperthreading: 2 logical CPUs
 real memory  = 1072889856 (1023 MB)
 avail memory = 1040363520 (992 MB)
 ACPI APIC Table: <A M I  OEMAPIC >
 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
 ioapic0 <Version 2.0> irqs 0-23 on motherboard
 acpi0: <A M I OEMXSDT> on motherboard
 acpi0: Power Button (fixed)
 
 I am willing to run debugging, run special kernels, or whatever may help.
 
 If you would like me to do some of these tests, please follow up in this 
 ticket and I will perform the actions.
 
 Risner
 
 
 
State-Changed-From-To: open->closed 
State-Changed-By: bz 
State-Changed-When: Wed Dec 28 09:37:24 UTC 2005 
State-Changed-Why:  
I am closing this PR because the watchdog timeouts described 
in here a from a time before sk(4) got a lot of fixes. 
Please track PR 91000 for the watchdog timeouts problem that 
is still visible these days. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67818 
>Unformatted:
