"panic: trap: fast data access mmu miss" on 5.2-C
kris at obsecurity.org
Thu Feb 5 09:10:36 PST 2004
On Thu, Feb 05, 2004 at 03:35:36PM +0100, Thomas Moestl wrote:
> On Thu, 2004/02/05 at 00:54:09 -0800, Kris Kennaway wrote:
> > On Sun, Feb 01, 2004 at 05:49:50PM +0100, Thomas Moestl wrote:
> > > Looks like the back trace ran off the end of the stack;
> > > db_stack_trace_cmd() only handles the usual starting points of kernel
> > > stacks (traps from userland), but not freshly forked processes (or
> > > kernel threads). The attached patch should fix that by initializing
> > > the fr_pc and fr_fp fields of the first frame to 0 in cpu_fork().
> Did you get a witness backtrace ending in fork_trampoline() since?
I just checked, and one occurred overnight without panicking.
> > I'm getting another panic with this patch (transcribed manually):
> > fast data access mmu miss tar=0 %o7=0xc0114a0c
> > copyin+0x5c
> > pipe_write+0x568
> > dofilewrite+0xec
> > write+0x3c
> > syscall+0x314
> Is it possible that this is caused by the bug which rwatson fixed in
> r1.166 of sys/sys_pipe.c (i.e. do you have r1.165 of that file)?
Oops, you're right. I thought I had CVS updated again to rule this out.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-sparc64/attachments/20040205/daad86cd/attachment-0001.bin
More information about the freebsd-sparc64