[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f8bab1d-5f60-c962-3789-1b5ed8767076@bell.net>
Date: Thu, 5 Jan 2023 14:51:06 -0500
From: Matt Fagnani <matt.fagnani@...l.net>
To: Vasant Hegde <vasant.hegde@....com>,
Baolu Lu <baolu.lu@...ux.intel.com>,
Thorsten Leemhuis <regressions@...mhuis.info>
Cc: Joerg Roedel <jroedel@...e.de>,
"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>,
LKML <linux-kernel@...r.kernel.org>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
Linux PCI <linux-pci@...r.kernel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>
Subject: Re: [regression, bisected, pci/iommu] BugĀ 216865 - Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled
I booted 6.2-rc2 + the patch four times with early kdump enabled and
panicked the kernel. There weren't any kdump or dmesg files saved to
/var/crash though. Nothing showed up in the journal from boots where the
problem happened. The amdgpu crash happened before systemd-journald
started from what I could tell. I tried to rebuild
/boot/initramfs-6.2.0-rc2+kdump.img with amd_iommu=off added to the
kernel command line with dracut, but an error that the kdumpbase module
couldn't be found was shown. I read that a different dump capture kernel
could be used with kdump, but I haven't figured out how to use that with
early kdump yet. If anyone has ideas how to get the kdump and dmesg log,
let me know. Thanks.
Powered by blists - more mailing lists