From owner-freebsd-sparc64@FreeBSD.ORG Sun Feb 5 07:10:07 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 51AEF16A420 for ; Sun, 5 Feb 2006 07:10:07 +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 E12C343D48 for ; Sun, 5 Feb 2006 07:10:06 +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 k157A64N082938 for ; Sun, 5 Feb 2006 07:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k157A6iu082937; Sun, 5 Feb 2006 07:10:06 GMT (envelope-from gnats) Date: Sun, 5 Feb 2006 07:10:06 GMT Message-Id: <200602050710.k157A6iu082937@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Doug White 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: Doug White List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2006 07:10:07 -0000 The following reply was made to PR sparc64/92033; it has been noted by GNATS. From: Doug White To: Yasholomew Yashinski Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-sparc64@FreeBSD.org Subject: Re: sparc64/92033: dc(4) issues on Ultra10 Date: Sat, 4 Feb 2006 23:03:45 -0800 (PST) On Fri, 20 Jan 2006, Yasholomew Yashinski 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. > > #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. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org