kernel page fault with nfs
Tobias C. Berner
tcberner at gmail.com
Sat Oct 18 22:48:31 UTC 2014
Hi
World ist from october 16, installed world and kernel then.
Kernel was later rebuilt with debug-options.
Is the following more sensible?
##################################################
# kgdb NOXON/kernel.debug vmcore.1
Fatal trap 12: page fault while in kernel mode
cpuid = 5; apic id = 05
fault virtual address = 0xfffffe07d1744000
fault code = supervisor write data, page not present
instruction pointer = 0x20:0xffffffff80d4d58a
stack pointer = 0x28:0xfffffe086057f240
frame pointer = 0x28:0xfffffe086057f2f0
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 = 6524 (python2.7)
(kgdb) bt
#0 doadump (textdump=1) at pcpu.h:219
#1 0xffffffff80926b6d in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:447
#2 0xffffffff809270c0 in panic (fmt=<value optimized out>) at
/usr/src/sys/kern/kern_shutdown.c:746
#3 0xffffffff8035f167 in db_panic (addr=<value optimized out>, have_addr=2,
count=0, modif=0x0) at /usr/src/sys/ddb/db_command.c:473
#4 0xffffffff8035ed7d in db_command (cmd_table=0x0) at
/usr/src/sys/ddb/db_command.c:440
#5 0xffffffff8035eaf4 in db_command_loop () at /usr/src/sys/ddb/db_command.c:493
#6 0xffffffff80361600 in db_trap (type=<value optimized out>, code=0) at
/usr/src/sys/ddb/db_main.c:251
#7 0xffffffff80966f01 in kdb_trap (type=12, code=0, tf=<value optimized out>) at
/usr/src/sys/kern/subr_kdb.c:654
#8 0xffffffff80d4fa7c in trap_fatal (frame=0xfffffe086057f190, eva=<value optimized
out>) at /usr/src/sys/amd64/amd64/trap.c:861
#9 0xffffffff80d4fe0c in trap_pfault (frame=0xfffffe086057f190, usermode=<value
optimized out>) at /usr/src/sys/amd64/amd64/trap.c:677
#10 0xffffffff80d4f42e in trap (frame=0xfffffe086057f190) at
/usr/src/sys/amd64/amd64/trap.c:426
#11 0xffffffff80d33972 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:231
#12 0xffffffff80d4d58a in bzero () at /usr/src/sys/amd64/amd64/support.S:53
#13 0xffffffff80830463 in ncl_doio (vp=0xfffff801e7f99938, bp=0xfffffe07c5a168e8,
cr=<value optimized out>, td=<value optimized out>, called_from_strategy=<value
optimized out>)
at /usr/src/sys/fs/nfsclient/nfs_clbio.c:1648
#14 0xffffffff80831acf in ncl_write (ap=<value optimized out>) at
/usr/src/sys/fs/nfsclient/nfs_clbio.c:1124
#15 0xffffffff80e646a5 in VOP_WRITE_APV (vop=<value optimized out>, a=<value
optimized out>) at vnode_if.c:997
#16 0xffffffff809f52f9 in vn_write (fp=0xfffff80101c62780, uio=0xfffffe086057f970,
active_cred=<value optimized out>, flags=320, td=0x0) at vnode_if.h:413
#17 0xffffffff809f5602 in vn_io_fault_doio (args=<value optimized out>, uio=0xa00,
td=0x0) at /usr/src/sys/kern/vfs_vnops.c:991
#18 0xffffffff809f2aec in vn_io_fault1 () at /usr/src/sys/kern/vfs_vnops.c:1047
#19 0xffffffff809f0e3b in vn_io_fault (fp=0xfffff80101c62780, uio=0xfffffe086057f970,
active_cred=<value optimized out>, flags=0, td=0xfffff80171d79920)
at /usr/src/sys/kern/vfs_vnops.c:1152
#20 0xffffffff80982357 in dofilewrite (td=0xfffff80171d79920, fd=19,
fp=0xfffff80101c62780, auio=0xfffffe086057f970, offset=<value optimized out>,
flags=0) at file.h:306
#21 0xffffffff80982088 in kern_writev (td=0xfffff80171d79920, fd=19,
auio=0xfffffe086057f970) at /usr/src/sys/kern/sys_generic.c:467
#22 0xffffffff80982013 in sys_write (td=<value optimized out>, uap=<value
optimized out>) at /usr/src/sys/kern/sys_generic.c:382
#23 0xffffffff80d5051b in amd64_syscall (td=0xfffff80171d79920, traced=0) at
subr_syscall.c:133
#24 0xffffffff80d33c5b in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:390
#25 0x000000080137de4a in ?? ()
##################################################
Thanks in advance,
Tobias Berner
On Saturday 18 October 2014 20.43:12 Marcelo Araujo wrote:
> When you rebuild your system, did you rebuild and install all kernel and
> world?
>
> Best Regards,
>
> On Oct 18, 2014 7:57 PM, "John Baldwin" <jhb at freebsd.org> wrote:
> > On Friday, October 17, 2014 11:11:26 PM Tobias C. Berner wrote:
> > > Hi
> > >
> > >
> > > For some days now I've had problems with my current (last test with
> > > r273178M).
> > >
> > > Sometimes when accessing a nfs-share there is a pagefault:
> > >
> > >
##################################################
#####
> > > Fatal trap 12: page fault while in kernel mode
> > > cpuid = 7; apic id = 07
> > > fault virtual address = 0xfffffe07cfe60400
> > > fault code = supervisor read data, page not present
> > > instruction pointer = 0x20:0xffffffff80d4d4b6
> > > stack pointer = 0x28:0xfffffe086088b380
> > > frame pointer = 0x28:0xfffffe086088b3f0
> > > 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 = 43868 (mplayer)
> > >
> > >
> > > #0 0xffffffff80926d29 in shutdown_nice (howto=1) at
> > > /usr/src/sys/kern/kern_shutdown.c:207
> > > #1 0xffffffff80926a2d in kern_reboot (howto=260) at
> > > /usr/src/sys/kern/kern_shutdown.c:444
> > > #2 0xffffffff80926f80 in panic (fmt=0x104 <Address 0x104 out of
> >
> > bounds>) at
> >
> > > /usr/src/sys/kern/kern_shutdown.c:698
> > > #3 0xffffffff8035f147 in panic_cmd_del (arg=0x0) at
> > > /usr/src/sys/ddb/db_command.c:244
> > > #4 0xffffffff8035ed5d in db_command (cmd_table=0x0) at
> > > /usr/src/sys/ddb/db_command.c:439
> > > #5 0xffffffff8035ead4 in db_command_loop () at
> > > /usr/src/sys/ddb/db_command.c:488 #6 0xffffffff803615e0 in db_trap
> > > (type=<value optimized out>, code=0) at /usr/src/sys/ddb/db_main.c:247
> > > #7 0xffffffff80966db1 in kdb_trap (type=12, code=0,
> >
> > tf=0xfffffe086088b2d0)
More information about the freebsd-current
mailing list