I'm not really sure how a wireless driver could cause this. Even stranger is I build a 3.13.0-35 kernel with this commit reverted, and I'm unable to reproduce the bug. If anyone else wants to test that kernel, it can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1470250/trusty-revert/3.13.0-35/
I'm now testing Wily and Xenial kernels with the commit reverted as well to ensure a revert fixes those kernels as well.
If anyone else wants to test those kernels, then can be downloaded from:
If that commit is indeed the cause of the bug, we should do some more investigation to understand what is happening. I'll post my testing results of the other kernels within two days.
Yes, the bisect ended in a really strange results. I reported this commit as the cause:
commit c01fac1c77a0022 7f706a165431702 3e3f4ac7f0
Author: Felix Fietkau <email address hidden>
Date: Wed Jul 23 15:40:54 2014 +0200
ath9k: fix aggregation session lockup
I'm not really sure how a wireless driver could cause this. Even stranger is I build a 3.13.0-35 kernel with this commit reverted, and I'm unable to reproduce the bug. If anyone else wants to test that kernel, it can be downloaded from: kernel. ubuntu. com/~jsalisbury /lp1470250/ trusty- revert/ 3.13.0- 35/
http://
I'm now testing Wily and Xenial kernels with the commit reverted as well to ensure a revert fixes those kernels as well.
If anyone else wants to test those kernels, then can be downloaded from:
Trusty: http:// kernel. ubuntu. com/~jsalisbury /lp1470250/ trusty- revert/ kernel. ubuntu. com/~jsalisbury /lp1470250/ wily-revert/ kernel. ubuntu. com/~jsalisbury /lp1470250/ xenial- revert/
WIly: http://
Xenial: http://
If that commit is indeed the cause of the bug, we should do some more investigation to understand what is happening. I'll post my testing results of the other kernels within two days.