[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
Cristian Aravena Romero, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at the very top line at the top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed. Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Thank you for your help. ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
** No longer affects: linux (Ubuntu) ** Package changed: fedora => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: High => Undecided ** Changed in: linux (Ubuntu) Status: Expired => New ** Changed in: linux (Ubuntu) Remote watch: Red Hat Bugzilla #755370 => None ** No longer affects: linux (Ubuntu) ** Project changed: linux => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Medium => Undecided ** Changed in: linux (Ubuntu) Status: In Progress => New ** Changed in: linux (Ubuntu) Remote watch: Linux Kernel Bug Tracker #27392 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] [NEW] 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
You have been subscribed to a public bug: Message in dmesg: [ 22.308381] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 22.308447] ath: Failed to stop TX DMA! --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1670 F pulseaudio /dev/snd/controlC1: caravena 1670 F pulseaudio /dev/snd/pcmC1D0p: caravena 1670 F...m pulseaudio CRDA: country CL: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 20) DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2013-07-31 (17 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-2-generic root=UUID=0c67119c-ddae-476a-b510-142ec598f691 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 RelatedPackageVersions: linux-restricted-modules-3.11.0-2-generic N/A linux-backports-modules-3.11.0-2-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.11.0-2-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected needs-full-computer-model needs-kernel-logs needs-upstream-testing patch saucy -- 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame https://bugs.launchpad.net/bugs/736171 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] [NEW] 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
You have been subscribed to a public bug: Message in dmesg: [ 22.308381] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 22.308447] ath: Failed to stop TX DMA! --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1670 F pulseaudio /dev/snd/controlC1: caravena 1670 F pulseaudio /dev/snd/pcmC1D0p: caravena 1670 F...m pulseaudio CRDA: country CL: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5735 - 5835 @ 40), (N/A, 20) DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2013-07-31 (17 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130724) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-2-generic root=UUID=0c67119c-ddae-476a-b510-142ec598f691 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 RelatedPackageVersions: linux-restricted-modules-3.11.0-2-generic N/A linux-backports-modules-3.11.0-2-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.11.0-2-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux Importance: Medium Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected needs-full-computer-model needs-kernel-logs needs-upstream-testing patch saucy -- 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame https://bugs.launchpad.net/bugs/736171 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
** Changed in: fedora Status: Unknown => Expired ** Changed in: fedora Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776448/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
apport information ** Tags added: apport-collected saucy ** Description changed: Message in dmesg: [ 22.308381] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 22.308447] ath: Failed to stop TX DMA! + --- + ApportVersion: 2.12-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: caravena 1670 F pulseaudio + /dev/snd/controlC1: caravena 1670 F pulseaudio + /dev/snd/pcmC1D0p: caravena 1670 F...m pulseaudio + CRDA: + country CL: + (2402 - 2482 @ 40), (N/A, 20) + (5170 - 5250 @ 40), (N/A, 20) + (5250 - 5330 @ 40), (N/A, 20), DFS + (5735 - 5835 @ 40), (N/A, 20) + DistroRelease: Ubuntu 13.10 + HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 + InstallationDate: Installed on 2013-07-31 (17 days ago) + InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130724) + MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C + MarkForUpload: True + Package: linux (not installed) + ProcFB: + 0 inteldrmfb + 1 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.11.0-2-generic root=UUID=0c67119c-ddae-476a-b510-142ec598f691 ro rootflags=subvol=@ quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 + RelatedPackageVersions: + linux-restricted-modules-3.11.0-2-generic N/A + linux-backports-modules-3.11.0-2-generic N/A + linux-firmware1.113 + Tags: saucy + Uname: Linux 3.11.0-2-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + dmi.bios.date: 04/15/2013 + dmi.bios.vendor: Phoenix Technologies Ltd. + dmi.bios.version: P14AAJ + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: SAMSUNG_NP1234567890 + dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.board.version: FAB1 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.chassis.version: 0.1 + dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: + dmi.product.name: 530U3C/530U4C + dmi.product.version: 0.1 + dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776447/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776452/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776454/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776451/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776449/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776450/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776456/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] RfKill.txt
apport information ** Attachment added: RfKill.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776458/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776453/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776457/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776461/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776459/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776455/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/736171/+attachment/3776462/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
** Tags added: needs-full-computer-name ** Tags removed: needs-full-computer-name ** Tags added: needs-full-computer-model -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
Chistian Aravena, 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. ** Tags added: needs-kernel-logs needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Attachment removed: lspci -vv https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2175982/+files/lspci-vv.txt ** Attachment removed: lspci -vvn https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2175983/+files/lspci-vvn.txt ** Attachment removed: lspci -vvnn https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2175984/+files/lspci-vvnn.txt ** Attachment removed: dmesg dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2651461/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
** Bug watch added: Red Hat Bugzilla #755370 https://bugzilla.redhat.com/show_bug.cgi?id=755370 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=755370 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171]
The attachment ath9k-Fix-race-in-starting-stopping-DMA of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report. [This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
** Changed in: linux Status: Incomplete = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame
** Summary changed: - ath: Failed to stop TX DMA in 100 msec after killing last frame + 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
No, no news at all. I tried the developers list of the driver, but no response either. It looks like it is a reintroduced bug. I do not have the time to test compiling the driver and applying patches, in fact the laptop is now a Microsoft system and I gave it to my mother in law ;-) Good luck, Floris 2012/2/11 Александр cli...@yandex.ru: Hello. Any news? I have the same bug with my pci wi-fi card(dlink dwa 547) on atheros ar9223 chipset... -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame Status in The Linux Kernel: Incomplete Status in “linux” package in Ubuntu: Confirmed Bug description: Message in dmesg: [ 22.308381] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 22.308447] ath: Failed to stop TX DMA! To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Hello. Any news? I have the same bug with my pci wi-fi card(dlink dwa 547) on atheros ar9223 chipset... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Spatialist, do you get TX DMA error in your syslog? If not please check if you experience similar symptomps as described in bug #814035. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Hi Lukasz, I get exactly the same errors in dmesg as oguzy (I copy his, as my laptop has no network): Dec 30 14:57:03 gulsah-SATELLITE-PRO-C660 kernel: [ 5743.881187] ath: Failed to stop TX DMA! Dec 30 14:57:03 gulsah-SATELLITE-PRO-C660 kernel: [ 5743.895845] ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x62c0 Dec 30 14:57:03 gulsah-SATELLITE-PRO-C660 kernel: [ 5743.895856] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up I did try the nohwcrypt=1, but that did not work at all (the error was actually getting worse, i.e. almost immediately after having connected to the router). What might be significant is that some of the errors mention 100ms and oguzy and mine mention 10ms. Also when my wireless does work, the speed (8mb/s down) and ping (2ms to router) is normal and the indicator lighton the laptop is on. This changes to off, the errors appear in the logs and the network manager tries to reconnect, claiming that the connection needs a password, which it does already have. With a powerdown and start, the connection comes back up, a simple restart is not enough. After a simple restart, the kernel does not recognize the network card anymore, lspci does not show it to be present on bus 3:0.0 where it previously was. With a simple restart to Windows it does not recognize the card sometimes also. I read somewhere that this type of card needs/gets a firmware reinitialisation every time a reboot occurs, so that might be important. The all or nothing behaviour of the bug I see seems to me more consistent with a race condition than an encryption problem. Maybe this race condition changes when encryption is on/off. I think the above patchby Christian Aravena, which (I think) adds a call to a semaphore in the ath9 driver, is not present in the 3.0 kernel driver and therefore the bug was reintroduced. Is there someone who can verify it not being present in this kernel? That would explain a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
And I also confirm the bug, exact eroro messages as oguzy On 11.10 with kernel 3.0.0-14-generic-pae System: Acer aspire 5750g and atheros AR9287 wireless network adapter It seems that the 3.0 kernel reintroduced the bug. The wireless works ok for awhile, sometimes minutes, sometimes an hour and then stops suddenly. It takes a powerdown/reboot to work again. Can somebody check if the patch was applied in the 3.0 kernel? It does not seem to ban encryption problem, but more a race condition where the driver messes up the card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
This problem still holds for Kubuntu 11.10, i am attaching the log files related with the issue. I can see that the ath9k driver is installed but the error messages continue at the boot up. Removing the driver, reinstalling it or reinstalling it with the nohwcrypt=1 didn't solve the problem. ** Attachment added: dmesg dmesg.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2651461/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
=0x0220 DMADBG_7=0x6040 Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5744.898483] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 wpa_supplicant[992]: Trying to authenticate with 00:24:6c:b2:73:d0 (SSID='eduroam' freq=2462 MHz) Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.042517] ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x6040 Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.042528] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.063429] ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x0220 DMADBG_7=0x8040 Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.063432] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 NetworkManager[2776]: info (wlan0): supplicant interface state: scanning - authenticating Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.083816] wlan0: authenticate with 00:24:6c:b2:73:d0 (try 1) Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 wpa_supplicant[992]: Trying to associate with 00:24:6c:b2:73:d0 (SSID='eduroam' freq=2462 MHz) Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.085788] wlan0: authenticated Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 NetworkManager[2776]: info (wlan0): supplicant interface state: authenticating - associating Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.114198] wlan0: associate with 00:24:6c:b2:73:d0 (try 1) Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.116984] wlan0: RX AssocResp from 00:24:6c:b2:73:d0 (capab=0x21 status=10 aid=0) Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.116994] wlan0: 00:24:6c:b2:73:d0 denied association (code=10) Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 kernel: [ 5745.132961] wlan0: deauthenticating from 00:24:6c:b2:73:d0 by local choice (reason=3) Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 wpa_supplicant[992]: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3 Dec 30 14:57:04 gulsah-SATELLITE-PRO-C660 NetworkManager[2776]: info (wlan0): supplicant interface state: associating - disconnected # lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 01:00.0 VGA compatible controller: nVidia Corporation Device 0a7a (rev a2) 01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05) 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) # uname -a Linux gulsah-SATELLITE-PRO-C660 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 i686 i386 GNU/Linux # lsmod | grep ath ath9k 112612 0 mac80211 393459 1 ath9k ath9k_common 13599 1 ath9k ath9k_hw 293933 2 ath9k,ath9k_common ath19387 2 ath9k,ath9k_hw cfg80211 172392 3 ath9k,mac80211,ath No ndiswrapper module or acer related module is installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
ath9k on Ubuntu 11.10 with 3.0.0-12-generic-pae is 20x more reliable for me over the last 7 days since upgrade. I have Acer Aspire Timeline X 3820T laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I've just tried Oneiric and this unfortunate bug is still here. But here's something that might be useful: I have Natty downgraded to 2.6.36 (just to evade this bug) on another partition and when I did a warm reboot from Oneiric the bug was still there. I was quite surprised because I never had those issues before on .36 kernel. What also struck me was a Bluetooth indicator that was also never there before. The Bluetooth applet seemed functional but after a shutdown WiFi was back to normal and Bluetooth reports no adapters. Considering this all happened after a warm reboot maybe it's possible that powering up Bluetooth somehow messes with 802.11? Or it could be a faulty firmware uploaded? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Is anyone working on this? I'll add a bug bounty £100 for a fix. Email me if interested with your proposal: jg at jguk.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Changed in: linux (Ubuntu) Assignee: Seth Forshee (sforshee) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Apparently Chromium OS has fixed these by patching comptat-wireless. These fixes apparently are in the 2.6.39 kernel tree? Reference: http://code.google.com/p/chromium-os/issues/detail?id=13275 ** Bug watch added: code.google.com/p/chromium-os/issues #13275 http://code.google.com/p/chromium-os/issues/detail?id=13275 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
This bug affects me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I've just upgraded to 11.10 alpha 2 and get the same problem with the same error message just much rarely than in 11.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Seth: I had no problems with my wireless on previous versions of Ubuntu. So if I remember correctly 2.6.36 was the last kernel working for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I've just tried kernel 3.0 from Oneiric and I don't see any errors in the syslog but the connection is still crippled :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Also getting this error w/ AR5008 chipset. Able to detect networks, but unable to connect. Up to date Natty installation, with proposed ppa enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
@Christoph: Thanks for testing. You don't have to uninstall the old kernel. I just checked, and in the 2.6.37 build you will never get the messages, period, even if the condition that generates the messages exists. So whether or not you get the messages in earlier builds is no indication of whether or not the issue is happening. There may be more than one problem here. Does 2.6.37 (or any other previous version) work for anyone? I'd especially like to hear back from the original reporter of the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
The error message does not appear with this kernel. But the connection still disconnects. Do I have to uninstall the old kernel first? I better try a maverick or lucid live cd for testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
There's a report on the upstream bug report that this worked fine in 2.6.37, in which case we can do a bisection to determine which commit introduced the problem. First, can someone install the kernel at the following link and verify that the problem is not present? Thanks! http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.37-natty/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
lspci -vv ** Attachment added: lspci -vv https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2175982/+files/lspci-vv.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
lspci -vvn ** Attachment added: lspci -vvn https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2175983/+files/lspci-vvn.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
lspci -vvnn ** Attachment added: lspci -vvnn https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/2175984/+files/lspci-vvnn.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Version: Ubuntu 2.6.38-8.42-generic 2.6.38.2 uname -a: Linux mpc 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I confirm the bug! System Information: Ubuntu 11.04 (up to date: kernel 2.6.38-8) additional information will follow... Wifi Connection is established, but so slow that the network in unusable! Changing back to Kernel 2.6.35-28-generic fixes the Problem. Please change importance to high -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I confirm that bug. My hardware is 05:01.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) I am running Kubuntu 11.04 64 Bit (linux 2.6.38-8-generic) This bug makes my wireless networking useless. Please fix as fast as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/736171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I have the same issue. dmesg reports the same problem, uname -r returns 2.6.38-8-generteic. I have ubuntu 11.04 64bit. I would also like to add that ping times from wireless card to router are ridiculously high, even at idle. Using the wireless card at all is practically impossible, but only on a g router. What I mean is that on my router at home, which is brand new 802.11n router (2x2), pings are flawless. The connection will only crash during heavy file transfers for half an hour or more. However, at work we have only 802.11 g, and in one place 802.11b routers. The wireless to these routers is almost unusable. pings are at 50ms at idle, and loading even a webpage will push pings up into the 500ms range. Any sort of file transfer returns the failed to stop tx dma message. This is a showstopping bug as I can not use my linux partition for work as I intended. It is worth noting that the same laptop has no problems when loaded into my windows partition, so this is defintitely a linux-driver issue. hardware is an atheros AR9287. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
This continues to affect me on 2.6.38-9-generic-pae from -proposed. Wireless becomes unusable after a few hours. uname -a: Linux ceres 2.6.38-9-generic-pae #43-Ubuntu SMP Thu Apr 28 17:12:11 UTC 2011 i686 i686 i386 GNU/Linux excerpted lspci: 04:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) From dmesg: [58864.888234] ath: Failed to stop TX DMA in 100 msec after killing last frame [58864.888260] ath: Failed to stop TX DMA! (repeated every few seconds) Will provide more data on request. Have also tried latest stable compat-wireless but not yet bleeding edge. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I have the same problem and the same messages in dmesg output when the wireless connection stalls on heavy file transfer. It resumes after some time automatically. I still am running kernel 2.6.38-8-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I get these errors as soon as I connect my TV screen over HDMI. My wireless connection is absolutely unusable until I disconnect it again. This is just one regression out of many that I experience since I upgraded to natty. I'd be very happy to see at least one of them fixed before I downgrade again or switch distributions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Well I've just noticed this bug isn't entirely fixed after all. I thought it was but these errors still appear they are just much less frequent and don't influence my connection stability as much as they used to with 2.6.38-8. I am even able to use wifi card in 'n mode' which wasn't possible before. Sadly, today I've noticed some heavy packet loss and after checking the logs it turned out it's the same error. It just appears less often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I got Ubuntu Natty 64bit installed on my laptop with kernel 2.6.38-9-general on (from proposed repository)... but the bug is still present; I keep receiving those errors. When my interface gets deactivated, I have to click on my connection name (so it disconnects and reconnects to it) to make it work again, even if my network-applet says my connection is correctly established. My router is set in g only mode, sometimes I change channel just to test various frequencies, but it doesn't help me. WPA2-PSK AES protection is on too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I am happy to report that this bug is FIXED by the latest kernel update (to version 2.6.38-9). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Related: Bug 761134 Fix is indeed in 2.6.38-9 and in natty-propsed since 2011-05-02. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
** Changed in: linux Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Yes, it should be listed in known issues. As a matter of fact it should even be a show stopper for this kernel in natty. I made my wifi usable by forcing g only mode. The connection still resets every few minutes but it's much better than in n mode. So I guess there might be much more people out there who are not really aware of this problem as long as they don't use their wifi cards in n mode... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
This bug should be listed in Known Issues section of release notes since wireless is almost unusable with ath9k module. https://wiki.ubuntu.com/NattyNarwhal/ReleaseNotes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
This definitely affects me on maverick and natty, having this hardware: bkero@Prosper:~$ uname -a Linux Prosper 2.6.38-02063802-generic #201103281246 SMP Mon Mar 28 12:50:24 UTC 2011 x86_64 GNU/Linux bkero@Prosper:~$ dmesg|tail -10 [31775.258391] ath: Failed to stop TX DMA in 100 msec after killing last frame [31775.258428] ath: Failed to stop TX DMA! [31777.268397] ath: Failed to stop TX DMA in 100 msec after killing last frame [31777.268434] ath: Failed to stop TX DMA! [31814.278388] ath: Failed to stop TX DMA in 100 msec after killing last frame [31814.278426] ath: Failed to stop TX DMA! [31819.288366] ath: Failed to stop TX DMA in 100 msec after killing last frame [31819.288404] ath: Failed to stop TX DMA! [31822.298415] ath: Failed to stop TX DMA in 100 msec after killing last frame [31822.298453] ath: Failed to stop TX DMA! bkero@Prosper:~$ lspci|grep Atheros r01:08.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) It seems that there was a fix in 2.6.39-rc1 as evidenced in commit d78f4b3e2c4dfb9487624f7157af04ab4260e189 Here's a link to the changelog: http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.39-rc1 Additionally, the fix was ported to compat-wireless, so hopefully we can get a fix backported to 2.6.38 for natty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
FWIW - removing and inserting the ath9k module brings it back for me (on natty). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
Just tried the 2.6.39-rc4 kernel from the kernel PPA, and I can confirm that I no longer receive these errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
This bug also affects me making network operations practically impossible. lscpi for net below: Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Foxconn International, Inc. Device e030 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 16 Region 0: Memory at e8e0 (64-bit, non-prefetchable) [size=64K] Capabilities: access denied Kernel driver in use: ath9k Kernel modules: ath9k and the syslog: kernel: [ 5012.743836] ath: Failed to stop TX DMA! kernel: [ 5012.755839] ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x4220 kernel: [ 5012.755845] ath: Could not stop RX, we could be confusing the DMA engine when we start RX up kernel: [ 5012.767458] ath: DMA failed to stop in 10 ms AR_CR=0x0024 AR_DIAG_SW=0x4220 kernel: [ 5019.780925] ath: Failed to stop TX DMA in 100 msec after killing last frame kernel: [ 5019.780955] ath: Failed to stop TX DMA! kernel: [ 5059.803900] ath: Failed to stop TX DMA in 100 msec after killing last frame -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
This is what I'm seeing: steve@triton:~$ dmesg | grep -i ath [3.307689] device-mapper: multipath: version 1.2.0 loaded [3.307692] device-mapper: multipath round-robin: version 1.0.0 loaded [ 10.487950] ath9k :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 10.487974] ath9k :02:00.0: setting latency timer to 64 [ 10.581769] ath: EEPROM regdomain: 0x65 [ 10.581771] ath: EEPROM indicates we should expect a direct regpair map [ 10.581773] ath: Country alpha2 being used: 00 [ 10.581774] ath: Regpair used: 0x65 [ 11.020072] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' [ 11.020587] Registered led device: ath9k-phy0::radio [ 11.020635] Registered led device: ath9k-phy0::assoc [ 11.020660] Registered led device: ath9k-phy0::tx [ 11.020683] Registered led device: ath9k-phy0::rx [ 11.020690] ieee80211 phy0: Atheros AR9287 Rev:2 mem=0xc900057c, irq=16 [ 110.607163] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 110.615611] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 110.615641] ath: Failed to stop TX DMA! [ 111.014587] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 111.014620] ath: Failed to stop TX DMA! steve@triton:~$ lspci | grep -i wireless 02:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
I also see same messages in dmesg. Currently using Ubuntu natty beta 2.6.38-8-generic. Wireless speed is very slow. About 30% of packets are lost using ping: --- 192.168.1.1 ping statistics --- 45 packets transmitted, 31 received, 31% packet loss, time 44086ms rtt min/avg/max/mdev = 1.163/2.363/16.377/2.694 ms lspci -vvv 09:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) Subsystem: D-Link System Inc Device 3a69 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 168, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at fbce (32-bit, non-prefetchable) [size=64K] Capabilities: [40] #80 [] Kernel driver in use: ath9k Kernel modules: ath9k -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
** Patch added: ath9k-Fix-race-in-starting-stopping-DMA https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171/+attachment/1916326/+files/0001-ath9k-Fix-race-in-starting-stopping-DMA-of-hw-data-q.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] [NEW] ath: Failed to stop TX DMA in 100 msec after killing last frame
Public bug reported: Message in dmesg: [ 22.308381] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 22.308447] ath: Failed to stop TX DMA! ** Affects: linux Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Linux Kernel Bug Tracker #27392 http://bugzilla.kernel.org/show_bug.cgi?id=27392 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=27392 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
** Changed in: linux Status: Unknown = Confirmed ** Changed in: linux Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 736171] Re: ath: Failed to stop TX DMA in 100 msec after killing last frame
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736171 Title: ath: Failed to stop TX DMA in 100 msec after killing last frame -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
