Hide Forgot
Description of problem: I directed it to "suspend to RAM". I could see ABRT catch the error in the moments before the suspend took effect. It seems to have awoken just fine, I see some verbage about wireless in the error trace. Let me know if you need more info about my configuration. Additional info: reporter: libreport-2.1.6 WARNING: at net/mac80211/key.c:597 ieee80211_free_keys+0x150/0x160 [mac80211]() Modules linked in: fuse ebtable_nat nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE rfcomm ip6table_nat nf_nat_ipv6 ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables bnep dell_wmi iTCO_wdt iTCO_vendor_support sparse_keymap arc4 iwl3945 iwlegacy dell_laptop dcdbas snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm acpi_cpufreq mperf coretemp kvm_intel kvm mac80211 cfg80211 snd_page_alloc btusb bluetooth snd_timer rfkill b44 ssb snd soundcore microcode joydev radeon lpc_ich i2c_algo_bit sdhci_pci mfd_core ttm mii i2c_i801 sdhci drm_kms_helper r592 memstick mmc_core drm i2c_core wmi video uinput firewire_ohci firewire_core crc_itu_t CPU: 0 PID: 410 Comm: NetworkManager Not tainted 3.10.9-200.fc19.i686.PAE #1 Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 00000000 00000000 f1e7d9ec c098220b f1e7da14 c044a18e c0b17b3a f84efc01 00000255 f84bcdf0 f84bcdf0 f3d3b6e0 f3d3b6e0 f3d3b6ec f1e7da24 c044a252 00000009 00000000 f1e7da50 f84bcdf0 00000292 f3d3b500 f3d3b500 f3d3b6ec Call Trace: [<c098220b>] dump_stack+0x16/0x18 [<c044a18e>] warn_slowpath_common+0x5e/0x80 [<f84bcdf0>] ? ieee80211_free_keys+0x150/0x160 [mac80211] [<f84bcdf0>] ? ieee80211_free_keys+0x150/0x160 [mac80211] [<c044a252>] warn_slowpath_null+0x22/0x30 [<f84bcdf0>] ieee80211_free_keys+0x150/0x160 [mac80211] [<f84aa406>] ieee80211_do_stop+0x266/0x760 [mac80211] [<c0987823>] ? _raw_spin_unlock_bh+0x13/0x20 [<f84aa917>] ieee80211_stop+0x17/0x20 [mac80211] [<c0894439>] __dev_close_many+0x69/0xb0 [<c08acbfb>] ? netpoll_rx_disable+0x3b/0x50 [<c08944b6>] __dev_close+0x36/0x50 [<c0899f81>] __dev_change_flags+0x81/0x160 [<c089a0e8>] dev_change_flags+0x18/0x50 [<c08a6167>] do_setlink+0x2d7/0x830 [<c0694f72>] ? nla_parse+0x22/0xa0 [<c08a72c8>] rtnl_newlink+0x388/0x570 [<c062519c>] ? selinux_capable+0x2c/0x40 [<c061f57c>] ? security_capable+0x1c/0x30 [<c08a4008>] rtnetlink_rcv_msg+0x88/0x1f0 [<c08a3f80>] ? rtnetlink_rcv+0x30/0x30 [<c08bdbf6>] netlink_rcv_skb+0x86/0xa0 [<c08a3f71>] rtnetlink_rcv+0x21/0x30 [<c08bd35f>] netlink_unicast+0xbf/0x150 [<c08bd62a>] netlink_sendmsg+0x23a/0x670 [<c088439b>] sock_sendmsg+0x7b/0xb0 [<c08846a1>] ___sys_sendmsg+0x291/0x2a0 [<c08846b0>] ? ___sys_sendmsg+0x2a0/0x2a0 [<c0884dfe>] ? SYSC_sendto+0x10e/0x130 [<c0586e17>] ? fsnotify+0x1f7/0x2d0 [<c0885548>] __sys_sendmsg+0x38/0x70 [<c0885596>] SyS_sendmsg+0x16/0x20 [<c0885c7b>] SyS_socketcall+0x29b/0x2f0 [<c04ba2b6>] ? __audit_syscall_exit+0x1c6/0x260 [<c04ba0a4>] ? __audit_syscall_entry+0x94/0xe0 [<c098eacd>] sysenter_do_call+0x12/0x28
Created attachment 790746 [details] File: dmesg
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
Josh, I have to admit that I never encountered this error again. I tried suspend on the affected machine a few times with this latest kernel (3.11.1-200) and it worked fine.
OK. We'll close this out for now. If you see it again, please reopen.
Saw this with 3.11.4-201.
Created attachment 822616 [details] Another dmesg I don't know how it happened.
Description of problem: I was trying to yum upgrade my system and my wireless was hung up. I turned my wireless off then back on to reset it. This fixed my yum issue, but also caused the reported error. Version-Release number of selected component: kernel Additional info: reporter: libreport-2.1.9 cmdline: BOOT_IMAGE=/vmlinuz-3.11.6-200.fc19.i686 root=/dev/mapper/fedora_banana3k-root ro rd.lvm.lv=fedora_banana3k/swap rd.dm=0 rd.lvm.lv=fedora_banana3k/root vconsole.keymap=us rd.md=0 rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8 kernel: 3.11.6-200.fc19.i686 runlevel: N 5 type: Kerneloops Truncated backtrace: WARNING: CPU: 1 PID: 560 at net/mac80211/key.c:597 ieee80211_free_keys+0x150/0x160 [mac80211]() Modules linked in: fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE bnep bluetooth 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 coretemp snd_hda_codec_idt arc4 snd_hda_intel snd_hda_codec iwl3945 iwlegacy gpio_ich microcode snd_hwdep mac80211 b44 ssb mii snd_seq dell_wmi sparse_keymap iTCO_wdt dell_laptop snd_seq_device iTCO_vendor_support i2c_i801 wmi of_i2c sdhci_pci sdhci mmc_core joydev cfg80211 snd_pcm snd_page_alloc dcdbas snd_timer snd rfkill soundcore serio_raw lpc_ich r592 memstick video acpi_cpufreq mperf uinput radeon firewire_ohci ata_generic i2c_algo_bit pata_acpi drm_kms_helper firewire_core ttm crc_itu_t drm i2c_core CPU: 1 PID: 560 Comm: NetworkManager Not tainted 3.11.6-200.fc19.i686 #1 Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 00000000 00000000 f292b9e0 c0979529 00000000 f292ba10 c0447b0e c0b0b8b4 00000001 00000230 f8b5dbc0 00000255 f8b2bf70 f8b2bf70 f45e06cc f45e06cc f45e06d8 f292ba20 c0447bd2 00000009 00000000 f292ba4c f8b2bf70 00000286 Call Trace: [<c0979529>] dump_stack+0x41/0x52 [<c0447b0e>] warn_slowpath_common+0x7e/0xa0 [<f8b2bf70>] ? ieee80211_free_keys+0x150/0x160 [mac80211] [<f8b2bf70>] ? ieee80211_free_keys+0x150/0x160 [mac80211] [<c0447bd2>] warn_slowpath_null+0x22/0x30 [<f8b2bf70>] ieee80211_free_keys+0x150/0x160 [mac80211] [<f8b19396>] ieee80211_do_stop+0x266/0x770 [mac80211] [<c097f313>] ? _raw_spin_unlock_bh+0x13/0x20 [<f8b198b7>] ieee80211_stop+0x17/0x20 [mac80211] [<c0893f69>] __dev_close_many+0x69/0xb0 [<c0893fe2>] __dev_close+0x32/0x50 [<c0899f31>] __dev_change_flags+0x81/0x160 [<c089a0b8>] dev_change_flags+0x18/0x50 [<c08a6317>] do_setlink+0x2e7/0x820 [<c042dab8>] ? smp_apic_timer_interrupt+0x38/0x50 [<c097fafc>] ? apic_timer_interrupt+0x34/0x3c [<c0698a02>] ? nla_parse+0x22/0xa0 [<c08a73f8>] rtnl_newlink+0x388/0x570 [<c0627d4c>] ? selinux_capable+0x2c/0x40 [<c062234c>] ? security_capable+0x1c/0x30 [<c08a4018>] rtnetlink_rcv_msg+0x88/0x1f0 [<c08a3f90>] ? rtnetlink_rcv+0x30/0x30 [<c08bdfc6>] netlink_rcv_skb+0x86/0xa0 [<c08a3f81>] rtnetlink_rcv+0x21/0x30 [<c08bd6bf>] netlink_unicast+0xbf/0x150 [<c08bd9bd>] netlink_sendmsg+0x26d/0x6e0 [<c08838eb>] sock_sendmsg+0x7b/0xb0 [<c0883bf1>] ___sys_sendmsg+0x291/0x2a0 [<c0883c00>] ? ___sys_sendmsg+0x2a0/0x2a0 [<c088434e>] ? SYSC_sendto+0x10e/0x130 [<c0478f07>] ? update_curr+0xc7/0x180 [<c0587517>] ? fsnotify+0x1f7/0x2d0 [<c04768fd>] ? __enqueue_entity+0x6d/0x80 [<c047a11c>] ? put_prev_task_fair+0x5c/0x4a0 [<c0884a88>] __sys_sendmsg+0x38/0x70 [<c0884ad6>] SyS_sendmsg+0x16/0x20 [<c08851bb>] SyS_socketcall+0x29b/0x2f0 [<c04b8ed6>] ? __audit_syscall_exit+0x1c6/0x260 [<c04b8cc4>] ? __audit_syscall_entry+0x94/0xe0 [<c098688d>] sysenter_do_call+0x12/0x28
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
This bug is probably not fixed, but since it rare race condition which result in nothing more harmful than a WARNING , I'm closing this bug.