Bug 1052184 - [abrt] WARNING: CPU: 5 PID: 4955 at drivers/gpu/drm/i915/intel_display.c:8853 check_crtc_state+0x61f/0xb10 [i915]()
Summary: [abrt] WARNING: CPU: 5 PID: 4955 at drivers/gpu/drm/i915/intel_display.c:8853...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6ac9c791dedad39a308757bf8ea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-13 13:06 UTC by Emanuel Somosan
Modified: 2015-06-29 14:24 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:24:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: dmesg (99.26 KB, text/plain)
2014-01-13 13:06 UTC, Emanuel Somosan
no flags Details

Description Emanuel Somosan 2014-01-13 13:06:26 UTC
Description of problem:
I just tried to change the screen resolution.

Additional info:
reporter:       libreport-2.1.11
WARNING: CPU: 5 PID: 4955 at drivers/gpu/drm/i915/intel_display.c:8853 check_crtc_state+0x61f/0xb10 [i915]()
pipe state doesn't match!
Modules linked in: rfcomm fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE ip6t_REJECT xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep arc4 iTCO_wdt iTCO_vendor_support snd_hda_codec_realtek snd_hda_codec_hdmi dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison vfat fat iwlmvm mac80211 x86_pkg_temp_thermal coretemp kvm_intel kvm microcode joydev serio_raw iwlwifi uvcvideo videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_core i2c_i801 lpc_ich videodev mfd_core media snd_hda_intel sdhci_pci btusb sdhci snd_hda_codec bluetooth e1000e mmc_core snd_seq snd_hwdep snd_seq_device mei_me ptp mei pps_core snd_pcm snd_page_alloc snd_timer thinkpad_acpi shpchp snd tpm_tis soundcore tpm rfkill tpm_bios nfsd auth_rpcgss nfs_acl lockd sunrpc xfs libcrc32c dm_crypt nouveau crct10dif_pclmul crc32_pclmul i915 crc32c_intel ghash_clmulni_intel mxm_wmi ttm i2c_algo_bit drm_kms_helper drm i2c_core wmi video
CPU: 5 PID: 4955 Comm: Xorg Not tainted 3.12.6-300.fc20.x86_64 #1
Hardware name: LENOVO 20BG001CGE/20BG001CGE, BIOS GNET28WW (1.10 ) 11/21/2013
 0000000000000009 ffff88044f6d1898 ffffffff816630c1 ffff88044f6d18e0
 ffff88044f6d18d0 ffffffff810691dd ffff880462e8a000 ffff880462e8a6d0
 ffff880463d2fc18 ffff880463d2f800 ffff880463d2fc20 ffff88044f6d1930
Call Trace:
 [<ffffffff816630c1>] dump_stack+0x45/0x56
 [<ffffffff810691dd>] warn_slowpath_common+0x7d/0xa0
 [<ffffffff8106924c>] warn_slowpath_fmt+0x4c/0x50
 [<ffffffffa00f346f>] check_crtc_state+0x61f/0xb10 [i915]
 [<ffffffffa00ff723>] intel_modeset_check_state+0x2c3/0x780 [i915]
 [<ffffffffa00ffc75>] intel_set_mode+0x25/0x30 [i915]
 [<ffffffffa0100563>] intel_crtc_set_config+0x7e3/0x9d0 [i915]
 [<ffffffffa005c1bd>] drm_mode_set_config_internal+0x5d/0xe0 [drm]
 [<ffffffffa005ec37>] drm_mode_setcrtc+0xf7/0x650 [drm]
 [<ffffffff8154cbfe>] ? sock_aio_write+0xfe/0x130
 [<ffffffff81666ea2>] ? mutex_lock+0x12/0x30
 [<ffffffffa004fc32>] drm_ioctl+0x502/0x630 [drm]
 [<ffffffff811c0cdd>] do_vfs_ioctl+0x2dd/0x4b0
 [<ffffffff811c0f31>] SyS_ioctl+0x81/0xa0
 [<ffffffff81672129>] system_call_fastpath+0x16/0x1b

Potential duplicate: bug 1044724

Comment 1 Emanuel Somosan 2014-01-13 13:06:47 UTC
Created attachment 849339 [details]
File: dmesg

Comment 2 Greg Scott 2014-06-14 20:47:02 UTC
Oh wow.  I just stumbled across what looks like this exact same problem with a fresh install of RHEL 7.0 on a Lenovo SL500 laptop.  

Brand new, fresh virgin installation.  I accept the license and subscribe it to RHN.  It boots to the GUI login screen.  I login with user gregs.  The screen goes black, an "X" mouse pointer shows up, and it sits there like a bump on a log forever.  CTRL/Alt/F2 to go to an alternate console.  I log on as root and I see two messages about abrt-cli dumps.  I can enter a command to report these problems and I can enter another command to turn on automatic problem reporting.  I reported them - see Red Hat support case numbers 01122445 and 01122447.

Something ugly with a video driver right out of the gate?

Yum update says 57 packages have updates already, 4 days after RHEL 7 GA.  Maybe there's an update for this problem.

Applied the updates, rebooted and now I can log in graphically.

- Greg

Comment 3 Fedora End Of Life 2015-05-29 10:28:39 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 14:24:59 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.