Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: BOOT_IMAGE=/vmlinuz-3.6.6-1.fc17.x86_64 nox2apic root=/dev/mapper/vg_scylla-lv_root ro rd.luks.uuid=luks-ad37129b-1c8c-4262-b3b4-ecee3f8109f9 rd.md=0 rd.lvm.lv=vg_scylla/lv_root SYSFONT=latarcyrheb-sun16 KEYTABLE=us rd.lvm.lv=vg_scylla/lv_swap LANG=en_US.UTF-8 rd.dm=0 rhgb quiet kernel: 3.6.6-1.fc17.x86_64 backtrace: :BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u:1:3773] :Modules linked in: tcp_lp fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat xt_CHECKSUM iptable_mangle bridge stp llc rfcomm bnep nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_REJECT nf_conntrack_ipv6 nf_conntrack_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 xt_state nf_conntrack ip6table_filter ip6_tables snd_hda_codec_hdmi arc4 iwldvm mac80211 iTCO_wdt iTCO_vendor_support binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media coretemp snd_hda_codec_conexant btusb bluetooth microcode snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm iwlwifi i2c_i801 joydev cfg80211 lpc_ich mfd_core snd_page_alloc mei snd_timer vhost_net tun thinkpad_acpi macvtap macvlan snd soundcore tpm_tis kvm_intel rfkill tpm kvm tpm_bios uinput nfsd auth_rpcgss nfs_acl lockd xts gf128mul dm_crypt crc32c_intel ghash_clmulni_intel sdhci_pci firewire_ohci sdhci firewire_core mmc_core crc_itu_t e1000e nouveau mxm_wmi wmi video i2c_algo_bit drm_ :kms_helper ttm drm i2c_core sunrpc be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi :CPU 0 :Pid: 3773, comm: kworker/u:1 Not tainted 3.6.6-1.fc17.x86_64 #1 LENOVO 4270CTO/4270CTO :RIP: 0010:[<ffffffff81063e48>] [<ffffffff81063e48>] tasklet_kill+0x58/0x80 :RSP: 0018:ffff8804e2f15cb0 EFLAGS: 00000202 :RAX: 0000000000000003 RBX: 0000000000000200 RCX: 0000000000000010 :RDX: 0000000000001010 RSI: 0000000000000246 RDI: ffff88051c643178 :RBP: ffff8804e2f15cc0 R08: ffff88051a1f9a00 R09: ffff880528c00000 :R10: 0000000000000000 R11: 0000000000000000 R12: ffff88051c64001c :R13: ffff88051c640000 R14: ffff8804e2f15c30 R15: 00003a98000003e8 :FS: 0000000000000000(0000) GS:ffff88053dc00000(0000) knlGS:0000000000000000 :CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b :CR2: 00007f1b0d8e6048 CR3: 0000000001c0b000 CR4: 00000000000407f0 :DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 :DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 :Process kworker/u:1 (pid: 3773, threadinfo ffff8804e2f14000, task ffff8804e2ff2e20) :Stack: : ffff88051c640000 0000000000000286 ffff8804e2f15d10 ffffffffa0559e98 : ffff8804e2f15ce0 0000000000000246 0000000000000000 ffff88051fb41f10 : ffff88051c640000 ffff88051fb41f40 0000000000000000 0000000000000000 :Call Trace: : [<ffffffffa0559e98>] iwl_trans_pcie_stop_device+0x198/0x340 [iwlwifi] : [<ffffffffa07cf8cd>] iwl_down+0x20d/0x310 [iwldvm] : [<ffffffffa07cfa1f>] iwlagn_prepare_restart+0x4f/0xd0 [iwldvm] : [<ffffffffa07cfc65>] iwl_bg_restart+0x75/0x430 [iwldvm] : [<ffffffff81077cb7>] process_one_work+0x147/0x4a0 : [<ffffffffa07cfbf0>] ? iwl_cancel_deferred_work+0x90/0x90 [iwldvm] : [<ffffffff81079a1e>] worker_thread+0x15e/0x480 : [<ffffffff810798c0>] ? manage_workers+0x2f0/0x2f0 : [<ffffffff8107ede3>] kthread+0x93/0xa0 : [<ffffffff816269c4>] kernel_thread_helper+0x4/0x10 : [<ffffffff8107ed50>] ? kthread_freezable_should_stop+0x70/0x70 : [<ffffffff816269c0>] ? gs_change+0x13/0x13 :Code: 44 00 00 e8 cb 8c 5b 00 49 8b 44 24 08 a8 01 75 f2 f0 0f ba 2b 00 19 c0 85 c0 75 e7 49 8b 44 24 08 a8 02 74 0f 66 0f 1f 44 00 00 <49> 8b 44 24 08 a8 02 75 f7 f0 80 23 fe 5b 41 5c 5d c3 48 c7 c7
*** Bug 879251 has been marked as a duplicate of this bug. ***
Please install and boot a kernel-debug and try to reproduce this problem. Debug kernel should print some more informative call trace messages, so when you will reproduce this problem, attach dmesg output here.
I've been able to reproduce the problem once with a debug kernel after two days of running one, but I couldn't get any dmesg output from it. When this problem occurs with a normal kernel, the cores in my CPU get stuck at 100% usage (according to htop) one at a time over the course of a few minutes, which gives abrt enough chance to spot the problem with the kernel and collect output from dmesg. The debug kernel is way, way less responsive, so when (by all appearances) the same thing happened a few minutes ago, neither I nor abrt had a chance to get anything from dmesg---by the time I realized something was going on, the machine had locked up---and when I rebooted, there was nothing interesting in /var/log/messages. What to do?
Hmm, that strange. Please run on debug-kernel for few hours and then dump dmesg and attach it here, perhaps there will be some massages, which indicate where the problem is.
all of a sudden, i was trying to go to a web site on firefox, i go the kernel panic and then slowly but surely nothing else worked anymore (i could still move the mouse, but no more keyboard inputs and the windows were not responding either) Package: kernel OS Release: Fedora release 17 (Beefy Miracle)
I'm still getting stuck CPUs with kernel 3.7.3-101.fc17.x86_64. Sometime in the next few days I'll try running a debug kernel again to see if I can produce some useful data.
Please run it for some long period - let say a month. In most cases debug kernel should show problem quickly, but there are cases (what I realized currently) which need long time to reproduce also on debug kernel.
*** Bug 904699 has been marked as a duplicate of this bug. ***
I think I found where the problem is, not needed any further informations for now.
This will be fixed on 3.9 which include commit: commit 2bfb50924c7e92362ac937aef2ab56bc7bd3ca52 Author: Johannes Berg <johannes.berg> Date: Thu Dec 27 21:43:48 2012 +0100 iwlwifi: use threaded interrupt handler Closing with rawhide resolution ...