On Wed, Apr 01, 2015 at 10:51:03AM -0500, Chris wrote: > I started following this list due to the fact that I was getting lockups > with errors reported in my syslog like this: > > [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render > ring idle > > I've submitted a bug report at Ubuntu Launchpad and added to the bug > report at freedesktop.org both seem to be in a state of hiatus right now > as I haven't seen anything being done on either in quite awhile. Based > on a a recommendation from Daniel Vetter I started running the latest > drm kernel from > http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ > > I installed 4.0.0-997-generic #201503201505 SMP Fri Mar 20 15:07:05 UTC > 2015 x86_64 x86_64 x86_64 GNU/Linux on 27 March at 7:38am. It seemed to > run great, I was feeling pretty good that the bug or whatever was > finally fixed until last night, 31 March at 21:20 I was browsing with > Firefox I noticed that the seconds on my clock had stopped even though > the mouse continued to be movable. I could not switch windows as usual > when this happens. I saw the below in my syslog after I rebooted however > I was at the beginning of the boot process and I have no idea what it > means anyway. > > Mar 31 21:23:04 localhost kernel: [395103.520038] WARNING: CPU: 1 PID: > 14205 at /home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1142 > drm_wait_one_vblank+0x12f/0x180 [drm]() > Mar 31 21:23:04 localhost kernel: [395103.520040] vblank wait timed out > on crtc 0 > > There was no sign of the 'hangcheck...' error in last nights lockup. I > downloaded and installed kernel 4.0.0-997-generic #201503310205 SMP Tue > Mar 31 02:07:04 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux. Do I just keep > installing the latest kernel until the problem goes away or is there > anything else I can do to try and help figure out what the problem is? > Any information about my system I can provide? I'll do whatever it > takes. This having to reboot every couple of days or having the system > lockup at inopportune times is killing me. It's a different class of bug. At a rough guess you want to update xserver-xorg-video-intel instead this time. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx