From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: INFO: task hung in sync_blockdev To: Jan Kara , Dmitry Vyukov Cc: Andi Kleen , syzbot , Andrew Morton , jlayton@redhat.com, LKML , Linux-MM , Mel Gorman , Ingo Molnar , rgoldwyn@suse.com, syzkaller-bugs@googlegroups.com, linux-fsdevel@vger.kernel.org References: <001a11447070ac6fcb0564a08cb1@google.com> <20180207155229.GC10945@tassilo.jf.intel.com> <20180208092839.ebe5rk6mtvkk5da4@quack2.suse.cz> <20180208140833.lpr4yjn7g3v3cdy3@quack2.suse.cz> <20180208161821.f7x3gopytdtzgf65@quack2.suse.cz> From: Andrey Ryabinin Message-ID: <22e5e2e1-fd64-1a75-a80c-332a34266717@virtuozzo.com> Date: Thu, 8 Feb 2018 19:23:44 +0300 MIME-Version: 1.0 In-Reply-To: <20180208161821.f7x3gopytdtzgf65@quack2.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: 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: email@kvack.org