Bug 1219826

Summary: VT is unusable on i915
Product: [Fedora] Fedora Reporter: Neal Becker <ndbecker2>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 22CC: ajax, awilliam, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, mhayden, samuel-rhbugs, satellitgo, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:52:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
log
none
log none

Description Neal Becker 2015-05-08 11:41:08 UTC
Created attachment 1023458 [details]
log

Description of problem:

Testing f22-kde-tc2 live usb
When switched to VT (alt-ctrl-F2), primary screen starts flashing and is unusable. Fortunately, I have a 2nd screen which is OK.

Switching back to graphic mode, primary screen remains unusable.  It is still flashing and tearing.

Booting with drm.debug=14, I captured journalctl log output.
On the VT on the 2nd screen, I saw:
drm: intel_cpu_fifo_underrun_irq_handler [i915] *ERROR* CPU pipe A FIFO underrun

After this, the log shows various segfaults from kde components.
 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Adam Williamson 2015-05-09 00:10:28 UTC
It would be good if you could reproduce it with 'drm.debug=14' as a kernel parameter and attach the journalctl log from that - thanks!

Comment 2 Neal Becker 2015-05-10 17:22:36 UTC
Created attachment 1024021 [details]
log

OK, this should be with drm.debug=14.  At least, I checked /proc/cmdline and saw it there.

Comment 3 Adam Williamson 2015-05-11 20:52:24 UTC
Huh, still not much in there. I don't think I have any more ideas, it's up to ajax :/

Comment 4 Neal Becker 2015-05-12 11:03:16 UTC
The 1 thing is the buffer underrun - but it's not clear if this is the cause or effect.

Comment 5 Adam Williamson 2015-05-12 19:43:00 UTC
The odd thing is I'd usually expect that kind of error to be accompanied by more data when booted with drm.debug=14 , but it seems like it wasn't...

Comment 6 Neal Becker 2015-06-02 11:46:53 UTC
Just updated F21 machine to
4.0.4-202.fc21.x86_64

Now it suffers from the same problem as when I tested F22 using live usb.

I did notice this message on boot - BEFORE I tried the vt and activated the error, don't know if it's relevant:

Jun  2 03:42:04 nbecker2 kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Jun  2 03:42:04 nbecker2 kernel: i915 0000:00:02.0: registered panic notifier
Jun  2 03:42:04 nbecker2 kernel: [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!

Comment 7 Major Hayden 🤠 2015-06-02 13:12:17 UTC
This *might* be related to another bug: https://bugzilla.kernel.org/show_bug.cgi?id=95741

I'm seeing this issue on a third gen X1 Carbon and Dell XPS 13 9343 (2015 model).  I haven't tried the i915.enable_ips=0 fix yet.

Comment 8 Neal Becker 2015-06-02 13:41:57 UTC
Also 3rd gen X1 carbon here (2015).

I just tried i915.enable_ips=0 and it DOES fix the problem.

https://bugzilla.kernel.org/show_bug.cgi?id=95741

Comment 9 Fedora End Of Life 2016-07-19 18:52:29 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.