Bug 98901

Summary: amdgpu doesn't reinitialize after reboot in Xen PV DomU
Product: DRI Reporter: Mateusz Zalega <msgctl>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Logs from Xen Dom0 and affected DomU
none
domU dmesg linux-4.9.0-rc7 none

Description Mateusz Zalega 2016-11-29 11:53:44 UTC
Created attachment 128264 [details]
Logs from Xen Dom0 and affected DomU

I'm not sure whether this is a Xen or amdgpu bug.

amdgpu consistently does not reinitialize after paravirtualized Xen DomU reboots. It's a PCI passthrough setup - the physical machine does not reboot and it can't reset PCI Express devices.

This setup is working fine until I need to reboot the affected DomU.

DomU:
    Debian testing (29-11-2016)
    Linux version 4.7.0-1-amd64

Dom0:
    Debian GNU/Linux 8.6 (jessie)
    Linux 3.16.0-4-amd64

Graphics adapter:
    Radeon RX480

I attached an archive with all the relevant logs I could gather. Please contact me for further information/testing.
Comment 1 Alex Deucher 2016-11-29 13:34:16 UTC
Can you try a more recent kernel?  4.8 or 4.9?
Comment 2 Mateusz Zalega 2016-11-29 18:08:45 UTC
Created attachment 128271 [details]
domU dmesg linux-4.9.0-rc7
Comment 3 Mateusz Zalega 2016-11-29 18:10:02 UTC
(In reply to Alex Deucher from comment #1)
> Can you try a more recent kernel?  4.8 or 4.9?

I added a DomU startup log from a 4.9 series kernel. The result is the same in 4.8.
Comment 4 Martin Peres 2019-11-19 08:11:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/116.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.