* [ath9k-devel] AR5008 hanging computer
@ 2010-02-12 15:25 James Grossmann
2010-02-12 22:53 ` Pavel Roskin
0 siblings, 1 reply; 26+ messages in thread
From: James Grossmann @ 2010-02-12 15:25 UTC (permalink / raw)
To: ath9k-devel
I have a linksys wpc100, which contains the ar5008 chipset. After a
little while of use, It hangs the computer so that almost nothing
responds. I have found that if I hold the power button down until
just before it would force a poweroff, I can usually get it to
respond. I have it installed in a thinkpad x24 (pentium III, so
there's no multi-core/processor), and using ndiswrapper when I'm not
trying to overcome this problem. I have also had the same problem
when I had it installed in a t23, a very similar pentium III laptop.
I am running kubuntu 9.10 with the backports modules installed, I know
they aren't the newest, but I've tried the
I have followed the instructions to debug the problem, but I could use
some more specific ideas of what to debug, because with all debug
options on, over a couple of days, I produced a 1.2 gb debug file. In
perusing the file, I found a few anomalies that were obvious to the
casual observer...me, but which may or may not tell us anything, I
will post them below. I also note that there seems to be a lot of
authenticating/deauthenticating going on, although that could have
been from the ndiswrapper driver.
Thanks,
James
Feb 8 13:00:04 Pneuma kernel: [ 5223.147647] ath9k: new IMR 0x918414b4
Feb 8 13:00:04 Pneuma kernel: [ 5223.147659] ath9k: enable IER
Feb 8 13:00:04 Pneuma kernel: [ 5223.147670] ath9k: AR_IMR 0x918414b4 IER 0x1
Feb 8 13:00:04 Pneuma kernel: [ 5223.178949] ath9k: 0xf4041071 => 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.178958] ath9k: disable IER
Feb 8 13:00:04 Pneuma kernel: [ 5223.178971] ath9k: new IMR 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.179004] ath9k: 0x0 => 0xf4041071
Feb 8 13:00:04 Pneuma kernel: [ 5223.179013] ath9k: new IMR 0x918414b4
Feb 8 13:00:04 Pneuma kernel: [ 5223.179026] ath9k: enable IER
Feb 8 13:00:04 Pneuma kernel: [ 5223.179037] ath9k: AR_IMR 0x918414b4 IER 0x1
Feb 8 13:00:04 Pneuma kernel: [ 5223.188141] ath9k: Set channel: 2412 MHz
Feb 8 13:00:04 Pneuma kernel: [ 5223.188152] ath9k: tx chmask: 5, rx chmask: 5
Feb 8 13:00:04 Pneuma kernel: [ 5223.188161] ath9k: 0xf4041071 => 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.188169] ath9k: disable IER
Feb 8 13:00:04 Pneuma kernel: [ 5223.188181] ath9k: new IMR 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.188270] ath9k: Disable MIB counters
Feb 8 13:00:04 Pneuma kernel: [ 5223.188294] ath9k: (2462 MHz) ->
(2412 MHz), chanwidth: 0
Feb 8 13:00:04 Pneuma kernel: [ 5223.188308] ath9k: NF calibrated
[ctl] [chain 0] is -88
Feb 8 13:00:04 Pneuma kernel: [ 5223.188319] ath9k: NF calibrated
[ctl] [chain 1] is -89
Feb 8 13:00:04 Pneuma kernel: [ 5223.188329] ath9k: NF calibrated
[ctl] [chain 2] is 0
Feb 8 13:00:04 Pneuma kernel: [ 5223.188339] ath9k: NF calibrated
[ext] [chain 0] is 0
Feb 8 13:00:04 Pneuma kernel: [ 5223.188348] ath9k: NF calibrated
[ext] [chain 1] is 0
Feb 8 13:00:04 Pneuma kernel: [ 5223.188358] ath9k: NF calibrated
[ext] [chain 2] is 0
Feb 8 13:00:04 Pneuma kernel: [ 5223.190818] ath9k: PDADC (0, 0):
a280 06060505
Feb 8 13:00:04 Pneuma kernel: [ 5223.190829] ath9k: PDADC: Chain 0 |
PDADC 0 Value 5 | PDADC 1 Value 5 | PDADC 2 Value 6 |
PDADC 3 Value 6 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.190845] ath9k: PDADC (0, 0):
a284 09080807
Feb 8 13:00:04 Pneuma kernel: [ 5223.190854] ath9k: PDADC: Chain 0 |
PDADC 4 Value 7 | PDADC 5 Value 8 | PDADC 6 Value 8 |
PDADC 7 Value 9 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.190869] ath9k: PDADC (0, 0):
a288 0d0c0b0a
Feb 8 13:00:04 Pneuma kernel: [ 5223.190878] ath9k: PDADC: Chain 0 |
PDADC 8 Value 10 | PDADC 9 Value 11 | PDADC 10 Value 12 |
PDADC 11 Value 13 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.190893] ath9k: PDADC (0, 0):
a28c 1311100e
Feb 8 13:00:04 Pneuma kernel: [ 5223.190902] ath9k: PDADC: Chain 0 |
PDADC 12 Value 14 | PDADC 13 Value 16 | PDADC 14 Value 17 |
PDADC 15 Value 19 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.190918] ath9k: PDADC (0, 0):
a290 1b181614
Feb 8 13:00:04 Pneuma kernel: [ 5223.190927] ath9k: PDADC: Chain 0 |
PDADC 16 Value 20 | PDADC 17 Value 22 | PDADC 18 Value 24 |
PDADC 19 Value 27 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.190942] ath9k: PDADC (0, 0):
a294 2522201d
Feb 8 13:00:04 Pneuma kernel: [ 5223.190951] ath9k: PDADC: Chain 0 |
PDADC 20 Value 29 | PDADC 21 Value 32 | PDADC 22 Value 34 |
PDADC 23 Value 37 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.190966] ath9k: PDADC (0, 0):
a298 09082b28
Feb 8 13:00:04 Pneuma kernel: [ 5223.190975] ath9k: PDADC: Chain 0 |
PDADC 24 Value 40 | PDADC 25 Value 43 | PDADC 26 Value 8 |
PDADC 27 Value 9 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.190990] ath9k: PDADC (0, 0):
a29c 0d0c0b0a
Feb 8 13:00:04 Pneuma kernel: [ 5223.190999] ath9k: PDADC: Chain 0 |
PDADC 28 Value 10 | PDADC 29 Value 11 | PDADC 30 Value 12 |
PDADC 31 Value 13 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191014] ath9k: PDADC (0, 0):
a2a0 12100f0e
Feb 8 13:00:04 Pneuma kernel: [ 5223.191023] ath9k: PDADC: Chain 0 |
PDADC 32 Value 14 | PDADC 33 Value 15 | PDADC 34 Value 16 |
PDADC 35 Value 18 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191039] ath9k: PDADC (0, 0):
a2a4 19171514
Feb 8 13:00:04 Pneuma kernel: [ 5223.191048] ath9k: PDADC: Chain 0 |
PDADC 36 Value 20 | PDADC 37 Value 21 | PDADC 38 Value 23 |
PDADC 39 Value 25 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191063] ath9k: PDADC (0, 0):
a2a8 211f1d1b
Feb 8 13:00:04 Pneuma kernel: [ 5223.191072] ath9k: PDADC: Chain 0 |
PDADC 40 Value 27 | PDADC 41 Value 29 | PDADC 42 Value 31 |
PDADC 43 Value 33 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191087] ath9k: PDADC (0, 0):
a2ac 2e2a2724
Feb 8 13:00:04 Pneuma kernel: [ 5223.191096] ath9k: PDADC: Chain 0 |
PDADC 44 Value 36 | PDADC 45 Value 39 | PDADC 46 Value 42 |
PDADC 47 Value 46 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191111] ath9k: PDADC (0, 0):
a2b0 3a373431
Feb 8 13:00:04 Pneuma kernel: [ 5223.191120] ath9k: PDADC: Chain 0 |
PDADC 48 Value 49 | PDADC 49 Value 52 | PDADC 50 Value 55 |
PDADC 51 Value 58 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191135] ath9k: PDADC (0, 0):
a2b4 4643403d
Feb 8 13:00:04 Pneuma kernel: [ 5223.191144] ath9k: PDADC: Chain 0 |
PDADC 52 Value 61 | PDADC 53 Value 64 | PDADC 54 Value 67 |
PDADC 55 Value 70 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191159] ath9k: PDADC (0, 0):
a2b8 4c4c4c49
Feb 8 13:00:04 Pneuma kernel: [ 5223.191169] ath9k: PDADC: Chain 0 |
PDADC 56 Value 73 | PDADC 57 Value 76 | PDADC 58 Value 76 |
PDADC 59 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191184] ath9k: PDADC (0, 0):
a2bc 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191193] ath9k: PDADC: Chain 0 |
PDADC 60 Value 76 | PDADC 61 Value 76 | PDADC 62 Value 76 |
PDADC 63 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191208] ath9k: PDADC (0, 0):
a2c0 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191217] ath9k: PDADC: Chain 0 |
PDADC 64 Value 76 | PDADC 65 Value 76 | PDADC 66 Value 76 |
PDADC 67 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191232] ath9k: PDADC (0, 0):
a2c4 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191241] ath9k: PDADC: Chain 0 |
PDADC 68 Value 76 | PDADC 69 Value 76 | PDADC 70 Value 76 |
PDADC 71 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191256] ath9k: PDADC (0, 0):
a2c8 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191265] ath9k: PDADC: Chain 0 |
PDADC 72 Value 76 | PDADC 73 Value 76 | PDADC 74 Value 76 |
PDADC 75 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191280] ath9k: PDADC (0, 0):
a2cc 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191289] ath9k: PDADC: Chain 0 |
PDADC 76 Value 76 | PDADC 77 Value 76 | PDADC 78 Value 76 |
PDADC 79 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191304] ath9k: PDADC (0, 0):
a2d0 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191314] ath9k: PDADC: Chain 0 |
PDADC 80 Value 76 | PDADC 81 Value 76 | PDADC 82 Value 76 |
PDADC 83 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191329] ath9k: PDADC (0, 0):
a2d4 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191338] ath9k: PDADC: Chain 0 |
PDADC 84 Value 76 | PDADC 85 Value 76 | PDADC 86 Value 76 |
PDADC 87 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191353] ath9k: PDADC (0, 0):
a2d8 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191362] ath9k: PDADC: Chain 0 |
PDADC 88 Value 76 | PDADC 89 Value 76 | PDADC 90 Value 76 |
PDADC 91 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191377] ath9k: PDADC (0, 0):
a2dc 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191386] ath9k: PDADC: Chain 0 |
PDADC 92 Value 76 | PDADC 93 Value 76 | PDADC 94 Value 76 |
PDADC 95 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191401] ath9k: PDADC (0, 0):
a2e0 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191410] ath9k: PDADC: Chain 0 |
PDADC 96 Value 76 | PDADC 97 Value 76 | PDADC 98 Value 76 |
PDADC 99 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191425] ath9k: PDADC (0, 0):
a2e4 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191434] ath9k: PDADC: Chain 0 |
PDADC 100 Value 76 | PDADC 101 Value 76 | PDADC 102 Value 76 |
PDADC 103 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191450] ath9k: PDADC (0, 0):
a2e8 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191459] ath9k: PDADC: Chain 0 |
PDADC 104 Value 76 | PDADC 105 Value 76 | PDADC 106 Value 76 |
PDADC 107 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191474] ath9k: PDADC (0, 0):
a2ec 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191484] ath9k: PDADC: Chain 0 |
PDADC 108 Value 76 | PDADC 109 Value 76 | PDADC 110 Value 76 |
PDADC 111 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191499] ath9k: PDADC (0, 0):
a2f0 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191508] ath9k: PDADC: Chain 0 |
PDADC 112 Value 76 | PDADC 113 Value 76 | PDADC 114 Value 76 |
PDADC 115 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191523] ath9k: PDADC (0, 0):
a2f4 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191532] ath9k: PDADC: Chain 0 |
PDADC 116 Value 76 | PDADC 117 Value 76 | PDADC 118 Value 76 |
PDADC 119 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191548] ath9k: PDADC (0, 0):
a2f8 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191557] ath9k: PDADC: Chain 0 |
PDADC 120 Value 76 | PDADC 121 Value 76 | PDADC 122 Value 76 |
PDADC 123 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191572] ath9k: PDADC (0, 0):
a2fc 4c4c4c4c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191581] ath9k: PDADC: Chain 0 |
PDADC 124 Value 76 | PDADC 125 Value 76 | PDADC 126 Value 76 |
PDADC 127 Value 76 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191606] ath9k: PDADC (2,1000):
b280 0b0a0909
Feb 8 13:00:04 Pneuma kernel: [ 5223.191616] ath9k: PDADC: Chain 2 |
PDADC 0 Value 9 | PDADC 1 Value 9 | PDADC 2 Value 10 |
PDADC 3 Value 11 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191631] ath9k: PDADC (2,1000):
b284 100e0d0c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191640] ath9k: PDADC: Chain 2 |
PDADC 4 Value 12 | PDADC 5 Value 13 | PDADC 6 Value 14 |
PDADC 7 Value 16 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191656] ath9k: PDADC (2,1000):
b288 17151312
Feb 8 13:00:04 Pneuma kernel: [ 5223.191665] ath9k: PDADC: Chain 2 |
PDADC 8 Value 18 | PDADC 9 Value 19 | PDADC 10 Value 21 |
PDADC 11 Value 23 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191680] ath9k: PDADC (2,1000):
b28c 211f1c19
Feb 8 13:00:04 Pneuma kernel: [ 5223.191689] ath9k: PDADC: Chain 2 |
PDADC 12 Value 25 | PDADC 13 Value 28 | PDADC 14 Value 31 |
PDADC 15 Value 33 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191705] ath9k: PDADC (2,1000):
b290 2d2a2724
Feb 8 13:00:04 Pneuma kernel: [ 5223.191714] ath9k: PDADC: Chain 2 |
PDADC 16 Value 36 | PDADC 17 Value 39 | PDADC 18 Value 42 |
PDADC 19 Value 45 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191729] ath9k: PDADC (2,1000):
b294 3b373431
Feb 8 13:00:04 Pneuma kernel: [ 5223.191738] ath9k: PDADC: Chain 2 |
PDADC 20 Value 49 | PDADC 21 Value 52 | PDADC 22 Value 55 |
PDADC 23 Value 59 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191753] ath9k: PDADC (2,1000):
b298 0f0e433f
Feb 8 13:00:04 Pneuma kernel: [ 5223.191763] ath9k: PDADC: Chain 2 |
PDADC 24 Value 63 | PDADC 25 Value 67 | PDADC 26 Value 14 |
PDADC 27 Value 15 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191778] ath9k: PDADC (2,1000):
b29c 15141210
Feb 8 13:00:04 Pneuma kernel: [ 5223.191787] ath9k: PDADC: Chain 2 |
PDADC 28 Value 16 | PDADC 29 Value 18 | PDADC 30 Value 20 |
PDADC 31 Value 21 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191802] ath9k: PDADC (2,1000):
b2a0 1d1b1917
Feb 8 13:00:04 Pneuma kernel: [ 5223.191811] ath9k: PDADC: Chain 2 |
PDADC 32 Value 23 | PDADC 33 Value 25 | PDADC 34 Value 27 |
PDADC 35 Value 29 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191826] ath9k: PDADC (2,1000):
b2a4 2623211f
Feb 8 13:00:04 Pneuma kernel: [ 5223.191835] ath9k: PDADC: Chain 2 |
PDADC 36 Value 31 | PDADC 37 Value 33 | PDADC 38 Value 35 |
PDADC 39 Value 38 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191851] ath9k: PDADC (2,1000):
b2a8 322f2c29
Feb 8 13:00:04 Pneuma kernel: [ 5223.191860] ath9k: PDADC: Chain 2 |
PDADC 40 Value 41 | PDADC 41 Value 44 | PDADC 42 Value 47 |
PDADC 43 Value 50 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191875] ath9k: PDADC (2,1000):
b2ac 413d3935
Feb 8 13:00:04 Pneuma kernel: [ 5223.191884] ath9k: PDADC: Chain 2 |
PDADC 44 Value 53 | PDADC 45 Value 57 | PDADC 46 Value 61 |
PDADC 47 Value 65 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191899] ath9k: PDADC (2,1000):
b2b0 534e4a46
Feb 8 13:00:04 Pneuma kernel: [ 5223.191908] ath9k: PDADC: Chain 2 |
PDADC 48 Value 70 | PDADC 49 Value 74 | PDADC 50 Value 78 |
PDADC 51 Value 83 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191924] ath9k: PDADC (2,1000):
b2b4 67625d58
Feb 8 13:00:04 Pneuma kernel: [ 5223.191933] ath9k: PDADC: Chain 2 |
PDADC 52 Value 88 | PDADC 53 Value 93 | PDADC 54 Value 98 |
PDADC 55 Value 103 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191948] ath9k: PDADC (2,1000):
b2b8 7171716c
Feb 8 13:00:04 Pneuma kernel: [ 5223.191957] ath9k: PDADC: Chain 2 |
PDADC 56 Value 108 | PDADC 57 Value 113 | PDADC 58 Value 113 |
PDADC 59 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191972] ath9k: PDADC (2,1000):
b2bc 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.191982] ath9k: PDADC: Chain 2 |
PDADC 60 Value 113 | PDADC 61 Value 113 | PDADC 62 Value 113 |
PDADC 63 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.191997] ath9k: PDADC (2,1000):
b2c0 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192037] ath9k: PDADC: Chain 2 |
PDADC 64 Value 113 | PDADC 65 Value 113 | PDADC 66 Value 113 |
PDADC 67 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192053] ath9k: PDADC (2,1000):
b2c4 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192063] ath9k: PDADC: Chain 2 |
PDADC 68 Value 113 | PDADC 69 Value 113 | PDADC 70 Value 113 |
PDADC 71 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192078] ath9k: PDADC (2,1000):
b2c8 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192087] ath9k: PDADC: Chain 2 |
PDADC 72 Value 113 | PDADC 73 Value 113 | PDADC 74 Value 113 |
PDADC 75 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192102] ath9k: PDADC (2,1000):
b2cc 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192112] ath9k: PDADC: Chain 2 |
PDADC 76 Value 113 | PDADC 77 Value 113 | PDADC 78 Value 113 |
PDADC 79 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192127] ath9k: PDADC (2,1000):
b2d0 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192136] ath9k: PDADC: Chain 2 |
PDADC 80 Value 113 | PDADC 81 Value 113 | PDADC 82 Value 113 |
PDADC 83 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192151] ath9k: PDADC (2,1000):
b2d4 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192160] ath9k: PDADC: Chain 2 |
PDADC 84 Value 113 | PDADC 85 Value 113 | PDADC 86 Value 113 |
PDADC 87 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192176] ath9k: PDADC (2,1000):
b2d8 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192185] ath9k: PDADC: Chain 2 |
PDADC 88 Value 113 | PDADC 89 Value 113 | PDADC 90 Value 113 |
PDADC 91 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192200] ath9k: PDADC (2,1000):
b2dc 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192209] ath9k: PDADC: Chain 2 |
PDADC 92 Value 113 | PDADC 93 Value 113 | PDADC 94 Value 113 |
PDADC 95 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192225] ath9k: PDADC (2,1000):
b2e0 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192234] ath9k: PDADC: Chain 2 |
PDADC 96 Value 113 | PDADC 97 Value 113 | PDADC 98 Value 113 |
PDADC 99 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192249] ath9k: PDADC (2,1000):
b2e4 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192258] ath9k: PDADC: Chain 2 |
PDADC 100 Value 113 | PDADC 101 Value 113 | PDADC 102 Value 113 |
PDADC 103 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192274] ath9k: PDADC (2,1000):
b2e8 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192283] ath9k: PDADC: Chain 2 |
PDADC 104 Value 113 | PDADC 105 Value 113 | PDADC 106 Value 113 |
PDADC 107 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192298] ath9k: PDADC (2,1000):
b2ec 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192307] ath9k: PDADC: Chain 2 |
PDADC 108 Value 113 | PDADC 109 Value 113 | PDADC 110 Value 113 |
PDADC 111 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192323] ath9k: PDADC (2,1000):
b2f0 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192332] ath9k: PDADC: Chain 2 |
PDADC 112 Value 113 | PDADC 113 Value 113 | PDADC 114 Value 113 |
PDADC 115 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192347] ath9k: PDADC (2,1000):
b2f4 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192356] ath9k: PDADC: Chain 2 |
PDADC 116 Value 113 | PDADC 117 Value 113 | PDADC 118 Value 113 |
PDADC 119 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192371] ath9k: PDADC (2,1000):
b2f8 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192381] ath9k: PDADC: Chain 2 |
PDADC 120 Value 113 | PDADC 121 Value 113 | PDADC 122 Value 113 |
PDADC 123 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192396] ath9k: PDADC (2,1000):
b2fc 71717171
Feb 8 13:00:04 Pneuma kernel: [ 5223.192405] ath9k: PDADC: Chain 2 |
PDADC 124 Value 113 | PDADC 125 Value 113 | PDADC 126 Value 113 |
PDADC 127 Value 113 |
Feb 8 13:00:04 Pneuma kernel: [ 5223.192475] ath9k: Getting spur idx
0 is2Ghz. 1 val 8000
Feb 8 13:00:04 Pneuma kernel: [ 5223.192546] ath9k: Reset TX queue: 0
Feb 8 13:00:04 Pneuma kernel: [ 5223.192556] ath9k: tx ok 0x0 err 0x0
desc 0x10f eol 0x10f urn 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.192569] ath9k: Reset TX queue: 1
Feb 8 13:00:04 Pneuma kernel: [ 5223.192577] ath9k: tx ok 0x0 err 0x0
desc 0x10f eol 0x10f urn 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.192590] ath9k: Reset TX queue: 2
Feb 8 13:00:04 Pneuma kernel: [ 5223.192597] ath9k: tx ok 0x0 err 0x0
desc 0x10f eol 0x10f urn 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.192610] ath9k: Reset TX queue: 3
Feb 8 13:00:04 Pneuma kernel: [ 5223.192618] ath9k: tx ok 0x0 err 0x0
desc 0x10f eol 0x10f urn 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.192631] ath9k: Reset TXQ,
inactive queue: 4
Feb 8 13:00:04 Pneuma kernel: [ 5223.192638] ath9k: Reset TXQ,
inactive queue: 5
Feb 8 13:00:04 Pneuma kernel: [ 5223.192646] ath9k: Reset TXQ,
inactive queue: 6
Feb 8 13:00:04 Pneuma kernel: [ 5223.192653] ath9k: Reset TXQ,
inactive queue: 7
Feb 8 13:00:04 Pneuma kernel: [ 5223.192660] ath9k: Reset TX queue: 8
Feb 8 13:00:04 Pneuma kernel: [ 5223.192677] ath9k: tx ok 0x0 err 0x0
desc 0x10f eol 0x10f urn 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.192690] ath9k: Reset TX queue: 9
Feb 8 13:00:04 Pneuma kernel: [ 5223.192706] ath9k: tx ok 0x0 err 0x0
desc 0x10f eol 0x10f urn 0x0
Feb 8 13:00:04 Pneuma kernel: [ 5223.192723] ath9k: ah->misc_mode 0x4
Feb 8 13:00:04 Pneuma kernel: [ 5223.194004] ath9k: Enable MIB counters
Feb 8 13:00:04 Pneuma kernel: [ 5223.194052] ath9k: ANI parameters:
Feb 8 13:00:04 Pneuma kernel: [ 5223.194059] ath9k:
noiseImmunityLevel=0, spurImmunityLevel=0, ofdmWeakSigDetectOff=0
Feb 8 13:00:04 Pneuma kernel: [ 5223.194069] ath9k:
cckWeakSigThreshold=0, firstepLevel=0, listenTime=0
Feb 8 13:00:04 Pneuma kernel: [ 5223.194078] ath9k: cycleCount=0,
ofdmPhyErrCount=0, cckPhyErrCount=0
Feb 8 13:00:04 Pneuma kernel: [ 5223.194097] ath9k: Writing
ofdmbase=12582412 cckbase=12582712
Feb 8 13:00:04 Pneuma kernel: [ 5223.194120] ath9k: 0x81800964 => 0xf4041071
Feb 8 13:00:04 Pneuma kernel: [ 5223.194128] ath9k: disable IER
Feb 8 13:00:04 Pneuma kernel: [ 5223.194140] ath9k: new IMR 0x918414b4
Feb 8 13:00:04 Pneuma kernel: [ 5223.194152] ath9k: enable IER
It did this similar thing a couple of times around one of those hangs.
the Authenticating/deauthenticating looks like this, I removed the
module with the debugging enabled here, and immediately upon using the
card again later, I start getting the authenticating/deauthenticating
notes.
Feb 8 17:20:40 Pneuma kernel: [20858.910276] ath9k: Driver halt
Feb 8 17:20:40 Pneuma kernel: [20859.197114] ath9k: Release TX queue: 0
Feb 8 17:20:40 Pneuma kernel: [20859.197126] ath9k: tx ok 0x0 err 0x0
desc 0x10e eol 0x10e urn 0x0
Feb 8 17:20:40 Pneuma kernel: [20859.197140] ath9k: Release TX queue: 1
Feb 8 17:20:40 Pneuma kernel: [20859.197147] ath9k: tx ok 0x0 err 0x0
desc 0x10c eol 0x10c urn 0x0
Feb 8 17:20:40 Pneuma kernel: [20859.197159] ath9k: Release TX queue: 2
Feb 8 17:20:40 Pneuma kernel: [20859.197166] ath9k: tx ok 0x0 err 0x0
desc 0x108 eol 0x108 urn 0x0
Feb 8 17:20:40 Pneuma kernel: [20859.197178] ath9k: Release TX queue: 3
Feb 8 17:20:40 Pneuma kernel: [20859.197185] ath9k: tx ok 0x0 err 0x0
desc 0x100 eol 0x100 urn 0x0
Feb 8 17:20:40 Pneuma kernel: [20859.197197] ath9k: Release TX queue: 8
Feb 8 17:20:40 Pneuma kernel: [20859.197204] ath9k: tx ok 0x0 err 0x0
desc 0x0 eol 0x0 urn 0x0
Feb 8 17:20:40 Pneuma kernel: [20859.197216] ath9k: Disabling ANI
Feb 8 17:20:40 Pneuma kernel: [20859.197223] ath9k: Disable MIB counters
Feb 8 20:38:48 Pneuma kernel: [32747.472276] pci 0000:03:00.0: reg 10
32bit mmio: [0x000000-0x00ffff]
Feb 8 20:38:50 Pneuma kernel: [32748.814288] ath: EEPROM regdomain: 0x10
Feb 8 20:38:50 Pneuma kernel: [32748.814299] ath: EEPROM indicates we
should expect a direct regpair map
Feb 8 20:38:50 Pneuma kernel: [32748.814310] ath: Country alpha2 being used: CO
Feb 8 20:38:50 Pneuma kernel: [32748.814316] ath: Regpair used: 0x10
Feb 8 20:38:50 Pneuma kernel: [32748.995091] phy0: Selected rate
control algorithm 'ath9k_rate_control'
Feb 8 20:38:57 Pneuma kernel: [32756.582010] wlan1: deauthenticating
from 00:12:34:56:78:9a by local choice (reason=3)
Feb 8 20:38:57 Pneuma kernel: [32756.585645] wlan1: direct probe to
AP 00:12:34:56:78:9a (try 1)
Feb 8 20:38:57 Pneuma kernel: [32756.589501] wlan1: direct probe responded
Feb 8 20:38:57 Pneuma kernel: [32756.589517] wlan1: authenticate with
AP 00:12:34:56:78:9a (try 1)
Feb 8 20:38:57 Pneuma kernel: [32756.593125] wlan1: authenticated
Feb 8 20:38:57 Pneuma kernel: [32756.593191] wlan1: associate with AP
00:12:34:56:78:9a (try 1)
Feb 8 20:38:57 Pneuma kernel: [32756.597471] wlan1: RX AssocResp from
00:12:34:56:78:9a (capab=0x401 status=0 aid=2)
Feb 8 20:38:57 Pneuma kernel: [32756.597485] wlan1: associated
Feb 8 20:39:08 Pneuma kernel: [32767.340184] wlan1: no IPv6 routers present
Feb 8 20:40:39 Pneuma kernel: [32858.110237] wlan1: deauthenticated
from 00:12:34:56:78:9a (Reason: 7)
Feb 8 20:40:40 Pneuma kernel: [32858.965288] wlan1: direct probe to
AP 00:12:34:56:78:9a (try 1)
Feb 8 20:40:40 Pneuma kernel: [32858.972432] wlan1: direct probe responded
Feb 8 20:40:40 Pneuma kernel: [32858.972449] wlan1: authenticate with
AP 00:12:34:56:78:9a (try 1)
Feb 8 20:40:40 Pneuma kernel: [32858.976763] wlan1: authenticated
Feb 8 20:40:40 Pneuma kernel: [32858.976836] wlan1: associate with AP
00:12:34:56:78:9a (try 1)
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-12 15:25 [ath9k-devel] AR5008 hanging computer James Grossmann
@ 2010-02-12 22:53 ` Pavel Roskin
2010-02-12 23:35 ` James Grossmann
2010-02-12 23:42 ` hong zhang
0 siblings, 2 replies; 26+ messages in thread
From: Pavel Roskin @ 2010-02-12 22:53 UTC (permalink / raw)
To: ath9k-devel
On Fri, 2010-02-12 at 09:25 -0600, James Grossmann wrote:
> I have a linksys wpc100, which contains the ar5008 chipset. After a
> little while of use, It hangs the computer so that almost nothing
> responds. I have found that if I hold the power button down until
> just before it would force a poweroff, I can usually get it to
> respond. I have it installed in a thinkpad x24 (pentium III, so
> there's no multi-core/processor), and using ndiswrapper when I'm not
> trying to overcome this problem. I have also had the same problem
> when I had it installed in a t23, a very similar pentium III laptop.
> I am running kubuntu 9.10 with the backports modules installed, I know
> they aren't the newest, but I've tried the
> I have followed the instructions to debug the problem, but I could use
> some more specific ideas of what to debug, because with all debug
> options on, over a couple of days, I produced a 1.2 gb debug file.
I suggest that you give the exact kernel version, as a courtesy to those
not running kubuntu 9.10.
> In
> perusing the file, I found a few anomalies that were obvious to the
> casual observer...me, but which may or may not tell us anything, I
> will post them below. I also note that there seems to be a lot of
> authenticating/deauthenticating going on, although that could have
> been from the ndiswrapper driver.
You can use "dmesg -c" to erase the kernel log.
> Feb 8 13:00:04 Pneuma kernel: [ 5223.147647] ath9k: new IMR 0x918414b4
Getting kernel log from /var/log is not a good idea. Please use the
dmesg command.
You can use less debug options to get something of manageable size. You
can use sed to remove the timestamps (I don't think they are very useful
for this particular problem) and use lzma to compress the log:
dmesg | sed 's/^[^]]*] //' | lzma >kernel.log.lzma
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-12 22:53 ` Pavel Roskin
@ 2010-02-12 23:35 ` James Grossmann
2010-02-12 23:42 ` hong zhang
1 sibling, 0 replies; 26+ messages in thread
From: James Grossmann @ 2010-02-12 23:35 UTC (permalink / raw)
To: ath9k-devel
I was hoping you could provide possible debug options I could look at,
with all the debug options on, I was filling dmesg's buffer in less
than 1 sec, not enough time to catch it when it stopped and I had to
intervene. Kubuntu 9.10 is using the ubuntu 2.6.31-19-generic and the
2.6.31-20-generic kernels.
Thanks!
James
On Fri, Feb 12, 2010 at 4:53 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Fri, 2010-02-12 at 09:25 -0600, James Grossmann wrote:
>> I have a linksys wpc100, which contains the ar5008 chipset. ?After a
>> little while of use, It hangs the computer so that almost nothing
>> responds. ?I have found that if I hold the power button down until
>> just before it would force a poweroff, I can usually get it to
>> respond. ?I have it installed in a thinkpad x24 (pentium III, so
>> there's no multi-core/processor), and using ndiswrapper when I'm not
>> trying to overcome this problem. ?I have also had the same problem
>> when I had it installed in a t23, a very similar pentium III laptop.
>> I am running kubuntu 9.10 with the backports modules installed, I know
>> they aren't the newest, but I've tried the
>> I have followed the instructions to debug the problem, but I could use
>> some more specific ideas of what to debug, because with all debug
>> options on, over a couple of days, I produced a 1.2 gb debug file.
>
> I suggest that you give the exact kernel version, as a courtesy to those
> not running kubuntu 9.10.
>
>> ? In
>> perusing the file, I found a few anomalies that were obvious to the
>> casual observer...me, but which may or may not tell us anything, I
>> will post them below. ?I also note that there seems to be a lot of
>> authenticating/deauthenticating going on, although that could have
>> been from the ndiswrapper driver.
>
> You can use "dmesg -c" to erase the kernel log.
>
>> Feb ?8 13:00:04 Pneuma kernel: [ 5223.147647] ath9k: new IMR 0x918414b4
>
> Getting kernel log from /var/log is not a good idea. ?Please use the
> dmesg command.
>
> You can use less debug options to get something of manageable size. ?You
> can use sed to remove the timestamps (I don't think they are very useful
> for this particular problem) and use lzma to compress the log:
>
> dmesg | sed 's/^[^]]*] //' | lzma >kernel.log.lzma
>
> --
> Regards,
> Pavel Roskin
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-12 22:53 ` Pavel Roskin
2010-02-12 23:35 ` James Grossmann
@ 2010-02-12 23:42 ` hong zhang
2010-02-15 7:03 ` Pavel Roskin
1 sibling, 1 reply; 26+ messages in thread
From: hong zhang @ 2010-02-12 23:42 UTC (permalink / raw)
To: ath9k-devel
> Getting kernel log from /var/log is not a good idea.?
I know /var/log/syslog can hold more kernel message than dmesg. Any other disadvantage?
> Please use the
> dmesg command.
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-12 23:42 ` hong zhang
@ 2010-02-15 7:03 ` Pavel Roskin
[not found] ` <167ae39b1002152030s170128a0j362e7e9c61a4af42@mail.gmail.com>
0 siblings, 1 reply; 26+ messages in thread
From: Pavel Roskin @ 2010-02-15 7:03 UTC (permalink / raw)
To: ath9k-devel
On Fri, 2010-02-12 at 15:42 -0800, hong zhang wrote:
> > Getting kernel log from /var/log is not a good idea.
>
> I know /var/log/syslog can hold more kernel message than dmesg. Any other disadvantage?
That's true. But syslogd can omit low-priority messages from the
kernel. Irrelevant logs from other software can be present. The
timestamps are rarely needed and take extra space. They also don't
compress well. The is no convenient alternative to "dmesg -c" to clear
the log and start over. I would not recommend clearing the system log
like that, as it can contain important information from the userspace,
such as break-in attempts etc.
If the log buffer overflows, perhaps it's a good idea to disable
irrelevant debug options or to stop debug output as soon as the error
condition occurs. If case of hangs, serial console could help.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
[not found] ` <1266296860.17808.2.camel@mj>
@ 2010-02-16 23:54 ` James Grossmann
2010-02-17 17:47 ` Pavel Roskin
2010-02-17 17:56 ` hong zhang
0 siblings, 2 replies; 26+ messages in thread
From: James Grossmann @ 2010-02-16 23:54 UTC (permalink / raw)
To: ath9k-devel
On Mon, Feb 15, 2010 at 11:07 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Mon, 2010-02-15 at 22:30 -0600, James Grossmann wrote:
>> I'd love to disable irrelevant logs, however, nobody has told me what
>> would be relivant and what wouldn't--with all logging on, it was
>> hogging 30% of the cpu just to log the messages. ?Any help would be
>> appreciated. ?the system is hanging, and the only thing that seems to
>> get it out (and sometimes, even that doesn't work) is to hold down the
>> power button until just before the computer just turns off.
>
> Please don't take the discussion private.
Sorry about that, gmail does that automatically.
>
>> > If the log buffer overflows, perhaps it's a good idea to disable
>> > irrelevant debug options or to stop debug output as soon as the error
>> > condition occurs. ?If case of hangs, serial console could help.
>
> Please write under the quoted text, or I get the impression that you
> didn't read it.
>
> --
> Regards,
> Pavel Roskin
>
I'm also sorry about that, on the other hand, there are many schools
of thought on answering posts, but I don't want this to be a
discussion of that.
I would just like to get some ideas of what I can debug to get some
answers. Out of curiosity, is there a way to do a continuous
recording of dmesg to a serial console? These hangs occur regularly,
but very unpredictably and at fairly long intervals.
Thanks,
James
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-16 23:54 ` James Grossmann
@ 2010-02-17 17:47 ` Pavel Roskin
2010-02-17 17:56 ` hong zhang
1 sibling, 0 replies; 26+ messages in thread
From: Pavel Roskin @ 2010-02-17 17:47 UTC (permalink / raw)
To: ath9k-devel
On Tue, 2010-02-16 at 17:54 -0600, James Grossmann wrote:
> I would just like to get some ideas of what I can debug to get some
> answers. Out of curiosity, is there a way to do a continuous
> recording of dmesg to a serial console? These hangs occur regularly,
> but very unpredictably and at fairly long intervals.
What's really needed is what happens immediately before the hang, so the
history is not really interesting.
I would try to enable more debugging options in the kernel. It could
help detect the problem earlier if it's a software problem, such as
memory corruption.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-16 23:54 ` James Grossmann
2010-02-17 17:47 ` Pavel Roskin
@ 2010-02-17 17:56 ` hong zhang
2010-02-17 18:15 ` Pavel Roskin
1 sibling, 1 reply; 26+ messages in thread
From: hong zhang @ 2010-02-17 17:56 UTC (permalink / raw)
To: ath9k-devel
> >
> I'm also sorry about that, on the other hand, there are
> many schools
> of thought on answering posts, but I don't want this to be
> a
> discussion of that.
> I would just like to get some ideas of what I can debug to
> get some
> answers.? Out of curiosity, is there a way to do a
> continuous
> recording of dmesg to a serial console?? These hangs
> occur regularly,
Use netconsole but you need two machines.
> but very unpredictably and at fairly long intervals.
> Thanks,
> James
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-17 17:56 ` hong zhang
@ 2010-02-17 18:15 ` Pavel Roskin
2010-02-18 12:58 ` [ath9k-devel] 802.11n in Ad-hoc mode Jónatan Muñoz
2010-02-23 6:45 ` [ath9k-devel] AR5008 hanging computer James Grossmann
0 siblings, 2 replies; 26+ messages in thread
From: Pavel Roskin @ 2010-02-17 18:15 UTC (permalink / raw)
To: ath9k-devel
On Wed, 2010-02-17 at 09:56 -0800, hong zhang wrote:
> > >
> > I'm also sorry about that, on the other hand, there are
> > many schools
> > of thought on answering posts, but I don't want this to be
> > a
> > discussion of that.
> > I would just like to get some ideas of what I can debug to
> > get some
> > answers. Out of curiosity, is there a way to do a
> > continuous
> > recording of dmesg to a serial console? These hangs
> > occur regularly,
>
> Use netconsole but you need two machines.
I would never recommend using netconsole to debug a hang in a network
driver. Chances are too high that the hang will block the network stack
and prevent the most interesting data from leaving the system.
Besides, it's one thing to debug something that is easy to reproduce and
that is known to show up on the netconsole. It's another thing to debug
something that may not appear on any console after hours of waiting.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] 802.11n in Ad-hoc mode
2010-02-17 18:15 ` Pavel Roskin
@ 2010-02-18 12:58 ` Jónatan Muñoz
2010-02-24 7:02 ` Zhang Yanfei-B21500
2010-02-23 6:45 ` [ath9k-devel] AR5008 hanging computer James Grossmann
1 sibling, 1 reply; 26+ messages in thread
From: Jónatan Muñoz @ 2010-02-18 12:58 UTC (permalink / raw)
To: ath9k-devel
Hi all,
I am interested in the current status of 802.11n support under ad-hoc mode.
Do you know anything?
Are there some deadlines or plans implementing ad-hoc mode in 802.11n?
I have AR928x Atheros chipset.
Thanks,
John
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
@ 2010-02-18 20:31 Mark Sutton
2010-02-18 21:58 ` Mark Sutton
0 siblings, 1 reply; 26+ messages in thread
From: Mark Sutton @ 2010-02-18 20:31 UTC (permalink / raw)
To: ath9k-devel
Hi,
I have this problem as well.
Hardware is:
Atheros Communications Inc. AR5008
Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686 GNU/Linux
driver is supplied with kernel.
I used to think it had to do with returning from suspend to ram.
Because on return it will never initiate a scan for new AP's.
But it hung the other day wen the machine was left running and moved
to a new location, scan worked like it should when the lease expired
and froze the machine.
The panic can be caused by starting wpa_gui and requesting a scan.
Sometimes it works, some it crashes the machine. I'll see if I can
find a backtrace, or make one.
Thanks, mark
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-18 20:31 Mark Sutton
@ 2010-02-18 21:58 ` Mark Sutton
2010-02-19 1:36 ` Pavel Roskin
2010-02-21 8:31 ` Tomi Orava
0 siblings, 2 replies; 26+ messages in thread
From: Mark Sutton @ 2010-02-18 21:58 UTC (permalink / raw)
To: ath9k-devel
On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote:
> Hi,
> I have this problem as well.
> Hardware is:
>
> Atheros Communications Inc. AR5008
> Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
>
> Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686 GNU/Linux
>
Here is a call trace from last night when it hung during reboot.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
intel8x0_measure_ac97_clock: measured 55061 usecs (2653 samples)
intel8x0: clocking to 48000
Registered led device: ath9k-phy0::radio
Registered led device: ath9k-phy0::assoc
Registered led device: ath9k-phy0::tx
Registered led device: ath9k-phy0::rx
phy0: Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf0ce0000, irq=11
Adding 1044216k swap on /dev/hda2. Priority:-1 extents:1 across:1044216k
EXT4-fs (hda4): mounted filesystem with ordered data mode
Modules linked in: acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 ath9k snd_ac97_codec ac97_bus mac80211 snd_pcm snd_seq pcmcia snd_timer snd_seq_device ath fan thermal video uhci_hcd cfg80211 processor snd ehci_hcd yenta_socket thermal_sys soundcore toshiba_acpi rsrc_nonstatic rtc_cmos usbcore intel_agp pcmcia_core e100 psmouse agpgart rtc_core snd_page_alloc rfkill output rtc_lib mii led_class hwmon evdev ac battery button
Pid: 621, comm: phy0 Not tainted (2.6.32.7 #2) Portable PC
EIP: 0060:[<f087fa1f>] EFLAGS: 00000292 CPU: 0
EIP is at yenta_interrupt+0x1f/0xf0 [yenta_socket]
EAX: 00000000 EBX: eeb45440 ECX: 00020102 EDX: 00000000
ESI: c1394010 EDI: ee954400 EBP: 00000000 ESP: ed9c1cec
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b6b4b3b0 CR3: 22832000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<c1060bae>] ? handle_IRQ_event+0x6e/0x180
[<c102cd45>] ? irq_exit+0x35/0x80
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c90000>] ? ath9k_hw_AR9287_check_eeprom+0x1c0/0x250 [ath9k]
[<c1060b56>] ? handle_IRQ_event+0x16/0x180
[<c10064b2>] ? mask_and_ack_8259A+0x62/0x110
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<c102c9fd>] ? __do_softirq+0x3d/0x1c0
[<c1060bae>] ? handle_IRQ_event+0x6e/0x180
[<c102cbad>] ? do_softirq+0x2d/0x40
[<c102cd75>] ? irq_exit+0x65/0x80
[<c10049f3>] ? do_IRQ+0x43/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c9007b>] ? ath9k_hw_AR9287_check_eeprom+0x23b/0x250 [ath9k]
[<c119a972>] ? ioread32+0x32/0x40
[<f0c82180>] ? ath9k_hw_set_interrupts+0x230/0x2b0 [ath9k]
[<f0c98b76>] ? ath_set_channel+0x106/0x110 [ath9k]
[<f0c9a90d>] ? ath9k_config+0x29d/0x310 [ath9k]
[<f0bba062>] ? ieee80211_hw_config+0x62/0xb0 [mac80211]
[<f0bbdf7a>] ? ieee80211_scan_work+0x35a/0x5b0 [mac80211]
[<c103c9aa>] ? worker_thread+0x16a/0x270
[<c101e29b>] ? pick_next_task_fair+0x6b/0xb0
[<f0bbdc20>] ? ieee80211_scan_work+0x0/0x5b0 [mac80211]
[<c1040300>] ? autoremove_wake_function+0x0/0x50
[<c103c840>] ? worker_thread+0x0/0x270
[<c1040004>] ? kthread+0x74/0x80
[<c103ff90>] ? kthread+0x0/0x80
[<c1003653>] ? kernel_thread_helper+0x7/0x14
Modules linked in: acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 ath9k snd_ac97_codec ac97_bus mac80211 snd_pcm snd_seq pcmcia snd_timer snd_seq_device ath fan thermal video uhci_hcd cfg80211 processor snd ehci_hcd yenta_socket thermal_sys soundcore toshiba_acpi rsrc_nonstatic rtc_cmos usbcore intel_agp pcmcia_core e100 psmouse agpgart rtc_core snd_page_alloc rfkill output rtc_lib mii led_class hwmon evdev ac battery button
Pid: 621, comm: phy0 Not tainted (2.6.32.7 #2) Portable PC
EIP: 0060:[<c1060b56>] EFLAGS: 00000246 CPU: 0
EIP is at handle_IRQ_event+0x16/0x180
EAX: 00000000 EBX: eeb45440 ECX: 00020102 EDX: eeb45440
ESI: c1394010 EDI: eeb45440 EBP: ed9c1e10 ESP: ed9c1cfc
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b6b4b3b0 CR3: 22832000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<c102cd45>] ? irq_exit+0x35/0x80
[<c10064b2>] ? mask_and_ack_8259A+0x62/0x110
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c90000>] ? ath9k_hw_AR9287_check_eeprom+0x1c0/0x250 [ath9k]
[<c1060b56>] ? handle_IRQ_event+0x16/0x180
[<c10064b2>] ? mask_and_ack_8259A+0x62/0x110
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<c102c9fd>] ? __do_softirq+0x3d/0x1c0
[<c1060bae>] ? handle_IRQ_event+0x6e/0x180
[<c102cbad>] ? do_softirq+0x2d/0x40
[<c102cd75>] ? irq_exit+0x65/0x80
[<c10049f3>] ? do_IRQ+0x43/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c9007b>] ? ath9k_hw_AR9287_check_eeprom+0x23b/0x250 [ath9k]
[<c119a972>] ? ioread32+0x32/0x40
[<f0c82180>] ? ath9k_hw_set_interrupts+0x230/0x2b0 [ath9k]
[<f0c98b76>] ? ath_set_channel+0x106/0x110 [ath9k]
[<f0c9a90d>] ? ath9k_config+0x29d/0x310 [ath9k]
[<f0bba062>] ? ieee80211_hw_config+0x62/0xb0 [mac80211]
[<f0bbdf7a>] ? ieee80211_scan_work+0x35a/0x5b0 [mac80211]
[<c103c9aa>] ? worker_thread+0x16a/0x270
[<c101e29b>] ? pick_next_task_fair+0x6b/0xb0
[<f0bbdc20>] ? ieee80211_scan_work+0x0/0x5b0 [mac80211]
[<c1040300>] ? autoremove_wake_function+0x0/0x50
[<c103c840>] ? worker_thread+0x0/0x270
[<c1040004>] ? kthread+0x74/0x80
[<c103ff90>] ? kthread+0x0/0x80
[<c1003653>] ? kernel_thread_helper+0x7/0x14
Modules linked in: acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 ath9k snd_ac97_codec ac97_bus mac80211 snd_pcm snd_seq pcmcia snd_timer snd_seq_device ath fan thermal video uhci_hcd cfg80211 processor snd ehci_hcd yenta_socket thermal_sys soundcore toshiba_acpi rsrc_nonstatic rtc_cmos usbcore intel_agp pcmcia_core e100 psmouse agpgart rtc_core snd_page_alloc rfkill output rtc_lib mii led_class hwmon evdev ac battery button
Pid: 621, comm: phy0 Not tainted (2.6.32.7 #2) Portable PC
EIP: 0060:[<f09754ad>] EFLAGS: 00000246 CPU: 0
EIP is at usb_hcd_irq+0x2d/0x60 [usbcore]
EAX: 00000000 EBX: eea13400 ECX: 00001442 EDX: 00000000
ESI: 00000246 EDI: ee85d3c0 EBP: 00000000 ESP: ed9c1cf0
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b6b4b3b0 CR3: 22832000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<c1060bae>] ? handle_IRQ_event+0x6e/0x180
[<c102cd45>] ? irq_exit+0x35/0x80
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c90000>] ? ath9k_hw_AR9287_check_eeprom+0x1c0/0x250 [ath9k]
[<c1060b56>] ? handle_IRQ_event+0x16/0x180
[<c10064b2>] ? mask_and_ack_8259A+0x62/0x110
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<c102c9fd>] ? __do_softirq+0x3d/0x1c0
[<c1060bae>] ? handle_IRQ_event+0x6e/0x180
[<c102cbad>] ? do_softirq+0x2d/0x40
[<c102cd75>] ? irq_exit+0x65/0x80
[<c10049f3>] ? do_IRQ+0x43/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c9007b>] ? ath9k_hw_AR9287_check_eeprom+0x23b/0x250 [ath9k]
[<c119a972>] ? ioread32+0x32/0x40
[<f0c82180>] ? ath9k_hw_set_interrupts+0x230/0x2b0 [ath9k]
[<f0c98b76>] ? ath_set_channel+0x106/0x110 [ath9k]
[<f0c9a90d>] ? ath9k_config+0x29d/0x310 [ath9k]
[<f0bba062>] ? ieee80211_hw_config+0x62/0xb0 [mac80211]
[<f0bbdf7a>] ? ieee80211_scan_work+0x35a/0x5b0 [mac80211]
[<c103c9aa>] ? worker_thread+0x16a/0x270
[<c101e29b>] ? pick_next_task_fair+0x6b/0xb0
[<f0bbdc20>] ? ieee80211_scan_work+0x0/0x5b0 [mac80211]
[<c1040300>] ? autoremove_wake_function+0x0/0x50
[<c103c840>] ? worker_thread+0x0/0x270
[<c1040004>] ? kthread+0x74/0x80
[<c103ff90>] ? kthread+0x0/0x80
[<c1003653>] ? kernel_thread_helper+0x7/0x14
Modules linked in: acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 ath9k snd_ac97_codec ac97_bus mac80211 snd_pcm snd_seq pcmcia snd_timer snd_seq_device ath fan thermal video uhci_hcd cfg80211 processor snd ehci_hcd yenta_socket thermal_sys soundcore toshiba_acpi rsrc_nonstatic rtc_cmos usbcore intel_agp pcmcia_core e100 psmouse agpgart rtc_core snd_page_alloc rfkill output rtc_lib mii led_class hwmon evdev ac battery button
Pid: 621, comm: phy0 Not tainted (2.6.32.7 #2) Portable PC
EIP: 0060:[<c119a972>] EFLAGS: 00000292 CPU: 0
EIP is at ioread32+0x32/0x40
EAX: 00700100 EBX: eeb45440 ECX: 00001442 EDX: 00000030
ESI: 00000000 EDI: eea4eec0 EBP: ee94cc00 ESP: ed9c1ccc
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b6b4b3b0 CR3: 22832000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<f0cf3569>] ? snd_intel8x0_interrupt+0x19/0x280 [snd_intel8x0]
[<f08f5739>] ? e100_intr+0x19/0xd0 [e100]
[<c1060bae>] ? handle_IRQ_event+0x6e/0x180
[<c102cd45>] ? irq_exit+0x35/0x80
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c90000>] ? ath9k_hw_AR9287_check_eeprom+0x1c0/0x250 [ath9k]
[<c1060b56>] ? handle_IRQ_event+0x16/0x180
[<c10064b2>] ? mask_and_ack_8259A+0x62/0x110
[<c1062b6d>] ? handle_level_irq+0x7d/0x120
[<c1004e57>] ? handle_irq+0x17/0x20
[<c10049ea>] ? do_IRQ+0x3a/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<c102c9fd>] ? __do_softirq+0x3d/0x1c0
[<c1060bae>] ? handle_IRQ_event+0x6e/0x180
[<c102cbad>] ? do_softirq+0x2d/0x40
[<c102cd75>] ? irq_exit+0x65/0x80
[<c10049f3>] ? do_IRQ+0x43/0xa0
[<c1003569>] ? common_interrupt+0x29/0x30
[<f0c9007b>] ? ath9k_hw_AR9287_check_eeprom+0x23b/0x250 [ath9k]
[<c119a972>] ? ioread32+0x32/0x40
[<f0c82180>] ? ath9k_hw_set_interrupts+0x230/0x2b0 [ath9k]
[<f0c98b76>] ? ath_set_channel+0x106/0x110 [ath9k]
[<f0c9a90d>] ? ath9k_config+0x29d/0x310 [ath9k]
[<f0bba062>] ? ieee80211_hw_config+0x62/0xb0 [mac80211]
[<f0bbdf7a>] ? ieee80211_scan_work+0x35a/0x5b0 [mac80211]
[<c103c9aa>] ? worker_thread+0x16a/0x270
[<c101e29b>] ? pick_next_task_fair+0x6b/0xb0
[<f0bbdc20>] ? ieee80211_scan_work+0x0/0x5b0 [mac80211]
[<c1040300>] ? autoremove_wake_function+0x0/0x50
[<c103c840>] ? worker_thread+0x0/0x270
[<c1040004>] ? kthread+0x74/0x80
[<c103ff90>] ? kthread+0x0/0x80
[<c1003653>] ? kernel_thread_helper+0x7/0x14
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-18 21:58 ` Mark Sutton
@ 2010-02-19 1:36 ` Pavel Roskin
2010-03-05 23:04 ` Mark Sutton
2010-02-21 8:31 ` Tomi Orava
1 sibling, 1 reply; 26+ messages in thread
From: Pavel Roskin @ 2010-02-19 1:36 UTC (permalink / raw)
To: ath9k-devel
On Thu, 2010-02-18 at 13:58 -0800, Mark Sutton wrote:
> On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote:
> > Hi,
> > I have this problem as well.
> > Hardware is:
> >
> > Atheros Communications Inc. AR5008
> > Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
> >
> > Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686 GNU/Linux
> >
> Here is a call trace from last night when it hung during reboot.
>
>
> pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
> pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean.
> pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
> intel8x0_measure_ac97_clock: measured 55061 usecs (2653 samples)
> intel8x0: clocking to 48000
> Registered led device: ath9k-phy0::radio
> Registered led device: ath9k-phy0::assoc
> Registered led device: ath9k-phy0::tx
> Registered led device: ath9k-phy0::rx
> phy0: Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81: mem=0xf0ce0000, irq=11
> Adding 1044216k swap on /dev/hda2. Priority:-1 extents:1 across:1044216k
> EXT4-fs (hda4): mounted filesystem with ordered data mode
...
> Pid: 621, comm: phy0 Not tainted (2.6.32.7 #2) Portable PC
> EIP: 0060:[<f087fa1f>] EFLAGS: 00000292 CPU: 0
> EIP is at yenta_interrupt+0x1f/0xf0 [yenta_socket]
That's the PCMCIA subsystem, not ath9k. We could suspect ath9k to cause
it if it was immediately after ath9k was loaded, but there were other
things going on after the ath9k initialization.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-18 21:58 ` Mark Sutton
2010-02-19 1:36 ` Pavel Roskin
@ 2010-02-21 8:31 ` Tomi Orava
2010-02-22 18:02 ` Luis R. Rodriguez
1 sibling, 1 reply; 26+ messages in thread
From: Tomi Orava @ 2010-02-21 8:31 UTC (permalink / raw)
To: ath9k-devel
On 02/18/2010 11:58 PM, Mark Sutton wrote:
> On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote:
>> Hi,
>> I have this problem as well.
>> Hardware is:
>>
>> Atheros Communications Inc. AR5008
>> Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
>>
>> Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686 GNU/Linux
>>
> Here is a call trace from last night when it hung during reboot.
Hmm, it looks like my problem might be related to yours as well.
My lspci entry is:
03:00.0 Network controller: Atheros Communications Inc. AR5008
Wireless Network Adapter (rev 01)
Subsystem: Device 07d1:3a09
Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
Memory at 4c000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] #80 [0000]
Kernel driver in use: ath9k
Kernel modules: ath9k
and dmesg reports the hardware as:
phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81 mem=0xf8300000, irq=11
My problem is that the laptop will eventually hang sooner or later
to a complete halt if there is some traffic going via the wlan
pcmcia card. The hang can usually be recovered by ejecting the card
from its slot.
One of the logs contains the following information:
(kernel version isUbuntu 2.6.32-12.17-generic)
Feb 14 14:39:52 foobar kernel: [20442.972015] BUG: soft lockup - CPU#0 stuck for 61s! [phy1:2531]
Feb 14 14:39:52 foobar kernel: [20442.972015] Modules linked in: ip6table_filter ip6_tables act_police cls_flow cls_fw cls_u32 sch_htb sch_hfsc sch_ingre
ss sch_sfq xt_time xt_connlimit xt_realm iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REDIRECT ipt_NETMAP ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah
ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_ama
nda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrac
k_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport x
t_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY ipt_LO
G iptable_mangle nfnetlink arc4 ath9k mac80211 ath cfg80211 led_class binfmt_misc rfcomm ppdev sco bnep
Feb 14 14:39:52 foobar kernel: l2cap lirc_mceusb lirc_dev ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_RE
JECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish cast5 des_generic ae
s_i586 aes_generic xcbc rmd160 sha256_generic sha1_generic crypto_null af_key rpcsec_gss_krb5 nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc joydev pc
mcia snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq
snd_timer snd_seq_device snd yenta_socket rsrc_nonstatic pcmcia_core soundcore dell_wmi psmouse serio_raw btusb bluetooth dcdbas snd_page_alloc irda crc_c
citt shpchp lp parport raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor async_memcpy async_tx raid1 raid0 multipath linear dm_raid45 xor usbhi
d ohci1394 fbcon tileblit font bitblit softcursor intel_agp ieee1394 vga16fb vgastate tg3 video output agpg
Feb 14 14:39:52 foobar kernel: art
Feb 14 14:39:52 foobar kernel: [20442.972015]
Feb 14 14:39:52 foobar kernel: [20442.972015] Pid: 2531, comm: phy1 Not tainted (2.6.32-12-generic #17-Ubuntu) Portable PC
Feb 14 14:39:52 foobar kernel: [20442.972015] EIP: 0060:[<c0351b62>] EFLAGS: 00000292 CPU: 0
Feb 14 14:39:52 foobar kernel: [20442.972015] EIP is at ioread32+0x32/0x40
Feb 14 14:39:52 foobar kernel: [20442.972015] EAX: 00000000 EBX: e55c8000 ECX: f86600ac EDX: f86600b8
Feb 14 14:39:52 foobar kernel: [20442.972015] ESI: f4041071 EDI: 40c00000 EBP: e2239c60 ESP: e2239c60
Feb 14 14:39:52 foobar kernel: [20442.972015] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Feb 14 14:39:52 foobar kernel: [20442.972015] CR0: 8005003b CR2: b75a8000 CR3: 369ba000 CR4: 000006d0
Feb 14 14:39:52 foobar kernel: [20442.972015] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Feb 14 14:39:52 foobar kernel: [20442.972015] DR6: ffff0ff0 DR7: 00000400
Feb 14 14:39:52 foobar kernel: [20442.972015] Call Trace:
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88b83ab>] ath9k_ioread32+0x2b/0x80 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88b9ee4>] ath9k_hw_set_interrupts+0x1d4/0x360 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88d2d1d>] ath_isr+0x13d/0x170 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c019e204>] handle_IRQ_event+0x54/0x150
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0106e27>] ? mask_and_ack_8259A+0x57/0xf0
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c01a0734>] handle_level_irq+0x74/0x100
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0105a9d>] handle_irq+0x1d/0x30
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c05a9e4c>] do_IRQ+0x4c/0xc0
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88b83ab>] ? ath9k_ioread32+0x2b/0x80 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0103a90>] common_interrupt+0x30/0x40
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f80700e0>] ? xor_p5_mmx_5+0x20/0x1a0 [xor]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c01517fd>] ? __do_softirq+0x4d/0x1b0
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c012a458>] ? default_spin_lock_flags+0x8/0x10
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c05a598f>] ? _spin_lock_irqsave+0x2f/0x50
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0106d37>] ? enable_8259A_irq+0x47/0x70
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c01a0772>] ? handle_level_irq+0xb2/0x100
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c01519a5>] do_softirq+0x45/0x50
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0151af5>] irq_exit+0x65/0x70
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c05a9e55>] do_IRQ+0x55/0xc0
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0103a90>] common_interrupt+0x30/0x40
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0351b62>] ? ioread32+0x32/0x40
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88b83ab>] ath9k_ioread32+0x2b/0x80 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88b9f7a>] ath9k_hw_set_interrupts+0x26a/0x360 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88d176e>] ath_set_channel+0x17e/0x180 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f88d2b87>] ath9k_config+0x287/0x2e0 [ath9k]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f875bcc2>] ieee80211_hw_config+0x72/0xb0 [mac80211]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f875f635>] ieee80211_scan_work+0x175/0x320 [mac80211]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0161eee>] run_workqueue+0x8e/0x150
Feb 14 14:39:52 foobar kernel: [20442.972015] [<f875f4c0>] ? ieee80211_scan_work+0x0/0x320 [mac80211]
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0162034>] worker_thread+0x84/0xe0
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0165f90>] ? autoremove_wake_function+0x0/0x50
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0161fb0>] ? worker_thread+0x0/0xe0
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0165d04>] kthread+0x74/0x80
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c0165c90>] ? kthread+0x0/0x80
Feb 14 14:39:52 foobar kernel: [20442.972015] [<c01040e7>] kernel_thread_helper+0x7/0x10
Feb 14 14:39:52 foobar kernel: [20446.657338] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0
-- Here the pcmcia wlan card was ejected and the system started responding again.
Feb 14 14:39:52 foobar kernel: [20446.693722] wlan0: deauthenticating from 00:0d:0b:b2:8c:dd by local choice (reason=3)
Feb 14 14:39:52 foobar kernel: [20446.701944] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Feb 14 14:39:52 foobar kernel: [20446.710055] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Feb 14 14:39:52 foobar kernel: [20446.718167] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Feb 14 14:39:52 foobar kernel: [20446.726279] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Feb 14 14:39:52 foobar kernel: [20446.734390] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Feb 14 14:39:52 foobar kernel: [20446.742502] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
Feb 14 14:39:52 foobar kernel: [20446.742506] ath9k: Unable to stop TxDMA. Reset HAL!
Feb 14 14:39:52 foobar kernel: [20446.850877] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
Feb 14 14:39:52 foobar kernel: [20446.850881] ath9k: Chip reset failed
Feb 14 14:39:52 foobar kernel: [20446.850883] ath9k: Unable to reset hardware; reset status -22
Feb 14 14:39:52 foobar kernel: [20446.861656] ath9k: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff
Feb 14 14:39:52 foobar kernel: [20446.969249] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
Feb 14 14:39:52 foobar kernel: [20447.076842] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
Feb 14 14:39:52 foobar kernel: [20447.399108] ath9k 0000:03:00.0: PCI INT A disabled
Feb 14 14:39:54 foobar kernel: [20448.488074] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
Feb 14 14:39:54 foobar kernel: [20448.488156] pci 0000:03:00.0: reg 10 32bit mmio: [0x000000-0x00ffff]
Feb 14 14:39:54 foobar kernel: [20448.488495] ath9k 0000:03:00.0: enabling device (0000 -> 0002)
Feb 14 14:39:54 foobar kernel: [20448.488518] ath9k 0000:03:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
Feb 14 14:39:54 foobar kernel: [20448.939749] ath: EEPROM regdomain: 0x30
Feb 14 14:39:54 foobar kernel: [20448.939754] ath: EEPROM indicates we should expect a direct regpair map
Feb 14 14:39:54 foobar kernel: [20448.939757] ath: Country alpha2 being used: AM
Feb 14 14:39:54 foobar kernel: [20448.939759] ath: Regpair used: 0x30
Feb 14 14:39:54 foobar kernel: [20448.945107] phy2: Selected rate control algorithm 'ath9k_rate_control'
Feb 14 14:39:54 foobar kernel: [20448.946630] cfg80211: Calling CRDA for country: AM
Feb 14 14:39:54 foobar kernel: [20448.947513] Registered led device: ath9k-phy2::radio
Feb 14 14:39:54 foobar kernel: [20448.948455] Registered led device: ath9k-phy2::assoc
Feb 14 14:39:54 foobar kernel: [20448.948959] Registered led device: ath9k-phy2::tx
Feb 14 14:39:54 foobar kernel: [20448.949443] Registered led device: ath9k-phy2::rx
Feb 14 14:39:54 foobar kernel: [20448.949458] phy2: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf8520000, irq=11
Feb 14 14:39:54 foobar kernel: [20449.105089] cfg80211: Current regulatory domain intersected:
Feb 14 14:39:54 foobar kernel: [20449.105100] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Feb 14 14:39:54 foobar kernel: [20449.105110] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Feb 14 14:39:54 foobar kernel: [20449.105119] (5170000 KHz - 5250000 KHz @ 20000 KHz), (N/A, 1800 mBm)
Feb 14 14:39:54 foobar kernel: [20449.105128] (5250000 KHz - 5330000 KHz @ 20000 KHz), (N/A, 1800 mBm)
Feb 14 14:39:54 foobar kernel: [20449.162437] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 14 14:40:01 foobar kernel: [20455.898813] wlan0: deauthenticating from 00:0d:0b:b2:8c:dd by local choice (reason=3)
Feb 14 14:40:01 foobar kernel: [20455.904452] wlan0: direct probe to AP 00:0d:0b:b2:8c:dd (try 1)
Feb 14 14:40:01 foobar kernel: [20455.908238] wlan0: direct probe responded
Feb 14 14:40:01 foobar kernel: [20455.908242] wlan0: authenticate with AP 00:0d:0b:b2:8c:dd (try 1)
Feb 14 14:40:01 foobar kernel: [20455.910440] wlan0: authenticated
I'll have to find out if there really was some original karmic kernels (without the compat-wireless backport updates)
that actually doesn't have this hang problem.
Redards,
Tomi Orava
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-21 8:31 ` Tomi Orava
@ 2010-02-22 18:02 ` Luis R. Rodriguez
2010-02-22 18:24 ` Tomi Orava
0 siblings, 1 reply; 26+ messages in thread
From: Luis R. Rodriguez @ 2010-02-22 18:02 UTC (permalink / raw)
To: ath9k-devel
On Sun, Feb 21, 2010 at 12:31 AM, Tomi Orava
<Tomi.Orava@ncircle.nullnet.fi> wrote:
> On 02/18/2010 11:58 PM, Mark Sutton wrote:
>> On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote:
>>> Hi,
>>> ? ? ?I have this problem as well.
>>> Hardware is:
>>>
>>> Atheros Communications Inc. AR5008
>>> Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
>>>
>>> Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686 GNU/Linux
>>>
>> Here is a call trace from last night when it hung during reboot.
>
> Hmm, it looks like my problem might be related to yours as well.
>
> My lspci entry is:
>
> 03:00.0 Network controller: Atheros Communications Inc. AR5008
> Wireless Network Adapter (rev 01)
> ? ? ? ?Subsystem: Device 07d1:3a09
> ? ? ? ?Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
> ? ? ? ?Memory at 4c000000 (32-bit, non-prefetchable) [size=64K]
> ? ? ? ?Capabilities: [40] #80 [0000]
> ? ? ? ?Kernel driver in use: ath9k
> ? ? ? ?Kernel modules: ath9k
>
> and dmesg reports the hardware as:
>
> phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81 mem=0xf8300000, irq=11
>
> My problem is that the laptop will eventually hang sooner or later
> to a complete halt if there is some traffic going via the wlan
> pcmcia card. The hang can usually be recovered by ejecting the card
> from its slot.
>
> One of the logs contains the following information:
> (kernel version isUbuntu 2.6.32-12.17-generic)
>
> Feb 14 14:39:52 foobar kernel: [20442.972015] BUG: soft lockup - CPU#0 stuck for 61s! [phy1:2531]
> Feb 14 14:39:52 foobar kernel: [20442.972015] Modules linked in: ip6table_filter ip6_tables act_police cls_flow cls_fw cls_u32 sch_htb sch_hfsc sch_ingre
> ss sch_sfq xt_time xt_connlimit xt_realm iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REDIRECT ipt_NETMAP ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah
> ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_ama
> nda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrac
> k_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport x
> t_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY ipt_LO
> G iptable_mangle nfnetlink arc4 ath9k mac80211 ath cfg80211 led_class binfmt_misc rfcomm ppdev sco bnep
> Feb 14 14:39:52 foobar kernel: l2cap lirc_mceusb lirc_dev ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_RE
> JECT xt_tcpudp iptable_filter ip_tables x_tables bridge stp deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish cast5 des_generic ae
> s_i586 aes_generic xcbc rmd160 sha256_generic sha1_generic crypto_null af_key rpcsec_gss_krb5 nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc joydev pc
> mcia snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq
> snd_timer snd_seq_device snd yenta_socket rsrc_nonstatic pcmcia_core soundcore dell_wmi psmouse serio_raw btusb bluetooth dcdbas snd_page_alloc irda crc_c
> citt shpchp lp parport raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor async_memcpy async_tx raid1 raid0 multipath linear dm_raid45 xor usbhi
> d ohci1394 fbcon tileblit font bitblit softcursor intel_agp ieee1394 vga16fb vgastate tg3 video output agpg
> Feb 14 14:39:52 foobar kernel: art
> Feb 14 14:39:52 foobar kernel: [20442.972015]
> Feb 14 14:39:52 foobar kernel: [20442.972015] Pid: 2531, comm: phy1 Not tainted (2.6.32-12-generic #17-Ubuntu) Portable PC
> Feb 14 14:39:52 foobar kernel: [20442.972015] EIP: 0060:[<c0351b62>] EFLAGS: 00000292 CPU: 0
> Feb 14 14:39:52 foobar kernel: [20442.972015] EIP is at ioread32+0x32/0x40
> Feb 14 14:39:52 foobar kernel: [20442.972015] EAX: 00000000 EBX: e55c8000 ECX: f86600ac EDX: f86600b8
> Feb 14 14:39:52 foobar kernel: [20442.972015] ESI: f4041071 EDI: 40c00000 EBP: e2239c60 ESP: e2239c60
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
> Feb 14 14:39:52 foobar kernel: [20442.972015] CR0: 8005003b CR2: b75a8000 CR3: 369ba000 CR4: 000006d0
> Feb 14 14:39:52 foobar kernel: [20442.972015] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> Feb 14 14:39:52 foobar kernel: [20442.972015] DR6: ffff0ff0 DR7: 00000400
> Feb 14 14:39:52 foobar kernel: [20442.972015] Call Trace:
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88b83ab>] ath9k_ioread32+0x2b/0x80 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88b9ee4>] ath9k_hw_set_interrupts+0x1d4/0x360 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88d2d1d>] ath_isr+0x13d/0x170 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c019e204>] handle_IRQ_event+0x54/0x150
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0106e27>] ? mask_and_ack_8259A+0x57/0xf0
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c01a0734>] handle_level_irq+0x74/0x100
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0105a9d>] handle_irq+0x1d/0x30
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c05a9e4c>] do_IRQ+0x4c/0xc0
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88b83ab>] ? ath9k_ioread32+0x2b/0x80 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0103a90>] common_interrupt+0x30/0x40
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f80700e0>] ? xor_p5_mmx_5+0x20/0x1a0 [xor]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c01517fd>] ? __do_softirq+0x4d/0x1b0
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c012a458>] ? default_spin_lock_flags+0x8/0x10
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c05a598f>] ? _spin_lock_irqsave+0x2f/0x50
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0106d37>] ? enable_8259A_irq+0x47/0x70
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c01a0772>] ? handle_level_irq+0xb2/0x100
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c01519a5>] do_softirq+0x45/0x50
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0151af5>] irq_exit+0x65/0x70
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c05a9e55>] do_IRQ+0x55/0xc0
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0103a90>] common_interrupt+0x30/0x40
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0351b62>] ? ioread32+0x32/0x40
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88b83ab>] ath9k_ioread32+0x2b/0x80 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88b9f7a>] ath9k_hw_set_interrupts+0x26a/0x360 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88d176e>] ath_set_channel+0x17e/0x180 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f88d2b87>] ath9k_config+0x287/0x2e0 [ath9k]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f875bcc2>] ieee80211_hw_config+0x72/0xb0 [mac80211]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f875f635>] ieee80211_scan_work+0x175/0x320 [mac80211]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0161eee>] run_workqueue+0x8e/0x150
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<f875f4c0>] ? ieee80211_scan_work+0x0/0x320 [mac80211]
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0162034>] worker_thread+0x84/0xe0
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0165f90>] ? autoremove_wake_function+0x0/0x50
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0161fb0>] ? worker_thread+0x0/0xe0
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0165d04>] kthread+0x74/0x80
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c0165c90>] ? kthread+0x0/0x80
> Feb 14 14:39:52 foobar kernel: [20442.972015] ?[<c01040e7>] kernel_thread_helper+0x7/0x10
> Feb 14 14:39:52 foobar kernel: [20446.657338] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0
>
> -- Here the pcmcia wlan card was ejected and the system started responding again.
>
> Feb 14 14:39:52 foobar kernel: [20446.693722] wlan0: deauthenticating from 00:0d:0b:b2:8c:dd by local choice (reason=3)
> Feb 14 14:39:52 foobar kernel: [20446.701944] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
> Feb 14 14:39:52 foobar kernel: [20446.710055] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
> Feb 14 14:39:52 foobar kernel: [20446.718167] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
> Feb 14 14:39:52 foobar kernel: [20446.726279] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
> Feb 14 14:39:52 foobar kernel: [20446.734390] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
> Feb 14 14:39:52 foobar kernel: [20446.742502] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
> Feb 14 14:39:52 foobar kernel: [20446.742506] ath9k: Unable to stop TxDMA. Reset HAL!
> Feb 14 14:39:52 foobar kernel: [20446.850877] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
> Feb 14 14:39:52 foobar kernel: [20446.850881] ath9k: Chip reset failed
> Feb 14 14:39:52 foobar kernel: [20446.850883] ath9k: Unable to reset hardware; reset status -22
> Feb 14 14:39:52 foobar kernel: [20446.861656] ath9k: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff
> Feb 14 14:39:52 foobar kernel: [20446.969249] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
> Feb 14 14:39:52 foobar kernel: [20447.076842] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
> Feb 14 14:39:52 foobar kernel: [20447.399108] ath9k 0000:03:00.0: PCI INT A disabled
> Feb 14 14:39:54 foobar kernel: [20448.488074] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
> Feb 14 14:39:54 foobar kernel: [20448.488156] pci 0000:03:00.0: reg 10 32bit mmio: [0x000000-0x00ffff]
> Feb 14 14:39:54 foobar kernel: [20448.488495] ath9k 0000:03:00.0: enabling device (0000 -> 0002)
> Feb 14 14:39:54 foobar kernel: [20448.488518] ath9k 0000:03:00.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
> Feb 14 14:39:54 foobar kernel: [20448.939749] ath: EEPROM regdomain: 0x30
> Feb 14 14:39:54 foobar kernel: [20448.939754] ath: EEPROM indicates we should expect a direct regpair map
> Feb 14 14:39:54 foobar kernel: [20448.939757] ath: Country alpha2 being used: AM
> Feb 14 14:39:54 foobar kernel: [20448.939759] ath: Regpair used: 0x30
> Feb 14 14:39:54 foobar kernel: [20448.945107] phy2: Selected rate control algorithm 'ath9k_rate_control'
> Feb 14 14:39:54 foobar kernel: [20448.946630] cfg80211: Calling CRDA for country: AM
> Feb 14 14:39:54 foobar kernel: [20448.947513] Registered led device: ath9k-phy2::radio
> Feb 14 14:39:54 foobar kernel: [20448.948455] Registered led device: ath9k-phy2::assoc
> Feb 14 14:39:54 foobar kernel: [20448.948959] Registered led device: ath9k-phy2::tx
> Feb 14 14:39:54 foobar kernel: [20448.949443] Registered led device: ath9k-phy2::rx
> Feb 14 14:39:54 foobar kernel: [20448.949458] phy2: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81: mem=0xf8520000, irq=11
> Feb 14 14:39:54 foobar kernel: [20449.105089] cfg80211: Current regulatory domain intersected:
> Feb 14 14:39:54 foobar kernel: [20449.105100] ?(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> Feb 14 14:39:54 foobar kernel: [20449.105110] ?(2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
> Feb 14 14:39:54 foobar kernel: [20449.105119] ?(5170000 KHz - 5250000 KHz @ 20000 KHz), (N/A, 1800 mBm)
> Feb 14 14:39:54 foobar kernel: [20449.105128] ?(5250000 KHz - 5330000 KHz @ 20000 KHz), (N/A, 1800 mBm)
> Feb 14 14:39:54 foobar kernel: [20449.162437] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> Feb 14 14:40:01 foobar kernel: [20455.898813] wlan0: deauthenticating from 00:0d:0b:b2:8c:dd by local choice (reason=3)
> Feb 14 14:40:01 foobar kernel: [20455.904452] wlan0: direct probe to AP 00:0d:0b:b2:8c:dd (try 1)
> Feb 14 14:40:01 foobar kernel: [20455.908238] wlan0: direct probe responded
> Feb 14 14:40:01 foobar kernel: [20455.908242] wlan0: authenticate with AP 00:0d:0b:b2:8c:dd (try 1)
> Feb 14 14:40:01 foobar kernel: [20455.910440] wlan0: authenticated
>
> I'll have to find out if there really was some original karmic kernels (without the compat-wireless backport updates)
> that actually doesn't have this hang problem.
Karmic uses 2.6.31 which has already reached the end of its
development. You will no longer see stable kernel releases based on
2.6.31.y kernels so best is to upgrade. ath9k had a large number of
patches which did not get merged into 2.6.31 [1] which should have,
which is why we worked hard for 2.6.32 to ensure all regressions/fixes
are propagated to stable.
Karmic ships lbm though and that uses the 802.11 bits from 2.6.32
which should be good.
[1] http://bombadil.infradead.org/~mcgrof/patches/ath9k/fixes-not-in-2.6.31-for-ath9k.txt
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-22 18:02 ` Luis R. Rodriguez
@ 2010-02-22 18:24 ` Tomi Orava
2010-02-22 18:34 ` Luis R. Rodriguez
0 siblings, 1 reply; 26+ messages in thread
From: Tomi Orava @ 2010-02-22 18:24 UTC (permalink / raw)
To: ath9k-devel
Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
> On Sun, Feb 21, 2010 at 12:31 AM, Tomi Orava
> <Tomi.Orava@ncircle.nullnet.fi> wrote:
>> On 02/18/2010 11:58 PM, Mark Sutton wrote:
>>> On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote:
>>>> Hi,
>>>> ? ? ?I have this problem as well.
>>>> Hardware is:
>>>>
>>>> Atheros Communications Inc. AR5008
>>>> Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
>>>>
>>>> Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686
>>>> GNU/Linux
<snip>
> Karmic uses 2.6.31 which has already reached the end of its
> development. You will no longer see stable kernel releases based on
> 2.6.31.y kernels so best is to upgrade. ath9k had a large number of
> patches which did not get merged into 2.6.31 [1] which should have,
> which is why we worked hard for 2.6.32 to ensure all regressions/fixes
> are propagated to stable.
>
> Karmic ships lbm though and that uses the 802.11 bits from 2.6.32
> which should be good.
>
> [1]
> http://bombadil.infradead.org/~mcgrof/patches/ath9k/fixes-not-in-2.6.31-for-ath9k.txt
Unfortunately, I completely forgot to mention the very important fact that
in my understanding the "standard" karmic kernels ie. 2.6.31.x worked
quite ok compared to the compat-wireless versions included in
linux-backports-karmic etc etc. In other words, my problem tends to be
that the latest
ath9k versions are having some problems, while the older 2.6.31 seem to
be working without hangs in my case (not counting connection drops
every once in a while). Sorry, for turning this upside down.
Although, I've been way too busy with other important matters, I'll
try to find the last "properly" working kernel by using the GIT kernel
versions, so that I can be sure about the used versions.
Unfortunately, this laptop is quite slow and the hang doesn't happen
immediately (might take 1-2 days, but still it will always happen with
newer versions of the ath9k drivers). Anyway, it's very good to know
if these problems are more common among cards based on these chips or
is this just a rare case.
This particular card was sold as D-Link DWA-645.
I'll report back after I've done some more testing in order to get
more facts about different ath9k driver versions.
Regards,
Tomi Orava
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-22 18:24 ` Tomi Orava
@ 2010-02-22 18:34 ` Luis R. Rodriguez
0 siblings, 0 replies; 26+ messages in thread
From: Luis R. Rodriguez @ 2010-02-22 18:34 UTC (permalink / raw)
To: ath9k-devel
On Mon, Feb 22, 2010 at 10:24:57AM -0800, Tomi Orava wrote:
> Quoting "Luis R. Rodriguez" <mcgrof@gmail.com>:
>
> > On Sun, Feb 21, 2010 at 12:31 AM, Tomi Orava
> > <Tomi.Orava@ncircle.nullnet.fi> wrote:
> >> On 02/18/2010 11:58 PM, Mark Sutton wrote:
> >>> On Thu, Feb 18, 2010 at 12:31:26PM -0800, Mark Sutton wrote:
> >>>> Hi,
> >>>> ? ? ?I have this problem as well.
> >>>> Hardware is:
> >>>>
> >>>> Atheros Communications Inc. AR5008
> >>>> Atheros AR5416 MAC/BB Rev:2 AR5133 RF Rev:81
> >>>>
> >>>> Kernel:Linux 2.6.32.7 #2 PREEMPT Thu Feb 4 14:19:02 PST 2010 i686
> >>>> GNU/Linux
>
> <snip>
>
> > Karmic uses 2.6.31 which has already reached the end of its
> > development. You will no longer see stable kernel releases based on
> > 2.6.31.y kernels so best is to upgrade. ath9k had a large number of
> > patches which did not get merged into 2.6.31 [1] which should have,
> > which is why we worked hard for 2.6.32 to ensure all regressions/fixes
> > are propagated to stable.
> >
> > Karmic ships lbm though and that uses the 802.11 bits from 2.6.32
> > which should be good.
> >
> > [1]
> > http://bombadil.infradead.org/~mcgrof/patches/ath9k/fixes-not-in-2.6.31-for-ath9k.txt
>
> Unfortunately, I completely forgot to mention the very important fact that
> in my understanding the "standard" karmic kernels ie. 2.6.31.x worked
> quite ok compared to the compat-wireless versions included in
> linux-backports-karmic etc etc. In other words, my problem tends to be
> that the latest
> ath9k versions are having some problems, while the older 2.6.31 seem to
> be working without hangs in my case (not counting connection drops
> every once in a while). Sorry, for turning this upside down.
>
> Although, I've been way too busy with other important matters, I'll
> try to find the last "properly" working kernel by using the GIT kernel
> versions, so that I can be sure about the used versions.
> Unfortunately, this laptop is quite slow and the hang doesn't happen
> immediately (might take 1-2 days, but still it will always happen with
> newer versions of the ath9k drivers). Anyway, it's very good to know
> if these problems are more common among cards based on these chips or
> is this just a rare case.
>
> This particular card was sold as D-Link DWA-645.
>
> I'll report back after I've done some more testing in order to get
> more facts about different ath9k driver versions.
You'll want to read:
http://wireless.kernel.org/en/users/Documentation/Reporting_bugs
http://wireless.kernel.org/en/users/Documentation/Fix_Propagation
That should get you to test and report against the right thing.
Luis
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-17 18:15 ` Pavel Roskin
2010-02-18 12:58 ` [ath9k-devel] 802.11n in Ad-hoc mode Jónatan Muñoz
@ 2010-02-23 6:45 ` James Grossmann
2010-02-23 7:02 ` James Grossmann
1 sibling, 1 reply; 26+ messages in thread
From: James Grossmann @ 2010-02-23 6:45 UTC (permalink / raw)
To: ath9k-devel
On Wed, Feb 17, 2010 at 12:15 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Wed, 2010-02-17 at 09:56 -0800, hong zhang wrote:
>> > >
>> > I'm also sorry about that, on the other hand, there are
>> > many schools
>> > of thought on answering posts, but I don't want this to be
>> > a
>> > discussion of that.
>> > I would just like to get some ideas of what I can debug to
>> > get some
>> > answers. ?Out of curiosity, is there a way to do a
>> > continuous
>> > recording of dmesg to a serial console? ?These hangs
>> > occur regularly,
>>
>> Use netconsole but you need two machines.
>
> I would never recommend using netconsole to debug a hang in a network
> driver. ?Chances are too high that the hang will block the network stack
> and prevent the most interesting data from leaving the system.
>
> Besides, it's one thing to debug something that is easy to reproduce and
> that is known to show up on the netconsole. ?It's another thing to debug
> something that may not appear on any console after hours of waiting.
>
> --
> Regards,
> Pavel Roskin
>
Here is a dmesg containing a hang, the dmesg even notes that there was
a soft lockup.
I hope this helps, thanks in advance!
James
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kernel.log.lzma
Type: application/octet-stream
Size: 10225 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20100223/f93dd393/attachment.obj
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-23 6:45 ` [ath9k-devel] AR5008 hanging computer James Grossmann
@ 2010-02-23 7:02 ` James Grossmann
2010-03-11 8:01 ` Pavel Roskin
0 siblings, 1 reply; 26+ messages in thread
From: James Grossmann @ 2010-02-23 7:02 UTC (permalink / raw)
To: ath9k-devel
On Tue, Feb 23, 2010 at 12:45 AM, James Grossmann <cctsurf@gmail.com> wrote:
> On Wed, Feb 17, 2010 at 12:15 PM, Pavel Roskin <proski@gnu.org> wrote:
>> On Wed, 2010-02-17 at 09:56 -0800, hong zhang wrote:
>>> > >
>>> > I'm also sorry about that, on the other hand, there are
>>> > many schools
>>> > of thought on answering posts, but I don't want this to be
>>> > a
>>> > discussion of that.
>>> > I would just like to get some ideas of what I can debug to
>>> > get some
>>> > answers. ?Out of curiosity, is there a way to do a
>>> > continuous
>>> > recording of dmesg to a serial console? ?These hangs
>>> > occur regularly,
>>>
>>> Use netconsole but you need two machines.
>>
>> I would never recommend using netconsole to debug a hang in a network
>> driver. ?Chances are too high that the hang will block the network stack
>> and prevent the most interesting data from leaving the system.
>>
>> Besides, it's one thing to debug something that is easy to reproduce and
>> that is known to show up on the netconsole. ?It's another thing to debug
>> something that may not appear on any console after hours of waiting.
>>
>> --
>> Regards,
>> Pavel Roskin
>>
>
> Here is a dmesg containing a hang, the dmesg even notes that there was
> a soft lockup.
> I hope this helps, thanks in advance!
> James
>
I should note that I am now using a different computer with that card,
again, kubuntu, but using the 2.6.32.8 kernel available at
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.8/. I have also
updated to the latest linuxwireless compat drivers.
Thanks again!
James
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] 802.11n in Ad-hoc mode
2010-02-18 12:58 ` [ath9k-devel] 802.11n in Ad-hoc mode Jónatan Muñoz
@ 2010-02-24 7:02 ` Zhang Yanfei-B21500
2010-02-24 16:35 ` Jónatan Muñoz
0 siblings, 1 reply; 26+ messages in thread
From: Zhang Yanfei-B21500 @ 2010-02-24 7:02 UTC (permalink / raw)
To: ath9k-devel
Hi John
Do you have run successful in ad-hoc mode?
Regards,
yanfei
> -----Original Message-----
> From: ath9k-devel-bounces at venema.h4ckr.net
> [mailto:ath9k-devel-bounces at venema.h4ckr.net] On Behalf Of
> J?natan Mu?oz
> Sent: Thursday, February 18, 2010 8:59 PM
> To: ath9k-devel at venema.h4ckr.net
> Subject: [ath9k-devel] 802.11n in Ad-hoc mode
>
> Hi all,
>
> I am interested in the current status of 802.11n support
> under ad-hoc mode.
>
> Do you know anything?
>
> Are there some deadlines or plans implementing ad-hoc mode in 802.11n?
>
> I have AR928x Atheros chipset.
>
> Thanks,
>
> John
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] 802.11n in Ad-hoc mode
2010-02-24 7:02 ` Zhang Yanfei-B21500
@ 2010-02-24 16:35 ` Jónatan Muñoz
0 siblings, 0 replies; 26+ messages in thread
From: Jónatan Muñoz @ 2010-02-24 16:35 UTC (permalink / raw)
To: ath9k-devel
Hi yanfei,
in 802.11n not yet. I don't know how.
Regards
-----Mensaje original-----
De: Zhang Yanfei-B21500 [mailto:B21500 at freescale.com]
Enviado el: mi?rcoles, 24 de febrero de 2010 8:02
Para: J?natan Mu?oz; ath9k-devel at venema.h4ckr.net
Asunto: RE: [ath9k-devel] 802.11n in Ad-hoc mode
Hi John
Do you have run successful in ad-hoc mode?
Regards,
yanfei
> -----Original Message-----
> From: ath9k-devel-bounces at venema.h4ckr.net
> [mailto:ath9k-devel-bounces at venema.h4ckr.net] On Behalf Of
> J?natan Mu?oz
> Sent: Thursday, February 18, 2010 8:59 PM
> To: ath9k-devel at venema.h4ckr.net
> Subject: [ath9k-devel] 802.11n in Ad-hoc mode
>
> Hi all,
>
> I am interested in the current status of 802.11n support
> under ad-hoc mode.
>
> Do you know anything?
>
> Are there some deadlines or plans implementing ad-hoc mode in 802.11n?
>
> I have AR928x Atheros chipset.
>
> Thanks,
>
> John
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-19 1:36 ` Pavel Roskin
@ 2010-03-05 23:04 ` Mark Sutton
2010-03-11 7:56 ` Pavel Roskin
0 siblings, 1 reply; 26+ messages in thread
From: Mark Sutton @ 2010-03-05 23:04 UTC (permalink / raw)
To: ath9k-devel
> > Pid: 621, comm: phy0 Not tainted (2.6.32.7 #2) Portable PC
> > EIP: 0060:[<f087fa1f>] EFLAGS: 00000292 CPU: 0
> > EIP is at yenta_interrupt+0x1f/0xf0 [yenta_socket]
>
> That's the PCMCIA subsystem, not ath9k. We could suspect ath9k to cause
> it if it was immediately after ath9k was loaded, but there were other
> things going on after the ath9k initialization.
>
Sorry about that Pavel, this was a boot hang after a crash caused through
an ath9k hang. I thought it was the same problem, but the card is
mini-pci, so shouldn't have to do with yenta.
I can cause the hang every time if I boot the machine with no
configured AP available. I have rebuilt ath9k with debugging and configured
kdump. I was just trying to make a core dump by unplugging the AP.
This time it took 55 seconds for the machine to hang. I say hang not crash
since after two or so minutes (not knowing what should happen with a kdump
kernel, there is no "stop-a" like on sparc) it came back.
I have included the traces from dmesg.
I can also pass debug mask or I guess force a dump, which ever is
more useful. The driver will also not scan for APs after a suspend to ram.
Booting the machine in an area without wifi will cause a hang every time,
even just booting to a cli login prompt.
Time frame is 30 to 120 seconds.
I suppose now it would come back if an AP were turned on.
Logging in as root and rmmod ath9k, problem goes away.
The driver/card will run for weeks if associated.
Is it possible this is a hardware issue?
Thanks, mark
wlan0: direct probe to AP 00:0c:e5:48:f9:2f (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:0c:e5:48:f9:2f (try 1)
wlan0: authenticated
wlan0: associate with AP 00:0c:e5:48:f9:2f (try 1)
wlan0: RX AssocResp from 00:0c:e5:48:f9:2f (capab=0x401 status=0 aid=1)
wlan0: associated
No probe response from AP 00:0c:e5:48:f9:2f after 500ms, disconnecting.
BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
Modules linked in: usbhid hid nvidia(P) acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm ath9k pcmcia snd_seq mac80211 snd_timer yenta_socket snd_seq_device ath fan rsrc_nonstatic uhci_hcd thermal cfg80211 video snd processor toshiba_acpi pcmcia_core ehci_hcd thermal_sys led_class rtc_cmos e100 soundcore rtc_core battery ac evdev hwmon mii rtc_lib output rfkill snd_page_alloc intel_agp usbcore psmouse agpgart button
Pid: 604, comm: phy0 Tainted: P (2.6.32.7 #4) Portable PC
EIP: 0060:[<c0294d02>] EFLAGS: 00000296 CPU: 0
EIP is at ioread32+0x32/0x40
EAX: 00000000 EBX: edc40000 ECX: f0c40000 EDX: f0c48258
ESI: edc40000 EDI: 00001000 EBP: 00000000 ESP: ed899d24
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b7868000 CR3: 27fc7000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<f0bfc656>] ? ath9k_hw_procmibevent+0x36/0x140 [ath9k]
[<f0c03090>] ? ath_isr+0x140/0x180 [ath9k]
[<c015f175>] ? handle_IRQ_event+0x45/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c016122d>] ? handle_level_irq+0x7d/0x120
[<c0104d75>] ? handle_irq+0x15/0x20
[<c010492a>] ? do_IRQ+0x3a/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c012b4ad>] ? __do_softirq+0x3d/0x1d0
[<c015f175>] ? handle_IRQ_event+0x45/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c0106280>] ? enable_8259A_irq+0x40/0x70
[<c012b66d>] ? do_softirq+0x2d/0x40
[<c012b825>] ? irq_exit+0x65/0x70
[<c0104933>] ? do_IRQ+0x43/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c0294d02>] ? ioread32+0x32/0x40
[<f0be83b4>] ? ath9k_hw_set_interrupts+0x294/0x350 [ath9k]
[<f0c00e0d>] ? ath_set_channel+0x19d/0x1a0 [ath9k]
[<f0c02efd>] ? ath9k_config+0x2ed/0x340 [ath9k]
[<f0b26056>] ? ieee80211_hw_config+0x56/0xa0 [mac80211]
[<f0b29dcd>] ? ieee80211_scan_work+0x28d/0x530 [mac80211]
[<c013eb00>] ? prepare_to_wait_exclusive+0x40/0x90
[<f0b29b40>] ? ieee80211_scan_work+0x0/0x530 [mac80211]
[<c013af8a>] ? worker_thread+0x13a/0x2b0
[<c011d001>] ? pick_next_task_fair+0xb1/0x100
[<c013e8e0>] ? autoremove_wake_function+0x0/0x40
[<c013ae50>] ? worker_thread+0x0/0x2b0
[<c013e624>] ? kthread+0x74/0x80
[<c013e5b0>] ? kthread+0x0/0x80
[<c01035d3>] ? kernel_thread_helper+0x7/0x14
BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
Modules linked in: usbhid hid nvidia(P) acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm ath9k pcmcia snd_seq mac80211 snd_timer yenta_socket snd_seq_device ath fan rsrc_nonstatic uhci_hcd thermal cfg80211 video snd processor toshiba_acpi pcmcia_core ehci_hcd thermal_sys led_class rtc_cmos e100 soundcore rtc_core battery ac evdev hwmon mii rtc_lib output rfkill snd_page_alloc intel_agp usbcore psmouse agpgart button
Pid: 604, comm: phy0 Tainted: P (2.6.32.7 #4) Portable PC
EIP: 0060:[<c0294d02>] EFLAGS: 00000296 CPU: 0
EIP is at ioread32+0x32/0x40
EAX: 00000000 EBX: edc40000 ECX: f0c40000 EDX: f0c48258
ESI: edc40000 EDI: 00001000 EBP: 00000000 ESP: ed899c7c
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b7868000 CR3: 27fc7000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<f0bfc656>] ? ath9k_hw_procmibevent+0x36/0x140 [ath9k]
[<f0c03090>] ? ath_isr+0x140/0x180 [ath9k]
[<c015f175>] ? handle_IRQ_event+0x45/0x190
[<c0161273>] ? handle_level_irq+0xc3/0x120
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c016122d>] ? handle_level_irq+0x7d/0x120
[<c0104d75>] ? handle_irq+0x15/0x20
[<c010492a>] ? do_IRQ+0x3a/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<f0c00000>] ? ath9k_configure_filter+0x40/0x70 [ath9k]
[<c015f146>] ? handle_IRQ_event+0x16/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c016122d>] ? handle_level_irq+0x7d/0x120
[<c0104d75>] ? handle_irq+0x15/0x20
[<c010492a>] ? do_IRQ+0x3a/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c012b4ad>] ? __do_softirq+0x3d/0x1d0
[<c015f175>] ? handle_IRQ_event+0x45/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c0106280>] ? enable_8259A_irq+0x40/0x70
[<c012b66d>] ? do_softirq+0x2d/0x40
[<c012b825>] ? irq_exit+0x65/0x70
[<c0104933>] ? do_IRQ+0x43/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c0294d02>] ? ioread32+0x32/0x40
[<f0be83b4>] ? ath9k_hw_set_interrupts+0x294/0x350 [ath9k]
[<f0c00e0d>] ? ath_set_channel+0x19d/0x1a0 [ath9k]
[<f0c02efd>] ? ath9k_config+0x2ed/0x340 [ath9k]
[<f0b26056>] ? ieee80211_hw_config+0x56/0xa0 [mac80211]
[<f0b29dcd>] ? ieee80211_scan_work+0x28d/0x530 [mac80211]
[<c013eb00>] ? prepare_to_wait_exclusive+0x40/0x90
[<f0b29b40>] ? ieee80211_scan_work+0x0/0x530 [mac80211]
[<c013af8a>] ? worker_thread+0x13a/0x2b0
[<c011d001>] ? pick_next_task_fair+0xb1/0x100
[<c013e8e0>] ? autoremove_wake_function+0x0/0x40
[<c013ae50>] ? worker_thread+0x0/0x2b0
[<c013e624>] ? kthread+0x74/0x80
[<c013e5b0>] ? kthread+0x0/0x80
[<c01035d3>] ? kernel_thread_helper+0x7/0x14
BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
Modules linked in: usbhid hid nvidia(P) acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm ath9k pcmcia snd_seq mac80211 snd_timer yenta_socket snd_seq_device ath fan rsrc_nonstatic uhci_hcd thermal cfg80211 video snd processor toshiba_acpi pcmcia_core ehci_hcd thermal_sys led_class rtc_cmos e100 soundcore rtc_core battery ac evdev hwmon mii rtc_lib output rfkill snd_page_alloc intel_agp usbcore psmouse agpgart button
Pid: 604, comm: phy0 Tainted: P (2.6.32.7 #4) Portable PC
EIP: 0060:[<c015f146>] EFLAGS: 00000246 CPU: 0
EIP is at handle_IRQ_event+0x16/0x190
EAX: 0000000b EBX: eea10580 ECX: 00020101 EDX: eea10580
ESI: 0000000b EDI: 00000000 EBP: ed899d10 ESP: ed899ca4
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b7868000 CR3: 27fc7000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<c0161273>] ? handle_level_irq+0xc3/0x120
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c016122d>] ? handle_level_irq+0x7d/0x120
[<c0104d75>] ? handle_irq+0x15/0x20
[<c010492a>] ? do_IRQ+0x3a/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<f0c00000>] ? ath9k_configure_filter+0x40/0x70 [ath9k]
[<c015f146>] ? handle_IRQ_event+0x16/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c016122d>] ? handle_level_irq+0x7d/0x120
[<c0104d75>] ? handle_irq+0x15/0x20
[<c010492a>] ? do_IRQ+0x3a/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c012b4ad>] ? __do_softirq+0x3d/0x1d0
[<c015f175>] ? handle_IRQ_event+0x45/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c0106280>] ? enable_8259A_irq+0x40/0x70
[<c012b66d>] ? do_softirq+0x2d/0x40
[<c012b825>] ? irq_exit+0x65/0x70
[<c0104933>] ? do_IRQ+0x43/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c0294d02>] ? ioread32+0x32/0x40
[<f0be83b4>] ? ath9k_hw_set_interrupts+0x294/0x350 [ath9k]
[<f0c00e0d>] ? ath_set_channel+0x19d/0x1a0 [ath9k]
[<f0c02efd>] ? ath9k_config+0x2ed/0x340 [ath9k]
[<f0b26056>] ? ieee80211_hw_config+0x56/0xa0 [mac80211]
[<f0b29dcd>] ? ieee80211_scan_work+0x28d/0x530 [mac80211]
[<c013eb00>] ? prepare_to_wait_exclusive+0x40/0x90
[<f0b29b40>] ? ieee80211_scan_work+0x0/0x530 [mac80211]
[<c013af8a>] ? worker_thread+0x13a/0x2b0
[<c011d001>] ? pick_next_task_fair+0xb1/0x100
[<c013e8e0>] ? autoremove_wake_function+0x0/0x40
[<c013ae50>] ? worker_thread+0x0/0x2b0
[<c013e624>] ? kthread+0x74/0x80
[<c013e5b0>] ? kthread+0x0/0x80
[<c01035d3>] ? kernel_thread_helper+0x7/0x14
BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
Modules linked in: usbhid hid nvidia(P) acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm ath9k pcmcia snd_seq mac80211 snd_timer yenta_socket snd_seq_device ath fan rsrc_nonstatic uhci_hcd thermal cfg80211 video snd processor toshiba_acpi pcmcia_core ehci_hcd thermal_sys led_class rtc_cmos e100 soundcore rtc_core battery ac evdev hwmon mii rtc_lib output rfkill snd_page_alloc intel_agp usbcore psmouse agpgart button
Pid: 604, comm: phy0 Tainted: P (2.6.32.7 #4) Portable PC
EIP: 0060:[<c0294d02>] EFLAGS: 00000296 CPU: 0
EIP is at ioread32+0x32/0x40
EAX: 00000000 EBX: edc40000 ECX: f0c40000 EDX: f0c4402c
ESI: 00000000 EDI: f0c29bed EBP: f4041071 ESP: ed899c60
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
CR0: 8005003b CR2: b7868000 CR3: 27fc7000 CR4: 000006d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
DR6: ffff0ff0 DR7: 00000400
Call Trace:
[<f0be8464>] ? ath9k_hw_set_interrupts+0x344/0x350 [ath9k]
[<f0c03089>] ? ath_isr+0x139/0x180 [ath9k]
[<c015f175>] ? handle_IRQ_event+0x45/0x190
[<c0161273>] ? handle_level_irq+0xc3/0x120
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c016122d>] ? handle_level_irq+0x7d/0x120
[<c0104d75>] ? handle_irq+0x15/0x20
[<c010492a>] ? do_IRQ+0x3a/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<f0c00000>] ? ath9k_configure_filter+0x40/0x70 [ath9k]
[<c015f146>] ? handle_IRQ_event+0x16/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c016122d>] ? handle_level_irq+0x7d/0x120
[<c0104d75>] ? handle_irq+0x15/0x20
[<c010492a>] ? do_IRQ+0x3a/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c012b4ad>] ? __do_softirq+0x3d/0x1d0
[<c015f175>] ? handle_IRQ_event+0x45/0x190
[<c010637c>] ? mask_and_ack_8259A+0x5c/0x100
[<c0106280>] ? enable_8259A_irq+0x40/0x70
[<c012b66d>] ? do_softirq+0x2d/0x40
[<c012b825>] ? irq_exit+0x65/0x70
[<c0104933>] ? do_IRQ+0x43/0xa0
[<c01034e9>] ? common_interrupt+0x29/0x30
[<c0294d02>] ? ioread32+0x32/0x40
[<f0be83b4>] ? ath9k_hw_set_interrupts+0x294/0x350 [ath9k]
[<f0c00e0d>] ? ath_set_channel+0x19d/0x1a0 [ath9k]
[<f0c02efd>] ? ath9k_config+0x2ed/0x340 [ath9k]
[<f0b26056>] ? ieee80211_hw_config+0x56/0xa0 [mac80211]
[<f0b29dcd>] ? ieee80211_scan_work+0x28d/0x530 [mac80211]
[<c013eb00>] ? prepare_to_wait_exclusive+0x40/0x90
[<f0b29b40>] ? ieee80211_scan_work+0x0/0x530 [mac80211]
[<c013af8a>] ? worker_thread+0x13a/0x2b0
[<c011d001>] ? pick_next_task_fair+0xb1/0x100
[<c013e8e0>] ? autoremove_wake_function+0x0/0x40
[<c013ae50>] ? worker_thread+0x0/0x2b0
[<c013e624>] ? kthread+0x74/0x80
[<c013e5b0>] ? kthread+0x0/0x80
[<c01035d3>] ? kernel_thread_helper+0x7/0x14
wlan0: direct probe to AP 00:0c:e5:48:f9:2f (try 1)
wlan0: direct probe responded
wlan0: authenticate with AP 00:0c:e5:48:f9:2f (try 1)
wlan0: authenticated
wlan0: associate with AP 00:0c:e5:48:f9:2f (try 1)
wlan0: RX AssocResp from 00:0c:e5:48:f9:2f (capab=0x401 status=0 aid=1)
wlan0: associated
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-03-05 23:04 ` Mark Sutton
@ 2010-03-11 7:56 ` Pavel Roskin
2010-03-11 10:38 ` Peter Stuge
2010-04-17 17:49 ` Tomi Orava
0 siblings, 2 replies; 26+ messages in thread
From: Pavel Roskin @ 2010-03-11 7:56 UTC (permalink / raw)
To: ath9k-devel
On Fri, 2010-03-05 at 15:04 -0800, Mark Sutton wrote:
> Is it possible this is a hardware issue?
It looks like a hardware issue, but maybe it can be worked around.
> BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
> Modules linked in: usbhid hid nvidia(P) acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm ath9k pcmcia snd_seq mac80211 snd_timer yenta_socket snd_seq_device ath fan rsrc_nonstatic uhci_hcd thermal cfg80211 video snd processor toshiba_acpi pcmcia_core ehci_hcd thermal_sys led_class rtc_cmos e100 soundcore rtc_core battery ac evdev hwmon mii rtc_lib output rfkill snd_page_alloc intel_agp usbcore psmouse agpgart button
>
> Pid: 604, comm: phy0 Tainted: P (2.6.32.7 #4) Portable PC
> EIP: 0060:[<c0294d02>] EFLAGS: 00000296 CPU: 0
> EIP is at ioread32+0x32/0x40
> EAX: 00000000 EBX: edc40000 ECX: f0c40000 EDX: f0c48258
> ESI: edc40000 EDI: 00001000 EBP: 00000000 ESP: ed899d24
> DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
> CR0: 8005003b CR2: b7868000 CR3: 27fc7000 CR4: 000006d0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff0ff0 DR7: 00000400
> Call Trace:
> [<f0bfc656>] ? ath9k_hw_procmibevent+0x36/0x140 [ath9k]
I believe the register number is in DX. Register 0x8258 is
AR_SLP_MIB_CTRL, and it's indeed being read in ath9k_hw_procmibevent().
Somehow reading that register causes a CPU lockup.
An easy workaround would be to comment out this line in ani.c:
if (!(REG_READ(ah, AR_SLP_MIB_CTRL) & AR_SLP_MIB_PENDING))
Leave the new line so that the register is cleared unconditionally.
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-02-23 7:02 ` James Grossmann
@ 2010-03-11 8:01 ` Pavel Roskin
0 siblings, 0 replies; 26+ messages in thread
From: Pavel Roskin @ 2010-03-11 8:01 UTC (permalink / raw)
To: ath9k-devel
On Tue, 2010-02-23 at 01:02 -0600, James Grossmann wrote:
> > Here is a dmesg containing a hang, the dmesg even notes that there was
> > a soft lockup.
> > I hope this helps, thanks in advance!
Sorry for delay.
Assuming the the EDX register holds the chip register number number, it
looks like a CPU lockup when AR_ISR_RAC is read in ath9k_hw_getisr(). I
have no idea how to work it around. Maybe somebody with access to
Atheros specifications could help?
--
Regards,
Pavel Roskin
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-03-11 7:56 ` Pavel Roskin
@ 2010-03-11 10:38 ` Peter Stuge
2010-04-17 17:49 ` Tomi Orava
1 sibling, 0 replies; 26+ messages in thread
From: Peter Stuge @ 2010-03-11 10:38 UTC (permalink / raw)
To: ath9k-devel
Pavel Roskin wrote:
> > BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
Yesterday I experienced a panic when I put some load on my 5008 card.
I'm using wireless-testing as of Mar 7, and in general this is a
clear improvement when compared with code as of Feb 1. Thanks to
Felix for great work on the driver!
Unfortunately I don't have a backtrace since I was in X on my laptop,
and I also haven't been able to reproduce the issue. :\
Will post again, possibly in a new thread, if I can make it happen
again. Previously I have not been using .11n much, but now I was, 130
or 170Mb connection and 70/70 link quality, I was a few meters away
from the AP.
//Peter
^ permalink raw reply [flat|nested] 26+ messages in thread
* [ath9k-devel] AR5008 hanging computer
2010-03-11 7:56 ` Pavel Roskin
2010-03-11 10:38 ` Peter Stuge
@ 2010-04-17 17:49 ` Tomi Orava
1 sibling, 0 replies; 26+ messages in thread
From: Tomi Orava @ 2010-04-17 17:49 UTC (permalink / raw)
To: ath9k-devel
Quoting Pavel Roskin <proski@gnu.org>:
> On Fri, 2010-03-05 at 15:04 -0800, Mark Sutton wrote:
>
>> Is it possible this is a hardware issue?
>
> It looks like a hardware issue, but maybe it can be worked around.
>
>> BUG: soft lockup - CPU#0 stuck for 61s! [phy0:604]
>> Modules linked in: usbhid hid nvidia(P) acpi_cpufreq cpufreq_stats
>> cpufreq_userspace cpufreq_ondemand cpufreq_powersave freq_table
>> cpufreq_conservative lm90 adm1021 arc4 ecb snd_intel8x0
>> snd_ac97_codec ac97_bus snd_pcm ath9k pcmcia snd_seq mac80211
>> snd_timer yenta_socket snd_seq_device ath fan rsrc_nonstatic
>> uhci_hcd thermal cfg80211 video snd processor toshiba_acpi
>> pcmcia_core ehci_hcd thermal_sys led_class rtc_cmos e100 soundcore
>> rtc_core battery ac evdev hwmon mii rtc_lib output rfkill
>> snd_page_alloc intel_agp usbcore psmouse agpgart button
>>
>> Pid: 604, comm: phy0 Tainted: P (2.6.32.7 #4) Portable PC
>> EIP: 0060:[<c0294d02>] EFLAGS: 00000296 CPU: 0
>> EIP is at ioread32+0x32/0x40
>> EAX: 00000000 EBX: edc40000 ECX: f0c40000 EDX: f0c48258
>> ESI: edc40000 EDI: 00001000 EBP: 00000000 ESP: ed899d24
>> DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
>> CR0: 8005003b CR2: b7868000 CR3: 27fc7000 CR4: 000006d0
>> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
>> DR6: ffff0ff0 DR7: 00000400
>> Call Trace:
>> [<f0bfc656>] ? ath9k_hw_procmibevent+0x36/0x140 [ath9k]
>
> I believe the register number is in DX. Register 0x8258 is
> AR_SLP_MIB_CTRL, and it's indeed being read in ath9k_hw_procmibevent().
> Somehow reading that register causes a CPU lockup.
>
> An easy workaround would be to comment out this line in ani.c:
>
> if (!(REG_READ(ah, AR_SLP_MIB_CTRL) & AR_SLP_MIB_PENDING))
>
> Leave the new line so that the register is cleared unconditionally.
I've been running a 2.6.33.1 with this one line modification and I haven't
seen a single system hang anymore. My wlan device is sold as D-Link DWA-645:
03:00.0 Network controller: Atheros Communications Inc. AR5008
Wireless Network Adapter (rev 01)
Subsystem: Device 07d1:3a09
Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 11
Memory at 4c000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] #80 [0000]
Kernel driver in use: ath9k
Kernel modules: ath9k
Without this patch I would get a ath9k based hang in a 3-4 days time
eventually.
The hang could be solved usually by unplugging and re-plugging the
pcmcia card.
Regards,
Tomi Orava
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2010-04-17 17:49 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-02-12 15:25 [ath9k-devel] AR5008 hanging computer James Grossmann
2010-02-12 22:53 ` Pavel Roskin
2010-02-12 23:35 ` James Grossmann
2010-02-12 23:42 ` hong zhang
2010-02-15 7:03 ` Pavel Roskin
[not found] ` <167ae39b1002152030s170128a0j362e7e9c61a4af42@mail.gmail.com>
[not found] ` <1266296860.17808.2.camel@mj>
2010-02-16 23:54 ` James Grossmann
2010-02-17 17:47 ` Pavel Roskin
2010-02-17 17:56 ` hong zhang
2010-02-17 18:15 ` Pavel Roskin
2010-02-18 12:58 ` [ath9k-devel] 802.11n in Ad-hoc mode Jónatan Muñoz
2010-02-24 7:02 ` Zhang Yanfei-B21500
2010-02-24 16:35 ` Jónatan Muñoz
2010-02-23 6:45 ` [ath9k-devel] AR5008 hanging computer James Grossmann
2010-02-23 7:02 ` James Grossmann
2010-03-11 8:01 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2010-02-18 20:31 Mark Sutton
2010-02-18 21:58 ` Mark Sutton
2010-02-19 1:36 ` Pavel Roskin
2010-03-05 23:04 ` Mark Sutton
2010-03-11 7:56 ` Pavel Roskin
2010-03-11 10:38 ` Peter Stuge
2010-04-17 17:49 ` Tomi Orava
2010-02-21 8:31 ` Tomi Orava
2010-02-22 18:02 ` Luis R. Rodriguez
2010-02-22 18:24 ` Tomi Orava
2010-02-22 18:34 ` Luis R. Rodriguez
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.