Description of problem: Believe laptop was resuming from sleep Additional info: reporter: libreport-2.1.8 BUG: soft lockup - CPU#0 stuck for 22s! [X:529] Modules linked in: lib80211_crypt_ccmp snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm ipw2200 libipw iTCO_wdt snd_page_alloc gpio_ich iTCO_vendor_support joydev lpc_ich cfg80211 snd_timer ppdev snd toshiba_acpi lib80211 e1000 sparse_keymap serio_raw soundcore rfkill microcode parport_pc acpi_cpufreq parport mperf binfmt_misc uinput hid_logitech_dj nouveau mxm_wmi wmi i2c_algo_bit drm_kms_helper ata_generic ttm drm pata_acpi firewire_ohci firewire_core yenta_socket crc_itu_t i2c_core video CPU: 0 PID: 529 Comm: X Not tainted 3.11.6-200.fc19.i686 #1 Hardware name: TOSHIBA Tecra M2/Portable PC, BIOS Version 1.60 02/14/2008 task: f3caa760 ti: f5806000 task.ti: f42de000 EIP: 0060:[<c068d922>] EFLAGS: 00003292 CPU: 0 EIP is at ioread32+0x32/0x40 EAX: 0001b9ef EBX: f7eadde0 ECX: 00000000 EDX: f90e0048 ESI: f3ccffc0 EDI: f29afe00 EBP: f42dfd20 ESP: f42dfd1c DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 CR0: 8005003b CR2: b878bed8 CR3: 34f2b000 CR4: 000007d0 Stack: f7e40162 f42dfd2c f7e6f4eb f29afa00 f42dfd44 f7e680e6 f3c3c080 00000000 f1e082c0 000003e8 f42dfd70 f7e6860d 00000000 f3caa760 f3caa760 000082c0 f7ec26c0 f5ba338c f690be00 f7ec26c0 f5ba338c f42dfd78 f7e69e63 f42dfda4 Call Trace: [<f7e40162>] ? _nouveau_fifo_channel_rd32+0x12/0x20 [nouveau] [<f7e6f4eb>] nv10_fence_read+0x1b/0x20 [nouveau] [<f7e680e6>] nouveau_fence_update+0x56/0x70 [nouveau] [<f7e6860d>] nouveau_fence_wait+0xad/0x180 [nouveau] [<f7e69e63>] nouveau_bo_fence_wait+0x13/0x20 [nouveau] [<f7c59676>] ttm_bo_wait+0x76/0x140 [ttm] [<f7e6daf7>] nouveau_gem_ioctl_pushbuf+0x8c7/0xf50 [nouveau] [<c044c9ea>] ? irq_exit+0x6a/0xa0 [<c0404585>] ? do_IRQ+0x45/0xb0 [<f7e6d230>] ? nouveau_gem_ioctl_new+0x180/0x180 [nouveau] [<f7ce2bba>] drm_ioctl+0x49a/0x540 [drm] [<c0406481>] ? mask_and_ack_8259A+0xb1/0xf0 [<f7e6d230>] ? nouveau_gem_ioctl_new+0x180/0x180 [nouveau] [<c0587870>] ? fsnotify_put_event+0x50/0x90 [<c0587528>] ? fsnotify+0x208/0x2d0 [<f7ce2720>] ? drm_copy_field+0x70/0x70 [drm] [<c0560456>] do_vfs_ioctl+0x2e6/0x4d0 [<c0552b71>] ? __sb_end_write+0x31/0x70 [<c0550ff5>] ? vfs_write+0x155/0x1b0 [<c05606a0>] SyS_ioctl+0x60/0x80 [<c0406481>] ? mask_and_ack_8259A+0xb1/0xf0 [<c0406481>] ? mask_and_ack_8259A+0xb1/0xf0 [<c098688d>] sysenter_do_call+0x12/0x28 [<c0406481>] ? mask_and_ack_8259A+0xb1/0xf0 [<c0406481>] ? mask_and_ack_8259A+0xb1/0xf0 Code: 3d 00 00 01 00 76 0a 0f b7 d0 ed c3 90 8d 74 26 00 55 ba 69 30 b4 c0 89 e5 e8 0b ff ff ff b8 ff ff ff ff 5d c3 8d 74 26 00 8b 00 <c3> 8d b6 00 00 00 00 8d bc 27 00 00 00 00 81 fa ff ff 03 00 89
Created attachment 816335 [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.