From owner-freebsd-sparc64@FreeBSD.ORG  Tue Feb  7 01:05:18 2006
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 D519416A420;
	Tue,  7 Feb 2006 01:05:18 +0000 (GMT)
	(envelope-from yashy@mail.yashy.com)
Received: from mail.yashy.com (mail.yashy.com [206.248.137.44])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 76DDD43D45;
	Tue,  7 Feb 2006 01:05:18 +0000 (GMT)
	(envelope-from yashy@mail.yashy.com)
Message-ID: <43E7F2A1.2020104@mail.yashy.com>
Date: Mon, 06 Feb 2006 20:06:41 -0500
From: Yasholomew Yashinski <yashy@mail.yashy.com>
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <200601200105.k0K15pBe051816@www.freebsd.org>
	<20060204230244.Y45494@carver.gumbysoft.com>
	<20060205114452.N46628@mail.yashy.com>
	<200602061325.12260.jhb@freebsd.org>
In-Reply-To: <200602061325.12260.jhb@freebsd.org>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-gnats-submit@freebsd.org, freebsd-sparc64@freebsd.org
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 <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>, 
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2006 01:05:19 -0000

John Baldwin wrote:

>>>>dc0: <Macronix 98715/98715A 10/100BaseTX> port 0x400-0x4ff mem
>>>>0x1800000-0x18000ff at device 2.0 on pci2 miibus1: <MII bus> on dc0
>>>>dcphy0: <Intel 21143 NWAY media interface> 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