[ath9k-devel] Failed to stop TX DMA

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi

I am using an Atheros AR928X Wireless Network card on Fedora Core 16 
via hostapd so that I can use it as an access point.  I have had the 
same problem and I think it is documented as an outstanding problem on 
the compat-wireless page but wanted to confirm that and / or perhaps 
find out what is happening if anything with it.  Or its completely 
something I am doing wrong [ MOST LIKELY ]

I have upgraded from Fedora 14 to 16 and now installed via source 
compact-wireless-next software and still have the same problem.

The errors I see are as follows...

Dec 28 19:55:37 sun kernel: [424600.248087] ath: Failed to stop TX DMA, 
queues=0x008!
Dec 28 19:55:37 sun kernel: [424600.262969] ath: DMA failed to stop in 
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x000062c0
Dec 28 19:55:37 sun kernel: [424600.266712] ath: Could not stop RX, we 
could be confusing the DMA engine when we start RX up
Dec 28 19:55:38 sun kernel: [424600.614024] ath: Failed to stop TX DMA, 
queues=0x004!
Dec 28 19:55:38 sun kernel: [424600.628918] ath: DMA failed to stop in 
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Dec 28 19:55:38 sun kernel: [424600.632647] ath: Could not stop RX, we 
could be confusing the DMA engine when we start RX up
Dec 28 19:55:38 sun kernel: [424600.987737] ath: Failed to stop TX DMA, 
queues=0x00c!
Dec 28 19:55:38 sun kernel: [424601.002046] ath: DMA failed to stop in 
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Dec 28 19:55:38 sun kernel: [424601.004757] ath: Could not stop RX, we 
could be confusing the DMA engine when we start RX up
Dec 28 19:55:38 sun kernel: [424601.356582] ath: DMA failed to stop in 
10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Dec 28 19:55:38 sun kernel: [424601.360311] ath: Could not stop RX, we 
could be confusing the DMA engine when we start RX up

and on and on...

This is always re-creatable by using speedtest.org and testing the 
speed of the connection.

Any one have any ideas please?

Thanks

Paul

[ath9k-devel] Failed to stop TX DMA

[Adrian Chadd]

Hi,

On 28 December 2011 17:19, Paul Farrow <ath9k@thefabfarrows.com> wrote:
>
> Hi
>
> I am using an Atheros AR928X Wireless Network card on Fedora Core 16
> via hostapd so that I can use it as an access point. ?I have had the
> same problem and I think it is documented as an outstanding problem on
> the compat-wireless page but wanted to confirm that and / or perhaps
> find out what is happening if anything with it. ?Or its completely
> something I am doing wrong [ MOST LIKELY ]

Did you have this problem on FC14?

Is this a PCI or PCIe NIC? (ie, AR9220 or AR9280.) What's the PCI id?




Adrian

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Adrian

I believe !!  I had a problem on FC14 using the wifi.  After running a 
speedtest the whole machine would go incredibly slow but I must be 
honest I didn't see anything being logged.  So I took it upon myself to 
upgrade.  Once upgraded to Fedora 16 I saw these errors coming to the 
console which I didn't in FC14.  I then downloaded the latest source 
(compat wireless) and compiled and loaded per the compat-wireless 
instructions and I still see these errors (hopefully I did it 
correctly).

This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board.  I am not 
sure how to get the PCI id?  But here is the output from lspci.

03:00.0 Network controller: Atheros Communications Inc. AR928X Wireless 
Network Adapter (PCI-Express) (rev 01)

Thanks for any help in advance.

Paul

On Wed, 28 Dec 2011 20:07:32 -0800, Adrian Chadd wrote:
> Hi,
>
> On 28 December 2011 17:19, Paul Farrow <ath9k@thefabfarrows.com> 
> wrote:
>>
>> Hi
>>
>> I am using an Atheros AR928X Wireless Network card on Fedora Core 16
>> via hostapd so that I can use it as an access point. ?I have had the
>> same problem and I think it is documented as an outstanding problem 
>> on
>> the compat-wireless page but wanted to confirm that and / or perhaps
>> find out what is happening if anything with it. ?Or its completely
>> something I am doing wrong [ MOST LIKELY ]
>
> Did you have this problem on FC14?
>
> Is this a PCI or PCIe NIC? (ie, AR9220 or AR9280.) What's the PCI id?
>
>
>
>
> Adrian

[ath9k-devel] Failed to stop TX DMA

[Adrian Chadd]

On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com> wrote:
>
> Hi Adrian
>
> I believe !! ?I had a problem on FC14 using the wifi. ?After running a
> speedtest the whole machine would go incredibly slow but I must be

It's quite possible that the errors were just hidden with FC14.

> honest I didn't see anything being logged. ?So I took it upon myself to
> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming to the
> console which I didn't in FC14. ?I then downloaded the latest source
> (compat wireless) and compiled and loaded per the compat-wireless
> instructions and I still see these errors (hopefully I did it
> correctly).
>
> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I am not
> sure how to get the PCI id? ?But here is the output from lspci.

Try passing -vvv to lspci. I think that gets it to dump everything you need.

So the right thing to do here is establish whether it was a problem or
not with FC14. Are you able to find a compat-wireless version from way
back in the FC14 days (ie, whatever roughly it was shipping with,
either as a package or whatever was in the kernel FC14 shipped with)
and build it on FC16? Once we've got that working (ie, slowdown but no
console messages logged) we can try compiling it with debugging and
turning up the debugging. I can also go through and see what's
different between those two versions.

Bah, I really wish bugzilla.kernel.org was actually working at this
point. I'd really like to give all these bugs to the ath9k guys and
see if we can get some lab time to investigate. Having it in bugzilla
would certainly make that easier to track.


Adrian

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Ok Adrian

Firstly thanks for your help.  I would really like to get this going.

I can try to look for a version but I won't be able to do it until the 
back end of next week as I will be away for new year celebrations.

Here is the lspci -vvv for the Atheros device

03:00.0 Network controller: Atheros Communications Inc. AR928X Wireless 
Network Adapter (PCI-Express) (rev 01)
         Subsystem: Apple Computer Inc. Device 008f
         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B- DisINTx-
         Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
         Latency: 0, Cache Line Size: 64 bytes
         Interrupt: pin A routed to IRQ 18
         Region 0: Memory@fdbf0000 (64-bit, non-prefetchable) 
[size=64K]
         Capabilities: [40] Power Management version 2
                 Flags: PMEClk- DSI- D1+ D2- AuxCurrent=375mA 
PME(D0+,D1+,D2-,D3hot+,D3cold+)
                 Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
         Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
                 Address: 00000000  Data: 0000
         Capabilities: [60] Express (v1) Legacy Endpoint, MSI 00
                 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s 
<512ns, L1 <64us
                         ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
                 DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
                         RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
                         MaxPayload 128 bytes, MaxReadReq 512 bytes
                 DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- 
AuxPwr+ TransPend-
                 LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM unknown, 
Latency L0 <512ns, L1 <64us
                         ClockPM- Surprise- LLActRep- BwNot-
                 LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- 
CommClk+
                         ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                 LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
         Capabilities: [90] MSI-X: Enable- Count=1 Masked-
                 Vector table: BAR=0 offset=00000000
                 PBA: BAR=0 offset=00000000
         Capabilities: [100 v1] Advanced Error Reporting
                 UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- 
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                 UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- 
UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
                 UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- 
UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
                 CESta:  RxErr+ BadTLP+ BadDLLP+ Rollover- Timeout+ 
NonFatalErr-
                 CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
NonFatalErr-
                 AERCap: First Error Pointer: 00, GenCap+ CGenEn- 
ChkCap+ ChkEn-
         Capabilities: [140 v1] Virtual Channel
                 Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                 Arb:    Fixed- WRR32- WRR64- WRR128-
                 Ctrl:   ArbSelect=Fixed
                 Status: InProgress-
                 VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 
RejSnoopTrans-
                         Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- 
WRR256-
                         Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
                         Status: NegoPending- InProgress-
         Capabilities: [160 v1] Device Serial Number 
00-00-00-00-00-00-00-00
         Kernel driver in use: ath9k
         Kernel modules: ath9k

Hope that makes some sense to someone.

Happy New Year to you and thanks again

Paul

On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com> 
> wrote:
>>
>> Hi Adrian
>>
>> I believe !! ?I had a problem on FC14 using the wifi. ?After running 
>> a
>> speedtest the whole machine would go incredibly slow but I must be
>
> It's quite possible that the errors were just hidden with FC14.
>
>> honest I didn't see anything being logged. ?So I took it upon myself 
>> to
>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming to 
>> the
>> console which I didn't in FC14. ?I then downloaded the latest source
>> (compat wireless) and compiled and loaded per the compat-wireless
>> instructions and I still see these errors (hopefully I did it
>> correctly).
>>
>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I am 
>> not
>> sure how to get the PCI id? ?But here is the output from lspci.
>
> Try passing -vvv to lspci. I think that gets it to dump everything 
> you need.
>
> So the right thing to do here is establish whether it was a problem 
> or
> not with FC14. Are you able to find a compat-wireless version from 
> way
> back in the FC14 days (ie, whatever roughly it was shipping with,
> either as a package or whatever was in the kernel FC14 shipped with)
> and build it on FC16? Once we've got that working (ie, slowdown but 
> no
> console messages logged) we can try compiling it with debugging and
> turning up the debugging. I can also go through and see what's
> different between those two versions.
>
> Bah, I really wish bugzilla.kernel.org was actually working at this
> point. I'd really like to give all these bugs to the ath9k guys and
> see if we can get some lab time to investigate. Having it in bugzilla
> would certainly make that easier to track.
>
>
> Adrian

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Adrian

Just thinking about what you have asked me to do, does that mean that 
this card, driver and setup as an access point used to work??!!!!  I 
wondered if it had ever worked.

Cheers & Happy New Year

Paul

On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com> 
> wrote:
>>
>> Hi Adrian
>>
>> I believe !! ?I had a problem on FC14 using the wifi. ?After running 
>> a
>> speedtest the whole machine would go incredibly slow but I must be
>
> It's quite possible that the errors were just hidden with FC14.
>
>> honest I didn't see anything being logged. ?So I took it upon myself 
>> to
>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming to 
>> the
>> console which I didn't in FC14. ?I then downloaded the latest source
>> (compat wireless) and compiled and loaded per the compat-wireless
>> instructions and I still see these errors (hopefully I did it
>> correctly).
>>
>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I am 
>> not
>> sure how to get the PCI id? ?But here is the output from lspci.
>
> Try passing -vvv to lspci. I think that gets it to dump everything 
> you need.
>
> So the right thing to do here is establish whether it was a problem 
> or
> not with FC14. Are you able to find a compat-wireless version from 
> way
> back in the FC14 days (ie, whatever roughly it was shipping with,
> either as a package or whatever was in the kernel FC14 shipped with)
> and build it on FC16? Once we've got that working (ie, slowdown but 
> no
> console messages logged) we can try compiling it with debugging and
> turning up the debugging. I can also go through and see what's
> different between those two versions.
>
> Bah, I really wish bugzilla.kernel.org was actually working at this
> point. I'd really like to give all these bugs to the ath9k guys and
> see if we can get some lab time to investigate. Having it in bugzilla
> would certainly make that easier to track.
>
>
> Adrian

[ath9k-devel] Failed to stop TX DMA

[Mohammed Shafi]

On Fri, Dec 30, 2011 at 4:01 AM, Paul Farrow <ath9k@thefabfarrows.com> wrote:
>
> Adrian
>
> Just thinking about what you have asked me to do, does that mean that
> this card, driver and setup as an access point used to work??!!!! ?I
> wondered if it had ever worked.

please post your hostapd.conf and which hostapd version you are using
hostapd -v ?
i can see if its recreatble quite easily. i have ubuntu machines here

>
> Cheers & Happy New Year

happy new year :)
>
> Paul
>
> On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
>> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com>
>> wrote:
>>>
>>> Hi Adrian
>>>
>>> I believe !! ?I had a problem on FC14 using the wifi. ?After running
>>> a
>>> speedtest the whole machine would go incredibly slow but I must be
>>
>> It's quite possible that the errors were just hidden with FC14.
>>
>>> honest I didn't see anything being logged. ?So I took it upon myself
>>> to
>>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming to
>>> the
>>> console which I didn't in FC14. ?I then downloaded the latest source
>>> (compat wireless) and compiled and loaded per the compat-wireless
>>> instructions and I still see these errors (hopefully I did it
>>> correctly).
>>>
>>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I am
>>> not
>>> sure how to get the PCI id? ?But here is the output from lspci.
>>
>> Try passing -vvv to lspci. I think that gets it to dump everything
>> you need.
>>
>> So the right thing to do here is establish whether it was a problem
>> or
>> not with FC14. Are you able to find a compat-wireless version from
>> way
>> back in the FC14 days (ie, whatever roughly it was shipping with,
>> either as a package or whatever was in the kernel FC14 shipped with)
>> and build it on FC16? Once we've got that working (ie, slowdown but
>> no
>> console messages logged) we can try compiling it with debugging and
>> turning up the debugging. I can also go through and see what's
>> different between those two versions.
>>
>> Bah, I really wish bugzilla.kernel.org was actually working at this
>> point. I'd really like to give all these bugs to the ath9k guys and
>> see if we can get some lab time to investigate. Having it in bugzilla
>> would certainly make that easier to track.
>>
>>
>> Adrian
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel



-- 
shafi

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Mohammed

Firstly thanks very much.

hostapd -v gave

[root at sun ~]# hostapd -v
hostapd v0.7.3
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2010, Jouni Malinen <j@w1.fi> and contributors
[root at sun ~]#


my hostapd.conf file is as follows passwords and ssid has been replaced 
for security ...

logger_syslog=-1
logger_syslog_level=2
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0

# Some usable default settings...
macaddr_acl=0
auth_algs=1
ignore_broadcast_ssid=0
# Uncomment these for base WPA & WPA2 support with a pre-shared key
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP

# DO NOT FORGET TO SET A WPA PASSPHRASE!!
wpa_passphrase=password

# Most modern wireless drivers in the kernel need driver=nl80211
driver=nl80211

wme_enabled=1
ieee80211n=1
#ht_capab=[HT40-][SHORT-GI-40][DSSS_CCK-40]

# Customize these for your local configuration...
interface=wlan0
hw_mode=g
channel=2
ssid=ssid
ieee80211n=1
own_ip_addr=192.168.1.15


And uname -r yields

3.1.6-1.fc16.x86_64

Thanks again

Paul

On Fri, 30 Dec 2011 11:53:26 +0530, Mohammed Shafi wrote:
> On Fri, Dec 30, 2011 at 4:01 AM, Paul Farrow 
> <ath9k@thefabfarrows.com> wrote:
>>
>> Adrian
>>
>> Just thinking about what you have asked me to do, does that mean 
>> that
>> this card, driver and setup as an access point used to work??!!!! ?I
>> wondered if it had ever worked.
>
> please post your hostapd.conf and which hostapd version you are using
> hostapd -v ?
> i can see if its recreatble quite easily. i have ubuntu machines here
>
>>
>> Cheers & Happy New Year
>
> happy new year :)
>>
>> Paul
>>
>> On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
>>> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com>
>>> wrote:
>>>>
>>>> Hi Adrian
>>>>
>>>> I believe !! ?I had a problem on FC14 using the wifi. ?After 
>>>> running
>>>> a
>>>> speedtest the whole machine would go incredibly slow but I must be
>>>
>>> It's quite possible that the errors were just hidden with FC14.
>>>
>>>> honest I didn't see anything being logged. ?So I took it upon 
>>>> myself
>>>> to
>>>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming to
>>>> the
>>>> console which I didn't in FC14. ?I then downloaded the latest 
>>>> source
>>>> (compat wireless) and compiled and loaded per the compat-wireless
>>>> instructions and I still see these errors (hopefully I did it
>>>> correctly).
>>>>
>>>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I 
>>>> am
>>>> not
>>>> sure how to get the PCI id? ?But here is the output from lspci.
>>>
>>> Try passing -vvv to lspci. I think that gets it to dump everything
>>> you need.
>>>
>>> So the right thing to do here is establish whether it was a problem
>>> or
>>> not with FC14. Are you able to find a compat-wireless version from
>>> way
>>> back in the FC14 days (ie, whatever roughly it was shipping with,
>>> either as a package or whatever was in the kernel FC14 shipped 
>>> with)
>>> and build it on FC16? Once we've got that working (ie, slowdown but
>>> no
>>> console messages logged) we can try compiling it with debugging and
>>> turning up the debugging. I can also go through and see what's
>>> different between those two versions.
>>>
>>> Bah, I really wish bugzilla.kernel.org was actually working at this
>>> point. I'd really like to give all these bugs to the ath9k guys and
>>> see if we can get some lab time to investigate. Having it in 
>>> bugzilla
>>> would certainly make that easier to track.
>>>
>>>
>>> Adrian
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] Failed to stop TX DMA

[Mohammed Shafi]

Hi Paul,

sorry, i am into some critical tasks, i just could not analyze and
debug it now. will definitely take a look at this ASAP, also it
requires some good time to fix this.

On Wed, Jan 4, 2012 at 7:57 PM, Paul Farrow <ath9k@thefabfarrows.com> wrote:
>
> Hey Mohammed
>
> I hate to be on people especially as its an open source project but did I
> supply you everything that you might need to try to recreate the problem?
> ?Just want to make sure your not waiting on me :)
>
>
> Thanks again
>
> Paul
>
> On Fri, 30 Dec 2011 11:53:26 +0530, Mohammed Shafi wrote:
>>
>> On Fri, Dec 30, 2011 at 4:01 AM, Paul Farrow <ath9k@thefabfarrows.com>
>> wrote:
>>>
>>>
>>> Adrian
>>>
>>> Just thinking about what you have asked me to do, does that mean that
>>> this card, driver and setup as an access point used to work??!!!! ?I
>>> wondered if it had ever worked.
>>
>>
>> please post your hostapd.conf and which hostapd version you are using
>> hostapd -v ?
>> i can see if its recreatble quite easily. i have ubuntu machines here
>>
>>>
>>> Cheers & Happy New Year
>>
>>
>> happy new year :)
>>>
>>>
>>> Paul
>>>
>>> On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
>>>>
>>>> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com>
>>>> wrote:
>>>>>
>>>>>
>>>>> Hi Adrian
>>>>>
>>>>> I believe !! ?I had a problem on FC14 using the wifi. ?After running
>>>>> a
>>>>> speedtest the whole machine would go incredibly slow but I must be
>>>>
>>>>
>>>> It's quite possible that the errors were just hidden with FC14.
>>>>
>>>>> honest I didn't see anything being logged. ?So I took it upon myself
>>>>> to
>>>>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming to
>>>>> the
>>>>> console which I didn't in FC14. ?I then downloaded the latest source
>>>>> (compat wireless) and compiled and loaded per the compat-wireless
>>>>> instructions and I still see these errors (hopefully I did it
>>>>> correctly).
>>>>>
>>>>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I am
>>>>> not
>>>>> sure how to get the PCI id? ?But here is the output from lspci.
>>>>
>>>>
>>>> Try passing -vvv to lspci. I think that gets it to dump everything
>>>> you need.
>>>>
>>>> So the right thing to do here is establish whether it was a problem
>>>> or
>>>> not with FC14. Are you able to find a compat-wireless version from
>>>> way
>>>> back in the FC14 days (ie, whatever roughly it was shipping with,
>>>> either as a package or whatever was in the kernel FC14 shipped with)
>>>> and build it on FC16? Once we've got that working (ie, slowdown but
>>>> no
>>>> console messages logged) we can try compiling it with debugging and
>>>> turning up the debugging. I can also go through and see what's
>>>> different between those two versions.
>>>>
>>>> Bah, I really wish bugzilla.kernel.org was actually working at this
>>>> point. I'd really like to give all these bugs to the ath9k guys and
>>>> see if we can get some lab time to investigate. Having it in bugzilla
>>>> would certainly make that easier to track.
>>>>
>>>>
>>>> Adrian
>>>
>>>
>>> _______________________________________________
>>> ath9k-devel mailing list
>>> ath9k-devel at lists.ath9k.org
>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>



-- 
shafi

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Thank you.

Paul

On Thu, 5 Jan 2012 12:16:31 +0530, Mohammed Shafi wrote:
> Hi Paul,
>
> sorry, i am into some critical tasks, i just could not analyze and
> debug it now. will definitely take a look at this ASAP, also it
> requires some good time to fix this.
>
> On Wed, Jan 4, 2012 at 7:57 PM, Paul Farrow <ath9k@thefabfarrows.com> 
> wrote:
>>
>> Hey Mohammed
>>
>> I hate to be on people especially as its an open source project but 
>> did I
>> supply you everything that you might need to try to recreate the 
>> problem?
>> ?Just want to make sure your not waiting on me :)
>>
>>
>> Thanks again
>>
>> Paul
>>
>> On Fri, 30 Dec 2011 11:53:26 +0530, Mohammed Shafi wrote:
>>>
>>> On Fri, Dec 30, 2011 at 4:01 AM, Paul Farrow 
>>> <ath9k@thefabfarrows.com>
>>> wrote:
>>>>
>>>>
>>>> Adrian
>>>>
>>>> Just thinking about what you have asked me to do, does that mean 
>>>> that
>>>> this card, driver and setup as an access point used to work??!!!! 
>>>> ?I
>>>> wondered if it had ever worked.
>>>
>>>
>>> please post your hostapd.conf and which hostapd version you are 
>>> using
>>> hostapd -v ?
>>> i can see if its recreatble quite easily. i have ubuntu machines 
>>> here
>>>
>>>>
>>>> Cheers & Happy New Year
>>>
>>>
>>> happy new year :)
>>>>
>>>>
>>>> Paul
>>>>
>>>> On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
>>>>>
>>>>> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi Adrian
>>>>>>
>>>>>> I believe !! ?I had a problem on FC14 using the wifi. ?After 
>>>>>> running
>>>>>> a
>>>>>> speedtest the whole machine would go incredibly slow but I must 
>>>>>> be
>>>>>
>>>>>
>>>>> It's quite possible that the errors were just hidden with FC14.
>>>>>
>>>>>> honest I didn't see anything being logged. ?So I took it upon 
>>>>>> myself
>>>>>> to
>>>>>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming 
>>>>>> to
>>>>>> the
>>>>>> console which I didn't in FC14. ?I then downloaded the latest 
>>>>>> source
>>>>>> (compat wireless) and compiled and loaded per the 
>>>>>> compat-wireless
>>>>>> instructions and I still see these errors (hopefully I did it
>>>>>> correctly).
>>>>>>
>>>>>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I 
>>>>>> am
>>>>>> not
>>>>>> sure how to get the PCI id? ?But here is the output from lspci.
>>>>>
>>>>>
>>>>> Try passing -vvv to lspci. I think that gets it to dump 
>>>>> everything
>>>>> you need.
>>>>>
>>>>> So the right thing to do here is establish whether it was a 
>>>>> problem
>>>>> or
>>>>> not with FC14. Are you able to find a compat-wireless version 
>>>>> from
>>>>> way
>>>>> back in the FC14 days (ie, whatever roughly it was shipping with,
>>>>> either as a package or whatever was in the kernel FC14 shipped 
>>>>> with)
>>>>> and build it on FC16? Once we've got that working (ie, slowdown 
>>>>> but
>>>>> no
>>>>> console messages logged) we can try compiling it with debugging 
>>>>> and
>>>>> turning up the debugging. I can also go through and see what's
>>>>> different between those two versions.
>>>>>
>>>>> Bah, I really wish bugzilla.kernel.org was actually working at 
>>>>> this
>>>>> point. I'd really like to give all these bugs to the ath9k guys 
>>>>> and
>>>>> see if we can get some lab time to investigate. Having it in 
>>>>> bugzilla
>>>>> would certainly make that easier to track.
>>>>>
>>>>>
>>>>> Adrian
>>>>
>>>>
>>>> _______________________________________________
>>>> ath9k-devel mailing list
>>>> ath9k-devel at lists.ath9k.org
>>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>>

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Can any one confirm if they have a working AP with AR9280 card on 
Fedora 16?  I got the latest code base for hostapd and the ath9k driver 
and it appeared to work once but after that miracle it appears to error 
all the time.
I tried to take a code base of about a year back but compiling that 
seems to have lots of dependency errors for the age of the kernel.

Has any one got any suggestions how I might resolve this problem?

Thanks in advance

Paul

On Thu, 5 Jan 2012 12:16:31 +0530, Mohammed Shafi wrote:
> Hi Paul,
>
> sorry, i am into some critical tasks, i just could not analyze and
> debug it now. will definitely take a look at this ASAP, also it
> requires some good time to fix this.
>
> On Wed, Jan 4, 2012 at 7:57 PM, Paul Farrow <ath9k@thefabfarrows.com> 
> wrote:
>>
>> Hey Mohammed
>>
>> I hate to be on people especially as its an open source project but 
>> did I
>> supply you everything that you might need to try to recreate the 
>> problem?
>> ?Just want to make sure your not waiting on me :)
>>
>>
>> Thanks again
>>
>> Paul
>>
>> On Fri, 30 Dec 2011 11:53:26 +0530, Mohammed Shafi wrote:
>>>
>>> On Fri, Dec 30, 2011 at 4:01 AM, Paul Farrow 
>>> <ath9k@thefabfarrows.com>
>>> wrote:
>>>>
>>>>
>>>> Adrian
>>>>
>>>> Just thinking about what you have asked me to do, does that mean 
>>>> that
>>>> this card, driver and setup as an access point used to work??!!!! 
>>>> ?I
>>>> wondered if it had ever worked.
>>>
>>>
>>> please post your hostapd.conf and which hostapd version you are 
>>> using
>>> hostapd -v ?
>>> i can see if its recreatble quite easily. i have ubuntu machines 
>>> here
>>>
>>>>
>>>> Cheers & Happy New Year
>>>
>>>
>>> happy new year :)
>>>>
>>>>
>>>> Paul
>>>>
>>>> On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
>>>>>
>>>>> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi Adrian
>>>>>>
>>>>>> I believe !! ?I had a problem on FC14 using the wifi. ?After 
>>>>>> running
>>>>>> a
>>>>>> speedtest the whole machine would go incredibly slow but I must 
>>>>>> be
>>>>>
>>>>>
>>>>> It's quite possible that the errors were just hidden with FC14.
>>>>>
>>>>>> honest I didn't see anything being logged. ?So I took it upon 
>>>>>> myself
>>>>>> to
>>>>>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming 
>>>>>> to
>>>>>> the
>>>>>> console which I didn't in FC14. ?I then downloaded the latest 
>>>>>> source
>>>>>> (compat wireless) and compiled and loaded per the 
>>>>>> compat-wireless
>>>>>> instructions and I still see these errors (hopefully I did it
>>>>>> correctly).
>>>>>>
>>>>>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I 
>>>>>> am
>>>>>> not
>>>>>> sure how to get the PCI id? ?But here is the output from lspci.
>>>>>
>>>>>
>>>>> Try passing -vvv to lspci. I think that gets it to dump 
>>>>> everything
>>>>> you need.
>>>>>
>>>>> So the right thing to do here is establish whether it was a 
>>>>> problem
>>>>> or
>>>>> not with FC14. Are you able to find a compat-wireless version 
>>>>> from
>>>>> way
>>>>> back in the FC14 days (ie, whatever roughly it was shipping with,
>>>>> either as a package or whatever was in the kernel FC14 shipped 
>>>>> with)
>>>>> and build it on FC16? Once we've got that working (ie, slowdown 
>>>>> but
>>>>> no
>>>>> console messages logged) we can try compiling it with debugging 
>>>>> and
>>>>> turning up the debugging. I can also go through and see what's
>>>>> different between those two versions.
>>>>>
>>>>> Bah, I really wish bugzilla.kernel.org was actually working at 
>>>>> this
>>>>> point. I'd really like to give all these bugs to the ath9k guys 
>>>>> and
>>>>> see if we can get some lab time to investigate. Having it in 
>>>>> bugzilla
>>>>> would certainly make that easier to track.
>>>>>
>>>>>
>>>>> Adrian
>>>>
>>>>
>>>> _______________________________________________
>>>> ath9k-devel mailing list
>>>> ath9k-devel at lists.ath9k.org
>>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>>

[ath9k-devel] Failed to stop TX DMA

[Peter Stuge]

Paul Farrow wrote:
> Has any one got any suggestions how I might resolve this problem?

Get a different brand wifi card unless you have tools and experience
to debug this yourself.


//Peter

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/19/2012 07:36 PM, Paul Farrow wrote:
>
> Can any one confirm if they have a working AP with AR9280 card on
> Fedora 16?  I got the latest code base for hostapd and the ath9k driver
> and it appeared to work once but after that miracle it appears to error
> all the time.
> I tried to take a code base of about a year back but compiling that
> seems to have lots of dependency errors for the age of the kernel.
>
> Has any one got any suggestions how I might resolve this problem?

Well, I have a kernel that is well tested with the AR9380 NICs, at least.

If you want to try different kernels, please feel free to give it a
try:

http://dmz2.candelatech.com/git/?p=linux-3.0.dev.y/.git;a=summary

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Peter

Can you suggest a card?  Do you have a working card on Fedora 16 as an 
access point?

Cheers

Paul

On Fri, 20 Jan 2012 04:50:59 +0100, Peter Stuge wrote:
> Paul Farrow wrote:
>> Has any one got any suggestions how I might resolve this problem?
>
> Get a different brand wifi card unless you have tools and experience
> to debug this yourself.
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Ben

Thanks for getting back to me.  Are the AR9380's the ones to use for 
Access Point functionality?

I am a hobbyist when it comes to Linux stuff so please be gentle.  I am 
using a 64bit version of Fedora 16 at the moment, should I really be 
using the 32 bit version for it to work successfully.

Do your kernels have much modifications or are they just copies from 
kernel.org?

Cheers and thanks again

Paul

On Thu, 19 Jan 2012 21:30:17 -0800, Ben Greear wrote:
> On 01/19/2012 07:36 PM, Paul Farrow wrote:
>>
>> Can any one confirm if they have a working AP with AR9280 card on
>> Fedora 16?  I got the latest code base for hostapd and the ath9k 
>> driver
>> and it appeared to work once but after that miracle it appears to 
>> error
>> all the time.
>> I tried to take a code base of about a year back but compiling that
>> seems to have lots of dependency errors for the age of the kernel.
>>
>> Has any one got any suggestions how I might resolve this problem?
>
> Well, I have a kernel that is well tested with the AR9380 NICs, at 
> least.
>
> If you want to try different kernels, please feel free to give it a
> try:
>
> http://dmz2.candelatech.com/git/?p=linux-3.0.dev.y/.git;a=summary
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Mohammed Shafi]

Hi Paul,

On Fri, Jan 20, 2012 at 9:06 AM, Paul Farrow <ath9k@thefabfarrows.com> wrote:
>
> Can any one confirm if they have a working AP with AR9280 card on Fedora 16?

sorry for the very much delayed response
i have got ubuntu 11.10 64 bit on my x86 i could just try to use of hostapd.conf
and try to recreate it. this tx DMA is been for some time and i am not
sure it can be  immediately fix it. we are just addressing few
critical issues in ath9k STA mode.

> ?I got the latest code base for hostapd and the ath9k driver and it appeared
> to work once but after that miracle it appears to error all the time.
> I tried to take a code base of about a year back but compiling that seems to
> have lots of dependency errors for the age of the kernel.
>
> Has any one got any suggestions how I might resolve this problem?

>
> Thanks in advance
>
>
> Paul
>
> On Thu, 5 Jan 2012 12:16:31 +0530, Mohammed Shafi wrote:
>>
>> Hi Paul,
>>
>> sorry, i am into some critical tasks, i just could not analyze and
>> debug it now. will definitely take a look at this ASAP, also it
>> requires some good time to fix this.
>>
>> On Wed, Jan 4, 2012 at 7:57 PM, Paul Farrow <ath9k@thefabfarrows.com>
>> wrote:
>>>
>>>
>>> Hey Mohammed
>>>
>>> I hate to be on people especially as its an open source project but did I
>>> supply you everything that you might need to try to recreate the problem?
>>> ?Just want to make sure your not waiting on me :)
>>>
>>>
>>> Thanks again
>>>
>>> Paul
>>>
>>> On Fri, 30 Dec 2011 11:53:26 +0530, Mohammed Shafi wrote:
>>>>
>>>>
>>>> On Fri, Dec 30, 2011 at 4:01 AM, Paul Farrow <ath9k@thefabfarrows.com>
>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Adrian
>>>>>
>>>>> Just thinking about what you have asked me to do, does that mean that
>>>>> this card, driver and setup as an access point used to work??!!!! ?I
>>>>> wondered if it had ever worked.
>>>>
>>>>
>>>>
>>>> please post your hostapd.conf and which hostapd version you are using
>>>> hostapd -v ?
>>>> i can see if its recreatble quite easily. i have ubuntu machines here
>>>>
>>>>>
>>>>> Cheers & Happy New Year
>>>>
>>>>
>>>>
>>>> happy new year :)
>>>>>
>>>>>
>>>>>
>>>>> Paul
>>>>>
>>>>> On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
>>>>>>
>>>>>>
>>>>>> On 29 December 2011 06:10, Paul Farrow <ath9k@thefabfarrows.com>
>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi Adrian
>>>>>>>
>>>>>>> I believe !! ?I had a problem on FC14 using the wifi. ?After running
>>>>>>> a
>>>>>>> speedtest the whole machine would go incredibly slow but I must be
>>>>>>
>>>>>>
>>>>>>
>>>>>> It's quite possible that the errors were just hidden with FC14.
>>>>>>
>>>>>>> honest I didn't see anything being logged. ?So I took it upon myself
>>>>>>> to
>>>>>>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming to
>>>>>>> the
>>>>>>> console which I didn't in FC14. ?I then downloaded the latest source
>>>>>>> (compat wireless) and compiled and loaded per the compat-wireless
>>>>>>> instructions and I still see these errors (hopefully I did it
>>>>>>> correctly).
>>>>>>>
>>>>>>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. ?I am
>>>>>>> not
>>>>>>> sure how to get the PCI id? ?But here is the output from lspci.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Try passing -vvv to lspci. I think that gets it to dump everything
>>>>>> you need.
>>>>>>
>>>>>> So the right thing to do here is establish whether it was a problem
>>>>>> or
>>>>>> not with FC14. Are you able to find a compat-wireless version from
>>>>>> way
>>>>>> back in the FC14 days (ie, whatever roughly it was shipping with,
>>>>>> either as a package or whatever was in the kernel FC14 shipped with)
>>>>>> and build it on FC16? Once we've got that working (ie, slowdown but
>>>>>> no
>>>>>> console messages logged) we can try compiling it with debugging and
>>>>>> turning up the debugging. I can also go through and see what's
>>>>>> different between those two versions.
>>>>>>
>>>>>> Bah, I really wish bugzilla.kernel.org was actually working at this
>>>>>> point. I'd really like to give all these bugs to the ath9k guys and
>>>>>> see if we can get some lab time to investigate. Having it in bugzilla
>>>>>> would certainly make that easier to track.
>>>>>>
>>>>>>
>>>>>> Adrian
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> ath9k-devel mailing list
>>>>> ath9k-devel at lists.ath9k.org
>>>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>
>>>
>>>
>



-- 
shafi

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Mohammed

I read a post from a year back where someone was having the exact same 
problem as myself.  I would really like to find a solution to the 
problem as I don't want to have to buy a wifi access point and would 
like to use my linux box.

If you need anything else from me or any one else has a solution.   I 
am wondering if another card would even fix my problem as some people 
say it works and others say it doesn't looks like it could be another 
variable ie the motherboard.

Please let me know and thanks

Paul

On Fri, 20 Jan 2012 19:35:30 +0530, Mohammed Shafi wrote:
> Hi Paul,
>
> On Fri, Jan 20, 2012 at 9:06 AM, Paul Farrow 
> <ath9k@thefabfarrows.com> wrote:
>>
>> Can any one confirm if they have a working AP with AR9280 card on 
>> Fedora 16?
>
> sorry for the very much delayed response
> i have got ubuntu 11.10 64 bit on my x86 i could just try to use of
> hostapd.conf
> and try to recreate it. this tx DMA is been for some time and i am 
> not
> sure it can be  immediately fix it. we are just addressing few
> critical issues in ath9k STA mode.
>
>> ?I got the latest code base for hostapd and the ath9k driver and it 
>> appeared
>> to work once but after that miracle it appears to error all the 
>> time.
>> I tried to take a code base of about a year back but compiling that 
>> seems to
>> have lots of dependency errors for the age of the kernel.
>>
>> Has any one got any suggestions how I might resolve this problem?
>
>>
>> Thanks in advance
>>
>>
>> Paul
>>
>> On Thu, 5 Jan 2012 12:16:31 +0530, Mohammed Shafi wrote:
>>>
>>> Hi Paul,
>>>
>>> sorry, i am into some critical tasks, i just could not analyze and
>>> debug it now. will definitely take a look at this ASAP, also it
>>> requires some good time to fix this.
>>>
>>> On Wed, Jan 4, 2012 at 7:57 PM, Paul Farrow 
>>> <ath9k@thefabfarrows.com>
>>> wrote:
>>>>
>>>>
>>>> Hey Mohammed
>>>>
>>>> I hate to be on people especially as its an open source project 
>>>> but did I
>>>> supply you everything that you might need to try to recreate the 
>>>> problem?
>>>> ?Just want to make sure your not waiting on me :)
>>>>
>>>>
>>>> Thanks again
>>>>
>>>> Paul
>>>>
>>>> On Fri, 30 Dec 2011 11:53:26 +0530, Mohammed Shafi wrote:
>>>>>
>>>>>
>>>>> On Fri, Dec 30, 2011 at 4:01 AM, Paul Farrow 
>>>>> <ath9k@thefabfarrows.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> Adrian
>>>>>>
>>>>>> Just thinking about what you have asked me to do, does that mean 
>>>>>> that
>>>>>> this card, driver and setup as an access point used to 
>>>>>> work??!!!! ?I
>>>>>> wondered if it had ever worked.
>>>>>
>>>>>
>>>>>
>>>>> please post your hostapd.conf and which hostapd version you are 
>>>>> using
>>>>> hostapd -v ?
>>>>> i can see if its recreatble quite easily. i have ubuntu machines 
>>>>> here
>>>>>
>>>>>>
>>>>>> Cheers & Happy New Year
>>>>>
>>>>>
>>>>>
>>>>> happy new year :)
>>>>>>
>>>>>>
>>>>>>
>>>>>> Paul
>>>>>>
>>>>>> On Thu, 29 Dec 2011 12:34:08 -0800, Adrian Chadd wrote:
>>>>>>>
>>>>>>>
>>>>>>> On 29 December 2011 06:10, Paul Farrow 
>>>>>>> <ath9k@thefabfarrows.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi Adrian
>>>>>>>>
>>>>>>>> I believe !! ?I had a problem on FC14 using the wifi. ?After 
>>>>>>>> running
>>>>>>>> a
>>>>>>>> speedtest the whole machine would go incredibly slow but I 
>>>>>>>> must be
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> It's quite possible that the errors were just hidden with FC14.
>>>>>>>
>>>>>>>> honest I didn't see anything being logged. ?So I took it upon 
>>>>>>>> myself
>>>>>>>> to
>>>>>>>> upgrade. ?Once upgraded to Fedora 16 I saw these errors coming 
>>>>>>>> to
>>>>>>>> the
>>>>>>>> console which I didn't in FC14. ?I then downloaded the latest 
>>>>>>>> source
>>>>>>>> (compat wireless) and compiled and loaded per the 
>>>>>>>> compat-wireless
>>>>>>>> instructions and I still see these errors (hopefully I did it
>>>>>>>> correctly).
>>>>>>>>
>>>>>>>> This is a PICe AR9280 NIC on a Jetaway NF93R intel duo board. 
>>>>>>>> ?I am
>>>>>>>> not
>>>>>>>> sure how to get the PCI id? ?But here is the output from 
>>>>>>>> lspci.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Try passing -vvv to lspci. I think that gets it to dump 
>>>>>>> everything
>>>>>>> you need.
>>>>>>>
>>>>>>> So the right thing to do here is establish whether it was a 
>>>>>>> problem
>>>>>>> or
>>>>>>> not with FC14. Are you able to find a compat-wireless version 
>>>>>>> from
>>>>>>> way
>>>>>>> back in the FC14 days (ie, whatever roughly it was shipping 
>>>>>>> with,
>>>>>>> either as a package or whatever was in the kernel FC14 shipped 
>>>>>>> with)
>>>>>>> and build it on FC16? Once we've got that working (ie, slowdown 
>>>>>>> but
>>>>>>> no
>>>>>>> console messages logged) we can try compiling it with debugging 
>>>>>>> and
>>>>>>> turning up the debugging. I can also go through and see what's
>>>>>>> different between those two versions.
>>>>>>>
>>>>>>> Bah, I really wish bugzilla.kernel.org was actually working at 
>>>>>>> this
>>>>>>> point. I'd really like to give all these bugs to the ath9k guys 
>>>>>>> and
>>>>>>> see if we can get some lab time to investigate. Having it in 
>>>>>>> bugzilla
>>>>>>> would certainly make that easier to track.
>>>>>>>
>>>>>>>
>>>>>>> Adrian
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> ath9k-devel mailing list
>>>>>> ath9k-devel at lists.ath9k.org
>>>>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>>>
>>>>
>>>>
>>

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/20/2012 05:25 AM, Paul Farrow wrote:
>
> Hi Ben
>
> Thanks for getting back to me. Are the AR9380's the ones to use for Access Point functionality?

We use them mostly for client mode, but we do test them as access points as well.
I've only tested 32-bit kernels in AP mode, but 64-bit and 32-bit kernels in station
mode.  Will be testing 64-bit AP mode shortly.

>
> I am a hobbyist when it comes to Linux stuff so please be gentle. I am using a 64bit version of Fedora 16 at the moment, should I really be using the 32 bit
> version for it to work successfully.
>
> Do your kernels have much modifications or are they just copies from kernel.org?

It has some modifications..but nothing very significant for AP mode,
as far as I know.  It does have all of the stable patches applied, which
may help.

You may still see problems, and if you do, please let me know.  Not sure
I can fix anything, but post your hostapd conf file and such and I'll
see if we can reproduce the problem at least.  I have a couple of older
ath9k NICs lying around, maybe some with your chipset.

We also run with nohwcrypt enabled, so possibly that has some impact on
stability.

Thanks,
Ben


>
> Cheers and thanks again
>
> Paul
>
> On Thu, 19 Jan 2012 21:30:17 -0800, Ben Greear wrote:
>> On 01/19/2012 07:36 PM, Paul Farrow wrote:
>>>
>>> Can any one confirm if they have a working AP with AR9280 card on
>>> Fedora 16? I got the latest code base for hostapd and the ath9k driver
>>> and it appeared to work once but after that miracle it appears to error
>>> all the time.
>>> I tried to take a code base of about a year back but compiling that
>>> seems to have lots of dependency errors for the age of the kernel.
>>>
>>> Has any one got any suggestions how I might resolve this problem?
>>
>> Well, I have a kernel that is well tested with the AR9380 NICs, at least.
>>
>> If you want to try different kernels, please feel free to give it a
>> try:
>>
>> http://dmz2.candelatech.com/git/?p=linux-3.0.dev.y/.git;a=summary
>>
>> Thanks,
>> Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Adrian Chadd]

Is someone able to help me reliably replicate this behaviour?

If I can replicate it, I'll see if I can book some lab time and diagnose it.

(I can't replicate that kind of issue reliably under FreeBSD, so I can't
just drag my existing kit in..)


Adrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120120/bc1a61f1/attachment.htm 

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/20/2012 12:09 PM, Adrian Chadd wrote:
>
> Is someone able to help me reliably replicate this behaviour?

I only occasionally see these errors in my setups, and they don't
seem to cause problems when I do, so I'm not sure how to reliably
reproduce it.

Hopefully the folks that can will (re)post their hostapd.conf and other
pertinent info and I can at least see if it works on my systems...

> If I can replicate it, I'll see if I can book some lab time and diagnose it.
>
> (I can't replicate that kind of issue reliably under FreeBSD, so I can't just drag my existing kit in..)
>
>
> Adrian

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Ben

Thanks for replying and offering to try it on your machine.  Perhaps 
the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
  - not sure.  I have attached hostapd.conf and lspci for your 
information.

Hostapd I have used version 0.73 from the distribution and I have used 
also used the latest development source branch.

hostapd v2.0-devel
User space daemon for IEEE 802.11 AP management,
IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
Copyright (c) 2002-2012, Jouni Malinen <j@w1.fi> and contributors

I also compiled the latest ath9k device but all produce the dma errors 
to the terminal.

When I run hostapd I get a wlan0.mon interface - I take it that is 
normal.

Also the ONE time it seemed to work I used the latest source code I 
selected the driver as ath9k_htc, not sure if that was the trick or just 
fluke as I couldn't get it to work again.

Thanks for trying

Paul

On Fri, 20 Jan 2012 09:03:39 -0800, Ben Greear wrote:
> On 01/20/2012 05:25 AM, Paul Farrow wrote:
>>
>> Hi Ben
>>
>> Thanks for getting back to me. Are the AR9380's the ones to use for 
>> Access Point functionality?
>
> We use them mostly for client mode, but we do test them as access
> points as well.
> I've only tested 32-bit kernels in AP mode, but 64-bit and 32-bit
> kernels in station
> mode.  Will be testing 64-bit AP mode shortly.
>
>>
>> I am a hobbyist when it comes to Linux stuff so please be gentle. I 
>> am using a 64bit version of Fedora 16 at the moment, should I really 
>> be using the 32 bit
>> version for it to work successfully.
>>
>> Do your kernels have much modifications or are they just copies from 
>> kernel.org?
>
> It has some modifications..but nothing very significant for AP mode,
> as far as I know.  It does have all of the stable patches applied, 
> which
> may help.
>
> You may still see problems, and if you do, please let me know.  Not 
> sure
> I can fix anything, but post your hostapd conf file and such and I'll
> see if we can reproduce the problem at least.  I have a couple of 
> older
> ath9k NICs lying around, maybe some with your chipset.
>
> We also run with nohwcrypt enabled, so possibly that has some impact 
> on
> stability.
>
> Thanks,
> Ben
>
>
>>
>> Cheers and thanks again
>>
>> Paul
>>
>> On Thu, 19 Jan 2012 21:30:17 -0800, Ben Greear wrote:
>>> On 01/19/2012 07:36 PM, Paul Farrow wrote:
>>>>
>>>> Can any one confirm if they have a working AP with AR9280 card on
>>>> Fedora 16? I got the latest code base for hostapd and the ath9k 
>>>> driver
>>>> and it appeared to work once but after that miracle it appears to 
>>>> error
>>>> all the time.
>>>> I tried to take a code base of about a year back but compiling 
>>>> that
>>>> seems to have lots of dependency errors for the age of the kernel.
>>>>
>>>> Has any one got any suggestions how I might resolve this problem?
>>>
>>> Well, I have a kernel that is well tested with the AR9380 NICs, at 
>>> least.
>>>
>>> If you want to try different kernels, please feel free to give it a
>>> try:
>>>
>>> http://dmz2.candelatech.com/git/?p=linux-3.0.dev.y/.git;a=summary
>>>
>>> Thanks,
>>> Ben
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lspci.txt
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120123/a22fadac/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: hostapd.conf
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120123/a22fadac/attachment-0001.txt 

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Whats really odd was that the time that I selected that driver 
(ath9k_htc) and recompiled the code was the time that it appeared to 
work.  Perhaps what I really did was selected the driver as ath9k_htc 
and recompiled but then modprobe'd the old ath9k object from the 
compilation before this one.

As I said I am Linux hobbyist and tried many things to get this to work 
so it could be my failing memory (brain power) and I actually forgot the 
correct chain of events.

I would like to add about this problem that my wifi clients are an 
android phone and a intel duo macbook pro.  The way that I replicate the 
problem is that I just run speedtest.net and it happens straight away 
every time so not sure if its a load problem or what.

Thanks to any one that can figure this problem out.  Looking back 
through the newsgroup it would have been happening since late 2010 so it 
would be nice to get to the bottom of it.

Cheers

Paul

On Mon, 23 Jan 2012 18:56:07 +0530, Mohammed Shafi wrote:
> On Mon, Jan 23, 2012 at 6:48 PM, Paul Farrow 
> <ath9k@thefabfarrows.com> wrote:
>> Hi Ben
>>
>> Thanks for replying and offering to try it on your machine. ?Perhaps 
>> the
>> trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
>> ?- not sure. ?I have attached hostapd.conf and lspci for your 
>> information.
>>
>> Hostapd I have used version 0.73 from the distribution and I have 
>> used also
>> used the latest development source branch.
>>
>> hostapd v2.0-devel
>>
>> User space daemon for IEEE 802.11 AP management,
>> IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator
>> Copyright (c) 2002-2012, Jouni Malinen <j@w1.fi> and contributors
>>
>> I also compiled the latest ath9k device but all produce the dma 
>> errors to
>> the terminal.
>>
>> When I run hostapd I get a wlan0.mon interface - I take it that is 
>> normal.
>>
>> Also the ONE time it seemed to work I used the latest source code I 
>> selected
>> the driver as ath9k_htc, not sure if that was the trick or just 
>> fluke as I
>> couldn't get it to work again.
>
> ath9k_htc is for USB chipsets and ath9k PCI chipsets, so please don't
> select ath9k_htc
> http://linuxwireless.org/en/users/Drivers/ath9k_htc
>
>>
>> Thanks for trying
>>
>> Paul
>>
>>
>> On Fri, 20 Jan 2012 09:03:39 -0800, Ben Greear wrote:
>>>
>>> On 01/20/2012 05:25 AM, Paul Farrow wrote:
>>>>
>>>>
>>>> Hi Ben
>>>>
>>>> Thanks for getting back to me. Are the AR9380's the ones to use 
>>>> for
>>>> Access Point functionality?
>>>
>>>
>>> We use them mostly for client mode, but we do test them as access
>>> points as well.
>>> I've only tested 32-bit kernels in AP mode, but 64-bit and 32-bit
>>> kernels in station
>>> mode. ?Will be testing 64-bit AP mode shortly.
>>>
>>>>
>>>> I am a hobbyist when it comes to Linux stuff so please be gentle. 
>>>> I am
>>>> using a 64bit version of Fedora 16 at the moment, should I really 
>>>> be using
>>>> the 32 bit
>>>> version for it to work successfully.
>>>>
>>>> Do your kernels have much modifications or are they just copies 
>>>> from
>>>> kernel.org?
>>>
>>>
>>> It has some modifications..but nothing very significant for AP 
>>> mode,
>>> as far as I know. ?It does have all of the stable patches applied, 
>>> which
>>> may help.
>>>
>>> You may still see problems, and if you do, please let me know. ?Not 
>>> sure
>>> I can fix anything, but post your hostapd conf file and such and 
>>> I'll
>>> see if we can reproduce the problem at least. ?I have a couple of 
>>> older
>>> ath9k NICs lying around, maybe some with your chipset.
>>>
>>> We also run with nohwcrypt enabled, so possibly that has some 
>>> impact on
>>> stability.
>>>
>>> Thanks,
>>> Ben
>>>
>>>
>>>>
>>>> Cheers and thanks again
>>>>
>>>> Paul
>>>>
>>>> On Thu, 19 Jan 2012 21:30:17 -0800, Ben Greear wrote:
>>>>>
>>>>> On 01/19/2012 07:36 PM, Paul Farrow wrote:
>>>>>>
>>>>>>
>>>>>> Can any one confirm if they have a working AP with AR9280 card 
>>>>>> on
>>>>>> Fedora 16? I got the latest code base for hostapd and the ath9k 
>>>>>> driver
>>>>>> and it appeared to work once but after that miracle it appears 
>>>>>> to error
>>>>>> all the time.
>>>>>> I tried to take a code base of about a year back but compiling 
>>>>>> that
>>>>>> seems to have lots of dependency errors for the age of the 
>>>>>> kernel.
>>>>>>
>>>>>> Has any one got any suggestions how I might resolve this 
>>>>>> problem?
>>>>>
>>>>>
>>>>> Well, I have a kernel that is well tested with the AR9380 NICs, 
>>>>> at
>>>>> least.
>>>>>
>>>>> If you want to try different kernels, please feel free to give it 
>>>>> a
>>>>> try:
>>>>>
>>>>> http://dmz2.candelatech.com/git/?p=linux-3.0.dev.y/.git;a=summary
>>>>>
>>>>> Thanks,
>>>>> Ben

[ath9k-devel] Failed to stop TX DMA

[Peter Stuge]

Hi Paul,

Paul Farrow wrote:
> The way that I replicate the problem is that I just run
> speedtest.net and it happens straight away every time so not sure
> if its a load problem or what.

What can you say about the PC you're using the card in?

Indeed I have never had reliable high throughput with any ath9k, but
I have not tried with AR93xx cards yet.


> Thanks to any one that can figure this problem out.  Looking back 
> through the newsgroup it would have been happening since late 2010
> so it would be nice to get to the bottom of it.

Doing so may require quite advanced equipment analyzing what is going
on inside the PC.


//Peter

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

The PC is a Jetaway NF93R with a Intel DUO P8700 @ 2.53Ghz, the PCI 
slot is empty and the AR9280 card is in the pci-e slot.

Attached lspci output as before.

On Mon, 23 Jan 2012 15:01:23 +0100, Peter Stuge wrote:
> Hi Paul,
>
> Paul Farrow wrote:
>> The way that I replicate the problem is that I just run
>> speedtest.net and it happens straight away every time so not sure
>> if its a load problem or what.
>
> What can you say about the PC you're using the card in?
>
> Indeed I have never had reliable high throughput with any ath9k, but
> I have not tried with AR93xx cards yet.
>
>
>> Thanks to any one that can figure this problem out.  Looking back
>> through the newsgroup it would have been happening since late 2010
>> so it would be nice to get to the bottom of it.
>
> Doing so may require quite advanced equipment analyzing what is going
> on inside the PC.
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lspci.txt
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120123/c4194c14/attachment.txt 

[ath9k-devel] Failed to stop TX DMA

[Peter Stuge]

Paul Farrow wrote:
> The PC is a Jetaway NF93R with a Intel DUO P8700 @ 2.53Ghz, the
> PCI slot is empty and the AR9280 card is in the pci-e slot.

Does the BIOS have any PCIe settings you could experiment with?

Anything about clocks or frequencies would be an obvious start.


//Peter

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

I can certainly look this evening to see if there is anything.

On Mon, 23 Jan 2012 15:29:22 +0100, Peter Stuge wrote:
> Paul Farrow wrote:
>> The PC is a Jetaway NF93R with a Intel DUO P8700 @ 2.53Ghz, the
>> PCI slot is empty and the AR9280 card is in the pci-e slot.
>
> Does the BIOS have any PCIe settings you could experiment with?
>
> Anything about clocks or frequencies would be an obvious start.
>
>
> //Peter
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/23/2012 05:18 AM, Paul Farrow wrote:
> Hi Ben
>
> Thanks for replying and offering to try it on your machine. Perhaps the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
> - not sure. I have attached hostapd.conf and lspci for your information.

Can you try my kernel first?

http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.0.dev.y/.git;a=summary


You see the problem when you test either with your Android or Macbook,
or just some specific combination?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Ben

Can you give me instructions on how I can use that link to install that 
kernel without losing the ones I have currently installed under a grub2 
config ?  Maybe build to a DVD or something !!, did I mention that I was 
a hobbyist not a professional Linux programmer :)

The Android and Macbook are my personal machines I have.  My son has an 
ipod touch which I haven't tried.  I could also borrow my work PC to try 
but I suspect that would still do it.  I had that on my this machine 
back a few distributions (Fedora 14) and it just hung and didn't output 
anything to the terminal when connected via the wireless - I suspect it 
was the same problem but just didn't tell me how it does on the latest 
distribution Fedora 16.

Thanks

Paul

On Mon, 23 Jan 2012 11:08:09 -0800, Ben Greear wrote:
> On 01/23/2012 05:18 AM, Paul Farrow wrote:
>> Hi Ben
>>
>> Thanks for replying and offering to try it on your machine. Perhaps 
>> the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
>> - not sure. I have attached hostapd.conf and lspci for your 
>> information.
>
> Can you try my kernel first?
>
> 
> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.0.dev.y/.git;a=summary
>
>
> You see the problem when you test either with your Android or 
> Macbook,
> or just some specific combination?
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Ben ignore that request on instructions, was having trouble with GIT 
with your url but have sorted out how I get it.  Just give me time :) 
and hopefully I will have built your 3.0 kernel to test with.  I take it 
that has the ath9k driver built into it?

I also don't think I was that clear on your Android Mac question.  
Basically if I use either the Mac or Android in any combination I get 
the DMA errors and pretty much straight away from connecting and running 
the test from speedtest.net or the application (on the Android phone).

Cheers

Paul

On Mon, 23 Jan 2012 11:08:09 -0800, Ben Greear wrote:
> On 01/23/2012 05:18 AM, Paul Farrow wrote:
>> Hi Ben
>>
>> Thanks for replying and offering to try it on your machine. Perhaps 
>> the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
>> - not sure. I have attached hostapd.conf and lspci for your 
>> information.
>
> Can you try my kernel first?
>
> 
> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.0.dev.y/.git;a=summary
>
>
> You see the problem when you test either with your Android or 
> Macbook,
> or just some specific combination?
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/23/2012 12:57 PM, Paul Farrow wrote:
>
> Ben ignore that request on instructions, was having trouble with GIT with your url but have sorted out how I get it. Just give me time :) and hopefully I will
> have built your 3.0 kernel to test with. I take it that has the ath9k driver built into it?

That's up to the kernel config you use.  You can find my 64-bit config file in
the git repository: [repo]/configs/ct-x64.cfg

Please use my config file or something similar.

> I also don't think I was that clear on your Android Mac question. Basically if I use either the Mac or Android in any combination I get the DMA errors and
> pretty much straight away from connecting and running the test from speedtest.net or the application (on the Android phone).

Ok, sounds like the problem is not related to a specific client.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Ben

I used make oldconfig which I guess just uses the config of my latest 
distribution kernel, if I want to use your 64 bit config how would I go 
about that?  Eventually it built on my little old DUO but when I did 
"make install" it threw errors with accessing some of my volumes.  I 
think because my volume names have spaces in them !!  Will try to rename 
my volumes and do it again over the next few nights.

Will let you know how it goes.

Thanks again

Paul

On Mon, 23 Jan 2012 16:40:43 -0800, Ben Greear wrote:
> On 01/23/2012 12:57 PM, Paul Farrow wrote:
>>
>> Ben ignore that request on instructions, was having trouble with GIT 
>> with your url but have sorted out how I get it. Just give me time :) 
>> and hopefully I will
>> have built your 3.0 kernel to test with. I take it that has the 
>> ath9k driver built into it?
>
> That's up to the kernel config you use.  You can find my 64-bit
> config file in
> the git repository: [repo]/configs/ct-x64.cfg
>
> Please use my config file or something similar.
>
>> I also don't think I was that clear on your Android Mac question. 
>> Basically if I use either the Mac or Android in any combination I get 
>> the DMA errors and
>> pretty much straight away from connecting and running the test from 
>> speedtest.net or the application (on the Android phone).
>
> Ok, sounds like the problem is not related to a specific client.
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/24/2012 05:04 AM, Paul Farrow wrote:
>
> Hi Ben
>
> I used make oldconfig which I guess just uses the config of my latest distribution kernel, if I want to use your 64 bit config how would I go about that?
> Eventually it built on my little old DUO but when I did "make install" it threw errors with accessing some of my volumes. I think because my volume names have
> spaces in them !! Will try to rename my volumes and do it again over the next few nights.
>
> Will let you know how it goes.

Copy the ct-x64.cfg over the .config file, then 'make oldconfig' and rebuild.

The 'make install', 'make modules_install' and so forth shouldn't be any
different from normal kernels...my patches are mostly just related to
networking.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Ben

Thanks for the info on .config will do that once I have installed 
something of yours.

For some reason (and this is the first time I have installed a kernel 
from source) unrelated to the wireless issue, since Fedora 16 my raid 
drives are mapped to a name which has spaces in it and I think this is 
the problem the make install can't find the drives to install the kernel 
on.  Once I have sorted that problem out I will be good to go.

Cheers

Paul

On Tue, 24 Jan 2012 09:26:39 -0800, Ben Greear wrote:
> On 01/24/2012 05:04 AM, Paul Farrow wrote:
>>
>> Hi Ben
>>
>> I used make oldconfig which I guess just uses the config of my 
>> latest distribution kernel, if I want to use your 64 bit config how 
>> would I go about that?
>> Eventually it built on my little old DUO but when I did "make 
>> install" it threw errors with accessing some of my volumes. I think 
>> because my volume names have
>> spaces in them !! Will try to rename my volumes and do it again over 
>> the next few nights.
>>
>> Will let you know how it goes.
>
> Copy the ct-x64.cfg over the .config file, then 'make oldconfig' and 
> rebuild.
>
> The 'make install', 'make modules_install' and so forth shouldn't be 
> any
> different from normal kernels...my patches are mostly just related to
> networking.
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Ben

I finally booted into your kernel which was built using my own .config 
from original Fedora 16 and it didn't recognise the wifi card - iwconfig 
does not bring anything up like it used to.  I kinda thought it was 
going to be included in the kernel, do I need to compile the ath9k 
module and load it?

Thanks

Paul



On Tue, 24 Jan 2012 09:26:39 -0800, Ben Greear wrote:
> On 01/24/2012 05:04 AM, Paul Farrow wrote:
>>
>> Hi Ben
>>
>> I used make oldconfig which I guess just uses the config of my 
>> latest distribution kernel, if I want to use your 64 bit config how 
>> would I go about that?
>> Eventually it built on my little old DUO but when I did "make 
>> install" it threw errors with accessing some of my volumes. I think 
>> because my volume names have
>> spaces in them !! Will try to rename my volumes and do it again over 
>> the next few nights.
>>
>> Will let you know how it goes.
>
> Copy the ct-x64.cfg over the .config file, then 'make oldconfig' and 
> rebuild.
>
> The 'make install', 'make modules_install' and so forth shouldn't be 
> any
> different from normal kernels...my patches are mostly just related to
> networking.
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/25/2012 05:22 PM, Paul Farrow wrote:
>
> Hi Ben
>
> I finally booted into your kernel which was built using my own .config from original Fedora 16 and it didn't recognise the wifi card - iwconfig does not bring
> anything up like it used to. I kinda thought it was going to be included in the kernel, do I need to compile the ath9k module and load it?

Do any modules load?  Did you run 'make modules_install' ?

Plz send the results of 'lsmod' and 'lspci' and 'uname -a' when you
have booted into the new kernel.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Ok Ben

I did do a uname -r and it did appear to have the right kernel.  I 
think if its ok with you that I will just talk to you direct until I can 
get your kernel in, building kernels etc is not really a thing for this 
group and as I said I am a linux hobbyist so more than likely I have 
done something wrong around compiling your kernel source :)

I can try again tonight and do the lsmod just to make sure I have 
everything loaded.

Will let you know and thanks again for the help

Paul

On Wed, 25 Jan 2012 19:14:46 -0800, Ben Greear wrote:
> On 01/25/2012 05:22 PM, Paul Farrow wrote:
>>
>> Hi Ben
>>
>> I finally booted into your kernel which was built using my own 
>> .config from original Fedora 16 and it didn't recognise the wifi card 
>> - iwconfig does not bring
>> anything up like it used to. I kinda thought it was going to be 
>> included in the kernel, do I need to compile the ath9k module and load 
>> it?
>
> Do any modules load?  Did you run 'make modules_install' ?
>
> Plz send the results of 'lsmod' and 'lspci' and 'uname -a' when you
> have booted into the new kernel.
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Sune Mølgaard]

Ben Greear wrote:
> On 01/23/2012 05:18 AM, Paul Farrow wrote:
>> Hi Ben
>>
>> Thanks for replying and offering to try it on your machine. Perhaps the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
>> - not sure. I have attached hostapd.conf and lspci for your information.
>
> Can you try my kernel first?
>
> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.0.dev.y/.git;a=summary
>
>
> You see the problem when you test either with your Android or Macbook,
> or just some specific combination?
>
> Thanks,
> Ben
>

I seem to be hit by this as well. My machine is rather old, and I'm 
quite busy today, but I will start a build now and test it later.

What did you want to know when it's running?

Best regards,

Sune M?lgaard

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/27/2012 03:47 AM, Sune M?lgaard wrote:
> Ben Greear wrote:
>> On 01/23/2012 05:18 AM, Paul Farrow wrote:
>>> Hi Ben
>>>
>>> Thanks for replying and offering to try it on your machine. Perhaps the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
>>> - not sure. I have attached hostapd.conf and lspci for your information.
>>
>> Can you try my kernel first?
>>
>> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.0.dev.y/.git;a=summary
>>
>>
>> You see the problem when you test either with your Android or Macbook,
>> or just some specific combination?
>>
>> Thanks,
>> Ben
>>
>
> I seem to be hit by this as well. My machine is rather old, and I'm quite busy today, but I will start a build now and test it later.
>
> What did you want to know when it's running?

If you hit the problem on my kernel, please send me a full bug report (kernel splat, 'lspci', brief
description of how you caused the problem, how reproducible it is, etc).

I can't promise I can fix it, but I will definitely take a good look at it
and will try to reproduce the problem on my systems.  If we can ever find
a way to reliably reproduce these problems, then the ath9k developers will
have a much easier time fixing the problem.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Sune Mølgaard]

Ben Greear wrote:
> On 01/27/2012 03:47 AM, Sune M?lgaard wrote:
>> Ben Greear wrote:
>>> On 01/23/2012 05:18 AM, Paul Farrow wrote:
>>>> Hi Ben
>>>>
>>>> Thanks for replying and offering to try it on your machine. Perhaps
>>>> the trick is the 64 bit kernel (3.1.9-1.fc16.x86_64.debug)
>>>> - not sure. I have attached hostapd.conf and lspci for your
>>>> information.
>>>
>>> Can you try my kernel first?
>>>
>>> http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.0.dev.y/.git;a=summary
>>>
>>>
>>>
>>> You see the problem when you test either with your Android or Macbook,
>>> or just some specific combination?
>>>
>>> Thanks,
>>> Ben
>>>
>>
>> I seem to be hit by this as well. My machine is rather old, and I'm
>> quite busy today, but I will start a build now and test it later.
>>
>> What did you want to know when it's running?
>
> If you hit the problem on my kernel, please send me a full bug report
> (kernel splat, 'lspci', brief
> description of how you caused the problem, how reproducible it is, etc).
>
> I can't promise I can fix it, but I will definitely take a good look at it
> and will try to reproduce the problem on my systems. If we can ever find
> a way to reliably reproduce these problems, then the ath9k developers will
> have a much easier time fixing the problem.
>
> Thanks,
> Ben
>

Attached. I even hit it with WMM and 11n disabled.

I hit it with high speeds occurring - it took 5 cycles of hostapd for 
the syslog file to be scp'ed over (the complete file was 24Mb, though).

Best regards,

Sune
-------------- next part --------------
3>ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
br0: port 3(wlan0) entering forwarding state
net_ratelimit: 2 callbacks suppressed
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
ath: received PCI FATAL interrupt
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
br0: port 3(wlan0) entering forwarding state
ath: received PCI FATAL interrupt
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
ieee80211 phy0: Allocated STA f8:db:7f:de:53:72
ieee80211 phy0: Inserted STA f8:db:7f:de:53:72
ieee80211 phy0: Removed STA f8:db:7f:de:53:72
ieee80211 phy0: Destroyed STA f8:db:7f:de:53:72
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
ath: received PCI FATAL interrupt
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
br0: port 3(wlan0) entering forwarding state
ath: received PCI FATAL interrupt
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
br0: port 3(wlan0) entering forwarding state
ath: received PCI FATAL interrupt
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
br0: port 3(wlan0) entering forwarding state
ath: received PCI FATAL interrupt
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00024040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
device wlan0 left promiscuous mode
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: device now idle
ath: Failed to stop TX DMA!
ath: Failed to stop TX DMA!
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ieee80211 phy0: device no longer idle - in use
device wlan0 entered promiscuous mode
br0: port 3(wlan0) entering forwarding state
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Allocated STA f8:db:7f:de:53:72
ieee80211 phy0: Inserted STA f8:db:7f:de:53:72
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
br0: port 3(wlan0) entering forwarding state
ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
net_ratelimit: 3 callbacks suppressed
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
-------------- next part --------------
00:00.0 Host bridge: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge
	Subsystem: VIA Technologies, Inc. VT8375 [KM266/KL266] Host Bridge
	Flags: bus master, 66MHz, medium devsel, latency 8
	Memory at d0000000 (32-bit, prefetchable) [size=128M]
	Capabilities: <access denied>
	Kernel driver in use: agpgart-via

00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	Memory behind bridge: e0000000-e1ffffff
	Prefetchable memory behind bridge: d8000000-dfffffff
	Capabilities: <access denied>

00:05.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02)
	Subsystem: Silicon Image, Inc. Device 7114
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16
	I/O ports at 9000 [size=8]
	I/O ports at 9400 [size=4]
	I/O ports at 9800 [size=8]
	I/O ports at 9c00 [size=4]
	I/O ports at a000 [size=16]
	Memory at e3010000 (32-bit, non-prefetchable) [size=1K]
	[virtual] Expansion ROM at 80000000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: sata_sil
	Kernel modules: sata_sil

00:06.0 Network controller: Atheros Communications Inc. AR922X Wireless Network Adapter (rev 01)
	Subsystem: D-Link System Inc Device 3a7c
	Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 17
	Memory at e3000000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: ath9k
	Kernel modules: ath9k

00:07.0 Ethernet controller: Sundance Technology Inc / IC Plus Corp IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY (rev 31)
	Subsystem: Sundance Technology Inc / IC Plus Corp Device 0201
	Flags: bus master, medium devsel, latency 32, IRQ 18
	I/O ports at a400 [size=128]
	Memory at e3011000 (32-bit, non-prefetchable) [size=512]
	[virtual] Expansion ROM at 80080000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: sundance
	Kernel modules: sundance

00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
	Subsystem: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
	Flags: bus master, medium devsel, latency 32, IRQ 17
	I/O ports at a800 [size=256]
	Memory at e3012000 (32-bit, non-prefetchable) [size=256]
	[virtual] Expansion ROM at 80090000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: 8139too
	Kernel modules: 8139too, 8139cp

00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
	Subsystem: VIA Technologies, Inc. Device 3074
	Flags: bus master, stepping, medium devsel, latency 0
	Capabilities: <access denied>
	Kernel modules: i2c-viapro, via-ircc

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE
	Flags: bus master, medium devsel, latency 32, IRQ 23
	[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
	[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
	I/O ports at ac00 [size=16]
	Capabilities: <access denied>
	Kernel driver in use: pata_via
	Kernel modules: pata_via

00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) (prog-if 00 [UHCI])
	Subsystem: First International Computer, Inc. VA-502 Mainboard
	Flags: bus master, medium devsel, latency 32, IRQ 21
	I/O ports at b000 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) (prog-if 00 [UHCI])
	Subsystem: First International Computer, Inc. VA-502 Mainboard
	Flags: bus master, medium devsel, latency 32, IRQ 21
	I/O ports at b400 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 40)
	Subsystem: Micro-Star International Co., Ltd. Device 3900
	Flags: medium devsel, IRQ 22
	I/O ports at b800 [size=256]
	Capabilities: <access denied>
	Kernel driver in use: VIA 82xx Audio
	Kernel modules: snd-via82xx

01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] (prog-if 00 [VGA controller])
	Subsystem: Micro-Star International Co., Ltd. Device 3908
	Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
	Memory at e1000000 (32-bit, non-prefetchable) [size=512K]
	Memory at d8000000 (32-bit, prefetchable) [size=128M]
	[virtual] Expansion ROM at e0000000 [disabled] [size=64K]
	Capabilities: <access denied>
	Kernel modules: savagefb

-------------- next part --------------
Jan 27 18:51:35 jadis rsyslogd: connot create '/var/spool/postfix/dev/log': No such file or directory
Jan 27 18:51:35 jadis kernel: imklog 5.8.1, log source = /proc/kmsg started.
Jan 27 18:51:35 jadis rsyslogd: [origin software="rsyslogd" swVersion="5.8.1" x-pid="1260" x-info="http://www.rsyslog.com"] start
Jan 27 18:51:35 jadis rsyslogd: rsyslogd's groupid changed to 102
Jan 27 18:51:35 jadis rsyslogd: rsyslogd's userid changed to 101
Jan 27 18:51:35 jadis rsyslogd-2039: Could no open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys cpuset
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys cpu
Jan 27 18:51:35 jadis kernel: Linux version 3.0.18-sune-1 (sune at jadis) (gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ) #3 SMP Fri Jan 27 17:40:57 CET 2012
Jan 27 18:51:35 jadis kernel: KERNEL supported cpus:
Jan 27 18:51:35 jadis kernel:  Intel GenuineIntel
Jan 27 18:51:35 jadis kernel:  AMD AuthenticAMD
Jan 27 18:51:35 jadis kernel:  NSC Geode by NSC
Jan 27 18:51:35 jadis kernel:  Cyrix CyrixInstead
Jan 27 18:51:35 jadis kernel:  Centaur CentaurHauls
Jan 27 18:51:35 jadis kernel:  Transmeta GenuineTMx86
Jan 27 18:51:35 jadis kernel:  Transmeta TransmetaCPU
Jan 27 18:51:35 jadis kernel:  UMC UMC UMC UMC
Jan 27 18:51:35 jadis kernel: BIOS-provided physical RAM map:
Jan 27 18:51:35 jadis kernel: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
Jan 27 18:51:35 jadis kernel: BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Jan 27 18:51:35 jadis kernel: BIOS-e820: 0000000000100000 - 000000007dff0000 (usable)
Jan 27 18:51:35 jadis kernel: BIOS-e820: 000000007dff0000 - 000000007dff3000 (ACPI NVS)
Jan 27 18:51:35 jadis kernel: BIOS-e820: 000000007dff3000 - 000000007e000000 (ACPI data)
Jan 27 18:51:35 jadis kernel: BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Jan 27 18:51:35 jadis kernel: Notice: NX (Execute Disable) protection missing in CPU!
Jan 27 18:51:35 jadis kernel: DMI 2.2 present.
Jan 27 18:51:35 jadis kernel: DMI: MICRO-STAR INTERNATIONAL CO., LTD 8366-8233/MS-6390, BIOS 6.00 PG 10/28/2002
Jan 27 18:51:35 jadis kernel: e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jan 27 18:51:35 jadis kernel: e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jan 27 18:51:35 jadis kernel: last_pfn = 0x7dff0 max_arch_pfn = 0x100000
Jan 27 18:51:35 jadis kernel: MTRR default type: uncachable
Jan 27 18:51:35 jadis kernel: MTRR fixed ranges enabled:
Jan 27 18:51:35 jadis kernel:  00000-9FFFF write-back
Jan 27 18:51:35 jadis kernel:  A0000-BFFFF uncachable
Jan 27 18:51:35 jadis kernel:  C0000-CBFFF write-protect
Jan 27 18:51:35 jadis kernel:  CC000-FFFFF uncachable
Jan 27 18:51:35 jadis kernel: MTRR variable ranges enabled:
Jan 27 18:51:35 jadis kernel:  0 base 000000000 mask F80000000 write-back
Jan 27 18:51:35 jadis kernel:  1 base 07E000000 mask FFE000000 uncachable
Jan 27 18:51:35 jadis kernel:  2 disabled
Jan 27 18:51:35 jadis kernel:  3 disabled
Jan 27 18:51:35 jadis kernel:  4 disabled
Jan 27 18:51:35 jadis kernel:  5 base 0D0000000 mask FF8000000 write-combining
Jan 27 18:51:35 jadis kernel:  6 disabled
Jan 27 18:51:35 jadis kernel:  7 disabled
Jan 27 18:51:35 jadis kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jan 27 18:51:35 jadis kernel: found SMP MP-table at [c00f6660] f6660
Jan 27 18:51:35 jadis kernel: initial memory mapped : 0 - 01000000
Jan 27 18:51:35 jadis kernel: Base memory trampoline at [c0099000] 99000 size 16384
Jan 27 18:51:35 jadis kernel: init_memory_mapping: 0000000000000000-00000000377fe000
Jan 27 18:51:35 jadis kernel: 0000000000 - 0000400000 page 4k
Jan 27 18:51:35 jadis kernel: 0000400000 - 0037400000 page 2M
Jan 27 18:51:35 jadis kernel: 0037400000 - 00377fe000 page 4k
Jan 27 18:51:35 jadis kernel: kernel direct mapping tables up to 377fe000 @ ffb000-1000000
Jan 27 18:51:35 jadis kernel: RAMDISK: 368e4000 - 3746a000
Jan 27 18:51:35 jadis kernel: ACPI: RSDP 000f8080 00014 (v00 VT8375)
Jan 27 18:51:35 jadis kernel: ACPI: RSDT 7dff3000 0002C (v01 VT8375 MSI ACPI 42302E31 AWRD 00000000)
Jan 27 18:51:35 jadis kernel: ACPI: FACP 7dff3040 00074 (v01 VT8375 MSI ACPI 42302E31 AWRD 00000000)
Jan 27 18:51:35 jadis kernel: ACPI: DSDT 7dff30c0 03ACB (v01 VT8375 MSI ACPI 00001000 MSFT 0100000C)
Jan 27 18:51:35 jadis kernel: ACPI: FACS 7dff0000 00040
Jan 27 18:51:35 jadis kernel: ACPI: APIC 7dff6bc0 00054 (v01 VT8375 MSI ACPI 42302E31 AWRD 00000000)
Jan 27 18:51:35 jadis kernel: ACPI: Local APIC address 0xfee00000
Jan 27 18:51:35 jadis kernel: 1127MB HIGHMEM available.
Jan 27 18:51:35 jadis kernel: 887MB LOWMEM available.
Jan 27 18:51:35 jadis kernel:  mapped low ram: 0 - 377fe000
Jan 27 18:51:35 jadis kernel:  low ram: 0 - 377fe000
Jan 27 18:51:35 jadis kernel: Zone PFN ranges:
Jan 27 18:51:35 jadis kernel:  DMA      0x00000010 -> 0x00001000
Jan 27 18:51:35 jadis kernel:  Normal   0x00001000 -> 0x000377fe
Jan 27 18:51:35 jadis kernel:  HighMem  0x000377fe -> 0x0007dff0
Jan 27 18:51:35 jadis kernel: Movable zone start PFN for each node
Jan 27 18:51:35 jadis kernel: early_node_map[2] active PFN ranges
Jan 27 18:51:35 jadis kernel:    0: 0x00000010 -> 0x000000a0
Jan 27 18:51:35 jadis kernel:    0: 0x00000100 -> 0x0007dff0
Jan 27 18:51:35 jadis kernel: On node 0 totalpages: 515968
Jan 27 18:51:35 jadis kernel: free_area_init_node: node 0, pgdat c099e8c0, node_mem_map f5924200
Jan 27 18:51:35 jadis kernel:  DMA zone: 32 pages used for memmap
Jan 27 18:51:35 jadis kernel:  DMA zone: 0 pages reserved
Jan 27 18:51:35 jadis kernel:  DMA zone: 3952 pages, LIFO batch:0
Jan 27 18:51:35 jadis kernel:  Normal zone: 1744 pages used for memmap
Jan 27 18:51:35 jadis kernel:  Normal zone: 221486 pages, LIFO batch:31
Jan 27 18:51:35 jadis kernel:  HighMem zone: 2256 pages used for memmap
Jan 27 18:51:35 jadis kernel:  HighMem zone: 286498 pages, LIFO batch:31
Jan 27 18:51:35 jadis kernel: Using APIC driver default
Jan 27 18:51:35 jadis kernel: ACPI: PM-Timer IO Port: 0x4008
Jan 27 18:51:35 jadis kernel: ACPI: Local APIC address 0xfee00000
Jan 27 18:51:35 jadis kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jan 27 18:51:35 jadis kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Jan 27 18:51:35 jadis kernel: IOAPIC[0]: apic_id 2, version 2, address 0xfec00000, GSI 0-23
Jan 27 18:51:35 jadis kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jan 27 18:51:35 jadis kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 dfl dfl)
Jan 27 18:51:35 jadis kernel: ACPI: IRQ0 used by override.
Jan 27 18:51:35 jadis kernel: ACPI: IRQ2 used by override.
Jan 27 18:51:35 jadis kernel: ACPI: IRQ11 used by override.
Jan 27 18:51:35 jadis kernel: Using ACPI (MADT) for SMP configuration information
Jan 27 18:51:35 jadis kernel: SMP: Allowing 1 CPUs, 0 hotplug CPUs
Jan 27 18:51:35 jadis kernel: nr_irqs_gsi: 40
Jan 27 18:51:35 jadis kernel: PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
Jan 27 18:51:35 jadis kernel: PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
Jan 27 18:51:35 jadis kernel: Allocating PCI resources starting at 7e000000 (gap: 7e000000:81ff0000)
Jan 27 18:51:35 jadis kernel: Booting paravirtualized kernel on bare hardware
Jan 27 18:51:35 jadis kernel: setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1
Jan 27 18:51:35 jadis kernel: PERCPU: Embedded 12 pages/cpu @f5400000 s25024 r0 d24128 u4194304
Jan 27 18:51:35 jadis kernel: pcpu-alloc: s25024 r0 d24128 u4194304 alloc=1*4194304
Jan 27 18:51:35 jadis kernel: pcpu-alloc: [0] 0 
Jan 27 18:51:35 jadis kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 511936
Jan 27 18:51:35 jadis kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-3.0.18-sune-1 root=UUID=9ab1ca74-1f10-4d72-b682-74dc1a4e6380 ro video=uvesafb:mode_option:1600x1200-32,mtrr:3,yscroll
Jan 27 18:51:35 jadis kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
Jan 27 18:51:35 jadis kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Jan 27 18:51:35 jadis kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Jan 27 18:51:35 jadis kernel: Initializing CPU#0
Jan 27 18:51:35 jadis kernel: allocated 8257024 bytes of page_cgroup
Jan 27 18:51:35 jadis kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jan 27 18:51:35 jadis kernel: Initializing HighMem for node 0 (000377fe:0007dff0)
Jan 27 18:51:35 jadis kernel: Memory: 2020280k/2064320k available (3570k kernel code, 43592k reserved, 2214k data, 456k init, 1155016k highmem)
Jan 27 18:51:35 jadis kernel: virtual kernel memory layout:
Jan 27 18:51:35 jadis kernel:    fixmap  : 0xffd34000 - 0xfffff000   (2860 kB)
Jan 27 18:51:35 jadis kernel:    pkmap   : 0xff800000 - 0xffc00000   (4096 kB)
Jan 27 18:51:35 jadis kernel:    vmalloc : 0xf7ffe000 - 0xff7fe000   ( 120 MB)
Jan 27 18:51:35 jadis kernel:    lowmem  : 0xc0000000 - 0xf77fe000   ( 887 MB)
Jan 27 18:51:35 jadis kernel:      .init : 0xc09a7000 - 0xc0a19000   ( 456 kB)
Jan 27 18:51:35 jadis kernel:      .data : 0xc077c82e - 0xc09a6040   (2214 kB)
Jan 27 18:51:35 jadis kernel:      .text : 0xc0400000 - 0xc077c82e   (3570 kB)
Jan 27 18:51:35 jadis kernel: Checking if this processor honours the WP bit even in supervisor mode...Ok.
Jan 27 18:51:35 jadis kernel: SLUB: Genslabs=15, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Jan 27 18:51:35 jadis kernel: Hierarchical RCU implementation.
Jan 27 18:51:35 jadis kernel: NR_IRQS:1280
Jan 27 18:51:35 jadis kernel: CPU 0 irqstacks, hard=f4818000 soft=f481a000
Jan 27 18:51:35 jadis kernel: Console: colour VGA+ 80x25
Jan 27 18:51:35 jadis kernel: console [tty0] enabled
Jan 27 18:51:35 jadis kernel: Fast TSC calibration using PIT
Jan 27 18:51:35 jadis kernel: Detected 1477.368 MHz processor.
Jan 27 18:51:35 jadis kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 2954.73 BogoMIPS (lpj=1477368)
Jan 27 18:51:35 jadis kernel: pid_max: default: 32768 minimum: 301
Jan 27 18:51:35 jadis kernel: Security Framework initialized
Jan 27 18:51:35 jadis kernel: SELinux:  Initializing.
Jan 27 18:51:35 jadis kernel: SELinux:  Starting in permissive mode
Jan 27 18:51:35 jadis kernel: Mount-cache hash table entries: 512
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys cpuacct
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys memory
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys devices
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys freezer
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys net_cls
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys blkio
Jan 27 18:51:35 jadis kernel: Initializing cgroup subsys perf_event
Jan 27 18:51:35 jadis kernel: CPU: CLK_CTL MSR was 6003d223. Reprogramming to 2003d223
Jan 27 18:51:35 jadis kernel: mce: CPU supports 4 MCE banks
Jan 27 18:51:35 jadis kernel: SMP alternatives: switching to UP code
Jan 27 18:51:35 jadis kernel: Freeing SMP alternatives: 12k freed
Jan 27 18:51:35 jadis kernel: ACPI: Core revision 20110413
Jan 27 18:51:35 jadis kernel: Enabling APIC mode:  Flat.  Using 1 I/O APICs
Jan 27 18:51:35 jadis kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jan 27 18:51:35 jadis kernel: CPU0: AMD Unknow CPU Type stepping 00
Jan 27 18:51:35 jadis kernel: Performance Events: AMD PMU driver.
Jan 27 18:51:35 jadis kernel: ... version:                0
Jan 27 18:51:35 jadis kernel: ... bit width:              48
Jan 27 18:51:35 jadis kernel: ... generic registers:      4
Jan 27 18:51:35 jadis kernel: ... value mask:             0000ffffffffffff
Jan 27 18:51:35 jadis kernel: ... max period:             00007fffffffffff
Jan 27 18:51:35 jadis kernel: ... fixed-purpose events:   0
Jan 27 18:51:35 jadis kernel: ... event mask:             000000000000000f
Jan 27 18:51:35 jadis kernel: NMI watchdog enabled, takes one hw-pmu counter.
Jan 27 18:51:35 jadis kernel: Brought up 1 CPUs
Jan 27 18:51:35 jadis kernel: Total of 1 processors activated (2954.73 BogoMIPS).
Jan 27 18:51:35 jadis kernel: devtmpfs: initialized
Jan 27 18:51:35 jadis kernel: PM: Registering ACPI NVS region at 7dff0000 (12288 bytes)
Jan 27 18:51:35 jadis kernel: print_constraints: dummy: 
Jan 27 18:51:35 jadis kernel: Time: 17:51:19  Date: 01/27/12
Jan 27 18:51:35 jadis kernel: NET: Registered protocol family 16
Jan 27 18:51:35 jadis kernel: ACPI: bus type pci registered
Jan 27 18:51:35 jadis kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb930, last bus=1
Jan 27 18:51:35 jadis kernel: PCI: Using configuration type 1 for base access
Jan 27 18:51:35 jadis kernel: bio: create slab <bio-0> at 0
Jan 27 18:51:35 jadis kernel: ACPI: EC: Look up EC in DSDT
Jan 27 18:51:35 jadis kernel: ACPI: Interpreter enabled
Jan 27 18:51:35 jadis kernel: ACPI: (supports S0 S1 S4 S5)
Jan 27 18:51:35 jadis kernel: ACPI: Using IOAPIC for interrupt routing
Jan 27 18:51:35 jadis kernel: ACPI: No dock devices found.
Jan 27 18:51:35 jadis kernel: HEST: Table not found.
Jan 27 18:51:35 jadis kernel: PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
Jan 27 18:51:35 jadis kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Jan 27 18:51:35 jadis kernel: pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
Jan 27 18:51:35 jadis kernel: pci_root PNP0A03:00: host bridge window [io  0x0d00-0x3fff] (ignored)
Jan 27 18:51:35 jadis kernel: pci_root PNP0A03:00: host bridge window [io  0x4100-0x4fff] (ignored)
Jan 27 18:51:35 jadis kernel: pci_root PNP0A03:00: host bridge window [io  0x5010-0xffff] (ignored)
Jan 27 18:51:35 jadis kernel: pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
Jan 27 18:51:35 jadis kernel: pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
Jan 27 18:51:35 jadis kernel: pci_root PNP0A03:00: host bridge window [mem 0x7e000000-0xfebfffff] (ignored)
Jan 27 18:51:35 jadis kernel: pci 0000:00:00.0: [1106:3116] type 0 class 0x000600
Jan 27 18:51:35 jadis kernel: pci 0000:00:00.0: reg 10: [mem 0xd0000000-0xd7ffffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0: [1106:b091] type 1 class 0x000604
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0: supports D1
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: [1095:3114] type 0 class 0x000104
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: reg 10: [io  0x9000-0x9007]
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: reg 14: [io  0x9400-0x9403]
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: reg 18: [io  0x9800-0x9807]
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: reg 1c: [io  0x9c00-0x9c03]
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: reg 20: [io  0xa000-0xa00f]
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: reg 24: [mem 0xe3010000-0xe30103ff]
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: reg 30: [mem 0x00000000-0x0007ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: supports D1 D2
Jan 27 18:51:35 jadis kernel: pci 0000:00:06.0: [168c:0029] type 0 class 0x000280
Jan 27 18:51:35 jadis kernel: pci 0000:00:06.0: reg 10: [mem 0xe3000000-0xe300ffff]
Jan 27 18:51:35 jadis kernel: pci 0000:00:06.0: PME# supported from D0 D3hot
Jan 27 18:51:35 jadis kernel: pci 0000:00:06.0: PME# disabled
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: [13f0:0200] type 0 class 0x000200
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: reg 10: [io  0xa400-0xa47f]
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: reg 14: [mem 0xe3011000-0xe30111ff]
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: reg 30: [mem 0x00000000-0x0000ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: supports D1 D2
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: PME# supported from D1 D2 D3hot D3cold
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: PME# disabled
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: [10ec:8139] type 0 class 0x000200
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: reg 10: [io  0xa800-0xa8ff]
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: reg 14: [mem 0xe3012000-0xe30120ff]
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: reg 30: [mem 0x00000000-0x0000ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: supports D1 D2
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: PME# supported from D1 D2 D3hot D3cold
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: PME# disabled
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.0: [1106:3147] type 0 class 0x000601
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.1: [1106:0571] type 0 class 0x000101
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.1: reg 20: [io  0xac00-0xac0f]
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.2: [1106:3038] type 0 class 0x000c03
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.2: reg 20: [io  0xb000-0xb01f]
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.3: [1106:3038] type 0 class 0x000c03
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.3: reg 20: [io  0xb400-0xb41f]
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.5: [1106:3059] type 0 class 0x000401
Jan 27 18:51:35 jadis kernel: pci 0000:00:11.5: reg 10: [io  0xb800-0xb8ff]
Jan 27 18:51:35 jadis kernel: pci 0000:01:00.0: [5333:8d04] type 0 class 0x000300
Jan 27 18:51:35 jadis kernel: pci 0000:01:00.0: reg 10: [mem 0xe1000000-0xe107ffff]
Jan 27 18:51:35 jadis kernel: pci 0000:01:00.0: reg 14: [mem 0xd8000000-0xdfffffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:01:00.0: supports D1 D2
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0: PCI bridge to [bus 01-01]
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0:   bridge window [io  0xf000-0x0000] (disabled)
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe1ffffff]
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xdfffffff pref]
Jan 27 18:51:35 jadis kernel: pci_bus 0000:00: on NUMA node 0
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Jan 27 18:51:35 jadis kernel: ACPI Warning: For \_SB_.PCI0._PRT: Return Package type mismatch at index 3 - found Reference, expected Integer (20110413/nspredef-1060)
Jan 27 18:51:35 jadis kernel: ACPI Warning: (PRT[18].Source) SourceName and SourceIndex are reversed, fixed (20110413/rscreate-277)
Jan 27 18:51:35 jadis kernel: ACPI Warning: (PRT[19].Source) SourceName and SourceIndex are reversed, fixed (20110413/rscreate-277)
Jan 27 18:51:35 jadis kernel: ACPI Warning: (PRT[1A].Source) SourceName and SourceIndex are reversed, fixed (20110413/rscreate-277)
Jan 27 18:51:35 jadis kernel: ACPI Warning: (PRT[1B].Source) SourceName and SourceIndex are reversed, fixed (20110413/rscreate-277)
Jan 27 18:51:35 jadis kernel: pci0000:00: Unable to request _OSC control (_OSC support mask: 0x1e)
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 10 11 *12 14 15)
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKA] (IRQs 16 17 18 19 20 21 22 23) *0
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKB] (IRQs 16 17 18 19 20 21 22 23) *0
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKC] (IRQs 22) *0
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKD] (IRQs 21) *0
Jan 27 18:51:35 jadis kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
Jan 27 18:51:35 jadis kernel: vgaarb: loaded
Jan 27 18:51:35 jadis kernel: vgaarb: bridge control possible 0000:01:00.0
Jan 27 18:51:35 jadis kernel: SCSI subsystem initialized
Jan 27 18:51:35 jadis kernel: libata version 3.00 loaded.
Jan 27 18:51:35 jadis kernel: usbcore: registered new interface driver usbfs
Jan 27 18:51:35 jadis kernel: usbcore: registered new interface driver hub
Jan 27 18:51:35 jadis kernel: usbcore: registered new device driver usb
Jan 27 18:51:35 jadis kernel: PCI: Using ACPI for IRQ routing
Jan 27 18:51:35 jadis kernel: PCI: pci_cache_line_size set to 32 bytes
Jan 27 18:51:35 jadis kernel: reserve RAM buffer: 000000007dff0000 - 000000007fffffff 
Jan 27 18:51:35 jadis kernel: NetLabel: Initializing
Jan 27 18:51:35 jadis kernel: NetLabel:  domain hash size = 128
Jan 27 18:51:35 jadis kernel: NetLabel:  protocols = UNLABELED CIPSOv4
Jan 27 18:51:35 jadis kernel: NetLabel:  unlabeled traffic allowed by default
Jan 27 18:51:35 jadis kernel: pnp: PnP ACPI init
Jan 27 18:51:35 jadis kernel: ACPI: bus type pnp registered
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0x000d1000-0x000d3fff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0x000f0000-0x000f7fff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0x000f8000-0x000fbfff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0x000fc000-0x000fffff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0x7dff0000-0x7dffffff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0xffff0000-0xffffffff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0x00000000-0x0009ffff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0x00100000-0x7dfeffff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0xfec00000-0xfec00fff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0xfee00000-0xfee00fff]
Jan 27 18:51:35 jadis kernel: pnp 00:00: [mem 0xfff80000-0xfffeffff]
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0x000d1000-0x000d3fff] has been reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0x000f0000-0x000f7fff] could not be reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0x000f8000-0x000fbfff] could not be reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0x000fc000-0x000fffff] could not be reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0x7dff0000-0x7dffffff] could not be reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0xffff0000-0xffffffff] has been reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0x00000000-0x0009ffff] could not be reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0x00100000-0x7dfeffff] could not be reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0xfec00000-0xfec00fff] could not be reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0xfee00000-0xfee00fff] has been reserved
Jan 27 18:51:35 jadis kernel: system 00:00: [mem 0xfff80000-0xfffeffff] has been reserved
Jan 27 18:51:35 jadis kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:01: [bus 00-ff]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x0cf8-0x0cff]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x0000-0x0cf7 window]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x0d00-0x3fff window]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x4000-0x407f]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x4080-0x40ff]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x4100-0x4fff window]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x5000-0x500f]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [io  0x5010-0xffff window]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [mem 0x000a0000-0x000bffff window]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [mem 0x000c0000-0x000dffff window]
Jan 27 18:51:35 jadis kernel: pnp 00:01: [mem 0x7e000000-0xfebfffff window]
Jan 27 18:51:35 jadis kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0a03 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0010-0x001f]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0022-0x003f]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0044-0x005f]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0062-0x0063]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0065-0x006f]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0074-0x007f]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0091-0x0093]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x00a2-0x00bf]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x00e0-0x00ef]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x04d0-0x04d1]
Jan 27 18:51:35 jadis kernel: pnp 00:02: [io  0x0294-0x0297]
Jan 27 18:51:35 jadis kernel: system 00:02: [io  0x04d0-0x04d1] has been reserved
Jan 27 18:51:35 jadis kernel: system 00:02: [io  0x0294-0x0297] has been reserved
Jan 27 18:51:35 jadis kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:03: [dma 4]
Jan 27 18:51:35 jadis kernel: pnp 00:03: [io  0x0000-0x000f]
Jan 27 18:51:35 jadis kernel: pnp 00:03: [io  0x0080-0x0090]
Jan 27 18:51:35 jadis kernel: pnp 00:03: [io  0x0094-0x009f]
Jan 27 18:51:35 jadis kernel: pnp 00:03: [io  0x00c0-0x00df]
Jan 27 18:51:35 jadis kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0200 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:04: [io  0x0070-0x0073]
Jan 27 18:51:35 jadis kernel: pnp 00:04: [irq 8]
Jan 27 18:51:35 jadis kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0b00 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:05: [io  0x0061]
Jan 27 18:51:35 jadis kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0800 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:06: [io  0x00f0-0x00ff]
Jan 27 18:51:35 jadis kernel: pnp 00:06: [irq 13]
Jan 27 18:51:35 jadis kernel: pnp 00:06: Plug and Play ACPI device, IDs PNP0c04 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:07: [io  0x03f2-0x03f5]
Jan 27 18:51:35 jadis kernel: pnp 00:07: [io  0x03f7]
Jan 27 18:51:35 jadis kernel: pnp 00:07: [irq 6]
Jan 27 18:51:35 jadis kernel: pnp 00:07: [dma 2]
Jan 27 18:51:35 jadis kernel: pnp 00:07: Plug and Play ACPI device, IDs PNP0700 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:08: [io  0x03f8-0x03ff]
Jan 27 18:51:35 jadis kernel: pnp 00:08: [irq 4]
Jan 27 18:51:35 jadis kernel: pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:09: [io  0x02f8-0x02ff]
Jan 27 18:51:35 jadis kernel: pnp 00:09: [irq 3]
Jan 27 18:51:35 jadis kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:0a: [io  0x0378-0x037f]
Jan 27 18:51:35 jadis kernel: pnp 00:0a: [io  0x0778-0x077b]
Jan 27 18:51:35 jadis kernel: pnp 00:0a: [irq 7]
Jan 27 18:51:35 jadis kernel: pnp 00:0a: [dma 3]
Jan 27 18:51:35 jadis kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0401 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:0b: [io  0x0060]
Jan 27 18:51:35 jadis kernel: pnp 00:0b: [io  0x0064]
Jan 27 18:51:35 jadis kernel: pnp 00:0b: [irq 1]
Jan 27 18:51:35 jadis kernel: pnp 00:0b: Plug and Play ACPI device, IDs PNP0303 (active)
Jan 27 18:51:35 jadis kernel: pnp 00:0c: [io  0x0201-0x0207]
Jan 27 18:51:35 jadis kernel: pnp 00:0c: [io  0x0200]
Jan 27 18:51:35 jadis kernel: pnp 00:0c: Plug and Play ACPI device, IDs PNPb02f (active)
Jan 27 18:51:35 jadis kernel: pnp 00:0d: [io  0x0330-0x0331]
Jan 27 18:51:35 jadis kernel: pnp 00:0d: [irq 10]
Jan 27 18:51:35 jadis kernel: pnp 00:0d: Plug and Play ACPI device, IDs PNPb006 (active)
Jan 27 18:51:35 jadis kernel: pnp: PnP ACPI: found 14 devices
Jan 27 18:51:35 jadis kernel: ACPI: ACPI bus type pnp unregistered
Jan 27 18:51:35 jadis kernel: Switching to clocksource acpi_pm
Jan 27 18:51:35 jadis kernel: PCI: max bus depth: 1 pci_try_num: 2
Jan 27 18:51:35 jadis kernel: pci 0000:00:05.0: BAR 6: assigned [mem 0x80000000-0x8007ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:07.0: BAR 6: assigned [mem 0x80080000-0x8008ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:0e.0: BAR 6: assigned [mem 0x80090000-0x8009ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0: PCI bridge to [bus 01-01]
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0:   bridge window [io  disabled]
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe1ffffff]
Jan 27 18:51:35 jadis kernel: Switched to NOHz mode on CPU #0
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0:   bridge window [mem 0xd8000000-0xdfffffff pref]
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0: setting latency timer to 64
Jan 27 18:51:35 jadis kernel: pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
Jan 27 18:51:35 jadis kernel: pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
Jan 27 18:51:35 jadis kernel: pci_bus 0000:01: resource 1 [mem 0xe0000000-0xe1ffffff]
Jan 27 18:51:35 jadis kernel: pci_bus 0000:01: resource 2 [mem 0xd8000000-0xdfffffff pref]
Jan 27 18:51:35 jadis kernel: NET: Registered protocol family 2
Jan 27 18:51:35 jadis kernel: IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
Jan 27 18:51:35 jadis kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Jan 27 18:51:35 jadis kernel: TCP bind hash table entries: 65536 (order: 8, 1310720 bytes)
Jan 27 18:51:35 jadis kernel: TCP: Hash tables configured (established 131072 bind 65536)
Jan 27 18:51:35 jadis kernel: TCP reno registered
Jan 27 18:51:35 jadis kernel: UDP hash table entries: 512 (order: 2, 24576 bytes)
Jan 27 18:51:35 jadis kernel: UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
Jan 27 18:51:35 jadis kernel: NET: Registered protocol family 1
Jan 27 18:51:35 jadis kernel: pci 0000:00:01.0: disabling DAC on VIA PCI bridge
Jan 27 18:51:35 jadis kernel: pci 0000:01:00.0: Boot video device
Jan 27 18:51:35 jadis kernel: PCI: CLS 32 bytes, default 32
Jan 27 18:51:35 jadis kernel: Trying to unpack rootfs image as initramfs...
Jan 27 18:51:35 jadis kernel: Freeing initrd memory: 11800k freed
Jan 27 18:51:35 jadis kernel: apm: BIOS not found.
Jan 27 18:51:35 jadis kernel: audit: initializing netlink socket (disabled)
Jan 27 18:51:35 jadis kernel: type=2000 audit(1327686678.746:1): initialized
Jan 27 18:51:35 jadis kernel: highmem bounce pool size: 64 pages
Jan 27 18:51:35 jadis kernel: HugeTLB registered 4 MB page size, pre-allocated 0 pages
Jan 27 18:51:35 jadis kernel: VFS: Disk quotas dquot_6.5.2
Jan 27 18:51:35 jadis kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan 27 18:51:35 jadis kernel: msgmni has been set to 1713
Jan 27 18:51:35 jadis kernel: SELinux:  Registering netfilter hooks
Jan 27 18:51:35 jadis kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
Jan 27 18:51:35 jadis kernel: io scheduler noop registered
Jan 27 18:51:35 jadis kernel: io scheduler deadline registered
Jan 27 18:51:35 jadis kernel: io scheduler cfq registered (default)
Jan 27 18:51:35 jadis kernel: start plist test
Jan 27 18:51:35 jadis kernel: end plist test
Jan 27 18:51:35 jadis kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jan 27 18:51:35 jadis kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jan 27 18:51:35 jadis kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jan 27 18:51:35 jadis kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jan 27 18:51:35 jadis kernel: ACPI: Power Button [PWRB]
Jan 27 18:51:35 jadis kernel: input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1
Jan 27 18:51:35 jadis kernel: ACPI: Sleep Button [SLPB]
Jan 27 18:51:35 jadis kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Jan 27 18:51:35 jadis kernel: ACPI: Power Button [PWRF]
Jan 27 18:51:35 jadis kernel: ACPI: Fan [FAN] (on)
Jan 27 18:51:35 jadis kernel: ACPI: acpi_idle registered with cpuidle
Jan 27 18:51:35 jadis kernel: thermal LNXTHERM:00: registered as thermal_zone0
Jan 27 18:51:35 jadis kernel: ACPI: Thermal Zone [THRM] (22 C)
Jan 27 18:51:35 jadis kernel: ERST: Table is not found!
Jan 27 18:51:35 jadis kernel: GHES: HEST is not enabled!
Jan 27 18:51:35 jadis kernel: isapnp: Scanning for PnP cards...
Jan 27 18:51:35 jadis kernel: isapnp: No Plug & Play device found
Jan 27 18:51:35 jadis kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Jan 27 18:51:35 jadis kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Jan 27 18:51:35 jadis kernel: serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Jan 27 18:51:35 jadis kernel: 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Jan 27 18:51:35 jadis kernel: 00:09: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Jan 27 18:51:35 jadis kernel: Refined TSC clocksource calibration: 1477.500 MHz.
Jan 27 18:51:35 jadis kernel: Switching to clocksource tsc
Jan 27 18:51:35 jadis kernel: Non-volatile memory driver v1.3
Jan 27 18:51:35 jadis kernel: Linux agpgart interface v0.103
Jan 27 18:51:35 jadis kernel: agpgart: Detected VIA PM266/KM266 chipset
Jan 27 18:51:35 jadis kernel: agpgart-via 0000:00:00.0: AGP aperture is 128M @ 0xd0000000
Jan 27 18:51:35 jadis kernel: brd: module loaded
Jan 27 18:51:35 jadis kernel: loop: module loaded
Jan 27 18:51:35 jadis kernel: Fixed MDIO Bus: probed
Jan 27 18:51:35 jadis kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan 27 18:51:35 jadis kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan 27 18:51:35 jadis kernel: uhci_hcd: USB Universal Host Controller Interface driver
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKD] BIOS reported IRQ 0, using IRQ 21
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 21
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.2: PCI INT D -> Link[ALKD] -> GSI 21 (level, low) -> IRQ 21
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.2: UHCI Host Controller
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.2: new USB bus registered, assigned bus number 1
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.2: irq 21, io base 0x0000b000
Jan 27 18:51:35 jadis kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
Jan 27 18:51:35 jadis kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan 27 18:51:35 jadis kernel: usb usb1: Product: UHCI Host Controller
Jan 27 18:51:35 jadis kernel: usb usb1: Manufacturer: Linux 3.0.18-sune-1 uhci_hcd
Jan 27 18:51:35 jadis kernel: usb usb1: SerialNumber: 0000:00:11.2
Jan 27 18:51:35 jadis kernel: hub 1-0:1.0: USB hub found
Jan 27 18:51:35 jadis kernel: hub 1-0:1.0: 2 ports detected
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.3: PCI INT D -> Link[ALKD] -> GSI 21 (level, low) -> IRQ 21
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.3: UHCI Host Controller
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.3: new USB bus registered, assigned bus number 2
Jan 27 18:51:35 jadis kernel: uhci_hcd 0000:00:11.3: irq 21, io base 0x0000b400
Jan 27 18:51:35 jadis kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
Jan 27 18:51:35 jadis kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan 27 18:51:35 jadis kernel: usb usb2: Product: UHCI Host Controller
Jan 27 18:51:35 jadis kernel: usb usb2: Manufacturer: Linux 3.0.18-sune-1 uhci_hcd
Jan 27 18:51:35 jadis kernel: usb usb2: SerialNumber: 0000:00:11.3
Jan 27 18:51:35 jadis kernel: hub 2-0:1.0: USB hub found
Jan 27 18:51:35 jadis kernel: hub 2-0:1.0: 2 ports detected
Jan 27 18:51:35 jadis kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Jan 27 18:51:35 jadis kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Jan 27 18:51:35 jadis kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jan 27 18:51:35 jadis kernel: mousedev: PS/2 mouse device common for all mice
Jan 27 18:51:35 jadis kernel: rtc_cmos 00:04: RTC can wake from S4
Jan 27 18:51:35 jadis kernel: rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
Jan 27 18:51:35 jadis kernel: rtc0: alarms up to one year, y3k, 242 bytes nvram
Jan 27 18:51:35 jadis kernel: device-mapper: uevent: version 1.0.3
Jan 27 18:51:35 jadis kernel: device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel at redhat.com
Jan 27 18:51:35 jadis kernel: cpuidle: using governor ladder
Jan 27 18:51:35 jadis kernel: cpuidle: using governor menu
Jan 27 18:51:35 jadis kernel: EFI Variables Facility v0.08 2004-May-17
Jan 27 18:51:35 jadis kernel: usbcore: registered new interface driver usbhid
Jan 27 18:51:35 jadis kernel: usbhid: USB HID core driver
Jan 27 18:51:35 jadis kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jan 27 18:51:35 jadis kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan 27 18:51:35 jadis kernel: TCP cubic registered
Jan 27 18:51:35 jadis kernel: Initializing XFRM netlink socket
Jan 27 18:51:35 jadis kernel: NET: Registered protocol family 17
Jan 27 18:51:35 jadis kernel: Registering the dns_resolver key type
Jan 27 18:51:35 jadis kernel: Using IPI No-Shortcut mode
Jan 27 18:51:35 jadis kernel: PM: Hibernation image not present or could not be loaded.
Jan 27 18:51:35 jadis kernel: registered taskstats version 1
Jan 27 18:51:35 jadis kernel:  Magic number: 12:141:897
Jan 27 18:51:35 jadis kernel: Freeing unused kernel memory: 456k freed
Jan 27 18:51:35 jadis kernel: Write protecting the kernel text: 3572k
Jan 27 18:51:35 jadis kernel: Write protecting the kernel read-only data: 1704k
Jan 27 18:51:35 jadis kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
Jan 27 18:51:35 jadis kernel: md: linear personality registered for level -1
Jan 27 18:51:35 jadis kernel: md: multipath personality registered for level -4
Jan 27 18:51:35 jadis kernel: md: raid0 personality registered for level 0
Jan 27 18:51:35 jadis kernel: md: raid1 personality registered for level 1
Jan 27 18:51:35 jadis kernel: async_tx: api initialized (async)
Jan 27 18:51:35 jadis kernel: xor: automatically using best checksumming function: pIII_sse
Jan 27 18:51:35 jadis kernel:   pIII_sse  :  3980.000 MB/sec
Jan 27 18:51:35 jadis kernel: xor: using function: pIII_sse (3980.000 MB/sec)
Jan 27 18:51:35 jadis kernel: raid6: int32x1    429 MB/s
Jan 27 18:51:35 jadis kernel: raid6: int32x2    558 MB/s
Jan 27 18:51:35 jadis kernel: raid6: int32x4    464 MB/s
Jan 27 18:51:35 jadis kernel: raid6: int32x8    320 MB/s
Jan 27 18:51:35 jadis kernel: raid6: mmxx1     1207 MB/s
Jan 27 18:51:35 jadis kernel: raid6: mmxx2     2054 MB/s
Jan 27 18:51:35 jadis kernel: raid6: sse1x1    1097 MB/s
Jan 27 18:51:35 jadis kernel: raid6: sse1x2    1765 MB/s
Jan 27 18:51:35 jadis kernel: raid6: using algorithm sse1x2 (1765 MB/s)
Jan 27 18:51:35 jadis kernel: md: raid6 personality registered for level 6
Jan 27 18:51:35 jadis kernel: md: raid5 personality registered for level 5
Jan 27 18:51:35 jadis kernel: md: raid4 personality registered for level 4
Jan 27 18:51:35 jadis kernel: md: raid10 personality registered for level 10
Jan 27 18:51:35 jadis kernel: FDC 0 is a post-1991 82077
Jan 27 18:51:35 jadis kernel: sata_sil 0000:00:05.0: version 2.4
Jan 27 18:51:35 jadis kernel: sata_sil 0000:00:05.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan 27 18:51:35 jadis kernel: sata_sil 0000:00:05.0: Applying R_ERR on DMA activate FIS errata fix
Jan 27 18:51:35 jadis kernel: sundance.c:v1.2 11-Sep-2006 Written by Donald Becker
Jan 27 18:51:35 jadis kernel: 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
Jan 27 18:51:35 jadis kernel: scsi0 : sata_sil
Jan 27 18:51:35 jadis kernel: scsi1 : sata_sil
Jan 27 18:51:35 jadis kernel: scsi2 : sata_sil
Jan 27 18:51:35 jadis kernel: scsi3 : sata_sil
Jan 27 18:51:35 jadis kernel: ata1: SATA max UDMA/100 mmio m1024 at 0xe3010000 tf 0xe3010080 irq 16
Jan 27 18:51:35 jadis kernel: ata2: SATA max UDMA/100 mmio m1024 at 0xe3010000 tf 0xe30100c0 irq 16
Jan 27 18:51:35 jadis kernel: ata3: SATA max UDMA/100 mmio m1024 at 0xe3010000 tf 0xe3010280 irq 16
Jan 27 18:51:35 jadis kernel: ata4: SATA max UDMA/100 mmio m1024 at 0xe3010000 tf 0xe30102c0 irq 16
Jan 27 18:51:35 jadis kernel: pata_via 0000:00:11.1: version 0.3.4
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKA] BIOS reported IRQ 0, using IRQ 23
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 23
Jan 27 18:51:35 jadis kernel: pata_via 0000:00:11.1: PCI INT A -> Link[ALKA] -> GSI 23 (level, low) -> IRQ 23
Jan 27 18:51:35 jadis kernel: scsi4 : pata_via
Jan 27 18:51:35 jadis kernel: scsi5 : pata_via
Jan 27 18:51:35 jadis kernel: ata5: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xac00 irq 14
Jan 27 18:51:35 jadis kernel: ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xac08 irq 15
Jan 27 18:51:35 jadis kernel: sundance 0000:00:07.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jan 27 18:51:35 jadis kernel: eth0: IC Plus Corporation IP100A FAST Ethernet Adapter at 0001a400, 00:08:54:54:69:60, IRQ 18.
Jan 27 18:51:35 jadis kernel: eth0: MII PHY found at address 0, status 0x786d advertising 01e1.
Jan 27 18:51:35 jadis kernel: 8139cp 0000:00:0e.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
Jan 27 18:51:35 jadis kernel: ata5.01: ATA-5: QUANTUM FIREBALLP AS40.0, A1Y.1500, max UDMA/100
Jan 27 18:51:35 jadis kernel: ata5.01: 78177792 sectors, multi 16: LBA 
Jan 27 18:51:35 jadis kernel: ata5.01: limited to UDMA/33 due to 40-wire cable
Jan 27 18:51:35 jadis kernel: ata5.01: configured for UDMA/33
Jan 27 18:51:35 jadis kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 27 18:51:35 jadis kernel: ata1.00: ATA-8: Hitachi HDP725025GLA380, GM2OA5CA, max UDMA/133
Jan 27 18:51:35 jadis kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jan 27 18:51:35 jadis kernel: ata1.00: configured for UDMA/100
Jan 27 18:51:35 jadis kernel: scsi 0:0:0:0: Direct-Access     ATA      Hitachi HDP72502 GM2O PQ: 0 ANSI: 5
Jan 27 18:51:35 jadis kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan 27 18:51:35 jadis kernel: sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Jan 27 18:51:35 jadis kernel: sd 0:0:0:0: [sda] Write Protect is off
Jan 27 18:51:35 jadis kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan 27 18:51:35 jadis kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 18:51:35 jadis kernel: sda: sda1 sda2 sda3
Jan 27 18:51:35 jadis kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jan 27 18:51:35 jadis kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 27 18:51:35 jadis kernel: ata2.00: ATA-8: Hitachi HDP725025GLA380, GM2OA52A, max UDMA/133
Jan 27 18:51:35 jadis kernel: ata2.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jan 27 18:51:35 jadis kernel: ata2.00: configured for UDMA/100
Jan 27 18:51:35 jadis kernel: scsi 1:0:0:0: Direct-Access     ATA      Hitachi HDP72502 GM2O PQ: 0 ANSI: 5
Jan 27 18:51:35 jadis kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Jan 27 18:51:35 jadis kernel: sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Jan 27 18:51:35 jadis kernel: sd 1:0:0:0: [sdb] Write Protect is off
Jan 27 18:51:35 jadis kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jan 27 18:51:35 jadis kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 18:51:35 jadis kernel: sdb: sdb1 sdb2 sdb3
Jan 27 18:51:35 jadis kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
Jan 27 18:51:35 jadis kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 27 18:51:35 jadis kernel: ata3.00: ATA-8: Hitachi HDP725025GLA380, GM2OA52A, max UDMA/133
Jan 27 18:51:35 jadis kernel: ata3.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jan 27 18:51:35 jadis kernel: ata3.00: configured for UDMA/100
Jan 27 18:51:35 jadis kernel: scsi 2:0:0:0: Direct-Access     ATA      Hitachi HDP72502 GM2O PQ: 0 ANSI: 5
Jan 27 18:51:35 jadis kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Jan 27 18:51:35 jadis kernel: sd 2:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Jan 27 18:51:35 jadis kernel: sd 2:0:0:0: [sdc] Write Protect is off
Jan 27 18:51:35 jadis kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Jan 27 18:51:35 jadis kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 18:51:35 jadis kernel: sdc: sdc1 sdc2 sdc3
Jan 27 18:51:35 jadis kernel: sd 2:0:0:0: [sdc] Attached SCSI disk
Jan 27 18:51:35 jadis kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jan 27 18:51:35 jadis kernel: ata4.00: ATA-8: Hitachi HDP725025GLA380, GM2OA52A, max UDMA/133
Jan 27 18:51:35 jadis kernel: ata4.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
Jan 27 18:51:35 jadis kernel: ata4.00: configured for UDMA/100
Jan 27 18:51:35 jadis kernel: scsi 3:0:0:0: Direct-Access     ATA      Hitachi HDP72502 GM2O PQ: 0 ANSI: 5
Jan 27 18:51:35 jadis kernel: sd 3:0:0:0: Attached scsi generic sg3 type 0
Jan 27 18:51:35 jadis kernel: scsi 4:0:1:0: Direct-Access     ATA      QUANTUM FIREBALL A1Y. PQ: 0 ANSI: 5
Jan 27 18:51:35 jadis kernel: sd 4:0:1:0: Attached scsi generic sg4 type 0
Jan 27 18:51:35 jadis kernel: sd 4:0:1:0: [sde] 78177792 512-byte logical blocks: (40.0 GB/37.2 GiB)
Jan 27 18:51:35 jadis kernel: sd 3:0:0:0: [sdd] 488397168 512-byte logical blocks: (250 GB/232 GiB)
Jan 27 18:51:35 jadis kernel: sd 4:0:1:0: [sde] Write Protect is off
Jan 27 18:51:35 jadis kernel: sd 4:0:1:0: [sde] Mode Sense: 00 3a 00 00
Jan 27 18:51:35 jadis kernel: sd 3:0:0:0: [sdd] Write Protect is off
Jan 27 18:51:35 jadis kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00
Jan 27 18:51:35 jadis kernel: sd 4:0:1:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 18:51:35 jadis kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 27 18:51:35 jadis kernel: sdd: sdd1 sdd2 sdd3
Jan 27 18:51:35 jadis kernel: sd 3:0:0:0: [sdd] Attached SCSI disk
Jan 27 18:51:35 jadis kernel: sde: sde1 sde2
Jan 27 18:51:35 jadis kernel: sd 4:0:1:0: [sde] Attached SCSI disk
Jan 27 18:51:35 jadis kernel: ata6.00: ATAPI: ASUS DVD-ROM DVD-E616P              0104, E1.04, max UDMA/66
Jan 27 18:51:35 jadis kernel: ata6.01: ATAPI: LITE-ON LTR-52327S, QS09, max UDMA/33
Jan 27 18:51:35 jadis kernel: ata6.00: limited to UDMA/33 due to 40-wire cable
Jan 27 18:51:35 jadis kernel: ata6.00: configured for UDMA/33
Jan 27 18:51:35 jadis kernel: ata6.01: configured for UDMA/33
Jan 27 18:51:35 jadis kernel: scsi 5:0:0:0: CD-ROM            ASUS     DVD-E616P        1.04 PQ: 0 ANSI: 5
Jan 27 18:51:35 jadis kernel: sr0: scsi3-mmc drive: 48x/48x cd/rw xa/form2 cdda tray
Jan 27 18:51:35 jadis kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Jan 27 18:51:35 jadis kernel: sr 5:0:0:0: Attached scsi CD-ROM sr0
Jan 27 18:51:35 jadis kernel: sr 5:0:0:0: Attached scsi generic sg5 type 5
Jan 27 18:51:35 jadis kernel: scsi 5:0:1:0: CD-ROM            LITE-ON  LTR-52327S       QS09 PQ: 0 ANSI: 5
Jan 27 18:51:35 jadis kernel: sr1: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray
Jan 27 18:51:35 jadis kernel: sr 5:0:1:0: Attached scsi CD-ROM sr1
Jan 27 18:51:35 jadis kernel: sr 5:0:1:0: Attached scsi generic sg6 type 5
Jan 27 18:51:35 jadis kernel: 8139too: 8139too Fast Ethernet driver 0.9.28
Jan 27 18:51:35 jadis kernel: 8139too 0000:00:0e.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jan 27 18:51:35 jadis kernel: 8139too 0000:00:0e.0: eth1: RealTek RTL8139 at 0xf8158000, 00:10:dc:d6:14:0f, IRQ 17
Jan 27 18:51:35 jadis kernel: mdadm: sending ioctl 1261 to a partition!
Jan 27 18:51:35 jadis kernel: last message repeated 9 times
Jan 27 18:51:35 jadis kernel: md: bind<sdc3>
Jan 27 18:51:35 jadis kernel: md: bind<sdd2>
Jan 27 18:51:35 jadis kernel: md: bind<sdd3>
Jan 27 18:51:35 jadis kernel: md: bind<sdc1>
Jan 27 18:51:35 jadis kernel: md: bind<sda3>
Jan 27 18:51:35 jadis kernel: md: bind<sda1>
Jan 27 18:51:35 jadis kernel: md: bind<sdd1>
Jan 27 18:51:35 jadis kernel: md: bind<sdc2>
Jan 27 18:51:35 jadis kernel: md: bind<sdb3>
Jan 27 18:51:35 jadis kernel: md: bind<sda2>
Jan 27 18:51:35 jadis kernel: bio: create slab <bio-1> at 1
Jan 27 18:51:35 jadis kernel: md/raid:md1: device sdb3 operational as raid disk 1
Jan 27 18:51:35 jadis kernel: md/raid:md1: device sda3 operational as raid disk 0
Jan 27 18:51:35 jadis kernel: md/raid:md1: device sdd3 operational as raid disk 3
Jan 27 18:51:35 jadis kernel: md/raid:md1: device sdc3 operational as raid disk 2
Jan 27 18:51:35 jadis kernel: md/raid:md1: allocated 4232kB
Jan 27 18:51:35 jadis kernel: md/raid:md1: raid level 5 active with 4 out of 4 devices, algorithm 2
Jan 27 18:51:35 jadis kernel: RAID conf printout:
Jan 27 18:51:35 jadis kernel: --- level:5 rd:4 wd:4
Jan 27 18:51:35 jadis kernel: disk 0, o:1, dev:sda3
Jan 27 18:51:35 jadis kernel: disk 1, o:1, dev:sdb3
Jan 27 18:51:35 jadis kernel: disk 2, o:1, dev:sdc3
Jan 27 18:51:35 jadis kernel: disk 3, o:1, dev:sdd3
Jan 27 18:51:35 jadis kernel: md1: detected capacity change from 0 to 1258094592
Jan 27 18:51:35 jadis kernel: md: bind<sdb1>
Jan 27 18:51:35 jadis kernel: md1: unknown partition table
Jan 27 18:51:35 jadis kernel: md/raid1:md2: active with 4 out of 4 mirrors
Jan 27 18:51:35 jadis kernel: md2: detected capacity change from 0 to 205520896
Jan 27 18:51:35 jadis kernel: md: bind<sdb2>
Jan 27 18:51:35 jadis kernel: md/raid:md0: device sdb2 operational as raid disk 1
Jan 27 18:51:35 jadis kernel: md/raid:md0: device sda2 operational as raid disk 0
Jan 27 18:51:35 jadis kernel: md/raid:md0: device sdc2 operational as raid disk 2
Jan 27 18:51:35 jadis kernel: md/raid:md0: device sdd2 operational as raid disk 3
Jan 27 18:51:35 jadis kernel: md/raid:md0: allocated 4232kB
Jan 27 18:51:35 jadis kernel: md/raid:md0: raid level 5 active with 4 out of 4 devices, algorithm 2
Jan 27 18:51:35 jadis kernel: RAID conf printout:
Jan 27 18:51:35 jadis kernel: --- level:5 rd:4 wd:4
Jan 27 18:51:35 jadis kernel: disk 0, o:1, dev:sda2
Jan 27 18:51:35 jadis kernel: disk 1, o:1, dev:sdb2
Jan 27 18:51:35 jadis kernel: disk 2, o:1, dev:sdc2
Jan 27 18:51:35 jadis kernel: disk 3, o:1, dev:sdd2
Jan 27 18:51:35 jadis kernel: md0: detected capacity change from 0 to 748294569984
Jan 27 18:51:35 jadis kernel: md2: unknown partition table
Jan 27 18:51:35 jadis kernel: md0: unknown partition table
Jan 27 18:51:35 jadis kernel: EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 27 18:51:35 jadis kernel: init: ureadahead main process (299) terminated with status 5
Jan 27 18:51:35 jadis kernel: Adding 1228604k swap on /dev/md1.  Priority:-1 extents:1 across:1228604k 
Jan 27 18:51:35 jadis kernel: lp: driver loaded but no devices found
Jan 27 18:51:35 jadis kernel: w83627hf: w83627hf: Found W83697HF chip at 0x290
Jan 27 18:51:35 jadis kernel: ACPI: resource w83627hf [io  0x0295-0x0296] conflicts with ACPI region IP__ [io 0x295-0x296]
Jan 27 18:51:35 jadis kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jan 27 18:51:35 jadis kernel: parport_pc 00:0a: reported by Plug and Play ACPI
Jan 27 18:51:35 jadis kernel: parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE,EPP]
Jan 27 18:51:35 jadis kernel: lp0: using parport0 (interrupt-driven).
Jan 27 18:51:35 jadis kernel: lp0: console ready
Jan 27 18:51:35 jadis kernel: gameport gameport0: NS558 PnP Gameport is pnp00:0c/gameport0, io 0x201, speed 877kHz
Jan 27 18:51:35 jadis kernel: cfg80211: Calling CRDA to update world regulatory domain
Jan 27 18:51:35 jadis kernel: NET: Registered protocol family 23
Jan 27 18:51:35 jadis kernel: EXT4-fs (md0): re-mounted. Opts: errors=remount-ro
Jan 27 18:51:35 jadis kernel: ath9k 0000:00:06.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jan 27 18:51:35 jadis kernel: ppdev: user-space parallel port driver
Jan 27 18:51:35 jadis kernel: ath: EEPROM regdomain: 0x30
Jan 27 18:51:35 jadis kernel: ath: EEPROM indicates we should expect a direct regpair map
Jan 27 18:51:35 jadis kernel: ath: Country alpha2 being used: AM
Jan 27 18:51:35 jadis kernel: ath: Regpair used: 0x30
Jan 27 18:51:35 jadis kernel: cfg80211: World regulatory domain updated:
Jan 27 18:51:35 jadis kernel: cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 27 18:51:35 jadis kernel: cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 18:51:35 jadis kernel: cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 27 18:51:35 jadis kernel: cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jan 27 18:51:35 jadis kernel: cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 18:51:35 jadis kernel: cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jan 27 18:51:35 jadis kernel: scsi_verify_blk_ioctl: 272 callbacks suppressed
Jan 27 18:51:35 jadis kernel: mdadm: sending ioctl 1261 to a partition!
Jan 27 18:51:35 jadis kernel: last message repeated 5 times
Jan 27 18:51:35 jadis kernel: ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
Jan 27 18:51:35 jadis kernel: cfg80211: Calling CRDA for country: AM
Jan 27 18:51:35 jadis kernel: Registered led device: ath9k-phy0
Jan 27 18:51:35 jadis kernel: ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xf8540000, irq=17
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKC] BIOS reported IRQ 0, using IRQ 22
Jan 27 18:51:35 jadis kernel: ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
Jan 27 18:51:35 jadis kernel: VIA 82xx Audio 0000:00:11.5: PCI INT C -> Link[ALKC] -> GSI 22 (level, low) -> IRQ 22
Jan 27 18:51:35 jadis kernel: VIA 82xx Audio 0000:00:11.5: setting latency timer to 64
Jan 27 18:51:35 jadis kernel: cfg80211: Regulatory domain changed to country: AM
Jan 27 18:51:35 jadis kernel: cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 27 18:51:35 jadis kernel: cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 27 18:51:35 jadis kernel: cfg80211:     (5170000 KHz - 5250000 KHz @ 20000 KHz), (N/A, 1800 mBm)
Jan 27 18:51:35 jadis kernel: cfg80211:     (5250000 KHz - 5330000 KHz @ 20000 KHz), (N/A, 1800 mBm)
Jan 27 18:51:35 jadis kernel: mdadm: sending ioctl 1261 to a partition!
Jan 27 18:51:35 jadis kernel: mdadm: sending ioctl 1261 to a partition!
Jan 27 18:51:35 jadis kernel: NET: Registered protocol family 10
Jan 27 18:51:35 jadis kernel: Bridge firewalling registered
Jan 27 18:51:35 jadis kernel: wlan0: setting MTU 1492
Jan 27 18:51:35 jadis kernel: ieee80211 phy0: device now idle
Jan 27 18:51:35 jadis kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 27 18:51:35 jadis kernel: device eth1 entered promiscuous mode
Jan 27 18:51:35 jadis kernel: eth1: Link up
Jan 27 18:51:35 jadis kernel: eth1: Link changed: 100Mbps, full duplex
Jan 27 18:51:35 jadis kernel: mdadm: sending ioctl 1261 to a partition!
Jan 27 18:51:35 jadis kernel: mdadm: sending ioctl 1261 to a partition!
Jan 27 18:51:35 jadis kernel: br0: port 1(eth1) entering forwarding state
Jan 27 18:51:35 jadis kernel: br0: port 1(eth1) entering forwarding state
Jan 27 18:51:35 jadis kernel: init: udev-fallback-graphics main process (1021) terminated with status 1
Jan 27 18:51:35 jadis kernel: 8139too 0000:00:0e.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Jan 27 18:51:35 jadis kernel: REISERFS (device sde1): found reiserfs format "3.6" with standard journal
Jan 27 18:51:35 jadis kernel: REISERFS (device sde1): using ordered data mode
Jan 27 18:51:35 jadis kernel: REISERFS (device sde1): journal params: device sde1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan 27 18:51:35 jadis kernel: REISERFS (device sde1): checking transaction log (sde1)
Jan 27 18:51:35 jadis kernel: REISERFS (device sde1): Using r5 hash to sort names
Jan 27 18:51:35 jadis kernel: init: smbd main process (1125) killed by HUP signal
Jan 27 18:51:35 jadis kernel: init: smbd main process ended, respawning
Jan 27 18:51:35 jadis kernel: IPv6 over IPv4 tunneling driver
Jan 27 18:51:36 jadis avahi-daemon[1330]: Found user 'avahi' (UID 119) and group 'avahi' (GID 127).
Jan 27 18:51:36 jadis avahi-daemon[1330]: Successfully dropped root privileges.
Jan 27 18:51:36 jadis avahi-daemon[1330]: avahi-daemon 0.6.30 starting up.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Successfully called chroot().
Jan 27 18:51:36 jadis avahi-daemon[1330]: Successfully dropped remaining capabilities.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Loading service file /services/udisks.service.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface br0.IPv6 with address fe80::208:54ff:fe54:6960.
Jan 27 18:51:36 jadis avahi-daemon[1330]: New relevant interface br0.IPv6 for mDNS.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.1.
Jan 27 18:51:36 jadis avahi-daemon[1330]: New relevant interface br0.IPv4 for mDNS.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::22c:6eff:fe7a:7f43.
Jan 27 18:51:36 jadis avahi-daemon[1330]: New relevant interface eth0.IPv6 for mDNS.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface eth0.IPv4 with address 95.166.144.106.
Jan 27 18:51:36 jadis avahi-daemon[1330]: New relevant interface eth0.IPv4 for mDNS.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Network interface enumeration completed.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Registering new address record for fe80::208:54ff:fe54:6960 on br0.*.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Registering new address record for 192.168.1.1 on br0.IPv4.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Registering new address record for fe80::22c:6eff:fe7a:7f43 on eth0.*.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Registering new address record for 95.166.144.106 on eth0.IPv4.
Jan 27 18:51:36 jadis avahi-daemon[1330]: Registering HINFO record with values 'I686'/'LINUX'.
Jan 27 18:51:37 jadis postfix/postfix-script[1340]: fatal: the Postfix mail system is not running
Jan 27 18:51:37 jadis dhclient: bound to 95.166.144.106 -- renewal in 41854 seconds.
Jan 27 18:51:37 jadis kernel: init: ssh main process (1135) terminated with status 255
Jan 27 18:51:37 jadis avahi-daemon[1330]: Server startup complete. Host name is jadis.local. Local service cookie is 3761654055.
Jan 27 18:51:37 jadis ntpdate[1431]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:37 jadis ntpdate[1431]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:37 jadis ntpdate[1431]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:37 jadis ntpdate[1431]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:37 jadis ntpdate[1431]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Jan 27 18:51:37 jadis ntpdate[1431]: no servers can be used, exiting
Jan 27 18:51:38 jadis ntpd[1462]: ntpd 4.2.6p2 at 1.2194 Fri Sep  2 18:37:15 UTC 2011 (1)
Jan 27 18:51:38 jadis ntpd[1472]: proto: precision = 0.434 usec
Jan 27 18:51:38 jadis ntpd[1472]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Jan 27 18:51:38 jadis ntpd[1472]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen and drop on 1 v6wildcard :: UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 3 eth0 95.166.144.106 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 4 br0 192.168.1.1 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 5 eth0 fe80::22c:6eff:fe7a:7f43 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 6 br0 fe80::208:54ff:fe54:6960 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 7 sixxs 2001:16d8:ee00:2e::2 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 8 sixxs fe80::c0a8:101 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 9 sixxs fe80::5fa6:906a UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Listen normally on 10 lo ::1 UDP 123
Jan 27 18:51:38 jadis ntpd[1472]: Deferring DNS for 0.ubuntu.pool.ntp.org 1
Jan 27 18:51:38 jadis ntpd[1472]: Deferring DNS for 1.ubuntu.pool.ntp.org 1
Jan 27 18:51:38 jadis ntpd[1472]: Deferring DNS for 2.ubuntu.pool.ntp.org 1
Jan 27 18:51:38 jadis ntpd[1472]: Deferring DNS for 3.ubuntu.pool.ntp.org 1
Jan 27 18:51:38 jadis ntpd[1472]: Deferring DNS for ntp.ubuntu.com 1
Jan 27 18:51:38 jadis avahi-daemon[1330]: Service "jadis" (/services/udisks.service) successfully established.
Jan 27 18:51:40 jadis ntpd_intres[1474]: host name not found: 0.ubuntu.pool.ntp.org
Jan 27 18:51:40 jadis ntpd_intres[1474]: host name not found: 1.ubuntu.pool.ntp.org
Jan 27 18:51:40 jadis ntpd_intres[1474]: host name not found: 2.ubuntu.pool.ntp.org
Jan 27 18:51:40 jadis ntpd_intres[1474]: host name not found: 3.ubuntu.pool.ntp.org
Jan 27 18:51:40 jadis ntpd_intres[1474]: host name not found: ntp.ubuntu.com
Jan 27 18:51:42 jadis kernel: br0: no IPv6 routers present
Jan 27 18:51:43 jadis kernel: eth0: no IPv6 routers present
Jan 27 18:51:43 jadis kernel: init: ssh main process (1393) terminated with status 255
Jan 27 18:51:44 jadis ntpd[1472]: ntpd exiting on signal 15
Jan 27 18:51:44 jadis ntpdate[1692]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:44 jadis ntpdate[1692]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:44 jadis ntpdate[1692]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:44 jadis ntpdate[1692]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:44 jadis ntpdate[1692]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Jan 27 18:51:44 jadis ntpdate[1692]: no servers can be used, exiting
Jan 27 18:51:44 jadis ntpd[1722]: ntpd 4.2.6p2 at 1.2194 Fri Sep  2 18:37:15 UTC 2011 (1)
Jan 27 18:51:44 jadis ntpd[1723]: proto: precision = 0.428 usec
Jan 27 18:51:44 jadis ntpd[1723]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Jan 27 18:51:44 jadis ntpd[1723]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen and drop on 1 v6wildcard :: UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 3 eth0 95.166.144.106 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 4 br0 192.168.1.1 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 5 eth0 fe80::22c:6eff:fe7a:7f43 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 6 br0 fe80::208:54ff:fe54:6960 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 7 sixxs 2001:16d8:ee00:2e::2 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 8 sixxs fe80::c0a8:101 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 9 sixxs fe80::5fa6:906a UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Listen normally on 10 lo ::1 UDP 123
Jan 27 18:51:44 jadis ntpd[1723]: Deferring DNS for 0.ubuntu.pool.ntp.org 1
Jan 27 18:51:44 jadis ntpd[1723]: Deferring DNS for 1.ubuntu.pool.ntp.org 1
Jan 27 18:51:44 jadis ntpd[1723]: Deferring DNS for 2.ubuntu.pool.ntp.org 1
Jan 27 18:51:44 jadis ntpd[1723]: Deferring DNS for 3.ubuntu.pool.ntp.org 1
Jan 27 18:51:44 jadis ntpd[1723]: Deferring DNS for ntp.ubuntu.com 1
Jan 27 18:51:46 jadis ntpd_intres[1725]: host name not found: 0.ubuntu.pool.ntp.org
Jan 27 18:51:46 jadis ntpd_intres[1725]: host name not found: 1.ubuntu.pool.ntp.org
Jan 27 18:51:46 jadis ntpd_intres[1725]: host name not found: 2.ubuntu.pool.ntp.org
Jan 27 18:51:46 jadis ntpd_intres[1725]: host name not found: 3.ubuntu.pool.ntp.org
Jan 27 18:51:46 jadis ntpd_intres[1725]: host name not found: ntp.ubuntu.com
Jan 27 18:51:47 jadis kernel: br0: port 1(eth1) entering forwarding state
Jan 27 18:51:48 jadis ntpd[1723]: ntpd exiting on signal 15
Jan 27 18:51:48 jadis ntpdate[1750]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:48 jadis ntpdate[1750]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:48 jadis ntpdate[1750]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:48 jadis ntpdate[1750]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2)
Jan 27 18:51:48 jadis ntpdate[1750]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Jan 27 18:51:48 jadis ntpdate[1750]: no servers can be used, exiting
Jan 27 18:51:48 jadis ntpd[1777]: ntpd 4.2.6p2 at 1.2194 Fri Sep  2 18:37:15 UTC 2011 (1)
Jan 27 18:51:48 jadis ntpd[1778]: proto: precision = 0.429 usec
Jan 27 18:51:48 jadis ntpd[1778]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16
Jan 27 18:51:48 jadis ntpd[1778]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen and drop on 1 v6wildcard :: UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 3 eth0 95.166.144.106 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 4 br0 192.168.1.1 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 5 eth0 fe80::22c:6eff:fe7a:7f43 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 6 br0 fe80::208:54ff:fe54:6960 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 7 sixxs 2001:16d8:ee00:2e::2 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 8 sixxs fe80::c0a8:101 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 9 sixxs fe80::5fa6:906a UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Listen normally on 10 lo ::1 UDP 123
Jan 27 18:51:48 jadis ntpd[1778]: Deferring DNS for 0.ubuntu.pool.ntp.org 1
Jan 27 18:51:48 jadis ntpd[1778]: Deferring DNS for 1.ubuntu.pool.ntp.org 1
Jan 27 18:51:48 jadis ntpd[1778]: Deferring DNS for 2.ubuntu.pool.ntp.org 1
Jan 27 18:51:48 jadis ntpd[1778]: Deferring DNS for 3.ubuntu.pool.ntp.org 1
Jan 27 18:51:48 jadis ntpd[1778]: Deferring DNS for ntp.ubuntu.com 1
Jan 27 18:51:50 jadis ntpd_intres[1780]: host name not found: 0.ubuntu.pool.ntp.org
Jan 27 18:51:50 jadis ntpd_intres[1780]: host name not found: 1.ubuntu.pool.ntp.org
Jan 27 18:51:50 jadis ntpd_intres[1780]: host name not found: 2.ubuntu.pool.ntp.org
Jan 27 18:51:50 jadis ntpd_intres[1780]: host name not found: 3.ubuntu.pool.ntp.org
Jan 27 18:51:50 jadis ntpd_intres[1780]: host name not found: ntp.ubuntu.com
Jan 27 18:52:10 jadis ntpd_intres[1474]: parent died before we finished, exiting
Jan 27 18:52:16 jadis ntpd_intres[1725]: parent died before we finished, exiting
Jan 27 18:52:53 jadis ntpd_intres[1780]: host name not found: 0.ubuntu.pool.ntp.org
Jan 27 18:52:53 jadis ntpd_intres[1780]: host name not found: 1.ubuntu.pool.ntp.org
Jan 27 18:52:53 jadis ntpd_intres[1780]: host name not found: 2.ubuntu.pool.ntp.org
Jan 27 18:52:53 jadis ntpd_intres[1780]: host name not found: 3.ubuntu.pool.ntp.org
Jan 27 18:52:53 jadis ntpd_intres[1780]: host name not found: ntp.ubuntu.com
Jan 27 18:53:38 jadis kernel: Netfilter messages via NETLINK v0.30.
Jan 27 18:53:38 jadis kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 27 18:53:38 jadis kernel: NF_TPROXY: Transparent proxy support initialized, version 4.1.0
Jan 27 18:53:38 jadis kernel: NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
Jan 27 18:53:38 jadis kernel: ctnetlink v0.93: registering with nfnetlink.
Jan 27 18:53:38 jadis kernel: ip_set: protocol 6
Jan 27 18:53:39 jadis kernel: ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
Jan 27 18:53:39 jadis kernel: xt_time: kernel timezone is +0100
Jan 27 18:53:40 jadis kernel: u32 classifier
Jan 27 18:53:40 jadis kernel:    Performance counters on
Jan 27 18:53:40 jadis kernel:    input device check on
Jan 27 18:53:40 jadis kernel:    Actions configured
Jan 27 18:53:41 jadis logger: Shorewall started
Jan 27 18:53:41 jadis uptimed: created bootid: 1327686677
Jan 27 18:53:42 jadis kernel: init: apport pre-start process (2242) terminated with status 1
Jan 27 18:53:42 jadis anacron[2282]: Anacron 2.3 started on 2012-01-27
Jan 27 18:53:42 jadis acpid: starting up with proc fs
Jan 27 18:53:42 jadis cron[2249]: (CRON) INFO (pidfile fd = 3)
Jan 27 18:53:42 jadis cron[2296]: (CRON) STARTUP (fork ok)
Jan 27 18:53:42 jadis kernel: init: apport post-stop process (2294) terminated with status 1
Jan 27 18:53:42 jadis anacron[2282]: Normal exit (0 jobs run)
Jan 27 18:53:42 jadis acpid: 1 rule loaded
Jan 27 18:53:42 jadis acpid: waiting for events: event logging is off
Jan 27 18:53:43 jadis cron[2296]: (CRON) INFO (Running @reboot jobs)
Jan 27 18:53:43 jadis named[2371]: starting BIND 9.7.3 -u bind -t /var/bind -c /etc/named.conf
Jan 27 18:53:43 jadis named[2371]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS='
Jan 27 18:53:43 jadis named[2371]: adjusted limit on open files from 4096 to 1048576
Jan 27 18:53:43 jadis named[2371]: found 1 CPU, using 1 worker thread
Jan 27 18:53:43 jadis named[2371]: using up to 4096 sockets
Jan 27 18:53:44 jadis named[2371]: loading configuration from '/etc/named.conf'
Jan 27 18:53:44 jadis named[2371]: using default UDP/IPv4 port range: [1024, 65535]
Jan 27 18:53:44 jadis named[2371]: using default UDP/IPv6 port range: [1024, 65535]
Jan 27 18:53:44 jadis named[2371]: listening on IPv6 interfaces, port 53
Jan 27 18:53:44 jadis named[2371]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 27 18:53:44 jadis named[2371]: listening on IPv4 interface eth0, 95.166.144.106#53
Jan 27 18:53:44 jadis named[2371]: listening on IPv4 interface br0, 192.168.1.1#53
Jan 27 18:53:44 jadis named[2371]: generating session key for dynamic DNS
Jan 27 18:53:44 jadis named[2371]: set up managed keys zone for view internal, file '3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys'
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 254.169.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 2.0.192.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 100.51.198.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 113.0.203.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 255.255.255.255.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: D.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 8.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 9.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: A.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: B.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view internal: 8.B.D.0.1.0.0.2.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: set up managed keys zone for view vpn, file 'ebf20cefc9169e0b714703d63d480c3e63c64a8535a13acf5a62ea66c5f0ea8c.mkeys'
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 254.169.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 2.0.192.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 100.51.198.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 113.0.203.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 255.255.255.255.IN-ADDR.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: D.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 8.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 9.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: A.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: B.E.F.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: automatic empty zone: view vpn: 8.B.D.0.1.0.0.2.IP6.ARPA
Jan 27 18:53:44 jadis named[2371]: set up managed keys zone for view external, file '3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys'
Jan 27 18:53:44 jadis named[2371]: command channel listening on 127.0.0.1#953
Jan 27 18:53:44 jadis named[2371]: logging channel 'default_debug' file 'data/named.run': file not found
Jan 27 18:53:44 jadis named[2371]: logging channel 'security_file' file '/var/log/named/security.log': file not found
Jan 27 18:53:44 jadis named[2371]: zone 0.in-addr.arpa/IN/internal: loaded serial 2008060602
Jan 27 18:53:44 jadis named[2371]: zone 10.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 127.in-addr.arpa/IN/internal: loaded serial 2008060602
Jan 27 18:53:44 jadis named[2371]: zone 16.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 17.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 18.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 19.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 20.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 21.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 22.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 23.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 24.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 25.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 26.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 27.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 28.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 29.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 30.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 31.172.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 168.192.in-addr.arpa/IN/internal: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 1.168.192.in-addr.arpa/IN/internal: loaded serial 2012011501
Jan 27 18:53:44 jadis named[2371]: zone 255.in-addr.arpa/IN/internal: loaded serial 2008060602
Jan 27 18:53:44 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Jan 27 18:53:44 jadis kernel: ADDRCONF(NETDEV_UP): virbr0: link is not ready
Jan 27 18:53:44 jadis avahi-daemon[1330]: New relevant interface virbr0.IPv4 for mDNS.
Jan 27 18:53:44 jadis avahi-daemon[1330]: Registering new address record for 192.168.122.1 on virbr0.IPv4.
Jan 27 18:53:44 jadis named[2371]: zone 162.90.48.86.in-addr.arpa/IN/internal: loaded serial 2011111902
Jan 27 18:53:44 jadis named[2371]: zone e.e.8.d.6.1.1.0.0.2.ip6.arpa/IN/internal: loaded serial 2011120401
Jan 27 18:53:44 jadis named[2371]: zone localhost/IN/internal: loaded serial 2008060602
Jan 27 18:53:44 jadis named[2371]: zone molgaard.org/IN/internal: loaded serial 2012011901
Jan 27 18:53:44 jadis named[2371]: managed-keys-zone ./IN/internal: loading from master file 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys failed: file not found
Jan 27 18:53:44 jadis named[2371]: managed-keys-zone ./IN/internal: loaded serial 0
Jan 27 18:53:44 jadis named[2371]: zone 0.in-addr.arpa/IN/vpn: loaded serial 2008060602
Jan 27 18:53:44 jadis named[2371]: zone 10.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 0.8.10.in-addr.arpa/IN/vpn: loaded serial 2011080401
Jan 27 18:53:44 jadis named[2371]: zone 127.in-addr.arpa/IN/vpn: loaded serial 2008060602
Jan 27 18:53:44 jadis named[2371]: zone 16.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 17.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 18.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 19.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 20.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 21.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 22.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 23.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 24.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 25.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 26.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 27.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 28.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 29.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 30.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 31.172.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 168.192.in-addr.arpa/IN/vpn: loaded serial 1
Jan 27 18:53:44 jadis named[2371]: zone 255.in-addr.arpa/IN/vpn: loaded serial 2008060602
Jan 27 18:53:44 jadis named[2371]: zone 162.90.48.86.in-addr.arpa/IN/vpn: loaded serial 2011111902
Jan 27 18:53:44 jadis named[2371]: zone e.e.8.d.6.1.1.0.0.2.ip6.arpa/IN/vpn: loaded serial 2010053001
Jan 27 18:53:44 jadis named[2371]: zone localhost/IN/vpn: loaded serial 2008060602
Jan 27 18:53:44 jadis named[2371]: zone molgaard.org/IN/vpn: loaded serial 2011080401
Jan 27 18:53:44 jadis named[2371]: managed-keys-zone ./IN/vpn: loading from master file ebf20cefc9169e0b714703d63d480c3e63c64a8535a13acf5a62ea66c5f0ea8c.mkeys failed: file not found
Jan 27 18:53:44 jadis named[2371]: managed-keys-zone ./IN/vpn: loaded serial 0
Jan 27 18:53:44 jadis dnsmasq[2447]: started, version 2.57 cachesize 150
Jan 27 18:53:44 jadis dnsmasq[2447]: compile time options: IPv6 GNU-getopt DBus I18N DHCP TFTP IDN
Jan 27 18:53:44 jadis dnsmasq-dhcp[2447]: DHCP, IP range 192.168.122.2 -- 192.168.122.254, lease time 1h
Jan 27 18:53:44 jadis dnsmasq[2447]: reading /etc/resolv.conf
Jan 27 18:53:44 jadis dnsmasq[2447]: using nameserver 127.0.0.1#53
Jan 27 18:53:44 jadis dnsmasq[2447]: read /etc/hosts - 9 addresses
Jan 27 18:53:44 jadis named[2371]: zone 106.144.166.95.in-addr.arpa/IN/external: loaded serial 2011122501
Jan 27 18:53:44 jadis named[2371]: zone 201.154.166.95.in-addr.arpa/IN/external: loaded serial 2011080401
Jan 27 18:53:44 jadis named[2371]: zone e.e.8.d.6.1.1.0.0.2.ip6.arpa/IN/external: loaded serial 2010053001
Jan 27 18:53:44 jadis named[2371]: zone molgaard.org/IN/external: loaded serial 2011122501
Jan 27 18:53:44 jadis named[2371]: managed-keys-zone ./IN/external: loading from master file 3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys failed: file not found
Jan 27 18:53:44 jadis named[2371]: managed-keys-zone ./IN/external: loaded serial 0
Jan 27 18:53:44 jadis named[2371]: running
Jan 27 18:53:44 jadis named[2371]: isc_log_open 'data/named.run' failed: file not found
Jan 27 18:53:45 jadis /etc/mysql/debian-start[2523]: Upgrading MySQL tables if necessary.
Jan 27 18:53:45 jadis ovpn-jadis[2519]: OpenVPN 2.2.0 i686-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [eurephia] [MH] [PF_INET6] [IPv6 payload 20110424-2 (2.2RC2)] built on Jul  4 2011
Jan 27 18:53:45 jadis ovpn-jadis[2519]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Jan 27 18:53:45 jadis /etc/mysql/debian-start[2526]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Jan 27 18:53:45 jadis /etc/mysql/debian-start[2526]: Looking for 'mysql' as: /usr/bin/mysql
Jan 27 18:53:45 jadis /etc/mysql/debian-start[2526]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Jan 27 18:53:45 jadis /etc/mysql/debian-start[2526]: This installation of MySQL is already upgraded to 5.1.58, use --force if you still need to run mysql_upgrade
Jan 27 18:53:45 jadis /etc/mysql/debian-start[2533]: Checking for insecure root accounts.
Jan 27 18:53:45 jadis /etc/mysql/debian-start[2537]: Triggering myisam-recover for all MyISAM tables
Jan 27 18:53:46 jadis ovpn-jadis[2519]: Diffie-Hellman initialized with 2048 bit key
Jan 27 18:53:46 jadis ovpn-jadis[2519]: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Jan 27 18:53:46 jadis ovpn-jadis[2519]: Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Jan 27 18:53:46 jadis ovpn-jadis[2519]: Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Jan 27 18:53:46 jadis ovpn-jadis[2519]: TLS-Auth MTU parms [ L:1574 D:166 EF:66 EB:0 ET:0 EL:0 ]
Jan 27 18:53:46 jadis ovpn-jadis[2519]: Socket Buffers: R=[114688->131072] S=[114688->131072]
Jan 27 18:53:46 jadis kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 27 18:53:46 jadis kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan 27 18:53:46 jadis ovpn-jadis[2519]: TUN/TAP device tap0 opened
Jan 27 18:53:46 jadis ovpn-jadis[2519]: TUN/TAP TX queue length set to 100
Jan 27 18:53:46 jadis ovpn-jadis[2519]: do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Jan 27 18:53:46 jadis ovpn-jadis[2519]: /sbin/ifconfig tap0 10.8.0.1 netmask 255.255.255.0 mtu 1500 broadcast 10.8.0.255
Jan 27 18:53:46 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface tap0.IPv4 with address 10.8.0.1.
Jan 27 18:53:46 jadis avahi-daemon[1330]: New relevant interface tap0.IPv4 for mDNS.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Registering new address record for 10.8.0.1 on tap0.IPv4.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Withdrawing address record for 10.8.0.1 on tap0.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Leaving mDNS multicast group on interface tap0.IPv4 with address 10.8.0.1.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Interface tap0.IPv4 no longer relevant for mDNS.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface tap0.IPv4 with address 10.8.0.1.
Jan 27 18:53:46 jadis avahi-daemon[1330]: New relevant interface tap0.IPv4 for mDNS.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Registering new address record for 10.8.0.1 on tap0.IPv4.
Jan 27 18:53:46 jadis ovpn-jadis[2519]: /etc/openvpn/jadis.up tap0 1500 1574 10.8.0.1 255.255.255.0 init
Jan 27 18:53:46 jadis ovpn-jadis[2519]: Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Jan 27 18:53:46 jadis ovpn-jadis[2558]: GID set to nogroup
Jan 27 18:53:46 jadis ovpn-jadis[2558]: UID set to nobody
Jan 27 18:53:46 jadis ovpn-jadis[2558]: UDPv4 link local (bound): [undef]
Jan 27 18:53:46 jadis ovpn-jadis[2558]: UDPv4 link remote: [undef]
Jan 27 18:53:46 jadis ovpn-jadis[2558]: MULTI: multi_init called, r=256 v=256
Jan 27 18:53:46 jadis ovpn-jadis[2558]: IFCONFIG POOL: base=10.8.0.2 size=253, ipv6=0
Jan 27 18:53:46 jadis ovpn-jadis[2558]: ifconfig_pool_read(), in='tommelise,10.8.0.2', TODO: IPv6
Jan 27 18:53:46 jadis ovpn-jadis[2558]: succeeded -> ifconfig_pool_set()
Jan 27 18:53:46 jadis ovpn-jadis[2558]: IFCONFIG POOL LIST
Jan 27 18:53:46 jadis ovpn-jadis[2558]: tommelise,10.8.0.2
Jan 27 18:53:46 jadis ovpn-jadis[2558]: Initialization Sequence Completed
Jan 27 18:53:46 jadis kernel: device tap0 entered promiscuous mode
Jan 27 18:53:46 jadis kernel: br0: port 2(tap0) entering forwarding state
Jan 27 18:53:46 jadis kernel: br0: port 2(tap0) entering forwarding state
Jan 27 18:53:46 jadis avahi-daemon[1330]: Withdrawing address record for 10.8.0.1 on tap0.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Leaving mDNS multicast group on interface tap0.IPv4 with address 10.8.0.1.
Jan 27 18:53:46 jadis avahi-daemon[1330]: Interface tap0.IPv4 no longer relevant for mDNS.
Jan 27 18:53:46 jadis bbackupd[2634]: NOTICE: Box Backup Client v0.11rc8+, (c) Ben Summers and contributors 2003-2011
Jan 27 18:53:47 jadis bbackupd[2640]: NOTICE: Starting daemon, version: 0.11rc8+
Jan 27 18:53:47 jadis bbackupd[2640]: NOTICE: Using configuration file: /etc/boxbackup/bbackupd.conf
Jan 27 18:53:47 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface tap0.IPv6 with address 2001:16d8:ee1e:2::1.
Jan 27 18:53:47 jadis avahi-daemon[1330]: New relevant interface tap0.IPv6 for mDNS.
Jan 27 18:53:47 jadis avahi-daemon[1330]: Registering new address record for 2001:16d8:ee1e:2::1 on tap0.*.
Jan 27 18:53:47 jadis bbackupd[2640]: NOTICE: Beginning scan of local files
Jan 27 18:53:47 jadis bbstored[2648]: NOTICE: Box Backup Store Server v0.11rc8+, (c) Ben Summers and contributors 2003-2011
Jan 27 18:53:47 jadis bbstored[2653]: NOTICE: Starting daemon, version: 0.11rc8+
Jan 27 18:53:47 jadis bbstored[2653]: NOTICE: Using configuration file: /etc/boxbackup/bbstored.conf
Jan 27 18:53:50 jadis bbstored[3032]: NOTICE: Handling incoming connection from 192.168.1.1 port 57452
Jan 27 18:53:50 jadis bbstored client=0x075ab23e[3032]: NOTICE: Login from Client ID 0x075ab23e (name=): Read/Write from 192.168.1.1 port 57452
Jan 27 18:53:51 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 18:53:51 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 18:53:51 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 18:53:51 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 18:53:51 jadis kernel: cfg80211: Calling CRDA for country: DK
Jan 27 18:53:51 jadis kernel: cfg80211: Regulatory domain changed to country: DK
Jan 27 18:53:51 jadis kernel: cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jan 27 18:53:51 jadis kernel: cfg80211:     (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 27 18:53:51 jadis kernel: cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 27 18:53:51 jadis kernel: cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Jan 27 18:53:51 jadis kernel: cfg80211:     (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Jan 27 18:53:51 jadis kernel: Intel AES-NI instructions are not detected.
Jan 27 18:53:51 jadis kernel: padlock_aes: VIA PadLock not detected.
Jan 27 18:53:51 jadis dhcpd: Warning: subnet 10.8.0.0/16 overlaps subnet 10.0.0.0/8
Jan 27 18:53:51 jadis dhcpd: Warning: subnet 10.8.0.0/16 overlaps subnet 10.0.0.0/8
Jan 27 18:53:51 jadis dhcpd: Wrote 0 deleted host decls to leases file.
Jan 27 18:53:51 jadis dhcpd: Wrote 0 new dynamic host decls to leases file.
Jan 27 18:53:51 jadis dhcpd: Wrote 9 leases to leases file.
Jan 27 18:53:51 jadis dhcpd: 
Jan 27 18:53:51 jadis dhcpd: No subnet declaration for virbr0 (192.168.122.1).
Jan 27 18:53:51 jadis dhcpd: ** Ignoring requests on virbr0.  If this is not what
Jan 27 18:53:51 jadis dhcpd:    you want, please write a subnet declaration
Jan 27 18:53:51 jadis dhcpd:    in your dhcpd.conf file for the network segment
Jan 27 18:53:51 jadis dhcpd:    to which interface virbr0 is attached. **
Jan 27 18:53:51 jadis dhcpd: 
Jan 27 18:53:51 jadis dhcpd: 
Jan 27 18:53:51 jadis dhcpd: No subnet declaration for eth0 (95.166.144.106).
Jan 27 18:53:51 jadis dhcpd: ** Ignoring requests on eth0.  If this is not what
Jan 27 18:53:51 jadis dhcpd:    you want, please write a subnet declaration
Jan 27 18:53:51 jadis dhcpd:    in your dhcpd.conf file for the network segment
Jan 27 18:53:51 jadis dhcpd:    to which interface eth0 is attached. **
Jan 27 18:53:51 jadis dhcpd: 
Jan 27 18:53:54 jadis named[2371]: client 173.244.206.26#24921: view external: transfer of 'molgaard.org/IN': AXFR started
Jan 27 18:53:54 jadis named[2371]: client 173.244.206.26#24921: view external: transfer of 'molgaard.org/IN': AXFR ended
Jan 27 18:53:54 jadis upnpd[3197]: 0xb75be6c0 UPnP SDK Successfully Initialized.
Jan 27 18:53:54 jadis upnpd[3197]: 0xb75be6c0 Successfully set the Web Server Root Directory.
Jan 27 18:53:54 jadis upnpd[3197]: 0xb75be6c0 IGD root device successfully registered.
Jan 27 18:53:54 jadis lpd[3213]: restarted
Jan 27 18:53:55 jadis upnpd[3197]: 0xb75be6c0 Advertisements Sent.  Listening for requests ... 
Jan 27 18:53:56 jadis dovecot: master: Dovecot v2.0.13 starting up (core dumps disabled)
Jan 27 18:53:56 jadis postfix/master[3297]: fatal: bind 0.0.0.0 port 25: Address already in use
Jan 27 18:53:56 jadis kernel: tap0: no IPv6 routers present
Jan 27 18:53:57 jadis smartd[3321]: smartd 5.41 2011-06-09 r3365 [i686-linux-3.0.18-sune-1] (local build)
Jan 27 18:53:57 jadis smartd[3321]: Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
Jan 27 18:53:57 jadis smartd[3321]: Opened configuration file /etc/smartd.conf
Jan 27 18:53:57 jadis smartd[3321]: Drive: DEVICESCAN, implied '-a' Directive on line 22 of file /etc/smartd.conf
Jan 27 18:53:57 jadis smartd[3321]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
Jan 27 18:53:57 jadis smartd[3321]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Jan 27 18:53:57 jadis smartd[3321]: Device: /dev/sda [SAT], opened
Jan 27 18:53:57 jadis smartd[3321]: Device: /dev/sda [SAT], Hitachi HDP725025GLA380, S/N:GEK234RS0VJAHA, WWN:5-000cca-355cc0efb, FW:GM2OA5CA, 250 GB
Jan 27 18:53:57 jadis smartd[3321]: Device: /dev/sda [SAT], found in smartd database.
Jan 27 18:53:58 jadis smartd[3321]: Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Jan 27 18:53:59 jadis smartd[3321]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK234RS0VJAHA.ata.state
Jan 27 18:53:59 jadis smartd[3321]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Jan 27 18:53:59 jadis smartd[3321]: Device: /dev/sdb [SAT], opened
Jan 27 18:53:59 jadis smartd[3321]: Device: /dev/sdb [SAT], Hitachi HDP725025GLA380, S/N:GEK230RBR65H4A, WWN:5-000cca-329c2ced4, FW:GM2OA52A, 250 GB
Jan 27 18:53:59 jadis smartd[3321]: Device: /dev/sdb [SAT], found in smartd database.
Jan 27 18:54:00 jadis smartd[3321]: Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Jan 27 18:54:00 jadis smartd[3321]: Device: /dev/sdb [SAT], state read from /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK230RBR65H4A.ata.state
Jan 27 18:54:00 jadis smartd[3321]: Device: /dev/sdc, type changed from 'scsi' to 'sat'
Jan 27 18:54:00 jadis smartd[3321]: Device: /dev/sdc [SAT], opened
Jan 27 18:54:00 jadis smartd[3321]: Device: /dev/sdc [SAT], Hitachi HDP725025GLA380, S/N:GEK230RBR5NJTA, WWN:5-000cca-329c292f7, FW:GM2OA52A, 250 GB
Jan 27 18:54:00 jadis smartd[3321]: Device: /dev/sdc [SAT], found in smartd database.
Jan 27 18:54:01 jadis smartd[3321]: Device: /dev/sdc [SAT], is SMART capable. Adding to "monitor" list.
Jan 27 18:54:01 jadis smartd[3321]: Device: /dev/sdc [SAT], state read from /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK230RBR5NJTA.ata.state
Jan 27 18:54:01 jadis smartd[3321]: Device: /dev/sdd, type changed from 'scsi' to 'sat'
Jan 27 18:54:01 jadis smartd[3321]: Device: /dev/sdd [SAT], opened
Jan 27 18:54:01 jadis smartd[3321]: Device: /dev/sdd [SAT], Hitachi HDP725025GLA380, S/N:GEK230RBR5RM2A, WWN:5-000cca-329c29ac0, FW:GM2OA52A, 250 GB
Jan 27 18:54:01 jadis smartd[3321]: Device: /dev/sdd [SAT], found in smartd database.
Jan 27 18:54:01 jadis kernel: br0: port 2(tap0) entering forwarding state
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sdd [SAT], is SMART capable. Adding to "monitor" list.
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sdd [SAT], state read from /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK230RBR5RM2A.ata.state
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde, type changed from 'scsi' to 'sat'
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde [SAT], opened
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde [SAT], QUANTUM FIREBALLP AS40.0, S/N:194100536603, FW:A1Y.1500, 40.0 GB
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde [SAT], found in smartd database.
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde [SAT], no SMART Self-test Log, ignoring -l selftest (override with -T permissive)
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde [SAT], no SMART Error Log, ignoring -l error (override with -T permissive)
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde [SAT], is SMART capable. Adding to "monitor" list.
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sde [SAT], state read from /var/lib/smartmontools/smartd.QUANTUM_FIREBALLP_AS40_0-194100536603.ata.state
Jan 27 18:54:02 jadis smartd[3321]: Monitoring 5 ATA and 0 SCSI devices
Jan 27 18:54:02 jadis smartd[3321]: Device: /dev/sda [SAT], offline data collection was suspended by an interrupting command from host (auto:on)
Jan 27 18:54:03 jadis smartd[3321]: Device: /dev/sdb [SAT], offline data collection was suspended by an interrupting command from host (auto:on)
Jan 27 18:54:04 jadis smartd[3321]: Device: /dev/sdc [SAT], offline data collection was suspended by an interrupting command from host (auto:on)
Jan 27 18:54:04 jadis smartd[3321]: Device: /dev/sdd [SAT], offline data collection was suspended by an interrupting command from host (auto:on)
Jan 27 18:54:05 jadis smartd[3321]: Device: /dev/sde [SAT], Failed SMART usage Attribute: 9 Power_On_Hours.
Jan 27 18:54:05 jadis smartd[3321]: Device: /dev/sda [SAT], state written to /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK234RS0VJAHA.ata.state
Jan 27 18:54:05 jadis smartd[3321]: Device: /dev/sdb [SAT], state written to /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK230RBR65H4A.ata.state
Jan 27 18:54:05 jadis smartd[3321]: Device: /dev/sdc [SAT], state written to /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK230RBR5NJTA.ata.state
Jan 27 18:54:05 jadis smartd[3321]: Device: /dev/sdd [SAT], state written to /var/lib/smartmontools/smartd.Hitachi_HDP725025GLA380-GEK230RBR5RM2A.ata.state
Jan 27 18:54:05 jadis smartd[3321]: Device: /dev/sde [SAT], state written to /var/lib/smartmontools/smartd.QUANTUM_FIREBALLP_AS40_0-194100536603.ata.state
Jan 27 18:54:05 jadis smartd[3323]: smartd has fork()ed into background mode. New PID=3323.
Jan 27 18:54:05 jadis smartd[3323]: file /var/run/smartd.pid written containing PID 3323
Jan 27 18:54:06 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 18:54:08 jadis nagios3: Nagios 3.2.3 starting... (PID=3478)
Jan 27 18:54:08 jadis nagios3: Local time is Fri Jan 27 18:54:08 CET 2012
Jan 27 18:54:08 jadis nagios3: LOG VERSION: 2.0
Jan 27 18:54:08 jadis nagios3: Warning: Host 'gateway' has no services associated with it!
Jan 27 18:54:09 jadis nagios3: Finished daemonizing... (New PID=3479)
Jan 27 18:54:21 jadis logger: Shorewall restarted
Jan 27 18:54:23 jadis avahi-daemon[1330]: Leaving mDNS multicast group on interface br0.IPv6 with address fe80::208:54ff:fe54:6960.
Jan 27 18:54:23 jadis avahi-daemon[1330]: Joining mDNS multicast group on interface br0.IPv6 with address 2001:16d8:ee1e::2.
Jan 27 18:54:23 jadis avahi-daemon[1330]: Registering new address record for 2001:16d8:ee1e::2 on br0.*.
Jan 27 18:54:23 jadis avahi-daemon[1330]: Withdrawing address record for fe80::208:54ff:fe54:6960 on br0.
Jan 27 18:54:40 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 18:54:40 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 18:54:40 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 18:54:40 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 18:54:40 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E4AF-00000000
Jan 27 18:54:40 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 18:54:41 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 18:54:41 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 18:54:49 jadis dbus[1315]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jan 27 18:54:49 jadis dbus[1315]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Jan 27 18:54:49 jadis bbstored[4112]: NOTICE: Handling incoming connection from 95.166.144.82 port 53363
Jan 27 18:54:49 jadis polkitd[4109]: started daemon version 0.102 using authority implementation `local' version `0.102'
Jan 27 18:54:49 jadis dbus[1315]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 27 18:54:49 jadis dbus[1315]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Jan 27 18:54:49 jadis bbstored client=0x075ab23f[4112]: NOTICE: Login from Client ID 0x075ab23f (name=): Read/Write from 95.166.144.82 port 53363
Jan 27 18:54:55 jadis ntpd_intres[1780]: DNS 0.ubuntu.pool.ntp.org -> 169.229.70.64
Jan 27 18:54:55 jadis ntpd_intres[1780]: DNS 1.ubuntu.pool.ntp.org -> 216.45.57.38
Jan 27 18:54:55 jadis ntpd_intres[1780]: DNS 2.ubuntu.pool.ntp.org -> 2600:3c00::2:b401
Jan 27 18:54:55 jadis ntpd_intres[1780]: DNS 3.ubuntu.pool.ntp.org -> 199.4.29.166
Jan 27 18:54:55 jadis ntpd_intres[1780]: DNS ntp.ubuntu.com -> 91.189.94.4
Jan 27 18:54:55 jadis ntpd[1778]: Listen normally on 11 virbr0 192.168.122.1 UDP 123
Jan 27 18:54:55 jadis ntpd[1778]: Listen normally on 12 tap0 fe80::2c66:1bff:fe16:ff76 UDP 123
Jan 27 18:54:55 jadis ntpd[1778]: Listen normally on 13 br0 2001:16d8:ee1e::2 UDP 123
Jan 27 18:54:55 jadis ntpd[1778]: Listen normally on 14 tap0 2001:16d8:ee1e:2::1 UDP 123
Jan 27 18:54:55 jadis ntpd[1778]: new interface(s) found: waking up resolver
Jan 27 18:55:21 jadis kernel: process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.default.retrans_time; Use net.ipv6.neigh.default.retrans_time_ms instead.
Jan 27 18:55:41 jadis bbstored client=0x075ab23f[4112]: NOTICE: Session finished for Client ID 0x075ab23f (name=)
Jan 27 18:55:41 jadis bbstored client=0x075ab23f[4112]: NOTICE: Connection statistics for 0x075ab23f (name=): IN=11634 OUT=635241 NET_IN=-623607 TOTAL=646875
Jan 27 18:55:53 jadis radvd[4461]: version 1.8.3 started
Jan 27 18:56:15 jadis bbstored[4690]: NOTICE: Handling incoming connection from 95.166.144.82 port 53392
Jan 27 18:56:15 jadis bbstored client=0x075ab23f[4690]: NOTICE: Login from Client ID 0x075ab23f (name=): Read/Write from 95.166.144.82 port 53392
Jan 27 18:56:17 jadis bbackupd[2640]: WARNING: Found conflicting parent ID for file ID 1636 (/var/lib/dpkg/info/linux-headers-3.0.18-sune-1.list): expected 18792 but found 18784 (same directory used in two different locations?)
Jan 27 18:56:17 jadis bbackupd[2640]: WARNING: Found conflicting parent ID for file ID 200 (/var/lib/dpkg/info/linux-image-3.0.18-sune-1.list): expected 18792 but found 11813 (same directory used in two different locations?)
Jan 27 18:56:42 jadis bbstored client=0x075ab23f[4690]: NOTICE: Session finished for Client ID 0x075ab23f (name=)
Jan 27 18:56:42 jadis bbstored client=0x075ab23f[4690]: NOTICE: Connection statistics for 0x075ab23f (name=): IN=11634 OUT=635241 NET_IN=-623607 TOTAL=646875
Jan 27 18:56:50 jadis bbstored client=0x075ab23e[3032]: NOTICE: Session finished for Client ID 0x075ab23e (name=)
Jan 27 18:56:50 jadis bbstored client=0x075ab23e[3032]: NOTICE: Connection statistics for 0x075ab23e (name=): IN=661693 OUT=2096509 NET_IN=-1434816 TOTAL=2758202
Jan 27 18:56:50 jadis bbackupd[2640]: NOTICE: Finished scan of local files
Jan 27 18:56:50 jadis bbackupd[2640]: NOTICE: File statistics: total file size uploaded 888850, bytes already on server 48947, encoded size 608516, 25 files uploaded, 11 dirs created
Jan 27 18:57:10 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 18:57:10 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 18:57:10 jadis kernel: device wlan0 left promiscuous mode
Jan 27 18:57:10 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 18:57:10 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:10 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:10 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:10 jadis avahi-daemon[1330]: Withdrawing workstation service for mon.wlan0.
Jan 27 18:57:10 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:10 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:10 jadis kernel: ieee80211 phy0: device now idle
Jan 27 18:57:10 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:10 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:10 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:18 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:18 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:18 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 18:57:18 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:18 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:18 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:18 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:18 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 18:57:18 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:18 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:18 jadis radvd[4463]: attempting to reread config file
Jan 27 18:57:18 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 18:57:18 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 18:57:18 jadis radvd[4463]: resuming normal operation
Jan 27 18:57:19 jadis kernel: wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
Jan 27 18:57:22 jadis kernel: last message repeated 2 times
Jan 27 18:57:22 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 18:57:22 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 18:57:22 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 18:57:22 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 18:57:22 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E57E-00000000
Jan 27 18:57:22 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 18:57:33 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:05:51 jadis bbackupd[2640]: NOTICE: Terminating daemon
Jan 27 19:05:56 jadis bbstored/hk[2654]: NOTICE: Terminating daemon
Jan 27 19:05:56 jadis bbstored[2653]: NOTICE: Terminating daemon
Jan 27 19:06:38 jadis kernel: ath: received PCI FATAL interrupt
Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:38 jadis kernel: ------------[ cut here ]------------
Jan 27 19:06:38 jadis kernel: WARNING: at drivers/net/wireless/ath/ath9k/recv.c:528 ath_stoprecv+0xbc/0xe0 [ath9k]()
Jan 27 19:06:38 jadis kernel: Hardware name: 8366-8233
Jan 27 19:06:38 jadis kernel: Modules linked in: cryptd aes_i586 aes_generic ip6table_filter tun xt_CHECKSUM xt_TCPMSS act_police cls_flow cls_fw cls_u32 sch_tbf sch_prio sch_htb sch_hfsc sch_ingress sch_sfq xt_time xt_connlimit xt_realm xt_addrtype iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah xt_set ip_set nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp 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_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY nf_tproxy_core ip6_tables nf_defrag_ipv6 xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt
Jan 27 19:06:38 jadis kernel: _connmark xt_CLASSIFY xt_AUDIT ipt_LOG iptable_nat nf_nat iptable_mangle nfnetlink sit tunnel4 reiserfs bridge ipv6 stp llc arc4 snd_cs4236 snd_wss_lib snd_via82xx snd_ac97_codec snd_opl3_lib ppdev snd_hwdep ac97_bus ath9k snd_pcm mac80211 snd_timer ath9k_common ath9k_hw snd_page_alloc snd_mpu401 i2c_viapro snd_mpu401_uart snd_rawmidi ath via_ircc snd_seq_device irda snd cfg80211 soundcore crc_ccitt ns558 gameport parport_pc hwmon_vid hwmon lp parport 8139too ata_generic pata_acpi 8139cp sundance pata_via sata_sil mii floppy raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear
Jan 27 19:06:38 jadis kernel: Pid: 4298, comm: java Not tainted 3.0.18-sune-1 #3
Jan 27 19:06:38 jadis kernel: Call Trace:
Jan 27 19:06:38 jadis kernel: [<c0431086>] warn_slowpath_common+0x63/0x78
Jan 27 19:06:38 jadis kernel: [<f851eaab>] ? ath_stoprecv+0xbc/0xe0 [ath9k]
Jan 27 19:06:38 jadis kernel: [<c04310aa>] warn_slowpath_null+0xf/0x13
Jan 27 19:06:38 jadis kernel: [<f851eaab>] ath_stoprecv+0xbc/0xe0 [ath9k]
Jan 27 19:06:38 jadis kernel: [<f851d782>] ath_reset+0x64/0x17c [ath9k]
Jan 27 19:06:38 jadis kernel: [<c07771e1>] ? _raw_spin_unlock_irqrestore+0x12/0x15
Jan 27 19:06:38 jadis kernel: [<f851d9ef>] ath9k_tasklet+0x27/0x133 [ath9k]
Jan 27 19:06:38 jadis kernel: [<c0435308>] tasklet_action+0x65/0xa7
Jan 27 19:06:38 jadis kernel: [<c04355e0>] __do_softirq+0x6c/0xe6
Jan 27 19:06:38 jadis kernel: [<c0435574>] ? local_bh_enable+0xa/0xa
Jan 27 19:06:38 jadis kernel: <IRQ>  [<c04357b8>] ? irq_exit+0x35/0x84
Jan 27 19:06:38 jadis kernel: [<c0403a78>] ? do_IRQ+0x6c/0x80
Jan 27 19:06:38 jadis kernel: [<c077be69>] ? common_interrupt+0x29/0x30
Jan 27 19:06:38 jadis kernel: ---[ end trace 46bdcea34024800a ]---
Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:39 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:39 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:40 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:40 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:40 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:41 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:41 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:41 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:42 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:42 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:42 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:43 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:43 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:45 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:45 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:45 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:46 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:46 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:47 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:47 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:47 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:06:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:50 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:54 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:54 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:54 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:54 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:54 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:54 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:06:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:58 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:58 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:58 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:06:58 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:58 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:58 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:59 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:00 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:01 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:02 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
Jan 27 19:07:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:03 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
Jan 27 19:07:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:05 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:05 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:06 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:06 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:06 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:07 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:07:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:07 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:07 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:08 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:08 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:08 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
Jan 27 19:07:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:17 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
Jan 27 19:07:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:20 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:21 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:21 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:22 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: deauthenticated due to local deauth request
Jan 27 19:07:22 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:07:22 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:07:22 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:07:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:26 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:26 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:26 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:26 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:07:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:07:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:31 jadis kernel: device wlan0 left promiscuous mode
Jan 27 19:07:31 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:07:31 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:31 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:31 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:31 jadis avahi-daemon[1330]: Withdrawing workstation service for mon.wlan0.
Jan 27 19:07:31 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:31 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:31 jadis kernel: ieee80211 phy0: device now idle
Jan 27 19:07:31 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:31 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:31 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:07:31 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:07:31 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:31 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:07:31 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:07:31 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:31 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:39 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:39 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:39 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 19:07:39 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:39 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:39 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:39 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:39 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 19:07:39 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:39 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:39 jadis radvd[4463]: attempting to reread config file
Jan 27 19:07:39 jadis radvd[4463]: resuming normal operation
Jan 27 19:07:39 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:07:39 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:07:42 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:07:42 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:07:42 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:07:42 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:07:42 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E7EB-00000000
Jan 27 19:07:42 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:07:42 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 19:07:42 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 19:07:54 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:08:53 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:08:53 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:09:01 jadis CRON[6082]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Jan 27 19:09:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:09:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:09:05 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:09:05 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:09:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E7EB-00000001
Jan 27 19:09:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:09:05 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 19:09:05 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 19:10:44 jadis kernel: ath: received PCI FATAL interrupt
Jan 27 19:10:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:45 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:45 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:45 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:46 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:46 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:47 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:47 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:47 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:10:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:50 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:50 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:10:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:10:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:54 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:54 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:54 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:54 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:54 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:10:54 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:10:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:10:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:57 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:10:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:57 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:57 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:10:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:58 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:58 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:58 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:58 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:58 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:58 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:59 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:59 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:10:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:10:59 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:10:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:10:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:00 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:11:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:00 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:00 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:01 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:01 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:01 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:02 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:02 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:02 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:03 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:03 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:05 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:05 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:05 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:06 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:07 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:17 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:17 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:17 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:11:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:18 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:18 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:20 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:20 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:20 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:20 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:20 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:20 jadis avahi-daemon[1330]: Withdrawing workstation service for mon.wlan0.
Jan 27 19:11:20 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:20 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:20 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:11:20 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:11:20 jadis kernel: device wlan0 left promiscuous mode
Jan 27 19:11:20 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:11:20 jadis kernel: ieee80211 phy0: device now idle
Jan 27 19:11:20 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:20 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:11:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:11:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:11:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:11:20 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:20 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:28 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:28 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:28 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 19:11:28 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:28 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:28 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:28 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:28 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 19:11:28 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:28 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:28 jadis radvd[4463]: attempting to reread config file
Jan 27 19:11:28 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:11:28 jadis radvd[4463]: resuming normal operation
Jan 27 19:11:28 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:11:33 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:11:33 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:11:33 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:11:33 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:11:33 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E8D0-00000000
Jan 27 19:11:33 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:11:38 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:11:38 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:11:38 jadis kernel: wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
Jan 27 19:11:43 jadis kernel: last message repeated 9 times
Jan 27 19:11:43 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:11:45 jadis kernel: net_ratelimit: 2 callbacks suppressed
Jan 27 19:11:45 jadis kernel: wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
Jan 27 19:11:52 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:11:52 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:11:52 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:11:52 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:11:52 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E8D0-00000001
Jan 27 19:11:52 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:11:52 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 19:11:52 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 19:12:01 jadis kernel: ath: received PCI FATAL interrupt
Jan 27 19:12:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:01 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:01 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:02 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:02 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:03 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:03 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:03 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:05 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:05 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:06 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:06 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:06 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:07 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:07 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:07 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:08 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:08 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:08 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:12:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:12:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:17 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:17 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:17 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:18 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:18 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:20 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:20 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:20 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:21 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:21 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:21 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:22 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:22 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:23 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:23 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:23 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:24 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:24 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:24 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:25 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:25 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:25 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:26 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:26 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:26 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:26 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:26 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:26 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:27 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:27 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:27 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:28 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:28 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:28 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:29 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:29 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:29 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:30 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:30 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:30 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:31 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:31 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:31 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:31 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:31 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:31 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:32 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:32 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:32 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:32 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:32 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:32 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:32 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:32 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:33 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:33 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:33 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:33 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:33 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:33 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:33 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:33 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:33 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:34 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:34 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:34 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:34 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:34 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:34 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:34 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:34 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:34 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:35 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:35 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:35 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:35 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:35 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:35 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:35 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:35 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:35 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:36 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:36 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:36 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:36 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:36 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:36 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:37 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:37 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:37 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:37 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:37 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:37 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:37 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:37 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:37 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:38 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:38 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:38 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:39 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:39 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:40 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:41 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:42 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:43 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:44 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:12:44 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:12:44 jadis kernel: device wlan0 left promiscuous mode
Jan 27 19:12:44 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:12:44 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:44 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:44 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:44 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:44 jadis avahi-daemon[1330]: Withdrawing workstation service for mon.wlan0.
Jan 27 19:12:44 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:44 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:44 jadis kernel: ieee80211 phy0: device now idle
Jan 27 19:12:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:12:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:12:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:12:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:12:44 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:44 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:52 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:52 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:52 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 19:12:52 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:52 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:52 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:52 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:52 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 19:12:52 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:52 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:52 jadis radvd[4463]: attempting to reread config file
Jan 27 19:12:52 jadis radvd[4463]: resuming normal operation
Jan 27 19:12:52 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:12:52 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:13:01 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:13:01 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:13:01 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:13:01 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:13:01 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E924-00000000
Jan 27 19:13:01 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:13:01 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 19:13:01 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 19:13:07 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:13:08 jadis kernel: ath: received PCI FATAL interrupt
Jan 27 19:13:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
Jan 27 19:13:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:08 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:09 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:10 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:11 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:15 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:16 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:20 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:20 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:21 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:21 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:21 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:22 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:22 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:22 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:22 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:22 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:23 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:23 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:23 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:23 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:23 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:24 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:24 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:24 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:24 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:24 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:25 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:25 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:25 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:25 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:26 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:26 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:26 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:26 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:26 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:26 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:26 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:26 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:26 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:27 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:27 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:27 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:27 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:27 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:28 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:28 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:28 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:28 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:28 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:29 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:29 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:29 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:29 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:29 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:30 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:30 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:30 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:30 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:31 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:31 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:31 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:31 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:31 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:31 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:31 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:31 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:31 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:32 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:32 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:32 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:32 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:32 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:32 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:32 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:32 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:32 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:33 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:33 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:33 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:33 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:33 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:33 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:33 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:34 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:34 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:34 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:34 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:34 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:34 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:34 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:35 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:35 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:35 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:35 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:36 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:36 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:36 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:36 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:36 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:36 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:37 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:37 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:37 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:37 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:37 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:37 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:39 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:39 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:40 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:40 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:42 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:43 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:44 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:50 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:50 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:50 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:52 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:52 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:52 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:53 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:53 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:53 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:54 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:54 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:54 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:54 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:54 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:54 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:54 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:54 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:54 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:55 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:55 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:55 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:56 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:56 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:56 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:57 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:57 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:57 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:57 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:57 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:58 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:58 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:58 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:58 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:58 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:58 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:59 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:13:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:59 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:13:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:13:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:13:59 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:13:59 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:00 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:00 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:01 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:01 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:02 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:02 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:02 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:03 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:03 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:03 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:04 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:04 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:04 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:05 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:05 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:06 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:06 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:07 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:07 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:08 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:08 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:09 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:09 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:10 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:10 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:11 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:11 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:12 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:12 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:12 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:13 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:13 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:13 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:14 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:14 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:14 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:15 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:15 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:16 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:16 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:17 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:17 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:18 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:18 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:14:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:19 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:19 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:14:19 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:14:19 jadis kernel: device wlan0 left promiscuous mode
Jan 27 19:14:19 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:14:19 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:19 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:19 jadis avahi-daemon[1330]: Withdrawing workstation service for mon.wlan0.
Jan 27 19:14:19 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:19 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:19 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:19 jadis kernel: ieee80211 phy0: device now idle
Jan 27 19:14:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:19 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:14:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:14:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:19 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:14:19 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:14:19 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:19 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:27 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:27 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:27 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 19:14:27 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:27 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:27 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:27 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:27 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 19:14:27 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:27 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:27 jadis radvd[4463]: attempting to reread config file
Jan 27 19:14:27 jadis radvd[4463]: resuming normal operation
Jan 27 19:14:27 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:14:27 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:14:36 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:14:38 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:14:38 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:14:38 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:14:38 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: disassociated
Jan 27 19:14:38 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:14:38 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:14:39 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: deauthenticated due to inactivity
Jan 27 19:14:42 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:14:45 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:14:47 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:14:47 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:14:47 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:14:47 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E983-00000000
Jan 27 19:14:47 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:14:47 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 19:14:47 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 19:15:44 jadis hostapd: wlan0: STA f8:db:7f:de:53:72 IEEE 802.11: authenticated
Jan 27 19:15:44 jadis hostapd: wlan0: STA f8:db:7f:de:53:72 IEEE 802.11: associated (aid 2)
Jan 27 19:15:44 jadis kernel: ieee80211 phy0: Allocated STA f8:db:7f:de:53:72
Jan 27 19:15:44 jadis kernel: ieee80211 phy0: Inserted STA f8:db:7f:de:53:72
Jan 27 19:15:44 jadis hostapd: wlan0: STA f8:db:7f:de:53:72 WPA: WPA IE from (Re)AssocReq did not match with msg 2/4
Jan 27 19:15:44 jadis hostapd: wlan0: STA f8:db:7f:de:53:72 IEEE 802.11: deauthenticated due to local deauth request
Jan 27 19:15:44 jadis kernel: ieee80211 phy0: Removed STA f8:db:7f:de:53:72
Jan 27 19:15:44 jadis kernel: ieee80211 phy0: Destroyed STA f8:db:7f:de:53:72
Jan 27 19:16:31 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:16:31 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:16:41 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:16:41 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:16:41 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:16:41 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:16:41 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22E983-00000001
Jan 27 19:16:41 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:16:41 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 19:16:41 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 19:16:41 jadis kernel: ath: received PCI FATAL interrupt
Jan 27 19:16:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
Jan 27 19:16:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:41 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00028040
Jan 27 19:16:41 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:42 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:16:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:42 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:42 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:43 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:16:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:43 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:43 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:44 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:44 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00004040
Jan 27 19:16:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:45 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:45 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:16:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:46 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:46 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:47 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:16:47 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:48 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:16:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:48 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:48 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:49 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:16:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:49 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:16:49 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:50 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:16:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:50 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:50 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:51 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:51 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:16:51 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:16:51 jadis kernel: device wlan0 left promiscuous mode
Jan 27 19:16:51 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:16:51 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:51 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:51 jadis avahi-daemon[1330]: Withdrawing workstation service for mon.wlan0.
Jan 27 19:16:51 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:51 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:51 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:51 jadis kernel: ieee80211 phy0: device now idle
Jan 27 19:16:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:16:51 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:51 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:51 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:16:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:16:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:51 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00008040
Jan 27 19:16:51 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:16:59 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:59 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:59 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 19:16:59 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:59 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:59 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:59 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:59 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:59 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:59 jadis radvd[4463]: attempting to reread config file
Jan 27 19:16:59 jadis radvd[4463]: resuming normal operation
Jan 27 19:16:59 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 19:16:59 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:16:59 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:17:01 jadis CRON[7066]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 27 19:17:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:17:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:17:05 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:17:05 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:17:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22EA1B-00000000
Jan 27 19:17:05 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:17:14 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:17:36 jadis kernel: ieee80211 phy0: Removed STA 00:22:fb:98:bd:50
Jan 27 19:17:36 jadis kernel: ieee80211 phy0: Destroyed STA 00:22:fb:98:bd:50
Jan 27 19:17:36 jadis kernel: device wlan0 left promiscuous mode
Jan 27 19:17:36 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:17:36 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:36 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:36 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:36 jadis avahi-daemon[1330]: Withdrawing workstation service for mon.wlan0.
Jan 27 19:17:36 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:36 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:36 jadis kernel: ieee80211 phy0: device now idle
Jan 27 19:17:36 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:36 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:36 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:44 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:44 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:45 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:45 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:45 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:45 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:45 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:45 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:45 jadis radvd[4463]: attempting to reread config file
Jan 27 19:17:45 jadis radvd[4463]: resuming normal operation
Jan 27 19:17:44 jadis kernel: ieee80211 phy0: device no longer idle - in use
Jan 27 19:17:45 jadis kernel: device wlan0 entered promiscuous mode
Jan 27 19:17:45 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:17:45 jadis kernel: br0: port 3(wlan0) entering forwarding state
Jan 27 19:17:45 jadis kernel: wlan0: dropped frame to 00:22:fb:98:bd:50 (unauthorized port)
Jan 27 19:17:58 jadis kernel: last message repeated 3 times
Jan 27 19:17:58 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: authenticated
Jan 27 19:17:58 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 IEEE 802.11: associated (aid 1)
Jan 27 19:17:58 jadis kernel: ieee80211 phy0: Allocated STA 00:22:fb:98:bd:50
Jan 27 19:17:58 jadis kernel: ieee80211 phy0: Inserted STA 00:22:fb:98:bd:50
Jan 27 19:17:58 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 RADIUS: starting accounting session 4F22EA49-00000000
Jan 27 19:17:58 jadis hostapd: wlan0: STA 00:22:fb:98:bd:50 WPA: pairwise key handshake completed (RSN)
Jan 27 19:17:58 jadis dhcpd: DHCPREQUEST for 192.168.1.3 from 00:22:fb:98:bd:50 via br0
Jan 27 19:17:58 jadis dhcpd: DHCPACK on 192.168.1.3 to 00:22:fb:98:bd:50 via br0
Jan 27 19:18:00 jadis kernel: br0: port 3(wlan0) entering forwarding state

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/27/2012 10:30 AM, Sune M?lgaard wrote:
> Ben Greear wrote:
>> On 01/27/2012 03:47 AM, Sune M?lgaard wrote:

>> If you hit the problem on my kernel, please send me a full bug report
>> (kernel splat, 'lspci', brief
>> description of how you caused the problem, how reproducible it is, etc).
>>
>> I can't promise I can fix it, but I will definitely take a good look at it
>> and will try to reproduce the problem on my systems. If we can ever find
>> a way to reliably reproduce these problems, then the ath9k developers will
>> have a much easier time fixing the problem.
>>
>> Thanks,
>> Ben
>>
>
> Attached. I even hit it with WMM and 11n disabled.
>
> I hit it with high speeds occurring - it took 5 cycles of hostapd for the syslog file to be scp'ed over (the complete file was 24Mb, though).

Ok, this is the first obvious error I see, and that FATAL interrupt looks bad, and my guess
is that the IRQ problem is the root cause.

This is caused by the AR_INTR_SYNC_HOST1_FATAL interrupt, but I don't have any idea what can cause that
interrupt, and I don't have access to any of the datasheets for ath9k chips.  Maybe one
of the ath9k devs has some ideas on this?

I am not sure I have a NIC with your chipset.
Can you let me know the exact brand & part number of your NIC.


Jan 27 19:06:38 jadis kernel: ath: received PCI FATAL interrupt
Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:38 jadis kernel: ------------[ cut here ]------------
Jan 27 19:06:38 jadis kernel: WARNING: at drivers/net/wireless/ath/ath9k/recv.c:528 ath_stoprecv+0xbc/0xe0 [ath9k]()
Jan 27 19:06:38 jadis kernel: Hardware name: 8366-8233
Jan 27 19:06:38 jadis kernel: Modules linked in: cryptd aes_i586 aes_generic ip6table_filter tun xt_CHECKSUM xt_TCPMSS act_police cls_flow cls_fw cls_u32 
sch_tbf sch_prio sch_htb sch_hfsc sch_ingress sch_sfq xt_time xt_connlimit xt_realm xt_addrtype iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REDIRECT 
ipt_NETMAP ipt_MASQUERADE ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah xt_set ip_set nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp 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_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip 
nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY nf_tproxy_core ip6_tables nf_defrag_ipv6 xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log 
xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt
Jan 27 19:06:38 jadis kernel: _connmark xt_CLASSIFY xt_AUDIT ipt_LOG iptable_nat nf_nat iptable_mangle nfnetlink sit tunnel4 reiserfs bridge ipv6 stp llc arc4 
snd_cs4236 snd_wss_lib snd_via82xx snd_ac97_codec snd_opl3_lib ppdev snd_hwdep ac97_bus ath9k snd_pcm mac80211 snd_timer ath9k_common ath9k_hw snd_page_alloc 
snd_mpu401 i2c_viapro snd_mpu401_uart snd_rawmidi ath via_ircc snd_seq_device irda snd cfg80211 soundcore crc_ccitt ns558 gameport parport_pc hwmon_vid hwmon lp 
parport 8139too ata_generic pata_acpi 8139cp sundance pata_via sata_sil mii floppy raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy 
async_tx raid1 raid0 multipath linear
Jan 27 19:06:38 jadis kernel: Pid: 4298, comm: java Not tainted 3.0.18-sune-1 #3
Jan 27 19:06:38 jadis kernel: Call Trace:
Jan 27 19:06:38 jadis kernel: [<c0431086>] warn_slowpath_common+0x63/0x78
Jan 27 19:06:38 jadis kernel: [<f851eaab>] ? ath_stoprecv+0xbc/0xe0 [ath9k]
Jan 27 19:06:38 jadis kernel: [<c04310aa>] warn_slowpath_null+0xf/0x13
Jan 27 19:06:38 jadis kernel: [<f851eaab>] ath_stoprecv+0xbc/0xe0 [ath9k]
Jan 27 19:06:38 jadis kernel: [<f851d782>] ath_reset+0x64/0x17c [ath9k]
Jan 27 19:06:38 jadis kernel: [<c07771e1>] ? _raw_spin_unlock_irqrestore+0x12/0x15
Jan 27 19:06:38 jadis kernel: [<f851d9ef>] ath9k_tasklet+0x27/0x133 [ath9k]
Jan 27 19:06:38 jadis kernel: [<c0435308>] tasklet_action+0x65/0xa7
Jan 27 19:06:38 jadis kernel: [<c04355e0>] __do_softirq+0x6c/0xe6
Jan 27 19:06:38 jadis kernel: [<c0435574>] ? local_bh_enable+0xa/0xa
Jan 27 19:06:38 jadis kernel: <IRQ>  [<c04357b8>] ? irq_exit+0x35/0x84
Jan 27 19:06:38 jadis kernel: [<c0403a78>] ? do_IRQ+0x6c/0x80
Jan 27 19:06:38 jadis kernel: [<c077be69>] ? common_interrupt+0x29/0x30
Jan 27 19:06:38 jadis kernel: ---[ end trace 46bdcea34024800a ]---
Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
....

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Adrian Chadd]

"pissed off bus glue."

You'll get that error whenever the PCI/PCIe interface glue errors out.

"

host1_fatal signal from PCI core during a DMA transfer

"


As for what this means, I'll have to go and tickle someone in the MAC group
to give us some ideas.


Ben, would you please work with the OP to take everything above and dump it
into a comphrensive bugzilla.kernel.org report?

I'll then assign it to the ath9k team here and follow it up with the MAC
group. Maybe they'll have some ideas on what we can do.


Bonus points if we can get a unit/config that's misbehaving to someone with
a PCI/PCIe bus analyser. The trouble though is it may be related to the
"air" and so reproducing it here may not be trivial.


(Note to community: please write some tools to dump/analyse the pktlog data
that ath9k exports. :-)




Adrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120127/ddc99445/attachment.htm 

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/27/2012 12:05 PM, Adrian Chadd wrote:
> "pissed off bus glue."
>
> You'll get that error whenever the PCI/PCIe interface glue errors out.
>
> "
>
> host1_fatal signal from PCI core during a DMA transfer
>
> "
>
>
> As for what this means, I'll have to go and tickle someone in the MAC group to give us some ideas.
>
>
> Ben, would you please work with the OP to take everything above and dump it into a comphrensive bugzilla.kernel.org <http://bugzilla.kernel.org> report?
>
> I'll then assign it to the ath9k team here and follow it up with the MAC group. Maybe they'll have some ideas on what we can do.

The bug is here:

https://bugzilla.kernel.org/show_bug.cgi?id=42673


If I can figure out exactly what NIC it is I'll try to get one
and see if I can reproduce the problem on my machines.  It's always
possible it's a bad interaction with some specific
motherboard(s).  I don't have a bus analyzer, but if I
can reproduce it, likely others can as well.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Sune Mølgaard]

My card is a D-Link DWA-547, FW-ver. 1,70. HW ver. A3. It's a PCI card.

Best regards, and thank you for looking into it,

Sune M?lgaard

Ben Greear wrote:
> On 01/27/2012 10:30 AM, Sune M?lgaard wrote:
>> Ben Greear wrote:
>>> On 01/27/2012 03:47 AM, Sune M?lgaard wrote:
>
>>> If you hit the problem on my kernel, please send me a full bug report
>>> (kernel splat, 'lspci', brief
>>> description of how you caused the problem, how reproducible it is, etc).
>>>
>>> I can't promise I can fix it, but I will definitely take a good look
>>> at it
>>> and will try to reproduce the problem on my systems. If we can ever find
>>> a way to reliably reproduce these problems, then the ath9k developers
>>> will
>>> have a much easier time fixing the problem.
>>>
>>> Thanks,
>>> Ben
>>>
>>
>> Attached. I even hit it with WMM and 11n disabled.
>>
>> I hit it with high speeds occurring - it took 5 cycles of hostapd for
>> the syslog file to be scp'ed over (the complete file was 24Mb, though).
>
> Ok, this is the first obvious error I see, and that FATAL interrupt
> looks bad, and my guess
> is that the IRQ problem is the root cause.
>
> This is caused by the AR_INTR_SYNC_HOST1_FATAL interrupt, but I don't
> have any idea what can cause that
> interrupt, and I don't have access to any of the datasheets for ath9k
> chips. Maybe one
> of the ath9k devs has some ideas on this?
>
> I am not sure I have a NIC with your chipset.
> Can you let me know the exact brand & part number of your NIC.
>
>
> Jan 27 19:06:38 jadis kernel: ath: received PCI FATAL interrupt
> Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms
> AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
> Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be
> confusing the DMA engine when we start RX up
> Jan 27 19:06:38 jadis kernel: ------------[ cut here ]------------
> Jan 27 19:06:38 jadis kernel: WARNING: at
> drivers/net/wireless/ath/ath9k/recv.c:528 ath_stoprecv+0xbc/0xe0 [ath9k]()
> Jan 27 19:06:38 jadis kernel: Hardware name: 8366-8233
> Jan 27 19:06:38 jadis kernel: Modules linked in: cryptd aes_i586
> aes_generic ip6table_filter tun xt_CHECKSUM xt_TCPMSS act_police
> cls_flow cls_fw cls_u32 sch_tbf sch_prio sch_htb sch_hfsc sch_ingress
> sch_sfq xt_time xt_connlimit xt_realm xt_addrtype iptable_raw xt_comment
> xt_recent xt_policy ipt_ULOG ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE
> ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah xt_set ip_set nf_nat_tftp
> nf_nat_snmp_basic nf_conntrack_snmp 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_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip
> nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre
> nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast
> nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY
> nf_tproxy_core ip6_tables nf_defrag_ipv6 xt_tcpmss xt_pkttype xt_physdev
> xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_mark xt_mac
> xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp
> xt_dccp xt
> Jan 27 19:06:38 jadis kernel: _connmark xt_CLASSIFY xt_AUDIT ipt_LOG
> iptable_nat nf_nat iptable_mangle nfnetlink sit tunnel4 reiserfs bridge
> ipv6 stp llc arc4 snd_cs4236 snd_wss_lib snd_via82xx snd_ac97_codec
> snd_opl3_lib ppdev snd_hwdep ac97_bus ath9k snd_pcm mac80211 snd_timer
> ath9k_common ath9k_hw snd_page_alloc snd_mpu401 i2c_viapro
> snd_mpu401_uart snd_rawmidi ath via_ircc snd_seq_device irda snd
> cfg80211 soundcore crc_ccitt ns558 gameport parport_pc hwmon_vid hwmon
> lp parport 8139too ata_generic pata_acpi 8139cp sundance pata_via
> sata_sil mii floppy raid10 raid456 async_raid6_recov async_pq raid6_pq
> async_xor xor async_memcpy async_tx raid1 raid0 multipath linear
> Jan 27 19:06:38 jadis kernel: Pid: 4298, comm: java Not tainted
> 3.0.18-sune-1 #3
> Jan 27 19:06:38 jadis kernel: Call Trace:
> Jan 27 19:06:38 jadis kernel: [<c0431086>] warn_slowpath_common+0x63/0x78
> Jan 27 19:06:38 jadis kernel: [<f851eaab>] ? ath_stoprecv+0xbc/0xe0 [ath9k]
> Jan 27 19:06:38 jadis kernel: [<c04310aa>] warn_slowpath_null+0xf/0x13
> Jan 27 19:06:38 jadis kernel: [<f851eaab>] ath_stoprecv+0xbc/0xe0 [ath9k]
> Jan 27 19:06:38 jadis kernel: [<f851d782>] ath_reset+0x64/0x17c [ath9k]
> Jan 27 19:06:38 jadis kernel: [<c07771e1>] ?
> _raw_spin_unlock_irqrestore+0x12/0x15
> Jan 27 19:06:38 jadis kernel: [<f851d9ef>] ath9k_tasklet+0x27/0x133 [ath9k]
> Jan 27 19:06:38 jadis kernel: [<c0435308>] tasklet_action+0x65/0xa7
> Jan 27 19:06:38 jadis kernel: [<c04355e0>] __do_softirq+0x6c/0xe6
> Jan 27 19:06:38 jadis kernel: [<c0435574>] ? local_bh_enable+0xa/0xa
> Jan 27 19:06:38 jadis kernel: <IRQ> [<c04357b8>] ? irq_exit+0x35/0x84
> Jan 27 19:06:38 jadis kernel: [<c0403a78>] ? do_IRQ+0x6c/0x80
> Jan 27 19:06:38 jadis kernel: [<c077be69>] ? common_interrupt+0x29/0x30
> Jan 27 19:06:38 jadis kernel: ---[ end trace 46bdcea34024800a ]---
> Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
> Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms
> AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
> Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be
> confusing the DMA engine when we start RX up
> Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
> ....
>
> Thanks,
> Ben
>

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Ok I finally got the kernel built and running.  Think I messed up with 
the .config file on the first build.

My card was bought from ebay and the details of the card from the 
seller are as follows.

Apple Macbook Airport A1181, AR9280 AR5BXB92 300m N card

I have attached the relevant files.  Wonder if its the same as Sune's 
issue.

Thank you for your help Ben.

Cheers

Paul

On Sat, 28 Jan 2012 10:39:54 +0100, Sune M?lgaard wrote:
> My card is a D-Link DWA-547, FW-ver. 1,70. HW ver. A3. It's a PCI 
> card.
>
> Best regards, and thank you for looking into it,
>
> Sune M?lgaard
>
> Ben Greear wrote:
>> On 01/27/2012 10:30 AM, Sune M?lgaard wrote:
>>> Ben Greear wrote:
>>>> On 01/27/2012 03:47 AM, Sune M?lgaard wrote:
>>
>>>> If you hit the problem on my kernel, please send me a full bug 
>>>> report
>>>> (kernel splat, 'lspci', brief
>>>> description of how you caused the problem, how reproducible it is, 
>>>> etc).
>>>>
>>>> I can't promise I can fix it, but I will definitely take a good 
>>>> look
>>>> at it
>>>> and will try to reproduce the problem on my systems. If we can 
>>>> ever find
>>>> a way to reliably reproduce these problems, then the ath9k 
>>>> developers
>>>> will
>>>> have a much easier time fixing the problem.
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>
>>> Attached. I even hit it with WMM and 11n disabled.
>>>
>>> I hit it with high speeds occurring - it took 5 cycles of hostapd 
>>> for
>>> the syslog file to be scp'ed over (the complete file was 24Mb, 
>>> though).
>>
>> Ok, this is the first obvious error I see, and that FATAL interrupt
>> looks bad, and my guess
>> is that the IRQ problem is the root cause.
>>
>> This is caused by the AR_INTR_SYNC_HOST1_FATAL interrupt, but I 
>> don't
>> have any idea what can cause that
>> interrupt, and I don't have access to any of the datasheets for 
>> ath9k
>> chips. Maybe one
>> of the ath9k devs has some ideas on this?
>>
>> I am not sure I have a NIC with your chipset.
>> Can you let me know the exact brand & part number of your NIC.
>>
>>
>> Jan 27 19:06:38 jadis kernel: ath: received PCI FATAL interrupt
>> Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms
>> AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
>> Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be
>> confusing the DMA engine when we start RX up
>> Jan 27 19:06:38 jadis kernel: ------------[ cut here ]------------
>> Jan 27 19:06:38 jadis kernel: WARNING: at
>> drivers/net/wireless/ath/ath9k/recv.c:528 ath_stoprecv+0xbc/0xe0 
>> [ath9k]()
>> Jan 27 19:06:38 jadis kernel: Hardware name: 8366-8233
>> Jan 27 19:06:38 jadis kernel: Modules linked in: cryptd aes_i586
>> aes_generic ip6table_filter tun xt_CHECKSUM xt_TCPMSS act_police
>> cls_flow cls_fw cls_u32 sch_tbf sch_prio sch_htb sch_hfsc 
>> sch_ingress
>> sch_sfq xt_time xt_connlimit xt_realm xt_addrtype iptable_raw 
>> xt_comment
>> xt_recent xt_policy ipt_ULOG ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE
>> ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah xt_set ip_set nf_nat_tftp
>> nf_nat_snmp_basic nf_conntrack_snmp 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_amanda nf_conntrack_sane nf_conntrack_tftp 
>> nf_conntrack_sip
>> nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre
>> nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast
>> nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY
>> nf_tproxy_core ip6_tables nf_defrag_ipv6 xt_tcpmss xt_pkttype 
>> xt_physdev
>> xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_mark 
>> xt_mac
>> xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp
>> xt_dccp xt
>> Jan 27 19:06:38 jadis kernel: _connmark xt_CLASSIFY xt_AUDIT ipt_LOG
>> iptable_nat nf_nat iptable_mangle nfnetlink sit tunnel4 reiserfs 
>> bridge
>> ipv6 stp llc arc4 snd_cs4236 snd_wss_lib snd_via82xx snd_ac97_codec
>> snd_opl3_lib ppdev snd_hwdep ac97_bus ath9k snd_pcm mac80211 
>> snd_timer
>> ath9k_common ath9k_hw snd_page_alloc snd_mpu401 i2c_viapro
>> snd_mpu401_uart snd_rawmidi ath via_ircc snd_seq_device irda snd
>> cfg80211 soundcore crc_ccitt ns558 gameport parport_pc hwmon_vid 
>> hwmon
>> lp parport 8139too ata_generic pata_acpi 8139cp sundance pata_via
>> sata_sil mii floppy raid10 raid456 async_raid6_recov async_pq 
>> raid6_pq
>> async_xor xor async_memcpy async_tx raid1 raid0 multipath linear
>> Jan 27 19:06:38 jadis kernel: Pid: 4298, comm: java Not tainted
>> 3.0.18-sune-1 #3
>> Jan 27 19:06:38 jadis kernel: Call Trace:
>> Jan 27 19:06:38 jadis kernel: [<c0431086>] 
>> warn_slowpath_common+0x63/0x78
>> Jan 27 19:06:38 jadis kernel: [<f851eaab>] ? ath_stoprecv+0xbc/0xe0 
>> [ath9k]
>> Jan 27 19:06:38 jadis kernel: [<c04310aa>] 
>> warn_slowpath_null+0xf/0x13
>> Jan 27 19:06:38 jadis kernel: [<f851eaab>] ath_stoprecv+0xbc/0xe0 
>> [ath9k]
>> Jan 27 19:06:38 jadis kernel: [<f851d782>] ath_reset+0x64/0x17c 
>> [ath9k]
>> Jan 27 19:06:38 jadis kernel: [<c07771e1>] ?
>> _raw_spin_unlock_irqrestore+0x12/0x15
>> Jan 27 19:06:38 jadis kernel: [<f851d9ef>] ath9k_tasklet+0x27/0x133 
>> [ath9k]
>> Jan 27 19:06:38 jadis kernel: [<c0435308>] tasklet_action+0x65/0xa7
>> Jan 27 19:06:38 jadis kernel: [<c04355e0>] __do_softirq+0x6c/0xe6
>> Jan 27 19:06:38 jadis kernel: [<c0435574>] ? local_bh_enable+0xa/0xa
>> Jan 27 19:06:38 jadis kernel: <IRQ> [<c04357b8>] ? 
>> irq_exit+0x35/0x84
>> Jan 27 19:06:38 jadis kernel: [<c0403a78>] ? do_IRQ+0x6c/0x80
>> Jan 27 19:06:38 jadis kernel: [<c077be69>] ? 
>> common_interrupt+0x29/0x30
>> Jan 27 19:06:38 jadis kernel: ---[ end trace 46bdcea34024800a ]---
>> Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
>> Jan 27 19:06:38 jadis kernel: ath: DMA failed to stop in 10 ms
>> AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
>> Jan 27 19:06:38 jadis kernel: ath: Could not stop RX, we could be
>> confusing the DMA engine when we start RX up
>> Jan 27 19:06:38 jadis kernel: ath: Failed to stop TX DMA!
>> ....
>>
>> Thanks,
>> Ben
>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmsg_dma_error.txt
Type: text/x-c++
Size: 92287 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120128/6c0d6216/attachment-0001.bin 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: lspci_-v.txt
Url: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120128/6c0d6216/attachment-0001.txt 

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/28/2012 08:49 AM, Paul Farrow wrote:
> Ok I finally got the kernel built and running. Think I messed up with the .config file on the first build.
>
> My card was bought from ebay and the details of the card from the seller are as follows.
>
> Apple Macbook Airport A1181, AR9280 AR5BXB92 300m N card
>
> I have attached the relevant files. Wonder if its the same as Sune's issue.
>
> Thank you for your help Ben.

Well, I don't see the PCI bus errors that Sune reported.  The
DMADBG_7 register is different in your case as well, though
at this point, I'm not sure what those bits mean.

I added your kernel splat and NIC info to the bugzilla entry,
and I'm going to try to order these two NICs.

Can you please review the info I added about your situation
and make sure it is correct?

https://bugzilla.kernel.org/process_bug.cgi

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Looks good.  Just one thing the url in your email to the kernel.org 
website didn't have the bug number in it, so for completeness here it 
is...

https://bugzilla.kernel.org/show_bug.cgi?id=42673

On Mon, 30 Jan 2012 09:45:40 -0800, Ben Greear wrote:
> On 01/28/2012 08:49 AM, Paul Farrow wrote:
>> Ok I finally got the kernel built and running. Think I messed up 
>> with the .config file on the first build.
>>
>> My card was bought from ebay and the details of the card from the 
>> seller are as follows.
>>
>> Apple Macbook Airport A1181, AR9280 AR5BXB92 300m N card
>>
>> I have attached the relevant files. Wonder if its the same as Sune's 
>> issue.
>>
>> Thank you for your help Ben.
>
> Well, I don't see the PCI bus errors that Sune reported.  The
> DMADBG_7 register is different in your case as well, though
> at this point, I'm not sure what those bits mean.
>
> I added your kernel splat and NIC info to the bugzilla entry,
> and I'm going to try to order these two NICs.
>
> Can you please review the info I added about your situation
> and make sure it is correct?
>
> https://bugzilla.kernel.org/process_bug.cgi
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 01/30/2012 10:22 AM, Paul Farrow wrote:
>
> Looks good. Just one thing the url in your email to the kernel.org website didn't have the bug number in it, so for completeness here it is...
>

Just FYI, I received a NIC that I believe is very close to yours (perhaps
identical).  I've been running station to station traffic at about 13Mbps in one direction and 5 Mbps in
the other...I've seen no problems.

I believe your test case was slightly different...mostly download
from wired to station, so I'll try that test later if this one
continues to run clean...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] (no subject)

[Mieszko Ślusarczyk]

I was getting the same error message, when using my card (TP-LINK-WN851ND) with hosted (in master mode) as an access point. After few minutes of steady transfer at about 7-8 Mbytes network was going down with repeating "Failed to stop TX DMA" messages..  

tried out compat-wireless 3.0, 3.1, and 3.2_rc  

--  
Mieszko ?lusarczyk




On Monday, 30 January 2012 at 19:22, Paul Farrow wrote:

>  
> Looks good. Just one thing the url in your email to the kernel.org (http://kernel.org)  
> website didn't have the bug number in it, so for completeness here it  
> is...
>  
> https://bugzilla.kernel.org/show_bug.cgi?id=42673
>  
> On Mon, 30 Jan 2012 09:45:40 -0800, Ben Greear wrote:
> > On 01/28/2012 08:49 AM, Paul Farrow wrote:
> > > Ok I finally got the kernel built and running. Think I messed up  
> > > with the .config file on the first build.
> > >  
> > > My card was bought from ebay and the details of the card from the  
> > > seller are as follows.
> > >  
> > > Apple Macbook Airport A1181, AR9280 AR5BXB92 300m N card
> > >  
> > > I have attached the relevant files. Wonder if its the same as Sune's  
> > > issue.
> > >  
> > > Thank you for your help Ben.
> >  
> > Well, I don't see the PCI bus errors that Sune reported. The
> > DMADBG_7 register is different in your case as well, though
> > at this point, I'm not sure what those bits mean.
> >  
> > I added your kernel splat and NIC info to the bugzilla entry,
> > and I'm going to try to order these two NICs.
> >  
> > Can you please review the info I added about your situation
> > and make sure it is correct?
> >  
> > https://bugzilla.kernel.org/process_bug.cgi
> >  
> > Thanks,
> > Ben
> >  
>  
>  
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org (mailto:ath9k-devel at lists.ath9k.org)
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120204/0823fe08/attachment.htm 

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

Hi Ben

Firstly thanks again for buying that NIC and spending your time on it.  
Yes I basically do a speed test from the wireless device which is then 
forwarded through a wired NIC on the motherboard using firewall rules of 
IPTables etc.  I basically boot the machine and then run hostapd and 
immediately connect either my Android phone or MacBook Pro to the 
wireless and do a speedtest and immediately I see the problem.

Couple of questions here though.

I take it you used my exact hostapd.conf file?
Can I see your lspci output to see if the card you have is the same 
revision as mine is a revision 1 card?
Those speeds seem quite slow as I thought it was a 300 Mbps card?

Thanks

Paul

On Fri, 03 Feb 2012 13:26:55 -0800, Ben Greear wrote:
> On 01/30/2012 10:22 AM, Paul Farrow wrote:
>>
>> Looks good. Just one thing the url in your email to the kernel.org 
>> website didn't have the bug number in it, so for completeness here it 
>> is...
>>
>
> Just FYI, I received a NIC that I believe is very close to yours 
> (perhaps
> identical).  I've been running station to station traffic at about
> 13Mbps in one direction and 5 Mbps in
> the other...I've seen no problems.
>
> I believe your test case was slightly different...mostly download
> from wired to station, so I'll try that test later if this one
> continues to run clean...
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 02/05/2012 04:01 AM, Paul Farrow wrote:
>
> Hi Ben
>
> Firstly thanks again for buying that NIC and spending your time on it. Yes I basically do a speed test from the wireless device which is then forwarded through
> a wired NIC on the motherboard using firewall rules of IPTables etc. I basically boot the machine and then run hostapd and immediately connect either my Android
> phone or MacBook Pro to the wireless and do a speedtest and immediately I see the problem.
>
> Couple of questions here though.
>
> I take it you used my exact hostapd.conf file?

I used something similar, but not exactly the same.

You might try changing yours (channel, encryption, etc) to see
if it has some affect.

> Can I see your lspci output to see if the card you have is the same revision as mine is a revision 1 card?

03:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)

My system is 64-bit, embedded appliance sort of thing with low-power Core-i7 processor.

> Those speeds seem quite slow as I thought it was a 300 Mbps card?

Station to station is much slower than wired to station, but it's
easier to set up in my test bed.  I'll try wired to station, but I'm busy
with other things today.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] (no subject)

[Ben Greear]

On 02/04/2012 04:43 AM, Mieszko ?lusarczyk wrote:
> I was getting the same error message, when using my card (TP-LINK-WN851ND) with hosted (in master mode) as an access point. After few minutes of steady transfer
> at about 7-8 Mbytes network was going down with repeating "Failed to stop TX DMA" messages..
>
> tried out compat-wireless 3.0, 3.1, and 3.2_rc

Please post the output of 'lspci' on your system,
and if you can reproduce the problem, the output of 'dmesg'
with the error visible.

Motherboard, OS, and any other info should be helpful as well.

My hope is that if we can get enough detailed reports we
might can see a pattern.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Mieszko Ślusarczyk]

00:14.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (rev 01)


Motherboard is VIA VB7001AG (with a VIA C7 processor).
Distrbution is ipfire, as I've mentioned I've tried few versions of compat-wireless

Error was:

Dec 15 15:15:40 spitfire-ipfire1 kernel: ath: Failed to stop TX DMA!
Dec 15 15:15:40 spitfire-ipfire1 kernel: ath: Failed to stop TX DMA!
Dec 15 15:15:40 spitfire-ipfire1 kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00026040
Dec 15 15:15:40 spitfire-ipfire1 kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Dec 15 15:15:40 spitfire-ipfire1 kernel: ath: Failed to stop TX DMA!
Dec 15 15:15:40 spitfire-ipfire1 kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Dec 15 15:15:40 spitfire-ipfire1 kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Dec 15 15:15:41 spitfire-ipfire1 kernel: ath: Failed to stop TX DMA!
Dec 15 15:15:41 spitfire-ipfire1 kernel: ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
Dec 15 15:15:41 spitfire-ipfire1 kernel: ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
Dec 15 15:15:41 spitfire-ipfire1 kernel: ath: Failed to stop TX DMA!  

--  
Mieszko ?lusarczyk




On Monday, 6 February 2012 at 18:51, Ben Greear wrote:

> On 02/04/2012 04:43 AM, Mieszko ?lusarczyk wrote:
> > I was getting the same error message, when using my card (TP-LINK-WN851ND) with hosted (in master mode) as an access point. After few minutes of steady transfer
> > at about 7-8 Mbytes network was going down with repeating "Failed to stop TX DMA" messages..
> >  
> > tried out compat-wireless 3.0, 3.1, and 3.2_rc
>  
> Please post the output of 'lspci' on your system,
> and if you can reproduce the problem, the output of 'dmesg'
> with the error visible.
>  
> Motherboard, OS, and any other info should be helpful as well.
>  
> My hope is that if we can get enough detailed reports we
> might can see a pattern.
>  
> Thanks,
> Ben
>  
> --  
> Ben Greear <greearb at candelatech.com (mailto:greearb@candelatech.com)>
> Candela Technologies Inc http://www.candelatech.com
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120206/5f980ebb/attachment.htm 

[ath9k-devel] Failed to stop TX DMA

[Mieszko Ślusarczyk]

That messages are old (as you can see) and I cannot play with that ATM.\I'll give you more debugging, when I'll have some more time.  

--  
Mieszko ?lusarczyk




On Monday, 6 February 2012 at 19:07, Ben Greear wrote:

> On 02/06/2012 09:55 AM, Mieszko ?lusarczyk wrote:
> > 00:14.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (rev 01)
> >  
> >  
> > Motherboard is VIA VB7001AG (with a VIA C7 processor).
> > Distrbution is ipfire, as I've mentioned I've tried few versions of compat-wireless
> >  
>  
>  
> Can you post full lspci and dmesg? For 'dmesg', it is best if we can see from
> a clean boot until the first error. (/var/log/messages output should be
> fine as well).
>  
> I have a VIA system, but it only takes mini-pci NICs.
>  
> Do you happen to have any other motherboads you can try your
> NIC in?
>  
> Do you have any different NICs that work in your current motherboard?
>  
> Thanks,
> Ben
>  
> --  
> Ben Greear <greearb at candelatech.com (mailto:greearb@candelatech.com)>
> Candela Technologies Inc http://www.candelatech.com
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120206/bde289b8/attachment-0001.htm 

[ath9k-devel] (no subject)

[Sune Mølgaard]

Ben Greear wrote:
> Motherboard, OS, and any other info should be helpful as well.
>
> My hope is that if we can get enough detailed reports we
> might can see a pattern.

For my own part, my MB is an old MSI MS-6390. I notice that booting with 
acpi=off seems to alleviate the problem to *some* extent, but it still 
happens. Going without wmm and 11n also helps a bit, but not fully...

Best regards,

Sune M?lgaard

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

On Mon, 06 Feb 2012 09:47:28 -0800, Ben Greear wrote:
> On 02/05/2012 04:01 AM, Paul Farrow wrote:
>>
>> Hi Ben
>>
>> Firstly thanks again for buying that NIC and spending your time on 
>> it. Yes I basically do a speed test from the wireless device which is 
>> then forwarded through
>> a wired NIC on the motherboard using firewall rules of IPTables etc. 
>> I basically boot the machine and then run hostapd and immediately 
>> connect either my Android
>> phone or MacBook Pro to the wireless and do a speedtest and 
>> immediately I see the problem.
>>
>> Couple of questions here though.
>>
>> I take it you used my exact hostapd.conf file?
>
> I used something similar, but not exactly the same.
>
> You might try changing yours (channel, encryption, etc) to see
> if it has some affect.
>
>> Can I see your lspci output to see if the card you have is the same 
>> revision as mine is a revision 1 card?
>
> 03:00.0 Network controller: Atheros Communications Inc. AR928X
> Wireless Network Adapter (PCI-Express) (rev 01)
>
> My system is 64-bit, embedded appliance sort of thing with low-power
> Core-i7 processor.
>
>> Those speeds seem quite slow as I thought it was a 300 Mbps card?
>
> Station to station is much slower than wired to station, but it's
> easier to set up in my test bed.  I'll try wired to station, but I'm 
> busy
> with other things today.
>
> Thanks,
> Ben


Just a follow up on my TX DMA problem.  Firstly thank you to Ben for 
helping me lots outside of this group.  Secondly I gave up on the AR9280 
card and bought one that Ben was using the Sparklan WPEA-127N Atheros 
AR9380 XB112 AR5BXB11 which it has been running now for a week in AP 
mode without any problems.  So conclusion is its either something to do 
with the AR9280 card, combination of A9280 and my Jetway NF93R-LF or the 
ath9k driver.

The bug was saved on kernel.org but as of yet no one seems to have 
looked at it.

I am so happy that I have a working AP now though, so thanks to 
everyone who tried to help and especially to Ben Greear for even buying 
the same NIC to try to help, very much appreciated.

Paul

[ath9k-devel] Failed to stop TX DMA

[Adrian Chadd]

Hi,

But the root cause with the AR9280 wasn't found/fixed, and it's quite
possible the issue exists but is different for the AR9380.

So I'm glad you've got it fixed, but we're still no closer to figuring
out why :(


Adrian

[ath9k-devel] Failed to stop TX DMA

[Ben Greear]

On 03/16/2012 08:35 AM, Adrian Chadd wrote:
> Hi,
>
> But the root cause with the AR9280 wasn't found/fixed, and it's quite
> possible the issue exists but is different for the AR9380.
>
> So I'm glad you've got it fixed, but we're still no closer to figuring
> out why :(

Paul:  Want to donate your old broken NIC to science? :)

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

[ath9k-devel] Failed to stop TX DMA

[Paul Farrow]

I would swap it with the 9280 you bought as I would like to put it in 
one of my other machines to use the bluetooth capabilities.  Also it 
appeared to behave itself as a client it was only as an AP that I saw 
the problem.

On Fri, 16 Mar 2012 09:08:44 -0700, Ben Greear wrote:
> On 03/16/2012 08:35 AM, Adrian Chadd wrote:
>> Hi,
>>
>> But the root cause with the AR9280 wasn't found/fixed, and it's 
>> quite
>> possible the issue exists but is different for the AR9380.
>>
>> So I'm glad you've got it fixed, but we're still no closer to 
>> figuring
>> out why :(
>
> Paul:  Want to donate your old broken NIC to science? :)
>
> Thanks,
> Ben

[ath9k-devel] Failed to stop TX DMA

[Adrian Chadd]

I'm still not convinced it's broken..


Adrian



Sent from my Palm Pre on AT&T
On Mar 16, 2012 10:19 AM, Paul Farrow <ath9k at thefabfarrows.com> wrote: 



I would swap it with the 9280 you bought as I would like to put it in 

one of my other machines to use the bluetooth capabilities.  Also it 

appeared to behave itself as a client it was only as an AP that I saw 

the problem.



On Fri, 16 Mar 2012 09:08:44 -0700, Ben Greear wrote:

> On 03/16/2012 08:35 AM, Adrian Chadd wrote:

>> Hi,

>>

>> But the root cause with the AR9280 wasn't found/fixed, and it's 

>> quite

>> possible the issue exists but is different for the AR9380.

>>

>> So I'm glad you've got it fixed, but we're still no closer to 

>> figuring

>> out why :(

>

> Paul:  Want to donate your old broken NIC to science? :)

>

> Thanks,

> Ben




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120316/a8dfc6c0/attachment.htm 

[ath9k-devel] (no subject)

[Majid Davari]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160916/237f2cb6/attachment.htm 

[ath9k-devel] (no subject)

[Diego Cananéa]

Hi,

my name is Diego and I'm a Master Student. My research is about Available
Bandwidth Tools on 802.11n networks, the influence of MAC layer.

I want to work with TP-Link TLWN822N USB Adapter, which use Atheros Chipset
and Ath9k_htc driver. But I don't know how I can enable and disable MAC
layer paramaters like:

- AMPDU
- AMSD
- BlockACK

I look at https://github.com/qca/open-ath9k-htc-firmware for this option,
but I don't see how can do this.

Thanks!

-- 
Diego Canan?a N?brega de Azevedo
http://dcna.io
www.twitter.com/diegocananea
www.facebook.com/diegocananea
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20151110/959d36a7/attachment.htm 

[ath9k-devel] (no subject)

[hong zhang]

Looks like in new kernel. There are no fixed_rate_idx and mac80211 subdirectory.
On Tuesday, April 15, 2014 1:01 AM, ????? <cafffe@qq.com> wrote:
 
Hi, I'm now using the Minstrel_ht as a rate control scheme in aht9k NIC driver, but find that I can't control the tx rate by set the fixed_rate_idx in /sys/kernel/debug/phy0/rc/?to a fixed value. Who can tell me what's wrong and who have some useful methods to set the fixed tx rate? I will be appreciate!
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140415/c6145606/attachment.htm 

[ath9k-devel] (no subject)

[=?gb18030?B?wO/UvLXEw6K5+w==?=]

Hi, I'm now using the Minstrel_ht as a rate control scheme in aht9k NIC driver, but find that I can't control the tx rate by set the fixed_rate_idx in /sys/kernel/debug/phy0/rc/ to a fixed value. Who can tell me what's wrong and who have some useful methods to set the fixed tx rate? I will be appreciate!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140415/cd5b85a2/attachment.htm 

[ath9k-devel] (no subject)

[Aman Sharma]

Hi Bruno,

Thanks for your quick reply.

In STA we are using ath9k (mac80211) driver and in AP we are
using propriety driver from atheros Fusion (same flavor as madwifi). it has
wds option enabled already.

You are right 4 address mode should work with this implementation but as
wds is not standard so i think its implementation is different with
different drivers. Ca you please confirm if anybody has faced same issue as
ours and if yes what have they done to correct it.
can you check with this link
http://wireless.kernel.org/en/users/Documentation/iw. Here they have
written that 4 address mode is incompatible with WDS.

Thanks
Aman Sharma


On Mon, Jan 6, 2014 at 4:32 PM, Bruno Antunes <bantunes@wavecom.pt> wrote:

> Hi Aman,
>
> My mistake, I assumed you were using Openwrt on both AP and STA.
>
> From your wireless config are you using madwifi?
>
> The wds option should be 1.
>
> From my experience 4 addr mode works with both devices using the ath9k
> driver as stated in the wiki.
>
> Bruno
>
>
> On 6 Jan, 2014, at 6:40 AM, Aman Sharma <amansh.sharma5@gmail.com> wrote:
>
> Hi Sujith,
>
> yes, we are using non-mac80211 driver in "*atheros"(AP mode)*.
>
> In STA mode, We are enabling 4 address mode using command  *iw dev wlan0
> set 4addr on.*
>
> And in AP mode, we are not enabling or disabling WDS.
>
> Thanks for your help.
>
> With Regards
> Aman Sharma
>
>
>
> On Mon, Jan 6, 2014 at 11:33 AM, Sujith Manoharan <sujith@msujith.org>wrote:
>
>> Aman Sharma wrote:
>> > Hey Bruno,
>> >
>> > One more thing:
>> >
>> > Laptop1 -------(AP)      -------     (STA)-------Laptop2
>> >                  atheros              ath9k
>> >
>> > If the STA interface is not in bridge then Laptop2 is able to get Ip
>> from AP
>> > but if the STA interface is in Bridge using 4 address mode then its not
>> able
>> > to take Ip from AP. I think its due to the 4 address compatibility
>> issue.
>> >
>> > Please suggest Something for this.
>>
>> By "atheros" do you mean a non-mac80211 driver ? WDS requires the same
>> implementation
>> on both the root/client APs. See:
>> http://wiki.openwrt.org/doc/howto/clientmode
>>
>> Sujith
>>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140106/853a2a48/attachment.htm 

[ath9k-devel] (no subject)

[Aman Sharma]

Hi Sujith,

yes, we are using non-mac80211 driver in "*atheros"(AP mode)*.

In STA mode, We are enabling 4 address mode using command  *iw dev wlan0
set 4addr on.*

And in AP mode, we are not enabling or disabling WDS.

Thanks for your help.

With Regards
Aman Sharma



On Mon, Jan 6, 2014 at 11:33 AM, Sujith Manoharan <sujith@msujith.org>wrote:

> Aman Sharma wrote:
> > Hey Bruno,
> >
> > One more thing:
> >
> > Laptop1 -------(AP)      -------     (STA)-------Laptop2
> >                  atheros              ath9k
> >
> > If the STA interface is not in bridge then Laptop2 is able to get Ip
> from AP
> > but if the STA interface is in Bridge using 4 address mode then its not
> able
> > to take Ip from AP. I think its due to the 4 address compatibility issue.
> >
> > Please suggest Something for this.
>
> By "atheros" do you mean a non-mac80211 driver ? WDS requires the same
> implementation
> on both the root/client APs. See:
> http://wiki.openwrt.org/doc/howto/clientmode
>
> Sujith
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140106/07bd7243/attachment.htm 

[ath9k-devel] (no subject)

[Sujith Manoharan]

Aman Sharma wrote:
> Hey Bruno,
> 
> One more thing:
> 
> Laptop1 -------(AP) ? ? ?------- ? ? (STA)-------Laptop2
> ? ? ? ? ? ? ? ? ?atheros ? ? ? ? ? ? ?ath9k
> 
> If the STA interface is not in?bridge then Laptop2 is able to get Ip from AP
> but if the STA interface is in Bridge using 4 address mode then its not able
> to take Ip from AP. I think its due to the 4 address compatibility issue.
> 
> Please suggest Something for this.

By "atheros" do you mean a non-mac80211 driver ? WDS requires the same implementation
on both the root/client APs. See: http://wiki.openwrt.org/doc/howto/clientmode

Sujith

[ath9k-devel] (no subject)

[Aman Sharma]

Hey Bruno,

One more thing:

Laptop1 -------(AP)      -------     (STA)-------Laptop2
                 atheros              ath9k

If the STA interface is not in bridge then Laptop2 is able to get Ip from
AP but if the STA interface is in Bridge using 4 address mode then its not
able to take Ip from AP. I think its due to the 4 address compatibility
issue.

Please suggest Something for this.


Thanks
Aman Sharma








On Mon, Jan 6, 2014 at 10:43 AM, Aman Sharma <amansh.sharma5@gmail.com>wrote:

> Hey Bruno,
>
> What's the contents of /etc/config/network of STA?
>
> ls /etc/network
> if-down.d  if-post-down.d  if-pre-up.d  if-up.d  interfaces  run
>
> What's the contents of /etc/config/wireless of AP?
>
> *Below is the attach file for the content of /etc/config/wireless/*
>
>
> *I am connecting STA to the wireless AP **FSL_AP1gn shown in attached
> file and it is connected to the network in which dhcp-server is present.*
>
> *And Both the laptops are in same lan and I am using Compact wireless 3.6
> version.*
>
> Thanks for your help but I am still struggling for the same.
> But I think its due to 4 address compatibity mode .
>
>
> With Regards
> Aman Sharma
>
>
> On Sat, Jan 4, 2014 at 9:05 PM, Bruno Antunes <bantunes@wavecom.pt> wrote:
>
>> Hi Aman,
>>
>> On 4 Jan, 2014, at 11:28 AM, Aman Sharma <amansh.sharma5@gmail.com>
>> wrote:
>>
>> > Hi All,
>> >
>> > I am facing issue regarding 4 address mode in Board acting as Station
>> using ath9k, Below is setup details:
>> >
>> >
>> > Laptop1 -------(AP)      -------     (STA)-------Laptop2
>> >                  atheros              ath9k
>> >
>> > I have added wireless interface of STA into Bridge, to do so i have
>> enabled 4 address mode on Wlan interface. AP is using atheros drivers and
>> added WLAN interface into bridge.
>>
>> What's the contents of /etc/config/network and /etc/config/wireless of
>> both AP and STA?
>>
>> >
>> > Able to connect ath9k Station to AP but not able to get IP on
>> Laptop2/bridge of STA, this is surely related to compatibility of 4 address
>> mode with atheros.
>> > I tried enabling WDS mode on AP side but it is also not working.
>>
>> Since this is a Layer 2 connection both the laptops should be in the same
>> network, e.g. 192.168.1.1/24  for laptop1 and 192.168.1.2/24 for laptop2.
>>
>> >
>> > Please let me know how to solve this issue, i think this is very common
>> setup and by doing some configuration it should work.
>>
>> don't know your openwrt version but this should indeed work.
>>
>> Bruno.
>> >
>> > Thanks in Advance.
>> >
>> > --
>> > Regards
>> >
>> > Aman Sharma
>> >
>> >
>> > _______________________________________________
>> > ath9k-devel mailing list
>> > ath9k-devel at lists.ath9k.org
>> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140106/e353b4ab/attachment.htm 

[ath9k-devel] (no subject)

[Aman Sharma]

Hey Bruno,

What's the contents of /etc/config/network of STA?

ls /etc/network
if-down.d  if-post-down.d  if-pre-up.d  if-up.d  interfaces  run

What's the contents of /etc/config/wireless of AP?

*Below is the attach file for the content of /etc/config/wireless/*


*I am connecting STA to the wireless AP **FSL_AP1gn shown in attached file
and it is connected to the network in which dhcp-server is present.*

*And Both the laptops are in same lan and I am using Compact wireless 3.6
version.*

Thanks for your help but I am still struggling for the same.
But I think its due to 4 address compatibity mode .


With Regards
Aman Sharma


On Sat, Jan 4, 2014 at 9:05 PM, Bruno Antunes <bantunes@wavecom.pt> wrote:

> Hi Aman,
>
> On 4 Jan, 2014, at 11:28 AM, Aman Sharma <amansh.sharma5@gmail.com> wrote:
>
> > Hi All,
> >
> > I am facing issue regarding 4 address mode in Board acting as Station
> using ath9k, Below is setup details:
> >
> >
> > Laptop1 -------(AP)      -------     (STA)-------Laptop2
> >                  atheros              ath9k
> >
> > I have added wireless interface of STA into Bridge, to do so i have
> enabled 4 address mode on Wlan interface. AP is using atheros drivers and
> added WLAN interface into bridge.
>
> What's the contents of /etc/config/network and /etc/config/wireless of
> both AP and STA?
>
> >
> > Able to connect ath9k Station to AP but not able to get IP on
> Laptop2/bridge of STA, this is surely related to compatibility of 4 address
> mode with atheros.
> > I tried enabling WDS mode on AP side but it is also not working.
>
> Since this is a Layer 2 connection both the laptops should be in the same
> network, e.g. 192.168.1.1/24  for laptop1 and 192.168.1.2/24 for laptop2.
>
> >
> > Please let me know how to solve this issue, i think this is very common
> setup and by doing some configuration it should work.
>
> don't know your openwrt version but this should indeed work.
>
> Bruno.
> >
> > Thanks in Advance.
> >
> > --
> > Regards
> >
> > Aman Sharma
> >
> >
> > _______________________________________________
> > ath9k-devel mailing list
> > ath9k-devel at lists.ath9k.org
> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140106/69f22414/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wireless
Type: application/octet-stream
Size: 2344 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140106/69f22414/attachment.obj 

[ath9k-devel] (no subject)

[Bruno Antunes]

Hi Aman,

On 4 Jan, 2014, at 11:28 AM, Aman Sharma <amansh.sharma5@gmail.com> wrote:

> Hi All,
> 
> I am facing issue regarding 4 address mode in Board acting as Station using ath9k, Below is setup details:
> 
> 
> Laptop1 -------(AP)      -------     (STA)-------Laptop2
>                  atheros              ath9k
> 
> I have added wireless interface of STA into Bridge, to do so i have enabled 4 address mode on Wlan interface. AP is using atheros drivers and added WLAN interface into bridge.

What's the contents of /etc/config/network and /etc/config/wireless of both AP and STA?

> 
> Able to connect ath9k Station to AP but not able to get IP on Laptop2/bridge of STA, this is surely related to compatibility of 4 address mode with atheros.
> I tried enabling WDS mode on AP side but it is also not working.

Since this is a Layer 2 connection both the laptops should be in the same network, e.g. 192.168.1.1/24  for laptop1 and 192.168.1.2/24 for laptop2.

> 
> Please let me know how to solve this issue, i think this is very common setup and by doing some configuration it should work.

don't know your openwrt version but this should indeed work.

Bruno.
> 
> Thanks in Advance.
> 
> --
> Regards
> 
> Aman Sharma
> 
> 
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel

[ath9k-devel] (no subject)

[Aman Sharma]

Hi All,

I am facing issue regarding 4 address mode in Board acting as Station using
ath9k, Below is setup details:


Laptop1 -------(AP)      -------     (STA)-------Laptop2
                 atheros              ath9k

I have added wireless interface of STA into Bridge, to do so i have enabled
4 address mode on Wlan interface. AP is using atheros drivers and added
WLAN interface into bridge.

Able to connect ath9k Station to AP but not able to get IP on
Laptop2/bridge of STA, this is surely related to compatibility of 4 address
mode with atheros.
I tried enabling WDS mode on AP side but it is also not working.

Please let me know how to solve this issue, i think this is very common
setup and by doing some configuration it should work.

Thanks in Advance.

--
Regards

Aman Sharma
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140104/9735b573/attachment.htm 

[ath9k-devel] (no subject)

[Kamran Nishat]

hello can we force ath9k to send every packet as an AMPDU. Currently if
there is only one packet in the queue then ath9k tell the hardware to just
send it as MPDU.
Is there a way to ask driver to wait for more packets and send them as
AMPDU? Simple wait is not working in ath_tx_start(),  ath_tx_send_ampdu()
or ath_tx_form_aggr().

Any help will be highly appreciated.

Kamran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20130930/49e9af3f/attachment.htm 

[ath9k-devel] (no subject)

[Yashashree Jadhav]

Hello ,

Can any tell ...How to fix transmission rate in ath9k driver

During experiment when I put one node on monitoring node....on wireshark....
I found MPDU's within 1 A-MPDU shows different transmission rate.As per my
understanding
in 802.11n all MPDU withing A-MPDU should transmit with the same
transmission rate .
Also in case of failure if transmission rate change then there should be
block ack received intermediately after that failure...but
I found group of MPDU transmit with various transmission rate...and then
one block ack is received....I couldn't identify how exactly aggregation
work
in ath9k driver.

Also if I fixed transmission rate  echo 15 > fixed_rate_idx ....as
aggregation turn of ....and agg. default set to 1....performance degrade
badly...

So , I want some proper way to fix transmission rate...like in madwifi
driver  with command line it is possible to set TX rate.

Regards,
Yashashree
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20121024/ffa56e17/attachment.htm 

[ath9k-devel] (no subject)

[Yashashree Jadhav]

Hello oiioeu,

I just saw your question.Same performance I also experience during my
experiment.
But, as per active research group of ATH9K ,many researcher says  "A-MSDU
aggregation yet not supported by ath9k".
But , I am also interested ,if some one give there opinion abt it.


AP configuration file:


 config wifi-device  radio0
        option type     mac80211
        option channel  161
        option macaddr  xx:xx:xx:xx:xx:xx
        option hwmode   11na
        option htmode   HT40-
        list ht_capab   SHORT-GI-40
        list ht_capab   TX-STBC
        list ht_capab   RX-STBC123
        list ht_capab   MAX-AMSDU-7935
        list ht_capab   DSSS_CCK-40

iw list shows
Wiphy phy0
        Band 1:
                Capabilities: 0x11ce
                        HT20/HT40
                        SM Power Save disabled
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15




then I checked the AMSDU length in a STA established connection with the AP

# iw wlan0 scan dump
BSS 00:80:48:67:d7:30 (on wlan0) -- associated
        TSF: 1072160621 usec (0d, 00:17:52)
        freq: 5805
        beacon interval: 100
        capability: ESS (0x0001)
        signal: -37.00 dBm
        last seen: 25190 ms ago
        SSID: OpenWrt
        Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
        DS Parameter set: channel 161
        WMM:     * Parameter version 1
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
        HT capabilities:
                Capabilities: 0x1bce
                        HT20/HT40
                        SM Power Save disabled
                        RX HT40 SGI
                        TX STBC
                        RX STBC 3-streams
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 1/2 usec (0x02)
                HT TX/RX MCS rate indexes supported: 0-15

STA says Max AMSDU length is 3839 bytes, what was interesting: if I remove the
MAX-AMSDU-7935 option from the wireless configuration file of the AP, the STA
will show:
Max AMSDU length: 7935 bytes

then how to obtain the real 7935 bytes of the AMSDU length? Thank you !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120920/30101189/attachment.htm 

[ath9k-devel] (no subject)

[madcapmagician at netzero.net]

ok following the direction received from an e mail... said to send my e-mail to this address if I wanted to post.... so here it is in the from section =) hope i got this right, I hope you guys can help with an issue I am having


MadcapMagician
____________________________________________________________
Mom 55 dates 25
Breakthrough in Science Makes Mom Look Younger Without Surgery
http://thirdpartyoffers.netzero.net/TGL3231/500cbad239223ad1757ast53vuc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120723/953a104b/attachment.htm 

[ath9k-devel] (no subject)

[Mohammed Shafi]

On Sat, Jan 7, 2012 at 5:49 PM, Anup Krishnan <anuppeechanatt@gmail.com> wrote:
> Hi,
>
> Does ath9k_htc support mesh point mode in any linux kernel?

not yet but there was an RFC sent
http://permalink.gmane.org/gmane.linux.kernel.wireless.general/81716
		
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>



-- 
shafi

[ath9k-devel] (no subject)

[Anup Krishnan]

Hi,

Does ath9k_htc support mesh point mode in any linux kernel?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20120107/5fe1e13f/attachment.htm 

[ath9k-devel] (no subject)

[cherishl163]

Hi Shafi,
I download and decompress "compat-wireless-2.6.tar.bz2" then run script/driver-select ath9k.
When I run "make KLIB=/home/leo/NAS_AP_Team_NAND_SDK_20111116/SDK_3.0.0-sources/linux-kernel KLIB_BUILD=/home/leo/NAS_AP_Team_NAND_SDK_20111116/SDK_3.0.0-sources/linux-kernel", I got some errors. I save it in the attachment.Can you help me?




At 2011-12-05 17:02:13,"Mohammed Shafi" <shafi.wireless@gmail.com> wrote:
>2011/12/5 cherishl163 <cherishl163@163.com>:
>> Hi,
>> I want to develop a device using hostap to implement softap. I use the
>> kernel 2.6.31 and my wifi module is ar9285. But the kernel don't support
>> ar9285, so I want to cross-compile compat-wireless.But which version I
>> should use?
>
>http://linuxwireless.org/en/users/Download#Where_to_download_bleeding_edge
>
>> My develop platform is arm11.
>>
>>
>>
>> _______________________________________________
>> ath9k-devel mailing list
>> ath9k-devel at lists.ath9k.org
>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>
>
>
>
>-- 
>shafi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111205/a10cbb1d/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log
Type: application/octet-stream
Size: 23556 bytes
Desc: not available
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20111205/a10cbb1d/attachment-0001.obj 

[ath9k-devel] (no subject)

[David Goodenough]

On Saturday 15 Oct 2011, sekharjyoti deka wrote:
> Thanx Adrian,
> 
> For your valuable reply. but i was concentrating on modification of
> some sort of parameters like changing of slot timing and also the ack
> time to get maximal throughput of the network..Since i am trying to
> modify ath9k for long distance network like it should cover a distance
> about 3-4km with directional antenna( as wifi only covers upto 50m in
> default).. So this is my point. So if you can help me in modifying the
> code and also if you can provide some materials related it it'll be
> highly appreceated..
> 
> 
> your's sincerely
> Sekharjyoti
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
Support for this already exists:-

iw phy <phyname> set distance <distance>

No need to change anything.

David

[ath9k-devel] (no subject)

[sekharjyoti deka]

Thanx Adrian,

For your valuable reply. but i was concentrating on modification of
some sort of parameters like changing of slot timing and also the ack
time to get maximal throughput of the network..Since i am trying to
modify ath9k for long distance network like it should cover a distance
about 3-4km with directional antenna( as wifi only covers upto 50m in
default).. So this is my point. So if you can help me in modifying the
code and also if you can provide some materials related it it'll be
highly appreceated..


your's sincerely
Sekharjyoti

On 10/15/11, sekharjyoti deka <rd6793@gmail.com> wrote:
> Thanx Adrian,
>
> For your valuable reply. but i was concentrating on modification of
> some sort of parameters like changing of slot timing and also the ack
> time to get maximal throughput of the network..Since i am trying to
> modify ath9k for long distance network like it should cover a distance
> about 3-4km with directional antenna( as wifi only covers upto 50m in
> default).. So this is my point. So if you can help me in modifying the
> code and also if you can provide some materials related it it'll be
> highly appreceated..
>
>
> your's sincerely
> Sekharjyoti
>

[ath9k-devel] (no subject)

[sekharjyoti deka]

Thanx Adrian,

For your valuable reply. but i was concentrating on modification of
some sort of parameters like changing of slot timing and also the ack
time to get maximal throughput of the network..Since i am trying to
modify ath9k for long distance network like it should cover a distance
about 3-4km with directional antenna( as wifi only covers upto 50m in
default).. So this is my point. So if you can help me in modifying the
code and also if you can provide some materials related it it'll be
highly appreceated..


your's sincerely
Sekharjyoti

[ath9k-devel] (no subject)

[Alex Hacker]

On Sun, Sep 18, 2011 at 02:39:06PM +0800, Adrian Chadd wrote:
> On 18 September 2011 14:32, Alex Hacker <hacker@epn.ru> wrote:
> 
> > The chainmasks are limit set of antennas used for RX and TX, both settings can be
> > changed in debugfs 'ieee80211/phyX/ath9k'. The distance limit is all Aheros cards
> > property due to maximum setting for the ACK timeout. It can be set with
> > 'iw phy <phyname> distance <distance>' command. Of course, you need a high gain antenna
> > to achieve long range communication.
> 
> Just as a side-point; hasn't someone come up with a way of just doing
> software-based delayed ACK with Linux/FreeBSD, and ignoring the
> hardware-driven RTS/CTS/ACK retry stuff?
>
> Adrian

We do it in our propiertary driver, obviously not in FreeBSD or Linux. Longest link we
are tested in Australia is 74km it work well.

Regards,
Alex.

[ath9k-devel] (no subject)

[Adrian Chadd]

On 18 September 2011 14:32, Alex Hacker <hacker@epn.ru> wrote:

> The chainmasks are limit set of antennas used for RX and TX, both settings can be
> changed in debugfs 'ieee80211/phyX/ath9k'. The distance limit is all Aheros cards
> property due to maximum setting for the ACK timeout. It can be set with
> 'iw phy <phyname> distance <distance>' command. Of course, you need a high gain antenna
> to achieve long range communication.

Just as a side-point; hasn't someone come up with a way of just doing
software-based delayed ACK with Linux/FreeBSD, and ignoring the
hardware-driven RTS/CTS/ACK retry stuff?



Adrian

[ath9k-devel] (no subject)

[Alex Hacker]

On Sat, Sep 17, 2011 at 07:25:36PM +0530, subham das wrote:
>    Hello Alex,
>    Can you please describe a little about RX/TX chain masks setting to 1, and
>    about the maximum distance that you told was with reference to which
>    antenna or nic card.
> 
The chainmasks are limit set of antennas used for RX and TX, both settings can be
changed in debugfs 'ieee80211/phyX/ath9k'. The distance limit is all Aheros cards
property due to maximum setting for the ACK timeout. It can be set with
'iw phy <phyname> distance <distance>' command. Of course, you need a high gain antenna
to achieve long range communication.

Regards,
Alex.

[ath9k-devel] (no subject)

[subham das]

Hello Alex,
Can you please describe a little about RX/TX chain masks setting to 1, and
about the maximum distance that you told was with reference to which antenna
or nic card.

On Fri, Sep 16, 2011 at 10:42 PM, Alex Hacker <hacker@epn.ru> wrote:

> I think no any modifcations of the driver code are required. If your card
> has MIMO
> capability (based on AR9160, AR9220, AR9280, AR9380 or AR9390 chips) you
> need to set
> RX/TX chain masks to 1 and connect your antenna to the fisrst chain
> connector. For the
> long links you need to adjust coverage class value. Maximum distance
> limited by hardware
> is about 50km for 20MHz and 25km for 40MHz bandwidth.
>
> Regards,
> Alex.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110917/c95b825e/attachment.htm 

[ath9k-devel] (no subject)

[subham das]

Thank you every one, i shall surely try those out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110917/0b365216/attachment.htm 

[ath9k-devel] (no subject)

[Alex Hacker]

I think no any modifcations of the driver code are required. If your card has MIMO
capability (based on AR9160, AR9220, AR9280, AR9380 or AR9390 chips) you need to set
RX/TX chain masks to 1 and connect your antenna to the fisrst chain connector. For the
long links you need to adjust coverage class value. Maximum distance limited by hardware
is about 50km for 20MHz and 25km for 40MHz bandwidth.

Regards,
Alex.

[ath9k-devel] (no subject)

[Peter Stuge]

subham das wrote:
> I would like to connect a Directional Antenna to my laptop Atheros
> wireless card by some way/means and still use the ath9k driver

The driver doesn't care much about the antenna. You just need to
connect your directional antenna to the u.FL connector on the wifi
card, inside your laptop. There's not likely any external antenna
connector, so you'll probably have to modify the laptop case to make
dealing with the external antenna convenient.


//Peter

[ath9k-devel] (no subject)

[subham das]

I would like to connect a Directional Antenna to my laptop Atheros wireless
card by some way/means and still use the ath9k driver to transmit/carry the
network connection to a far of (long) distance as much as possible on the
Line Of Sight. My basic idea is transmitting/carrying ( not routing) the
network connection to a long distance, wirelessly because doing the same
using wired would be expensive compared to the former. So my question is, if
this is feasible and if yes then which Atheros wireless card would be best
in this case and if necessary which files/codes to be changed so that
efficiency would increase interms of range/distance in carrying the internet
connection in a direction ( not routing in omni-direction).

Thanking you in advance

Subham Das

You can also email me at das.subham87 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110916/8c51f591/attachment.htm 

[ath9k-devel] (no subject)

[ionut ionescu]

stop
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20110603/441f3711/attachment.htm 

[ath9k-devel] (no subject)

[Kemble Wagner]

http://dehler-pollozek.de/images/aast.php
http://www.youtube.com/watch?v=RUzLhHH7gHg

[ath9k-devel] (no subject)

[Jaime Lozano Padilla]

 

 

Atentamente:

Jaime Lozano Padilla

Administrador de Bases de Datos Oracle

Tel?fono:  5322-0497 ext. 85454

Email: jaime.lozani at fovissste.gob.mx

 

 

 

ADVERTENCIA LEGAL

Este mensaje contiene informaci?n confidencial y privilegiada. Se entiende dirigido y para uso exclusivo del destinatario, por lo que su contenido no podr? divulgarse, distribuirse y/o difundirse por ning?n medio sin la previa autorizaci?n del emisor original. Si recibi? usted este mensaje y no es el destinatario a quien fue enviado, se le proh?be su utilizaci?n total o parcial para cualquier fin. Por favor contacte inmediatamente a quien le env?a este mensaje si usted lo ha recibido por error. 

 

Antes de imprimir este mensaje, por favor compruebe si es verdaderamente necesario hacerlo.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20091110/567d4c5e/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 15091 bytes
Desc: image001.png
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20091110/567d4c5e/attachment-0001.png 

[ath9k-devel] (no subject)

[Matt Fog]

Hello,

 Please unsubscribe me from this mailing list. I accidently signed up for the wrong one.

 

Thank you

 

Matt
 		 	   		  
_________________________________________________________________
New Windows 7: Find the right PC for you. Learn more.
http://www.microsoft.com/uk/windows/buy/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20091105/dfb7f234/attachment.htm 

[ath9k-devel] (no subject)

[Will Dyson]

On Sat, May 23, 2009 at 1:30 PM, Jeff Hansen <x@jeffhansen.com> wrote:
> Hello,
>
> I have a TrendNet 652-BRP running OpenWRT + ath9k very well. ?The only
> problem is that the beacon gets stuck maybe once a day. ?After Vasanthakumar
> Thiagarajan's "ath9k: cleanup beacon parameters configuration" patch, ath9k
> would nearly re-configure the beacons after it detected the stuck beacon,
> and did a reset. ?But it would fail the SC_OP_TSF_RESET check in
> ath_beacon_config_ap. ?This patch gets the beacon fully reconfigured after
> the reset.

I too have been seeing the problem where beacons stop with ath9k on an
ar71xx-based router.

I've been running with this patch for about 48 hours, and the beacons
are still going. Previously, they would stop after 6-12 hours. Looks
good!

-- 
Will Dyson

[ath9k-devel] (no subject)

[Jeff Hansen]

[ath9k-devel] (no subject)

[Jeff Hansen]

[ath9k-devel] (no subject)

[Jeff Hansen]

[ath9k-devel] (no subject)

[Jeff Hansen]

[ath9k-devel] (no subject)

[Luis R. Rodriguez]

On Sat, May 23, 2009 at 10:30 AM, Jeff Hansen <x@jeffhansen.com> wrote:
> Hello,
>
> I have a TrendNet 652-BRP running OpenWRT + ath9k very well. ?The only
> problem is that the beacon gets stuck maybe once a day. ?After Vasanthakumar
> Thiagarajan's "ath9k: cleanup beacon parameters configuration" patch, ath9k
> would nearly re-configure the beacons after it detected the stuck beacon,
> and did a reset. ?But it would fail the SC_OP_TSF_RESET check in
> ath_beacon_config_ap. ?This patch gets the beacon fully reconfigured after
> the reset.

Thanks Jeff, can you please submit to linux-wireless with a
Signed-off-by, you can read what that implies in
Documentation/SubmittingPatches, specifically refer to the
"Developer's Certificate of Origin 1.1". Also please refer to:

http://wireless.kernel.org/en/developers/Documentation/SubmittingPatches

  Luis

[ath9k-devel] (no subject)

[Jeff Hansen]

Hello,

I have a TrendNet 652-BRP running OpenWRT + ath9k very well.  The only 
problem is that the beacon gets stuck maybe once a day.  After 
Vasanthakumar Thiagarajan's "ath9k: cleanup beacon parameters 
configuration" patch, ath9k would nearly re-configure the beacons after it 
detected the stuck beacon, and did a reset.  But it would fail the 
SC_OP_TSF_RESET check in ath_beacon_config_ap.  This patch gets the beacon 
fully reconfigured after the reset.

-Jeff

---------------------------------------------------
"If someone's gotta do it, it might as well be me."
                 x at jeffhansen.com
-------------- next part --------------
--- ./drivers/net/wireless/ath/ath9k/beacon.c.orig	2009-05-20 12:53:01.000000000 +0000
+++ ./drivers/net/wireless/ath/ath9k/beacon.c	2009-05-23 13:36:10.000000000 +0000
@@ -411,6 +411,7 @@
 		} else if (sc->beacon.bmisscnt >= BSTUCK_THRESH) {
 			DPRINTF(sc, ATH_DBG_BEACON,
 				"beacon is officially stuck\n");
+			sc->sc_flags |= SC_OP_TSF_RESET;
 			ath_reset(sc, false);
 		}
 

[ath9k-devel] (no subject)

[Evandro]

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090218/d38350df/attachment.htm 

[ath9k-devel] (no subject)

[Luis R. Rodriguez]

On Thu, Jan 29, 2009 at 09:05:23AM -0800, Voitek Burski wrote:
> May I be exclude from the list.

You unsubscribe here:

https://lists.ath9k.org/mailman/listinfo/ath9k-devel

  Luis

[ath9k-devel] (no subject)

[Voitek Burski]

May I be exclude from the list. 


With regards

Voitek Burski




      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090129/18e63d96/attachment.htm 

[ath9k-devel] (no subject)

[Vaibhav Chhabra]

I tried Intrepid but for some reason the wireless was too slow... just logging to yahoo mail took like a minute or so... I don't know i am using the same .config file from my 2.6.25 kernel when i compile 2.6.27-rcx kernels (from kernel.com) and enable the (new) ath9k driver before compiling. 

Last night i was amazed by the speed when i used the non-kernel driver. I mean i actually went to hulu.com and watch a high-res vid with tcpdump -v running in the background. 

Maybe the debian kernel is patched with something i dont know about than the kernel from kernel.com

Something about tcpdump was it kept saying "unknown 802.11 header (3)" something like that at times. 

--- On Wed, 9/24/08, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
From: Luis R. Rodriguez <lrodriguez@atheros.com>
Subject: Re: [ath9k-devel] (no subject)
To: "Vaibhav Chhabra" <vib_chhabra@yahoo.com>
Cc: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Date: Wednesday, September 24, 2008, 4:09 PM

On Wed, Sep 24, 2008 at 01:38:25PM -0700, Luis Rodriguez wrote:
> On Wed, Sep 24, 2008 at 01:26:01PM -0700, Vaibhav Chhabra wrote:
> > so last night i reverted back to linux-source-2.6.26 (debian) and
used
"compat-wireless-ath9k-20080916.tar.gz<http://rapidshare.com/files/145746749/compat-wireless-ath9k-20080916.tar.gz.html>"
from: http://ubuntuforums.org/showthread.php?t=907129

I also forgot to mention Ubuntu Intrepid now has 2.6.27 so if you
like too, you can just upgrade to Intrepid and use 2.6.27.

  Luis



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20080924/542d5eef/attachment.htm 

[ath9k-devel] (no subject)

[Luis R. Rodriguez]

On Wed, Sep 24, 2008 at 01:38:25PM -0700, Luis Rodriguez wrote:
> On Wed, Sep 24, 2008 at 01:26:01PM -0700, Vaibhav Chhabra wrote:
> > so last night i reverted back to linux-source-2.6.26 (debian) and used "compat-wireless-ath9k-20080916.tar.gz<http://rapidshare.com/files/145746749/compat-wireless-ath9k-20080916.tar.gz.html>" from: http://ubuntuforums.org/showthread.php?t=907129

I also forgot to mention Ubuntu Intrepid now has 2.6.27 so if you
like too, you can just upgrade to Intrepid and use 2.6.27.

  Luis

[ath9k-devel] (no subject)

[Luis R. Rodriguez]

On Wed, Sep 24, 2008 at 01:26:01PM -0700, Vaibhav Chhabra wrote:
> so last night i reverted back to linux-source-2.6.26 (debian) and used "compat-wireless-ath9k-20080916.tar.gz<http://rapidshare.com/files/145746749/compat-wireless-ath9k-20080916.tar.gz.html>" from: http://ubuntuforums.org/showthread.php?t=907129

We now have ath9k in compat-wireless-old (for kernels <= 2.6.26).
But please note more effort is being put into updating ath9k
upstream. compat-wireless-old essentially is a fork of mac80211
and its drivers for support on older kernels. Developers wishing
to contribute to it can further bring patches from wireless-testing
to it (please send patches to compat-masters list).

> you have to modify the script and remove the uname -r checks from dependencies (for non-ubuntu users that use a debian flavor)
> 
> The wireless works fine, just at times drops connections the things that fixes it is removing the module and loading it again:
> rmmod ath9k
> modprobe ath9k
> iwconfig wlan0 essid ...
> dhclient wlan0
> 
> don't know if this helps the dev's to debug (regarding the dropped connection issues) or someone trying to get AR9281 wireless cards to work on any debian flavor. Any feed back would be appreciated.

There have been some new patches which fix some drop connection issues
(group key patch) which has been pushed out to 2.6.27 and on
wireless-testing.

I'd recommend to try 2.6.27-rc7 with the group key patch and MIB
interrupt disable patch. I guess we should put these pending patches
somewhere, then we just have to apply them to compat-wireless-old too.

Help with this is greatly welcomed as compat-wireless-old is lead
by the help of the community.

  Luis

[ath9k-devel] (no subject)

[Vaibhav Chhabra]

so last night i reverted back to linux-source-2.6.26 (debian) and used "compat-wireless-ath9k-20080916.tar.gz" from: http://ubuntuforums.org/showthread.php?t=907129

you have to modify the script and remove the uname -r checks from dependencies (for non-ubuntu users that use a debian flavor)

The wireless works fine, just at times drops connections the things that fixes it is removing the module and loading it again:
rmmod ath9k
modprobe ath9k
iwconfig wlan0 essid ...
dhclient wlan0

don't know if this helps the dev's to debug (regarding the dropped connection issues) or someone trying to get AR9281 wireless cards to work on any debian flavor. Any feed back would be appreciated.

Thanks,
Vib


--- On Tue, 9/16/08, Vaibhav Chhabra <vib_chhabra@yahoo.com> wrote:
From: Vaibhav Chhabra <vib_chhabra@yahoo.com>
Subject: Re: [ath9k-devel] (no subject)
To: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>, "Jean Schurger" <jean@schurger.org>
Date: Tuesday, September 16, 2008, 1:51 PM

will try that... and post results. Thanks


--- On Tue, 9/16/08, Jean Schurger <jean@schurger.org> wrote:

> From: Jean Schurger <jean@schurger.org>
> Subject: Re: [ath9k-devel] (no subject)
> To: "ath9k-devel at lists.ath9k.org"
<ath9k-devel@lists.ath9k.org>
> Date: Tuesday, September 16, 2008, 1:30 PM
> Le mardi 16 septembre 2008 ? 11:21 -0700, Vaibhav Chhabra a
> ?crit :
> 
> > "iwlist wlan0 scan" does show my router. 
> > I have another box with broadcom wireless card and it
> works fine
> > running gentoo linux.
> 
> 
> can you monitor the "trafic" betwin your aheros
> card and your AP ? 
> 
> (using aircrack-ng, tcpdump, whatever...) ?
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel


      
_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20080924/d8e07e34/attachment.htm 

[ath9k-devel] (no subject)

[Vaibhav Chhabra]

will try that... and post results. Thanks


--- On Tue, 9/16/08, Jean Schurger <jean@schurger.org> wrote:

> From: Jean Schurger <jean@schurger.org>
> Subject: Re: [ath9k-devel] (no subject)
> To: "ath9k-devel at lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
> Date: Tuesday, September 16, 2008, 1:30 PM
> Le mardi 16 septembre 2008 ? 11:21 -0700, Vaibhav Chhabra a
> ?crit :
> 
> > "iwlist wlan0 scan" does show my router. 
> > I have another box with broadcom wireless card and it
> works fine
> > running gentoo linux.
> 
> 
> can you monitor the "trafic" betwin your aheros
> card and your AP ? 
> 
> (using aircrack-ng, tcpdump, whatever...) ?
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel


      

[ath9k-devel] (no subject)

[Jean Schurger]

Le mardi 16 septembre 2008 ? 11:21 -0700, Vaibhav Chhabra a ?crit :

> "iwlist wlan0 scan" does show my router. 
> I have another box with broadcom wireless card and it works fine
> running gentoo linux.


can you monitor the "trafic" betwin your aheros card and your AP ? 

(using aircrack-ng, tcpdump, whatever...) ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20080916/4c75752c/attachment.htm 

[ath9k-devel] (no subject)

[Vaibhav Chhabra]

"iwlist wlan0 scan" does show my router. 
I have another box with broadcom wireless card and it works fine running gentoo linux.

--- On Tue, 9/16/08, Jean Schurger <jean@schurger.org> wrote:

From: Jean Schurger <jean@schurger.org>
Subject: Re: [ath9k-devel] (no subject)
To: ath9k-devel at lists.ath9k.org
Date: Tuesday, September 16, 2008, 1:15 PM


Le mardi 16 septembre 2008 ? 11:07 -0700, Vaibhav Chhabra a ?crit?:





I recently installed Elive (debian flavor) of linux and compiled kernel 2.6.27-rc6 inorder to get ath9k. My card is a atheros AR9281. I use 802.11g at home. ? What i can't seem to understand is that i can't get a dhcp offer. I am sitting right next to my router and get no ip on: dhclient wlan0. ? i have checked everything here is the command i use to set my wireless when i have a my key enabled: iwconfig wlan0 essid "rcvc" key s:xxxx open channel 8 mode Managed ? Any thing i missed? Thanks for the help. 
does "iwlist wlan0 scanning" show your AP ?

can you use an other box or wifi card supporting monitor mode at the same time to try to see if something happend (go out of your card) ?


_______________________________________________
ath9k-devel mailing list
ath9k-devel at lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20080916/3f637815/attachment.htm 

[ath9k-devel] (no subject)

[Jean Schurger]

Le mardi 16 septembre 2008 ? 11:07 -0700, Vaibhav Chhabra a ?crit :

> I recently installed Elive (debian flavor) of linux and compiled
> kernel 2.6.27-rc6 inorder to get ath9k. My card is a atheros AR9281. I
> use 802.11g at home. 
>  
> What i can't seem to understand is that i can't get a dhcp offer. I am
> sitting right next to my router and get no ip on: dhclient wlan0.
>  
> i have checked everything here is the command i use to set my wireless
> when i have a my key enabled:
> iwconfig wlan0 essid "rcvc" key s:xxxx open channel 8 mode Managed
>  
> Any thing i missed? Thanks for the help.


does "iwlist wlan0 scanning" show your AP ?

can you use an other box or wifi card supporting monitor mode at the
same time to try to see if something happend (go out of your card) ?


 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20080916/5bf3889f/attachment.htm 

[ath9k-devel] (no subject)

[Vaibhav Chhabra]

I recently installed Elive (debian flavor) of linux and compiled kernel 2.6.27-rc6 inorder to get ath9k. My card is a atheros AR9281. I use 802.11g at home. 
?
What i can't seem to understand is that i can't get a dhcp offer. I am sitting right next to my router and get no ip on: dhclient wlan0.
?
i have checked everything here is the command i use to set my wireless when i have a my key enabled:
iwconfig wlan0 essid "rcvc" key s:xxxx open channel 8 mode Managed
?
Any thing i missed? Thanks for the help.


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20080916/998106b0/attachment.htm