From mboxrd@z Thu Jan  1 00:00:00 1970
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Date: Wed, 16 Dec 2009 15:43:08 -0800
Subject: [ath9k-devel] Linux bug 14267 "No probe response from AP after
 500ms, disconnecting."
In-Reply-To: <20091216222157.28840.qmail@stuge.se>
References: <20091216172356.15849.qmail@stuge.se> <20091216174112.GD11461@tux>
	<20091216222157.28840.qmail@stuge.se>
Message-ID: <20091216234308.GA425@tux>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On Wed, Dec 16, 2009 at 02:21:57PM -0800, Peter Stuge wrote:
> Hi,
> 
> Luis R. Rodriguez wrote:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=14267#c55
> >
> > That bug report is about issues (so far AR5416 only reported with
> > the PS issue) about disconnections with your AP if PS is left
> > enabled by default which will trigger dynamic PS to be enabled by
> > by default, its all about 2.6.32.
> 
> I observe the exact same problem with my two kernels. One was
> 2.6.32-rc6 and now with wl-testing.

2.6.32-rc6 is ancient :)

> > The fix on 2.6.32 which should help AR5416 (so far concrete device
> > with issues) is to disable PS by default.
> >
> > You can also disable PS manually if your kernel has it enabled:
> >
> > iwconfig wlan0 power off
> 
> This worked well for me during brief testing with the -rc6 kernel. I
> then switched to wl-testing to be up to date.

That's indeed a good move to test.

> The fix to disable by
> default is included in my kernel, and PS is off. I still observe the
> problem, although it is much less frequent. Ie. the fix does not
> solve the problem for me. I'm not saying that it neccessarily is
> exactly the same problem, but the manifestation is; I am
> disconnected. :)

Well so depending on the device you have you may need some patches which
may or may not have been present on wireless-testing. Some recent fixes
for ath9k on 2.6.32 and wireless-testing are important, Sujith also posted
some recent fixes. They don't all pertain to power save but some do. On your
bug report you did not indicate if you tested 2.6.32 with the latest patches
I had suggested to Justin.

> > Your post on that bug report is very different, you say you have
> > merged wireless-testing into your kernel (why??),
> 
> I was running drm-intel.git to get some bleeding edge KMS patches. I
> had that git so it was easy to pull in wl-testing, and I thought it
> would make debugging and working with the experts easier. (And to
> rule out that it had been fixed, of course. :)

It does help, absolutely, its what we prefer for debugging.

> > you also posted a log but it doesn't contain the initailization
> > part of ath9k so your card device cannot be seen. What card is this
> > with?
> 
> I did not find this bug at first, and so I started posting
> information in bug 14664, my init information and more background is
> there: http://bugzilla.kernel.org/show_bug.cgi?id=14664#c1
> After a while I found 14267 and realized that 14664 was a dup.

OK you also have an AR5416, which is the first 11n chipset generation
for Atheros, the bug report was originally for AR9280. Justin also
has an AR5416.

Lets make sure to keep these separate.

> > Please keep stable kernel bugs apart from wireless-testing bugs.
> 
> It looks like it is actually one and the same bug.

No, its one whole hardware generation part, the symptoms are
certainly the same though but I have not gotten indication from
AR2980 users that the issues are present there -- and that's
frankly what we have mainly been testing with.

> It's not fixed for me by the committed workaround. It is of course
> possible that it is in fact a different bug producing identical
> symptoms, even more so since I don't have exactly the same hardware.

Right.

> > Wireless-testing is bleedinge edge and as such if you have issues
> > you should use ath9k-devel or the linux-wireless list (like this)
> > and not post on bug reports for stable bugs.
> 
> Nod. Let's go. How can I help further? Since the attachment log I
> posted I had another failure here, now I have a debug log also with
> some more activity before the failure. Should I attach it?

Try sucking in Sujith's recent posted patches, although none of those
are PS fixes, and you can also follow the instructions I gave Justin
to help debug things.

  Luis