From owner-freebsd-sparc64@FreeBSD.ORG Tue Feb 7 01:10:08 2006 Return-Path: X-Original-To: freebsd-sparc64@hub.freebsd.org Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4050B16A420 for ; Tue, 7 Feb 2006 01:10:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BA4443D46 for ; Tue, 7 Feb 2006 01:10:08 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k171A7a6042943 for ; Tue, 7 Feb 2006 01:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k171A7W8042941; Tue, 7 Feb 2006 01:10:07 GMT (envelope-from gnats) Date: Tue, 7 Feb 2006 01:10:07 GMT Message-Id: <200602070110.k171A7W8042941@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Yasholomew Yashinski Cc: Subject: Re: sparc64/92033: dc(4) issues on Ultra10 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Yasholomew Yashinski 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 01:10:08 -0000 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/kerneldebug-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' 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. Thanks in Advance, -- Yashy