Bug 104740 - Atomic update failure on pipe B with kernel 4.15
Summary: Atomic update failure on pipe B with kernel 4.15
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-22 22:08 UTC by Amel Rastoder
Modified: 2018-04-20 15:55 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features: display/atomic

Attachments

Description Amel Rastoder 2018-01-22 22:08:41 UTC 
I get the following error message on startup using kernel 4.15. No issues with kernel 4.14 and 4.9.

kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=406182 end=406183) time 159 us, min 1073, max 1079, scanline start 1069, end 1080

Machine:   Device: laptop System: LENOVO product: 20FRS05B00 v: ThinkPad X1 Carbon 4th serial: N/A
           Mobo: LENOVO model: 20FRS05B00 v: SDK0J40697 WIN serial: N/A
           UEFI: LENOVO v: N1FET34W (1.08 ) date: 01/21/2016
Comment 1 Elizabeth 2018-01-23 18:31:40 UTC 
Hello Amel, could you please attach full dmesg with debug information, drm.debug=0x1e log_bug_len=2M parameters on grub. Thanks.
Comment 2 Jani Saarinen 2018-03-29 07:11:25 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 3 Jani Saarinen 2018-04-20 15:53:52 UTC 
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.