From: Drew Raines <aaraines@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: drivers/net/wireless/iwlwifi/dvm/tx.c and arch/x86/kernel/apic/ipi.c: Kernel trace when roaming between different Access Points with the same ESSID
Date: Mon, 25 Feb 2013 10:42:07 -0600 [thread overview]
Message-ID: <87bob8cpls.fsf@mid.raines.me> (raw)
In-Reply-To: 87d2vowff1.fsf@mid.raines.me
Drew Raines wrote:
> Richard Hartmann wrote:
>
>> Yet another one, this time during high USB i/o load.
>
> I've been suffering this issue as well since some version of the
> experimental Wheezy packages of 3.7.x, but it's also happening with a
> make-kpkg build of 3.8.
>
> If I switch APs in my house, my connection immediately fails and it
> won't work until I power the radio off and back on with the hardware
> switch on the side of the laptop. I can't even `modprobe -r iwlwifi'
> the driver ("FATAL: Module iwlwifi is in use.").
As I was messing around with downgrading my kernel package (where'd
3.5-trunk go??) it occurred to me that I hadn't yet tried a more
recent version of firmware-iwlwifi. I had been on 0.36+wheezy.1.
After installing 0.37 from experimental, this issue seems to have
disappeared. I've been roaming around the house watching my wlan0
reassociate several times with a `ping -i3' running and it hasn't
lost its connection.
Richard, if you haven't updated, you might want to try:
sudo apt-get -t experimental install firmware-iwlwifi
Thanks to the Intel guys for keeping this excellent hardware going on
Linux!
-Drew
next prev parent reply other threads:[~2013-02-25 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 21:09 drivers/net/wireless/iwlwifi/dvm/tx.c and arch/x86/kernel/apic/ipi.c: Kernel trace when roaming between different Access Points with the same ESSID Richard Hartmann
2013-01-29 21:09 ` Richard Hartmann
2013-02-09 19:57 ` Richard Hartmann
2013-02-25 16:01 ` Drew Raines
2013-02-25 16:42 ` Drew Raines [this message]
2013-02-28 16:10 ` Drew Raines
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=87bob8cpls.fsf@mid.raines.me \
--to=aaraines@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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.