From: Nils Radtke <lkml@Think-Future.de>
To: reinette.chatre@intel.com
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: kernel BUG in iwl-agn-rs.c:2076, WAS: iwlagn + some accesspoint == hardlock
Date: Fri, 14 May 2010 19:45:06 +0200 [thread overview]
Message-ID: <20100514174506.GD18740@localhost> (raw)
In-Reply-To: <1273768269.2295.1144.camel@rchatre-DESK>
Hi Reinette,
Might be of interest:
[63099.789939] eth1: associated
[63166.919257] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63180.322024] Hangcheck: hangcheck value past margin!
[63190.664526] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63193.255873] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63194.941768] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63195.099286] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63196.524065] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63197.417740] iwlagn 0000:03:00.0: expected_tpt should have been calculated by now
[63199.767526] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0
[63205.689184] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0
[63210.821316] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0
[63228.178530] iwlagn 0000:03:00.0: iwl_tx_agg_start on ra = 00:1a:70:aa:aa:aa tid = 0
Happened on site B, with high throughput (280-340k/s). So, it's happening w/ both, fast
and slow conn speed.
Yes, I noticed and had a look into the compat-wireless scripts but preferred to do
it manually. Thank you for your explanation.
Cheers,
Nils
next prev parent reply other threads:[~2010-05-14 17:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 19:17 kernel BUG in iwl-agn-rs.c:2076, WAS: iwlagn + some accesspoint == hardlock NilsRadtkelkml
2010-05-03 19:22 ` John W. Linville
2010-05-06 9:14 ` Christian Borntraeger
2010-05-06 16:28 ` reinette chatre
2010-05-11 15:50 ` Christian Borntraeger
2010-05-11 17:21 ` reinette chatre
2010-05-12 15:18 ` Christian Borntraeger
2010-05-10 18:36 ` Nils Radtke
2010-05-10 23:32 ` reinette chatre
2010-05-12 14:39 ` Nils Radtke
2010-05-12 23:14 ` reinette chatre
2010-05-13 10:34 ` Nils Radtke
2010-05-13 11:32 ` Nils Radtke
2010-05-13 16:31 ` reinette chatre
2010-05-14 17:45 ` Nils Radtke [this message]
2010-05-13 15:05 ` Nils Radtke
2010-05-17 23:19 ` reinette chatre
2010-05-20 12:15 ` Nils Radtke
2010-05-20 18:33 ` reinette chatre
2010-05-31 20:12 ` Nils Radtke
2010-06-02 17:51 ` reinette chatre
2010-06-04 16:57 ` Nils Radtke
2010-06-08 17:46 ` reinette chatre
2010-06-10 14:22 ` Nils Radtke
2010-06-10 16:19 ` reinette chatre
2010-05-20 12:31 ` Nils Radtke
2010-05-20 18:26 ` reinette chatre
2010-05-20 22:30 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-05-11 9:41 Nils Radtke
2010-04-29 18:26 kernel BUG in iwl-agn-rs.c:2076,was: iwlagn + some accesspoint = hardlock lkml
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=20100514174506.GD18740@localhost \
--to=lkml@think-future.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@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).