A patch has been posted to linux-wireless which accomplishes the
workaround of disabling wireless power saving (ie. iw dev wlan0 set
power_save off) by disabling power saving in the ath9k driver itself.
http://marc.info/?l=linux-wirelessm=137005085710866w=2
I applied it to Debian's 3.2.41 kernel
On Fri, 2013-03-29 at 22:07 +, Ben Hutchings wrote:
Control: tag -1 unreproducible
Until you find a *reliable* way to reproduce the bug, bisection cannot
find the fix. I'm sorry I can't be more helpful.
I haven't found a way to reliably reproduce, but I have found a way to
ensure that
Processing control commands:
tag -1 unreproducible
Bug #695968 [src:linux] linux-image-3.2.0-4-amd64: ath.ko starts printing
thousands of error messages several minutes after boot
Bug #695969 [src:linux] linux-image-3.2.0-4-amd64: ath.ko prints thousands of
error messages and wireless
Control: tag -1 unreproducible
On Thu, 2013-03-28 at 19:42 -0400, Joel Diaz wrote:
After looking at this some more, my bisect has left me between these two
commits:
The last good commit:
[db9d8c60266a5010e905829e10cd722519e14777] Merge
After looking at this some more, my bisect has left me between these two
commits:
The last good commit:
[db9d8c60266a5010e905829e10cd722519e14777] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
The last bad commit:
[45e7715922217493f01c8238d8c9eff5c3fea5a2] Merge tag
On Sun, 2013-01-20 at 15:42 +, Ben Hutchings wrote:
I've looked for changes to the drive that seem related to power and
reset sequencing. Could you test whether applying the attached patches
to Debian's 3.2 kernel fixes the problem? See the instructions at
Processing control commands:
tag -1 moreinfo
Bug #695968 [src:linux] linux-image-3.2.0-4-amd64: ath.ko starts printing
thousands of error messages several minutes after boot
Bug #695969 [src:linux] linux-image-3.2.0-4-amd64: ath.ko prints thousands of
error messages and wireless connection
Control: tag -1 moreinfo
On Wed, 2013-01-02 at 15:04 -0500, Joel Diaz wrote:
After several long and painful 'git bisect drivers/net/wireless/ath*'
sessions (too many false positives), I think I've come to the conclusion
that the issues in this bug disappear starting with
After several long and painful 'git bisect drivers/net/wireless/ath*'
sessions (too many false positives), I think I've come to the conclusion
that the issues in this bug disappear starting with
Package: src:linux
Version: 3.2.35-1
Severity: important
Dear Maintainer,
* What led up to the situation?
Just using the computer normally. For unrelated reasons, the actual network
traffic was being routed through eth0 and not wlan0 (even though wlan0 had a
valid IP address).
Ran my machine
10 matches
Mail list logo