Fatal trap 12 in exec_copyout_strings()
John Baldwin
jhb at FreeBSD.org
Fri Jun 17 19:20:44 GMT 2005
On Sunday 29 May 2005 01:50 pm, Kris Kennaway wrote:
> On Tue, May 10, 2005 at 03:36:36PM -0700, Kris Kennaway wrote:
> > Got this on a dual amd64 with 8GB RAM running 6.0 from last week:
> >
> > Fatal trap 12: page fault while in kernel mode
> > cpuid = 1; apic id = 01
> > fault virtual address = 0xffffffffa9cdc000
> > fault code = supervisor read, page not present
> > instruction pointer = 0x8:0xffffffff8037759f
> > stack pointer = 0x10:0xffffffffba1637d0
> > frame pointer = 0x10:0xffffffffba163820
> > code segment = base 0x0, limit 0xfffff, type 0x1b
> > = DPL 0, pres 1, long 1, def32 0, gran 1
> > processor eflags = interrupt enabled, resume, IOPL = 0
> > current process = 52247 (sh)
> > [thread pid 52247 tid 100149 ]
> > Stopped at exec_copyout_strings+0x12f:
> > db> wh
> > Tracing pid 52247 tid 100149 td 0xffffff016e5724c0
> > exec_copyout_strings() at exec_copyout_strings+0x12f
> > do_execve() at do_execve+0x39a
> > kern_execve() at kern_execve+0xab
> > execve() at execve+0x49
> > syscall() at syscall+0x382
> > Xfast_syscall() at Xfast_syscall+0xa8
> > --- syscall (59, FreeBSD ELF64, execve), rip = 0x80090622c, rsp =
> > 0x7fffffffe058, rbp = 0xffffffff --- db>
>
> I've got this panic twice more since.
Do you have a kernel.debug? Can you do 'list *exec_copyout_strings+0x12f'? I
think I've seen reports of the linux32_exec_copyout_strings() having a
similar fault as well on amd64.
--
John Baldwin <jhb at FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
More information about the freebsd-amd64
mailing list