From: Ben Hutchings <ben@decadent.org.uk>
To: Chris Mason <chris.mason@oracle.com>
Cc: Maik Zumstrull <maik@zumstrull.net>,
624131@bugs.debian.org, linux-btrfs@vger.kernel.org,
cwillu <cwillu@cwillu.com>
Subject: Re: Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code
Date: Tue, 26 Apr 2011 04:59:03 +0100 [thread overview]
Message-ID: <1303790343.3032.352.camel@localhost> (raw)
In-Reply-To: <BANLkTi=VMW1bsOduH2Xn27NUQkpHiHngqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Mon, 2011-04-25 at 15:05 -0600, cwillu wrote:
> On Mon, Apr 25, 2011 at 2:50 PM, Peter Stuge <peter@stuge.se> wrote:
> > Maik Zumstrull wrote:
> >> >> Bug at fs/btrfs/free-space-cache.c:1246
> >> >> Bug type: invalid opcode: 0000
> >> >> Kernel not tainted, running on an ASUSTek 1005HAG
> >> >> EIP is at btrfs_add_free_space+0x285/0x39a [btrfs]
> >> >
> >> > You will probably need to provide a more complete copy of the panic
> >> > message.
> >>
> >> I thought as much, but other than taking a picture of the screen, I
> >> don't know how.
> >
> > Take a picture and ideally transcribe it after reboot.
>
> Known issue; josef sent a patch
> (http://permalink.gmane.org/gmane.comp.file-systems.btrfs/10261) that
> should fix it, or you can mount with clear_cache on each boot as a
> workaround.
This fix doesn't seem to be in your for-linux branch yet. Please can
you ensure that this (or an alternate fix) is included in 2.6.39.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2011-04-26 3:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikiVMbH0BU4xTZirNDUu=GhG0ooyg@mail.gmail.com>
2011-04-25 20:15 ` Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code Ben Hutchings
2011-04-25 20:18 ` Maik Zumstrull
2011-04-25 20:50 ` Peter Stuge
2011-04-25 21:05 ` cwillu
2011-04-26 3:59 ` Ben Hutchings [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=1303790343.3032.352.camel@localhost \
--to=ben@decadent.org.uk \
--cc=624131@bugs.debian.org \
--cc=chris.mason@oracle.com \
--cc=cwillu@cwillu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=maik@zumstrull.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.