From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 05:30:48 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F394516A4CE; Fri, 12 Dec 2003 05:30:47 -0800 (PST) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id B071643D09; Fri, 12 Dec 2003 05:30:45 -0800 (PST) (envelope-from robin.blanchard@gactr.uga.edu) Received: from 127.0.0.1 (localhost [127.0.0.1]) by dummy.domain.name (Postfix) with SMTP id 3E00A7730C; Fri, 12 Dec 2003 08:30:45 -0500 (EST) Received: from EBE1.gc.nat (E2K1.gc.nat [10.10.11.21]) by mail.gactr.uga.edu (Postfix) with ESMTP id 11DCC77305; Fri, 12 Dec 2003 08:30:45 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 12 Dec 2003 08:30:44 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Device bge watchdog timeouts Thread-Index: AcPAQM1R7XzqkOE9R7i37N+/ceQtHAAcwgGQ From: "Robin P. Blanchard" To: "Doug White" cc: Bill Paul cc: current@freebsd.org Subject: RE: Device bge watchdog timeouts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 13:30:48 -0000 > -----Original Message----- > From: Doug White [mailto:dwhite@gumbysoft.com]=20 > Sent: Thursday, December 11, 2003 6:45 PM > To: Robin P. Blanchard > Cc: current@freebsd.org; Bill Paul > Subject: Re: Device bge watchdog timeouts >=20 >=20 > On Thu, 11 Dec 2003, Robin P. Blanchard wrote: >=20 > > We just repurposed a Dell 2550 from a 4.9-STABLE backup=20 > server (very=20 > > intensive network load) to a 5.2-CURRENT=20 > shoutcast/realserver (minimal=20 > > network load) and are seeing watchdog timeout errors constantly. We=20 > > experience no such trouble in it's -STABLE incarnation (using the=20 > > -STABLE bge driver). We have temporarily given up on the=20 > bge driver in=20 > > -CURRENT and are using the other 100base (fxp) onboard nic.=20 > Has anyone=20 > > got any suggestions on how to get this machine running=20 > smoothly using=20 > > its gig interface (with > > -CURRENT) ? Thanks in advance. >=20 > This might be a wider problem with interrupt routing on your=20 > system. Post the output of 'boot -v' and try it with and=20 > without acpi for kicks. Good idea. Although I can't take this box down right now as it's happily streaming our local NPR affiliate. Nevertheless, I like your suspicion: # vmstat -i interrupt total rate irq1: atkbd0 2 0 irq4: sio0 22 0 irq6: fdc0 4 0 irq8: rtc 18682170 127 irq13: npx0 1 0 irq14: ata0 92 0 irq16: fxp0 12889411 88 irq20: pcm0 25138308 172 irq30: ahc0 15 0 irq31: aac0 17985 0 irq0: clk 145977654 1000 Total 202705665 1388 # dmesg |fgrep bge Preloaded elf module "/boot/modules/if_bge.ko" at 0xc07c01f4. bge0: mem 0xfeb00000-0xfeb0ffff irq 17 at device 8.0 on pci1 bge0: Ethernet address: 00:06:5b:05:33:99 miibus0: on bge0 Should not device bge / irq 17 be in the vmstat output above ?=20