From: Marcel Holtmann <marcel@holtmann.org>
To: "Guy, Wey-Yi W" <wey-yi.w.guy@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: iwlagn and many firmware restarts with Fedora kernel
Date: Mon, 19 Jul 2010 16:28:38 -0700 [thread overview]
Message-ID: <1279582118.4572.42.camel@localhost.localdomain> (raw)
In-Reply-To: <E9954878DD1FB34FAE5187FB88C58A350120692494@orsmsx506.amr.corp.intel.com>
Hi Wey,
> so during the last few weeks, I have seen a huge amount of firmware
> restarts with my Intel 5350 card and Fedora 13 kernel (2.6.33.6-147).
>
> iwlagn 0000:03:00.0: low ack count detected, restart firmware
> iwlagn 0000:03:00.0: On demand firmware reload
> iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting
> iwlagn 0000:03:00.0: queue number out of range: 0, must be 10 to 19
>
> If this happens then I don't see it once, I normally see this 10-20
> times and the connectivity is stalled until the cards comes back to
> life. I have seen patches that should have fixed this symptom, but they
> might be also send to -stable since this is a major hassle.
>
> The time without connectivity is something around 4-5 minutes or longer
> when this happens. Not really funny.
>
> Which patch you referring to? I will try to work on submit it to stable.
no patch in particular, I just have seen some commit messages that would
be indicating this got fixed.
Regards
Marcel
next prev parent reply other threads:[~2010-07-19 23:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 18:43 iwlagn and many firmware restarts with Fedora kernel Marcel Holtmann
2010-07-19 22:23 ` Guy, Wey-Yi W
2010-07-19 23:28 ` Marcel Holtmann [this message]
2010-07-19 22:33 ` drago01
2010-07-19 23:29 ` Marcel Holtmann
2010-07-19 23:56 ` Guy, Wey-Yi
2010-07-21 19:59 ` drago01
2010-07-21 20:37 ` Guy, Wey-Yi
2010-07-21 21:00 ` drago01
2010-07-22 18:37 ` Guy, Wey-Yi
2010-07-23 22:32 ` drago01
2010-07-24 4:34 ` Guy, Wey-Yi W
2010-07-25 21:25 ` drago01
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=1279582118.4572.42.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.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).