From: reinette chatre <reinette.chatre@intel.com>
To: Nils Radtke <lkml@Think-Future.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: kernel BUG in iwl-agn-rs.c:2076, WAS: iwlagn + some accesspoint == hardlock
Date: Wed, 02 Jun 2010 10:51:25 -0700 [thread overview]
Message-ID: <1275501085.2091.28873.camel@rchatre-DESK> (raw)
In-Reply-To: <20100531201225.GA6327@localhost>
On Mon, 2010-05-31 at 13:12 -0700, Nils Radtke wrote:
> This line indicates the first timestamp _after_ the crash:
> May 31 17:35:19 localhost kernel: [ 69.488456]
>
> The crash happened after site A and on site B. Just arrived, opened lid and *crash*.
>
> I noticed in iwl-agn-rs.c:2080:
> BUG_ON(window->average_tpt != ((window->success_ratio *
> tbl->expected_tpt[index] + 64) / 128));
> Could that be again the point that hit me today when the machine crashed once?
> Would you mind changing this into a milder WARN? That way I wouldn't hit the wall
> that hard. And I would notice it anyway while skimming the logs as we still are on the
> hunt. It's more maintainable if it's a WARN in the src instead of me patching it w/ any
> update..
>
> Wasn't this BUG_ON a WARNING in .33.3? (didn't check..)
Seems like you performed the testing without the patch that we used to
address the hang issue from the beginning of this thread. Please see
http://marc.info/?l=linux-wireless&m=127290931304496&w=2 - that thread
also explains why the patch is not in 2.6.34.
I think it is time to move this discussion to a bug report so that it
can be tracked better. Please open a new bug at
http://bugzilla.intellinuxwireless.org/
Reinette
next prev parent reply other threads:[~2010-06-02 17:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1274380408.2091.9272.camel@rchatre-DESK>
2010-05-31 20:12 ` kernel BUG in iwl-agn-rs.c:2076, WAS: iwlagn + some accesspoint == hardlock Nils Radtke
2010-06-02 17:51 ` reinette chatre [this message]
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
[not found] <1273768269.2295.1144.camel@rchatre-DESK>
2010-05-14 17:45 ` Nils Radtke
2010-05-11 9:41 Nils Radtke
[not found] <20100503191756.GA3479@localhost>
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
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=1275501085.2091.28873.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkml@Think-Future.de \
/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