I'd assumed that this was related to the endianness fix. You're
sure you were running with that in place? If you can capture
a buffer trace that'd be great.
> On a
> related note, what does ext3 do to the disk when this happens, I
> think I need to point the yaboot author at it since it couldn't
> load a kernel (which was fun, let me tell you.. :))
ext3 is designed to nicely crash the machine if it thinks something
may be wrong with the fs - it's very defensive of your data.
If yaboot is open firmware's native ext2 capability then presumably
it refuses to read an ext3 partition which needs recovery. ext3
is designed to not be compatible with ext2 when it's in the
needs-recovery state.
Probably the simplest way to avoid this is to make the boot partition
ext2.
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/