[Bug 102322] System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Comment # 18 on bug 102322 from
The good news: So far no crashes during normal uptime with
amdgpu.vm_update_mode=3

The bad news: System crashes immediately upon S3 resume (with messages quite
different from the ones I saw with earlier S3-resume crashes) - I filed bug
report https://bugs.freedesktop.org/show_bug.cgi?id=107065 on this.

(In reply to Andrey Grodzovsky from comment #17)
> dwagner, this is obviously just a work around and not a fix. It points to
> some problem with SDMA packets, if you want to continue exploring we can try
> to dump some fence traces and SDMA HW ring content to examine the latest
> packets before the hang happened.

If you can include some debug output into "amd-staging-drm-next" that helps
finding the root cause, I might be able to provide some output - if the kernel
survives long enough after the crash to write the system journal - this has not
always been the case.


You are receiving this mail because:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux