All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Tim Walberg <twalberg@comcast.net>,
	Kristoffer Ericson <kristoffer.ericson@gmail.com>,
	"Justin P. Mattock" <justinmattock@gmail.com>,
	Stefan Lippers-Hollmann <s.L-H@gmx.de>,
	linux-wireless@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Disassociating atheros wlan with 2.6.31
Date: Wed, 07 Oct 2009 18:49:59 -0700	[thread overview]
Message-ID: <4ACD4547.2000306@gmail.com> (raw)
In-Reply-To: <20091008011247.GC22458@comcast.net>

Tim Walberg wrote:
> Another confirmed instance of this on ath9k - on 2.6.31.2 and 2.6.31.3 - didn't
> happen on 2.6.30.6 or 2.6.30.9. A couple other interesting facts:
>
> - it seems to be related (at least in my case) to heavy transmit load -
>    I can download a kernel tarball without it failing, but if I try to
>    copy it to another system, it fails within 2 seconds reliably...
> - running 'rmmod ath9k ath mac80211 cfg80211' followed by 'modprobe ath9k'
>    clears it up
>
> No indication in dmesg except:
>
> 	wlan<n>: no probe response from AP AA:BB:DD:EE:FF:GG - disassociating
>
> and suddenly no packets going in either direction.
>
> I'm in the process of moving back to 2.6.30.x for now...
>
>
>
>
>
> On 10/04/2009 17:45 +0200, Kristoffer Ericson wrote:
>    
>
>    
I get this reliably by simple running a radio station
through mplayer(probably around 5/10 min of running)
when I run this commit:
2.6.31-rc8-00039-g03c3bbc I don't have this at all.
(I might of changed my .config without realizing it)

After running a bisect from this commit to current
I came up with nothing, which led me to believe that I must have through
the confusion changed something in my .config, or messed up
with choosing good/bad with the bisect because I didn't wait long enough for
this to fire off.

In any case either/or I'm still going to give a go at the bisect again
but this time wait longer(10/20 min) to really make sure I don't miss
anything.

BTW: when this hits for you is it pretty bad(no connection) i.g when 
this fires off over here
music still plays from mplayer, but did notice that mplayer player all 
of a sudden would die out, but
easily connected again.

Justin P. Mattock

      reply	other threads:[~2009-10-08  1:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 10:16 Disassociating atheros wlan with 2.6.31 Kristoffer Ericson
2009-09-24 18:26 ` Justin P. Mattock
2009-09-24 19:55   ` Stefan Lippers-Hollmann
2009-09-24 20:07     ` Justin P. Mattock
2009-09-29  9:16       ` Kristoffer Ericson
2009-09-30 10:53       ` Kristoffer Ericson
2009-10-04 15:45       ` Kristoffer Ericson
2009-10-05  0:20         ` Justin Mattock
2009-10-08  1:12         ` Tim Walberg
2009-10-08  1:49           ` Justin P. Mattock [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=4ACD4547.2000306@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=s.L-H@gmx.de \
    --cc=twalberg@comcast.net \
    /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.