yingqiang Ma wrote:
> 2010/1/20 Sujith
> > Yep, this happens because I changed the debug mask for that
> > message to FATAL.
> > It is harmless,
WTF?! Please make up your mind! Either it's FATAL, or it's harmless -
which is it?
> > but can be fixed by cleaning up the virtual wiphy / idle stuff.
On my machine when I encounter this issue, the wireless doesn't work any
more. My machine is running latest 2.6.32.7 as an AP on a ARM box.
2010/1/20 Sujith
> Benoit PAPILLAULT wrote:
> > I am seeing this as well on 2.6.33-rc4-wl, but only at unload time
> > (modprobe -r ath9k).
>
> Yep, this ha
Sujith wrote:
> Benoit PAPILLAULT wrote:
> > I am seeing this as well on 2.6.33-rc4-wl, but only at unload
> > time (modprobe -r ath9k).
>
> Yep, this happens because I changed the debug mask for that message
> to FATAL. It is harmless, but can be fixed by cleaning up the
> virtual wiphy / idle st
Benoit PAPILLAULT wrote:
> I am seeing this as well on 2.6.33-rc4-wl, but only at unload time
> (modprobe -r ath9k).
Yep, this happens because I changed the debug mask for that message to FATAL.
It is harmless, but can be fixed by cleaning up the virtual wiphy / idle stuff.
Sujith
___
On Tue, Jan 19, 2010 at 5:04 PM, Peter Stuge wrote:
> Luis R. Rodriguez wrote:
>> > [302214.359875] ath: Failed to stop TX DMA in 100 msec after killing last
>> > frame
>> > [302214.359900] ath: Unable to stop TxDMA. Reset HAL!
>>
>> What kernel?
>
> The one that I reported using in the disconnec
Luis R. Rodriguez wrote:
> > [302214.359875] ath: Failed to stop TX DMA in 100 msec after killing last
> > frame
> > [302214.359900] ath: Unable to stop TxDMA. Reset HAL!
>
> What kernel?
The one that I reported using in the disconnect thread. I'll repeat
in this thread. Sorry that I forgot to m
Luis R. Rodriguez a écrit :
> On Mon, Jan 18, 2010 at 06:31:19PM -0800, Peter Stuge wrote:
>
>> Today when I came home and resumed my system I got these messages
>> from the driver:
>>
>> [302214.156400] phy1: device no longer idle - scanning
>> [302214.341494] ath: ath_isr status=0009 imask
On Mon, Jan 18, 2010 at 06:31:19PM -0800, Peter Stuge wrote:
> Today when I came home and resumed my system I got these messages
> from the driver:
>
> [302214.156400] phy1: device no longer idle - scanning
> [302214.341494] ath: ath_isr status=0009 imask=f4001071 wecare=0001
> [302214.341
Today when I came home and resumed my system I got these messages
from the driver:
[302214.156400] phy1: device no longer idle - scanning
[302214.341494] ath: ath_isr status=0009 imask=f4001071 wecare=0001
[302214.341983] ath: ath_isr status=0109 imask=f4001071 wecare=0001
[302214.
