Description of problem: Opened laptop lid, closed last night to suspend. Additional info: reporter: libreport-2.2.0 WARNING: CPU: 0 PID: 5199 at drivers/gpu/drm/nouveau/nouveau_bo.c:358 nouveau_bo_unpin+0x120/0x130 [nouveau]() Modules linked in: fuse ipt_MASQUERADE ccm xt_CHECKSUM ip6t_rpfilter ip6t_REJECT xt_conntrack rfcomm bnep 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 dm_crypt snd_hda_codec_analog arc4 snd_hda_intel iwl4965 iwlegacy mac80211 cfg80211 snd_hda_codec e1000e r592 memstick snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support sdhci_pci sdhci mmc_core btusb microcode joydev serio_raw i2c_i801 lpc_ich mfd_core bluetooth thinkpad_acpi snd soundcore rfkill tpm_tis ptp pps_core shpchp tpm acpi_cpufreq uinput nouveau firewire_ohci ata_generic pata_acpi firewire_core crc_itu_t yenta_socket mxm_wmi i2c_algo_bit drm_kms_helper ttm drm i2c_core wmi video CPU: 0 PID: 5199 Comm: kworker/u4:42 Not tainted 3.13.9-100.fc19.x86_64 #1 Hardware name: LENOVO 6459CTO/6459CTO, BIOS 7LETB7WW (2.17 ) 04/25/2008 Workqueue: events_unbound async_run_entry_fn 0000000000000009 ffff880079cb5c28 ffffffff81681444 0000000000000000 ffff880079cb5c60 ffffffff8106d3bd ffff880037244000 ffff880037321358 ffff880135577170 ffff880037321000 0000000000000080 ffff880079cb5c70 Call Trace: [<ffffffff81681444>] dump_stack+0x45/0x56 [<ffffffff8106d3bd>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8106d49a>] warn_slowpath_null+0x1a/0x20 [<ffffffffa015add0>] nouveau_bo_unpin+0x120/0x130 [nouveau] [<ffffffffa01663b8>] nouveau_display_suspend+0x98/0xd0 [nouveau] [<ffffffffa0154789>] nouveau_do_suspend+0x219/0x280 [nouveau] [<ffffffffa0154895>] nouveau_pmops_suspend+0xa5/0xb0 [nouveau] [<ffffffff813524ac>] pci_pm_suspend+0x6c/0x150 [<ffffffff81352440>] ? pci_pm_freeze+0xe0/0xe0 [<ffffffff8141f049>] dpm_run_callback+0x49/0xa0 [<ffffffff8141f44b>] __device_suspend+0xdb/0x280 [<ffffffff8141f60f>] async_suspend+0x1f/0xa0 [<ffffffff810950b9>] async_run_entry_fn+0x39/0x120 [<ffffffff81087aa6>] process_one_work+0x176/0x430 [<ffffffff810886db>] worker_thread+0x11b/0x3a0 [<ffffffff810885c0>] ? rescuer_thread+0x350/0x350 [<ffffffff8108f1a2>] kthread+0xd2/0xf0 [<ffffffff8108f0d0>] ? insert_kthread_work+0x40/0x40 [<ffffffff8169033c>] ret_from_fork+0x7c/0xb0 [<ffffffff8108f0d0>] ? insert_kthread_work+0x40/0x40
Created attachment 887929 [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.