Opened 11 years ago

Closed 10 years ago

#3403 closed bug (fixed)

PANIC: vm_page_fault: unhandled page fault in kernel space at 0x808046e4, ip 0x800cd1ce

Reported by: kaliber Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0x808046e4, ip 0x800cd1ce, write 0, user 0, thread 0x6a34
PANIC: vm_page_fault: unhandled page fault in kernel space at 0x808046e4, ip 0x800cd1ce

Welcome to Kernel Debugging Land...
Thread 27188 "gcc" running on CPU 0
kdebug> bt
stack trace for thread 27188 "gcc"
    kernel stack: 0x826e8000 to 0x826ec000
      user stack: 0x7efef000 to 0x7ffef000
frame               caller     <image>:function + offset
 0 826eb570 (+  48) 8005bd65   <kernel_x86>:invoke_debugger_command + 0x00f5
 1 826eb5a0 (+  64) 8005bb55   <kernel_x86> invoke_pipe_segment(debugger_command_pipe*: 0x80122a60, int32: 0, 0x0 "<NULL>") + 0x0079
 2 826eb5e0 (+  64) 8005bedc   <kernel_x86>:invoke_debugger_command_pipe + 0x009c
 3 826eb620 (+  48) 8005d464   <kernel_x86> ExpressionParser<0x826eb6d4>::_ParseCommandPipe(0x826eb6d0) + 0x0234
 4 826eb650 (+  64) 8005c89e   <kernel_x86> ExpressionParser<0x826eb6d4>::EvaluateCommand(0x801128a0 "bt", 0x826eb6d0) + 0x02ba
 5 826eb690 (+ 224) 8005e88c   <kernel_x86>:evaluate_debug_command + 0x0088
 6 826eb770 (+  64) 80059c62   <kernel_x86> kernel_debugger_loop() + 0x01ae
 7 826eb7b0 (+  32) 8005aae5   <kernel_x86>:kernel_debugger + 0x004d
 8 826eb7d0 (+ 192) 8005aa8d   <kernel_x86>:panic + 0x0029
 9 826eb890 (+  80) 800ba96d   <kernel_x86>:vm_page_fault + 0x0139
10 826eb8e0 (+  64) 800ca8cd   <kernel_x86>:page_fault_exception + 0x00d9
11 826eb920 (+  12) 800cdfb6   <kernel_x86>:int_bottom + 0x0036
kernel iframe at 0x826eb92c (end = 0x826eb97c)
 eax 0x80804000     ebx 0x1b9           ecx 0x8013164c   edx 0x3
 esi 0x80200000     edi 0x826eb9e0      ebp 0x826eb9b4   esp 0x826eb960
 eip 0x800cd1ce  eflags 0x10202    
 vector: 0xe, error code: 0x0
12 826eb92c (+ 136) 800cd1ce   <kernel_x86> query_tmap(vm_translation_map*: 0x80f8e030, uint32: 0x835b9000, 0x814ff49c, 0x826eb9e0) + 0x0076
13 826eb9b4 (+  48) 800b8139   <kernel_x86>:vm_get_page_mapping + 0x0035
14 826eb9e4 (+  64) 800cd811   <kernel_x86>:arch_vm_translation_map_init_map + 0x0191
15 826eba24 (+  64) 800bdf28   <kernel_x86>:vm_create_address_space + 0x0094
16 826eba64 (+1232) 8004e060   <kernel_x86> fork_team() + 0x01cc
17 826ebf34 (+  16) 8005068b   <kernel_x86>:_user_fork + 0x000b
18 826ebf44 (+ 100) 800ce1e2   <kernel_x86>:handle_syscall + 0x00af
user iframe at 0x826ebfa8 (end = 0x826ec000)
 eax 0x27           ebx 0x2c57f0        ecx 0x7ffeea00   edx 0xffff0104
 esi 0x0            edi 0x18018028      ebp 0x7ffeea2c   esp 0x826ebfdc
 eip 0xffff0104  eflags 0x246      user esp 0x7ffeea00
 vector: 0x63, error code: 0x0
19 826ebfa8 (+   0) ffff0104   <commpage>:commpage_syscall + 0x0004
20 7ffeea2c (+  32) 002a4b94   <libroot.so>:vfork + 0x0018
21 7ffeea4c (+  64) 0020cf59   <gcc>:pexecute + 0x00d9
22 7ffeea8c (+ 128) 0020456d   <gcc>:xstrerror (nearest) + 0x1a5d
23 7ffeeb0c (+ 112) 00207354   <gcc>:do_spec (nearest) + 0x02ec
24 7ffeeb7c (+  96) 00209234   <gcc>:do_spec (nearest) + 0x21cc
25 7ffeebdc (+ 128) 00208954   <gcc>:do_spec (nearest) + 0x18ec
26 7ffeec5c (+  96) 00209234   <gcc>:do_spec (nearest) + 0x21cc
27 7ffeecbc (+ 128) 00208954   <gcc>:do_spec (nearest) + 0x18ec
28 7ffeed3c (+  96) 00209234   <gcc>:do_spec (nearest) + 0x21cc
29 7ffeed9c (+ 128) 00208954   <gcc>:do_spec (nearest) + 0x18ec
30 7ffeee1c (+  48) 002070c4   <gcc>:do_spec + 0x005c
31 7ffeee4c (+ 304) 0020b06a   <gcc>:main + 0x176a
32 7ffeef7c (+  48) 002020bf   <gcc>:_start + 0x005b
33 7ffeefac (+  48) 0010090a   </boot/beos/system/runtime_loader@0x00100000>:unknown + 0x090a
34 7ffeefdc (+   0) 7ffeefec   1065203:gcc_main_stack@0x7efef000 + 0xffffec

Change History (2)

comment:1 by kaliber, 10 years ago

It looks like it have been fixed. I cannot reproduce it with current revision.

comment:2 by stpere, 10 years ago

Resolution: fixed
Status: newclosed

Thanks for the update! If it does reappear, don't hesitate to tell here.

Note: See TracTickets for help on using tickets.