I've been having a similar problem with my new install on a 50 MHz 486DX
with 8M of RAM. On my machine, however, the problem seems intermittent
but often appears when I'm prompted for a terminal type just after login
as root. When I enter a selection, be it the default or otherwise, it
crashes and kicks me into the ddb> prompt. It has also done this at
some point during the night when I had sucessfully logged in and left
the machine running overnight so it must have been trigger by some cron
One big question I have: how did you get the output of that trace
command to a file? I have run it and it gives me a sceenful so I don't
feel inclined to retype it into this posting. Any help would be
appreciated. At this point I think I'll pull all of the memory and
other cards and give the machine a good vacumming inside to hopefully
remove some of the dust as it has been sitting idle for some years.
Thanks in advance.
> > Try typing "trace" next time you are thrown out to the "ddb>" prompt
> > we get more info on this crash.
> i did...
> vm_fault(0xe0b78f00, dead0000, 3, 0) -> 5
> kernel: page fault trap, code=0
> Stopped at _vm_page_insert+0x94: movl %ebx,0(%eax)
> ddb> trace
> _vm_page_insert(e055e470,e0b76200,1a000,e021e68c,e055e470) at
> _vm_page_rename(e055e470,e0b76200,1a000,1) at _vm_page_rename+0x29
> _vm_object_overlay(e0b76200,20,e0a96e00,ffffffff,e0b76200) at
> _vm_object_collapse_internal(e0b76200,e2ae3e78,e022ce85) at
> _vm_object_deallocate(0,e0b66a00,e0b62600,79000) at
Quote:> _vm_map_delete(e0b78f00,0,dfbfe000,e0b78800,e0b78f00) at
Quote:> _vm_map_remove(e0b78f00,0,dfbfe000,e2ae3f38) at _vm_map_remove+0x65
> _exit1(e0b78800,0,4776c,5,e0b6e500) at _exit1+0x104
> _sys_exit(e0b78800,e2ae3f88,e2ae3f80,e022ebd8,0) at _sys_exit+0x1a
> _syscall() at _syscall+0x242
> --- syscall (number 1) ---
Sent via Deja.com http://www.deja.com/
Before you buy.