X crashes back to login screen when running firefox, chrome, etc.

Bug #1251873 reported by Konstantinos Filios
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I recently upgraded from 13.04 to 13.10. Since then, whenever I try to start certain programs such as Mozilla Firefox, Google Chrome (not Chromium), fglrxinfo, etc., I see a blank screen for a second (seems like X crashes) and I'm taken back to the X login screen.

dmesg gives the following output when the crash occurs:

[ 126.337872] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags (expected 1, found 0)
[ 126.337882] ------------[ cut here ]------------
[ 126.337937] WARNING: CPU: 2 PID: 1953 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x58f/0x9c0 [i915]()
[ 126.337940] pipe state doesn't match!
[ 126.337943] Modules linked in: parport_pc(F) ppdev(F) cuse bnep rfcomm x86_pkg_temp_thermal intel_powerclamp coretemp kvm(F) crct10dif_pclmul(F) crc32_pclmul(F) ghash_clmulni_intel(F) cryptd(F) hp_wmi sparse_keymap arc4(F) uvcvideo iwldvm videobuf2_vmalloc videobuf2_memops mac80211 videobuf2_core videodev joydev(F) iwlwifi snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) btusb cfg80211 snd_page_alloc(F) microcode(F) hp_accel mei_me snd_timer(F) mei bluetooth snd(F) psmouse(F) soundcore(F) rtsx_pci_ms lis3lv02d memstick serio_raw(F) input_polldev lpc_ich mac_hid binfmt_misc(F) usbserial lp(F) parport(F) hid_generic usbhid hid rtsx_pci_sdmmc i915 r8169 i2c_algo_bit drm_kms_helper mii(F) drm sdhci_pci sdhci rtsx_pci ahci(F) libahci(F) wmi video(F) [last unloaded: amd_iommu_v2]
[ 126.338054] CPU: 2 PID: 1953 Comm: Xorg Tainted: PF W O 3.11.0-13-generic #20-Ubuntu
[ 126.338058] Hardware name: Hewlett-Packard HP Pavilion dv6 Notebook PC/17F9, BIOS F.01 08/10/2011
[ 126.338063] 0000000000000009 ffff8801558c5898 ffffffff816e54ba ffff8801558c58e0
[ 126.338073] ffff8801558c58d0 ffffffff81061dbd ffff8801594a76d0 0000000000000001
[ 126.338080] ffff880154d44000 ffff8801594a7000 ffff880154d44478 ffff8801558c5930
[ 126.338087] Call Trace:
[ 126.338101] [<ffffffff816e54ba>] dump_stack+0x45/0x56
[ 126.338112] [<ffffffff81061dbd>] warn_slowpath_common+0x7d/0xa0
[ 126.338120] [<ffffffff81061e2c>] warn_slowpath_fmt+0x4c/0x50
[ 126.338153] [<ffffffffa00f0a0f>] check_crtc_state+0x58f/0x9c0 [i915]
[ 126.338188] [<ffffffffa00fbc63>] intel_modeset_check_state+0x2c3/0x770 [i915]
[ 126.338216] [<ffffffffa00fc185>] intel_set_mode+0x25/0x30 [i915]
[ 126.338244] [<ffffffffa00fc9d2>] intel_crtc_set_config+0x742/0x910 [i915]
[ 126.338277] [<ffffffffa0067f8d>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
[ 126.338303] [<ffffffffa006a9c7>] drm_mode_setcrtc+0xf7/0x650 [drm]
[ 126.338332] [<ffffffffa00f1f92>] ? intel_crtc_load_lut+0xd2/0x170 [i915]
[ 126.338355] [<ffffffffa005b212>] drm_ioctl+0x532/0x660 [drm]
[ 126.338368] [<ffffffff816ec889>] ? _raw_spin_unlock_bh+0x19/0x20
[ 126.338379] [<ffffffff811b8bf5>] do_vfs_ioctl+0x2e5/0x4d0
[ 126.338388] [<ffffffff811b8e61>] SyS_ioctl+0x81/0xa0
[ 126.338397] [<ffffffff816f529d>] system_call_fastpath+0x1a/0x1f
[ 126.338402] ---[ end trace 59b005c4544df4fe ]---
[ 126.538153] [drm:intel_pipe_config_compare] *ERROR* mismatch in adjusted_mode.flags (expected 1, found 0)
[ 126.538164] ------------[ cut here ]------------
[ 126.538222] WARNING: CPU: 0 PID: 1953 at /build/buildd/linux-3.11.0/drivers/gpu/drm/i915/intel_display.c:8292 check_crtc_state+0x58f/0x9c0 [i915]()
[ 126.538226] pipe state doesn't match!
[ 126.538228] Modules linked in: parport_pc(F) ppdev(F) cuse bnep rfcomm x86_pkg_temp_thermal intel_powerclamp coretemp kvm(F) crct10dif_pclmul(F) crc32_pclmul(F) ghash_clmulni_intel(F) cryptd(F) hp_wmi sparse_keymap arc4(F) uvcvideo iwldvm videobuf2_vmalloc videobuf2_memops mac80211 videobuf2_core videodev joydev(F) iwlwifi snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep(F) snd_pcm(F) btusb cfg80211 snd_page_alloc(F) microcode(F) hp_accel mei_me snd_timer(F) mei bluetooth snd(F) psmouse(F) soundcore(F) rtsx_pci_ms lis3lv02d memstick serio_raw(F) input_polldev lpc_ich mac_hid binfmt_misc(F) usbserial lp(F) parport(F) hid_generic usbhid hid rtsx_pci_sdmmc i915 r8169 i2c_algo_bit drm_kms_helper mii(F) drm sdhci_pci sdhci rtsx_pci ahci(F) libahci(F) wmi video(F) [last unloaded: amd_iommu_v2]
[ 126.538338] CPU: 0 PID: 1953 Comm: Xorg Tainted: PF W O 3.11.0-13-generic #20-Ubuntu
[ 126.538342] Hardware name: Hewlett-Packard HP Pavilion dv6 Notebook PC/17F9, BIOS F.01 08/10/2011
[ 126.538347] 0000000000000009 ffff8801558c5898 ffffffff816e54ba ffff8801558c58e0
[ 126.538356] ffff8801558c58d0 ffffffff81061dbd ffff8801594a76d0 0000000000000001
[ 126.538363] ffff880154d44000 ffff8801594a7000 ffff880154d44478 ffff8801558c5930
[ 126.538371] Call Trace:
[ 126.538387] [<ffffffff816e54ba>] dump_stack+0x45/0x56
[ 126.538397] [<ffffffff81061dbd>] warn_slowpath_common+0x7d/0xa0
[ 126.538405] [<ffffffff81061e2c>] warn_slowpath_fmt+0x4c/0x50
[ 126.538437] [<ffffffffa00f0a0f>] check_crtc_state+0x58f/0x9c0 [i915]
[ 126.538472] [<ffffffffa00fbc63>] intel_modeset_check_state+0x2c3/0x770 [i915]
[ 126.538500] [<ffffffffa00fc185>] intel_set_mode+0x25/0x30 [i915]
[ 126.538528] [<ffffffffa00fc9d2>] intel_crtc_set_config+0x742/0x910 [i915]
[ 126.538560] [<ffffffffa0067f8d>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
[ 126.538586] [<ffffffffa006a9c7>] drm_mode_setcrtc+0xf7/0x650 [drm]
[ 126.538615] [<ffffffffa00f1f92>] ? intel_crtc_load_lut+0xd2/0x170 [i915]
[ 126.538638] [<ffffffffa005b212>] drm_ioctl+0x532/0x660 [drm]
[ 126.538651] [<ffffffff816ec889>] ? _raw_spin_unlock_bh+0x19/0x20
[ 126.538662] [<ffffffff811b8bf5>] do_vfs_ioctl+0x2e5/0x4d0
[ 126.538671] [<ffffffff811b8e61>] SyS_ioctl+0x81/0xa0
[ 126.538680] [<ffffffff816f529d>] system_call_fastpath+0x1a/0x1f
[ 126.538684] ---[ end trace 59b005c4544df4ff ]---

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Sat Nov 16 18:17:18 2013
InstallationDate: Installed on 2012-07-25 (478 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MarkForUpload: True
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to saucy on 2013-10-20 (27 days ago)

Revision history for this message
Konstantinos Filios (konfilios) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Thiago Martins (tcmartins) wrote :

I have the same error at intel_set_mode+0x25/0x30 [i915]. X won't always come back to login screen, but screen turns black and every X client dies.

I can reproduce it consistently by triggering resolution changes. Important information: I am using kde with kwin as window manager (this appears to be OP's case as well, since his "InstallationMedia" is listed as "Kubuntu 12.04").

Revision history for this message
penalvch (penalvch) wrote :

Konstantinos Filios, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux REPLACE-WITH-BUG-NUMBER

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

affects: xorg (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-kernel-logs needs-upstream-testing regression-potential
Revision history for this message
Thiago Martins (tcmartins) wrote :

Bug appears to be fixed in kernel 3.11.0-14

Revision history for this message
Konstantinos Filios (konfilios) wrote :

Sorry for the late response.

This bug was a major annoyance, so I re-installed a fresh copy of 13.04 a couple of weeks after filing the bug and everything works ok again.

If there's a way I can provide more info without re-upgrading to 13.10 (thus risking to make the system unusable again) I'd be happy to help.

Thanks for your feedback anyway

Revision history for this message
penalvch (penalvch) wrote :

Konstantinos Filios, you could test a live environment of Trusty via http://cdimage.ubuntu.com/daily-live/current/ .

tags: added: needs-bisect regression-release
removed: regression-potential
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.