Bug 99745 - [BYT][vlv] unclaimed register PIPE_CRC
Summary: [BYT][vlv] unclaimed register PIPE_CRC
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg 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: 2017-02-09 22:14 UTC by Chris Wilson
Modified: 2018-04-23 08:00 UTC (History)
1 user (show)

See Also:
i915 platform: BYT
i915 features: display/Other


Attachments

Description Chris Wilson 2017-02-09 22:14:05 UTC
[  105.528589] ------------[ cut here ]------------
[  105.528721] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/i915/intel_uncore.c:795 __unclaimed_reg_debug+0x51/0x60 [i915]
[  105.528742] Unclaimed read from register 0x1e106c
[  105.528754] Modules linked in: i915(+) drm_kms_helper drm intel_gtt i2c_algo_bit prime_numbers intel_powerclamp crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel cryptd lpc_ich mfd_core i2c_i801 battery video i2c_designware_platform i2c_designware_core button autofs4 sd_mod ahci libahci libata scsi_mod fan thermal i2c_hid i2c_core hid [last unloaded: i915]
[  105.528835] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G     U  W       4.10.0-rc7+ #6
[  105.528853] Hardware name: GIGABYTE GB-BXBT-1900/MZBAYAB-00, BIOS F8 03/02/2016
[  105.528869] Call Trace:
[  105.528882]  <IRQ>
[  105.528900]  dump_stack+0x63/0x8e
[  105.528916]  __warn+0xd1/0xf0
[  105.528930]  warn_slowpath_fmt+0x4f/0x60
[  105.528946]  ? ttwu_do_wakeup+0x19/0xf0
[  105.529043]  __unclaimed_reg_debug+0x51/0x60 [i915]
[  105.529140]  fwtable_read32+0x17a/0x1e0 [i915]
[  105.529228]  i9xx_pipe_crc_irq_handler+0x116/0x160 [i915]
[  105.529316]  valleyview_pipestat_irq_handler+0x86/0xe0 [i915]
[  105.529404]  valleyview_irq_handler+0x170/0x210 [i915]
[  105.529420]  ? __next_timer_interrupt+0xb1/0xe0
[  105.529436]  __handle_irq_event_percpu+0x81/0x1c0
[  105.529450]  handle_irq_event_percpu+0x23/0x60
[  105.529464]  handle_irq_event+0x36/0x60
[  105.529478]  handle_edge_irq+0x7b/0x150
[  105.529493]  handle_irq+0x20/0x30
[  105.529508]  do_IRQ+0x46/0xd0
[  105.529522]  common_interrupt+0x89/0x89
[  105.529537] RIP: 0010:cpuidle_enter_state+0x153/0x2f0
[  105.529550] RSP: 0018:ffffffff81803df8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff8d
[  105.529569] RAX: ffff88013fc183c0 RBX: ffffe8ffffc08d00 RCX: 000000000000001f
[  105.529581] RDX: 0000000000000000 RSI: ffff88013fc15a98 RDI: 0000000000000000
[  105.529594] RBP: ffffffff81803e30 R08: 0000000000000003 R09: 0000000000000e07
[  105.529607] R10: 00000000ffffffff R11: ffff88013fc152a4 R12: 0000000000000003
[  105.529620] R13: 0000000000000003 R14: 0000000000000000 R15: 00000018917bcfe4
[  105.529632]  </IRQ>
[  105.529647]  ? cpuidle_enter_state+0x12f/0x2f0
[  105.529661]  cpuidle_enter+0x17/0x20
[  105.529676]  call_cpuidle+0x2c/0x50
[  105.529689]  do_idle+0x102/0x1e0
[  105.529703]  cpu_startup_entry+0x1d/0x20
[  105.529718]  rest_init+0x85/0x90
[  105.529731]  start_kernel+0x41c/0x429
[  105.529746]  ? early_idt_handler_array+0x120/0x120
[  105.529760]  x86_64_start_reservations+0x2a/0x2c
[  105.529775]  x86_64_start_kernel+0x13b/0x14a
[  105.529789]  start_cpu+0x14/0x14
[  105.529802] ---[ end trace 7eff6599c6c80b74 ]---
Comment 1 Elizabeth 2017-06-30 15:24:30 UTC
Hello Chris,
Is there any update in this case? Thank you.
Comment 2 Elizabeth 2017-08-21 21:19:39 UTC
(In reply to Elizabeth from comment #1)
> Hello Chris,
> Is there any update in this case? Thank you.
Hello, revised by email. Still no advances on this. Reopening bug. Thank you.
Comment 3 Jani Saarinen 2018-03-29 07:11:10 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 4 Jani Saarinen 2018-04-23 08:00:04 UTC
Chris, is this still the issue? 
Closing, please re-open if still occurs.


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.