From owner-freebsd-sparc64@FreeBSD.ORG  Mon Feb  6 18:30:12 2006
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 24D1416A420
	for <freebsd-sparc64@hub.freebsd.org>;
	Mon,  6 Feb 2006 18:30:12 +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 E590643D46
	for <freebsd-sparc64@hub.freebsd.org>;
	Mon,  6 Feb 2006 18:30:11 +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 k16IUB59018498
	for <freebsd-sparc64@freefall.freebsd.org>; Mon, 6 Feb 2006 18:30:11 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k16IUBO1018493;
	Mon, 6 Feb 2006 18:30:11 GMT (envelope-from gnats)
Date: Mon, 6 Feb 2006 18:30:11 GMT
Message-Id: <200602061830.k16IUBO1018493@freefall.freebsd.org>
To: freebsd-sparc64@FreeBSD.org
From: John Baldwin <jhb@freebsd.org>
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: John Baldwin <jhb@freebsd.org>
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: Mon, 06 Feb 2006 18:30:12 -0000

The following reply was made to PR sparc64/92033; it has been noted by GNATS.

From: John Baldwin <jhb@freebsd.org>
To: freebsd-sparc64@freebsd.org
Cc: Yasholomew Yashinski <yashy@mail.yashy.com>,
        Doug White <dwhite@gumbysoft.com>, freebsd-gnats-submit@freebsd.org
Subject: Re: sparc64/92033: dc(4) issues on Ultra10
Date: Mon, 6 Feb 2006 13:25:10 -0500

 On Sunday 05 February 2006 11:50, Yasholomew Yashinski wrote:
 > On Sat, 4 Feb 2006, Doug White 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?
 
 -- 
 John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
 "Power Users Use the Power to Serve"  =  http://www.FreeBSD.org