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

From: Kris Kennaway <kris_at_obsecurity.org>
Date: Thu, 31 Jul 2003 20:04:11 -0700
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):

----
(cd . && ln -s  )
usage: ln [-fhinsv] file1 file2
       ln [-fhinsv] file ... directory
       link file1 file2
*** Error code 1
----

----
bzip2: I/O or other error, bailing out.  Possible reason follows.
bzip2: Bad address
	Input file = (stdin), output file = (stdout)
----
cc1plus
:

Bad

address
:

error

writing

to

-
*** Error code 1
----

Something funny is definitely going on.  The alpha machines were not
running with witness, but I have just upgraded the i386 package
machines (which do have witness) to try and reproduce it there.

Kris

Received on Thu Jul 31 2003 - 18:04:13 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:17 UTC