Description of problem: T520 with Intel and nVidia GPUs Optimus mode enabled in BIOS 1. boot with laptop display only 2. connect external Displayport monitor reproducible: always Note: There is also a kernel crash when booting with "discrete graphics" only with Displayport monitor connected. No crash when using DP-DVI reduction. Additional info: reporter: libreport-2.2.2 WARNING: CPU: 2 PID: 974 at drivers/gpu/drm/drm_crtc.c:2074 drm_mode_set_config_internal+0xd6/0xe0 [drm]() Modules linked in: ccm rfcomm fuse ip6t_rpfilter 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 btrfs raid6_pq xor iTCO_wdt iTCO_vendor_support snd_hda_codec_conexant snd_hda_codec_generic x86_pkg_temp_thermal coretemp kvm_intel arc4 kvm iwldvm mac80211 snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device microcode iwlwifi snd_pcm i2c_i801 i915 joydev btusb serio_raw bluetooth cfg80211 6lowpan_iphc lpc_ich mfd_core sdhci_pci sdhci e1000e mmc_core snd_timer ptp pps_core mei_me mei thinkpad_acpi shpchp snd soundcore tpm_tis rfkill tpm binfmt_misc dm_thin_pool dm_persistent_data libcrc32c dm_bio_prison dm_crypt nouveau crct10dif_pclmul crc32_pclmul crc32c_intel mxm_wmi i2c_algo_bit drm_kms_helper ttm drm ghash_clmulni_intel i2c_core wmi video CPU: 2 PID: 974 Comm: Xorg Not tainted 3.14.8-200.fc20.x86_64 #1 Hardware name: LENOVO 42404LG/42404LG, BIOS 8AET57WW (1.37 ) 04/05/2012 0000000000000000 0000000079f3f5bf ffff8800b90cdc80 ffffffff816f0502 0000000000000000 ffff8800b90cdcb8 ffffffff8108a1cd ffff880211290600 0000000000000000 ffff880230b4b000 ffff880211290600 0000000000000013 Call Trace: [<ffffffff816f0502>] dump_stack+0x45/0x56 [<ffffffff8108a1cd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8108a2fa>] warn_slowpath_null+0x1a/0x20 [<ffffffffa0048ab6>] drm_mode_set_config_internal+0xd6/0xe0 [drm] [<ffffffffa004b907>] drm_mode_setcrtc+0x107/0x610 [drm] [<ffffffffa003cbf2>] drm_ioctl+0x4f2/0x620 [drm] [<ffffffffa014094e>] nouveau_drm_ioctl+0x4e/0x90 [nouveau] [<ffffffff811fd110>] do_vfs_ioctl+0x2e0/0x4a0 [<ffffffff811fd351>] SyS_ioctl+0x81/0xa0 [<ffffffff81121ed6>] ? __audit_syscall_exit+0x1f6/0x2a0 [<ffffffff817008e9>] system_call_fastpath+0x16/0x1b
Created attachment 911024 [details] File: dmesg
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.
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.