Re: hardware restart on Intel 7260

2016-04-12 Thread Johann Haarhoff 

> Meh... So what happens here is that the firmware is stuck while
> transmitting. The driver detects this and as a workaround, resets the
> firmware. The detection takes 10 seconds.
> The only way to understand what is going on here is to take the
> firmware from [1] and to run the steps to collect firmware debug data
> from [2]. I recommend you open a bug on bugzilla.
> Out of curiosity, did you try to work in DC mode (on battery, not
> connected to the power)? A user reported that it helped [3].

I followed the steps you suggested, and am now tracking the bug here:

https://bugzilla.kernel.org/show_bug.cgi?id=116191



--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: hardware restart on Intel 7260

2016-04-11 Thread Emmanuel Grumbach 
Hi,

On Mon, Apr 11, 2016 at 5:09 PM, Johann Haarhoff  wrote:
>
> Hi
>
> (Please CC as I am not subscribed to the list)
>
> I'm seeing the following trace on a Lenovo Yoga 2 Pro with an Intel 7260 (rev 
> 6b).
>
> Kernel is 4.5 on using the latest -16 firmware from wireless.wiki.kernel.org. 
> I tried the -17 firmware from git.kernel.org with a
> very similar result.
>
> module was loaded with:
>
> options iwlwifi power_save=0 bt_coex_active=0 swcrypto=1

Can you try:
options iwlmvm power_scheme=1

>
> The trace is accompanied by a couple seconds where no data transfer can 
> happen (youtube stutters etc.), but other than that it seems
> to resume fine. This happens every 2-15 minutes if I am moving data.
>
> Disabling 11n fixes the problem, but that is not really an viable option.

That can help to know where the problem hides.

>
> Please let me know if there is anything I can add to help with the debugging.
>
> > Apr 11 15:52:30  kernel: [13827.165868] iwlwifi :01:00.0: Queue 2 stuck 
> > for 1 ms.
> > Apr 11 15:52:30  kernel: [13827.165878] iwlwifi :01:00.0: Current SW 
> > read_ptr 135 write_ptr 171

Meh... So what happens here is that the firmware is stuck while
transmitting. The driver detects this and as a workaround, resets the
firmware. The detection takes 10 seconds.
The only way to understand what is going on here is to take the
firmware from [1] and to run the steps to collect firmware debug data
from [2]. I recommend you open a bug on bugzilla.
Out of curiosity, did you try to work in DC mode (on battery, not
connected to the power)? A user reported that it helped [3].

[1] https://bugzilla.kernel.org/attachment.cgi?id=208381
[2] 
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging
[3] https://bugzilla.kernel.org/show_bug.cgi?id=112931


>
>
> Thanks,
>
> Johann
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

hardware restart on Intel 7260

2016-04-11 Thread Johann Haarhoff 
Hi

(Please CC as I am not subscribed to the list)

I'm seeing the following trace on a Lenovo Yoga 2 Pro with an Intel 7260 (rev 
6b).

Kernel is 4.5 on using the latest -16 firmware from wireless.wiki.kernel.org. I 
tried the -17 firmware from git.kernel.org with a
very similar result.

module was loaded with:

options iwlwifi power_save=0 bt_coex_active=0 swcrypto=1

The trace is accompanied by a couple seconds where no data transfer can happen 
(youtube stutters etc.), but other than that it seems
to resume fine. This happens every 2-15 minutes if I am moving data.

Disabling 11n fixes the problem, but that is not really an viable option.

Please let me know if there is anything I can add to help with the debugging.

> Apr 11 15:52:30  kernel: [13827.165868] iwlwifi :01:00.0: Queue 2 stuck 
> for 1 ms.
> Apr 11 15:52:30  kernel: [13827.165878] iwlwifi :01:00.0: Current SW 
> read_ptr 135 write_ptr 171
> Apr 11 15:52:30  kernel: [13827.165917] iwl data: : 00 00 00 00 00 00 
> 00 00 00 00 00 00 00 00 00 00  
> Apr 11 15:52:30  kernel: [13827.165928] iwlwifi :01:00.0: FH TRBs(0) = 
> 0x
> Apr 11 15:52:30  kernel: [13827.165940] iwlwifi :01:00.0: FH TRBs(1) = 
> 0xc0110003
> Apr 11 15:52:30  kernel: [13827.165951] iwlwifi :01:00.0: FH TRBs(2) = 
> 0x
> Apr 11 15:52:30  kernel: [13827.165962] iwlwifi :01:00.0: FH TRBs(3) = 
> 0x803f
> Apr 11 15:52:30  kernel: [13827.165973] iwlwifi :01:00.0: FH TRBs(4) = 
> 0x
> Apr 11 15:52:30  kernel: [13827.165985] iwlwifi :01:00.0: FH TRBs(5) = 
> 0x
> Apr 11 15:52:30  kernel: [13827.165996] iwlwifi :01:00.0: FH TRBs(6) = 
> 0x
> Apr 11 15:52:30  kernel: [13827.166007] iwlwifi :01:00.0: FH TRBs(7) = 
> 0x007090ed
> Apr 11 15:52:30  kernel: [13827.166056] iwlwifi :01:00.0: Q 0 is active 
> and mapped to fifo 3 ra_tid 0x [16,16]
> Apr 11 15:52:30  kernel: [13827.166104] iwlwifi :01:00.0: Q 1 is active 
> and mapped to fifo 2 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166151] iwlwifi :01:00.0: Q 2 is active 
> and mapped to fifo 1 ra_tid 0x [135,171]
> Apr 11 15:52:30  kernel: [13827.166199] iwlwifi :01:00.0: Q 3 is active 
> and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166247] iwlwifi :01:00.0: Q 4 is inactive 
> and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166295] iwlwifi :01:00.0: Q 5 is inactive 
> and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166343] iwlwifi :01:00.0: Q 6 is inactive 
> and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166391] iwlwifi :01:00.0: Q 7 is inactive 
> and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166439] iwlwifi :01:00.0: Q 8 is inactive 
> and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166487] iwlwifi :01:00.0: Q 9 is active 
> and mapped to fifo 7 ra_tid 0x [238,238]
> Apr 11 15:52:30  kernel: [13827.166535] iwlwifi :01:00.0: Q 10 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166583] iwlwifi :01:00.0: Q 11 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166631] iwlwifi :01:00.0: Q 12 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166679] iwlwifi :01:00.0: Q 13 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166727] iwlwifi :01:00.0: Q 14 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.166930] iwlwifi :01:00.0: Q 15 is active 
> and mapped to fifo 5 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167155] iwlwifi :01:00.0: Q 16 is active 
> and mapped to fifo 1 ra_tid 0x000f [244,176]
> Apr 11 15:52:30  kernel: [13827.167204] iwlwifi :01:00.0: Q 17 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167254] iwlwifi :01:00.0: Q 18 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167328] iwlwifi :01:00.0: Q 19 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167381] iwlwifi :01:00.0: Q 20 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167444] iwlwifi :01:00.0: Q 21 is 
> inactive and mapped to fifo 0 ra_tid 0xfff0 [0,0]
> Apr 11 15:52:30  kernel: [13827.167551] iwlwifi :01:00.0: Q 22 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167612] iwlwifi :01:00.0: Q 23 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167720] iwlwifi :01:00.0: Q 24 is 
> inactive and mapped to fifo 0 ra_tid 0x [0,0]
> Apr 11 15:52:30  kernel: [13827.167781] iwlwifi :01:00.0: Q 25 is 
> inactive and