From: Abbas <akhan@phi9.com>
To: linux-kernel@vger.kernel.org
Subject: iwlwifi crash with queue full and qos errors
Date: Sun, 28 Oct 2012 18:26:33 -0700 [thread overview]
Message-ID: <508DDB49.1060400@phi9.com> (raw)
Reporting a possible regression with latest kernel 3.6.2-1. Intel's
iwlwifi crashes intermittently.
Downgraded to 3.5.3.1 including the microcode drivers and didnot notice
any crashes since.
Chunks from stack trace:
[108759.658475] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues
[108761.655855] iwlwifi 0000:03:00.0: Error sending REPLY_QOS_PARAM: time out
after 2000ms.
[108761.655867] iwlwifi 0000:03:00.0: Failed to update QoS
..... repetitions ....
[108844.230466] iwlwifi 0000:03:00.0: Restarting adapter queue is full
[108844.230479] iwlwifi 0000:03:00.0: Error sending REPLY_SCAN_CMD:
enqueue_hcmd failed: -28
[108844.251368] ------------[ cut here ]------------
[108844.251383] WARNING: at drivers/net/wireless/iwlwifi/iwl-io.c:150
iwl_grab_nic_access+0x7f/0xf0 [iwlwifi]()
[108844.251385] Hardware name: 2306CTO
[108844.251477] Pid: 12818, comm: kworker/u:0 Not tainted 3.6.2-1-ARCH #1
[108844.251479] Call Trace:
[108844.251489] [<ffffffff81055c2f>] warn_slowpath_common+0x7f/0xc0
[108844.251495] [<ffffffff81055d26>] warn_slowpath_fmt+0x46/0x50
[108844.251501] [<ffffffffa04e4838>] ? iwl_grab_nic_access_silent+0x188/0x200
------
abbas
reply other threads:[~2012-10-29 2:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=508DDB49.1060400@phi9.com \
--to=akhan@phi9.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome