From: Ben Hutchings <ben@decadent.org.uk>
To: Maik Zumstrull <maik@zumstrull.net>
Cc: 624131@bugs.debian.org, linux-btrfs@vger.kernel.org
Subject: Re: Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code
Date: Mon, 25 Apr 2011 21:15:26 +0100 [thread overview]
Message-ID: <1303762526.3032.296.camel@localhost> (raw)
In-Reply-To: <BANLkTikiVMbH0BU4xTZirNDUu=GhG0ooyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Mon, 2011-04-25 at 22:05 +0200, Maik Zumstrull wrote:
> Package: linux-image-2.6.39-rc4-686-pae
> Version: 2.6.39~rc4-1~experimental.1
> Severity: normal
> Tags: experimental
>
> By simply stressing the system with some I/O, I can make it crash within
> seconds. I'm not setting a higher severity because the bug is in an
> experimental file system in an experimental kernel.
I assume this doesn't happen in 2.6.38?
> Here's the important bits (by my guess) I have on screen from the kernel panic:
>
> 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. Let's see what the btrfs developers say.
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 --]
next parent reply other threads:[~2011-04-25 20:15 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 ` Ben Hutchings [this message]
2011-04-25 20:18 ` Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code Maik Zumstrull
2011-04-25 20:50 ` Peter Stuge
2011-04-25 21:05 ` cwillu
2011-04-26 3:59 ` Ben Hutchings
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=1303762526.3032.296.camel@localhost \
--to=ben@decadent.org.uk \
--cc=624131@bugs.debian.org \
--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 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).