Bug 906555 - [abrt]: WARNING: at drivers/net/wireless/iwlwifi/pcie/tx.c:584 iwl_enqueue_hcmd+0x65c/0x670 [iwlwifi]()
Summary: [abrt]: WARNING: at drivers/net/wireless/iwlwifi/pcie/tx.c:584 iwl_enqueue_hc...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c14398b2661ee3e946b3d6e6b0f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-31 21:39 UTC by Suren Karapetyan
Modified: 2013-08-01 10:51 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 10:51:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
full dmesg (141.21 KB, text/plain)
2013-03-21 19:11 UTC, Suren Karapetyan
no flags Details

Description Suren Karapetyan 2013-01-31 21:39:57 UTC
Additional info:
WARNING: at drivers/net/wireless/iwlwifi/pcie/tx.c:584 iwl_enqueue_hcmd+0x65c/0x670 [iwlwifi]()
Hardware name: HP Compaq 6730b 
Modules linked in: nfsv3 nfs_acl nfsv4 auth_rpcgss nfs dns_resolver fscache uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media fuse ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_CHECKSUM iptable_mangle bridge stp llc lockd sunrpc be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi rfcomm ib_iser bnep rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 ip6table_filter nf_defrag_ipv4 xt_state nf_conntrack ib_core iscsi_tcp libiscsi_tcp ip6_tables libiscsi scsi_transport_iscsi arc4 iwldvm mac80211 snd_hda_codec_analog btusb bluetooth snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer hp_wmi snd coretemp sparse_keymap iwlwifi cfg80211 hp_accel lis3lv02d iTCO_wdt soundcore serio_raw rfkill iTCO_vendor_support lpc_ich input_polldev mfd_core microcode tg3 vhost_net tun macvtap macvlan kvm_intel kvm uinput 
binfmt_misc firewire_ohci firewire_core crc_itu_t wmi i915 video i2c_algo_bit drm_kms_helper drm i2c_core
Pid: 5916, comm: kworker/0:2 Not tainted 3.7.3-101.fc17.x86_64 #1
Call Trace:
 [<ffffffff8105e69f>] warn_slowpath_common+0x7f/0xc0
 [<ffffffff8105e6fa>] warn_slowpath_null+0x1a/0x20
 [<ffffffffa029199c>] iwl_enqueue_hcmd+0x65c/0x670 [iwlwifi]
 [<ffffffffa0292454>] iwl_trans_pcie_send_cmd+0xe4/0x440 [iwlwifi]
 [<ffffffff810825b0>] ? wake_up_bit+0x40/0x40
 [<ffffffffa0456902>] iwl_dvm_send_cmd+0x52/0x140 [iwldvm]
 [<ffffffffa0457c1f>] iwl_send_calib_results+0x6f/0xc0 [iwldvm]
 [<ffffffffa0452a1d>] iwl_alive_notify+0x18d/0x1f0 [iwldvm]
 [<ffffffffa0453002>] iwl_load_ucode_wait_alive+0x2b2/0x340 [iwldvm]
 [<ffffffffa04526b0>] ? iwl_alloc_all+0x30/0x30 [iwldvm]
 [<ffffffffa04511aa>] iwlagn_mac_start+0x13a/0x220 [iwldvm]
 [<ffffffffa03c89da>] ieee80211_reconfig+0x1da/0x1080 [mac80211]
 [<ffffffff8162e98d>] ? mutex_lock+0x1d/0x50
 [<ffffffffa03a3792>] ieee80211_restart_work+0x92/0xb0 [mac80211]
 [<ffffffff8107a4a7>] process_one_work+0x147/0x490
 [<ffffffffa03a3700>] ? ieee80211_recalc_smps_work+0x20/0x20 [mac80211]
 [<ffffffff8107cd3e>] worker_thread+0x15e/0x450
 [<ffffffff8107cbe0>] ? busy_worker_rebind_fn+0x110/0x110
 [<ffffffff81081ca0>] kthread+0xc0/0xd0
 [<ffffffff81010000>] ? ftrace_raw_event_xen_mmu_flush_tlb_others+0x50/0xe0
 [<ffffffff81081be0>] ? kthread_create_on_node+0x120/0x120
 [<ffffffff816396ec>] ret_from_fork+0x7c/0xb0
 [<ffffffff81081be0>] ? kthread_create_on_node+0x120/0x120

Potential duplicate: bug 906102

Comment 1 Stanislaw Gruszka 2013-03-13 09:12:53 UTC
Please attach full dmesg file (with this warning included), which you can find in .cache/abrt/spool/oops-{DATE}/ or in /var/spool/abrt/oops-{DATE}/

Comment 2 Suren Karapetyan 2013-03-21 19:11:17 UTC
Created attachment 714054 [details]
full dmesg

I've carelessly deleted the exact oops I've reported, but this one looks exactly alike.

Comment 3 Stanislaw Gruszka 2013-03-22 07:31:25 UTC
First firmware report error at:

[ 4615.498306] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.

and after some time it hangs:

[13230.722031] iwlwifi 0000:02:00.0: fail to flush all tx fifo queues
[13232.728049] iwlwifi 0000:02:00.0: Error sending REPLY_ADD_STA: time out after 2000ms.
[13232.728054] iwlwifi 0000:02:00.0: Current CMD queue read_ptr 172 write_ptr 181

So this is another iwlwifi firmware problem, CCing: Intel ...

Comment 4 Fedora End Of Life 2013-07-04 03:23:22 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.

Comment 5 Fedora End Of Life 2013-08-01 10:51:18 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.