Date: Sun, 5 Feb 2006 07:10:06 GMT From: Doug White <dwhite@gumbysoft.com> To: freebsd-sparc64@FreeBSD.org Subject: Re: sparc64/92033: dc(4) issues on Ultra10 Message-ID: <200602050710.k157A6iu082937@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR sparc64/92033; it has been noted by GNATS. From: Doug White <dwhite@gumbysoft.com> To: Yasholomew Yashinski <yashy@mail.yashy.com> 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: <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. > > #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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602050710.k157A6iu082937>