On 3 June 2015 at 02:05, Christopher M. Penalver <
<email address hidden>> wrote:
> Jonas G. Drange, could you please test the latest upstream kernel
>
Sure. But there are a couple of things that are making me suspect the
ath9k driver:
1. Reloading the driver (rmmod ath9k && modprobe ath9k) makes this less of
a problem
2. Turning (soft) off bluetooth seems to improve the situation as well. And
I see a lot of bluetooth+ath9k related issues.
So before I do a bisect, do we know that the ath9k driver gets updated
after 3.19.0-18-generic?
On 3 June 2015 at 02:05, Christopher M. Penalver <
<email address hidden>> wrote:
> Jonas G. Drange, could you please test the latest upstream kernel
>
Sure. But there are a couple of things that are making me suspect the
ath9k driver:
1. Reloading the driver (rmmod ath9k && modprobe ath9k) makes this less of
a problem
2. Turning (soft) off bluetooth seems to improve the situation as well. And
I see a lot of bluetooth+ath9k related issues.
So before I do a bisect, do we know that the ath9k driver gets updated
after 3.19.0-18-generic?