Segfault Suggestions?

Taavi Burns taavi-LbuTpDkqzNzXI80/IeQp7B2eb7JE58TQ at public.gmane.org
Tue Mar 2 15:09:36 UTC 2004


On Tue, Mar 02, 2004 at 09:44:41AM -0500, Peter King wrote:
> Test 57, 1000 Lucas-Lehmer iterations of M225281 using 12k FFT length
>   Unable to handle kernel paging request at virtual address fffffffe
>   printing eip:
>    c82c986c
>  *pde=00002063
>  *pte=00000000
>  Oops: 0002
> <snip>
>  kernel panic: Aieee, killing interrupt handler!
> 
> Well, this is all very exciting. It looks like the Dell went down due
> to a kernel paging request -- which means, I think, that the kernel
> asked for some memory that it expected to have, and the Dell did not
> provide it. That provides good reasons for suspecting the memory rather
> than the CPU.
> 
> Is that the right way to read the information? If not, what does it mean?

That address looks mighty fishy, but then again I have no idea what a Linux
process sees at the top end of its address space.  It's as fishy in my mind as
seeing a request for memory at 0x00000000.

That being said...it could be the CPU (the MMU or just the CPU in general).
It could be the cache (you can try turning the L1 and L2 caches off in the
BIOS and see if the machine becomes stable; it's worked for me).  It could
be the RAM (despite memtest86; fail means fail, pass means it didn't fail, not
that it's good).  It could be the HD (was the HD involved by providing swap
space?).

-- 
taa

   It is better to copulate than never.
      - Robert A. Heinlein
/*eof*/
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list