Description of problem:
Kernel panic. See attached photograph. This might very well be related to i686
weirdness as described in bug 200330. My guess right now is binutils weirdness
breaking i686 for the AMD Geode.
Version-Release number of selected component (if applicable):
Run some file system intensive code like 'yum -y install wget'. Reproducible on
build45 on OLPC available here
bunzip2 the image, dd it to a USB stick (e.g. /dev/sda) with at least 512MB of
space and boot it on a OLPC developer boards. We have one such board in the
Created attachment 133158 [details]
photograph of panic
Doesn't appear to be related. The code at the crash point is:
c04748d4: e8 be f7 ff ff call c0474097 <unmap_underlying_metadata>
c04748d9: 8b 5b 04 mov 0x4(%ebx),%ebx <=== crashes here
I'd guess that %ebx ended up with an invalid address, for whatever reason.
Without the top of the Oops, it's hard to tell more. It's definitely not an
It might actually have to do with i686 instructions, though, if some replacement
chunk of code for instructions missing on the Geode turn out to corrupt %ebx or
whatever memory slot it happened to be preserved in by the callee.
Do we still see this panic after the rebuild with the new binutils?
No, this seems to be fixed. Closing. Thanks.