reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Marcin Baczyński" <marbacz@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: kernel BUG at fs/reiser4/block_alloc.c:151
Date: Wed, 09 Feb 2011 01:20:02 +0100	[thread overview]
Message-ID: <4D51DDB2.20605@gmail.com> (raw)
In-Reply-To: <AANLkTi=DKZfNUQDXWUNMZXBonYWTdgAr6cMtyGk12ebM@mail.gmail.com>

On 02/08/2011 11:13 PM, Marcin Baczyński wrote:
> Hi,
> I'm attaching a trace of kernel BUG that Firefox hits. It's 100% reproducible,
> every time I start the browser it hits the bug within several seconds, then
> whole system hangs. However I've never triggered the problem with any other
> application.
> I've tested 2.6.37-gentoo-hardened + reiser4 patch, and 2.6.36-zen kernels
> and both are affected.
> I'm happy to test patches or provide more info if needed.

You also can try to compile reiser4 with debugging info
and then run firefox. If some assertion is failed before
"kernel BUG at fs/reiser4/block_alloc.c:151", it would be
useful information...

Thanks,
Edward.

>
> Thanks,
> Marcin

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-02-09  0:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 22:13 kernel BUG at fs/reiser4/block_alloc.c:151 Marcin Baczyński
2011-02-08 22:36 ` Edward Shishkin
2011-02-08 23:56   ` Marcin Baczyński
2011-02-09  0:10     ` Edward Shishkin
2011-02-09  2:37       ` Edward Shishkin
2011-02-09 10:15         ` Marcin Baczyński
2011-02-09 15:14           ` Edward Shishkin
2011-02-09  0:20 ` Edward Shishkin [this message]

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=4D51DDB2.20605@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=marbacz@gmail.com \
    --cc=reiserfs-devel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).