Christian,

I'm attaching the output of sudo lspci -vvvv. I'm not sure what $bus_id 
is in this case. I guess it might be 00 in 00:00.0. I attached the dmesg 
from previous boots with 6.2-rc1 at 
https://bugzilla.kernel.org/show_bug.cgi?id=216865#c2 as I mentioned at 
https://lore.kernel.org/all/52583644-d875-a454-7288-8b00ea0566ae@bell.net/ 
and 6.2-rc2 + Vasant's patch with rd.driver.blacklist=amdgpu on the 
kernel command line at 
https://lore.kernel.org/all/ff26929d-9fb0-3c85-2594-dc2937c1ba9a@bell.net/ 
I'm using the Radeon R5 integrated GPU which is called Wani in lspci and 
Carrizo in dmesg. The CPU is AMD A10-9620P which is Bristol Ridge or 
Excavator+ according to 
https://en.wikipedia.org/wiki/List_of_AMD_accelerated_processing_units 
I'm using the internal Elan touchscreen in the laptop. I'm not using the 
HDMI port for an external monitor or audio which I think is called 
Kabini HDMI/DP Audio in lspci

Thanks,

Matt

On 1/10/23 08:56, Christian König wrote:
> 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
>