From: "Carlos R. Mafra" <crmafra2@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: 2.6.33-rc2+ bug in fs/btrfs/ordered-data.c:672
Date: Sat, 2 Jan 2010 11:32:27 +0100 [thread overview]
Message-ID: <20100102103227.GA3678@Pilar.aei.mpg.de> (raw)
I started testing btrfs for my /home a few days ago and yesterday
I hit a kernel bug, using 2.6.33-rc2-00187-g08d869a.
I wasn't doing any stress test with it, I was simply watching a
DVD with xine while chrome was open in another workspace.
I noticed the kernel bug when the movie was over and I typed
'echo mem > /sys/power/state' to go to sleep but it got stuck,
so I checked what was happening in dmesg and I saw the bug in there.
By looking at the printk timings the bug was there for ~16 minutes, so
that last suspend to RAM atempt was not guilty in this bug. However,
the laptop was turned on for some hours already and had already passed
through a few suspend to RAM in this period.
I tried to save the dmesg but it failed writing, so I took a picture
of the bug trace
http://www.aei.mpg.de/~crmafra/btrfs_bug.jpg
Some info about my laptop is in this dmesg from this morning
http://www.aei.mpg.de/~crmafra/dmesg-2.6.33-rc2.txt
I hope this helps.
next reply other threads:[~2010-01-02 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 10:32 Carlos R. Mafra [this message]
2010-01-02 22:34 ` 2.6.33-rc2+ bug in fs/btrfs/ordered-data.c:672 Carlos R. Mafra
2010-01-04 0:22 ` Johannes Hirte
2010-01-04 4:20 ` Yan, Zheng
2010-01-04 9:35 ` Carlos R. Mafra
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=20100102103227.GA3678@Pilar.aei.mpg.de \
--to=crmafra2@gmail.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@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