On Thu, May 18, 2017 at 02:20:09PM +0200, Hans de Goede wrote: > Hi, > > So while trying to reproduce my previously reported > "RPM wakelock ref not held during HW access" in 4.12-rc1 ?" > > Bug, to test the possible fixes I encountered a new > "RPM wakelock ref not held during HW access" error combined > with a "Unclaimed read from register 0x1f0034" error: > > Which I believe is a new issue in 4.12-rc1 I've tried adding > i915.mmio_debug=99 to the kernel cmdline and then I get the > same unclaimed read error 3 times for a single resume. > > [ 69.462566] Suspended for 3.099 seconds > [ 69.463092] PM: resume from suspend-to-idle > [ 69.489870] PM: noirq resume of devices complete after 26.368 msecs > [ 69.490177] RPM wakelock ref not held during HW access > [ 69.490355] ------------[ cut here ]------------ > [ 69.490441] WARNING: CPU: 1 PID: 2003 at drivers/gpu/drm/i915/intel_drv.h:1780 intel_init_vebox_ring_buffer+0x3753/0x4cb0 [i915] > ... > [ 69.491022] RIP: 0010:intel_init_vebox_ring_buffer+0x3753/0x4cb0 [i915] > ... > [ 69.491089] Call Trace: > [ 69.491152] intel_gvt_init_cmd_parser+0x25a/0x360 [i915] Your symbols are wrong, that's the only explanation I can give for the incorrect function chains. Can you track down what's causing the stack trace to be so confused? -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
