linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nils Radtke <lkml@Think-Future.de>
To: reinette.chatre@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG in iwl-agn-rs.c:2076, WAS: iwlagn + some accesspoint == hardlock
Date: Thu, 13 May 2010 17:05:06 +0200	[thread overview]
Message-ID: <20100513150504.GB7535@localhost> (raw)
In-Reply-To: <1273706072.2295.67.camel@rchatre-DESK>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

  Hi Reinette,

Attached the output from the debug-enabled in-tree iwlwifi driver connects.

The order of trial is: site A first, then site B. The sites have thus been visited 
in the same order as last time and the commands executed have been equally the
same. The failures evenly.. All the log entries that caught my eye last time
can be found in the attached one also. I'm sending it bz2 compressed. My uplink
is a poor man's volume limited UMTS one.

The timestamp that is the last entry for site A log is: 4174.659838
Everthing after that timestamp is log for site B, 10 minutes by bike from site A.

We've been lucky, I could just finish site B survey as heaven opened it's doors such
wide that the streets flooded within seconds. Before that mosquitos took the chance 
and bit me a dozen of times (*scratch*). I hope it was worth it and there's something 
to be found in the logs. ;)

If there's anything else, let me know.

  Cheers,

                  Nils


[-- Attachment #2: 2010-05-13_iwlwifi_dbg_filter.bz2 --]
[-- Type: application/octet-stream, Size: 99247 bytes --]

  parent reply	other threads:[~2010-05-13 15:05 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
2010-05-13 15:05           ` Nils Radtke [this message]
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=20100513150504.GB7535@localhost \
    --to=lkml@think-future.de \
    --cc=linux-kernel@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).