From nobody@FreeBSD.org  Sat Apr 10 23:15:52 2010
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1E0761065675
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 10 Apr 2010 23:15:52 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 0E54C8FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 10 Apr 2010 23:15:52 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o3ANFpaP057775
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 10 Apr 2010 23:15:51 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id o3ANFpsZ057774;
	Sat, 10 Apr 2010 23:15:51 GMT
	(envelope-from nobody)
Message-Id: <201004102315.o3ANFpsZ057774@www.freebsd.org>
Date: Sat, 10 Apr 2010 23:15:51 GMT
From: Roar Pettersen <roar.pettersen@it.uib.no>
To: freebsd-gnats-submit@FreeBSD.org
Subject: BGE watchdog timeout --resetting -> crash
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         145621
>Category:       kern
>Synopsis:       [bge] [panic] bge watchdog timeout --resetting -> crash
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    yongari
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr 10 23:20:01 UTC 2010
>Closed-Date:    Mon Jan 17 19:58:11 UTC 2011
>Last-Modified:  Mon Jan 17 19:58:11 UTC 2011
>Originator:     Roar Pettersen
>Release:        FreeBSD 8.0-STABLE
>Organization:
University of Bergen
>Environment:
FreeBSD hib-vpn-gw.hib.no 8.0-STABLE FreeBSD 8.0-STABLE #3: Sat Apr 10 23:38:27 CEST 2010
root@hib-vpn-gw.hib.no:/usr/obj/usr/src/sys/HIB-VPN-GW  i386
>Description:

bge0@pci0:3:6:0:        class=0x020000 card=0x01211028 chip=0x164514e4 rev=0x15 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'broadtcomBCM5701 Gigabit Ethernet (BCM5701)'
    class      = network
    subclass   = ethernet
bge1@pci0:3:8:0:        class=0x020000 card=0x01211028 chip=0x164514e4 rev=0x15 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'broadtcomBCM5701 Gigabit Ethernet (BCM5701)'
    class      = network

# devinfo -rv | grep phy
            brgphy0 pnpinfo oui=0x818 model=0x11 rev=0x0 at phyno=1
            brgphy1 pnpinfo oui=0x818 model=0x11 rev=0x0 at phyno=1


# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device          miibus          # MII bus support
#device         bce             # Broadcom BCM5706/BCM5708 Gigabit Ethernet
device          bge             # Broadcom BCM570xx Gigabit Ethernet
#device          em              # Intel PRO/1000 adapter Gigabit Ethernet Card



I don't get a crash file in /var/crash, strange because I have this in my rc.conf :

# Add swap
tmpmfs="YES"
tmpsize="512m"
#
dumpdev="AUTO"
#
fsck_y_enable="YES"
#
background_fsck="NO"
>How-To-Repeat:
Every 15-20 minuttes I get a BGE watchdog timeout --resetting on the console, then the system reboots.
>Fix:


>Release-Note:
>Audit-Trail:

From: Roar Pettersen <roar.pettersen@uib.no>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-i386@FreeBSD.org
Cc:  
Subject: Re: i386/145621: BGE watchdog timeout --resetting -> crash
Date: Sun, 11 Apr 2010 11:40:39 +0200 (CEST)

 edprp            pts/1    10.0.0.1         Sun Apr 11 09:04 - crash  (00:16)
 edprp            pts/0    10.0.0.1         Sun Apr 11 08:57 - crash  (00:22)
 reboot           ~                         Sun Apr 11 08:29
 edprp            pts/1    10.0.0.1         Sun Apr 11 07:31 - crash  (00:58)
 edprp            pts/0    10.0.0.1         Sun Apr 11 07:30 - crash  (00:58)
 reboot           ~                         Sun Apr 11 00:59
 edprp            pts/1    10.0.0.1         Sun Apr 11 00:13 - crash  (00:45)
 edprp            pts/0    10.0.0.1         Sun Apr 11 00:13 - crash  (00:46)
 edprp            pts/1    10.0.0.1         Sat Apr 10 22:55 - crash  (00:07)
 edprp            pts/0    10.0.0.1         Sat Apr 10 22:49 - crash  (00:13)
 reboot           ~                         Sat Apr 10 22:49
 edprp            pts/1    10.0.0.1         Sat Apr 10 22:37 - crash  (00:12)
 edprp            pts/0    10.0.0.1         Sat Apr 10 22:35 - crash  (00:13)
 reboot           ~                         Sat Apr 10 22:34
 edprp            pts/1    10.0.0.1         Sat Apr 10 21:51 - crash  (00:43)
 edprp            pts/0    10.0.0.1         Sat Apr 10 21:48 - crash  (00:46)
 reboot           ~                         Sat Apr 10 21:04
 reboot           ~                         Sat Apr 10 20:45
 reboot           ~                         Sat Apr 10 20:25
 
 
 
 Copyright (c) 1992-2010 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
          The Regents of the University of California. All rights reserved.
 FreeBSD is a registered trademark of The FreeBSD Foundation.
 FreeBSD 8.0-STABLE #0: Sun Apr 11 03:20:07 CEST 2010
      root@hib-vpn-gw.hib.no:/usr/obj/usr/src/sys/HIB-VPN-GW i386
 Timecounter "i8254" frequency 1193182 Hz quality 0
 CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2389.60-MHz 686-class CPU)
    Origin = "GenuineIntel"  Id = 0xf27  Family = f  Model = 2  Stepping = 7
 
 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<CNXT-ID,xTPR>
 real memory  = 1073741824 (1024 MB)
 avail memory = 1040519168 (992 MB)
 ACPI APIC Table: <DELL   PE2650  >
 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 FreeBSD/SMP: 2 package(s) x 1 core(s) x 2 HTT threads
   cpu0 (BSP): APIC ID:  0
   cpu1 (AP/HT): APIC ID:  1
   cpu2 (AP): APIC ID:  6
   cpu3 (AP/HT): APIC ID:  7
 ioapic0: Changing APIC ID to 8
 ioapic1: Changing APIC ID to 9
 ioapic2: Changing APIC ID to 10
 MADT: Forcing active-low polarity and level trigger for SCI
 ioapic0 <Version 1.1> irqs 0-15 on motherboard
 ioapic1 <Version 1.1> irqs 16-31 on motherboard
 ioapic2 <Version 1.1> irqs 32-47 on motherboard
 kbd1 at kbdmux0
 acpi0: <DELL PE2650> on motherboard
 acpi0: [ITHREAD]
 acpi0: Power Button (fixed)
 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
 cpu0: <ACPI CPU> on acpi0
 cpu1: <ACPI CPU> on acpi0
 cpu2: <ACPI CPU> on acpi0
 cpu3: <ACPI CPU> on acpi0
 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
 pci0: <ACPI PCI bus> on pcib0
 pci0: <unknown> at device 4.0 (no driver attached)
 uart2: <Non-standard ns8250 class UART with FIFOs> port 0xec80-0xecbf mem 
 0xfe102000-0xfe102fff,0xfeb00000-0xfeb7ffff irq 23 at device 4.1 on pci0
 uart2: [FILTER]
 pci0: <unknown> at device 4.2 (no driver attached)
 vgapci0: <VGA-compatible display> port 0xe800-0xe8ff mem 
 0xfd000000-0xfdffffff,0xfe101000-0xfe101fff at device 14.0 on pci0
 atapci0: <ServerWorks CSB5 UDMA100 controller> port 
 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x8b0-0x8bf at device 15.1 on pci0
 ata0: <ATA channel 0> on atapci0
 ata0: [ITHREAD]
 ata1: <ATA channel 1> on atapci0
 ata1: [ITHREAD]
 ohci0: <OHCI (generic) USB controller> mem 0xfe100000-0xfe100fff irq 5 at 
 device 15.2 on pci0
 ohci0: [ITHREAD]
 usbus0: <OHCI (generic) USB controller> on ohci0
 isab0: <PCI-ISA bridge> at device 15.3 on pci0
 isa0: <ISA bus> on isab0
 pcib1: <ACPI Host-PCI bridge> on acpi0
 pci4: <ACPI PCI bus> on pcib1
 pcib2: <ACPI PCI-PCI bridge> at device 8.0 on pci4
 pci5: <ACPI PCI bus> on pcib2
 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on 
 pci4
 aac0: [FILTER]
 aac0: Adaptec RAID controller, aac driver 2.1.9-1
 pcib3: <ACPI Host-PCI bridge> on acpi0
 pci3: <ACPI PCI bus> on pcib3
 bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x000105> 
 mem 0xfcf10000-0xfcf1ffff irq 28 at device 6.0 on pci3
 miibus0: <MII bus> on bge0
 brgphy0: <BCM5701 10/100/1000baseTX PHY> PHY 1 on miibus0
 brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-FDX, auto
 bge0: Ethernet address: 00:06:5b:f1:c6:51
 bge0: [ITHREAD]
 bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x000105> 
 mem 0xfcf00000-0xfcf0ffff irq 29 at device 8.0 on pci3
 miibus1: <MII bus> on bge1
 brgphy1: <BCM5701 10/100/1000baseTX PHY> PHY 1 on miibus1
 brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 1000baseT-FDX, auto
 bge1: Ethernet address: 00:06:5b:f1:c6:52
 bge1: [ITHREAD]
 pcib4: <ACPI Host-PCI bridge> on acpi0
 pci2: <ACPI PCI bus> on pcib4
 pcib5: <ACPI Host-PCI bridge> on acpi0
 pci1: <ACPI PCI bus> on pcib5
 fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on 
 acpi0
 fdc0: [FILTER]
 fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
 atkbd0: <AT Keyboard> irq 1 on atkbdc0
 kbd0 at atkbd0
 atkbd0: [GIANT-LOCKED]
 atkbd0: [ITHREAD]
 psm0: <PS/2 Mouse> irq 12 on atkbdc0
 psm0: [GIANT-LOCKED]
 psm0: [ITHREAD]
 psm0: model IntelliMouse Explorer, device ID 4
 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
 uart0: [FILTER]
 uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
 uart1: [FILTER]
 atrtc0: <AT realtime clock> port 0x70-0x7f irq 8 on acpi0
 pmtimer0 on isa0
 orm0: <ISA Option ROMs> at iomem 
 0xc0000-0xc7fff,0xc8000-0xcbfff,0xec000-0xeffff pnpid ORM0000 on isa0
 sc0: <System console> at flags 0x100 on isa0
 sc0: VGA <16 virtual consoles, flags=0x300>
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 ppc0: parallel port not found.
 p4tcc0: <CPU Frequency Thermal Control> on cpu0
 p4tcc1: <CPU Frequency Thermal Control> on cpu1
 p4tcc2: <CPU Frequency Thermal Control> on cpu2
 p4tcc3: <CPU Frequency Thermal Control> on cpu3
 Timecounters tick every 1.953 msec
 usbus0: 12Mbps Full Speed USB v1.0
 acd0: CDROM <TEAC CD-ROM CD-224E/K.9A> at ata0-master UDMA33
 aacd0: <RAID 1 (Mirror)> on aac0
 aacd0: 34712MB (71091456 sectors)
 SMP: AP CPU #3 Launched!
 SMP: AP CPU #1 Launched!
 SMP: AP CPU #2 Launched!
 ugen0.1: <(0x1166)> at usbus0
 uhub0: <(0x1166) OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on 
 usbus0
 uhub0: 4 ports with 4 removable, self powered
 Trying to mount root from ufs:/dev/aacd0s1a
 WARNING: / was not properly dismounted
 Setting hostuuid: 44454c4c-3000-1034-8044-b8c04f52304a.
 Setting hostid: 0xce7a2875.
 Entropy harvesting:
   interrupts
   ethernet
   point_to_point
   kickstart
 .
 Starting file system checks:
 /dev/aacd0s1a: 11872 files, 300053 used, 2744994 free (882 frags, 343014 
 blocks, 0.0% fragmentation)
 /dev/aacd0s1f: 100 files, 70473 used, 4952704 free (56 frags, 619081 
 blocks, 0.0% fragmentation)
 /dev/aacd0s1d: 296534 files, 1757907 used, 2303156 free (79628 frags, 
 277941 blocks, 2.0% fragmentation)
 /dev/aacd0s1e: UNREF FILE I=188431  OWNER=root MODE=140666
 /dev/aacd0s1e: SIZE=0 MTIME=Apr 11 09:20 2010  (CLEARED)
 /dev/aacd0s1e: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
 /dev/aacd0s1e: SUMMARY INFORMATION BAD (SALVAGED)
 /dev/aacd0s1e: BLK(S) MISSING IN BIT MAPS (SALVAGED)
 /dev/aacd0s1e: 1291 files, 290418 used, 3770645 free (733 frags, 471239 
 blocks, 0.0% fragmentation)
 Mounting local file systems:
 .
 Setting hostname: hib-vpn-gw.hib.no
 .
 Starting Network: bge0 bge1 lo0.
 bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
 
 options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
          ether 00:06:5b:f1:c6:51
          inet 158.37.73.2 netmask 0xffffff00 broadcast 158.37.73.255
          media: Ethernet autoselect (none)
          status: no carrier
 bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
 
 options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
          ether 00:06:5b:f1:c6:52
          inet 10.192.1.1 netmask 0xffffff00 broadcast 10.192.1.255
          media: Ethernet autoselect (none)
          status: no carrier
 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
          options=3<RXCSUM,TXCSUM>
          inet 127.0.0.1 netmask 0xff000000
 Enabling pf
 pf enabled
 .
 add net default: gateway 158.37.73.1
 Additional routing options:
   IP gateway=YES
 .
 Starting devd.
 ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib 
 /usr/local/lib/compat/pkg /usr/local/lib/compat/pkg
 a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
 Creating and/or trimming log files
 .
 Starting syslogd.
 No core dumps found.
 Starting named.
 Setting date via ntp.
 11 Apr 11:28:10
 ntpdate[851]: sendto(158.37.73.1): Unknown error: 0
 bge0: link state changed to UP
 bge1: link state changed to UP
 11 Apr 11:28:12
 ntpdate[851]: sendto(158.37.73.1): Host is down
 11 Apr 11:28:13
 ntpdate[851]: sendto(158.37.73.1): Host is down
 11 Apr 11:28:14
 ntpdate[851]: no server suitable for synchronization found
 NFS access cache time=60
 Clearing /tmp (X related).
 Starting mpd5.
 Starting snmpd.
 Starting radiusd.
 Sun Apr 11 11:28:15 2010 : Info: Starting - reading configuration files 
 ...
 Starting dhcpd.
 Starting local daemons:
 add net 10.160.0.0: gateway 10.192.1.254
 add net 10.0.0.0: gateway 10.192.1.254
 add net 172.16.0.0: gateway 10.192.1.254
 add net 10.192.0.0: gateway 10.192.1.253
 .
 Updating motd:
 .
 Starting ntpd.
 Starting exim.
 Configuring syscons:
   keymap
   keyrate
   font8x16
   font8x14
   font8x8
   blanktime
   screensaver
 .
 Starting sshd.
 Starting cron.
 
 --
 Med vennlig hilsen / Regards;
 
    Roar Pettersen
    Universitetet i Bergen -  The University of Bergen
    Nygardsgt. 5  -  N-5020 BERGEN  - Norway
    Tlf: +47 55 58 40 55  fax: +47 55 58 40 70
    roar.pettersen@it.uib.no - IT-Avd, UiB - http://www.uib.no
Responsible-Changed-From-To: freebsd-i386->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Mon Apr 12 01:56:25 UTC 2010 
Responsible-Changed-Why:  
This does not sound i386-specific. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=145621 
State-Changed-From-To: open->feedback 
State-Changed-By: yongari 
State-Changed-When: Tue Jul 6 01:30:23 UTC 2010 
State-Changed-Why:  
Due to lack of backtrace I'm not sure whether you're seeing known 
bge(4) issue that was fixed in stable/8. Would you try latest 
stable/8 or 8.1-RC2? 
If you are still able to reproduce the panic on latest stable/8, 
please show me the backtrace information as well as verbosed 
dmesg output. 


Responsible-Changed-From-To: freebsd-net->yongari 
Responsible-Changed-By: yongari 
Responsible-Changed-When: Tue Jul 6 01:30:23 UTC 2010 
Responsible-Changed-Why:  
Grab. 

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

From: NetOne - Doychin Dokov <root@net1.cc>
To: bug-followup@FreeBSD.org, roar.pettersen@it.uib.no
Cc:  
Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt;
 crash
Date: Sun, 12 Sep 2010 17:57:36 +0300

   I'm having similar problem. I've upgraded to 8.1-RELEASE-p0, and have 
 tried using one of the on-board BCM5704 NICs (haven't tried before the 
 upgrade, so can't say if the problem is new or existed before too). I'm 
 getting bge watchdog timeouts exactly each 10 or 20 minutes. When using 
 em NICs, there are no problems. There were about 100 to 150 Mbits 
 traffic through the NIC while experiencing the problems.
 
 Sep 12 10:27:16 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 10:46:25 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 11:06:18 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 11:16:13 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 11:26:40 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 11:36:13 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 11:46:14 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 11:56:20 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 12:06:14 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 12:16:13 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 12:36:14 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 12:46:13 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 12:56:25 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 13:06:38 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 13:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 13:26:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 13:36:29 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 13:46:31 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 13:56:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 14:06:14 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 14:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 14:26:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 14:36:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 14:46:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 14:56:28 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 15:06:17 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 15:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 15:36:14 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 15:46:27 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 15:56:22 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 16:06:39 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 16:16:29 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 16:26:16 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 16:36:16 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 16:56:16 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 17:06:16 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 17:26:16 wilma kernel: bge0: watchdog timeout -- resetting
 Sep 12 17:27:41 wilma kernel: bge0: watchdog timeout -- resetting
 
 # uname -a
 FreeBSD wilma.net1.cc 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 
 02:36:49 UTC 2010     
 root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 
 # sysctl -a | grep asf
 hw.bge.allow_asf: 0
 
 # vmstat -i
 interrupt                          total       rate
 irq1: atkbd0                        2241          0
 irq10: ohci0 ohci1+                    3          0
 irq11: atapci0                    219522          7
 irq20: em0                       6593141        219
 irq21: em1                         23799          0
 irq24: bge0                    183105227       6097
 cpu0: timer                     60053653       1999
 cpu1: timer                     60053480       1999
 Total                          310051066      10325
 
 Sep 12 09:36:17 wilma kernel: bge0: <Broadcom NetXtreme Gigabit Ethernet 
 Controller, ASIC rev. 0x002100> mem 0xff3b0000-0xff3bffff irq 24 at 
 device 3.0 on pci2
 Sep 12 09:36:17 wilma kernel: bge1: <Broadcom NetXtreme Gigabit Ethernet 
 Controller, ASIC rev. 0x002100> mem 0xff3a0000-0xff3affff irq 25 at 
 device 3.1 on pci2
 
 If you need any more info, please let me know. This is a production 
 machine, so I can't do much testing, though.
 
 Kind regards,
 Doychin Dokov
 
 
 

From: NetOne - Doychin Dokov <root@net1.cc>
To: bug-followup@FreeBSD.org, roar.pettersen@it.uib.no
Cc:  
Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt;
 crash
Date: Mon, 13 Sep 2010 01:03:39 +0300

   Something more, I have exactly the same machine like the one I 
 mentioned above - this is Supermicro H8SSL-i2 motherboard with an 
 Opteron CPU. It's running FreeBSD 7.0-STABLE, pushing similar amounts of 
 traffic (>100, 200 Mbps peak), and not having a single problem with the 
 on-board bge devices.
State-Changed-From-To: feedback->open 
State-Changed-By: yongari 
State-Changed-When: Mon Sep 13 18:13:58 UTC 2010 
State-Changed-Why:  
Feedback received. 

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

From: Pyun YongHyeon <pyunyh@gmail.com>
To: NetOne - Doychin Dokov <root@net1.cc>
Cc: yongari@freebsd.org, bug-followup@FreeBSD.org
Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt; crash
Date: Mon, 13 Sep 2010 11:15:53 -0700

 --gBBFr7Ir9EOA20Yy
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 On Sun, Sep 12, 2010 at 03:20:03PM +0000, NetOne - Doychin Dokov wrote:
 > The following reply was made to PR kern/145621; it has been noted by GNATS.
 > 
 > From: NetOne - Doychin Dokov <root@net1.cc>
 > To: bug-followup@FreeBSD.org, roar.pettersen@it.uib.no
 > Cc:  
 > Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt;
 >  crash
 > Date: Sun, 12 Sep 2010 17:57:36 +0300
 > 
 >    I'm having similar problem. I've upgraded to 8.1-RELEASE-p0, and have 
 >  tried using one of the on-board BCM5704 NICs (haven't tried before the 
 >  upgrade, so can't say if the problem is new or existed before too). I'm 
 >  getting bge watchdog timeouts exactly each 10 or 20 minutes. When using 
 >  em NICs, there are no problems. There were about 100 to 150 Mbits 
 >  traffic through the NIC while experiencing the problems.
 >  
 >  Sep 12 10:27:16 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 10:46:25 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 11:06:18 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 11:16:13 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 11:26:40 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 11:36:13 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 11:46:14 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 11:56:20 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 12:06:14 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 12:16:13 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 12:36:14 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 12:46:13 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 12:56:25 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 13:06:38 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 13:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 13:26:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 13:36:29 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 13:46:31 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 13:56:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 14:06:14 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 14:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 14:26:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 14:36:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 14:46:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 14:56:28 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 15:06:17 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 15:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 15:36:14 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 15:46:27 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 15:56:22 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 16:06:39 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 16:16:29 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 16:26:16 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 16:36:16 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 16:56:16 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 17:06:16 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 17:26:16 wilma kernel: bge0: watchdog timeout -- resetting
 >  Sep 12 17:27:41 wilma kernel: bge0: watchdog timeout -- resetting
 >  
 >  # uname -a
 >  FreeBSD wilma.net1.cc 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 
 >  02:36:49 UTC 2010     
 >  root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 >  
 >  # sysctl -a | grep asf
 >  hw.bge.allow_asf: 0
 >  
 >  # vmstat -i
 >  interrupt                          total       rate
 >  irq1: atkbd0                        2241          0
 >  irq10: ohci0 ohci1+                    3          0
 >  irq11: atapci0                    219522          7
 >  irq20: em0                       6593141        219
 >  irq21: em1                         23799          0
 >  irq24: bge0                    183105227       6097
 >  cpu0: timer                     60053653       1999
 >  cpu1: timer                     60053480       1999
 >  Total                          310051066      10325
 >  
 >  Sep 12 09:36:17 wilma kernel: bge0: <Broadcom NetXtreme Gigabit Ethernet 
 >  Controller, ASIC rev. 0x002100> mem 0xff3b0000-0xff3bffff irq 24 at 
 >  device 3.0 on pci2
 >  Sep 12 09:36:17 wilma kernel: bge1: <Broadcom NetXtreme Gigabit Ethernet 
 >  Controller, ASIC rev. 0x002100> mem 0xff3a0000-0xff3affff irq 25 at 
 >  device 3.1 on pci2
 >  
 >  If you need any more info, please let me know. This is a production 
 >  machine, so I can't do much testing, though.
 >  
 
 Would you try attached patch and let me know how it works on your
 box?
 
 --gBBFr7Ir9EOA20Yy
 Content-Type: text/x-diff; charset=us-ascii
 Content-Disposition: attachment; filename="bge.rx.patch"
 
 Index: sys/dev/bge/if_bge.c
 ===================================================================
 --- sys/dev/bge/if_bge.c	(revision 212341)
 +++ sys/dev/bge/if_bge.c	(working copy)
 @@ -3386,9 +3386,11 @@
  	sc->bge_rx_saved_considx = rx_cons;
  	bge_writembx(sc, BGE_MBX_RX_CONS0_LO, sc->bge_rx_saved_considx);
  	if (stdcnt)
 -		bge_writembx(sc, BGE_MBX_RX_STD_PROD_LO, sc->bge_std);
 +		bge_writembx(sc, BGE_MBX_RX_STD_PROD_LO, (sc->bge_std +
 +		    BGE_STD_RX_RING_CNT - 1) % BGE_STD_RX_RING_CNT);
  	if (jumbocnt)
 -		bge_writembx(sc, BGE_MBX_RX_JUMBO_PROD_LO, sc->bge_jumbo);
 +		bge_writembx(sc, BGE_MBX_RX_JUMBO_PROD_LO, (sc->bge_jumbo +
 +		    BGE_JUMBO_RX_RING_CNT - 1) % BGE_JUMBO_RX_RING_CNT);
  #ifdef notyet
  	/*
  	 * This register wraps very quickly under heavy packet drops.
 
 --gBBFr7Ir9EOA20Yy--

From: NetOne - Doychin Dokov <root@net1.cc>
To: pyunyh@gmail.com
Cc: yongari@freebsd.org, bug-followup@FreeBSD.org
Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt;
 crash
Date: Wed, 15 Sep 2010 14:51:25 +0300

    13.9.2010 . 21:15 ., Pyun YongHyeon :
 > On Sun, Sep 12, 2010 at 03:20:03PM +0000, NetOne - Doychin Dokov wrote:
 >> The following reply was made to PR kern/145621; it has been noted by GNATS.
 >>
 >> From: NetOne - Doychin Dokov<root@net1.cc>
 >> To: bug-followup@FreeBSD.org, roar.pettersen@it.uib.no
 >> Cc:
 >> Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt;
 >>   crash
 >> Date: Sun, 12 Sep 2010 17:57:36 +0300
 >>
 >>     I'm having similar problem. I've upgraded to 8.1-RELEASE-p0, and have
 >>   tried using one of the on-board BCM5704 NICs (haven't tried before the
 >>   upgrade, so can't say if the problem is new or existed before too). I'm
 >>   getting bge watchdog timeouts exactly each 10 or 20 minutes. When using
 >>   em NICs, there are no problems. There were about 100 to 150 Mbits
 >>   traffic through the NIC while experiencing the problems.
 >>
 >>   Sep 12 10:27:16 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 10:46:25 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 11:06:18 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 11:16:13 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 11:26:40 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 11:36:13 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 11:46:14 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 11:56:20 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 12:06:14 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 12:16:13 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 12:36:14 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 12:46:13 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 12:56:25 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 13:06:38 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 13:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 13:26:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 13:36:29 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 13:46:31 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 13:56:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 14:06:14 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 14:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 14:26:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 14:36:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 14:46:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 14:56:28 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 15:06:17 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 15:16:15 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 15:36:14 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 15:46:27 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 15:56:22 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 16:06:39 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 16:16:29 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 16:26:16 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 16:36:16 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 16:56:16 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 17:06:16 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 17:26:16 wilma kernel: bge0: watchdog timeout -- resetting
 >>   Sep 12 17:27:41 wilma kernel: bge0: watchdog timeout -- resetting
 >>
 >>   # uname -a
 >>   FreeBSD wilma.net1.cc 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19
 >>   02:36:49 UTC 2010
 >>   root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 >>
 >>   # sysctl -a | grep asf
 >>   hw.bge.allow_asf: 0
 >>
 >>   # vmstat -i
 >>   interrupt                          total       rate
 >>   irq1: atkbd0                        2241          0
 >>   irq10: ohci0 ohci1+                    3          0
 >>   irq11: atapci0                    219522          7
 >>   irq20: em0                       6593141        219
 >>   irq21: em1                         23799          0
 >>   irq24: bge0                    183105227       6097
 >>   cpu0: timer                     60053653       1999
 >>   cpu1: timer                     60053480       1999
 >>   Total                          310051066      10325
 >>
 >>   Sep 12 09:36:17 wilma kernel: bge0:<Broadcom NetXtreme Gigabit Ethernet
 >>   Controller, ASIC rev. 0x002100>  mem 0xff3b0000-0xff3bffff irq 24 at
 >>   device 3.0 on pci2
 >>   Sep 12 09:36:17 wilma kernel: bge1:<Broadcom NetXtreme Gigabit Ethernet
 >>   Controller, ASIC rev. 0x002100>  mem 0xff3a0000-0xff3affff irq 25 at
 >>   device 3.1 on pci2
 >>
 >>   If you need any more info, please let me know. This is a production
 >>   machine, so I can't do much testing, though.
 >>
 > Would you try attached patch and let me know how it works on your
 > box?
 Hi,
 
 I would be able to try that around the end of the week (Friday/Saturday 
 maybe). Will let you know it makes a difference.
 
 Is the high IRQ count normal?
 
 Kind regards,
 Doychin

From: Pyun YongHyeon <pyunyh@gmail.com>
To: NetOne - Doychin Dokov <root@net1.cc>
Cc: yongari@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt; crash
Date: Wed, 15 Sep 2010 18:23:32 -0700

 On Wed, Sep 15, 2010 at 02:51:25PM +0300, NetOne - Doychin Dokov wrote:
 
 [...]
 
 > >>  # uname -a
 > >>  FreeBSD wilma.net1.cc 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19
 > >>  02:36:49 UTC 2010
 > >>  root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 > >>
 > >>  # sysctl -a | grep asf
 > >>  hw.bge.allow_asf: 0
 > >>
 > >>  # vmstat -i
 > >>  interrupt                          total       rate
 > >>  irq1: atkbd0                        2241          0
 > >>  irq10: ohci0 ohci1+                    3          0
 > >>  irq11: atapci0                    219522          7
 > >>  irq20: em0                       6593141        219
 > >>  irq21: em1                         23799          0
 > >>  irq24: bge0                    183105227       6097
 > >>  cpu0: timer                     60053653       1999
 > >>  cpu1: timer                     60053480       1999
 > >>  Total                          310051066      10325
 > >>
 > >>  Sep 12 09:36:17 wilma kernel: bge0:<Broadcom NetXtreme Gigabit Ethernet
 > >>  Controller, ASIC rev. 0x002100>  mem 0xff3b0000-0xff3bffff irq 24 at
 > >>  device 3.0 on pci2
 > >>  Sep 12 09:36:17 wilma kernel: bge1:<Broadcom NetXtreme Gigabit Ethernet
 > >>  Controller, ASIC rev. 0x002100>  mem 0xff3a0000-0xff3affff irq 25 at
 > >>  device 3.1 on pci2
 > >>
 > >>  If you need any more info, please let me know. This is a production
 > >>  machine, so I can't do much testing, though.
 > >>
 > >Would you try attached patch and let me know how it works on your
 > >box?
 > Hi,
 > 
 > I would be able to try that around the end of the week (Friday/Saturday 
 > maybe). Will let you know it makes a difference.
 > 
 > Is the high IRQ count normal?
 > 
 
 That depends on your network load and it looks normal to me.
 However if you happen to see 20k/s interrupts it would indicate you
 may have to tune some interrupt coalescing parameters.

From: Pyun YongHyeon <pyunyh@gmail.com>
To: NetOne - Doychin Dokov <root@net1.cc>
Cc: yongari@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/145621: [bge] [panic] bge watchdog timeout --resetting -&gt; crash
Date: Tue, 19 Oct 2010 18:10:01 -0700

 On Wed, Sep 15, 2010 at 06:23:32PM -0700, Pyun YongHyeon wrote:
 > On Wed, Sep 15, 2010 at 02:51:25PM +0300, NetOne - Doychin Dokov wrote:
 > 
 > [...]
 > 
 > > >>  # uname -a
 > > >>  FreeBSD wilma.net1.cc 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19
 > > >>  02:36:49 UTC 2010
 > > >>  root@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
 > > >>
 > > >>  # sysctl -a | grep asf
 > > >>  hw.bge.allow_asf: 0
 > > >>
 > > >>  # vmstat -i
 > > >>  interrupt                          total       rate
 > > >>  irq1: atkbd0                        2241          0
 > > >>  irq10: ohci0 ohci1+                    3          0
 > > >>  irq11: atapci0                    219522          7
 > > >>  irq20: em0                       6593141        219
 > > >>  irq21: em1                         23799          0
 > > >>  irq24: bge0                    183105227       6097
 > > >>  cpu0: timer                     60053653       1999
 > > >>  cpu1: timer                     60053480       1999
 > > >>  Total                          310051066      10325
 > > >>
 > > >>  Sep 12 09:36:17 wilma kernel: bge0:<Broadcom NetXtreme Gigabit Ethernet
 > > >>  Controller, ASIC rev. 0x002100>  mem 0xff3b0000-0xff3bffff irq 24 at
 > > >>  device 3.0 on pci2
 > > >>  Sep 12 09:36:17 wilma kernel: bge1:<Broadcom NetXtreme Gigabit Ethernet
 > > >>  Controller, ASIC rev. 0x002100>  mem 0xff3a0000-0xff3affff irq 25 at
 > > >>  device 3.1 on pci2
 > > >>
 > > >>  If you need any more info, please let me know. This is a production
 > > >>  machine, so I can't do much testing, though.
 > > >>
 > > >Would you try attached patch and let me know how it works on your
 > > >box?
 > > Hi,
 > > 
 > > I would be able to try that around the end of the week (Friday/Saturday 
 > > maybe). Will let you know it makes a difference.
 > > 
 
 Any progress here? Please let me know whether the patch fixes the
 issue or not. Note, the patch already MFCed to stable/8 and
 stable/7 so if you don't see the issue on stable/8 it means the
 patch worked.
 
 > > Is the high IRQ count normal?
 > > 
 > 
 > That depends on your network load and it looks normal to me.
 > However if you happen to see 20k/s interrupts it would indicate you
 > may have to tune some interrupt coalescing parameters.
State-Changed-From-To: open->closed 
State-Changed-By: yongari 
State-Changed-When: Mon Jan 17 19:56:37 UTC 2011 
State-Changed-Why:  
Feedback timeout. 
There was a bge(4) stability issue but I believe it was fixed. If 
you happen to see it again, please open a new PR. 

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