From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Timo Juonoja <timo.juonoja@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Ubuntu 12.10 - iwl4965 problem?
Date: Fri, 25 Jan 2013 09:03:06 +0100 [thread overview]
Message-ID: <20130125080305.GA2264@redhat.com> (raw)
In-Reply-To: <CAKuDoO6q5HztQHEJE_9LRwVTDj4LhvoCb922dP_-dV3P27Q7FA@mail.gmail.com>
(CC linux-wireless mailing list)
On Fri, Jan 25, 2013 at 09:01:59AM +0200, Timo Juonoja wrote:
> I have problems on maintaining the wireless connection, when it is just in
> idle state. It works better when there are traffic ongoing, but
> occasionally there are same problems on those circumstances too. I'm using
> Ubuntu 12.10 and its default 3.5 kernel. Do you happen to know what is
> causing these problems? Is there some fixes in newer kernels related to
> iwl4965 and iwlegacy?
There are very few fixes on iwlegacy between 3.5 and current upstream,
none of them look to be related with the problem. But we have lot of
changes in mac80211, which can influence driver stability, so trying
latest upstream kernel is a good idea.
> Here are some logs from the system:
> Jan 24 22:46:55 logger kernel: [ 8287.820071] iwl4965 0000:05:00.0: Error
> sending C_ADD_STA: time out after 500ms.
> Jan 24 22:46:55 logger kernel: [ 8287.820499] ieee80211 phy0: failed to
> remove key (0, 00:23:f8:2f:e1:a2) from hardware (-110)
> Jan 24 22:46:55 logger kernel: [ 8287.872022] iwl4965 0000:05:00.0: Queue 4
> stuck for 2000 ms.
This is firmware crash. If this still happen on latest version (i.e. 3.7
or 3.8) let me know. I'll then ask you for verbose debug messages and
will try to find out what cause the firmware crash.
Stanislaw
parent reply other threads:[~2013-01-25 8:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAKuDoO6q5HztQHEJE_9LRwVTDj4LhvoCb922dP_-dV3P27Q7FA@mail.gmail.com>]
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=20130125080305.GA2264@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=timo.juonoja@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).