linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Norbert Preining <preining@logic.at>
To: Dave Jones <davej@redhat.com>, Ted Ts'o <tytso@mit.edu>,
	David Miller <davem@davemloft.net>,
	egrumbach@gmail.com, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net, ilw@linux.intel.com
Subject: Re: 3.4-rc2, ilwagn still most of the time completely unusable
Date: Thu, 12 Apr 2012 08:01:57 +0900	[thread overview]
Message-ID: <20120411230157.GC12332@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <20120411200105.GA22002@redhat.com>

On Mi, 11 Apr 2012, Dave Jones wrote:
>  > I'll note that I've been having troubles with my iwlagn driver losing
>  > the ability to connect to WPA2 authenticated AP's at work (Google
>  > Cambridge).  This has been true for since sometime around 3.0; my
>  > excuse for why I haven't tried bisecting it is that it can take
>  > several hours for the bug to manifest itself, and when it does, it's
>  > much simpler to either (a) reboot, or (b) rmmod iwlagn and then
>  > modprobe iwlagn.

Agreed. 150%

> iwlwifi has a debug module option which generates a ton of spew, but
> the Intel developers have managed to diagnose several iwlwifi problems

I sent already several times *loads* of these dumps to the developers.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
MELLON UDRIGLE (n.)
The ghastly sound made by traditional folksingers.
			--- Douglas Adams, The Meaning of Liff

  reply	other threads:[~2012-04-11 23:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  1:17 iwlagn (3.3-wl), the saga continuous Norbert Preining
2012-04-11  2:37 ` 3.4-rc2, ilwagn still most of the time completely unusable Norbert Preining
2012-04-11  2:54   ` David Miller
2012-04-11 18:40     ` Ted Ts'o
2012-04-11 20:01       ` Dave Jones
2012-04-11 23:01         ` Norbert Preining [this message]
2012-04-11 23:24   ` Venkataraman, Meenakshi
2012-04-12  0:02     ` Norbert Preining
2012-04-13  1:32       ` Venkataraman, Meenakshi
2012-04-13  1:40         ` Norbert Preining
     [not found]           ` <59083F8344AE164EB150C0518405C0680E0F285C@FMSMSX107.amr.corp.intel.com>
2012-06-28  7:25             ` Norbert Preining
2012-06-28  7:51               ` [Ilw] " Johannes Berg
2012-06-28  8:16                 ` Norbert Preining
2012-07-03 19:35                   ` Alessandro Suardi
2012-07-12  8:14                   ` Norbert Preining
2012-07-12 16:16                     ` Johannes Berg
2012-07-25  3:07                       ` Norbert Preining
2012-04-13  5:38         ` Norbert Preining
2012-04-25  1:06           ` Venkataraman, Meenakshi
2012-04-26  0:51             ` Norbert Preining

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=20120411230157.GC12332@gamma.logic.tuwien.ac.at \
    --to=preining@logic.at \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=egrumbach@gmail.com \
    --cc=ilw@linux.intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).