All of lore.kernel.org
 help / color / mirror / Atom feed
From: adam.gradzki@gmail.com
To: Luciano Coelho <luciano.coelho@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)
Date: Thu, 29 Aug 2013 00:38:20 -0400	[thread overview]
Message-ID: <2449090.W0ZgYRKzHN@nuclearreactor> (raw)
In-Reply-To: <1377750599.4418.3.camel@porter.coelho.fi>

Hi Luca,

I was browsing the web while in a large hall with many connected wireless 
clients. There were also several routers sharing a common SSID. I remember 
playing with various RTS and fragmentation thresholds so this may have been 
the trigger. The connection itself involved WPA2 Enterprise PEAP w/ MSCHAPv2 
authentication. I wish I could go into more detail but I was browsing the 
system log long after the fact so I'm having trouble remembering things off the 
top of my head.

Linux laptop 3.10.9-1-ARCH #1 SMP PREEMPT Wed Aug 21 13:49:35 CEST 2013 x86_64 
GNU/Linux

Regards,
Adam


On Thursday, August 29, 2013 07:29:59 AM you wrote:
> Hi Adam,
> 
> On Thu, 2013-08-29 at 00:17 -0400, adam.gradzki@gmail.com wrote:
> > I would like to report a problem with the Intel iwlwifi driver
> > Here is what I found in my system log:
> > 
> > http://pastebin.com/j5cVsqzz
> 
> Thanks for reporting! Could you please give a bit more details on what
> you were doing when this happened? Just a simple connection to an AP?
> Heavy traffic?
> 
> --
> Cheers,
> Luca.


  reply	other threads:[~2013-08-29  4:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  4:17 [BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1) adam.gradzki
2013-08-29  4:29 ` Luciano Coelho
2013-08-29  4:38   ` adam.gradzki [this message]
2013-08-29  4:52     ` Luciano Coelho
2013-08-29 16:35       ` adam.gradzki

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=2449090.W0ZgYRKzHN@nuclearreactor \
    --to=adam.gradzki@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.