From: Chris Mason <chris.mason@oracle.com>
To: Phillip Michael <oopsicrappe@gmail.com>
Cc: Mike Fedyk <mfedyk@mikefedyk.com>, linux-btrfs@vger.kernel.org
Subject: Re: [BUG] scheduling while atomic: init/1/0x00000002
Date: Mon, 15 Mar 2010 20:39:36 -0400 [thread overview]
Message-ID: <20100316003936.GB11905@think> (raw)
In-Reply-To: <45e1b66a1003151520k2be08f2drb976abdad1ef9006@mail.gmail.com>
On Mon, Mar 15, 2010 at 03:20:23PM -0700, Phillip Michael wrote:
> >> BUG: scheduling while atomic: init/1/0x00000002
> >> Modules linked in:
> >> Pid: 1, comm: init Not tainted 2.6.33-zen2-20100307-stable #6
> >
> > Can you reproduce this error on stock 2.6.33 without the zen patches?
> >
>
> I get the same bug on a stock archlinux 2.6.33 kernel. I have to
> finish reinstalling before I can build a vanilla kernel to try.
This definitely looks like a bad interaction between btrfs and
tux-on-ice. I'll see what I can find, but I wouldn't suspend to disk
until I get it nailed down.
-chris
prev parent reply other threads:[~2010-03-16 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 23:49 [BUG] scheduling while atomic: init/1/0x00000002 Phillip Michael
2010-03-14 6:26 ` Mike Fedyk
2010-03-15 22:20 ` Phillip Michael
2010-03-16 0:39 ` Chris Mason [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=20100316003936.GB11905@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfedyk@mikefedyk.com \
--cc=oopsicrappe@gmail.com \
/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.