Additional info: reporter: libreport-2.1.11 BUG: soft lockup - CPU#0 stuck for 23s! [lspci:2988] Modules linked in: 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 arc4 iwldvm mac80211 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep sony_laptop iwlwifi coretemp kvm_intel kvm uvcvideo snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd mmc_block iTCO_wdt iTCO_vendor_support microcode cfg80211 rfkill e1000e soundcore ptp pps_core shpchp videobuf2_vmalloc videobuf2_memops videobuf2_core serio_raw videodev media i2c_i801 r592 memstick sdhci_pci sdhci mmc_core lpc_ich mfd_core acpi_cpufreq nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper firewire_ohci drm firewire_core yenta_socket crc_itu_t i2c_core wmi video CPU: 0 PID: 2988 Comm: lspci Not tainted 3.12.7-300.fc20.x86_64 #1 Hardware name: Sony Corporation VGN-Z5/VAIO, BIOS R5031M3 11/10/2009 task: ffff88009868ca40 ti: ffff880095cf2000 task.ti: ffff880095cf2000 RIP: 0010:[<ffffffff81317c02>] [<ffffffff81317c02>] ioread32+0x42/0x50 RSP: 0018:ffff880095cf3ab8 EFLAGS: 00000296 RAX: 00000000ffffffff RBX: ffffea000261f6c0 RCX: 0000000000000001 RDX: ffff880036dda800 RSI: 0000000077359400 RDI: ffffc90015989410 RBP: ffff880095cf3ad8 R08: 0000000000000000 R09: 0000000000000000 R10: ffffea00026111c0 R11: ffffffff8117b862 R12: ffff880095cf3a68 R13: ffffffff811a7e71 R14: ffff880095cf3a20 R15: ffffffff811a064e FS: 00007ffc43aa4740(0000) GS:ffff88013fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00007ff618b6e830 CR3: 000000009ab2f000 CR4: 00000000000407f0 Stack: ffffffffa01c821e ffff880136eda700 ffff880036dc5180 0000000000100c80 ffff880095cf3b20 ffffffffa01c7fc4 0000000077359400 ffffffffffffffff ffff880136eda700 0000000000000000 ffff88003681e000 0000000000000000 Call Trace: [<ffffffffa01c821e>] ? nv04_timer_read+0x4e/0x70 [nouveau] [<ffffffffa01c7fc4>] nouveau_timer_wait_eq+0x74/0xd0 [nouveau] [<ffffffffa01aa931>] nv50_bar_init+0xa1/0x170 [nouveau] [<ffffffffa01a8e7d>] nouveau_object_inc+0xbd/0x1b0 [nouveau] [<ffffffffa01ce315>] nouveau_device_init+0x25/0xa0 [nouveau] [<ffffffffa01a8e7d>] nouveau_object_inc+0xbd/0x1b0 [nouveau] [<ffffffffa01a8e57>] nouveau_object_inc+0x97/0x1b0 [nouveau] [<ffffffffa01a774b>] nouveau_handle_init+0x7b/0x230 [nouveau] [<ffffffffa01a77e1>] nouveau_handle_init+0x111/0x230 [nouveau] [<ffffffffa01a6162>] nouveau_client_init+0x32/0x60 [nouveau] [<ffffffffa0200b38>] nouveau_do_resume+0x48/0x190 [nouveau] [<ffffffffa0202190>] nouveau_pmops_runtime_resume+0x90/0x110 [nouveau] [<ffffffff8134030b>] pci_pm_runtime_resume+0x7b/0xc0 [<ffffffff813fdcf5>] vga_switcheroo_runtime_resume+0x35/0x40 [<ffffffff81410071>] __rpm_callback+0x31/0x80 [<ffffffff814100e4>] rpm_callback+0x24/0x80 [<ffffffff81411096>] rpm_resume+0x476/0x670 [<ffffffff811cca8e>] ? mntput_no_expire+0x3e/0x120 [<ffffffff814112df>] __pm_runtime_resume+0x4f/0x80 [<ffffffff8133f18a>] pci_config_pm_runtime_get+0x5a/0x60 [<ffffffff81342f48>] pci_read_config+0x88/0x2a0 [<ffffffff812258cb>] ? read+0x6b/0x1f0 [<ffffffff8122593b>] read+0xdb/0x1f0 [<ffffffff811ae96e>] vfs_read+0x9e/0x170 [<ffffffff811af602>] SyS_pread64+0x72/0xb0 [<ffffffff81676969>] system_call_fastpath+0x16/0x1b Code: 66 0f 1f 84 00 00 00 00 00 55 48 c7 c6 80 a7 a3 81 48 89 e5 e8 f0 fe ff ff b8 ff ff ff ff 5d c3 66 0f 1f 84 00 00 00 00 00 8b 07 <c3> 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 81 fe ff ff 03 00
Created attachment 850969 [details] File: dmesg
Booting with "nouveau.runpm=0" should work around this issue for the moment.
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.
*** This bug has been marked as a duplicate of bug 1447677 ***