From: Christian Borntraeger <borntraeger@de.ibm.com>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"NilsRadtkelkml@think-future.de" <NilsRadtkelkml@think-future.de>,
"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: Tue, 11 May 2010 17:50:08 +0200 [thread overview]
Message-ID: <201005111750.08533.borntraeger@de.ibm.com> (raw)
In-Reply-To: <1273163328.2226.2530.camel@rchatre-DESK>
Am Donnerstag 06 Mai 2010 18:28:48 schrieb reinette chatre:
> Below seven iwlwifi patches were added after rc4. If you are unable to
> bisect ... perhaps you can run a while by reverting more and more from
> this list?
>
> f2fa1b015e9c199e45c836c769d94db595150731 iwlwifi: correct 6000 EEPROM regulatory address
> 88be026490ed89c2ffead81a52531fbac5507e01 iwlwifi: fix scan races
> 8b9fce77737ae9983f61ec56cd53f52fb738b2c7 iwlwifi: work around bogus active chains detection
> ece6444c2fe80dab679beb5f0d58b091f1933b00 iwlwifi: need check for valid qos packet before free
> de0f60ea94e132c858caa64a44b2012e1e8580b0 iwlwifi: avoid Tx queue memory allocation in interface down
> 04f2dec1c3d375c4072613880f28f43b66524876 iwlwifi: use consistent table for tx data collect
> dd48744964296b5713032ea1d66eb9e3d990e287 iwlwifi: fix DMA allocation warnings
Just to give you some feedback. Sometimes it takes a while until it crashes.
My hand made bisect is currently at two remaining patches:
de0f60ea94e132c858caa64a44b2012e1e8580b0
8b9fce77737ae9983f61ec56cd53f52fb738b2c7
reverting both solves my hard lockup. I will try to isolate the "bad" patch
but this takes some more days since I wont be in the "hazardous environment"
this week.
Christian
next prev parent reply other threads:[~2010-05-11 15:50 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 [this message]
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
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=201005111750.08533.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=NilsRadtkelkml@think-future.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).