Date: Mon, 6 Feb 2006 13:25:10 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-sparc64@freebsd.org Cc: freebsd-gnats-submit@freebsd.org, Yasholomew Yashinski <yashy@mail.yashy.com> Subject: Re: sparc64/92033: dc(4) issues on Ultra10 Message-ID: <200602061325.12260.jhb@freebsd.org> In-Reply-To: <20060205114452.N46628@mail.yashy.com> References: <200601200105.k0K15pBe051816@www.freebsd.org> <20060204230244.Y45494@carver.gumbysoft.com> <20060205114452.N46628@mail.yashy.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602061325.12260.jhb>