Bug #2247

panic: page fault on cdb8af (vm-related)

Added by pavalos over 6 years ago. Updated over 6 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


I got the following panic on cdb8af today after about 9 hours of uptime.
Unfortunately it was unable to dump, and I had to power-cycle.

Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic->id = 00000000
fault virtual address = 0x0
fault code = supervisor read data, page not present
instruction pointer = 0x8:0xffffffff804160e4
stack pointer = 0x10:0xffffffe15b78f990
frame pointer = 0x10:0xffffffe15b78f9f8
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 0, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 38482
current thread = pri 6
trap number = 12
panic: page fault
cpuid = 0
Trace beginning at frame 0xffffffe15b78f718
panic() at panic+0x1fb
panic() at panic+0x1fb
trap_fatal() at trap_fatal+0x3d5
trap_pfault() at trap_pfault+0x1f2
trap() at trap+0x4cb
calltrap() at calltrap+0x8
--- trap 000000000000000c, rip = ffffffff804160e4, rsp = ffffffe15b78f990, rbp = ffffffe15b78f9f8 ---
vm_page_rb_tree_RB_SCAN() at vm_page_rb_tree_RB_SCAN+0xfd
pmap_object_init_pt() at pmap_object_init_pt+0xd5
vm_map_madvise() at vm_map_madvise+0x302
sys_madvise() at sys_madvise+0x63
syscall2() at syscall2+0x370
Xfast_syscall() at Xfast_syscall+0xcb
(null)() at 0x801df82cd
(null)() at 0x801ddc015
(null)() at 0x801de536e
(null)() at 0x801de8d56
(null)() at 0x801de871d
(null)() at 0x801bc7e78
(null)() at 0x800935011
(null)() at 0x8009286c4
(null)() at 0x800893878
(null)() at 0x8008932db
gd_ipending() at 0x400e54
gd_ipending() at 0x400ccd
boot() called on cpu#0
Uptime: 9h47m3s
Physical memory: 8156 MB
Dumping 2975 MB:spin_lock: 0xffffffff809d79b0, indefinite wait (1 secs)!

DragonFly 2.13-DEVELOPMENT DragonFly v2.13.0.357.gcdb8af-DEVELOPMENT #8: Tue Nov 22 19:12:52 PST 2011 :/usr/obj/usr/src/sys/YLEM64 x86_64

Any ideas?


noname (199 Bytes) noname pavalos, 11/23/2011 09:09 AM


#1 Updated by vsrinivas over 6 years ago

  • Status changed from New to Resolved

Should be fixed by 5f97768d56d8f4feadf9407630849bdd67cad2f1.

#2 Updated by pavalos over 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF