Hide Forgot
Description of problem: boot up the ultrabook and loged into gnome-shell Additional info: reporter: libreport-2.1.10 WARNING: CPU: 0 PID: 1078 at drivers/gpu/drm/i915/intel_display.c:8810 check_crtc_state+0x61f/0xb10 [i915]() pipe state doesn't match! Modules linked in: hid_sensor_magn_3d hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_als hid_sensor_trigger industrialio_triggered_buffer kfifo_buf industrialio hid_sensor_iio_common uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev hid_sensor_hub media fuse nls_utf8 cifs dns_resolver fscache 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 arc4 iwlmvm mac80211 snd_hda_codec_hdmi x86_pkg_temp_thermal snd_hda_codec_realtek coretemp kvm_intel kvm snd_hda_intel crct10dif_pclmul crc32_pclmul iwlwifi snd_hda_codec crc32c_intel snd_hwdep snd_seq cfg80211 iTCO_wdt snd_seq_device iTCO_vendor_support ghash_clmulni_intel snd_pcm microcode joydev rfkill serio_raw snd_page_alloc lpc_ich snd_timer shpchp mfd_core snd mei_me i2c_i801 mei soundcore uinput i915 i2c_algo_bit drm_kms_helper drm i2c_core video CPU: 0 PID: 1078 Comm: Xorg Not tainted 3.12.5-200.fc19.x86_64 #1 Hardware name: LENOVO 20266/Yoga2, BIOS 76CN27WW 09/17/2013 0000000000000009 ffff88023cc7d898 ffffffff8166305a ffff88023cc7d8e0 ffff88023cc7d8d0 ffffffff8106925d ffff880253417000 ffff8802534176d0 ffff8802510a9c18 ffff8802510a9800 ffff8802510a9c20 ffff88023cc7d930 Call Trace: [<ffffffff8166305a>] dump_stack+0x45/0x56 [<ffffffff8106925d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff810692cc>] warn_slowpath_fmt+0x4c/0x50 [<ffffffffa00b33ef>] check_crtc_state+0x61f/0xb10 [i915] [<ffffffffa00bf633>] intel_modeset_check_state+0x2c3/0x780 [i915] [<ffffffffa00bfb85>] intel_set_mode+0x25/0x30 [i915] [<ffffffffa00c0473>] intel_crtc_set_config+0x7e3/0x9d0 [i915] [<ffffffffa002d1ed>] drm_mode_set_config_internal+0x5d/0xe0 [drm] [<ffffffffa002fc67>] drm_mode_setcrtc+0xf7/0x650 [drm] [<ffffffff8154c89e>] ? sock_aio_write+0xfe/0x130 [<ffffffff81666e32>] ? mutex_lock+0x12/0x30 [<ffffffffa0020c32>] drm_ioctl+0x502/0x630 [drm] [<ffffffff811c0e9d>] do_vfs_ioctl+0x2dd/0x4b0 [<ffffffff811b029e>] ? ____fput+0xe/0x10 [<ffffffff811c10f1>] SyS_ioctl+0x81/0xa0 [<ffffffff816720a9>] system_call_fastpath+0x16/0x1b Potential duplicate: bug 1044724
Created attachment 840346 [details] File: dmesg
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.