Bug 101002 - [BAT][ELK] Warning in drm_calc_vbltimestamp_from_scanoutpos caught in CI
Summary: [BAT][ELK] Warning in drm_calc_vbltimestamp_from_scanoutpos caught in CI
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high critical
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-11 12:27 UTC by Martin Peres
Modified: 2017-07-27 16:54 UTC (History)
2 users (show)

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


Attachments

Description Martin Peres 2017-05-11 12:27:24 UTC
When running igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b on CI_DRM_2604, the machine fi-elk-e7500 generated the following warning:

[  389.934004] ------------[ cut here ]------------
[  389.934004] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/drm_irq.c:780 drm_calc_vbltimestamp_from_scanoutpos+0x16e/0x310
[  389.934004] Modules linked in: vgem i915 snd_hda_codec_realtek snd_hda_codec_generic coretemp snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm lpc_ich e1000e ptp prime_numbers mei_me pps_core mei
[  389.934004] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G     U  W       4.11.0-CI-CI_DRM_2604+ #1
[  389.934004] Hardware name: Hewlett-Packard HP Compaq 8000 Elite CMT PC/3647h, BIOS 786G7 v01.02 10/22/2009
[  389.934004] Call Trace:
[  389.934004]  <IRQ>
[  389.934004]  dump_stack+0x67/0x92
[  389.934004]  __warn+0xc6/0xe0
[  389.934004]  warn_slowpath_null+0x18/0x20
[  389.934004]  drm_calc_vbltimestamp_from_scanoutpos+0x16e/0x310
[  389.934004]  ? gen2_read32+0x73/0x200 [i915]
[  389.934004]  drm_get_last_vbltimestamp+0x3a/0x60
[  389.934004]  drm_update_vblank_count+0x62/0x290
[  389.934004]  drm_accurate_vblank_count+0x3f/0x80
[  389.934004]  display_pipe_crc_irq_handler+0x16d/0x210 [i915]
[  389.934004]  i9xx_pipe_crc_irq_handler+0xda/0x160 [i915]
[  389.934004]  i965_irq_handler+0x20a/0x2f0 [i915]
[  389.934004]  __handle_irq_event_percpu+0x58/0x370
[  389.934004]  handle_irq_event_percpu+0x1e/0x50
[  389.934004]  handle_irq_event+0x34/0x60
[  389.934004]  handle_edge_irq+0xbe/0x150
[  389.934004]  handle_irq+0x15/0x20
[  389.934004]  do_IRQ+0x63/0x130
[  389.934004]  common_interrupt+0x90/0x90
[  389.934004] RIP: 0010:cpuidle_enter_state+0x135/0x380
[  389.934004] RSP: 0018:ffffffff81e03de8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffac
[  389.934004] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
[  389.934004] RDX: 0000005ac9dfc3da RSI: ffffffff81c7891d RDI: ffffffff81706b31
[  389.934004] RBP: ffffffff81e03e20 R08: ffff88011bc170c4 R09: 0000000000000007
[  389.934004] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
[  389.934004] R13: ffff8801151dda88 R14: ffffffff81ec9f58 R15: 0000005ac9dfc3da
[  389.934004]  </IRQ>
[  389.934004]  ? cpuidle_enter_state+0x131/0x380
[  389.934004]  ? cpuidle_enter_state+0x131/0x380
[  389.934004]  cpuidle_enter+0x12/0x20
[  389.934004]  call_cpuidle+0x1e/0x40
[  389.934004]  do_idle+0x17e/0x1f0
[  389.934004]  cpu_startup_entry+0x18/0x20
[  389.934004]  rest_init+0x127/0x130
[  389.934004]  start_kernel+0x3f1/0x3fe
[  389.934004]  x86_64_start_reservations+0x2a/0x2c
[  389.934004]  x86_64_start_kernel+0x173/0x186
[  389.934004]  start_cpu+0x14/0x14
[  389.934004]  ? start_cpu+0x14/0x14
[  389.934004] ---[ end trace 10eb07f9d4184c48 ]---

Full logs: https://intel-gfx-ci.01.org/CI/CI_DRM_2604/fi-elk-e7500/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b.html
Comment 1 Maarten Lankhorst 2017-05-24 07:58:24 UTC
Could be useful to have a more elaborate dmesg.

Same thing with drm.debug=0x1f ?
Comment 2 Jani Saarinen 2017-05-29 08:29:26 UTC
Last seen: 2017-05-11
Statistics: Failure rate 4/76 run(s) (5%)
Comment 3 Jani Saarinen 2017-06-02 08:07:51 UTC
Updating statistics:
Last seen on igt@kms_pipe_crc_basic@nonblocking-crc-pipe-b (dmesg-warn): 2017-05-11
Statistics: Failure rate 4/101 run(s) (3%)

Last seen on igt@kms_pipe_crc_basic@nonblocking-crc-pipe-a (dmesg-fail): 	2017-05-04
Statistics: Failure rate 1/101 run(s) (0%)

Do we still consider this as issue?
Comment 4 Tomi Sarvela 2017-06-02 08:24:52 UTC
https://intel-gfx-ci.01.org/CI/fi-elk-e7500.html

Haven't seen this for a while. Can reopen if happens again.


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.