From owner-freebsd-current@FreeBSD.ORG Wed Sep 10 19:38:12 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 5EB6C16A4BF for ; Wed, 10 Sep 2003 19:38:12 -0700 (PDT) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C62243FFB for ; Wed, 10 Sep 2003 19:38:09 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: from freebsd1.cimlogic.com.au (localhost [127.0.0.1]) by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h8B2epbZ073369 for ; Thu, 11 Sep 2003 12:40:51 +1000 (EST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h8B2eomb073368 for current@freebsd.org; Thu, 11 Sep 2003 12:40:50 +1000 (EST) Date: Thu, 11 Sep 2003 12:40:50 +1000 From: John Birrell To: current@freebsd.org Message-ID: <20030911024050.GB65671@freebsd1.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: fxp hangs reseting to a stable state 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: Thu, 11 Sep 2003 02:38:12 -0000 This is the first time I've tried to run -current on this little board. Up-to-date RELENG_4 kernels run fine. The probe message (port & memory) values are the same. On -current, the kernel gets up to the point in the fxp code where it is supposedly doing a "reset to a stable state" and then it hangs. I have set the kernel option BREAK_TO_DEBUGGER, but I can't get it to drop to DDB. The fxp driver reports that it is using memory space register mapping, so I guess that there is something different about the memory access in -current compared to RELENG_4. The question is what? I assume it's not a bios setup problem since RELENG_4 works fine. The kernels are net booted (using etherboot) over the very device that -current hangs on. Weird. Any hints on what is going on? -- John Birrell