Created attachment 108360 [details] dmesg showing the crash, CPU 2 is stuck Hi! ii libdrm-intel1: 2.4.58-2 amd64 Userspace interface to intel-spec ii xserver-xorg-v 2:2.21.15-2+ amd64 X.Org X server -- Intel i8xx, i9x Linux eizo 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux From time to time, I get a crash when starting a video in XBMC. This is not easily reproducible. Nothing in xorg.0.log. Once crashed, X.org is freezed but the remaining of the CPU seems to run correctly as long as they don't need to query stuff on the stucked CPU. See the attached dmesg. Maybe this is related to this bug reported in the Debian BTS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765590
Oh, and forgot: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06)
commit 6c308fecb4d1f928d52f9586d976f79b37149388 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Jul 11 11:28:01 2014 +0100 drm/i915: Initialise userptr mmu_notifier serial to 1 During the range invalidate, we walk the list of buffers associated with the mmu_notifer and find the ones that overlap the range. An optimisation is made to speed up the iteration by assuming the previous iter is still valid whilst the tree is unmodified. This exposes a bug when a range invalidate is triggered after we have just created the mmu_notifier, but before attaching any buffers. In that case, we presume we have an unmodified list and start walking from the last iter which is NULL. Oops. The easiest fix is then to initialise the serial of the tree to 1. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> Testecase: igt/gem_userptr_blts/stress-mm Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> Oops, not cc'ed stable.
This patch has been merged on -nightly. Feel free to reopen the bug if you still face the issue on latest kernel that has this patch.
The point was that this should be in stable@
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.