Description of problem: after suspend the resume failed Additional info: reporter: libreport-2.1.11 WARNING: CPU: 2 PID: 1005 at drivers/gpu/drm/drm_crtc.c:2029 drm_mode_set_config_internal+0xd6/0xe0 [drm]() Modules linked in: tun wacom usb_storage btusb fuse ip6t_rpfilter ip6t_REJECT xt_conntrack bnep bluetooth 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 snd_hda_codec_hdmi snd_hda_codec_realtek iTCO_wdt iTCO_vendor_support vfat fat arc4 x86_pkg_temp_thermal coretemp kvm_intel kvm iwldvm mac80211 microcode joydev serio_raw i2c_i801 snd_hda_intel snd_hda_codec iwlwifi snd_hwdep lpc_ich snd_seq mfd_core uvcvideo snd_seq_device cfg80211 videobuf2_vmalloc videobuf2_memops videobuf2_core sdhci_pci videodev sdhci mmc_core media e1000e snd_pcm ptp pps_core snd_page_alloc mei_me snd_timer mei shpchp thinkpad_acpi snd soundcore tpm_tis rfkill tpm tpm_bios nfsd auth_rpcgss nfs_acl lockd sunrpc dm_crypt crct10dif_pclmul nouveau crc32_pclmul crc32c_intel ghash_clmulni_intel firewire_ohci mxm_wmi i2c_algo_bit drm_kms_helper ttm firewire_core crc_itu_t drm i2c_core wmi video CPU: 2 PID: 1005 Comm: X Not tainted 3.12.8-300.fc20.x86_64 #1 Hardware name: LENOVO 24474LG/24474LG, BIOS G5ET95WW (2.55 ) 09/13/2013 0000000000000009 ffff880209099c60 ffffffff81667a8b 0000000000000000 ffff880209099c98 ffffffff8106921d ffff8801d9bcf500 0000000000000000 ffff880211c77000 ffff8801d9bcf500 ffff880209099de8 ffff880209099ca8 Call Trace: [<ffffffff81667a8b>] dump_stack+0x45/0x56 [<ffffffff8106921d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff810692fa>] warn_slowpath_null+0x1a/0x20 [<ffffffffa003c236>] drm_mode_set_config_internal+0xd6/0xe0 [drm] [<ffffffffa003ec37>] drm_mode_setcrtc+0xf7/0x650 [drm] [<ffffffff8166b7f2>] ? mutex_lock+0x12/0x30 [<ffffffff8166b7f2>] ? mutex_lock+0x12/0x30 [<ffffffffa002fc32>] drm_ioctl+0x502/0x630 [drm] [<ffffffffa0154e51>] nouveau_drm_ioctl+0x51/0x90 [nouveau] [<ffffffff811c122d>] do_vfs_ioctl+0x2dd/0x4b0 [<ffffffff811c1481>] SyS_ioctl+0x81/0xa0 [<ffffffff81676a69>] system_call_fastpath+0x16/0x1b
Created attachment 855497 [details] File: dmesg
This happens sometimes after a suspend/resume cycle on a Lenovo W530 Notebook with Nvidia K1000 Graphics. Currently Bios/EFI Firmware G5ET95WW (2.55) is active. If you need further details on the hardware, please ask.
I have this hardware, and haven't noticed this issue. Can you think of any more specific way that you can reproduce it?
If I remember correctly it happens if I do the following: - Place the notebook in a Dockingstation with a second monitor connected. - Undock the Notebook while the OS is running. - Close the notebook relatively soon so that it suspends (suspend to ram). - After the notebook has finished suspending, you can reopen it and the crash should happen. One further detail, which might help: In the firmware I configured that only the nvidia graphics is active. No Optimus and no intel on cpu graphics. I'll add another comment tonight (CET) when I have been able to reproduce the crash the way I described it.
I am able to reproduce this 100% of the time by doing the following: Sometimes, this occurs when my connect my computer to a TV via HDMI cable. Sometimes, it occurs when disconnecting my computer from the TV by pulling out the HDMI cable. Either way, connecting then disconnecting my computer to a TV via HDMI is a 100% reliable way to reproduce this crash.
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.