From owner-freebsd-current@FreeBSD.ORG Mon Aug 14 14:17:10 2006 Return-Path: X-Original-To: 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 1614216A4E0; Mon, 14 Aug 2006 14:17:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6C7743D68; Mon, 14 Aug 2006 14:17:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k7EEGn9i013497; Mon, 14 Aug 2006 10:16:52 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 14 Aug 2006 09:11:56 -0400 User-Agent: KMail/1.9.1 References: <44DCFFBC.7080807@elischer.org> In-Reply-To: <44DCFFBC.7080807@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608140911.56908.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Mon, 14 Aug 2006 10:16:52 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/1659/Mon Aug 14 04:44:22 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Julian Elischer , current@freebsd.org Subject: Re: anyone seeing problems with bce driver? 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: Mon, 14 Aug 2006 14:17:10 -0000 On Friday 11 August 2006 18:07, Julian Elischer wrote: > We're seeing the following problems with a 6.1 based system with a bce > interface. > I've looked at -current and RELENG_6 and don't see any changes that > might affect this.. > > before I go diving further into the code, does anyone recognise this? > Looks like possibly the constantly incoming packets stop the PHY from > getting reinitialised. > I am guessing that when reinitiing we should stop new data from hitting > the chip. > I'm guessing this is what should be happenning but there is a window > somewhere > that is letting some through. Actually, there were some locking fixes I did in HEAD and 6-stable recently related to bce_watchdog() (IIRC). I'd check the 6-stable version of sys/dev/bce/* just to be sure. -- John Baldwin