Hide Forgot
Description of problem: wakeup after pm-suspend operation causes a total system freeze within 5 seconds. next thing that happened was this crash. Additional info: reporter: libreport-2.1.9 BUG: scheduling while atomic: swapper/2/0/0x10000100 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 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 rfcomm bnep be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi snd_hda_codec_hdmi x86_pkg_temp_thermal coretemp snd_hda_codec_realtek microcode snd_hda_intel snd_hda_codec arc4 vhost_net tun vhost macvtap macvlan ath9k ath9k_common ath9k_hw ath snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core mac80211 btusb cfg80211 nouveau eeepc_wmi mxm_wmi ttm asus_wmi sparse_keymap iTCO_wdt iTCO_vendor_support soundcore acpi_cpufreq mperf videodev media i2c_i801 bluetooth ir_lirc_codec ir_mce_kbd_decoder ir_sanyo_decoder lirc_dev ir_sony_decoder ir_nec_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder kvm_intel kvm rc_rc6_mce mei_me serio_raw mei ene_ir rc_core lpc_ich uinput shpchp mfd_core rfkill joydev dm_crypt hid_logitech_dj usb_storage i915 crc32_pclmul crc32c_intel i2c_algo_bit drm_kms_helper ghash_clmulni_intel drm r8169 mii i2c_core video wmi sunrpc CPU: 2 PID: 0 Comm: swapper/2 Not tainted 3.11.9-100.fc18.x86_64 #1 Hardware name: ASUSTeK Computer INC. ET2700I/ET2700I, BIOS 0602 11/04/2011 ffff8801bfa94180 ffff8801bfa83c00 ffffffff81666616 0000000000000007 ffff8801b693e000 ffff8801bfa83c10 ffffffff81662903 ffff8801bfa83c80 ffffffff8166b05d ffff8801b690d3e0 ffff8801b693ffd8 ffff8801b693ffd8 Call Trace: <IRQ> [<ffffffff81666616>] dump_stack+0x46/0x58 [<ffffffff81662903>] __schedule_bug+0x4d/0x5b [<ffffffff8166b05d>] __schedule+0x5ed/0x7a0 [<ffffffff81098d8a>] __cond_resched+0x2a/0x40 [<ffffffff8166b28f>] _cond_resched+0x2f/0x40 [<ffffffff81195ad5>] __kmalloc+0x55/0x260 [<ffffffff81524128>] ? hid_alloc_report_buf+0x28/0x30 [<ffffffff81524128>] hid_alloc_report_buf+0x28/0x30 [<ffffffffa00790b0>] logi_dj_ll_input_event+0xb0/0x1b0 [hid_logitech_dj] [<ffffffff814cb15e>] input_handle_event+0x8e/0x530 [<ffffffff814cb68c>] input_inject_event+0x8c/0xa0 [<ffffffff8167106d>] ? notifier_call_chain+0x4d/0x70 [<ffffffff813d4f80>] ? fn_null+0x10/0x10 [<ffffffff813d4ff3>] kbd_update_leds_helper+0x73/0x90 [<ffffffff814c8196>] input_handler_for_each_handle+0x56/0x80 [<ffffffff813d5af5>] kbd_bh+0x75/0x90 [<ffffffff8106e66a>] tasklet_action+0x6a/0xe0 [<ffffffff8106e1d8>] __do_softirq+0xe8/0x230 [<ffffffff8101b023>] ? native_sched_clock+0x13/0x80 [<ffffffff8167709c>] call_softirq+0x1c/0x30 [<ffffffff81015685>] do_softirq+0x75/0xb0 [<ffffffff8106e4b5>] irq_exit+0xb5/0xc0 [<ffffffff816779a3>] do_IRQ+0x63/0xe0 [<ffffffff8166d1ad>] common_interrupt+0x6d/0x6d <EOI> [<ffffffff8108ec2e>] ? __hrtimer_start_range_ns+0x1be/0x3f0 [<ffffffff8151aa2e>] ? cpuidle_enter_state+0x5e/0xe0 [<ffffffff8151aa27>] ? cpuidle_enter_state+0x57/0xe0 [<ffffffff8151ab6d>] cpuidle_idle_call+0xbd/0x200 [<ffffffff8101c75e>] arch_cpu_idle+0xe/0x30 [<ffffffff810b9510>] cpu_startup_entry+0xd0/0x260 [<ffffffff810409e7>] start_secondary+0x217/0x2c0
Created attachment 831453 [details] File: dmesg
This is the same problem that has been seen in #1023728, and my answer would be the same than the one I previously did (comment #5): "Actually, my best bet would be to test commit ce7373685ec33b94c293d9cfdb46daecb22db261, which is in v3.12. The patch is here: https://patchwork.kernel.org/patch/2836578/" However, I don't know if we plan to update F18 to 3.12.
*** This bug has been marked as a duplicate of bug 1023728 ***