From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: sedat.dilek@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
sfr@canb.auug.org.au, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [next-20101038] Call trace in ext4
Date: Thu, 28 Oct 2010 19:52:21 +0200 [thread overview]
Message-ID: <20101028175221.GA1578@arch.trippelsdorf.de> (raw)
In-Reply-To: <AANLkTi=E_uMj_ndGU86DCjX4aDwjHqg3dkwxjQRSJtq6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
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
[-- Attachment #2: ext4bug_.jpg --]
[-- Type: image/jpeg, Size: 210266 bytes --]
next prev parent reply other threads:[~2010-10-28 17:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 10:05 Sedat Dilek
2010-10-28 10:34 ` [next-20101028] " Sedat Dilek
2010-10-28 15:08 ` Sedat Dilek
2010-10-28 15:27 ` Ted Ts'o
2010-10-28 17:52 ` Markus Trippelsdorf [this message]
2010-10-28 18:01 ` [next-20101038] " Ted Ts'o
2010-10-28 18:16 ` Eric Sandeen
2010-10-28 19:32 ` Ted Ts'o
2010-10-28 19:36 ` Eric Sandeen
2010-10-28 19:54 ` Ted Ts'o
2010-10-28 19:54 ` Sedat Dilek
2010-10-28 20:05 ` Ted Ts'o
2010-10-28 20:15 ` Sedat Dilek
2010-10-28 20:37 ` Ted Ts'o
2010-10-28 21:02 ` Sedat Dilek
2010-10-28 21:06 ` Ted Ts'o
2010-10-28 21:17 ` Sedat Dilek
2010-10-28 18:20 ` Sedat Dilek
2010-10-28 18:34 ` Sedat Dilek
2010-10-28 18:55 ` Ted Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101028175221.GA1578@arch.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=arnd@arndb.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®