From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 0B966C433FE for ; Mon, 21 Nov 2022 14:15:13 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4NG8YC1gxZz3dxq for ; Tue, 22 Nov 2022 01:15:11 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kaod.org (client-ip=46.105.45.231; helo=8.mo548.mail-out.ovh.net; envelope-from=clg@kaod.org; receiver=) X-Greylist: delayed 2429 seconds by postgrey-1.36 at boromir; Tue, 22 Nov 2022 01:14:37 AEDT Received: from 8.mo548.mail-out.ovh.net (8.mo548.mail-out.ovh.net [46.105.45.231]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4NG8XY57pWz3c71 for ; Tue, 22 Nov 2022 01:14:33 +1100 (AEDT) Received: from mxplan5.mail.ovh.net (unknown [10.108.4.102]) by mo548.mail-out.ovh.net (Postfix) with ESMTPS id 6C2302422E; Mon, 21 Nov 2022 12:57:17 +0000 (UTC) Received: from kaod.org (37.59.142.100) by DAG4EX2.mxp5.local (172.16.2.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16; Mon, 21 Nov 2022 13:57:16 +0100 Authentication-Results: garm.ovh; auth=pass (GARM-100R003451810f8-7c3a-435c-bfd4-d3ca38bdca17, 3566E06BB212195A431F287D26CC7E6D91335DD7) smtp.auth=clg@kaod.org X-OVh-ClientIp: 82.64.250.170 Message-ID: <61dc96ad-f60e-932f-c063-d1b377006b78@kaod.org> Date: Mon, 21 Nov 2022 13:57:16 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: // a kdump hang caused by PPC pci patch series Content-Language: en-US To: Pingfan Liu , linuxppc-dev References: From: =?UTF-8?Q?C=c3=a9dric_Le_Goater?= In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [37.59.142.100] X-ClientProxiedBy: DAG2EX2.mxp5.local (172.16.2.12) To DAG4EX2.mxp5.local (172.16.2.32) X-Ovh-Tracer-GUID: 1ecdde95-3bd1-40c2-a7fb-d4f9ba5dbbf1 X-Ovh-Tracer-Id: 8479433675835280349 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvgedrheeigdeghecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfevfhfhjggtgfhisehtjeertddtfeejnecuhfhrohhmpeevrogurhhitgcunfgvucfiohgrthgvrhcuoegtlhhgsehkrghougdrohhrgheqnecuggftrfgrthhtvghrnhepuedutdetleegjefhieekgeffkefhleevgfefjeevffejieevgeefhefgtdfgiedtnecukfhppeduvdejrddtrddtrddupdefjedrheelrddugedvrddutddtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpeeotghlgheskhgrohgurdhorhhgqedpnhgspghrtghpthhtohepuddprhgtphhtthhopehkvghrnhgvlhhfrghnshesghhmrghilhdrtghomhdplhhinhhugihpphgtqdguvghvsehlihhsthhsrdhoiihlrggsshdrohhrghdptghogihusehrvgguhhgrthdrtghomhdpoffvtefjohhsthepmhhoheegkedpmhhouggvpehsmhhtphhouhht X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Coiby Xu Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On 11/21/22 12:57, Pingfan Liu wrote: > Sorry that forget a subject. > > On Mon, Nov 21, 2022 at 7:54 PM Pingfan Liu wrote: >> >> Hello Powerpc folks, >> >> I encounter an kdump bug, which I bisect and pin commit 174db9e7f775 >> ("powerpc/pseries/pci: Add support of MSI domains to PHB hotplug") >> In that case, using Fedora 36 as host, the mentioned commit as the >> guest kernel, and virto-block disk, the kdump kernel will hang: The host kernel should be using the PowerNV platform and not pseries or are you running a nested L2 guest on KVM/pseries L1 ? And as far as I remember, the patch above only impacts the IBM PowerVM hypervisor, not KVM, and PHB hotplug, or kdump induces some hot-plugging I am not aware of. Also, if indeed, this is a L2 guest, the XIVE interrupt controller is emulated in QEMU, "info pic" should return: ... irqchip: emulated >> >> [ 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 >> ... >> [ 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 >> >> >> During my test, I found that in very rare cases, the kdump can success >> (I guess it may be due to the cpu id). And if using either maxcpus=2 >> or using scsi-disk, then kdump can also success. And before the >> mentioned commit, kdump can also success. >> >> The attachment contains the xml to reproduce that bug. >> >> Do you have any ideas? Most certainly an interrupt not being delivered. You can check the status on the host with : virsh qemu-monitor-command --hmp "info pic" Thanks, C.