Comment # 22
on bug 110886
from Kai-Heng Feng
(In reply to Andrey Grodzovsky from comment #21) > In fact please rebase latest drm-next from here - > https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next, there > are 2 changes by Alex in communication with PSP with might help > > drm/amdgpu/psp: invalidate the hdp read cache before reading the psp > response > drm/amdgpu/psp: flush HDP write fifo after submitting cmds to the psp > > See if the PSP errors go away with that. The slightly different error message still popped out after 27th S3, and 28th S3 attempt froze the system: Sep 28 05:38:44 u-HP-ProBook-645-G4 kernel: [drm:psp_hw_start.cold [amdgpu]] *ERROR* PSP load asd failed! Sep 28 05:38:44 u-HP-ProBook-645-G4 kernel: [drm:psp_resume [amdgpu]] *ERROR* PSP resume failed Sep 28 05:38:44 u-HP-ProBook-645-G4 kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* resume of IP block <psp> failed -22 Sep 28 05:38:44 u-HP-ProBook-645-G4 kernel: [drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-22). Sep 28 05:38:44 u-HP-ProBook-645-G4 kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0xa0 returns -22 Sep 28 05:38:44 u-HP-ProBook-645-G4 kernel: PM: Device 0000:04:00.0 failed to resume async: error -22 $ journalctl -b -1 -k | grep "suspend entry (deep)" | wc -l 28
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
