| Summary: | [BAT][BYT] WARN intel_uncore.c:792 __unclaimed_reg_debug (reg 0x1f0034) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Maarten Lankhorst <bugs> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | critical | ||
| Priority: | high | CC: | intel-gfx-bugs, jwrdegoede |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | BYT | i915 features: | display/Other |
|
Description
Martin Peres
2017-07-06 10:57:47 UTC
Just adding a me too comment here. FWIW here is my almost identical backtrace: [ 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 I've not thought through the issue in detail, but I think one potential way to fix this would to add the MODESET domain to the display power well. That should also mean that we could again eliminate 886015a0ad43 ("drm/i915: reintroduce VLV/CHV PFI programming power domain workaround").
(In reply to Ville Syrjala from comment #2) > I've not thought through the issue in detail, but I think one potential way > to fix this would to add the MODESET domain to the display power well. That > should also mean that we could again eliminate 886015a0ad43 ("drm/i915: > reintroduce VLV/CHV PFI programming power domain workaround"). Hi Ville, I have been playing with this for a while, mostly blindly, since I don't have documentation on power domains. In fact, I had tried this suggestion beforebut I gave another try and it didn't make a difference: https://lists.freedesktop.org/archives/intel-gfx-trybot/2017-October/023994.html Seems first patch in https://patchwork.freedesktop.org/series/32739/ fixes it.. Quick note, we're still hitting this issue on BYT with IGT-Version: 1.20-g7aac0e8 (x86_64) (Linux: 4.14.0-rc7-drm-intel-qa-ww44-commit-ec9f758+ x86_64). https://intel-gfx-ci.01.org/tree/drm-tip/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b.html Seems fixed in CI_DRM_3320, most likely commit: commit 1a1f12872edcd5e425b668a35fb23548cfa918ef Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Nov 7 14:03:38 2017 +0000 drm/i915: Prevent unbounded wm results in g4x_compute_wm() |
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.