(unknown charset) Re: panic: vm_fault: fault on nofault entry, addr: fffffe0007e8e000

Kris Kennaway wrote:
> 
> On Thu, Jul 31, 2003 at 08:04:11PM -0700, Kris Kennaway wrote:
> > On Thu, Jul 31, 2003 at 01:48:42PM -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
> >
> > > Two more panics on alpha:
> > >
> > > panic: vm_fault: fault on nofault entry, addr: fffffe0007fde000
> >
> > > fatal kernel trap:
> > >
> > >     trap entry     = 0x2 (memory management fault)
> >
> > I'm also seeing a lot of random corruption going on on the alpha
> > machines (these packages build successfully if I retry):
> 
> Another one:
> 
> panic: vm_fault: fault on nofault entry, addr: fffffe0007fbe000
> 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() at bcopy+0x14
> 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 ---
> 

Could you please do an objdump -d on sys_pipe.o (or similar) to verify
that pipe_read+0x290 is the second call to uiomove() in pipe_read()?

Alan