From: adam.gradzki@gmail.com
To: Luciano Coelho <luciano.coelho@intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [BUG] iwlwifi Microcode SW error (firmware version: 18.168.6.1)
Date: Thu, 29 Aug 2013 12:35:30 -0400 [thread overview]
Message-ID: <11203548.8TH3DJmvk0@nuclearreactor> (raw)
In-Reply-To: <1377751965.4418.4.camel@porter.coelho.fi>
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.
prev parent reply other threads:[~2013-08-29 16:36 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
2013-08-29 4:52 ` Luciano Coelho
2013-08-29 16:35 ` adam.gradzki [this message]
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=11203548.8TH3DJmvk0@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.