[BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)

[BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)

[adam.gradzki]

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

Re: [BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)

[Luciano Coelho]

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.

Re: [BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)

[adam.gradzki]

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.

Re: [BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)

[Luciano Coelho]

On Thu, 2013-08-29 at 00:38 -0400, adam.gradzki@gmail.com wrote:
> 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

Thanks again! I'll follow this up internally.

--
Cheers,
Luca.

Re: [BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)

[adam.gradzki]

Hi Luca,

I have been having wireless connectivity problems indoors on campus with this 
Intel card since I bought this laptop in September 2012. Quite often the 
wireless is completely unusable.

I can reliably reproduce this problem whenever I attempt to connect to the 
University of Pittsburgh network in several locations indoors around campus. 
The problem is very prominent when I am around APs with 6+ clients around me.

I have attached a link to my complete system log dump over 3 reboot cycles 
today.

I can connect sporadically and send a few bytes here and there before the 
wireless becomes completely unusable

I have tried connecting in Windows 8 x64 and I also experience the same 
issues, except that my network adapter goes into "Limited connectivity" mode 
and gives me a 169.x.x.x address with no IPv4 gateway.

Here is the link to my logs:
http://paste.ubuntu.com/6040891/

~ Adam

On Thursday, August 29, 2013 07:52:45 AM Luciano Coelho wrote:
> On Thu, 2013-08-29 at 00:38 -0400, adam.gradzki@gmail.com wrote:
> > 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
> 
> Thanks again! I'll follow this up internally.
> 
> --
> Cheers,
> Luca.