From: Liam Howlett <liam.howlett@oracle.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Pedro Falcato <pedro.falcato@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
mm <linux-mm@kvack.org>, "yuzhao@google.com" <yuzhao@google.com>,
Michal Hocko <MHocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
"shy828301@gmail.com" <shy828301@gmail.com>
Subject: Re: Stalls in qemu with host running 6.1 (everything stuck at mmap_read_lock())
Date: Fri, 13 Jan 2023 17:14:46 +0000 [thread overview]
Message-ID: <20230113171433.vywn6viy5iiugywv@revolver> (raw)
In-Reply-To: <3da07f36-52ce-58ef-845b-67c98f78410d@kernel.org>
* Jiri Slaby <jirislaby@kernel.org> [230112 11:57]:
> On 12. 01. 23, 16:43, Jiri Slaby wrote:
> > > and dump a kcore (kdump is set up).
> >
> > Going to trigger a dump now.
>
> Hmm, crash doesn't seems to work for 6.1, apparently. Once it did nothing,
> second time, it dumped an empty dir...
These was a patch added a few days ago to crash to support the maple
tree [1]. This might be why you are having issues?
1. https://www.mail-archive.com/crash-utility@redhat.com/msg09805.html
Thanks,
Liam
next prev parent reply other threads:[~2023-01-13 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 8:00 Stalls in qemu with host running 6.1 (everything stuck at mmap_read_lock()) Jiri Slaby
2023-01-11 8:23 ` Vlastimil Babka
2023-01-11 8:31 ` Michal Hocko
2023-01-11 9:21 ` Linux kernel regression tracking (#adding)
2023-01-19 14:58 ` Vlastimil Babka
2023-01-11 22:50 ` Paolo Bonzini
2023-01-12 0:37 ` Pedro Falcato
2023-01-12 6:07 ` Jiri Slaby
2023-01-12 10:31 ` Maxim Levitsky
2023-01-12 10:35 ` Vlastimil Babka
2023-01-12 15:43 ` Jiri Slaby
2023-01-12 16:57 ` Jiri Slaby
2023-01-13 17:14 ` Liam Howlett [this message]
2023-01-12 8:23 ` Yu Zhao
2023-01-13 17:27 ` Liam Howlett
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=20230113171433.vywn6viy5iiugywv@revolver \
--to=liam.howlett@oracle.com \
--cc=MHocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=pedro.falcato@gmail.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=yuzhao@google.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).