From: Maik Zumstrull <maik@zumstrull.net>
To: Ben Hutchings <ben@decadent.org.uk>
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 22:18:41 +0200 [thread overview]
Message-ID: <BANLkTikyqs0Zx-V+0+431fEAA-XWsGo73g@mail.gmail.com> (raw)
In-Reply-To: <1303762526.3032.296.camel@localhost>
On Mon, Apr 25, 2011 at 22:15, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Mon, 2011-04-25 at 22:05 +0200, Maik Zumstrull wrote:
>> 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?
Not that I've noticed. I don't use that netbook much, but given how
quickly it happens with .39, I say I would have noticed.
>> 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.
I thought as much, but other than taking a picture of the screen, I
don't know how. I am prepared to cooperate fully in the debugging
effort, though. :-) You or they can tell me what is required.
next prev parent reply other threads:[~2011-04-25 20:18 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 [this message]
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=BANLkTikyqs0Zx-V+0+431fEAA-XWsGo73g@mail.gmail.com \
--to=maik@zumstrull.net \
--cc=624131@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=linux-btrfs@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).