168c:002a [Asus M51Tr] ath chip reset failed

See the attached text file for an excerpt of syslog

This would be a kernel bug, reassigning to 'linux'.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1016181

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I've run

apport-collect 1016181

And the missing logs are now submitted. Changed status to confirmed

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc3-quantal/

I've succesfully installed the following debs

linux-image-3.5.0-030500rc3-generic_3.5.0-030500rc3.201206162135_i386.deb
linux-image-extra-3.5.0-030500rc3-generic_3.5.0-030500rc3.201206162135_i386.deb

System starts up normally. :-)

Today i did not experience the problem with the older kernel, so te
problem seems to have an unsteady interval (sometimes several times 5+
times a day, sometimes not at all). I will try for a few days and see if
the problem occurs again and do as you mentioned according to the test
results.

Thanks

Op 22-06-12 20:50, Joseph Salisbury schreef:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v3.5kernel[0] (Not a kernel in the daily directory) and install both the
> linux-image and linux-image-extra .deb packages.
>
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag(Only that one tag, please leave the other tags).
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the 'needs-
> upstream-testing' text.
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
> Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc3-quantal/
>
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: needs-upstream-testing
>

Bug exists in upstream kernel. Occurred 2 times today within an hour. Changed tag needs-upstream-testing to kernel-bug-exists-upstream and confirmed bug.

Ubuntu 12.04 kernel 3.2.0-29-generic with atheros wireless driver same issue:
it could stay connected for a long time but then all of a sudden the wireless drops.

chipset:
03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev ff)

syslog extract:
ath: phy0: Unable to set channel
ath: phy0: Failed to stop TX DMA, queues=0x10f!
ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: phy0: Chip reset failed
ath: phy0: Unable to reset channel, reset status -22

all the previous kernel releases since kernel 3.0 had the same issue as far as I can remember.
Installing compat-wireless didn' t resolve the problem

I am having the exact same problem. I have a brand new Toshiba L840 with an Atheros AR9485 Wireless Network Adapter. I am running Ubuntu 12.04 32-bit and I have tried upgrading to the Q-Series ppa 3.5.0-14 Linux Kernel and the problem still persists. Is there any fix for this? I am considering buying a different wireless card as the solution if there is now way to fix this currently...

I've got the same problems. I tried buying another USB adapter only to find that that one has another, equally annoying problem. If there's any information I can provide please let me know.

I've exactly the same problem. I have an COMPAQ CQ58 130SF
I am running ubuntu 12.10 64bit. I've upgraded to mainline kernel to test if the bug persits... it persits...

The log when the connection drop :
Dec 10 22:17:08 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.293443] ath: phy0: Failed to wakeup in 500us
Dec 10 22:17:08 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.342506] ath: phy0: Failed to wakeup in 500us
Dec 10 22:17:08 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.458411] ath: phy0: Failed to wakeup in 500us
Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.574446] ath: phy0: Failed to wakeup in 500us
Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.591914] ath: phy0: Failed to wakeup in 500us
Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.603343] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.603385] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.667323] ath: phy0: Failed to stop TX DMA, queues=0x10f!
Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.786952] ath: phy0: Chip reset failed
Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.786959] ath: phy0: Unable to reset channel, reset status -22
Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1099.954232] ath: phy0: Failed to wakeup in 500us
Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.494169] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.494186] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.564164] ath: phy0: Failed to stop TX DMA, queues=0x10f!
Dec 10 22:17:11 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.680471] ath: phy0: Chip reset failed
Dec 10 22:17:11 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.680481] ath: phy0: Unable to reset channel, reset status -22
Dec 10 22:17:11 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.680521] ath: phy0: Unable to set channel

The only way to recover is to reboot the PC...

Hello installing kernel 3.6 self compiled resolved this issue. Try to
install the new kernel compiling from source and then let me know.
Giuseppe
Il giorno 10/dic/2012 22:41, "Hubert FONGARNAND" <email address hidden>
ha scritto:

> I've exactly the same problem. I have an COMPAQ CQ58 130SF
> I am running ubuntu 12.10 64bit. I've upgraded to mainline kernel to test
> if the bug persits... it persits...
>
> The log when the connection drop :
> Dec 10 22:17:08 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.293443]
> ath: phy0: Failed to wakeup in 500us
> Dec 10 22:17:08 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.342506]
> ath: phy0: Failed to wakeup in 500us
> Dec 10 22:17:08 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.458411]
> ath: phy0: Failed to wakeup in 500us
> Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.574446]
> ath: phy0: Failed to wakeup in 500us
> Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.591914]
> ath: phy0: Failed to wakeup in 500us
> Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.603343]
> ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff
> AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.603385]
> ath: phy0: Could not stop RX, we could be confusing the DMA engine when we
> start RX up
> Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.667323]
> ath: phy0: Failed to stop TX DMA, queues=0x10f!
> Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.786952]
> ath: phy0: Chip reset failed
> Dec 10 22:17:09 hubert-Presario-CQ58-Notebook-PC kernel: [ 1098.786959]
> ath: phy0: Unable to reset channel, reset status -22
> Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1099.954232]
> ath: phy0: Failed to wakeup in 500us
> Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.494169]
> ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff
> AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.494186]
> ath: phy0: Could not stop RX, we could be confusing the DMA engine when we
> start RX up
> Dec 10 22:17:10 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.564164]
> ath: phy0: Failed to stop TX DMA, queues=0x10f!
> Dec 10 22:17:11 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.680471]
> ath: phy0: Chip reset failed
> Dec 10 22:17:11 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.680481]
> ath: phy0: Unable to reset channel, reset status -22
> Dec 10 22:17:11 hubert-Presario-CQ58-Notebook-PC kernel: [ 1100.680521]
> ath: phy0: Unable to set channel
>
>
> The only way to recover is to reboot the PC...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1016181
>
> Title:
> ath chip reset failed
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> Since upgrading to U 12.04 i experience wireless lan drops. Sometimes
> just a few minutes after system startup, sometimes after hours of
> using my system.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: network-manager 0.9.4.0-0ubuntu...

I am having the exact same problem with Atheros AR9485. Using Ubuntu 12.10. Now I have tried with kernel "3.6.3-030603-generic #201210211349 SMP Sun Oct 21 17:50:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux". This did NOT solve the problem. The problem persists with kernel 3.6.3!

Same proble here kernel 3.5.0-25 amd64 with Ubuntu 12.04.2 and Atheros AR9485. It seems to happen when te connection is weak and it is lost and restablished many times.

I also have the AR9485, but only started seeing this with kernel 3.5.0-25 amd64. The previous 3.5.0-24 amd64 seems to be okay.

Hi there,
I have an AR9285 adapter and got crazy with it. As described by others I also had the following errors irregularly and my wireless-adaper then didn't wake up AFTER resume from suspend and just a reboot could revive it. I'm running Ubuntu 10.04 Lucid and tried several kernels and backported wireless drivers. I also tried ndiswrapper with several windows-drivers but the same problem occurred again.

[ 7144.465844] ath: Chip reset failed
[ 7144.465861] ath: Unable to reset channel (2422 MHz), reset status -22
or
[107330.931497] ath9k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[107330.931522] ath9k 0000:02:00.0: setting latency timer to 64
[107331.046361] ath9k 0000:02:00.0: Failed to initialize device
[107331.046445] ath9k 0000:02:00.0: PCI INT A disabled
[107331.046468] ath9k: probe of 0000:02:00.0 failed with error -5

The network-manager then says the device is deactivated. However I found a simple WORKAROUND which more or less fixed this issue. Try:

sudo iwconfig wlan0 power off

Also I disabled in gconf-editor:
/apps/gnome-power-manager/general/network_sleep

Probably the first command did the trick. It seems to turn off the power management of the adapter what should result in higher power consumption. Nevertheless better then rebooting all the time.
Currently I'm running 3.0.0-31-generic on an Asus 1005PE. I hope it won't occur again. Btw, I red somewhere that this has something to do with static electricity and the USB ports (?). But I can't find the link anymore.

Any other progress on how to really fix this?

Good luck!

Mmm... your last comment :" I red somewhere that this has something to do with static electricity and the USB ports"
inspire me!

Because since i don't use the USB dongle for my wireless mouse anymore, the problem has gone! So the problem is (in my case) clearly related to USB ports...

Maybe the patch in this https://bugzilla.redhat.com/show_bug.cgi?id=892811 could help?

Running kernel 3.9.3; the problem still occurs.

For the first time I just observed that wireless LAN failed on my Asus n55s.

I can assert that this hasn't been happening for weeks. It may be the first time this happens at all on this machine. Wireless LAN has always worked well, and now failing.

For the past hour and the half, dmesg spits around 30 messages per second burst rate, a repetition of

Jun 29 13:00:29 n55sf-l kernel: [727461.166426] ath: phy0: Chip reset failed
Jun 29 13:00:29 n55sf-l kernel: [727461.166428] ath: phy0: Unable to reset channel, reset status -22
Jun 29 13:00:29 n55sf-l kernel: [727461.166432] ath: phy0: Unable to set channel
Jun 29 13:00:29 n55sf-l kernel: [727461.180256] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
Jun 29 13:00:29 n55sf-l kernel: [727461.180268] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
Jun 29 13:00:29 n55sf-l kernel: [727461.251940] ath: phy0: Failed to stop TX DMA, queues=0x10f!

FWIW, here are the first messages before that endless loop :

Jun 29 12:33:45 n55sf-l kernel: [725859.090225] irq 17: nobody cared (try booting with the "irqpoll" option)
Jun 29 12:33:45 n55sf-l kernel: [725859.090240] Pid: 0, comm: swapper/0 Tainted: G O 3.5.0-34-generic #55-Ubuntu
Jun 29 12:33:45 n55sf-l kernel: [725859.090244] Call Trace:
Jun 29 12:33:45 n55sf-l kernel: [725859.090248] <IRQ> [<ffffffff810e1a8d>] __report_bad_irq+0x3d/0xe0
Jun 29 12:33:45 n55sf-l kernel: [725859.090269] [<ffffffff810e1f52>] note_interrupt+0x1c2/0x210
Jun 29 12:33:45 n55sf-l kernel: [725859.090282] [<ffffffff81391f8a>] ? intel_idle+0xea/0x150
Jun 29 12:33:45 n55sf-l kernel: [725859.090292] [<ffffffff810df6f7>] handle_irq_event_percpu+0xa7/0x1f0
Jun 29 12:33:45 n55sf-l kernel: [725859.090300] [<ffffffff810df88e>] handle_irq_event+0x4e/0x80
Jun 29 12:33:45 n55sf-l kernel: [725859.090307] [<ffffffff810e2a8a>] handle_fasteoi_irq+0x5a/0x100
Jun 29 12:33:45 n55sf-l kernel: [725859.090319] [<ffffffff81015072>] handle_irq+0x22/0x40
Jun 29 12:33:45 n55sf-l kernel: [725859.090328] [<ffffffff8168c08a>] do_IRQ+0x5a/0xe0
Jun 29 12:33:45 n55sf-l kernel: [725859.090340] [<ffffffff8168262a>] common_interrupt+0x6a/0x6a
Jun 29 12:33:45 n55sf-l kernel: [725859.090343] <EOI> [<ffffffff81391f8a>] ? intel_idle+0xea/0x150
Jun 29 12:33:45 n55sf-l kernel: [725859.090359] [<ffffffff81391f6b>] ? intel_idle+0xcb/0x150
Jun 29 12:33:45 n55sf-l kernel: [725859.090371] [<ffffffff81525f09>] cpuidle_enter+0x19/0x20
Jun 29 12:33:45 n55sf-l kernel: [725859.090378] [<ffffffff81526549>] cpuidle_idle_call+0xa9/0x240
Jun 29 12:33:45 n55sf-l kernel: [725859.090386] [<ffffffff8101c45f>] cpu_idle+0xaf/0x120
Jun 29 12:33:45 n55sf-l kernel: [725859.090394] [<ffffffff8164f52e>] rest_init+0x72/0x74
Jun 29 12:33:45 n55sf-l kernel: [725859.090405] [<ffffffff81cf3bf3>] start_kernel+0x3cf/0x3dc
Jun 29 12:33:45 n55sf-l kernel: [725859.090414] [<ffffffff81cf3673>] ? do_early_param+0x91/0x91
Jun 29 12:33:45 n55sf-l kernel: [725859.090424] [<ffffffff81cf3356>] x86_64_start_reservations+0x131/0x135
Jun 29 12:33:45 n55sf-l kernel: [725859.090432] [<ffffffff81cf345a>] x86_64_start_kernel+0x100/0x10f
Jun 29 12:3...

I rebooted a few hours after the previous comment (yesterday). Problem happened again today. Nothing known to be new in the environment. Kernel was 3.5.0-34 since June 14th and bug happened only starting June 29th, so it does not look like a kernel-level regression.

Could remarkably high solar activity ( source http://www.ibtimes.com/solar-activity-cycle-peaks-2013-more-solar-flares-expected-later-year-1302041 ) cause unusual wifi interference that could broaden the scope of this bug to hardware/environment that are usually unaffected ? ;-/

Anyway, a workaround is to turn off wifi and use wired network.

Evertjan Garretsen, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Though I'm not from Ubuntu clan (so I'm not reopening bug), I do have the same problem on Linux 3.4.58 i686. My adapter is AR9285 (EEE PC 1215b)

When I do `ifconfig wlp1s0 up`, I get

[98739.884046] ath: phy0: Chip reset failed
[98739.884050] ath: phy0: Unable to reset hardware; reset status -22 (freq 2462 Mhz)

Just to note - last time I used wireless mouse (static USB electricity lol), but two times it occured on its own (in three days).

Essential log

dhcpcd : wlp1s0: carrier lost
kernel : [98739.773400] ath: phy0: Failed to stop TX DMA, queues=0x10f!
kernel : [98739.712877] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
kernel : [98739.712897] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
kernel : [98739.884046] ath: phy0: Chip reset failed
kernel : [98739.884050] ath: phy0: Unable to reset channel, reset status -22
kernel : [98739.884055] ath: phy0: Unable to set channel

After removed and inserted back modules ath, ath9k, ath9k_hw, ath9_common, mac80211 my wireless adapter is no longer recognized. dmesg tells something like

ath: phy0: Couldn't reset chip
ath: phy0: Unable to initialize hardware; initialization status -5

Same error here:

ath: phy0: failed to stop tx dma, queues=0x004!

With 12.04 and Dell XPS 13 Developer Edition.

Christian Vielma, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Did someone watch at https://bugzilla.redhat.com/show_bug.cgi?id=892811? It seems to fix the bug! I am still affected on 3.8.0-30-generic

Dario, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Some extra information: the warnings stop and WLAN goes back to normal function when I restart my wireless router. Thank you.

cheers,

n@zgul, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

This bug is (most probably) related to power_save issues of the Ath9K module.

WORKAROUND: Disabling power saving mode (iw dev wlan0 set power_save off) fixed the problem. I added the following udev rule to set it right:

/etc/udev/rules.d/70-wifi-ath9k.rules

## DISABLE POWERSAVE for Atheros 9K Wireless Network Adapters
ACTION=="add", SUBSYSTEM=="net", KERNEL=="wlan*" DRIVERS=="ath9k" RUN+="/sbin/iw dev %k set power_save off"

Dear Christopher,

Unfortunatelly, I consider my hardware profile private information.
Therefore, I'm including only the information which I consider relevant.

MachineType:
       ASUSTeK Computer INC. 1015P
RelatedPackageVersions:
       linux-restricted-modules-3.5.0-42-generic
       linux-backports-modules-3.5.0-42-generic
       linux-firmware 1.95.1
PCI Information:
01:00.0 Ethernet controller: Atheros Communications Inc. AR8132 Fast Ethernet (rev c0)
 Subsystem: ASUSTeK Computer Inc. Device 838a
 Physical Slot: eeepc-wifi
 Flags: fast devsel, IRQ 46
 Memory at f7fc0000 (64-bit, non-prefetchable) [disabled] [size=256K]
 I/O ports at ec00 [disabled] [size=128]
 Capabilities: [40] Power Management version 3
 Capabilities: [48] MSI: Enable+ Count=1/1 Maskable- 64bit+
 Capabilities: [58] Express Endpoint, MSI 00
 Capabilities: [6c] Vital Product Data
 Capabilities: [100] Advanced Error Reporting
 Capabilities: [180] Device Serial Number <omitted>
 Kernel driver in use: atl1c
 Kernel modules: atl1c
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
 Subsystem: AzureWave AW-NE785 / AW-NE785H 802.11bgn Wireless Full or Half-size Mini PCIe Card
 Flags: bus master, fast devsel, latency 0, IRQ 17
 Memory at fbff0000 (64-bit, non-prefetchable) [size=64K]
 Capabilities: [40] Power Management version 3
 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit-
 Capabilities: [60] Express Legacy Endpoint, MSI 00
 Capabilities: [100] Advanced Error Reporting
 Capabilities: [140] Virtual Channel
 Capabilities: [160] Device Serial Number <omitted>
 Capabilities: [170] Power Budgeting <?>
 Kernel driver in use: ath9k
 Kernel modules: ath9k

Please specify if any additional debug information required (/sys/kernel/debug/ieee80211/phy0/ath9k).

Relevant tickets from other systems:
* https://dev.openwrt.org/ticket/9654
* https://dev.openwrt.org/ticket/11862
* https://bugzilla.kernel.org/show_bug.cgi?id=56301
* https://bugzilla.redhat.com/show_bug.cgi?id=892811
* https://bugzilla.redhat.com/show_bug.cgi?id=929217
* https://bugzilla.novell.com/show_bug.cgi?id=841675
* http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727772
* https://bbs.archlinux.org/viewtopic.php?pid=1217830
* https://bugzilla.kernel.org/show_bug.cgi?id=53171
* http://svn.dd-wrt.com/ticket/2952

Duplicates/Similar:
* https://bugs.launchpad.net/bugs/1102007
* https://bugs.launchpad.net/bugs/1032826
* https://bugs.launchpad.net/bugs/1234512

The bug is reproducible on my system.

I'm having the same problem in Ubuntu 13.10 on an Asus N53SV laptop. I have disabled the power saving as described in #54, I'll report if that fixes the problem. I'm also affected by the following bug, which seems to be caused by suspend/wake up issues, it might be related (in my case)? https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1184262

Here are some of the log messages after the wifi dies:

kernel: [11290.855711] ath: phy0: Unable to reset channel, reset status -22
kernel: [11290.855722] ath: phy0: Unable to set channel
kernel: [11290.972455] ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff
kernel: [11290.985712] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
kernel: [11295.325896] ath: phy0: Failed to wakeup in 500us
kernel: [11295.444032] ath: phy0: RX failed to go idle in 10 ms RXSM=0xffffffff
kernel: [11295.457584] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
kernel: [11295.669271] ath: phy0: Failed to wakeup in 500us
kernel: [11295.738664] ath: phy0: Failed to stop TX DMA, queues=0x18f!
kernel: [11295.752254] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
kernel: [11295.752765] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
kernel: [11295.870951] ath: phy0: Chip reset failed
kernel: [11295.870958] ath: phy0: Unable to reset channel, reset status -22
kernel: [11295.870991] ath: phy0: Unable to set channel
kernel: [11295.940392] ath: phy0: Failed to stop TX DMA, queues=0x18f!
kernel: [11295.953969] ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
kernel: [11295.954025] ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up
kernel: [11296.072215] ath: phy0: Chip reset failed

Z.D. / Sicco van Sas, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Christopher, please forgive me for NOT understanding. This bug is floating around for months now, and the submitters only get automated replies. ALL information was provided in the various bug reports. Consider, for example, the following duplicate/similar bugs:
* bug 773154 – Incomplete; full info included; affects 46 people.
* bug 947697 – Expired; affects 20 people.
* bug 1166865 – Expired; full info included; affects 3 people.
* bug 1168819 – Confirmed; full info included; affects 8 people.
* bug 1173681 – Incomplete; full info included; affects 11 people; WORKAROUND.
* bug 1199132 – Expired; full info included; affects 3 people.

Z.D., the reason you do not understand is you did not fully review the documentation previously mentioned to you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1016181/comments/59 . None of the reports you are posting (which isn't terribly helpful) are considered duplicates, similar, or having provided full info at this time for the reasons already documented to you. Please stop posting to this report.