From owner-freebsd-sparc64@FreeBSD.ORG Tue Feb 7 15:53:04 2006 Return-Path: X-Original-To: freebsd-sparc64@freebsd.org Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85DF316A420 for ; Tue, 7 Feb 2006 15:53:04 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0226F43D49 for ; Tue, 7 Feb 2006 15:53:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 7936581 for multiple; Tue, 07 Feb 2006 10:53:49 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k17Fr01s048808; Tue, 7 Feb 2006 10:53:00 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-sparc64@freebsd.org, Yasholomew Yashinski Date: Tue, 7 Feb 2006 10:32:22 -0500 User-Agent: KMail/1.9.1 References: <200602070110.k171A7W8042941@freefall.freebsd.org> In-Reply-To: <200602070110.k171A7W8042941@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602071032.24371.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1280/Tue Feb 7 05:11:53 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: sparc64/92033: dc(4) issues on Ultra10 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Feb 2006 15:53:04 -0000 On Monday 06 February 2006 20:10, Yasholomew Yashinski wrote: > The following reply was made to PR sparc64/92033; it has been noted by > GNATS. > > From: Yasholomew Yashinski > To: John Baldwin > Cc: freebsd-sparc64@freebsd.org, Doug White , > freebsd-gnats-submit@freebsd.org > Subject: Re: sparc64/92033: dc(4) issues on Ultra10 > Date: Mon, 06 Feb 2006 20:06:41 -0500 > > John Baldwin wrote: > >>>>dc0: port 0x400-0x4ff mem > >>>>0x1800000-0x18000ff at device 2.0 on pci2 miibus1: on dc0 > >>>>dcphy0: on miibus1 > >>>>dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > >>>>dc0: [GIANT-LOCKED] > >>>> > >>>>Unread portion of the kernel message buffer: > >>>>panic: trap: data access error > >>>>Uptime: 4m15s > >>>>Dumping 512 MB (2 chunks) > >>>> chunk at 0: 268435456 bytes | > >>> > >>>Can you consistently reproduce this problem? If so, it is likely a > >>> device driver bug. The data_access_error trap doesn't usually > >>> indicate a hardware issue. > >> > >>Yes. As noted below, as soon as dc0 is called upon, the kernel > >>cores. This happens every time dc0 is called upon. > > > > Can you figure out which instance of CSR_READ_4() or DC_CLRBIT() is > > triggering this panic? > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel >debug-online-ddb.html I've added: > options DDB > to my kernel. > > When I try "boot -d" it just brings me up to a standard login prompt. So > I tried option two: > > # sysctl debug.enter_debugger=ddb > sysctl: unknown oid 'debug.enter_debugger' This is different in 6.0, you would now do 'sysctl debug.kdb.enter=1' IIRC. > at which point I went to the console and tried CTRL+ALT+ESC, in which > case the kernel appeared to core and the system rebooted. However it's > not recognized by gdb: > This GDB was configured as "sparc64-marcel-freebsd"... > "/var/crash/vmcore.8" is not a core dump: File format not recognized > > while on this topic (the next page in the handbook): > > # gdb -k /usr/obj/usr/src/sys/COLONEL/kernel > gdb: unrecognized option `-k' > Use `gdb --help' for a complete list of options. Use 'kgdb' rather than 'gdb -k'. However, what I would need you to do is add printf's or KTR traces to the dcphy_status() function before each CSR_READ_4() or DC_CLRBIT() and use that to figure out which one is failing. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org