Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Arne Jansen <sensille@gmx.net>
To: "Jérôme Poulin" <jeromepoulin@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Kernel panic when scrub is used
Date: Mon, 18 Feb 2013 19:04:57 +0100	[thread overview]
Message-ID: <51226D49.2070705@gmx.net> (raw)
In-Reply-To: <CALJXSJpEVB6vESOQmpLfBkHYSqxU0quhByYGSJqgUR5SVY6Shw@mail.gmail.com>

On 02/18/13 18:53, Jérôme Poulin wrote:
> Here you go, I also added 2 other screenshots of the same problem.
> http://tinypic.com/r/5ckgug/6
> http://tinypic.com/r/t0i9t4/6
> http://tinypic.com/r/2r3xdvl/6

do you have any idea how I can reproduce it here?

-Arne

> 
> On Mon, Feb 18, 2013 at 12:37 PM, Arne Jansen <lists@die-jansens.de> wrote:
>> On 02/18/13 18:14, Jérôme Poulin wrote:
>>> I experience a kernel panic with "General protection fault" when doing
>>> a scrub on Kernel 3.8-rc7.
>>>
>>> Here is a screenshot: http://tinypic.com/r/34r6nad/6
>>
>> I'd love to see the first stacktrace...
>>
>>>
>>> The weird part is that the scrub completes from initramfs, but when
>>> system is fully booted, is kernel panics every time in the low
>>> percentage. (<10%)
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>


  reply	other threads:[~2013-02-18 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 17:14 Kernel panic when scrub is used Jérôme Poulin
2013-02-18 17:37 ` Arne Jansen
2013-02-18 17:53   ` Jérôme Poulin
2013-02-18 18:04     ` Arne Jansen [this message]
2013-02-20 13:11     ` David Sterba
2013-02-20 18:42       ` Jérôme Poulin
2013-02-20 20:38         ` Jérôme Poulin

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=51226D49.2070705@gmx.net \
    --to=sensille@gmx.net \
    --cc=jeromepoulin@gmail.com \
    --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