[Bug 79980] Random radeonsi crashes

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

 



Comment # 61 on bug 79980 from
thanks for all the fixes !

currently using
http://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-3.17-rebased-on-fixes
and it looks pretty stable so far (radeonsi, R9 270X)

even with 3.14.14 there were some (pretty seldom) but occasional crashes of X:

vanilla 3.16-rc6 was pretty much unusable (X + box hardlocks)

and especially http://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-3.17-wip
(*without* the fixes) had dozens of gpu crashes yesterday evening/night which
were recovering (probably thanks to radeon.hard_reset=1) without crashing X and
hardlocking the system:


ring 0 stalled for more than 10010msec GPU lockup
waiting for ... last fence id ... on ring 0
GPU softreset ...


[drm] UVD initialized successfully. 
[drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35)
radeon 0000:01:00.0: ib ring test failed (-35) 
couldn't schedule ib 
still active bo inside vm
GPU softreset ...


radeon 0000:01:00.0: ring 5 stalled for more than 10000msec
radeon 0000:01:00.0: GPU lockup (waiting for ... last fence id ... on ring 5
[drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed
(-35).[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5
(-35)[drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed)


radeon 0000:01:00.0: ring 5 stalled for more than 3438516msec
radeon 0000:01:00.0: GPU lockup (waiting for ... last fence id ... on ring 5)
radeon 0000:01:00.0: ffff8807cfa63000 pin failed
[drm:radeon_crtc_page_flip] *ERROR* failed to pin new rbo buffer before flip 




and messages in Xorg.0.log with 
(WW) RADEON(0): radeon_dri2_flip_event_handler: Pageflip completion event has
impossible msc 89175 < target_msc 89176

and

(WW) RADEON(0): flip queue failed: Invalid argument
(WW) RADEON(0): Page flip failed: Invalid argument



currently still running with radeon.hard_reset=1 - but that probably shouldn't
be needed anymore


best trigger for those occasional crashes was using chromium/chrome, watching
videos on youtube, switching apps via alt+tab (using an composited desktop with
compiz-fusion 0.8.8) and from time to time opening up gmail (which, if I
remember correctly would cause the gpu to crash at least twice of these
countless times yesterday)


You are receiving this mail because:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://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