Subject: Re: UVM and top
To: Markus Baeurle <emw4maba@gp.fht-esslingen.de>
From: Mark Brinicombe <amb@causality.com>
List: port-arm32
Date: 07/22/1998 20:30:59
On Wed, 22 Jul 1998, Markus Baeurle wrote:

> First one:
> Failed page fault in kernel
> [u]vm_fault(0xf00f7f50, f22b0000, 1, 0) -> 2
> panic: Halting (frame=0xf2a47e30)
> 
> Traceback (I just write the number in brackets and omit the repeated name of
> the function):
> _Debugger(0x10)
> _panic(0x14)
> _data_abort_handler(0x10)
> _amap_wipeout(0x10)
> _amap_unref(0x10)
> _uvm_unmap_detach(0x10)
> _uvm_unmap(0x10)
> _uvm_deallocate(0x10)
> _exit1(0x10)
> _sys_exit(0x10)
> _syscall(0x10)

Nothing springs to mind immediately about this one but Neil and myself
will look into it.

> Second (and more frequent) one:
> Data abort: Translation fault (section) status=005, addr=400000, PC=f0098250
> Section fault in SVC mode
> [u]vm_fault(0xf1251f00,400000,1,0) -> 1
>             ^^^^differs
> panic: Halting (frame=0xf2a2cd9c) <- always the same
> 
> Traceback:
> _Debugger(0x10)
> _panic(0x14)
> _data_abort_handler(0x10)
> _amap_copy(0x10)
> _udv_attach(0x604)
> _uvm_fault(0x10)
> _data_abort_handler(0x10)
> 
> Hope you have an idea what the problem could be.
What is happening here is clearer though the cause needs to be looked at.
The fault address is significant. The level 2 page table for the VA
address range 4MB->8MB is missing. thus causing the fault.

Cheers,
				Mark