From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs panic in 3.5.0
Date: Tue, 7 Aug 2012 10:40:47 -0700 [thread overview]
Message-ID: <20120807174047.GE24635@merlins.org> (raw)
Unfortunately I only have a screenshot.
Apparently the panic was in
btrfs_set_lock_blocking_rw
with a RIP in btrfs_cow_block
Screenshot here:
http://marc.merlins.org/tmp/btrfs_oops.jpg
Because the display looks a bit messed up, I can't tell if the ata error
happened before or after the oops.
System rebooted ok.
Was there a better way to get this ooops if I didn't have serial console?
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next reply other threads:[~2012-08-07 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 17:40 Marc MERLIN [this message]
2012-08-07 18:14 ` btrfs panic in 3.5.0 Arne Jansen
2012-08-07 18:47 ` Marc MERLIN
2012-08-09 2:52 ` Marc MERLIN
2012-08-09 6:42 ` Arne Jansen
2012-08-09 6:43 ` Jan Schmidt
2012-08-08 2:38 ` Jérôme Poulin
2012-08-08 2:47 ` Marc MERLIN
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=20120807174047.GE24635@merlins.org \
--to=marc@merlins.org \
--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;
as well as URLs for NNTP newsgroup(s).