From owner-cvs-src@FreeBSD.ORG Thu Dec 14 00:54:53 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 14D0316A4C9; Thu, 14 Dec 2006 00:54:53 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B99843CA0; Thu, 14 Dec 2006 00:51:53 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id kBE0rOdV045369; Wed, 13 Dec 2006 19:53:25 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Scott Long Date: Wed, 13 Dec 2006 19:53:19 -0500 User-Agent: KMail/1.6.2 References: <200612132051.kBDKppS4058663@repoman.freebsd.org> <200612131846.33252.jkim@FreeBSD.org> <45809992.5030604@samsco.org> In-Reply-To: <45809992.5030604@samsco.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200612131953.22024.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2327/Wed Dec 13 16:56:09 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/bge if_bge.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Dec 2006 00:54:53 -0000 On Wednesday 13 December 2006 07:23 pm, Scott Long wrote: > Jung-uk Kim wrote: > > On Wednesday 13 December 2006 03:51 pm, Scott Long wrote: > >> scottl 2006-12-13 20:51:51 UTC > >> > >> FreeBSD src repository > >> > >> Modified files: > >> sys/dev/bge if_bge.c > >> Log: > >> Remove a redundant write of the firmware reset magic number. > >> It looks to have been added erroneously, and it causes problems > >> on some chips. A larger change is needed to do this write at a > >> more appropriate place, but that change requires reworking the > >> ASF logic. That will be worked on in the future. > >> > >> Submitted by: Bruce Evans > > > > I am still getting firmware handshake timeouts and/or watchdog > > timeouts. Most importantly it panics or get witness warnings > > (lots of 'memory modified after free'). Panic goes like this > > (while kldunload if_bge with dhclient enabled): > > > > brgphy0: detached > > miibus0: detached > > bge0: firmware handshake timed out, found 0x4b657654 > > bge0: firmware handshake timed out, found 0x4b657654 > > bge0: detached > > bge0: mem ... > > bge0: firmware handshake timed out, found 0x4b657654 > > bge0: firmware handshake timed out, found 0x4b657654 > > miibus0: on bge0 > > brgphy0: on miibus0 > > brgphy0: 10baseT, ... > > bge0: Ethernet address: ... > > bge0: firmware handshake timed out, found 0x4b657654 > > bge0: firmware handshake timed out, found 0x4b657654 > > bge0: discard frame w/o leading ethernet header (len 4294967192 > > pkt len 42949672) > > Kernel page fault with the following non-sleepable locks held: > > exclusive sleep mutex bge0 (network driver) r = 0 > > (0xffffffff80e81010) locked @ > > /usr/src/sys/modules/bge/../../dev/bge/if_bge.c:2828 ... > > > > As you can see the packet length is really bogus. I am wondering > > if the chip is actually initialized correctly to begin with. > > > > Jung-uk Kim > > Does it work correctly before you do the unload? I believe it does. However, some times I get watchdog timeout by doing ifconfig down/up. It does not recover from it and it spits out lots of 'memory modified after free' warnings. Jung-uk Kim