On Thu, Oct 28, 2010 at 8:20 PM, Sedat Dilek <sedat.dilek@xxxxxxxxxxxxxx> wrote: > On Thu, Oct 28, 2010 at 7:52 PM, Markus Trippelsdorf > <markus@xxxxxxxxxxxxxxx> wrote: >> On Thu, Oct 28, 2010 at 12:05:05PM +0200, Sedat Dilek wrote: >>> Hi, >>> >>> I have built today linux-next as of next-20101028 in a non-BKL config >>> (kernel-config attached) on a Debian i386/sid host. >>> >>> When I start my quassel IRC-client I get reproducibly this call-trace: >>> >>> # tail -40 kern.log >>> Oct 28 11:42:54 tbox kernel: [ Â 32.872957] EXT3-fs (sdb5): warning: >>> maximal mount count reached, running e2fsck is recommended >>> Oct 28 11:42:54 tbox kernel: [ Â 32.873621] EXT3-fs (sdb5): using >>> internal journal >>> Oct 28 11:42:54 tbox kernel: [ Â 32.873635] EXT3-fs (sdb5): mounted >>> filesystem with ordered data mode >>> Oct 28 11:44:16 tbox kernel: [ Â115.480401] ------------[ cut here ]------------ >>> Oct 28 11:44:16 tbox kernel: [ Â115.480598] kernel BUG at >>> /home/sd/src/linux-2.6/linux-2.6.36/debian/build/source_i386_none/fs/ext4/inode.c:2721! >> >> The same BUG (inode.c:2721) happend here today running latest vanilla >> git. There is nothing in my logs unfortunately, but I shot a photo of >> the trace (see attachment). >> >> -- >> Markus >> > > Looks like the two patches from ext/for_linus GIT-branch stabilzes > system, here (2.6.36-git11). > > root@tbox:~# uptime > Â20:19:42 up 19 min, Â4 users, Âload average: 1.27, 0.89, 0.58 > > - Sedat - > One minute after I sent the mail, I ran into the error. Now, I could start my IRC-client for a while... till crash. - Sedat - -- 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
