On Tue, Mar 4, 2008 at 12:41 PM, Jiri Slaby <jirislaby@xxxxxxxxx> wrote: > >> while booting up a notebook on 32 bit, this oopses appeared on the console > >> after ext3 fsck: > >> http://www.fi.muni.cz/~xslaby/sklad/mem_oops/ > >> > >> It's 2.6.25-rc2-mm1, I can't find similar reports, is this known or hardware > >> issue (unlikely, 2.6.24.2 seems to be OK)? > > > > I don't recall seeing a similar report and yes, it'll be a kernel bug. > > > > We've fixed a few things and it could be that this will just go away in > > next -mm. If it doesn't, a bisection search would be good, thanks. > > Well, next -mm is out. Could you test, Jan? [our -mm git is up-to-date] I don't see your config but if you have CONFIG_SLUB enabled, this is probably the same problem as: http://bugzilla.kernel.org/show_bug.cgi?id=10015 which is fixed since 2.6.25-rc2 in mainline. Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
