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 | #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.
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
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
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
John Baldwin 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? http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html I've added: options DDB to my kernel. When I try "boot -d" it just brings me up to a standard login prompt. So I tried option two: # sysctl debug.enter_debugger=ddb sysctl: unknown oid 'debug.enter_debugger' at which point I went to the console and tried CTRL+ALT+ESC, in which case the kernel appeared to core and the system rebooted. However it's not recognized by gdb: This GDB was configured as "sparc64-marcel-freebsd"... "/var/crash/vmcore.8" is not a core dump: File format not recognized while on this topic (the next page in the handbook): # gdb -k /usr/obj/usr/src/sys/COLONEL/kernel gdb: unrecognized option `-k' Use `gdb --help' for a complete list of options. Thanks in Advance, -- Yashy
State Changed From-To: open->feedback
State Changed From-To: feedback->closed Feedback timeout (>1 month)