From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 217350] New: kdump kernel hangs in powerkvm guest
Date: Tue, 18 Apr 2023 13:11:49 +0000 [thread overview]
Message-ID: <bug-217350-206035@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=217350
Bug ID: 217350
Summary: kdump kernel hangs in powerkvm guest
Product: Platform Specific/Hardware
Version: 2.5
Hardware: PPC-64
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: PPC-64
Assignee: platform_ppc-64@kernel-bugs.osdl.org
Reporter: piliu@redhat.com
Regression: No
Created attachment 304157
--> https://bugzilla.kernel.org/attachment.cgi?id=304157&action=edit
The xml to configure the virtual machine
This bug has been observed at least since kernel version 5.19.
The kdump kernel command line:
[ 0.000000] Kernel command line: elfcorehdr=0x22c00000 no_timer_check
net.ifnames=0 console=tty0 console=hvc0,115200n8 irqpoll maxcpus=1
noirqdistrib reset_devices cgroup_disable=memory
numa=off udev.children-max=2 ehea.use_mcs=0 panic=10 kvm_cma_resv_ratio=0
transparent_hugepage=never novmcoredd hugetlb_cma=0
Finally, the system hangs:
[ 7.763260] virtio_blk virtio2: 32/0/0 default/read/poll queues
[ 7.771391] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks
(10.7 GB/10.0 GiB)
[ 68.398234] systemd-udevd[187]: virtio2: Worker [190] processing
SEQNUM=1193 is taking a long time
[ 188.398258] systemd-udevd[187]: virtio2: Worker [190] processing
SEQNUM=1193 killed
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2023-04-18 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 13:11 bugzilla-daemon [this message]
2023-05-09 9:33 ` [Bug 217350] kdump kernel hangs in powerkvm guest bugzilla-daemon
2023-05-10 17:53 ` bugzilla-daemon
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=bug-217350-206035@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.