Bug 97798 - [chv] Unclaimed register detected after reading register 0x1e1110 [PORT_HOTPLUG_EN]
Summary: [chv] Unclaimed register detected after reading register 0x1e1110 [PORT_HOTPL...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: highest blocker
Assignee: Elio
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 98255 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-13 19:13 UTC by Chris Wilson
Modified: 2017-02-20 11:08 UTC (History)
2 users (show)

See Also:
i915 platform: BSW/CHT
i915 features: display/Other, power/suspend-resume


Attachments

Description Chris Wilson 2016-09-13 19:13:39 UTC
On resume:

  534.786979] ------------[ cut here ]------------
[  534.787474] WARNING: CPU: 0 PID: 936 at drivers/gpu/drm/i915/intel_uncore.c:803 __unclaimed_reg_debug+0x73/0x90 [i915]
[  534.787491] Unclaimed register detected after reading register 0x1e1110
[  534.787624] Modules linked in: i915 nls_utf8 nls_cp437 vfat fat crct10dif_pclmul crc32c_intel aesni_intel intel_gtt aes_x86_64 glue_helper lrw drm_kms_helper gf128mul ablk_helper cryptd
[  534.787647] CPU: 0 PID: 936 Comm: kworker/u4:11 Not tainted 4.8.0-rc5+ #68
[  534.787658] Hardware name:                  /        , BIOS PYBSWCEL.86A.0027.2015.0507.1758 05/07/2015
[  534.787697] Workqueue: events_unbound async_run_entry_fn
[  534.787735]  ffffffffa01881d3 ffff8802327e7900 ffffffff813e98d9 ffff8802327e7978
[  534.787766]  0000000000000000 ffff8802327e7948 ffffffff81079b87 ffff88023275b180
[  534.787795]  0000032382a62af0 ffffed00464fcf2b 0000000000000001 00000000001e1110
[  534.787803] Call Trace:
[  534.788252]  [<ffffffffa01881d3>] ? __unclaimed_reg_debug+0x73/0x90 [i915]
[  534.788275]  [<ffffffff813e98d9>] dump_stack+0x68/0x9f
[  534.788300]  [<ffffffff81079b87>] __warn+0x107/0x130
[  534.788322]  [<ffffffff81079c42>] warn_slowpath_fmt+0x92/0xb0
[  534.788342]  [<ffffffff81079bb0>] ? __warn+0x130/0x130
[  534.788783]  [<ffffffffa018cd0c>] ? chv_read32+0x8c/0x350 [i915]
[  534.789226]  [<ffffffffa01881d3>] __unclaimed_reg_debug+0x73/0x90 [i915]
[  534.789665]  [<ffffffffa018cf82>] chv_read32+0x302/0x350 [i915]
[  534.790105]  [<ffffffffa018cc80>] ? chv_read16+0x350/0x350 [i915]
[  534.790507]  [<ffffffffa0109fc8>] i915_hpd_irq_setup+0x148/0x1c0 [i915]
[  534.790959]  [<ffffffffa01df23b>] intel_hpd_init+0xab/0xc0 [i915]
[  534.791358]  [<ffffffffa01007af>] i915_drm_resume+0xef/0x1b0 [i915]
[  534.791758]  [<ffffffffa01008aa>] i915_pm_restore+0x3a/0x40 [i915]
[  534.792156]  [<ffffffffa01008c9>] i915_pm_resume+0x9/0x10 [i915]
[  534.792177]  [<ffffffff81441a5e>] pci_pm_resume+0xde/0x180
[  534.792198]  [<ffffffff81441980>] ? pci_pm_resume_noirq+0x100/0x100
[  534.792222]  [<ffffffff8156fec0>] dpm_run_callback+0x40/0x80
[  534.792244]  [<ffffffff815706d9>] device_resume+0xe9/0x3a0
[  534.792264]  [<ffffffff81570990>] ? device_resume+0x3a0/0x3a0
[  534.792283]  [<ffffffff815709a8>] async_resume+0x18/0x40
[  534.792305]  [<ffffffff810af06f>] async_run_entry_fn+0x7f/0x220
[  534.792332]  [<ffffffff810a1be3>] process_one_work+0x3d3/0x810
[  534.792353]  [<ffffffff810a1b5d>] ? process_one_work+0x34d/0x810
[  534.792377]  [<ffffffff810a1810>] ? cancel_delayed_work_sync+0x10/0x10
[  534.792400]  [<ffffffff810a20a3>] worker_thread+0x83/0x720
[  534.792424]  [<ffffffff810a2020>] ? process_one_work+0x810/0x810
[  534.792443]  [<ffffffff810ab59d>] kthread+0x18d/0x1b0
[  534.792463]  [<ffffffff810ab410>] ? kthread_create_on_node+0x340/0x340
[  534.792488]  [<ffffffff81802e6f>] ret_from_fork+0x1f/0x40
[  534.792508]  [<ffffffff810ab410>] ? kthread_create_on_node+0x340/0x340
[  534.792521] ---[ end trace 0655747a541f420b ]---
[  534.909983] PM: resume of devices complete after 169.241 msecs
[  534.919573] PM: Finishing wakeup.
[  534.919578] Restarting tasks ... done.
Comment 1 Hans de Goede 2016-12-12 22:05:26 UTC
I'm seeing this too, on a cherrytrail z8300 based cube iwork8 air tablet:

[ 1050.660449] ------------[ cut here ]------------
[ 1050.660473] WARNING: CPU: 0 PID: 1807 at drivers/gpu/drm/i915/intel_uncore.c:
832 intel_init_vebox_ring_buffer+0x96f/0x4a40 [i915]
[ 1050.660475] Unclaimed read from register 0x1e1110
[ 1050.660519] Modules linked in: ... (many)
[ 1050.660583] CPU: 0 PID: 1807 Comm: kworker/u8:7 Tainted: G           OE   4.9.0-rc8+ #6
[ 1050.660585] Hardware name: cube i1-TF/Cherry Trail CR, BIOS 5.11 05/13/2016
[ 1050.660593] Workqueue: events_unbound async_run_entry_fn
[ 1050.660599]  ffffa7668114fba8 ffffffffb13ef4ad ffffa7668114fbf8 0000000000000000
[ 1050.660602]  ffffa7668114fbe8 ffffffffb10a1ddb 0000034033153fac 0000000000000000
[ 1050.660606]  00000000001e1110 0000000000000001 ffff8dbfff218750 0000000000000001
[ 1050.660607] Call Trace:
[ 1050.660614]  [<ffffffffb13ef4ad>] dump_stack+0x63/0x86
[ 1050.660618]  [<ffffffffb10a1ddb>] __warn+0xcb/0xf0
[ 1050.660620]  [<ffffffffb10a1e5f>] warn_slowpath_fmt+0x5f/0x80
[ 1050.660624]  [<ffffffffb10cd4c5>] ? wake_up_process+0x15/0x20
[ 1050.660640]  [<ffffffffc05727ef>] intel_init_vebox_ring_buffer+0x96f/0x4a40 [i915]
[ 1050.660656]  [<ffffffffc0575a17>] intel_init_vebox_ring_buffer+0x3b97/0x4a40 [i915]
[ 1050.660668]  [<ffffffffc052086a>] vlv_force_gfx_clock+0x555a/0x55b0 [i915]
[ 1050.660684]  [<ffffffffc05a9e3d>] intel_hpd_init+0x6d/0x80 [i915]
[ 1050.660695]  [<ffffffffc0519261>] 0xffffffffc0519261
[ 1050.660706]  [<ffffffffc051930e>] 0xffffffffc051930e
[ 1050.660716]  [<ffffffffc051933e>] 0xffffffffc051933e
[ 1050.660720]  [<ffffffffb1446014>] pci_pm_resume+0x64/0xa0
[ 1050.660723]  [<ffffffffb1445fb0>] ? pci_pm_thaw+0x90/0x90
[ 1050.660727]  [<ffffffffb1553b4d>] dpm_run_callback+0x4d/0x120
[ 1050.660730]  [<ffffffffb15540a6>] device_resume+0xa6/0x200
[ 1050.660732]  [<ffffffffb155421d>] async_resume+0x1d/0x50
[ 1050.660735]  [<ffffffffb10c4f49>] async_run_entry_fn+0x39/0x140
[ 1050.660739]  [<ffffffffb10bbe24>] process_one_work+0x184/0x430
[ 1050.660742]  [<ffffffffb10bc11e>] worker_thread+0x4e/0x490
[ 1050.660744]  [<ffffffffb10bc0d0>] ? process_one_work+0x430/0x430
[ 1050.660747]  [<ffffffffb10bc0d0>] ? process_one_work+0x430/0x430
[ 1050.660750]  [<ffffffffb10c1b29>] kthread+0xd9/0xf0
[ 1050.660753]  [<ffffffffb10c1a50>] ? kthread_park+0x60/0x60
[ 1050.660757]  [<ffffffffb18189d5>] ret_from_fork+0x25/0x30
[ 1050.660760] ---[ end trace bd5a695839ae61ae ]---

And then after a second resume:

[ 1060.746358] [drm:intel_init_vebox_ring_buffer [i915]] *ERROR* media: timed out waiting for forcewake ack request.
[ 1060.796482] [drm:intel_init_vebox_ring_buffer [i915]] *ERROR* media: timed out waiting for forcewake ack request.
Comment 2 Chris Wilson 2017-02-05 14:59:58 UTC
Still causing mass slowdown:

[    4.740136] WARNING: CPU: 1 PID: 221 at drivers/gpu/drm/i915/intel_uncore.c:795 __unclaimed_reg_debug+0x44/0x50 [i915]
[    4.740155] Unclaimed read from register 0x1e1110
[    4.740168] Modules linked in: i915(+) intel_gtt drm_kms_helper prime_numbers
[    4.740190] CPU: 1 PID: 221 Comm: systemd-udevd Not tainted 4.10.0-rc6+ #384
[    4.740203] Hardware name:                  /        , BIOS PYBSWCEL.86A.0027.2015.0507.1758 05/07/2015
[    4.740220] Call Trace:
[    4.740236]  dump_stack+0x4d/0x6f
[    4.740251]  __warn+0xc1/0xe0
[    4.740265]  warn_slowpath_fmt+0x4a/0x50
[    4.740281]  ? insert_work+0x77/0xc0
[    4.740355]  ? fwtable_write32+0x90/0x130 [i915]
[    4.740431]  __unclaimed_reg_debug+0x44/0x50 [i915]
[    4.740507]  fwtable_read32+0xd8/0x130 [i915]
[    4.740575]  i915_hpd_irq_setup+0xa5/0x100 [i915]
[    4.740649]  intel_hpd_init+0x68/0x80 [i915]
[    4.740716]  i915_driver_load+0xe19/0x1380 [i915]
[    4.740784]  i915_pci_probe+0x32/0x90 [i915]
[    4.740799]  pci_device_probe+0x8b/0xf0
[    4.740815]  driver_probe_device+0x2b6/0x450
[    4.740828]  __driver_attach+0xda/0xe0
[    4.740841]  ? driver_probe_device+0x450/0x450
[    4.740853]  bus_for_each_dev+0x5b/0x90
[    4.740865]  driver_attach+0x19/0x20
[    4.740878]  bus_add_driver+0x166/0x260
[    4.740892]  driver_register+0x5b/0xd0
[    4.740906]  ? 0xffffffffa0166000
[    4.740920]  __pci_register_driver+0x47/0x50
[    4.740985]  i915_init+0x5c/0x5e [i915]
[    4.740999]  do_one_initcall+0x3e/0x160
[    4.741015]  ? __vunmap+0x7c/0xc0
[    4.741029]  ? kmem_cache_alloc+0xcf/0x120
[    4.741045]  do_init_module+0x55/0x1c4
[    4.741060]  load_module+0x1f3f/0x25b0
[    4.741073]  ? __symbol_put+0x40/0x40
[    4.741086]  ? kernel_read_file+0x100/0x190
[    4.741100]  SYSC_finit_module+0xbc/0xf0
[    4.741112]  SyS_finit_module+0x9/0x10
[    4.741125]  entry_SYSCALL_64_fastpath+0x17/0x98
[    4.741135] RIP: 0033:0x7f8559a140f9
[    4.741145] RSP: 002b:00007fff7509a3e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    4.741161] RAX: ffffffffffffffda RBX: 00007f855aba02d1 RCX: 00007f8559a140f9
[    4.741172] RDX: 0000000000000000 RSI: 000055b6db0914f0 RDI: 0000000000000011
[    4.741183] RBP: 0000000000020000 R08: 0000000000000000 R09: 000000000000000e
[    4.741193] R10: 0000000000000011 R11: 0000000000000246 R12: 000055b6db0854d0
[    4.741204] R13: 000055b6db091150 R14: 0000000000000000 R15: 000055b6db035924
Comment 3 Jari Tahvanainen 2017-02-08 08:30:17 UTC
See comment (1) from Chris on bug 98255 as food for thought.
Comment 4 Jari Tahvanainen 2017-02-08 08:30:39 UTC
*** Bug 98255 has been marked as a duplicate of this bug. ***
Comment 5 Hans de Goede 2017-02-10 10:05:34 UTC
(In reply to Jari Tahvanainen from comment #3)
> See comment (1) from Chris on bug 98255 as food for thought.

I can confirm that the patch from bug 98255 comment 1 fixes this issue for me.
Comment 6 Ricardo 2017-02-14 16:50:58 UTC
Patch confirmed as a fix
Comment 7 Chris Wilson 2017-02-14 17:04:24 UTC
The patch hasn't been applied yet (lacks review), so the bug remains.
Comment 8 Jani Saarinen 2017-02-15 12:09:51 UTC
Patch sent for review
https://patchwork.freedesktop.org/series/19687/
Comment 9 Chris Wilson 2017-02-16 10:00:34 UTC
commit 262fd485ac6b476479f41f00bb104f6a1766ae66
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Feb 15 13:15:47 2017 +0000

    drm/i915: Only enable hotplug interrupts if the display interrupts are enabled


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.