From: Chris Mason <chris.mason@fusionio.com>
To: Jon Nelson <jnelson@jamponi.net>
Cc: Jon Nelson <jnelson+btrfs@jamponi.net>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: hang on 3.9, 3.10-rc5
Date: Fri, 21 Jun 2013 07:30:40 -0400 [thread overview]
Message-ID: <20130621113040.4477.83994@localhost.localdomain> (raw)
In-Reply-To: <CAKuK5J3TBDNgHJ_YUWupB4rO_ixG0LnZFE=K5Uo5Wbo=76rT+A@mail.gmail.com>
Quoting Jon Nelson (2013-06-20 21:46:46)
> Is this what you are looking for?
> After this, the CPU gets "stuck" and I have to reboot.
>
>
> [360491.932226] ------------[ cut here ]------------
> [360491.932261] kernel BUG at
> /home/abuild/rpmbuild/BUILD/kernel-desktop-3.9.6/linux-3.9/fs/btrfs/ctree.c:1144!
Aha, this is not a hang but a crash. I know the end result is the same
(you push the reset button) but for a crash we always want to see this
oops message.
I'll try to reproduce (and check out the bugzilla too). Do you have
compression on?
-chris
next prev parent reply other threads:[~2013-06-21 11:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 15:43 hang on 3.9, 3.10-rc5 Sage Weil
2013-06-11 16:21 ` Chris Mason
[not found] ` <alpine.DEB.2.00.1306121317300.27596@cobra.newdream.net>
2013-06-18 15:56 ` Sage Weil
2013-06-18 16:36 ` Chris Mason
2013-06-18 16:37 ` Josef Bacik
2013-06-18 16:59 ` Chris Mason
2013-06-20 3:44 ` Sage Weil
2013-06-20 21:56 ` Sage Weil
2013-06-21 0:42 ` Chris Mason
2013-06-21 1:00 ` Sage Weil
2013-06-21 1:04 ` Chris Mason
2013-06-21 1:09 ` Sage Weil
2013-08-09 18:04 ` Sage Weil
2013-08-09 18:08 ` Chris Mason
2013-06-18 17:19 ` Jon Nelson
2013-06-21 1:11 ` Chris Mason
2013-06-21 1:46 ` Jon Nelson
2013-06-21 5:40 ` Chris Murphy
2013-06-21 6:42 ` Clemens Eisserer
2013-06-25 15:52 ` Liu Bo
2013-06-21 11:30 ` Chris Mason [this message]
2013-06-21 13:14 ` Jon Nelson
2013-06-21 14:54 ` Johannes Hirte
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=20130621113040.4477.83994@localhost.localdomain \
--to=chris.mason@fusionio.com \
--cc=jnelson+btrfs@jamponi.net \
--cc=jnelson@jamponi.net \
--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).