[ath9k-devel] D-Link DWA-547, connection periodicly losts

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Alexander Petukhov]

Hello,

first of all - many thanks to you guys for developing this driver!
i'm owning D-Link DWA-547 card (Atheros Communications Inc. AR5416 802.11abgn Wireless PCI Adapter (rev 01)), and i'm on Debian Lenny\Sid.
My current kernel is 2.6.27 released not long ago, and i have one problem - connection periodicly losts, i.e. i can't even ping router i'm associated with. After some time (5-40 seconds) all becomes fine again. This happents one time for an hour or so on. Interface is not down when this problem occures, gnome applet shows it is up and have a normal(~90%) signal strength. Now i'm using wpa on router and wpasupplicant package on debian box(without any network-managers), but this still happents even without any encryption used.
Would be glad to help in testing.
-- 
Best regards,
Alexander Petukhov <al_petukhov@mail.ru>

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Luis R. Rodriguez]

On Sat, Oct 11, 2008 at 6:46 AM, Alexander Petukhov <al_petukhov@mail.ru> wrote:
> Hello,
>
> first of all - many thanks to you guys for developing this driver!
> i'm owning D-Link DWA-547 card (Atheros Communications Inc. AR5416 802.11abgn Wireless PCI Adapter (rev 01)), and i'm on Debian Lenny\Sid.
> My current kernel is 2.6.27 released not long ago, and i have one problem - connection periodicly losts, i.e. i can't even ping router i'm associated with. After some time (5-40 seconds) all becomes fine again. This happents one time for an hour or so on. Interface is not down when this problem occures, gnome applet shows it is up and have a normal(~90%) signal strength. Now i'm using wpa on router and wpasupplicant package on debian box(without any network-managers), but this still happents even without any encryption used.
> Would be glad to help in testing.

Can you do this:

sudo dmesg -c > /dev/null

Then connect to the AP, every now and then do this:

sudo dmesg -c | tee log

Keep doing this routinely, it'll keep overwriting the data from the
kernel ring buffer to the log but you will also be able to see it on
the screen. Once you see the strange disconnect issue appear please
play more careful attention to what comes up and send us the log. To
be safe you can just use 'tee -a' to append to the log all the
information.

Anyway please send us the log.

  Luis

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Alexander Petukhov]

Sad to say, there is nofing at all in log when this disconnect happents

and this is what i get from wlan0 interface (192.168.0.195 - wlan0, 192.168.0.1 - router)

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Luis R. Rodriguez]

2008/10/14 Alexander Petukhov <al_petukhov@mail.ru>:
> Sad to say, there is nofing at all in log when this disconnect happents
>
> and this is what i get from wlan0 interface (192.168.0.195 - wlan0, 192.168.0.1 - router)
>
> PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
> From 192.168.0.195 icmp_seq=1 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=3 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=4 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=5 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=7 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=8 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=9 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=10 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=11 Destination Host Unreachable
> From 192.168.0.195 icmp_seq=12 Destination Host Unreachable
>
> how can i else monitor the problem?

Are you using Network Manager? If so can you try disabling it? Please see:

http://wireless.kernel.org/en/users/Reporting_bugs

  Luis

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Alexander Petukhov]

Hello, Luis

I'm not using any network managers, last time i posted, i used wpa_supplicant but now i disabled it. My /etc/network/interfaces now looks like:

allow-hotplug wlan0
iface wlan0 inet dhcp
wireless-essid pit

, so i'm not using network managers, wpa_supplicant or even WEP encryption. The situation is as i wroted before:
periodically i have no ping to AP, while connection is up and association with AP is not lost, and nothing is printed by dmesg when this ocuures.
And unlike when wpa daemon was up i sometimes (but not very often) got lost association to AP

only two times i got something in dmesg output:

1.
[22977.920168] ath_tx_prepare: TX queue: 1 is full, depth: 492
[22977.925928] ath_tx_prepare: TX queue: 1 is full, depth: 492
[22977.931446] ath_tx_prepare: TX queue: 1 is full, depth: 492
[22977.932505] ath_tx_prepare: TX queue: 1 is full, depth: 492
[22977.933269] ath_tx_prepare: TX queue: 1 is full, depth: 492

repeated about hundreed times

this happened when the connection was up, but there was no ping to AP.

2. 
[10008.119819] wlan0: authenticate with AP 00:21:91:09:f9:3b
[10008.121648] wlan0: authenticated
[10008.121704] wlan0: associate with AP 00:21:91:09:f9:3b
[10008.125051] wlan0: RX AssocResp from 00:21:91:09:f9:3b (capab=0x421 status=0 aid=1)
[10008.125104] wlan0: associated
[10008.125316] wlan0 (WE) : Wireless Event too big (320)
[11931.384680] NET: Registered protocol family 4
[12906.074958] imwheel[5650]: segfault at 4 ip b7e770a2 sp bf988c50 error 4 in libX11.so.6.2.0[b7e4c000+eb000]
[20964.195016] wlan0: No ProbeResp from current AP 00:21:91:09:f9:3b - assume out of range

this happents when association to AP was lost. It seems to me it happened after i gave big load to network - p2p client + internet radio


On Tue, 14 Oct 2008 17:14:17 -0700
"Luis R. Rodriguez" <mcgrof@gmail.com> wrote:

> 2008/10/14 Alexander Petukhov <al_petukhov@mail.ru>:
> > Sad to say, there is nofing at all in log when this disconnect happents
> >
> > and this is what i get from wlan0 interface (192.168.0.195 - wlan0, 192.168.0.1 - router)
> >
> > PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
> > From 192.168.0.195 icmp_seq=1 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=3 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=4 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=5 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=7 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=8 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=9 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=10 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=11 Destination Host Unreachable
> > From 192.168.0.195 icmp_seq=12 Destination Host Unreachable
> >
> > how can i else monitor the problem?
> 
> Are you using Network Manager? If so can you try disabling it? Please see:
> 
> http://wireless.kernel.org/en/users/Reporting_bugs
> 
>   Luis
> 


-- 
Best regards,
Alexander Petukhov <al_petukhov@mail.ru>

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Luis R. Rodriguez]

On Wed, Oct 22, 2008 at 01:02:26PM -0700, Alexander Petukhov wrote:
> [22977.920168] ath_tx_prepare: TX queue: 1 is full, depth: 492

You can ignore this.

> [20964.195016] wlan0: No ProbeResp from current AP 00:21:91:09:f9:3b - assume out of range
> 
> this happents when association to AP was lost. It seems to me it happened after i gave big load to network - p2p client + internet radio

This is the real issue, we are looking into it.

  Luis

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[alan at georgiabrands.com]

I am seeing exactly the same problem on an Acer Aspire One with an AR5418.
No networkmanager, no wep, as vanilla as possible.
I am using the latest wireless-testing.
The problem occurs immediately when starting a large transfer but will  
occasionally happen with little traffic.
My logs almost exactly the same.


Quoting Alexander Petukhov <al_petukhov@mail.ru>:

> Hello, Luis
>
> I'm not using any network managers, last time i posted, i used   
> wpa_supplicant but now i disabled it. My /etc/network/interfaces now  
>  looks like:
>
> allow-hotplug wlan0
> iface wlan0 inet dhcp
> wireless-essid pit
>
> , so i'm not using network managers, wpa_supplicant or even WEP   
> encryption. The situation is as i wroted before:
> periodically i have no ping to AP, while connection is up and   
> association with AP is not lost, and nothing is printed by dmesg   
> when this ocuures.
> And unlike when wpa daemon was up i sometimes (but not very often)   
> got lost association to AP
>
> only two times i got something in dmesg output:
>
> 1.
> [22977.920168] ath_tx_prepare: TX queue: 1 is full, depth: 492
> [22977.925928] ath_tx_prepare: TX queue: 1 is full, depth: 492
> [22977.931446] ath_tx_prepare: TX queue: 1 is full, depth: 492
> [22977.932505] ath_tx_prepare: TX queue: 1 is full, depth: 492
> [22977.933269] ath_tx_prepare: TX queue: 1 is full, depth: 492
>
> repeated about hundreed times
>
> this happened when the connection was up, but there was no ping to AP.
>
> 2.
> [10008.119819] wlan0: authenticate with AP 00:21:91:09:f9:3b
> [10008.121648] wlan0: authenticated
> [10008.121704] wlan0: associate with AP 00:21:91:09:f9:3b
> [10008.125051] wlan0: RX AssocResp from 00:21:91:09:f9:3b   
> (capab=0x421 status=0 aid=1)
> [10008.125104] wlan0: associated
> [10008.125316] wlan0 (WE) : Wireless Event too big (320)
> [11931.384680] NET: Registered protocol family 4
> [12906.074958] imwheel[5650]: segfault at 4 ip b7e770a2 sp bf988c50   
> error 4 in libX11.so.6.2.0[b7e4c000+eb000]
> [20964.195016] wlan0: No ProbeResp from current AP 00:21:91:09:f9:3b  
>  - assume out of range
>
> this happents when association to AP was lost. It seems to me it   
> happened after i gave big load to network - p2p client + internet   
> radio
>
>
> On Tue, 14 Oct 2008 17:14:17 -0700
> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>
>> 2008/10/14 Alexander Petukhov <al_petukhov@mail.ru>:
>> > Sad to say, there is nofing at all in log when this disconnect happents
>> >
>> > and this is what i get from wlan0 interface (192.168.0.195 -   
>> wlan0, 192.168.0.1 - router)
>> >
>> > PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
>> > From 192.168.0.195 icmp_seq=1 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=3 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=4 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=5 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=7 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=8 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=9 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=10 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=11 Destination Host Unreachable
>> > From 192.168.0.195 icmp_seq=12 Destination Host Unreachable
>> >
>> > how can i else monitor the problem?
>>
>> Are you using Network Manager? If so can you try disabling it? Please see:
>>
>> http://wireless.kernel.org/en/users/Reporting_bugs
>>
>>   Luis
>>
>
>
> --
> Best regards,
> Alexander Petukhov <al_petukhov@mail.ru>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Alexander Petukhov]

hmm.. have found a bug with similar simptoms - http://bugzilla.kernel.org/show_bug.cgi?id=11570
but it is fixed and patch is already applied in 2.6.27 release as i see, but i have this bug on 2.6.27. Do i have to reopen it?   

[ath9k-devel] D-Link DWA-547, connection periodicly losts

[Luis R. Rodriguez]

On Mon, Oct 13, 2008 at 12:49 PM, Alexander Petukhov
<al_petukhov@mail.ru> wrote:
> hmm.. have found a bug with similar simptoms - http://bugzilla.kernel.org/show_bug.cgi?id=11570
> but it is fixed and patch is already applied in 2.6.27 release as i see, but i have this bug on 2.6.27. Do i have to reopen it?

Perhaps you can elaborate a little more. Also please be sure to check

http://wireless.kernel.org/en/users/Reporting_bugs

  Luis

Re: [ath9k-devel] D-Link DWA-547, connection periodicly losts

[Luis R. Rodriguez]

On Mon, Oct 13, 2008 at 12:49 PM, Alexander Petukhov
<al_petukhov@mail.ru> wrote:
> hmm.. have found a bug with similar simptoms - http://bugzilla.kernel.org/show_bug.cgi?id=11570
> but it is fixed and patch is already applied in 2.6.27 release as i see, but i have this bug on 2.6.27. Do i have to reopen it?

Perhaps you can elaborate a little more. Also please be sure to check

http://wireless.kernel.org/en/users/Reporting_bugs

  Luis