Hide Forgot
Description of problem: pm-suspend effectively caused a failing suspend cycle where system returned immediately with this problem report. Additional info: reporter: libreport-2.1.9 WARNING: CPU: 2 PID: 14965 at drivers/gpu/drm/nouveau/nouveau_bo.c:362 nouveau_bo_unpin+0x138/0x150 [nouveau]() Modules linked in: nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd fscache fuse drbd lru_cache libcrc32c 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 be2iscsi iscsi_boot_sysfs bnx2i ip6table_raw cnic uio ip6table_filter cxgb4i cxgb4 cxgb3i ip6_tables iptable_nat cxgb3 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle mdio libcxgbi iptable_security iptable_raw ib_iser rdma_cm ib_addr iw_cm ib_cm rfcomm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp bnep libiscsi scsi_transport_iscsi snd_hda_codec_hdmi arc4 snd_hda_codec_realtek snd_hda_intel ath9k ath9k_common ath9k_hw snd_hda_codec x86_pkg_temp_thermal snd_hwdep snd_seq ath coretemp mac80211 uvcvideo videobuf2_vmalloc vhost_net tun vhost macvtap macvlan cfg80211 videobuf2_memops kvm_intel videobuf2_core snd_seq_device snd_pcm videodev snd_page_alloc btusb snd_timer kvm bluetooth eeepc_wmi asus_wmi sparse_keymap microcode media snd rfkill i2c_i801 iTCO_wdt iTCO_vendor_support serio_raw joydev acpi_cpufreq mperf mei_me soundcore mei lpc_ich ir_lirc_codec lirc_dev ir_jvc_decoder ir_sony_decoder ir_sanyo_decoder ir_rc5_decoder ir_rc6_decoder ir_nec_decoder ir_mce_kbd_decoder mfd_core shpchp rc_rc6_mce ene_ir rc_core uinput dm_crypt hid_logitech_dj usb_storage nouveau i915 crc32_pclmul crc32c_intel mxm_wmi ghash_clmulni_intel i2c_algo_bit drm_kms_helper ttm r8169 drm mii i2c_core wmi video sunrpc CPU: 2 PID: 14965 Comm: kworker/u16:7 Not tainted 3.11.9-100.fc18.x86_64 #1 mei_me 0000:00:16.0: suspend Hardware name: ASUSTeK Computer INC. ET2700I/ET2700I, BIOS 0602 11/04/2011 Workqueue: events_unbound async_run_entry_fn 0000000000000009 ffff880172d43bb8 ffffffff81666616 0000000000000000 0000000000000000 ffff880172d43bf8 ffffffff810695ec ffff8801afea6000 ffff8801afbf5c00 ffff8801b03c64a8 ffff8801b6aba170 ffff8801b6aba000 Call Trace: [<ffffffff81666616>] dump_stack+0x46/0x58 [<ffffffff810695ec>] warn_slowpath_common+0x8c/0xc0 [<ffffffff8106963a>] warn_slowpath_null+0x1a/0x20 [<ffffffffa025e508>] nouveau_bo_unpin+0x138/0x150 [nouveau] [<ffffffffa0269bb8>] nouveau_display_suspend+0xa8/0xd0 [nouveau] [<ffffffffa0258649>] nouveau_do_suspend+0x79/0x250 [nouveau] [<ffffffffa02597d4>] nouveau_pmops_suspend+0x34/0x80 [nouveau] [<ffffffff8133cbf7>] pci_pm_suspend+0x77/0x140 [<ffffffff814137da>] ? __pm_runtime_barrier+0x1a/0x140 [<ffffffff8133cb80>] ? pci_pm_poweroff+0xf0/0xf0 [<ffffffff81410428>] dpm_run_callback+0x58/0x90 [<ffffffff8141054b>] __device_suspend+0xeb/0x280 [<ffffffff81410f8f>] async_suspend+0x1f/0xa0 [<ffffffff81092666>] async_run_entry_fn+0x46/0x140 [<ffffffff8108391a>] process_one_work+0x17a/0x400 [<ffffffff81084d8c>] worker_thread+0x11c/0x370 [<ffffffff81084c70>] ? manage_workers.isra.21+0x2b0/0x2b0 [<ffffffff8108b3e0>] kthread+0xc0/0xd0 [<ffffffff81010000>] ? perf_trace_xen_mc_callback+0xe0/0xe0 [<ffffffff8108b320>] ? kthread_create_on_node+0x120/0x120 [<ffffffff8167572c>] ret_from_fork+0x7c/0xb0 [<ffffffff8108b320>] ? kthread_create_on_node+0x120/0x120
Created attachment 830860 [details] File: dmesg
Removing the 'nouveau' module from the kernel solves this problem. /etc/default/grub; GRUB_CMDLINE_LINUX=".... quiet rdblacklist=nouveau nouveau.modeset=0" # grub2-mkconfig -o /boot/grub2/grub.cfg Boot message now lists; [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.11.9-100.fc18.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 vconsole.keymap=us rd.lvm.lv=fedora/root rd.luks.uuid=luks-d43afc59-2fba-40ce-b1e7-731d929a1601 rhgb quiet rdblacklist=nouveau nouveau.modeset=0 The is a whole set of bugzilla entries which in a way all seem to highlight my problem in nearly same way. I also read entries claiming the issue to be resolved in new kernels 3.13.... . I started experiencing the problem shortly after a kernel update to 3.11.9-100.fc18.x86_64 There is an additional problem however. I can pm-hibernate without issues. I can also pm-suspend and functionality is restored on wakeup but only for 5 seconds. Then the machine does freeze. I am unable t find out what causes this freeze on wakeup as there is no trail left on hard reset. During freeze the console keeps exactly same without any additional messags. Regards, -Wim ten Have.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.