Re: panic: vm_fault: fault on nofault entry, addr: fffffe0007e8e000

On Thu, Jul 31, 2003 at 01:48:59AM -0700, Kris Kennaway wrote:
> I upgraded the alpha package machines tonight, and one of them fell
> over shortly after taking load, with the following:
> 
> panic: vm_fault: fault on nofault entry, addr: fffffe0007e8e000
> Stack backtrace:
> db_print_backtrace() at db_print_backtrace+0x18
> backtrace() at backtrace+0x2c
> panic() at panic+0x148
> vm_fault() at vm_fault+0x1360
> trap() at trap+0x5c8
> XentMM() at XentMM+0x2c
> --- memory management fault (from ipl 0) ---
> bcopy_samealign_lp() at bcopy_samealign_lp
> cpu_fork() at cpu_fork+0x12c
> vm_forkproc() at vm_forkproc+0x204
> fork1() at fork1+0xfec
> vfork() at vfork+0x30
> syscall() at syscall+0x33c
> XentSys() at XentSys+0x64
> --- syscall (66) ---
> --- user mode ---

Two more panics on alpha:

panic: vm_fault: fault on nofault entry, addr: fffffe0007fde000
Debugger() at Debugger+0x38
panic() at panic+0x168
vm_fault() at vm_fault+0x1360
trap() at trap+0x5c8
XentMM() at XentMM+0x2c
--- memory management fault (from ipl 0) ---
bcopy_samealign_lp() at bcopy_samealign_lp+0x8
copyout() at copyout+0x38
uiomove() at uiomove+0x19c
pipe_read() at pipe_read+0x290
dofileread() at dofileread+0x100
read() at read+0x64
syscall() at syscall+0x33c
XentSys() at XentSys+0x64
--- syscall (3, FreeBSD ELF64, read) ---
--- user mode ---
db>

fatal kernel trap:

    trap entry     = 0x2 (memory management fault)
    faulting va    = 0xfffffe0007f9c088
    type           = access violation
    cause          = load instructon
    pc             = 0xfffffc000045570c
    ra             = 0xfffffc0000455700
    sp             = 0xfffffe0008021ce0
    usp            = 0x11ffccd8
    curthread      = 0xfffffc00014e84c0
        pid = 4214, comm = bzip2

Stopped at      ast+0x3ec:      ldq     t0,0x88(t1) <0xfffffe0007f9c088>        <t0=0xcfa0,t1=0xfffffe0007f9c00>