Additional info: reporter: libreport-2.1.12 BUG: soft lockup - CPU#1 stuck for 21s! [Xorg:390] Modules linked in: ccm fuse bnep bluetooth 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 arc4 snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd b43 bcma mac80211 cfg80211 hp_wmi sparse_keymap rfkill powernow_k8 kvm_amd kvm uvcvideo ssb videobuf2_vmalloc videobuf2_memops videobuf2_core videodev soundcore sdhci_pci media sdhci r592 forcedeth serio_raw mmc_core memstick k8temp nv_tco i2c_nforce2 nfsd auth_rpcgss nfs_acl lockd sunrpc ata_generic pata_acpi nouveau mxm_wmi i2c_algo_bit drm_kms_helper ttm firewire_ohci drm sata_nv firewire_core i2c_core crc_itu_t pata_amd wmi video CPU: 1 PID: 390 Comm: Xorg Not tainted 3.13.4-200.fc20.i686+PAE #1 Hardware name: Hewlett-Packard HP Pavilion dv6000 (GL914UA#ABC) /30B7, BIOS F.42 03/09/2009 task: f49f8480 ti: ec734000 task.ti: ec734000 EIP: 0060:[<c06ac832>] EFLAGS: 00003296 CPU: 1 EIP is at ioread32+0x32/0x40 EAX: 40000005 EBX: f4b57380 ECX: 00000000 EDX: f93000a4 ESI: 00080000 EDI: f814fd80 EBP: ec735bd0 ESP: ec735bcc DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 8005003b CR2: b7779000 CR3: 2e306000 CR4: 000007f0 Stack: f80d4102 ec735be8 f80d3dcd f814fd80 f4bd7b40 f814fd08 f814fd20 ec735c00 f809dd01 f814fd20 00000029 f814d0c0 f4aeaf60 ec735c54 f80db8ed f7485400 40000005 c051d4d7 f7485400 00000000 00000001 000000a4 00000000 000000a0 Call Trace: [<f80d4102>] ? nv40_instmem_rd32+0x12/0x20 [nouveau] [<f80d3dcd>] nv04_instobj_rd32+0x2d/0x40 [nouveau] [<f809dd01>] _nouveau_gpuobj_rd32+0x31/0x40 [nouveau] [<f80db8ed>] nv44_vm_fill+0x5d/0x1f0 [nouveau] [<c051d4d7>] ? free_pages_prepare+0xf7/0x170 [<f80dbd56>] nv44_vm_unmap+0x136/0x150 [nouveau] [<f80dac0f>] nouveau_vm_unmap_at+0xcf/0x100 [nouveau] [<f80dac6b>] nouveau_vm_unmap+0x2b/0x40 [nouveau] [<f8115b43>] nv04_sgdma_unbind+0x13/0x20 [nouveau] [<f7e9df90>] ttm_tt_unbind+0x20/0x30 [ttm] [<f7e9e77a>] ttm_bo_cleanup_memtype_use+0x2a/0x70 [ttm] [<f7e9f1a1>] ttm_bo_release+0x1d1/0x200 [ttm] [<f7e9f1f5>] ttm_bo_unref+0x25/0x30 [ttm] [<f8118e8a>] nouveau_gem_object_del+0x4a/0x50 [nouveau] [<f7ee0822>] drm_gem_object_free+0x22/0x30 [drm]
Created attachment 884712 [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.