Bug 94384 - [BAT HSW] Unclaimed register detected before writing to register 0x45110
Summary: [BAT HSW] Unclaimed register detected before writing to register 0x45110
Status: CLOSED DUPLICATE of bug 94349
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-03 10:42 UTC by Mika Kuoppala
Modified: 2017-07-24 22:42 UTC (History)
1 user (show)

See Also:
i915 platform: HSW
i915 features:


Attachments

Description Mika Kuoppala 2016-03-03 10:42:54 UTC
/opt/igt/tests/kms_pipe_crc_basic --run-subtest nonblocking-crc-pipe-B-frame-sequence
dmesg 	

[  295.562825] ------------[ cut here ]------------
[  295.562858] WARNING: CPU: 0 PID: 6858 at drivers/gpu/drm/i915/intel_uncore.c:649 __unclaimed_reg_debug+0x7e/0x90 [i915]()
[  295.562859] Unclaimed register detected before writing to register 0x45110
[  295.562860] Modules linked in: snd_hda_intel i915 snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec snd_hwdep snd_hda_core i2c_hid mei_me snd_pcm mei i2c_designware_platform lpc_ich i2c_designware_core r8169 mii sdhci_acpi sdhci mmc_core [last unloaded: i915]
[  295.562873] CPU: 0 PID: 6858 Comm: kms_pipe_crc_ba Tainted: G     U  W       4.5.0-rc6-gfxbench+ #1
[  295.562874] Hardware name: GIGABYTE M4HM87P-00/M4HM87P-00, BIOS F6 12/10/2014
[  295.562875]  0000000000000000 ffff8800d914b910 ffffffff813fba95 ffff8800d914b958
[  295.562877]  ffffffffa03c3d90 ffff8800d914b948 ffffffff81078711 0000000000045110
[  295.562878]  0000000000000001 0000000000000000 000000000892d21a 0000000000000296
[  295.562880] Call Trace:
[  295.562883]  [<ffffffff813fba95>] dump_stack+0x67/0x92
[  295.562886]  [<ffffffff81078711>] warn_slowpath_common+0x81/0xc0
[  295.562887]  [<ffffffff81078797>] warn_slowpath_fmt+0x47/0x50
[  295.562901]  [<ffffffffa032ac8e>] __unclaimed_reg_debug+0x7e/0x90 [i915]
[  295.562911]  [<ffffffffa033266b>] hsw_write32+0x21b/0x270 [i915]
[  295.562920]  [<ffffffffa02dba68>] _ilk_disable_lp_wm+0x98/0xd0 [i915]
[  295.562929]  [<ffffffffa02e1074>] ilk_program_watermarks+0x4e4/0x9a0 [i915]
[  295.562938]  [<ffffffffa02e1640>] ilk_optimize_watermarks+0x110/0x130 [i915]
[  295.562950]  [<ffffffffa0350a94>] intel_atomic_commit+0x8b4/0x1610 [i915]
[  295.562952]  [<ffffffff8152ba4a>] ? drm_atomic_set_crtc_for_connector+0x2a/0xe0
[  295.562954]  [<ffffffff8152c722>] drm_atomic_commit+0x32/0x50
[  295.562956]  [<ffffffff81509175>] drm_atomic_helper_set_config+0x75/0xb0
[  295.562958]  [<ffffffff8151cb60>] drm_mode_set_config_internal+0x60/0x110
[  295.562959]  [<ffffffff81520276>] drm_mode_setcrtc+0x186/0x4f0
[  295.562961]  [<ffffffff8118d0b8>] ? __might_fault+0x48/0xa0
[  295.562963]  [<ffffffff8151215d>] drm_ioctl+0x13d/0x590
[  295.562964]  [<ffffffff815200f0>] ? drm_mode_setplane+0x1b0/0x1b0
[  295.562966]  [<ffffffff811e5c7a>] do_vfs_ioctl+0x8a/0x670
[  295.562968]  [<ffffffff817c3026>] ? int_ret_from_sys_call+0x52/0x9f
[  295.562970]  [<ffffffff811f1b2a>] ? __fget_light+0x6a/0x90
[  295.562971]  [<ffffffff811e629c>] SyS_ioctl+0x3c/0x70
[  295.562973]  [<ffffffff817c2e9b>] entry_SYSCALL_64_fastpath+0x16/0x73
[  295.562974] ---[ end trace dea6ba6d805caae2 ]---
Comment 1 Tvrtko Ursulin 2016-03-04 09:58:44 UTC
Also sighted in:

/archive/results/CI_IGT_test/Patchwork_1521/hsw-gt2/html/hsw-gt2@Patchwork_1521@1/igt@kms_flip@basic-flip-vs-wf_vblank.html
Comment 2 Mika Kuoppala 2016-03-17 12:04:15 UTC
Trace in 
https://bugs.freedesktop.org/show_bug.cgi?id=94349

is similar so very likely a dup. Only difference is that this is
detected by hw unclaimed detector instead of driver one.
Comment 3 Mika Kuoppala 2016-04-22 06:28:23 UTC

*** This bug has been marked as a duplicate of bug 94349 ***


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.