From: "Christian König" <christian.koenig@amd.com> To: Jason Gunthorpe <jgg@nvidia.com> Cc: Joerg Roedel <jroedel@suse.de>, "regressions@lists.linux.dev" <regressions@lists.linux.dev>, Thorsten Leemhuis <regressions@leemhuis.info>, Linux PCI <linux-pci@vger.kernel.org>, "Pan, Xinhui" <Xinhui.Pan@amd.com>, Vasant Hegde <vasant.hegde@amd.com>, amd-gfx@lists.freedesktop.org, LKML <linux-kernel@vger.kernel.org>, Bjorn Helgaas <bhelgaas@google.com>, "iommu@lists.linux.dev" <iommu@lists.linux.dev>, Matt Fagnani <matt.fagnani@bell.net>, Alex Deucher <alexander.deucher@amd.com>, Baolu Lu <baolu.lu@linux.intel.com> Subject: Re: [regression, bisected, pci/iommu] Bug 216865 - Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled Date: Tue, 10 Jan 2023 14:56:52 +0100 [thread overview] Message-ID: <35b0f7db-e248-18ed-3e26-3f9f4f14f8c4@amd.com> (raw) In-Reply-To: <Y71tTdm/f+uxsTKj@nvidia.com> Am 10.01.23 um 14:51 schrieb Jason Gunthorpe: > On Tue, Jan 10, 2023 at 02:45:30PM +0100, Christian König wrote: > >> Since this is a device integrated in the CPU it could be that the ACS/ATS >> functionalities are controlled by the BIOS and can be enabled/disabled >> there. But this should always enable/disable both. > This sounds like a GPU driver bug then, it should tolerate PASID being > unavailable because of BIOS issues/whatever and not black screen on > boot? Yeah, potentially. Could I get a full "sudo lspci -vvvv -s $bus_id" + dmesg of that device? Thanks, Christian. > > Jason
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com> To: Jason Gunthorpe <jgg@nvidia.com> Cc: Baolu Lu <baolu.lu@linux.intel.com>, Alex Deucher <alexander.deucher@amd.com>, "Pan, Xinhui" <Xinhui.Pan@amd.com>, Vasant Hegde <vasant.hegde@amd.com>, Matt Fagnani <matt.fagnani@bell.net>, Thorsten Leemhuis <regressions@leemhuis.info>, Joerg Roedel <jroedel@suse.de>, "iommu@lists.linux.dev" <iommu@lists.linux.dev>, LKML <linux-kernel@vger.kernel.org>, "regressions@lists.linux.dev" <regressions@lists.linux.dev>, Linux PCI <linux-pci@vger.kernel.org>, Bjorn Helgaas <bhelgaas@google.com>, amd-gfx@lists.freedesktop.org Subject: Re: [regression, bisected, pci/iommu] Bug 216865 - Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled Date: Tue, 10 Jan 2023 14:56:52 +0100 [thread overview] Message-ID: <35b0f7db-e248-18ed-3e26-3f9f4f14f8c4@amd.com> (raw) In-Reply-To: <Y71tTdm/f+uxsTKj@nvidia.com> Am 10.01.23 um 14:51 schrieb Jason Gunthorpe: > On Tue, Jan 10, 2023 at 02:45:30PM +0100, Christian König wrote: > >> Since this is a device integrated in the CPU it could be that the ACS/ATS >> functionalities are controlled by the BIOS and can be enabled/disabled >> there. But this should always enable/disable both. > This sounds like a GPU driver bug then, it should tolerate PASID being > unavailable because of BIOS issues/whatever and not black screen on > boot? Yeah, potentially. Could I get a full "sudo lspci -vvvv -s $bus_id" + dmesg of that device? Thanks, Christian. > > Jason
next prev parent reply other threads:[~2023-01-10 13:57 UTC|newest] Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-30 8:18 [regression, bisected, pci/iommu] Bug 216865 - Black screen when amdgpu started during 6.2-rc1 boot with AMD IOMMU enabled Thorsten Leemhuis 2023-01-03 10:30 ` Joerg Roedel 2023-01-03 19:06 ` Matt Fagnani [not found] ` <5aa0e698-f715-0481-36e5-46505024ebc1@bell.net> 2023-01-04 6:54 ` Baolu Lu 2023-01-04 15:50 ` Vasant Hegde 2023-01-05 1:09 ` Matt Fagnani 2023-01-05 10:27 ` Vasant Hegde 2023-01-05 10:37 ` Baolu Lu 2023-01-05 10:46 ` Vasant Hegde 2023-01-05 14:46 ` Deucher, Alexander 2023-01-05 15:27 ` Felix Kuehling 2023-01-06 5:48 ` Baolu Lu 2023-02-15 15:39 ` Bjorn Helgaas 2023-02-15 15:39 ` Bjorn Helgaas 2023-02-16 0:35 ` Felix Kuehling 2023-02-16 0:35 ` Felix Kuehling 2023-02-16 0:44 ` Jason Gunthorpe 2023-02-16 0:44 ` Jason Gunthorpe 2023-02-16 5:37 ` Vasant Hegde 2023-02-16 5:37 ` Vasant Hegde 2023-02-16 14:55 ` Felix Kuehling 2023-02-16 14:55 ` Felix Kuehling 2023-02-16 14:53 ` Felix Kuehling 2023-02-16 14:53 ` Felix Kuehling 2023-02-16 5:25 ` Vasant Hegde 2023-02-16 5:25 ` Vasant Hegde 2023-02-16 18:59 ` Matt Fagnani 2023-02-16 18:59 ` Matt Fagnani 2023-02-16 19:59 ` Felix Kuehling 2023-02-16 19:59 ` Felix Kuehling 2023-02-17 5:36 ` Vasant Hegde 2023-02-17 5:36 ` Vasant Hegde 2023-02-17 5:23 ` Vasant Hegde 2023-02-17 5:23 ` Vasant Hegde 2023-01-05 19:51 ` Matt Fagnani 2023-01-06 7:28 ` Matt Fagnani 2023-01-10 16:08 ` Vasant Hegde 2023-01-10 16:12 ` Vasant Hegde 2023-01-06 14:14 ` Jason Gunthorpe 2023-01-07 2:44 ` Baolu Lu 2023-01-09 13:43 ` Jason Gunthorpe 2023-01-10 5:28 ` Baolu Lu 2023-01-10 5:48 ` Baolu Lu 2023-01-10 8:06 ` Matt Fagnani [not found] ` <bb3d5d1a-c222-9270-60fa-7d0b74bebd1a@linux.intel.com> 2023-01-10 22:12 ` Matt Fagnani 2023-01-10 22:12 ` Matt Fagnani 2023-01-10 13:25 ` Jason Gunthorpe 2023-01-10 13:25 ` Jason Gunthorpe 2023-01-10 13:45 ` Christian König 2023-01-10 13:45 ` Christian König 2023-01-10 13:51 ` Jason Gunthorpe 2023-01-10 13:51 ` Jason Gunthorpe 2023-01-10 13:56 ` Christian König [this message] 2023-01-10 13:56 ` Christian König 2023-01-10 20:51 ` Matt Fagnani 2023-01-10 20:51 ` Matt Fagnani 2023-01-11 8:35 ` Christian König 2023-01-11 8:35 ` Christian König 2023-01-10 15:05 ` Felix Kuehling 2023-01-10 15:05 ` Felix Kuehling 2023-01-10 15:19 ` Jason Gunthorpe 2023-01-10 15:19 ` Jason Gunthorpe 2023-01-10 15:21 ` Felix Kuehling 2023-01-10 15:21 ` Felix Kuehling 2023-01-11 3:16 ` Baolu Lu 2023-01-11 3:16 ` Baolu Lu 2023-01-11 13:08 ` Jason Gunthorpe 2023-01-11 13:08 ` Jason Gunthorpe
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=35b0f7db-e248-18ed-3e26-3f9f4f14f8c4@amd.com \ --to=christian.koenig@amd.com \ --cc=Xinhui.Pan@amd.com \ --cc=alexander.deucher@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=baolu.lu@linux.intel.com \ --cc=bhelgaas@google.com \ --cc=iommu@lists.linux.dev \ --cc=jgg@nvidia.com \ --cc=jroedel@suse.de \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=matt.fagnani@bell.net \ --cc=regressions@leemhuis.info \ --cc=regressions@lists.linux.dev \ --cc=vasant.hegde@amd.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: linkBe 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.