Re: Cannot boot any HIGHMEM kernel (kernel panic - not syncing)

[Andi Kleen]

Michael ElsdÃrfer wrote:
>>> Now, Machine Check Exception seems to point towards a hardware error,
>>
>> It not only seems to, it does.
>> The non highmem kernel will simply not use most of your memory, so if
>> the machine check happens accessing memory you will not see it.
> 
> Thanks Andi.
> 
> So the problem would be defective RAM in the machine?
> 
> I'm still wondering though while the previous kernel (a self-compiled
> 2.6.17.11) worked then. Laxer checks?

Memory access patterns change between kernels. Likely if you had filled
your memory with some program you would have seen it too.

I always use ftp://ftp.firstfloor.org/pub/ak/memeat.c for testing for
such problems. It simply allocates all free memory and reads and writes
it in a loop.


-Andi


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/