On 03/14/2013 04:50 AM, Steven Haigh wrote:
> On 14/03/13 16:20, Steven Haigh wrote:
>> On 14/03/13 09:42, Steven Haigh wrote:
>>> On 03/14/2013 01:54 AM, Matt Lewandowsky wrote:
>>>> On Wed, 13 Mar 2013 19:27:48 +1100, From: [log in to unmask]
>>>>
>>>>> So, as far as the access point goes, it seems the client disassociates
>>>>> itself, then associates again.
>>>>>
>>>>> The PC seems think that the access point has gone away, and
>>>>> disconnects.
>>>>>
>>>>> Strange.
>>>>
>>>>
>>>> When your system thinks the AP has gone away, do any other associated
>>>> clients believe this, as well? Do you see this behavior if one of them
>>>> does large amounts of traffic?
>>>
>>> Interestingly, no. The laptop didn't either under the Windows 7 drivers.
>>> It just seems under linux now, it drops out.
>>>
>>> What is driving me insane is that work has a WRT54GL router running
>>> dd-wrt and that *doesn't* drop out. I have a WRT54GS running dd-wrt and
>>> it does.
>>>
>>> I've been trying different versions of dd-wrt at home - thinking maybe
>>> that is where the issue lies - but as yet, I haven't managed to track it
>>> down.
>>>
>>
>> As a data point here, I'm going to try installing Fedora 18 (urrgh) to
>> see if it still drops out. Don't worry, I'll be back - but I need more
>> info ;)
>>
>
> Ok - so now I am completely confused. Fedora 18 was up for 2 hours, not a 
> single wifi dropout.
>
> The output of 'iw event -t' shows:
> 1363253967.217613: wlan0 (phy #0): scan started
> 1363253970.972935: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 
> 2437 2442 2447 2452 2457 2462 2467 2472 2484, ""
> 1363253970.974107: wlan0 (phy #0): connection quality monitor event: RSSI 
> went below threshold
> 1363254087.216325: wlan0 (phy #0): scan started
> 1363254090.968303: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 
> 2437 2442 2447 2452 2457 2462 2467 2472 2484, ""
> 1363254090.975328: wlan0 (phy #0): connection quality monitor event: RSSI 
> went below threshold
> 1363254207.218842: wlan0 (phy #0): scan started
> 1363254210.965364: wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 
> 2437 2442 2447 2452 2457 2462 2467 2472 2484, ""
> 1363254210.972594: wlan0 (phy #0): connection quality monitor event: RSSI 
> went below threshold
> 1363254282.979366: wlan0 (phy #0): connection quality monitor event: RSSI 
> went below threshold
>
> Not a single drop... One thing I noticed is that I think the 'unknown event' 
> in the SL wireless output is the connection quality notice above.
>
> So. Where to go from here?
>
> Fedora 18:
> kernel-3.8.2-206
> wireless-tools-29-8.1
>
> SL6.4
> kernel-3.8.2 (from elrepo)
> wireless-tools-29-5.1.1
>
> Pat: Any ideas? Now I'm stumped unless I file a bug upstream? As its not a 
> EL kernel though, they may just tell me to go away. Yet my bug remains about 
> the EEEPC module on the stock x86_64 kernels. *sigh*
>

It is a long shot, but is there anything interesting in the differences 
between the packages you've listed?

Perhaps a bug fix in wireless-tools-29-8.1 or a patch to ath9k in 
kernel-3.8.2-206 may be the key here....

Pat


-- 
Pat Riehecky

Scientific Linux developer
http://www.scientificlinux.org/