On Sat, 2009-06-06 at 15:29 +0100, David Woodhouse wrote:
You could also try using kexec -- that should help eliminate yaboot
bugs too.
Booting with kexec (after rebuilding it because for some reason we're
shipping a ppc32-capable kexec again, gr) shows that the corruption has
gone away:
Instruction dump:
fbbd0000 fbbd0008 48224d75 60000000 eb9e8000 7f83e378 48227829 60000000
<7fa3eb78> e89c0020 38bc0018 4beecb21 60000000 7f83e378 4822715d 60000000
38600000 383f0090 e8010010 7c0803a6 eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8
I had been seeing it before:
fbbd0000 fbbd0008 48224d75 60000000 eb9e8000 7f83e378 48227829 60000000
<00001010> 00000008 00001013 0000000f 7961626f 6f740000 00101600 00000c00
00000200 00101100 00000810 7c0803a6 eb81ffe0 eba1ffe8 ebc1fff0 ebe1fff8
I blame yaboot...
--
David Woodhouse Open Source Technology Centre
David.Woodhouse(a)intel.com Intel Corporation