Bug 105537 - [CI] [SKL only] igt@*@* - dmesg-warn - *ERROR* Potential atomic update failure on pipe A
Summary: [CI] [SKL only] igt@*@* - dmesg-warn - *ERROR* Potential atomic update failur...
Status: REOPENED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: high normal
Assignee: Maarten Lankhorst
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
: 91883 (view as bug list)
Depends on:
Blocks: 105981
  Show dependency treegraph
 
Reported: 2018-03-16 06:49 UTC by Marta Löfstedt
Modified: 2019-10-05 09:49 UTC (History)
6 users (show)

See Also:
i915 platform: KBL, SKL
i915 features: display/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Marta Löfstedt 2018-03-16 07:40:51 UTC
Although previous links appear to be on PSR related tests here are some others:

 https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@gem_ppgtt@blt-vs-render-ctxn.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@syncobj_wait@multi-wait-submitted.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@gem_mmap_gtt@fault-concurrent.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@gem_mmap_wc@write-cpu-read-wc-unflushed.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@gem_pread@uncached.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@gem_mmap_wc@write-gtt.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@sw_sync@sync_multi_producer_single_consumer.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6700hq/igt@kms_draw_crc@draw-method-rgb565-pwrite-xtiled.html

Also the fi-skl_6600u is hit:
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6600u/igt@gem_pread@uncached.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6600u/igt@gem_mmap_wc@write-gtt.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6600u/igt@sw_sync@sync_multi_producer_single_consumer.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6600u/igt@kms_draw_crc@draw-method-rgb565-pwrite-xtiled.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6600u/igt@kms_chv_cursor_fail@pipe-c-64x64-left-edge.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6600u/igt@syncobj_wait@wait-all-for-submit-snapshot.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-6600u/igt@kms_atomic@plane_overlay_legacy.html
Comment 2 Marta Löfstedt 2018-03-16 12:10:11 UTC
This is poular on SKL:

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@gem_mmap_gtt@basic-small-bo-tiledy.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@kms_psr_sink_crc@cursor_render.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@gem_mmap_gtt@basic-small-bo.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@kms_psr_sink_crc@sprite_render.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@kms_psr_sink_crc@cursor_mmap_gtt_waiting.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@gem_mmap_wc@write.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@kms_psr_sink_crc@primary_page_flip.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@drm_read@empty-block.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@gem_cpu_reloc@full.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@gem_pwrite@display.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6700hq/igt@gem_pwrite@small-cpu-fbr.html


https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@drm_read@empty-block.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@gem_cpu_reloc@full.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@gem_pwrite@display.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@gem_pwrite@small-cpu-fbr.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@gem_mmap_gtt@basic-copy.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@gem_exec_reuse@single.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@syncobj_wait@multi-wait-for-submit-submitted.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_2/fi-skl-6600u/igt@gem_exec_blt@normal.html
Comment 3 Marta Löfstedt 2018-03-20 12:40:47 UTC
Note, this appear to only be hitting out SKl laptops, i.e. eDP...
Comment 8 Marta Löfstedt 2018-04-06 08:13:55 UTC
some new examples from drmtip_12:
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700hq/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size.html

It is surprisingly frequent to hit new test on 2 machines on the same run. They do have the same testlist, so is there some context leak going on here?

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6600u/igt@gem_mmap_gtt@basic-small-copy-odd.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700hq/igt@gem_mmap_gtt@basic-small-copy-odd.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6600u/igt@syncobj_wait@multi-wait-all-for-submit-unsubmitted-signaled.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700hq/igt@syncobj_wait@multi-wait-all-for-submit-unsubmitted-signaled.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6600u/igt@gem_pwrite@small-gtt-forwards.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700hq/igt@gem_pwrite@small-gtt-forwards.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6600u/igt@kms_frontbuffer_tracking@fbcpsr-slowdraw.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700hq/igt@kms_frontbuffer_tracking@fbcpsr-slowdraw.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6600u/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt.html
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700hq/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-blt.html
Comment 9 Lakshmi 2018-08-27 09:51:17 UTC
*** Bug 91883 has been marked as a duplicate of this bug. ***
Comment 10 FadeMind 2018-11-01 15:28:36 UTC
Hello, this is not mine directly bug report. One manjaro forum user report issue for Kabylake Refresh 

System:    Host: manan-pc Kernel: 4.19.0-3-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: KDE Plasma 5.14.2 
           tk: Qt 5.11.2 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: LENOVO product: 20L5S08M00 v: ThinkPad T480 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: LENOVO model: 20L5S08M00 v: SDK0J40697 WIN serial: <filter> UEFI: LENOVO v: N24ET42W (1.17 ) date: 09/14/2018 
Battery:   ID-1: BAT1 charge: 48.7 Wh condition: 48.8/47.5 Wh (103%) volts: 12.5/10.8 model: LGC 01AV491 type: Li-ion 
           serial: <filter> status: Unknown cycles: 43 
CPU:       Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31880 
           Speed: 800 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5917 
           Device-2: NVIDIA GP108M [GeForce MX150] vendor: Lenovo driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:1d10 
           Display: x11 server: X.Org 1.20.3 driver: intel,modesetting unloaded: nouveau alternate: fbdev,nv,vesa 
           compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.2.3 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           chip ID: 8086:9d71 
           Sound Server: ALSA v: k4.19.0-3-MANJARO 
Network:   Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6 
           chip ID: 8086:15d8 
           IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter> 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: d000 bus ID: 03:00.0 chip ID: 8086:24fd 
           IF: wlp3s0 state: up mac: <filter> 
Drives:    Local Storage: total: 476.94 GiB used: 6.94 GiB (1.5%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000L7 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
           serial: <filter> rev: 3L2QEXA7 scheme: GPT 
Partition: ID-1: / size: 106.09 GiB used: 6.94 GiB (6.5%) fs: ext4 dev: /dev/nvme0n1p6 
           uuid: 5244c15b-6adf-448c-9920-3be4b52a1c31 
           ID-2: /boot/efi size: 798.4 MiB used: 264 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p5 uuid: E57E-BD5C 
Unmounted: ID-1: /dev/nvme0n1p1 size: 260.0 MiB fs: vfat label: SYSTEM uuid: F6A8-D891 
           ID-2: /dev/nvme0n1p2 size: 16.0 MiB fs: <root required> label: N/A uuid: N/A 
           ID-3: /dev/nvme0n1p3 size: 366.62 GiB fs: ntfs label: N/A uuid: 12E0FDAEE0FD9865 
           ID-4: /dev/nvme0n1p4 size: 1000.0 MiB fs: ntfs label: WinRE_DRV uuid: 30E0ACE5E0ACB290 
Sensors:   System Temperatures: cpu: 53.0 C mobo: N/A gpu: nouveau temp: 511 C 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 213 Uptime: 3m Memory: 15.44 GiB used: 1.02 GiB (6.6%) Init: systemd v: 2 39 Compilers: gcc: 8.2.1 
           Shell: bash v: 4.4.23 running in: yakuake inxi: 3.0.27

Nov 01 09:12:44 manan-pc kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [python3:567]
Nov 01 09:12:43 manan-pc kernel: [drm:intel_pipe_update_end [i915]] ERROR Atomic update failure on pipe A (start=26643 end=26644) time 7310 us, min 1073, max 1079, scanline start 616, end 1068
Nov 01 09:13:00 manan-pc kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Nov 01 09:13:00 manan-pc kernel: rcu: 7-…0: (0 ticks this GP) idle=9e6/1/0x4000000000000000 softirq=6747/6747 fqs=23759 last_accelerate: 9c00/b546, nonlazy_posted: 0, L.
Nov 01 09:13:00 manan-pc kernel: rcu: (detected by 2, t=72007 jiffies, g=20713, q=117355)

PLEASE read thread https://forum.manjaro.org/t/for-some-reason-i-am-not-able-to-shut-down-or-restart-my-laptop-gets-frozen/63665/

for details.
Comment 11 Martin Peres 2018-11-01 16:37:59 UTC
(In reply to FadeMind from comment #10)
> Hello, this is not mine directly bug report. One manjaro forum user report
> issue for Kabylake Refresh 
> 
> System:    Host: manan-pc Kernel: 4.19.0-3-MANJARO x86_64 bits: 64 compiler:
> gcc v: 8.2.1 Desktop: KDE Plasma 5.14.2 
>            tk: Qt 5.11.2 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
> Machine:   Type: Laptop System: LENOVO product: 20L5S08M00 v: ThinkPad T480
> serial: <filter> Chassis: type: 10 
>            serial: <filter> 
>            Mobo: LENOVO model: 20L5S08M00 v: SDK0J40697 WIN serial: <filter>
> UEFI: LENOVO v: N24ET42W (1.17 ) date: 09/14/2018 
> Battery:   ID-1: BAT1 charge: 48.7 Wh condition: 48.8/47.5 Wh (103%) volts:
> 12.5/10.8 model: LGC 01AV491 type: Li-ion 
>            serial: <filter> status: Unknown cycles: 43 
> CPU:       Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT
> MCP arch: Kaby Lake rev: A L2 cache: 8192 KiB 
>            flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips:
> 31880 
>            Speed: 800 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 800 2:
> 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
> Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v:
> kernel bus ID: 00:02.0 chip ID: 8086:5917 
>            Device-2: NVIDIA GP108M [GeForce MX150] vendor: Lenovo driver:
> nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:1d10 
>            Display: x11 server: X.Org 1.20.3 driver: intel,modesetting
> unloaded: nouveau alternate: fbdev,nv,vesa 
>            compositor: kwin_x11 resolution: 1920x1080~60Hz 
>            OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2)
> v: 4.5 Mesa 18.2.3 compat-v: 3.0 
>            direct render: Yes 
> Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver:
> snd_hda_intel v: kernel bus ID: 00:1f.3 
>            chip ID: 8086:9d71 
>            Sound Server: ALSA v: k4.19.0-3-MANJARO 
> Network:   Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v:
> 3.2.6-k port: efa0 bus ID: 00:1f.6 
>            chip ID: 8086:15d8 
>            IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac:
> <filter> 
>            Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel
> port: d000 bus ID: 03:00.0 chip ID: 8086:24fd 
>            IF: wlp3s0 state: up mac: <filter> 
> Drives:    Local Storage: total: 476.94 GiB used: 6.94 GiB (1.5%) 
>            ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HAJQ-000L7
> size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
>            serial: <filter> rev: 3L2QEXA7 scheme: GPT 
> Partition: ID-1: / size: 106.09 GiB used: 6.94 GiB (6.5%) fs: ext4 dev:
> /dev/nvme0n1p6 
>            uuid: 5244c15b-6adf-448c-9920-3be4b52a1c31 
>            ID-2: /boot/efi size: 798.4 MiB used: 264 KiB (0.0%) fs: vfat
> dev: /dev/nvme0n1p5 uuid: E57E-BD5C 
> Unmounted: ID-1: /dev/nvme0n1p1 size: 260.0 MiB fs: vfat label: SYSTEM uuid:
> F6A8-D891 
>            ID-2: /dev/nvme0n1p2 size: 16.0 MiB fs: <root required> label:
> N/A uuid: N/A 
>            ID-3: /dev/nvme0n1p3 size: 366.62 GiB fs: ntfs label: N/A uuid:
> 12E0FDAEE0FD9865 
>            ID-4: /dev/nvme0n1p4 size: 1000.0 MiB fs: ntfs label: WinRE_DRV
> uuid: 30E0ACE5E0ACB290 
> Sensors:   System Temperatures: cpu: 53.0 C mobo: N/A gpu: nouveau temp: 511
> C 
>            Fan Speeds (RPM): cpu: 0 
> Info:      Processes: 213 Uptime: 3m Memory: 15.44 GiB used: 1.02 GiB (6.6%)
> Init: systemd v: 2 39 Compilers: gcc: 8.2.1 
>            Shell: bash v: 4.4.23 running in: yakuake inxi: 3.0.27
> 
> Nov 01 09:12:44 manan-pc kernel: watchdog: BUG: soft lockup - CPU#2 stuck
> for 22s! [python3:567]
> Nov 01 09:12:43 manan-pc kernel: [drm:intel_pipe_update_end [i915]] ERROR
> Atomic update failure on pipe A (start=26643 end=26644) time 7310 us, min
> 1073, max 1079, scanline start 616, end 1068
> Nov 01 09:13:00 manan-pc kernel: rcu: INFO: rcu_preempt detected stalls on
> CPUs/tasks:
> Nov 01 09:13:00 manan-pc kernel: rcu: 7-…0: (0 ticks this GP)
> idle=9e6/1/0x4000000000000000 softirq=6747/6747 fqs=23759 last_accelerate:
> 9c00/b546, nonlazy_posted: 0, L.
> Nov 01 09:13:00 manan-pc kernel: rcu: (detected by 2, t=72007 jiffies,
> g=20713, q=117355)
> 
> PLEASE read thread
> https://forum.manjaro.org/t/for-some-reason-i-am-not-able-to-shut-down-or-
> restart-my-laptop-gets-frozen/63665/
> 
> for details.

Funny timing, I was about to close the bug because it has not been seen since drmtip_92 (3 months, 1 week / 1329 runs ago).

Please open a new bug if you can reproduce with 4.19 :)
Comment 12 pbazan 2019-09-03 14:16:55 UTC
started to appear in dmesg after latest upgrade that included kernel

dmesg

[49529.776550] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=990487 end=990488) time 296 us, min 1073, max 1079, scanline start 1069, end 1083
[49549.010097] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=991641 end=991642) time 289 us, min 1073, max 1079, scanline start 1069, end 1084
[49588.660536] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=994020 end=994021) time 315 us, min 1073, max 1079, scanline start 1063, end 1084
[49601.927316] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=994816 end=994817) time 132 us, min 1073, max 1079, scanline start 1072, end 1081
[49658.711340] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=998223 end=998224) time 177 us, min 1073, max 1079, scanline start 1071, end 1079
[49692.845142] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=1000271 end=1000272) time 152 us, min 1073, max 1079, scanline start 1072, end 1082
[49697.045349] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=1000523 end=1000524) time 197 us, min 1073, max 1079, scanline start 1072, end 1083
[49702.162041] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=1000830 end=1000831) time 234 us, min 1073, max 1079, scanline start 1067, end 1080
[49718.678822] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=1001821 end=1001822) time 188 us, min 1073, max 1079, scanline start 1071, end 1081
[49732.312328] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=1002639 end=1002640) time 192 us, min 1073, max 1079, scanline start 1067, end 1079
[49809.680065] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=1007281 end=1007282) time 108 us, min 1073, max 1079, scanline start 1072, end 108

uname -r

5.2.10-arch1-1-ARCH
Comment 13 Lakshmi 2019-09-06 11:38:58 UTC
(In reply to pbazan from comment #12)
> started to appear in dmesg after latest upgrade that included kernel
> 
> dmesg
> 
> [49529.776550] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=990487 end=990488) time 296 us, min 1073, max 1079,
> scanline start 1069, end 1083
> [49549.010097] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=991641 end=991642) time 289 us, min 1073, max 1079,
> scanline start 1069, end 1084
> [49588.660536] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=994020 end=994021) time 315 us, min 1073, max 1079,
> scanline start 1063, end 1084
> [49601.927316] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=994816 end=994817) time 132 us, min 1073, max 1079,
> scanline start 1072, end 1081
> [49658.711340] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=998223 end=998224) time 177 us, min 1073, max 1079,
> scanline start 1071, end 1079
> [49692.845142] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=1000271 end=1000272) time 152 us, min 1073, max
> 1079, scanline start 1072, end 1082
> [49697.045349] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=1000523 end=1000524) time 197 us, min 1073, max
> 1079, scanline start 1072, end 1083
> [49702.162041] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=1000830 end=1000831) time 234 us, min 1073, max
> 1079, scanline start 1067, end 1080
> [49718.678822] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=1001821 end=1001822) time 188 us, min 1073, max
> 1079, scanline start 1071, end 1081
> [49732.312328] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=1002639 end=1002640) time 192 us, min 1073, max
> 1079, scanline start 1067, end 1079
> [49809.680065] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
> failure on pipe B (start=1007281 end=1007282) time 108 us, min 1073, max
> 1079, scanline start 1072, end 108
> 
> uname -r
> 
> 5.2.10-arch1-1-ARCH

What is the impact of this other the error messages in dmesg?  Asking to know how serious is the issue. Can you please attach the log from boot with kernel parameters drm.debug=0x1e log_buf_len=4M.
This issue could be a duplicate to Bug 106107. But not 100% sure.
Comment 14 Claudiu Ion 2019-10-05 09:49:32 UTC
Hello. 

I managed to solve this error by enabling early KMS for the Intel graphics driver:

1. Edit /etc/mkinitcpio.conf and add i915 to MODULES.
2. Regenerate the initramfs (mkinitcpio -p linux)
3. Reboot

uname -r
5.3.1-arch1-1-ARCH


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.