On Friday 02 December 2005 6:41 pm, Chris wrote: > Had this waiting for me when I got home from work today. > > Dec 2 17:01:00 cpollock kernel: CPU 0: Machine Check Exception: > 0000000000000004 > Dec 2 17:01:00 cpollock kernel: Bank 2: f60020000000017a at > 0000000000148000 > Dec 2 17:01:00 cpollock kernel: Kernel panic: CPU context corrupt > > The one below is a panic I had back in May, looks pretty much the same > which turned out to be memory. Stupid question though, the Bank 2 that > is referenced, its apparently not memory bank 2 since I left it empty and > put modules in 1 and 3. So, just what does the "Bank 2" thats mentioned > mean? > > 11:15:02 cpollock kernel: CPU 0: Machine Check Exception: > 0000000000000004 May 26 11:15:02 cpollock kernel: Bank 2: > f60020000000017a at > 0000000000364000 > May 26 11:15:02 cpollock kernel: Kernel panic: CPU context corrupt > > Looks like I'll be picking up more memory tomorrow.
I'll reply to my own msg here, when memtest86 goes to run the "block move" test, instant reboot. Looks like it is memory for sure. -- Chris Registered Linux User 283774 http://counter.li.org 20:00:18 up 2 min, 1 user, load average: 1.45, 0.90, 0.36 Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "No" simply means begin again at one level higher -- Anti- Murphy's Laws n°13 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
pgpkhg17IPm5K.pgp
Description: PGP signature
____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
