Hi
Back in OpenBSD 4.0 I got the error below regarding a uvm_fualt.
According to the cvs logs in pmap.c the bug was not occuring in OpenBSD
4.1 due to some code being reverted, so we switched to that. It seemed
to corret the problem until just the other day. I had a computer
constantly rebooting all night, and on one of the shutdowns I got the error.
I noticed that there is a lot of changes going on in pmap.c since 4.1
and I was wondering on the status of this error? Has it actually been
fixed yet? If it has not, is there anything I can do to help? I have a
few dual and quad core machines I could use to test any changes.
Thanks
Jonathan Steel
uvm_fault(0x..., 0x..., 0, 1) -> e
kernel: page fault trap, code = 0
stopped at pmap_page_remove_86+0x114:
0(%eax, %edx, 4), %eax
The trace output is:
pmap_page_remove_86(d0d31420,c0,e9b57e2c,d04adeb9,e99f) at
pmap_page_remove_86+0x114
uvm_vnp_terminate(d8034e04,0,0,0,0,14,0,d7e95004) at uvm_vnpterminate+0x31f
uvm_attach(d8034e04,0,2,0,d7f38378) at uvn_attach+0x2b5
uvm_unmap_detach(d7e959a4,0,d7f3841c,1) at uvm_unmap_detach+-x62
uvmspace_free(d7f38378,6,d08120e0) at uvmspace_free+0xfd
uvm_exit(d7fbb868,14,8,286) at uvm_exit+0x19
reaper(d80df430) at reaper+0x90
Bad frame pointer: 0xd0913eb8
