From: Andrey Ryabinin <aryabinin@virtuozzo.com>
To: Jan Kara <jack@suse.cz>, Dmitry Vyukov <dvyukov@google.com>
Cc: Andi Kleen <ak@linux.intel.com>,
syzbot <syzbot+283c3c447181741aea28@syzkaller.appspotmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
jlayton@redhat.com, LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Mel Gorman <mgorman@techsingularity.net>,
Ingo Molnar <mingo@kernel.org>,
rgoldwyn@suse.com, syzkaller-bugs@googlegroups.com,
linux-fsdevel@vger.kernel.org
Subject: Re: INFO: task hung in sync_blockdev
Date: Thu, 8 Feb 2018 19:23:44 +0300 [thread overview]
Message-ID: <22e5e2e1-fd64-1a75-a80c-332a34266717@virtuozzo.com> (raw)
In-Reply-To: <20180208161821.f7x3gopytdtzgf65@quack2.suse.cz>
On 02/08/2018 07:18 PM, Jan Kara wrote:
>> By "full kernel crashdump" you mean kdump thing, or something else?
>
> Yes, the kdump thing (for KVM guest you can grab the memory dump also from
> the host in a simplier way and it should be usable with the crash utility
> AFAIK).
>
In QEMU monitor 'dump-guest-memory' command:
(qemu) help dump-guest-memory
dump-guest-memory [-p] [-d] [-z|-l|-s] filename [begin length] -- dump guest memory into file 'filename'.
-p: do paging to get guest's memory mapping.
-d: return immediately (do not wait for completion).
-z: dump in kdump-compressed format, with zlib compression.
-l: dump in kdump-compressed format, with lzo compression.
-s: dump in kdump-compressed format, with snappy compression.
begin: the starting physical address.
length: the memory size, in bytes
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-08 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a11447070ac6fcb0564a08cb1@google.com>
2018-02-07 15:52 ` INFO: task hung in sync_blockdev Andi Kleen
2018-02-08 9:28 ` Jan Kara
2018-02-08 13:28 ` Dmitry Vyukov
2018-02-08 14:08 ` Jan Kara
2018-02-08 14:18 ` Dmitry Vyukov
2018-02-08 16:18 ` Jan Kara
2018-02-08 16:23 ` Andrey Ryabinin [this message]
2018-02-08 17:17 ` Dmitry Vyukov
2018-02-09 15:31 ` Andrey Ryabinin
2018-02-08 14:49 ` Andi Kleen
2018-02-08 16:20 ` Jan Kara
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=22e5e2e1-fd64-1a75-a80c-332a34266717@virtuozzo.com \
--to=aryabinin@virtuozzo.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=rgoldwyn@suse.com \
--cc=syzbot+283c3c447181741aea28@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).