From: Mike Fedyk <mfedyk@mikefedyk.com>
To: Phillip Michael <oopsicrappe@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [BUG] scheduling while atomic: init/1/0x00000002
Date: Sat, 13 Mar 2010 22:26:01 -0800 [thread overview]
Message-ID: <93cdabd21003132226s2201c067vfdbcaad56ecffd81@mail.gmail.com> (raw)
In-Reply-To: <45e1b66a1003131549k28173905r85ab74cd870db36e@mail.gmail.com>
On Sat, Mar 13, 2010 at 3:49 PM, Phillip Michael <oopsicrappe@gmail.com=
> wrote:
> I have a btrfs filesystem with three subvolumes. One of them (named
> arch64) has 64 bit linux, one (arch32) =C2=A0has 32 bit linux, and th=
e
> third (files) has various files. After an unsuccessful tuxonice
> resume, the arch64 subvolume will no longer boot. It shows this bug:
>
> VFS: Mounted root (btrfs filesystem) readonly on device 0:13.
> Freeing unused kernel memory: 480k freed
> BFS CPU scheduler v0.315 by Con Kolivas.
> 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?
--
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
next prev parent reply other threads:[~2010-03-14 6:26 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 [this message]
2010-03-15 22:20 ` Phillip Michael
2010-03-16 0:39 ` Chris Mason
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=93cdabd21003132226s2201c067vfdbcaad56ecffd81@mail.gmail.com \
--to=mfedyk@mikefedyk.com \
--cc=linux-btrfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox