From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: [Bug #14267] Disassociating atheros wlan
Date: Sun, 22 Nov 2009 08:09:10 -0800 [thread overview]
Message-ID: <4B096226.4040505@gmail.com> (raw)
In-Reply-To: <20091122162131.0e2e60ef.kristoffer.ericson@gmail.com>
Kristoffer Ericson wrote:
> On Sun, 22 Nov 2009 15:19:54 +0100
> "Rafael J. Wysocki"<rjw@sisk.pl> wrote:
>
>
>> On Sunday 22 November 2009, Johannes Berg wrote:
>>
>>> On Sat, 2009-11-21 at 09:38 -0800, Justin P. Mattock wrote:
>>>
>>>
>>>> I did a bisect yesterday on this, and the results
>>>> seemed to have worked over here by reverting:
>>>>
>>>> 75e6c3b72b3ab01c47629f3fbd0fed4e6550bf3a
>>>> cfg80211: lower dynamic PS timeout to 100ms
>>>>
>>>> if Kristoffer can try reverting this one
>>>> to see, then we can go from there.
>>>>
>>> So that just means the driver is broken. Please run
>>>
>>> iwconfig wlan0 power off
>>>
>>> to fix it then. And the patch below will disable it by default since
>>> it's broken.
>>>
>>> johannes
>>>
>>> --- wireless-testing.orig/drivers/net/wireless/ath/ath9k/main.c 2009-11-22 11:44:41.000000000 +0100
>>> +++ wireless-testing/drivers/net/wireless/ath/ath9k/main.c 2009-11-22 11:45:26.000000000 +0100
>>> @@ -1893,6 +1893,8 @@ void ath_set_hw_capab(struct ath_softc *
>>> BIT(NL80211_IFTYPE_ADHOC) |
>>> BIT(NL80211_IFTYPE_MESH_POINT);
>>>
>>> + hw->wiphy->ps_default = false;
>>> +
>>> hw->queues = 4;
>>> hw->max_rates = 4;
>>> hw->channel_change_time = 5000;
>>>
>> OK, so perhaps this patch should be applied until th ath9k driver is fixed? Luis? John?
>>
>
> I applied the patch from johannes and it ended my issues atleast. I ran my machine for approx
> 2 hours without seeing the disconnect issue (which I usually saw after 15-25min). Cant be 100% of course
> but so far so good.
>
> I agree with Justin that we could wait until he gets a chance to test it. It should be accepted
> after initial merge (and stable trees) after that I think. Rafael thoughts?
>
> Also, we should notify the atheros people so they could start fixing the driver (in a perfect world).
>
> Best wishes
> Kristoffer Ericson
>
>
>
>
I can probably test it out, main problem
is where I'm headed internet connection might
not be strong enough to run any kind of media
(hotel connections are only strong enough to retrieve e-mails
streaming music/movies can be a bit much). luckily
I'm away only for a few days.
Justin P. Mattock
prev parent reply other threads:[~2009-11-22 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 14:59 2.6.32-rc8-git1: Reported regressions 2.6.30 -> 2.6.31 Rafael J. Wysocki
[not found] ` <4B08258E.9050607@gmail.com>
[not found] ` <1258886823.7094.101.camel@johannes.local>
2009-11-22 14:19 ` [Bug #14267] Disassociating atheros wlan Rafael J. Wysocki
2009-11-22 15:21 ` Kristoffer Ericson
2009-11-22 16:09 ` 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=4B096226.4040505@gmail.com \
--to=justinmattock@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kernel-testers@vger.kernel.org \
--cc=kristoffer.ericson@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=rjw@sisk.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).