Bug 101058 - [DP] [BDW] Multiple errors in i915
Summary: [DP] [BDW] Multiple errors in i915
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Maël Lavault
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-16 11:55 UTC by Maël Lavault
Modified: 2018-04-20 14:10 UTC (History)
1 user (show)

See Also:
i915 platform: BDW
i915 features: display/DP


Attachments

Description Maël Lavault 2017-05-16 11:55:04 UTC
On my iris 6100 pro on a macbook pro, kernel 4.11.0 I get a lot of errors like those using 3 DP displays with daisy chaining:

[drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
[drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C FIFO underrun
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
Comment 1 Jani Nikula 2017-05-17 10:11:13 UTC
(In reply to Maël Lavault from comment #0)
> On my iris 6100 pro on a macbook pro, kernel 4.11.0 I get a lot of errors
> like those using 3 DP displays with daisy chaining:

Is this a regression?

Please add drm.debug=14 module parameter, and attach dmesg from boot to the problem.
Comment 2 Maël Lavault 2017-05-17 14:52:20 UTC
I'm not sure if this is a regression or not, displayport with daisy chaining never worked flawlessly.

I will try that, thanks !
Comment 3 Jani Saarinen 2017-06-08 07:14:24 UTC
Reporter, please provide data asked, thanks. 
If this is not valid anymore, please close.
Comment 4 Maël Lavault 2017-06-08 07:18:33 UTC
The thing is, those errors do not happen on boot, they happen randomly while using the computer. I added the parameter and i'm waiting for it to happen.
Comment 5 Elizabeth 2017-07-20 19:56:51 UTC
(In reply to Maël Lavault from comment #4)
> The thing is, those errors do not happen on boot, they happen randomly while
> using the computer. I added the parameter and i'm waiting for it to happen.

Changing priority since is very sporadic. Thanks.
Comment 6 Elizabeth 2017-08-24 20:44:59 UTC
Hello Maël, any luck reproducing this bug? Thank you.
Comment 7 Maël Lavault 2017-08-29 09:45:19 UTC
Yes I get it multiple time a day and my gnome shell completely crash and sometimes restart to login screen, sometimes I have to reboot. I'm using kernel 4.12.8 currently.
Comment 8 Elizabeth 2017-08-29 15:22:10 UTC
(In reply to Maël Lavault from comment #7)
> Yes I get it multiple time a day and my gnome shell completely crash and
> sometimes restart to login screen, sometimes I have to reboot. I'm using
> kernel 4.12.8 currently.
Then have you been able to get a dmesg with the "drm.debug=14" parameter on it? 
As you mention problem doesn't occurs at boot, probably you'll need to increase dmesg size with "log_bug_len=4M" (or bigger than 4M).
Comment 9 Elizabeth 2017-10-06 18:54:59 UTC
Sorry for pestering. Any pattern identified or log collected so far? Thank you.
Comment 10 Jani Saarinen 2018-03-29 07:10:42 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 11 Jani Saarinen 2018-04-20 14:10:49 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.