On Sun, Aug 30, 2015 at 09:58:31PM +0300, Ruslan Makhmatkhanov wrote: > >> I think this is not root of cause, this is only cause of other error: > >> > >> === dmesg ==== > >> info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0 > >> error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... > >> GPU hung > >> info: [drm] capturing error event; look for more information in sysctl > >> hw.dri.0.info.i915_error_state > >> error: [drm:pid0:i915_reset] *ERROR* Failed to reset chip. > >> ============== > >> > >> This cause: > >> > >> === Xorg.log ==== > >> [ 51.010] (EE) intel(0): Detected a hung GPU, disabling acceleration. > >> [ 51.010] (EE) intel(0): When reporting this, please include > >> i915_error_state from debugfs and the full dmesg. > >> ================= > >> > >> and after this you see Attempting to unbind pinned buffer. > >> > >> I am see this in STABLE after Aug upgrade. I am don't see this at 2014-Oct > >> STABLE. > > > > For -STABLE: > > > > r280368 -- All works OK (no error messages, video playback work) > > r280369 -- All works OK (no error messages, video playback work) > > r282141 -- error: [drm:pid5:i915_gem_object_unbind] *ERROR* Attempting to > > unbind pinned buffer (video don't tested) > > r282199 -- error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer > > elapsed... GPU hung (video don't work) > > No doubt that this is not the root cause, but frankly I haven't that > "GPU hung" messages in my system. I have others like this one triggered > on shutdown: > error: [drm:pid1041:intel_lvds_enable] *ERROR* timed out waiting for > panel to power off > > And this one spamming almost with the same frequency as "pinned buffer": > error: [drm:pid1016:gen6_sanitize_pm] *ERROR* Power management > discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 000d0000, was 180d0000 > > But I had not investigated that yet and not sure they are related. > It's on r287029 head.
All of this related to import new DRI/DRM code and such code in Linux have same problems. r282141 in stable related to r279599 and r275209 in current. Can you try to revert r279599? _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"