[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101028175221.GA1578@arch.trippelsdorf.de>
Date: Thu, 28 Oct 2010 19:52:21 +0200
From: Markus Trippelsdorf <markus@...ppelsdorf.de>
To: sedat.dilek@...il.com
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 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
Download attachment "ext4bug_.jpg" of type "image/jpeg" (210266 bytes)
Powered by blists - more mailing lists