From owner-freebsd-current@FreeBSD.ORG Tue Aug 29 21:34:15 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 30DE216A4E0 for ; Tue, 29 Aug 2006 21:34:15 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAB8C43D62 for ; Tue, 29 Aug 2006 21:34:09 +0000 (GMT) (envelope-from davidch@broadcom.com) Received: from 10.10.64.154 by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.2.0)); Tue, 29 Aug 2006 14:34:03 -0700 X-Server-Uuid: D9EB6F12-1469-4C1C-87A2-5E4C0D6F9D06 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id 0DFB82B0; Tue, 29 Aug 2006 14:34:03 -0700 (PDT) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id DD7732AF; Tue, 29 Aug 2006 14:34:02 -0700 (PDT) Received: from mail-irva-12.broadcom.com (mail-irva-12.broadcom.com [10.10.64.146]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id EDY86135; Tue, 29 Aug 2006 14:33:57 -0700 (PDT) Received: from NT-IRVA-0750.brcm.ad.broadcom.com (nt-irva-0750 [10.8.194.64]) by mail-irva-12.broadcom.com (Postfix) with ESMTP id 62E8869CA4; Tue, 29 Aug 2006 14:33:57 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 29 Aug 2006 14:33:56 -0700 Message-ID: <09BFF2FA5EAB4A45B6655E151BBDD90301E2EF85@NT-IRVA-0750.brcm.ad.broadcom.com> In-Reply-To: <20060829174337.GA60234@host.fqdn.net> Thread-Topic: [sam@fqdn.net: bce0 watchdog timeout errors] Thread-Index: AcbLks9Mwjw/yXzaTY6XXw8RLLfNeAAHzWsw From: "David Christensen" To: "Sam Eaton" , freebsd-current@freebsd.org X-TMWD-Spam-Summary: SEV=1.1; DFV=A2006082908; IFV=2.0.6,4.0-7; RPD=4.00.0004; RPDID=303030312E30413031303230332E34344634423138432E303033372D412D; ENG=IBF; TS=20060829213406; CAT=NONE; CON=NONE; X-MMS-Spam-Filter-ID: A2006082908_4.00.0004_2.0.6,4.0-7 X-WSS-ID: 68EA6D413882994999-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: Subject: RE: [sam@fqdn.net: bce0 watchdog timeout errors] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 29 Aug 2006 21:34:15 -0000 > I see looking through the archives that Julian Elischer has reported > something *vaguely* similar to my problems described in the attached > message to this list, so I thought I'd join in. >=20 > Julian reports a problem when the bce interface is=20 > disconnected and then > reconnected under load, and never comes back until all load=20 > is removed, > while reporting watchdog timeout errors. >=20 > I see something rather like this (details in the attached message > (hopefully the attachment will survive :))), but without physically > disconnecting the cable. >=20 > I am wondering if I'm actually seeing the same problem, but=20 > that rather > than the cable being unplugged, it's something like the interface > resetting on our (old, 100Mb/s) switch resetting and triggering this. >=20 > Thought it was worth offering another data point. I'm=20 > running the most > recent version of the bce driver with the changes to fix the 'mbuf' > errors. >=20 A change was recently added to bge (r1.140) to address some issues with locking in the driver when performing PHY accesses which was=20 also causing watchdog timeout errors. I need to look at those changes and see if they are applicable to the bce driver as well,=20 though I've been having problems loading both bge and bce as modules on -CURRENT (causes a panic). If I can get past the module problem I'll look at the bge change soon. Dave