Bug 105538 - [CI][DSI only]igt@* - *ERROR* Potential atomic update failure on pipe A &| *ERROR* mismatch in dpll_hw_state.ebb0 (...) &| pipe state doesn't match! : WARNING: CPU: 1 PID: 1283 at drivers/gpu/drm/i915/intel_display.c:11623 intel_atomic_commit_tail+0
Summary: [CI][DSI only]igt@* - *ERROR* Potential atomic update failure on pipe A &| *E...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high normal
Assignee: Mika Kahola
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks: 105981
  Show dependency treegraph
 
Reported: 2018-03-16 07:12 UTC by Marta Löfstedt
Modified: 2019-11-29 17:42 UTC (History)
1 user (show)

See Also:
i915 platform: BXT, GLK
i915 features: display/atomic, display/DSI


Attachments

Description Marta Löfstedt 2018-03-16 07:12:15 UTC
On runs with shards testlist on BAT machines fi-bxt-dsi hit:

<3>[   51.830236] [drm:intel_pipe_update_start [i915]] *ERROR* Potential atomic update failure on pipe A
<7>[   51.840002] [drm:intel_power_well_disable [i915]] disabling dpio-common-bc
<7>[   51.840180] [drm:intel_power_well_disable [i915]] disabling power well 2
<7>[   51.840407] [drm:verify_connector_state.isra.78 [i915]] [CONNECTOR:98:DSI-1]
<7>[   51.840478] [drm:intel_dsi_get_hw_state [i915]] 
<7>[   51.840582] [drm:intel_atomic_commit_tail [i915]] [CRTC:46:pipe A]
<7>[   51.840679] [drm:intel_dsi_get_hw_state [i915]] 
<7>[   51.840759] [drm:intel_dsi_get_config [i915]] 
<7>[   51.840848] [drm:intel_dsi_get_pclk [i915]] Calculated pclk=148800
<3>[   51.840923] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ebb0 (expected 0x00006300, found 0x00000000)
<3>[   51.840994] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.ebb4 (expected 0x00002000, found 0x00000000)
<3>[   51.841065] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll0 (expected 0x00000021, found 0x00000000)
<3>[   51.841166] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll1 (expected 0x00000100, found 0x00000000)
<3>[   51.841237] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll2 (expected 0x001a6666, found 0x00000000)
<3>[   51.841308] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll3 (expected 0x00010000, found 0x00000000)
<3>[   51.841378] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll6 (expected 0x00030904, found 0x00000000)
<3>[   51.841449] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll8 (expected 0x00000008, found 0x00000000)
<3>[   51.841520] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll9 (expected 0x0000000a, found 0x00000000)
<3>[   51.841591] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pll10 (expected 0x08003c00, found 0x00000000)
<3>[   51.841661] [drm:pipe_config_err [i915]] *ERROR* mismatch in dpll_hw_state.pcsdw12 (expected 0x0000004d, found 0x00000000)
<4>[   51.841665] ------------[ cut here ]------------
<4>[   51.841668] pipe state doesn't match!
<4>[   51.841778] WARNING: CPU: 1 PID: 1283 at drivers/gpu/drm/i915/intel_display.c:11623 intel_atomic_commit_tail+0xc1c/0xd20 [i915]
<4>[   51.841782] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel lpc_ich i915 snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core mei_me snd_pcm igb mei prime_numbers i2c_hid pinctrl_broxton pinctrl_intel
<4>[   51.841846] CPU: 1 PID: 1283 Comm: kms_3d Not tainted 4.16.0-rc5-g613eb885b69e-drmtip_1+ #1
<4>[   51.841849] Hardware name: Intel Corp. Broxton P/Apollolake RVP1A, BIOS APLKRVPA.X64.0150.B11.1608081044 08/08/2016
<4>[   51.841920] RIP: 0010:intel_atomic_commit_tail+0xc1c/0xd20 [i915]
<4>[   51.841923] RSP: 0018:ffff976480297b38 EFLAGS: 00010292
<4>[   51.841929] RAX: 0000000000000019 RBX: ffff9479e4eca548 RCX: 0000000000000001
<4>[   51.841932] RDX: 0000000080000001 RSI: ffffffffaa0ea361 RDI: 00000000ffffffff
<4>[   51.841935] RBP: ffff9479f0beae98 R08: ffff9479f4b430e0 R09: 0000000001422669
<4>[   51.841937] R10: ffff9479f0beb178 R11: 0000000000000000 R12: ffff9479f0be92a8
<4>[   51.841940] R13: 0000000000000000 R14: ffff9479e5320000 R15: ffff9479e5320760
<4>[   51.841944] FS:  00007f29ce03f980(0000) GS:ffff9479ffc80000(0000) knlGS:0000000000000000
<4>[   51.841947] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[   51.841950] CR2: 00007f29c1aac000 CR3: 0000000174bc2000 CR4: 00000000003406e0
<4>[   51.841952] Call Trace:
<4>[   51.842040]  intel_atomic_commit+0x256/0x330 [i915]
<4>[   51.842054]  restore_fbdev_mode_atomic+0x199/0x1f0
<4>[   51.842080]  drm_fb_helper_restore_fbdev_mode_unlocked+0x42/0x90
<4>[   51.842086]  drm_fb_helper_set_par+0x24/0x50
<4>[   51.842157]  intel_fbdev_set_par+0x11/0x60 [i915]
<4>[   51.842164]  fbcon_init+0x594/0x620
<4>[   51.842178]  visual_init+0xca/0x120
<4>[   51.842185]  do_bind_con_driver+0x1bb/0x3a0
<4>[   51.842199]  store_bind+0x190/0x1b0
<4>[   51.842211]  kernfs_fop_write+0xfe/0x180
<4>[   51.842222]  __vfs_write+0x1e/0x130
<4>[   51.842229]  ? rcu_read_lock_sched_held+0x6f/0x80
<4>[   51.842233]  ? rcu_sync_lockdep_assert+0x25/0x50
<4>[   51.842238]  ? __sb_start_write+0xd9/0x1f0
<4>[   51.842241]  ? __sb_start_write+0xf3/0x1f0
<4>[   51.842251]  vfs_write+0xbd/0x1b0
<4>[   51.842260]  SyS_write+0x40/0xa0
<4>[   51.842270]  do_syscall_64+0x65/0x1a0
<4>[   51.842277]  entry_SYSCALL_64_after_hwframe+0x42/0xb7
<4>[   51.842281] RIP: 0033:0x7f29cd7c4281
<4>[   51.842284] RSP: 002b:00007ffe70b61a58 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
<4>[   51.842289] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f29cd7c4281
<4>[   51.842292] RDX: 0000000000000002 RSI: 00007f29cdc39bf1 RDI: 0000000000000007
<4>[   51.842295] RBP: 00007ffe70b62aa0 R08: 000055f44d2e6f83 R09: 0000000000000006
<4>[   51.842298] R10: 0000000000000000 R11: 0000000000000246 R12: 00007f29cd7ad718
<4>[   51.842300] R13: 0000000000000003 R14: 00007f29cd7b2628 R15: 00007f29cd7aed80
<4>[   51.842322] Code: 0f b6 d0 0f b6 f1 48 c7 c7 f8 a9 69 c0 e8 ed da aa e8 0f 0b 41 0f b6 4c 24 09 e9 d7 f9 ff ff 48 c7 c7 a7 79 67 c0 e8 d4 da aa e8 <0f> 0b e9 81 fa ff ff 80 3d 2f 73 15 00 00 0f b6 ca 0f 85 b4 00 
<4>[   51.842547] WARNING: CPU: 1 PID: 1283 at drivers/gpu/drm/i915/intel_display.c:11623 intel_atomic_commit_tail+0xc1c/0xd20 [i915]
<4>[   51.842550] ---[ end trace 0c6fc863bcc27d7f ]---

the repeated issues with intel_atomic_commit_tail

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_atomic_interruptible@universal-setplane-primary.html
Comment 1 Marta Löfstedt 2018-03-16 07:17:45 UTC
For overview of the results see:
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip.html

Here are some more occurrences:

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@debugfs_test@read_all_entries_display_off.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_3d.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_atomic_interruptible@universal-setplane-primary.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_ccs@pipe-a-crc-primary-rotation-180.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_chv_cursor_fail@pipe-c-256x256-top-edge.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_color@pipe-c-ctm-negative.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_cursor_crc@cursor-128x128-sliding.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_flip@dpms-off-confusion-interruptible.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-cpu.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-gtt.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-mmap-cpu.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_mmio_vs_cs_flip@setcrtc_vs_cs_flip.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_plane_scaling@pipe-b-scaler-with-rotation.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_rmfb@close-fd.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_rotation_crc@primary-rotation-90.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_vblank@pipe-b-wait-busy.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_vblank@pipe-b-wait-forked-hang.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_vblank@pipe-c-query-busy.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_vblank@pipe-c-ts-continuation-idle.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@pm_rpm@modeset-non-lpsp.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@pm_rpm@system-suspend-execbuf.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_busy@basic-flip-c.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-bxt-dsi/igt@kms_flip@basic-plain-flip.html
Comment 2 Marta Löfstedt 2018-03-16 12:15:58 UTC
There are a lot more hits on this issue:
Comment 9 Martin Peres 2018-07-02 22:58:22 UTC
Also seen on GLK: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_72/fi-glk-dsi/igt@kms_3d.html
Comment 10 CI Bug Log 2019-07-24 17:59:22 UTC
A CI Bug Log filter associated to this bug has been updated:

{- DSI: igt@runner@aborted - fail - Previous test: kms_hdmi_inject \(inject-(4k|audio)\)|Previous test: kms_3d -}
{+ DSI: igt@runner@aborted - fail - Previous test: kms_hdmi_inject \(inject-(4k|audio)\)|Previous test: kms_3d +}


  No new failures caught with the new filter
Comment 11 CI Bug Log 2019-07-25 11:48:53 UTC
A CI Bug Log filter associated to this bug has been updated:

{- DSI: igt@runner@aborted - fail - Previous test: kms_hdmi_inject \(inject-(4k|audio)\)|Previous test: kms_3d -}
{+ DSI: igt@runner@aborted - fail - Previous test: kms_hdmi_inject \(inject-(4k|audio)\)|kms_3d|gem_softpin (noreloc-s3) +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_333/fi-bxt-dsi/igt@runner@aborted.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_334/fi-bxt-dsi/igt@runner@aborted.html
Comment 12 CI Bug Log 2019-07-25 11:50:08 UTC
A CI Bug Log filter associated to this bug has been updated:

{- DSI: all tests - *ERROR* mismatch in dpll_hw_state -}
{+ DSI: all tests - dmesg-fail- *ERROR* mismatch in dpll_hw_state +}


  No new failures caught with the new filter
Comment 13 CI Bug Log 2019-07-25 11:50:48 UTC
A CI Bug Log filter associated to this bug has been updated:

{- DSI: all tests - pipe state doesn&#39;t match! -}
{+ DSI: all tests - dmesg-warn/dmesg-fail - pipe state doesn&#39;t match! +}


  No new failures caught with the new filter
Comment 14 CI Bug Log 2019-07-25 11:51:51 UTC
A CI Bug Log filter associated to this bug has been updated:

{- DSI: igt@kms_setmode@basic - Failed assertion: fabs(mean - expected) &lt; 1.718 * stddev &amp;&amp; pipe state doesn&#39;t match! -}
{+ DSI: igt@kms_setmode@basic - dmesg-fail - Failed assertion: fabs(mean - expected) &lt; 1.718 * stddev &amp;&amp; pipe state doesn&#39;t match! +}


  No new failures caught with the new filter
Comment 15 Jani Saarinen 2019-08-06 06:29:16 UTC
This was seen seen every day but not now seen 1,5 weeks already. Reason for that is that we are not running full idle runs. So just commenting this out.
Comment 16 Martin Peres 2019-11-29 17:42:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/86.


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.