On Mon, Dec 14, 2015 at 10:48 AM, Johannes Berg
wrote:
> On Mon, 2015-12-14 at 04:00 +, 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
On Mon, 2015-12-14 at 04:00 +, 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
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
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
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:
>
>
On Fri, Dec 11, 2015 at 10:59 AM, Luis R. Rodriguez
wrote:
> I could bisect *if this issue
> is not known*, but it may take a while...
So this is interesting..
The opensuse 4.2.4 kernel worked, but I tried my own vanilla 4.2.4
kernel and that didn't work. This lead me
Using 4.4-rc4 and today's wireless-testing (master-2015-12-10), and
the latest firmware on linux-firmware, my wireless driver runs into a
non-functional loop rambling about "L1 Enabled - LTR Enabled loop".
Reverting back to an older kernel works. I could bisect *if this issue
is not known*, but it