From risner@akira.stdio.com  Sun Sep 10 13:24:18 2006
Return-Path: <risner@akira.stdio.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7C52916A40F
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 10 Sep 2006 13:24:18 +0000 (UTC)
	(envelope-from risner@akira.stdio.com)
Received: from akira.stdio.com (akira.stdio.com [204.152.114.29])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0736443D45
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 10 Sep 2006 13:24:17 +0000 (GMT)
	(envelope-from risner@akira.stdio.com)
Received: from akira.stdio.com (localhost [127.0.0.1])
	by akira.stdio.com (8.13.6/8.13.6) with ESMTP id k8ADP9JM034751
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 10 Sep 2006 09:25:09 -0400 (EDT)
	(envelope-from risner@akira.stdio.com)
Received: (from risner@localhost)
	by akira.stdio.com (8.13.6/8.13.6/Submit) id k8ADP4MG034750;
	Sun, 10 Sep 2006 09:25:04 -0400 (EDT)
	(envelope-from risner)
Message-Id: <200609101325.k8ADP4MG034750@akira.stdio.com>
Date: Sun, 10 Sep 2006 09:25:04 -0400 (EDT)
From: risner@stdio.com
Reply-To: risner@stdio.com
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: sys/dev/sk [sk] still having watchdog timeouts
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         103090
>Category:       kern
>Synopsis:       [sk] sys/dev/sk still having watchdog timeouts
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    yongari
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 10 13:30:17 GMT 2006
>Closed-Date:    Tue Jun 12 07:46:49 GMT 2007
>Last-Modified:  Tue Jun 12 07:46:49 GMT 2007
>Originator:     James Risner
>Release:        FreeBSD 6.1-RELEASE-p5 i386
>Organization:
Openworld, Inc
>Environment:
System: FreeBSD akira.stdio.com 6.1-RELEASE-p5 FreeBSD 6.1-RELEASE-p5 #1: Sun Sep 3 03:08:46 EDT 2006 risner@akira.stdio.com:/usr/obj/usr/src/sys/AKIRA i386


Asus P4C800 Deluxe

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>
  Features2=0x4400<CNTX-ID,<b14>>
  Logical CPUs per core: 2
real memory  = 1072889856 (1023 MB)
avail memory = 1040838656 (992 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
skc0: <3Com 3C940 Gigabit Ethernet> port 0xd800-0xd8ff mem 0xfeaf8000-0xfeafbfff irq 22 at device 5.0 on pci2
skc0: 3Com Gigabit LOM (3C940) rev. (0x1)
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
Trying to mount root from ufs:/dev/twed0s1a

Buildworld from fresh cvsup on Sun Sep  3 01:27:01 2006:
*default release=cvs tag=RELENG_6_1

akira# mergemaster -cv
akira# make buildworld
akira# make buildkernel KERNCONF=AKIRA
akira# make installkernel KERNCONF=AKIRA
akira# mergemaster -p
akira# make installworld
akira# make delete-old

>Description:
	The sk driver has always had problems since I first installed this machine.
For the last year it has been working well enough that it doesn't require a reboot to start
working again.  I read in problem kern/91000 that the sk watchdog timers should be gone,
so I tried it out.  They are still present for me.  This causes loss of connectivity long
enough to reset a putty session (and require "Duplicate Session" to log back in.)
I can run any tests required or requested.

>How-To-Repeat:
I can not make the problem fail.  It seems to happen during use (while using putty or
using squid as a cache.)  It does not appear to damage outbound ssh connections (so
my ssh commands inside screen to other machines rarely get disconnected.)

Here is a list of the timeouts since 9/3/06:
Sep  9 00:23:42 akira kernel: sk0: watchdog timeout
Sep  9 00:36:08 akira kernel: sk0: watchdog timeout
Sep  9 00:39:53 akira kernel: sk0: watchdog timeout
Sep  9 00:43:53 akira kernel: sk0: watchdog timeout
Sep  9 00:50:29 akira kernel: sk0: watchdog timeout
Sep  9 00:56:59 akira kernel: sk0: watchdog timeout
Sep 10 01:11:14 akira kernel: sk0: watchdog timeout
Sep 10 01:12:32 akira kernel: sk0: watchdog timeout
Sep 10 01:27:31 akira kernel: sk0: watchdog timeout
Sep 10 02:07:07 akira kernel: sk0: watchdog timeout

>Fix:

Probably the best fix for this is to go buy a PCI gig-e board based on e1000 Intel, but
I am stuck with the onboard and if I did add an onboard PCI, I would worry about the lower
maximum throughput from PCI vs onboard.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->yongari 
Responsible-Changed-By: yongari 
Responsible-Changed-When: Mon Sep 11 06:11:15 UTC 2006 
Responsible-Changed-Why:  
Grab. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=103090 
State-Changed-From-To: open->feedback 
State-Changed-By: yongari 
State-Changed-When: Mon Sep 11 06:17:50 UTC 2006 
State-Changed-Why:  
I think the issue was already fixed in CURRENT and stable. 
Would you please try sk(4) on stable(RELENG_6)? 

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

From: Rich Wales <richw@stanford.edu>
To: bug-followup@FreeBSD.org,  risner@stdio.com
Cc:  
Subject: Re: kern/103090: [sk] sys/dev/sk still having watchdog timeouts
Date: Tue, 10 Apr 2007 14:28:37 -0700

 I wonder whether the IRQ used by the network interface might have anything
 to do with the watchdog timeout problem -- either because the NIC is sharing
 an IRQ with some other device, and/or because it's got a low-priority IRQ.
 
 The builtin NIC in my 6.1-RELEASE system uses the "sk" driver and occasionally
 gets watchdog timeouts.  Until yesterday, it was using IRQ 5 (which is pretty
 low priority -- remember that IRQ 8-15 are all stuffed into the spot where IRQ
 2 was originally).  I tried reconfiguring the motherboard but wasn't able to
 get the NIC to use a better IRQ than this.

From: Pyun YongHyeon <pyunyh@gmail.com>
To: Rich Wales <richw@stanford.edu>
Cc: yongari@FreeBSD.org, bug-followup@FreeBSD.org, risner@stdio.com
Subject: Re: kern/103090: [sk] sys/dev/sk still having watchdog timeouts
Date: Wed, 11 Apr 2007 09:19:25 +0900

 On Tue, Apr 10, 2007 at 10:00:15PM +0000, Rich Wales wrote:
  > The following reply was made to PR kern/103090; it has been noted by GNATS.
  > 
  > From: Rich Wales <richw@stanford.edu>
  > To: bug-followup@FreeBSD.org,  risner@stdio.com
  > Cc:  
  > Subject: Re: kern/103090: [sk] sys/dev/sk still having watchdog timeouts
  > Date: Tue, 10 Apr 2007 14:28:37 -0700
  > 
  >  I wonder whether the IRQ used by the network interface might have anything
  >  to do with the watchdog timeout problem -- either because the NIC is sharing
  >  an IRQ with some other device, and/or because it's got a low-priority IRQ.
  >  
  >  The builtin NIC in my 6.1-RELEASE system uses the "sk" driver and occasionally
  >  gets watchdog timeouts.  Until yesterday, it was using IRQ 5 (which is pretty
  >  low priority -- remember that IRQ 8-15 are all stuffed into the spot where IRQ
  >  2 was originally).  I tried reconfiguring the motherboard but wasn't able to
  >  get the NIC to use a better IRQ than this.
 
 I think sk(4) in 6.1-RELEASE has several bugs and you should update
 to 6.2-RELEASE or 6-STABLE.
 If you still see watchdog timeout errors in 6.2-RELEASE or 6-STABLE
 please let me know.
 
 -- 
 Regards,
 Pyun YongHyeon
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Jun 12 07:45:22 UTC 2007 
State-Changed-Why:  
Feedback timeout (2 months). 

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