[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTikOqeT8OznyMvL7XaWS06kh7ZZ+SJLyMfOc32P4@mail.gmail.com>
Date: Thu, 28 Oct 2010 20:20:33 +0200
From: Sedat Dilek <sedat.dilek@...glemail.com>
To: Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-ext4@...r.kernel.org,
"Theodore Ts'o" <tytso@....edu>, sfr@...b.auug.org.au,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [next-20101038] Call trace in ext4
On Thu, Oct 28, 2010 at 7:52 PM, Markus Trippelsdorf
<markus@...ppelsdorf.de> 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@...x:~# uptime
20:19:42 up 19 min, 4 users, load average: 1.27, 0.89, 0.58
- Sedat -
View attachment "0001-ext4-Fix-build-when-CONFIG_EXT4_FS_XATTR.patch" of type "text/x-diff" (1312 bytes)
View attachment "0002-fs-build-fix-when-CONFIG_BLOCK.patch" of type "text/x-diff" (1405 bytes)
Powered by blists - more mailing lists