On 12/14/2015 01:04 AM, Arend van Spriel wrote:
> On 12/12/2015 12:32 AM, Johannes Berg wrote:
>> On Fri, 2015-12-11 at 15:17 -0800, Luis R. Rodriguez wrote:
>>> I just tried a base config from opensuse, then localmodconfig, then
>>> 'make xenconfig' (which I need) and that worked. I can't debug
>>> further but I think this config might help debug this further:
>>>
>>> http://drvbp1.linux-foundation.org/~mcgrof/tmp/config-iwl-fail.txt
>>>
>>> So -- my new config works, but I have no idea what fixed it, a config
>>> option obviously. Not sure what though.
>>>
>> Can you post the good one too?
> I had the same issue occasionally when coming out of suspend. Running
> 4.1 vanilla kernel with 3160 device. The issue also occurred more often
> with particular ucode version. Running iwlwifi-3160-10.ucode now and
> have not seen the issue pop up since.
This is really weird. I don't see how that could be firmware related.
BTW, -10.ucode is fairly old :) we have -16.ucode out there.
>
> Gr. AvS
>
>
On Mon, Dec 14, 2015 at 10:48 AM, Johannes Berg
<[email protected]> wrote:
> On Mon, 2015-12-14 at 04:00 +0000, Grumbach, Emmanuel wrote:
>>
>> This is really weird. I don't see how that could be firmware related.
>> BTW, -10.ucode is fairly old :) we have -16.ucode out there.
>
> I guess the question is how we get into this situation to start with?
>
> About the only thing I can imagine is that we fail somehow during
> initialization (without printing any other message) and higher layers
> like wpa_supplicant/network-manager/... simply try to bring up the
> device over and over again?
>
I can reproduce this now when I unload / load iwlwifi until I kill the
supplicant.
Seems like the wpa_s is indeed toggling the device.
I don't have time to play with that right now.
On Mon, 2015-12-14 at 04:00 +0000, Grumbach, Emmanuel wrote:
>
> This is really weird. I don't see how that could be firmware related.
> BTW, -10.ucode is fairly old :) we have -16.ucode out there.
I guess the question is how we get into this situation to start with?
About the only thing I can imagine is that we fail somehow during
initialization (without printing any other message) and higher layers
like wpa_supplicant/network-manager/... simply try to bring up the
device over and over again?
johannes