From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs kernel hang? (4.1.3)
Date: Tue, 6 Oct 2015 16:51:11 -0700 [thread overview]
Message-ID: <20151006235111.GO20745@merlins.org> (raw)
In-Reply-To: <20151006054034.GA21376@merlins.org>
On Mon, Oct 05, 2015 at 10:40:34PM -0700, Marc MERLIN wrote:
> I started doing multiple mencoder/ffmpeg commands, and as I ran one
> more, the system froze up (as in everything froze, even running ssh
> sessions not doing any IO)
>
> sysrq-W output:
> http://marc.merlins.org/tmp/sysrq_4.1.3.txt
>
> I'm assuming btrfs is to blame, but I'm not certain.
> Hopefully someone knowledgeable can have a look.
Same exact bug/hang happened again, same condition. Started one ffmpeg
too many, and everything stopped.
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/ | PGP 1024R/763BE901
prev parent reply other threads:[~2015-10-06 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 5:40 btrfs kernel hang? (4.1.3) Marc MERLIN
2015-10-06 23:51 ` Marc MERLIN [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=20151006235111.GO20745@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).