Error in i915 driver
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linux |
Fix Released
|
Medium
|
|||
| linux (Ubuntu) |
Low
|
Unassigned | |||
| Wily |
Low
|
Unassigned | |||
Bug Description
The 7th of september I lost my Xorg display on wily. I was always in failsafe mode.
I still could get openbox to run, which was still loading i915, but didn't consume any 3D/advanced instruction I thinK.
I didn't got too much time to go beyond.
As I got also a btrfs kernel dump message, so I checked my ram at least with memtest86+, all was OK.
Reverting to vivid allowed me to be back on unity.
Wily-amd64, kernel 4.2.0.7-
Here are the traces I got:
[ 22.335530] [drm:intel_
[ 22.335535] ------------[ cut here ]------------
[ 22.335562] WARNING: CPU: 0 PID: 2190 at /build/
[ 22.335564] pipe state doesn't match!
[ 22.335566] Modules linked in: ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6_tables overlay xt_addrtype xt_conntrack xt_CHECKSUM ax88179_178a iptable_mangle usbnet ipt_MASQUERADE rtsx_usb_ms nf_nat_
[ 22.335625] uvcvideo videobuf2_vmalloc snd_hda_
[ 22.335682] rtsx_usb_sdmmc rtsx_usb i915 i2c_algo_bit drm_kms_helper drm psmouse ahci libahci sdhci_acpi sdhci video i2c_hid hid
[ 22.335698] CPU: 0 PID: 2190 Comm: Xorg Tainted: G W 4.2.0-7-lowlatency #7-Ubuntu
[ 22.335700] Hardware name: LENOVO 20344/INVALID, BIOS 96CN25WW(V1.11) 07/09/2014
[ 22.335703] ffffffffc02081e8 ffff8800995c77e8 ffffffff817bdf25 0000000000000000
[ 22.335708] ffff8800995c7838 ffff8800995c7828 ffffffff81078016 ffff8800995c7858
[ 22.335712] ffff8800995c78c0 ffff880035571000 0000000000000001 ffff880035571350
[ 22.335717] Call Trace:
[ 22.335724] [<ffffffff817bd
[ 22.335729] [<ffffffff81078
[ 22.335734] [<ffffffff81078
[ 22.335758] [<ffffffffc019b
[ 22.335781] [<ffffffffc019c
[ 22.335809] [<ffffffffc01af
[ 22.335834] [<ffffffffc01b0
[ 22.335852] [<ffffffffc0088
[ 22.335870] [<ffffffffc008c
[ 22.335883] [<ffffffffc007d
[ 22.335898] [<ffffffffc008c
[ 22.335903] [<ffffffff81205
[ 22.335908] [<ffffffff81083
[ 22.335912] [<ffffffff8120f
[ 22.335916] [<ffffffff81206
[ 22.335921] [<ffffffff817c4
[ 22.335924] ---[ end trace 7e8588f0d9eb10f9 ]---
This issue seems to have been fixed in v4.2-rc8. Closing this.
I am seeing this on a Dell E7240 (Haswell) freshly booted into 4.2. The issue was not seen on 4.1.2 or previous.
[ 2698.293746] [drm:check_
[ 2698.293753] ------------[ cut here ]------------
[ 2698.293761] WARNING: CPU: 0 PID: 1833 at drivers/
[ 2698.293763] pipe state doesn't match!
[ 2698.293780] Modules linked in: fuse ctr ccm xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_
[ 2698.293911] snd_hwdep snd_hda_core snd_pcm snd_timer tpm_tis 8250 serial_core evdev battery ac processor md_mod tpm_rng tpm rng_core efivarfs autofs4 btrfs xor raid6_pq algif_skcipher af_alg crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ehci_pci ehci_hcd sdhci_pci xhci_pci xhci_hcd thermal sdhci_acpi sdhci mmc_core i2c_hid hid jitterentropy_rng sha256_ssse3 sha256_generic hmac drbg ansi_cprng
[ 2698.293977] CPU: 0 PID: 1833 Comm: Xorg Not tainted 4.2.0 #1
[ 2698.293980] Hardware name: Dell Inc. Latitude E7240/07RPNV, BIOS A15 05/19/2015
[ 2698.293998] 0000000000000000 ffffffff819c26e0 ffffffff816898ee ffff8804030bf858
[ 2698.294004] ffffffff810b394c ffff8800d5ba9400 ffff88040c3d1000 ffff88040ab40000
[ 2698.294009] 0000000000000001 ffff88040c3d1350 ffffffff810b39c5 ffffffff819f0f1f
[ 2698.294015] Call Trace:
[ 2698.294024] [<ffffffff81689
[ 2698.294048] [<ffffffff810b3
[ 2698.294054] [<ffffffff810b3
[ 2698.294059] [<ffffffff81465
[ 2698.294066] [<ffffffff81442
[ 2698.294093] [<ffffffff81478
[ 2698.294101] [<ffffffff81479
[ 2698.294108] [<ffffffff813f6
[ 2698.294130] [<ffffffff813f7
[ 2698.294137] [<ffffffff813fb
[ 2698.294143] [<ffffffff813ed
[ 2698.294151] [<ffffffffc024c
[ 2698.294175] [<ffffffff811e7
[ 2698.294183] [<ffffffff810bd
[ 2698.294189] [<ffffffff811e7
[ 2698.294194] [<ffffffff810c0
[ 2698.294217] [<ffffffff8168f...
Reverting d2944cf21305c75
(In reply to Emil Renner Berthing from comment #3)
> Reverting d2944cf21305c75
commit d2944cf21305c75
Author: Maarten Lankhorst <email address hidden>
Date: Tue Aug 11 12:31:11 2015 +0200
drm/i915: Commit planes on each crtc separately.
|
|
#7 |
That commit fixes another issue unfortunately. It looks like post_enable_primary might not be called in some cases.
Can I have a drm.debug=0x1e log of the vt switching?
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1496433
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| Changed in linux: | |
| importance: | Unknown → Medium |
| status: | Unknown → Incomplete |
| tags: | added: needs-apport-collect |
| Changed in linux (Ubuntu Wily): | |
| importance: | Undecided → Low |
Created attachment 118386
Pipe state mismatch during screen blank/unblank
I didn't manage to trigger on a simple VT switch, but doing a screen blank/unblank (manual lock request in GNOME) triggered the attached warning.
I have upgraded to 4.3-rc2 and have not so far been able to reproduce the problem. I will update here if I can do so.
*** Bug 92187 has been marked as a duplicate of this bug. ***
(In reply to Jonathan McDowell from comment #7)
> I have upgraded to 4.3-rc2 and have not so far been able to reproduce the
> problem. I will update here if I can do so.
Presumed fixed, please reopen if the problem reappears with 4.3-rc2 or later.
| Changed in linux: | |
| status: | Incomplete → Fix Released |


Created attachment 117467
dmesg - warning when switching from X to tty
Using 4.2-rc4 on my Haswell laptop I get the warning you can see in the dmesg attached whenever I switch from X to tty. The same happens using 4.2-rc1.
This never happened before.