* Re: ath9k: freeze when putting interface up
@ 2010-09-09 2:50 Nick Nobody
0 siblings, 0 replies; 6+ messages in thread
From: Nick Nobody @ 2010-09-09 2:50 UTC (permalink / raw)
To: linux-wireless
I'm experiencing the exact same thing (with the same hardware). I'm
using 2.6.35.4 with compat-wireless-2010-08-21.
Running Bjørnar Hansen's test, my system will freeze around 20. Using
the version of ath9k that comes with 2.6.35.4 is impossible because the
system would freeze on the first "ifconfig wlan0 up". My wireless
connection is also a lot less stable compared to how it used to be with
a 2.6.32 kernel on Fedora 12 (I'm using Arch now).
I'll try to help in whatever way I can, just let me know what you need.
nick
^ permalink raw reply [flat|nested] 6+ messages in thread
* ath9k: freeze when putting interface up
@ 2010-08-22 15:57 Bjørnar Hansen
2010-08-23 23:19 ` Luis R. Rodriguez
0 siblings, 1 reply; 6+ messages in thread
From: Bjørnar Hansen @ 2010-08-22 15:57 UTC (permalink / raw)
To: linux-wireless
Good morning
With kernel 2..6.35.2 my computer locks up when doing
# ifconfig wlan0 up
I have now installed compat-wireless (2010-08-20), and no longer have
this problem.
I use the ath9k driver.
As this is a pretty serious problem (machine freezes completely),
would it be possible to pull some patches from compat-wireless into
the next point release of 2.6.35?
-Bjørnar Hansen
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath9k: freeze when putting interface up
2010-08-22 15:57 Bjørnar Hansen
@ 2010-08-23 23:19 ` Luis R. Rodriguez
2010-08-24 19:45 ` Bjørnar Hansen
0 siblings, 1 reply; 6+ messages in thread
From: Luis R. Rodriguez @ 2010-08-23 23:19 UTC (permalink / raw)
To: Bjørnar Hansen
Cc: linux-wireless, Senthil Balasubramanian, Satagopan Kanthadai
On Sun, Aug 22, 2010 at 8:57 AM, Bjørnar Hansen <tilbjornar@gmail.com> wrote:
> Good morning
>
> With kernel 2..6.35.2 my computer locks up when doing
> # ifconfig wlan0 up
What chipset do you have? You can find this from dmesg after loading ath9k.
> I have now installed compat-wireless (2010-08-20), and no longer have
> this problem.
> I use the ath9k driver.
>
> As this is a pretty serious problem (machine freezes completely),
> would it be possible to pull some patches from compat-wireless into
> the next point release of 2.6.35?
Absolutely, if we can determine what happened. First we need to reproduce.
Luis
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath9k: freeze when putting interface up
2010-08-23 23:19 ` Luis R. Rodriguez
@ 2010-08-24 19:45 ` Bjørnar Hansen
2010-09-05 19:49 ` Bjørnar Hansen
0 siblings, 1 reply; 6+ messages in thread
From: Bjørnar Hansen @ 2010-08-24 19:45 UTC (permalink / raw)
To: Luis R. Rodriguez
Cc: linux-wireless, Senthil Balasubramanian, Satagopan Kanthadai,
Mohammed Shafi
Hi
> What chipset do you have? You can find this from dmesg after loading ath9k.
>
The chipset is AR9285 Rev: 2.
I recompiled my kernel with atheros debugging support. Here is the
output from after bringing up wlan0:
Aug 24 21:13:16 localhost kernel: [ 323.948242] ath: Starting driver
with initial channel: 2412 MHz
Aug 24 21:13:16 localhost kernel: [ 323.949260] ath: FULL-SLEEP -> AWAKE
Aug 24 21:13:16 localhost kernel: [ 323.955212] ath: PDADC (0, 0):
a280 00000000
Aug 24 21:13:16 localhost kernel: [ 323.955216] ath: PDADC: Chain 0 |
PDADC 0 Value 0 | PDADC 1 Value 0 | PDADC 2 Value 0 |
PDADC 3 Value 0 |
Aug 24 21:13:16 localhost kernel: [ 323.955223] ath: PDADC (0, 0):
a284 02000000
Aug 24 21:13:16 localhost kernel: [ 323.955227] ath: PDADC: Chain 0 |
PDADC 4 Value 0 | PDADC 5 Value 0 | PDADC 6 Value 0 |
PDADC 7 Value 2 |
Aug 24 21:13:16 localhost kernel: [ 323.955234] ath: PDADC (0, 0):
a288 0a080604
Aug 24 21:13:16 localhost kernel: [ 323.955237] ath: PDADC: Chain 0 |
PDADC 8 Value 4 | PDADC 9 Value 6 | PDADC 10 Value 8 |
PDADC 11 Value 10 |
Aug 24 21:13:16 localhost kernel: [ 323.955244] ath: PDADC (0, 0):
a28c 12100e0c
Aug 24 21:13:16 localhost kernel: [ 323.955247] ath: PDADC: Chain 0 |
PDADC 12 Value 12 | PDADC 13 Value 14 | PDADC 14 Value 16 |
PDADC 15 Value 18 |
Aug 24 21:13:16 localhost kernel: [ 323.955254] ath: PDADC (0, 0):
a290 1a181614
Aug 24 21:13:16 localhost kernel: [ 323.955257] ath: PDADC: Chain 0 |
PDAAug 24 21:18:29 localhost kernel: [ 0.000000] Initializing
cgroup subsys cpuset
As you see, logging was interrupted in the middle of a line.
Sometimes I can bring the interface up and down multiple times before freezing.
-Bjørnar
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: ath9k: freeze when putting interface up
2010-08-24 19:45 ` Bjørnar Hansen
@ 2010-09-05 19:49 ` Bjørnar Hansen
2010-09-09 5:07 ` Luis R. Rodriguez
0 siblings, 1 reply; 6+ messages in thread
From: Bjørnar Hansen @ 2010-09-05 19:49 UTC (permalink / raw)
To: linux-wireless, ath9k-devel-request
Cc: Luis R. Rodriguez, Senthil Balasubramanian, Satagopan Kanthadai,
Mohammed Shafi, Vivek Natarajan
Hi again,
I managed to use git bisect to pinpoint the exact commit that causes
my laptop to freeze:
53bc7aa08b48e5cd745f986731cc7dc24eef2a9f is the first bad commit
commit 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f
Author: Vivek Natarajan <vnatarajan@atheros.com>
Date: Mon Apr 5 14:48:04 2010 +0530
ath9k: Add support for newer AR9285 chipsets.
This patch adds support for a modified newer version of AR9285
chipsets.
Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
I'm CC'ing this to Vivek also.
The chipset is reported as AR9285 rev 01. by lspci (I previously
stated it was rev 2, this is wrong).
While bisecting I found a reliable way to reproduce the freeze. I
devised a script to continuously bring the interface up and down:
COUNTER=1
while(true); do
sudo ifconfig wlan0 up &&
sudo ifconfig wlan0 down &&
echo $COUNTER &&
let COUNTER=COUNTER+1
done
On stable kernels I let it run to around 150. On unstable kernels it
reached at most 8.
-Bjørnar
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: ath9k: freeze when putting interface up
2010-09-05 19:49 ` Bjørnar Hansen
@ 2010-09-09 5:07 ` Luis R. Rodriguez
0 siblings, 0 replies; 6+ messages in thread
From: Luis R. Rodriguez @ 2010-09-09 5:07 UTC (permalink / raw)
To: Bjørnar Hansen, Nick Nobody, Vivek Natarajan,
Senthil Balasubramanian, Satagopan Kanthadai
Cc: linux-wireless, ath9k-devel-request, Mohammed Shafi,
Vivek Natarajan
On Sun, Sep 5, 2010 at 12:49 PM, Bjørnar Hansen <tilbjornar@gmail.com> wrote:
> Hi again,
>
> I managed to use git bisect to pinpoint the exact commit that causes
> my laptop to freeze:
>
> 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f is the first bad commit
> commit 53bc7aa08b48e5cd745f986731cc7dc24eef2a9f
> Author: Vivek Natarajan <vnatarajan@atheros.com>
> Date: Mon Apr 5 14:48:04 2010 +0530
>
> ath9k: Add support for newer AR9285 chipsets.
>
> This patch adds support for a modified newer version of AR9285
> chipsets.
>
> Signed-off-by: Vivek Natarajan <vnatarajan@atheros.com>
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
>
> I'm CC'ing this to Vivek also.
> The chipset is reported as AR9285 rev 01. by lspci (I previously
> stated it was rev 2, this is wrong).
>
> While bisecting I found a reliable way to reproduce the freeze. I
> devised a script to continuously bring the interface up and down:
>
> COUNTER=1
> while(true); do
> sudo ifconfig wlan0 up &&
> sudo ifconfig wlan0 down &&
> echo $COUNTER &&
> let COUNTER=COUNTER+1
> done
>
> On stable kernels I let it run to around 150. On unstable kernels it
> reached at most 8.
Some attention to this would be appreciated.
Luis
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-09-09 5:07 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-09-09 2:50 ath9k: freeze when putting interface up Nick Nobody
-- strict thread matches above, loose matches on Subject: below --
2010-08-22 15:57 Bjørnar Hansen
2010-08-23 23:19 ` Luis R. Rodriguez
2010-08-24 19:45 ` Bjørnar Hansen
2010-09-05 19:49 ` Bjørnar Hansen
2010-09-09 5:07 ` Luis R. Rodriguez
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox