[Intel-gfx] New " Unclaimed read from register 0x1f0034" in 4.12-rc1

[Hans de Goede]

Hi,

On 18-05-17 14:31, Chris Wilson wrote:
> 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]

Ok, so after rebuilding everything I get more sensible results,
the "RPM wakelock ref not held during HW access" error now is
the same one as I reported before in the
"New "RPM wakelock ref not held during HW access" in 4.12-rc1 ?"
thread. Now that I can reproduce it again, I will try the fixes
suggested there.

The "Unclaimed read from register 0x1f0034" error now has this
stacktrace:

[   56.955016] PM: early resume of devices complete after 1068.631 msecs
[   56.956396] pcieport 0000:00:1c.0: System wakeup disabled by ACPI
[   56.957697] rtc_cmos 00:04: System wakeup disabled by ACPI
[   56.958261] Suspended for 0.888 seconds
[   56.964250] Unclaimed read from register 0x1f0034
[   56.964347] ------------[ cut here ]------------
[   56.964428] WARNING: CPU: 2 PID: 1799 at drivers/gpu/drm/i915/intel_uncore.c:801 __unclaimed_reg_debug+0x4e/0x60 [i915]
...
[   56.964590] Workqueue: events_unbound async_run_entry_fn
[   56.964594] task: ffff89ad698b0000 task.stack: ffff9ba401454000
[   56.964662] RIP: 0010:__unclaimed_reg_debug+0x4e/0x60 [i915]
...
[   56.964688] Call Trace:
[   56.964758]  fwtable_read32+0x17a/0x1d0 [i915]
[   56.964818]  vlv_program_watermarks+0x3c4/0x610 [i915]
[   56.964883]  ? intel_hdmi_get_hw_state+0x27/0xd0 [i915]
[   56.964941]  vlv_optimize_watermarks+0x95/0xb0 [i915]
[   56.965008]  intel_atomic_commit_tail+0x2e2/0x1030 [i915]
[   56.965016]  ? tracing_record_cmdline+0x32/0x120
[   56.965022]  ? __schedule+0x23e/0x860
[   56.965090]  intel_atomic_commit+0x399/0x4b0 [i915]
[   56.965125]  ? drm_atomic_check_only+0x37f/0x540 [drm]
[   56.965155]  drm_atomic_commit+0x4b/0x50 [drm]
[   56.965174]  drm_atomic_helper_commit_duplicated_state+0xc2/0xd0 [drm_kms_helper]
[   56.965245]  __intel_display_resume+0x85/0xc0 [i915]
[   56.965312]  intel_display_resume+0xf7/0x120 [i915]
[   56.965370]  i915_drm_resume+0xe1/0x180 [i915]
[   56.965427]  i915_pm_resume+0x1e/0x30 [i915]
[   56.965434]  pci_pm_resume+0x65/0xa0
[   56.965440]  dpm_run_callback+0x57/0x140
[   56.965444]  ? pci_pm_thaw+0x90/0x90
[   56.965447]  device_resume+0xe1/0x200
[   56.965450]  async_resume+0x1d/0x50
[   56.965455]  async_run_entry_fn+0x39/0x170
[   56.965460]  process_one_work+0x193/0x3c0
...
[   57.062736] PM: resume of devices complete after 107.709 msecs
[   57.063468] PM: resume devices took 0.108 seconds
[   57.063478] PM: Finishing wakeup.

Regards,

Hans