1. 16 2月, 2023 1 次提交
  2. 26 1月, 2023 2 次提交
  3. 21 12月, 2022 1 次提交
    • T
      drm/amdgpu: skip mes self test after s0i3 resume for MES IP v11.0 · 8660495a
      Tim Huang 提交于
      MES is part of gfxoff and MES suspend and resume are skipped for S0i3.
      But the mes_self_test call path is still in the amdgpu_device_ip_late_init.
      it's should also be skipped for s0ix as no hardware re-initialization
      happened.
      
      Besides, mes_self_test will free the BO that triggers a lot of warning
      messages while in the suspend state.
      
      [   81.656085] WARNING: CPU: 2 PID: 1550 at drivers/gpu/drm/amd/amdgpu/amdgpu_object.c:425 amdgpu_bo_free_kernel+0xfc/0x110 [amdgpu]
      [   81.679435] Call Trace:
      [   81.679726]  <TASK>
      [   81.679981]  amdgpu_mes_remove_hw_queue+0x17a/0x230 [amdgpu]
      [   81.680857]  amdgpu_mes_self_test+0x390/0x430 [amdgpu]
      [   81.681665]  mes_v11_0_late_init+0x37/0x50 [amdgpu]
      [   81.682423]  amdgpu_device_ip_late_init+0x53/0x280 [amdgpu]
      [   81.683257]  amdgpu_device_resume+0xae/0x2a0 [amdgpu]
      [   81.684043]  amdgpu_pmops_resume+0x37/0x70 [amdgpu]
      [   81.684818]  pci_pm_resume+0x5c/0xa0
      [   81.685247]  ? pci_pm_thaw+0x90/0x90
      [   81.685658]  dpm_run_callback+0x4e/0x160
      [   81.686110]  device_resume+0xad/0x210
      [   81.686529]  async_resume+0x1e/0x40
      [   81.686931]  async_run_entry_fn+0x33/0x120
      [   81.687405]  process_one_work+0x21d/0x3f0
      [   81.687869]  worker_thread+0x4a/0x3c0
      [   81.688293]  ? process_one_work+0x3f0/0x3f0
      [   81.688777]  kthread+0xff/0x130
      [   81.689157]  ? kthread_complete_and_exit+0x20/0x20
      [   81.689707]  ret_from_fork+0x22/0x30
      [   81.690118]  </TASK>
      [   81.690380] ---[ end trace 0000000000000000 ]---
      
      v2: make the comment clean and use adev->in_s0ix instead of
      adev->suspend
      Signed-off-by: NTim Huang <tim.huang@amd.com>
      Reviewed-by: NMario Limonciello <mario.limonciello@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      Cc: stable@vger.kernel.org # 6.0, 6.1
      8660495a
  4. 02 12月, 2022 1 次提交
  5. 16 11月, 2022 1 次提交
  6. 05 11月, 2022 1 次提交
  7. 28 10月, 2022 1 次提交
  8. 22 10月, 2022 2 次提交
  9. 19 10月, 2022 3 次提交
  10. 18 10月, 2022 1 次提交
  11. 29 9月, 2022 2 次提交
  12. 28 9月, 2022 1 次提交
  13. 31 8月, 2022 2 次提交
  14. 30 8月, 2022 1 次提交
  15. 29 7月, 2022 1 次提交
  16. 13 7月, 2022 2 次提交
  17. 09 7月, 2022 1 次提交
  18. 06 7月, 2022 1 次提交
  19. 01 7月, 2022 2 次提交
  20. 28 6月, 2022 1 次提交
  21. 24 6月, 2022 2 次提交
  22. 09 6月, 2022 1 次提交
    • Y
      drm/amdgpu/mes: only invalid/prime icache when finish loading both pipe MES FWs. · 431d0712
      Yifan Zhang 提交于
      invalid/prime icahce operation takes effect both pipes cuconrrently,
      therefore CP_MES_IC_BASE_LO/HI and CP_MES_MDBASE_LO/HI both have to be
      set before prime icache. Otherwise MES hardware gets garbage data in
      above regsters and causes page fault
      
      [  470.873200] amdgpu 0000:33:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:217 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
      [  470.873222] amdgpu 0000:33:00.0: amdgpu:   in page starting at address 0x000092cb89b00000 from client 10
      [  470.873234] amdgpu 0000:33:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000BB3
      [  470.873242] amdgpu 0000:33:00.0: amdgpu:      Faulty UTCL2 client ID: CPC (0x5)
      [  470.873247] amdgpu 0000:33:00.0: amdgpu:      MORE_FAULTS: 0x1
      [  470.873251] amdgpu 0000:33:00.0: amdgpu:      WALKER_ERROR: 0x1
      [  470.873256] amdgpu 0000:33:00.0: amdgpu:      PERMISSION_FAULTS: 0xb
      [  470.873260] amdgpu 0000:33:00.0: amdgpu:      MAPPING_ERROR: 0x1
      [  470.873264] amdgpu 0000:33:00.0: amdgpu:      RW: 0x0
      Signed-off-by: NYifan Zhang <yifan1.zhang@amd.com>
      Acked-by: NAlex Deucher <alexander.deucher@amd.com>
      Reviewed-by: NTim Huang <Tim.Huang@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      431d0712
  23. 08 6月, 2022 1 次提交
    • Y
      drm/amdgpu/mes: only invalid/prime icache when finish loading both pipe MES FWs. · 8728df26
      Yifan Zhang 提交于
      invalid/prime icahce operation takes effect both pipes cuconrrently,
      therefore CP_MES_IC_BASE_LO/HI and CP_MES_MDBASE_LO/HI both have to be
      set before prime icache. Otherwise MES hardware gets garbage data in
      above regsters and causes page fault
      
      [  470.873200] amdgpu 0000:33:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:217 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
      [  470.873222] amdgpu 0000:33:00.0: amdgpu:   in page starting at address 0x000092cb89b00000 from client 10
      [  470.873234] amdgpu 0000:33:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000BB3
      [  470.873242] amdgpu 0000:33:00.0: amdgpu:      Faulty UTCL2 client ID: CPC (0x5)
      [  470.873247] amdgpu 0000:33:00.0: amdgpu:      MORE_FAULTS: 0x1
      [  470.873251] amdgpu 0000:33:00.0: amdgpu:      WALKER_ERROR: 0x1
      [  470.873256] amdgpu 0000:33:00.0: amdgpu:      PERMISSION_FAULTS: 0xb
      [  470.873260] amdgpu 0000:33:00.0: amdgpu:      MAPPING_ERROR: 0x1
      [  470.873264] amdgpu 0000:33:00.0: amdgpu:      RW: 0x0
      Signed-off-by: NYifan Zhang <yifan1.zhang@amd.com>
      Acked-by: NAlex Deucher <alexander.deucher@amd.com>
      Reviewed-by: NTim Huang <Tim.Huang@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      8728df26
  24. 16 5月, 2022 1 次提交
  25. 06 5月, 2022 3 次提交
  26. 04 5月, 2022 4 次提交