This looks like a traditional one-bit memory error - either in cache or
in main memory. It should probably be all zero's (meaning "no page
directory" which is pretty normal ), but it has gotten corrupted, so..
> The message that I saw that got me to write this email (reformatted):
>
> EXT2-fs error (device 08:01): ext2_find_entry: bad entry in directory
> #101620: inode out of bounds - offset=12 inode=4194306, rec_len=12,
> name_len=2
The inode number is 4194306 = 0x00400002. Again, it looks like it should
probably be just a plain "2" which is the normal ext2 root inode number,
but something corrupted it and set one bit in the number (note how it's
the same 00400000 bit again..)
Linus