Hi,
[sorry, forgot to Cc current first]
* Adrian Chadd [160715 22:40]:
> On 15 July 2016 at 13:28, Wolfgang Zenker wrote:
>> * Adrian Chadd [160715 00:00]:
>>> On 14 July 2016 at 14:37, Wolfgang Zenker wrote:
* Adrian Chadd [160710 21:47]:
> Since you've reverted the ath driver dire
Hi,
Just try disabling the others and see what happens.
Thanks!
-a
On 15 July 2016 at 13:28, Wolfgang Zenker wrote:
> * Adrian Chadd [160715 00:00]:
>> On 14 July 2016 at 14:37, Wolfgang Zenker wrote:
>>> * Adrian Chadd [160710 21:47]:
Since you've reverted the ath driver directories
* Adrian Chadd [160715 00:00]:
> On 14 July 2016 at 14:37, Wolfgang Zenker wrote:
>> * Adrian Chadd [160710 21:47]:
>>> Since you've reverted the ath driver directories without success, I'm
>>> mostly out of simple ideas. I think you need to bisect the whole
>>> kernel version until you find the
On 14 July 2016 at 14:37, Wolfgang Zenker wrote:
> Hi,
>
> * Adrian Chadd [160710 21:47]:
>> Since you've reverted the ath driver directories without success, I'm
>> mostly out of simple ideas. I think you need to bisect the whole
>> kernel version until you find the commit that broke things.
>
>
Hi,
* Adrian Chadd [160710 21:47]:
> Since you've reverted the ath driver directories without success, I'm
> mostly out of simple ideas. I think you need to bisect the whole
> kernel version until you find the commit that broke things.
done. The commit is 11-STABLE r302410. AFAICS the only chang
Hi,
That message just means a receive interrupt was handled whilst the NIC
was in reset, which is mostly fine.
Since you've reverted the ath driver directories without success, I'm
mostly out of simple ideas. I think you need to bisect the whole
kernel version until you find the commit that broke
* Wolfgang Zenker [160710 19:47]:
> * Adrian Chadd [160709 21:33]:
>> There weren't any changes in net80211 between those times, and ath(4)
>> only has some changes for locationing; nothing that should cause that
>> particular issue.
>> I'll go update to the latest -head on something with that N
Hi,
* Adrian Chadd [160709 21:33]:
> There weren't any changes in net80211 between those times, and ath(4)
> only has some changes for locationing; nothing that should cause that
> particular issue.
> I'll go update to the latest -head on something with that NIC and test
> it out some more.
> T
hi,
There weren't any changes in net80211 between those times, and ath(4)
only has some changes for locationing; nothing that should cause that
particular issue.
I'll go update to the latest -head on something with that NIC and test
it out some more.
Try reverting sys/dev/ath/ and sys/contrib/de
