From owner-freebsd-sparc64@FreeBSD.ORG  Sun Feb  5 16:48:14 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 BBCD116A422;
	Sun,  5 Feb 2006 16:48:14 +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 8AEDD43D5E;
	Sun,  5 Feb 2006 16:48:08 +0000 (GMT)
	(envelope-from yashy@mail.yashy.com)
Received: by mail.yashy.com (Postfix, from userid 1001)
	id 9C87D65DD; Sun,  5 Feb 2006 11:50:36 -0500 (EST)
Received: from localhost (localhost [127.0.0.1])
	by mail.yashy.com (Postfix) with ESMTP id 5D92865DC;
	Sun,  5 Feb 2006 11:50:36 -0500 (EST)
Date: Sun, 5 Feb 2006 11:50:36 -0500 (EST)
From: Yasholomew Yashinski <yashy@mail.yashy.com>
To: Doug White <dwhite@gumbysoft.com>
In-Reply-To: <20060204230244.Y45494@carver.gumbysoft.com>
Message-ID: <20060205114452.N46628@mail.yashy.com>
References: <200601200105.k0K15pBe051816@www.freebsd.org>
	<20060204230244.Y45494@carver.gumbysoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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: Sun, 05 Feb 2006 16:48:14 -0000

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.

>> #0  doadump () at /usr/src/sys/kern/kern_shutdown.c:233
>> 233             savectx(&dumppcb);
>> (kgdb) bt
>> #0  doadump () at /usr/src/sys/kern/kern_shutdown.c:233
>> #1  0x00000000c011ef68 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
>> #2  0x00000000c011f2f4 in panic (fmt=0xc0303880 "trap: %s") at /usr/src/sys/kern/kern_shutdown.c:555
>> #3  0x00000000c02c1de4 in trap (tf=0xd1a9b220) at /usr/src/sys/sparc64/sparc64/trap.c:369
>> #4  0x00000000c0048fc0 in tl1_trap ()
>> #5  0x00000000c00ac1f4 in dcphy_status (sc=0xfffff800006f1980) at cpufunc.h:104
>> #6  0x00000000c00ac178 in dcphy_service (sc=0xc00ac1f8, mii=0x0, cmd=0) at /usr/src/sys/dev/mii/dcphy.c:332
>> #7  0x00000000c00ac178 in dcphy_service (sc=0xfffff800006f1980, mii=0xfffff80000734200, cmd=1) at /usr/src/sys/dev/mii/dcphy.c:332
>> #8  0x00000000c00af5c4 in mii_tick (mii=0xfffff80000734200) at /usr/src/sys/dev/mii/mii.c:363
>> #9  0x00000000c0444ab0 in ?? ()
>> Previous frame identical to this frame (corrupt stack?)
>> (kgdb)
>>> How-To-Repeat:
>> Turn machine on with a call to the card. In this case, I had added
>> ifconfig_dc0="DHCP" to rc.conf. The crash happens before the card actually gets an IP.

  Thanks in Advance,

--
Yashy