[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2017-10-29 Thread Christopher M. Penalver
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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2017-10-29 Thread Christopher M. Penalver
** 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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2017-10-27 Thread Bug Watch Updater
** 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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2013-08-18 Thread Cristian Aravena
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 +

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2013-08-18 Thread Christopher M. Penalver
** 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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2013-08-17 Thread Christopher M. Penalver
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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2012-07-16 Thread kotofos
** 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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2012-06-14 Thread Bug Watch Updater
** 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

[Bug 736171] Re: 168c:002a ath: Failed to stop TX DMA in 100 msec after killing last frame

2012-05-12 Thread Christopher M. Penalver
** 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.