Your message dated Fri, 13 May 2011 05:07:42 +0100 with message-id <1305259662.4065.406.camel@localhost> and subject line Re: Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code has caused the Debian Bug report #624131, regarding linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 624131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624131 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code
- From: Maik Zumstrull <maik@zumstrull.net>
- Date: Mon, 25 Apr 2011 22:05:53 +0200
- Message-id: <BANLkTikiVMbH0BU4xTZirNDUu=GhG0ooyg@mail.gmail.com>
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. 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]
--- End Message ---
--- Begin Message ---
- To: Maik Zumstrull <maik@zumstrull.net>
- Cc: 624131-done@bugs.debian.org
- Subject: Re: Bug#624131: linux-image-2.6.39-rc4-686-pae: Can somewhat reliably produce kernel panic in btrfs code
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Fri, 13 May 2011 05:07:42 +0100
- Message-id: <1305259662.4065.406.camel@localhost>
- In-reply-to: <BANLkTikG6gaBxKqEAo3xAyxn7=itiksuZA@mail.gmail.com>
- References: <BANLkTikiVMbH0BU4xTZirNDUu=GhG0ooyg@mail.gmail.com> <1303762526.3032.296.camel@localhost> <BANLkTikyqs0Zx-V+0+431fEAA-XWsGo73g@mail.gmail.com> <20110425205008.11135.qmail@stuge.se> <BANLkTi=VMW1bsOduH2Xn27NUQkpHiHngqw@mail.gmail.com> <1303790343.3032.352.camel@localhost> <BANLkTikG6gaBxKqEAo3xAyxn7=itiksuZA@mail.gmail.com>
Version: 2.6.39~rc5-1~experimental.1 On Thu, 2011-05-12 at 14:00 +0200, Maik Zumstrull wrote: > On Tue, Apr 26, 2011 at 05:59, Ben Hutchings <ben@decadent.org.uk> wrote: > > > 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. > > It seems to be in. I also haven't noticed panics with rc5/rc6. Just in > case you want to close this one. Thanks for letting us know. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---