QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hello there,

I gave 4.2 rc3 a shot and I discovered the wireless was not working
anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in
ath10k_core (I assume you need fw api 5 to remove this, is that
correct?, I still have fw 4 only).

Loading with irq_mode=0

[   21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
[   21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[   21.277023] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[   21.278105] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
error -2
[   21.278109] ath10k_pci 0000:03:00.0: failed to load spec board
file, falling back to generic: -2
[   21.279048] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[   21.279051] ath10k_pci 0000:03:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[   22.445285] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   22.445319] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   23.445028] ath10k_pci 0000:03:00.0: failed to receive control
response completion, polling..
[   23.445183] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   23.445247] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   24.445040] ath10k_pci 0000:03:00.0: Service connect timeout
[   24.445043] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
[   24.508619] ath10k_pci 0000:03:00.0: could not init core (-110)
[   24.508640] ath10k_pci 0000:03:00.0: could not probe fw (-110)
[   74.965904] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt

With irq_mode=1 (and debug_mask=0x00000432 for ath10k_core... didn't
do.. anything?)

[  612.043708] ath10k_pci 0000:03:00.0: limiting irq mode to: 1
[  612.043711] ath10k_pci 0000:03:00.0: pci irq legacy interrupts 0
irq_mode 1 reset_mode 0
[  612.249048] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[  612.249148] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
error -2
[  612.249150] ath10k_pci 0000:03:00.0: failed to load spec board
file, falling back to generic: -2
[  612.249251] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[  612.249252] ath10k_pci 0000:03:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[  613.435568] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
3.0 wmi 4 cal otp max_sta 32
[  613.435571] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 0
dfs 0 testmode 0
[  613.509157] ath: EEPROM regdomain: 0x6c
[  613.509160] ath: EEPROM indicates we should expect a direct regpair map
[  613.509162] ath: Country alpha2 being used: 00
[  613.509163] ath: Regpair used: 0x6c
[  613.513311] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0


This is a Dell Alienware 15 (early 2015) laptop.

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hello there,

I gave 4.2 rc3 a shot and I discovered the wireless was not working
anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in
ath10k_core (I assume you need fw api 5 to remove this, is that
correct?, I still have fw 4 only).

Loading with irq_mode=0

[   21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
[   21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[   21.277023] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[   21.278105] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
error -2
[   21.278109] ath10k_pci 0000:03:00.0: failed to load spec board
file, falling back to generic: -2
[   21.279048] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[   21.279051] ath10k_pci 0000:03:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[   22.445285] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   22.445319] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   23.445028] ath10k_pci 0000:03:00.0: failed to receive control
response completion, polling..
[   23.445183] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   23.445247] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   24.445040] ath10k_pci 0000:03:00.0: Service connect timeout
[   24.445043] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
[   24.508619] ath10k_pci 0000:03:00.0: could not init core (-110)
[   24.508640] ath10k_pci 0000:03:00.0: could not probe fw (-110)
[   74.965904] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt

With irq_mode=1 (and debug_mask=0x00000432 for ath10k_core... didn't
do.. anything?)

[  612.043708] ath10k_pci 0000:03:00.0: limiting irq mode to: 1
[  612.043711] ath10k_pci 0000:03:00.0: pci irq legacy interrupts 0
irq_mode 1 reset_mode 0
[  612.249048] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[  612.249148] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
error -2
[  612.249150] ath10k_pci 0000:03:00.0: failed to load spec board
file, falling back to generic: -2
[  612.249251] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[  612.249252] ath10k_pci 0000:03:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[  613.435568] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
3.0 wmi 4 cal otp max_sta 32
[  613.435571] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 0
dfs 0 testmode 0
[  613.509157] ath: EEPROM regdomain: 0x6c
[  613.509160] ath: EEPROM indicates we should expect a direct regpair map
[  613.509162] ath: Country alpha2 being used: 00
[  613.509163] ath: Regpair used: 0x6c
[  613.513311] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0


This is a Dell Alienware 15 (early 2015) laptop.

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Michal Kazior]

On 27 July 2015 at 22:08, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> Hello there,
>
> I gave 4.2 rc3 a shot and I discovered the wireless was not working
> anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in
> ath10k_core (I assume you need fw api 5 to remove this, is that
> correct?, I still have fw 4 only).
>
> Loading with irq_mode=0
>
> [   21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
> [   21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0

There was already a similar report[1]. Just for the record: what
number of interrupts did you have before 4.2-rc3? I assume it was "pci
irq msi interrupts 1 irq_mode 0 reset_mode 0".

My suspicion is that either the firmware is buggy and doesn't play
well with multiple MSI interrupts or the MSI interrupt behaviour
changed significantly (compared to qca988x) and this remained hidden
because not an awful lot of machines seemed to have provided more than
1 msi interrupt for ath10k.

[1]: http://lists.infradead.org/pipermail/ath10k/2015-July/005695.html


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Michal Kazior]

On 27 July 2015 at 22:08, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> Hello there,
>
> I gave 4.2 rc3 a shot and I discovered the wireless was not working
> anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in
> ath10k_core (I assume you need fw api 5 to remove this, is that
> correct?, I still have fw 4 only).
>
> Loading with irq_mode=0
>
> [   21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
> [   21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0

There was already a similar report[1]. Just for the record: what
number of interrupts did you have before 4.2-rc3? I assume it was "pci
irq msi interrupts 1 irq_mode 0 reset_mode 0".

My suspicion is that either the firmware is buggy and doesn't play
well with multiple MSI interrupts or the MSI interrupt behaviour
changed significantly (compared to qca988x) and this remained hidden
because not an awful lot of machines seemed to have provided more than
1 msi interrupt for ath10k.

[1]: http://lists.infradead.org/pipermail/ath10k/2015-July/005695.html


Michał

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi Michal,

this is the dmesg output from a boot with kernel 4.1.2 with patch to
make the firmware load [1]

Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: enabling device (0000 -> 0002)
Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
failed with error -2
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0 wlp3s0: renamed from wlan0

I saw the report you mentioned (I'm subscribed to ath10k and try to
keep it up with it). Not being expert at all I was not sure it was the
same or not. Also there seems to be a difference that with irq_mode=1
for me it just works like before.

[1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060

On 28 July 2015 at 06:31, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 27 July 2015 at 22:08, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>> Hello there,
>>
>> I gave 4.2 rc3 a shot and I discovered the wireless was not working
>> anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in
>> ath10k_core (I assume you need fw api 5 to remove this, is that
>> correct?, I still have fw 4 only).
>>
>> Loading with irq_mode=0
>>
>> [   21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>> [   21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>
> There was already a similar report[1]. Just for the record: what
> number of interrupts did you have before 4.2-rc3? I assume it was "pci
> irq msi interrupts 1 irq_mode 0 reset_mode 0".
>
> My suspicion is that either the firmware is buggy and doesn't play
> well with multiple MSI interrupts or the MSI interrupt behaviour
> changed significantly (compared to qca988x) and this remained hidden
> because not an awful lot of machines seemed to have provided more than
> 1 msi interrupt for ath10k.
>
> [1]: http://lists.infradead.org/pipermail/ath10k/2015-July/005695.html
>
>
> Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi Michal,

this is the dmesg output from a boot with kernel 4.1.2 with patch to
make the firmware load [1]

Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: enabling device (0000 -> 0002)
Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
failed with error -2
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
0000:03:00.0 wlp3s0: renamed from wlan0

I saw the report you mentioned (I'm subscribed to ath10k and try to
keep it up with it). Not being expert at all I was not sure it was the
same or not. Also there seems to be a difference that with irq_mode=1
for me it just works like before.

[1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060

On 28 July 2015 at 06:31, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 27 July 2015 at 22:08, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>> Hello there,
>>
>> I gave 4.2 rc3 a shot and I discovered the wireless was not working
>> anymore with it. I tried adding irq_mode=1 alongside skip_otp=y in
>> ath10k_core (I assume you need fw api 5 to remove this, is that
>> correct?, I still have fw 4 only).
>>
>> Loading with irq_mode=0
>>
>> [   21.130224] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>> [   21.130734] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>
> There was already a similar report[1]. Just for the record: what
> number of interrupts did you have before 4.2-rc3? I assume it was "pci
> irq msi interrupts 1 irq_mode 0 reset_mode 0".
>
> My suspicion is that either the firmware is buggy and doesn't play
> well with multiple MSI interrupts or the MSI interrupt behaviour
> changed significantly (compared to qca988x) and this remained hidden
> because not an awful lot of machines seemed to have provided more than
> 1 msi interrupt for ath10k.
>
> [1]: http://lists.infradead.org/pipermail/ath10k/2015-July/005695.html
>
>
> Michał

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Michal Kazior]

On 28 July 2015 at 13:00, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> Hi Michal,
>
> this is the dmesg output from a boot with kernel 4.1.2 with patch to
> make the firmware load [1]
>
> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: enabling device (0000 -> 0002)
> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
> failed with error -2
> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
> killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0 wlp3s0: renamed from wlan0
>
> I saw the report you mentioned (I'm subscribed to ath10k and try to
> keep it up with it). Not being expert at all I was not sure it was the
> same or not. Also there seems to be a difference that with irq_mode=1
> for me it just works like before.

I'm quite puzzled with the above printout. So either there's some
weird regression either in driver or the pci subsystem. It's good you
posted ;-)

Just to be clear: were you using 4.2-rc3 as in from Linus' tree or Kalle's tree?

Asking for a `git bisect` is probably a bit excessive - but it would
help a lot. I guess you'd have to manually cherry-pick qca6174 hw2 fix
[1] while bisecting.

If bisect is too much I guess you could try reverting (in order):
 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=0bcbbe679b66fee1b56def5cb30bfb4f616b1127
 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=76d870ed09ab34154454b1adb823ae75f173c2d2
 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=77258d409ce45890104e3da11d0261402c49aee1

I'm shooting blind here though.

> [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Michal Kazior]

On 28 July 2015 at 13:00, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> Hi Michal,
>
> this is the dmesg output from a boot with kernel 4.1.2 with patch to
> make the firmware load [1]
>
> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: enabling device (0000 -> 0002)
> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
> failed with error -2
> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
> killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
> 0000:03:00.0 wlp3s0: renamed from wlan0
>
> I saw the report you mentioned (I'm subscribed to ath10k and try to
> keep it up with it). Not being expert at all I was not sure it was the
> same or not. Also there seems to be a difference that with irq_mode=1
> for me it just works like before.

I'm quite puzzled with the above printout. So either there's some
weird regression either in driver or the pci subsystem. It's good you
posted ;-)

Just to be clear: were you using 4.2-rc3 as in from Linus' tree or Kalle's tree?

Asking for a `git bisect` is probably a bit excessive - but it would
help a lot. I guess you'd have to manually cherry-pick qca6174 hw2 fix
[1] while bisecting.

If bisect is too much I guess you could try reverting (in order):
 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=0bcbbe679b66fee1b56def5cb30bfb4f616b1127
 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=76d870ed09ab34154454b1adb823ae75f173c2d2
 https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=77258d409ce45890104e3da11d0261402c49aee1

I'm shooting blind here though.

> [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060


Michał

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

I was testing the kernel from Fedora rawhide to test some issue
related to the sound card. So this is 4.2 rc3 as released by Linus
plus some Fedora patch. Nothing related to ath10k as far as I can see.

Bisecting would require a lot of time. I'm doing the full RPM package,
including modules signature and so on and I'm doing this in my free
time.This wont work for bisecting. I have to setup something else. Is
it ok if I restrict the bisect on the ath10k tree? That has enough
commit already to begin with, plus I'm going to be on the road in less
than two weeks.

On 28 July 2015 at 13:26, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 28 July 2015 at 13:00, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>> Hi Michal,
>>
>> this is the dmesg output from a boot with kernel 4.1.2 with patch to
>> make the firmware load [1]
>>
>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: enabling device (0000 -> 0002)
>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
>> failed with error -2
>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
>> killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0 wlp3s0: renamed from wlan0
>>
>> I saw the report you mentioned (I'm subscribed to ath10k and try to
>> keep it up with it). Not being expert at all I was not sure it was the
>> same or not. Also there seems to be a difference that with irq_mode=1
>> for me it just works like before.
>
> I'm quite puzzled with the above printout. So either there's some
> weird regression either in driver or the pci subsystem. It's good you
> posted ;-)
>
> Just to be clear: were you using 4.2-rc3 as in from Linus' tree or Kalle's tree?
>
> Asking for a `git bisect` is probably a bit excessive - but it would
> help a lot. I guess you'd have to manually cherry-pick qca6174 hw2 fix
> [1] while bisecting.
>
> If bisect is too much I guess you could try reverting (in order):
>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=0bcbbe679b66fee1b56def5cb30bfb4f616b1127
>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=76d870ed09ab34154454b1adb823ae75f173c2d2
>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=77258d409ce45890104e3da11d0261402c49aee1
>
> I'm shooting blind here though.
>
>> [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060
>
>
> Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

I was testing the kernel from Fedora rawhide to test some issue
related to the sound card. So this is 4.2 rc3 as released by Linus
plus some Fedora patch. Nothing related to ath10k as far as I can see.

Bisecting would require a lot of time. I'm doing the full RPM package,
including modules signature and so on and I'm doing this in my free
time.This wont work for bisecting. I have to setup something else. Is
it ok if I restrict the bisect on the ath10k tree? That has enough
commit already to begin with, plus I'm going to be on the road in less
than two weeks.

On 28 July 2015 at 13:26, Michal Kazior <michal.kazior@tieto.com> wrote:
> On 28 July 2015 at 13:00, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>> Hi Michal,
>>
>> this is the dmesg output from a boot with kernel 4.1.2 with patch to
>> make the firmware load [1]
>>
>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: enabling device (0000 -> 0002)
>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
>> failed with error -2
>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
>> killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>> 0000:03:00.0 wlp3s0: renamed from wlan0
>>
>> I saw the report you mentioned (I'm subscribed to ath10k and try to
>> keep it up with it). Not being expert at all I was not sure it was the
>> same or not. Also there seems to be a difference that with irq_mode=1
>> for me it just works like before.
>
> I'm quite puzzled with the above printout. So either there's some
> weird regression either in driver or the pci subsystem. It's good you
> posted ;-)
>
> Just to be clear: were you using 4.2-rc3 as in from Linus' tree or Kalle's tree?
>
> Asking for a `git bisect` is probably a bit excessive - but it would
> help a lot. I guess you'd have to manually cherry-pick qca6174 hw2 fix
> [1] while bisecting.
>
> If bisect is too much I guess you could try reverting (in order):
>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=0bcbbe679b66fee1b56def5cb30bfb4f616b1127
>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=76d870ed09ab34154454b1adb823ae75f173c2d2
>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=77258d409ce45890104e3da11d0261402c49aee1
>
> I'm shooting blind here though.
>
>> [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060
>
>
> Michał

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Alexandre Maloteaux]

Hi Enrico

I had the same issue a few days ago on an Eurocom P5 Pro.
I manage to get it working with the help of michal  by compiling the
kvalo kernel master branch : https://github.com/kvalo/ath

And then using this ath10k.conf file in /etc/modprobe.d

options ath10k_core skip_otp=y
options ath10k_pci  irq_mode=1

It works on my archlinux system but firmware loading take 1 minute
between each retry, so it takes 2 minutes to get the card up and
running. I have not yet found a solution to this issue.

Best Regards

On 07/28/2015 03:57 PM, Enrico Tagliavini wrote:
> I was testing the kernel from Fedora rawhide to test some issue
> related to the sound card. So this is 4.2 rc3 as released by Linus
> plus some Fedora patch. Nothing related to ath10k as far as I can see.
>
> Bisecting would require a lot of time. I'm doing the full RPM package, fe
> including modules signature and so on and I'm doing this in my free
> time.This wont work for bisecting. I have to setup something else. Is
> it ok if I restrict the bisect on the ath10k tree? That has enough
> commit already to begin with, plus I'm going to be on the road in less
> than two weeks.
>
> On 28 July 2015 at 13:26, Michal Kazior <michal.kazior@tieto.com> wrote:
>> On 28 July 2015 at 13:00, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>>> Hi Michal,
>>>
>>> this is the dmesg output from a boot with kernel 4.1.2 with patch to
>>> make the firmware load [1]
>>>
>>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>>> 0000:03:00.0: enabling device (0000 -> 0002)
>>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>>> 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
>>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>>> 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
>>> failed with error -2
>>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>>> 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
>>> killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
>>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>>> 0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>>> 0000:03:00.0 wlp3s0: renamed from wlan0
>>>
>>> I saw the report you mentioned (I'm subscribed to ath10k and try to
>>> keep it up with it). Not being expert at all I was not sure it was the
>>> same or not. Also there seems to be a difference that with irq_mode=1
>>> for me it just works like before.
>> I'm quite puzzled with the above printout. So either there's some
>> weird regression either in driver or the pci subsystem. It's good you
>> posted ;-)
>>
>> Just to be clear: were you using 4.2-rc3 as in from Linus' tree or Kalle's tree?
>>
>> Asking for a `git bisect` is probably a bit excessive - but it would
>> help a lot. I guess you'd have to manually cherry-pick qca6174 hw2 fix
>> [1] while bisecting.
>>
>> If bisect is too much I guess you could try reverting (in order):
>>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=0bcbbe679b66fee1b56def5cb30bfb4f616b1127
>>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=76d870ed09ab34154454b1adb823ae75f173c2d2
>>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=77258d409ce45890104e3da11d0261402c49aee1
>>
>> I'm shooting blind here though.
>>
>>> [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060
>>
>> Michał
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi Alexandre,

I think you have a different issue. In my case it doesn't take long to
load the firmware. It works for me as well with irq_mode=1, however
this was not needed with the previous kernel (4.1.2 as provided by
fedora updates-testing repo). Also Michał sees a problem with my
system.

I should also mention I made my firmware from the Windows driver with
dissect.py. I assume this is correct since it worked for an older
kernel, but I actually have no idea. And I also have no idea how to
generate the fw with API 5 (if this makes any difference, but since it
was not mentioned already I suppose it does not).

Thank you anyway :)

On 28 July 2015 at 17:12, Alexandre Maloteaux <a.maloteaux@gmail.com> wrote:
> Hi Enrico
>
> I had the same issue a few days ago on an Eurocom P5 Pro.
> I manage to get it working with the help of michal  by compiling the
> kvalo kernel master branch : https://github.com/kvalo/ath
>
> And then using this ath10k.conf file in /etc/modprobe.d
>
> options ath10k_core skip_otp=y
> options ath10k_pci  irq_mode=1
>
> It works on my archlinux system but firmware loading take 1 minute
> between each retry, so it takes 2 minutes to get the card up and
> running. I have not yet found a solution to this issue.
>
> Best Regards
>
> On 07/28/2015 03:57 PM, Enrico Tagliavini wrote:
>> I was testing the kernel from Fedora rawhide to test some issue
>> related to the sound card. So this is 4.2 rc3 as released by Linus
>> plus some Fedora patch. Nothing related to ath10k as far as I can see.
>>
>> Bisecting would require a lot of time. I'm doing the full RPM package, fe
>> including modules signature and so on and I'm doing this in my free
>> time.This wont work for bisecting. I have to setup something else. Is
>> it ok if I restrict the bisect on the ath10k tree? That has enough
>> commit already to begin with, plus I'm going to be on the road in less
>> than two weeks.
>>
>> On 28 July 2015 at 13:26, Michal Kazior <michal.kazior@tieto.com> wrote:
>>> On 28 July 2015 at 13:00, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>>>> Hi Michal,
>>>>
>>>> this is the dmesg output from a boot with kernel 4.1.2 with patch to
>>>> make the firmware load [1]
>>>>
>>>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>>>> 0000:03:00.0: enabling device (0000 -> 0002)
>>>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>>>> 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0
>>>> Jul 26 10:07:42 alientux.saurisiamonoi.org kernel: ath10k_pci
>>>> 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin
>>>> failed with error -2
>>>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>>>> 0000:03:00.0: qca6174 hw2.1 (0x05010000, 0x003405ff) fw
>>>> killer-n1525-fw api 4 htt 3.0 wmi 4 cal otp max_sta 32
>>>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>>>> 0000:03:00.0: debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>>>> Jul 26 10:07:44 alientux.saurisiamonoi.org kernel: ath10k_pci
>>>> 0000:03:00.0 wlp3s0: renamed from wlan0
>>>>
>>>> I saw the report you mentioned (I'm subscribed to ath10k and try to
>>>> keep it up with it). Not being expert at all I was not sure it was the
>>>> same or not. Also there seems to be a difference that with irq_mode=1
>>>> for me it just works like before.
>>> I'm quite puzzled with the above printout. So either there's some
>>> weird regression either in driver or the pci subsystem. It's good you
>>> posted ;-)
>>>
>>> Just to be clear: were you using 4.2-rc3 as in from Linus' tree or Kalle's tree?
>>>
>>> Asking for a `git bisect` is probably a bit excessive - but it would
>>> help a lot. I guess you'd have to manually cherry-pick qca6174 hw2 fix
>>> [1] while bisecting.
>>>
>>> If bisect is too much I guess you could try reverting (in order):
>>>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=0bcbbe679b66fee1b56def5cb30bfb4f616b1127
>>>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=76d870ed09ab34154454b1adb823ae75f173c2d2
>>>  https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/ath/ath10k?id=77258d409ce45890104e3da11d0261402c49aee1
>>>
>>> I'm shooting blind here though.
>>>
>>>> [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/wireless/ath/ath10k/pci.c?id=11a002efbaa7fbd9f6e616695ab42aa9f1caf060
>>>
>>> Michał
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Michal Kazior]

On 28 July 2015 at 17:12, Alexandre Maloteaux <a.maloteaux@gmail.com> wrote:
[...]
> It works on my archlinux system but firmware loading take 1 minute
> between each retry, so it takes 2 minutes to get the card up and
> running. I have not yet found a solution to this issue.

Go ask on the arch forum or lurk for udev firmware timeouts thread.
It's not entirely new and I'm betting this has been solved many times
already.


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Michal Kazior]

On 28 July 2015 at 16:57, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> I was testing the kernel from Fedora rawhide to test some issue
> related to the sound card. So this is 4.2 rc3 as released by Linus
> plus some Fedora patch. Nothing related to ath10k as far as I can see.
>
> Bisecting would require a lot of time. I'm doing the full RPM package,
> including modules signature and so on and I'm doing this in my free
> time.

I understand.


> This wont work for bisecting. I have to setup something else. Is
> it ok if I restrict the bisect on the ath10k tree? That has enough
> commit already to begin with, plus I'm going to be on the road in less
> than two weeks.

As long as you establish a working and a non-working commit id on
kvalo tree it should be fine I guess.


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Michal Kazior]

On 28 July 2015 at 16:57, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> I was testing the kernel from Fedora rawhide to test some issue
> related to the sound card. So this is 4.2 rc3 as released by Linus
> plus some Fedora patch. Nothing related to ath10k as far as I can see.
>
> Bisecting would require a lot of time. I'm doing the full RPM package,
> including modules signature and so on and I'm doing this in my free
> time.

I understand.


> This wont work for bisecting. I have to setup something else. Is
> it ok if I restrict the bisect on the ath10k tree? That has enough
> commit already to begin with, plus I'm going to be on the road in less
> than two weeks.

As long as you establish a working and a non-working commit id on
kvalo tree it should be fine I guess.


Michał

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Kalle Valo]

Michal Kazior <michal.kazior@tieto.com> writes:

>> This wont work for bisecting. I have to setup something else. Is
>> it ok if I restrict the bisect on the ath10k tree? That has enough
>> commit already to begin with, plus I'm going to be on the road in less
>> than two weeks.
>
> As long as you establish a working and a non-working commit id on
> kvalo tree it should be fine I guess.

And you can always limit the bisect to a certain directory, but the risk
here is that if the regression is outside ath10k bisect won't find it.
So you need to carefully consider is it safe to do or not. From the man
page:

"Cutting down bisection by giving more parameters to bisect start

       You can further cut down the number of trials, if you know what
       part of the tree is involved in the problem you are tracking
       down, by specifying path parameters when issuing the bisect start
       command:

           $ git bisect start -- arch/i386 include/asm-i386"

Also if you can even just narrow down the regression to a smaller set of
patches, let's say few hundred, might make it easier to find the
regression.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Kalle Valo]

Michal Kazior <michal.kazior@tieto.com> writes:

>> This wont work for bisecting. I have to setup something else. Is
>> it ok if I restrict the bisect on the ath10k tree? That has enough
>> commit already to begin with, plus I'm going to be on the road in less
>> than two weeks.
>
> As long as you establish a working and a non-working commit id on
> kvalo tree it should be fine I guess.

And you can always limit the bisect to a certain directory, but the risk
here is that if the regression is outside ath10k bisect won't find it.
So you need to carefully consider is it safe to do or not. From the man
page:

"Cutting down bisection by giving more parameters to bisect start

       You can further cut down the number of trials, if you know what
       part of the tree is involved in the problem you are tracking
       down, by specifying path parameters when issuing the bisect start
       command:

           $ git bisect start -- arch/i386 include/asm-i386"

Also if you can even just narrow down the regression to a smaller set of
patches, let's say few hundred, might make it easier to find the
regression.

-- 
Kalle Valo

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Yeah that's what I meant. My idea was to first bisect only the ath10k
directory, so restricting the bisect on the commits touching stuff
there. I guess if the issue is more broad it will come up somewhere
else as well, so this is a good starting point, I hope. Thank you for
pointing it out though, this will actually be the first time I do a
proper bisect.

Also do you want me to bisect Kalle's sources or Linus' master? By
what Michał said I guess Kalle's but I ask to be sure.

Also to be clear: I'm using Linus' sources at the moment, as provided
by Fedora rawhide.

For me it's the same, so let me know what you prefer and is more
useful to solve this issue.

On 29 July 2015 at 08:54, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>>> This wont work for bisecting. I have to setup something else. Is
>>> it ok if I restrict the bisect on the ath10k tree? That has enough
>>> commit already to begin with, plus I'm going to be on the road in less
>>> than two weeks.
>>
>> As long as you establish a working and a non-working commit id on
>> kvalo tree it should be fine I guess.
>
> And you can always limit the bisect to a certain directory, but the risk
> here is that if the regression is outside ath10k bisect won't find it.
> So you need to carefully consider is it safe to do or not. From the man
> page:
>
> "Cutting down bisection by giving more parameters to bisect start
>
>        You can further cut down the number of trials, if you know what
>        part of the tree is involved in the problem you are tracking
>        down, by specifying path parameters when issuing the bisect start
>        command:
>
>            $ git bisect start -- arch/i386 include/asm-i386"
>
> Also if you can even just narrow down the regression to a smaller set of
> patches, let's say few hundred, might make it easier to find the
> regression.
>
> --
> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Yeah that's what I meant. My idea was to first bisect only the ath10k
directory, so restricting the bisect on the commits touching stuff
there. I guess if the issue is more broad it will come up somewhere
else as well, so this is a good starting point, I hope. Thank you for
pointing it out though, this will actually be the first time I do a
proper bisect.

Also do you want me to bisect Kalle's sources or Linus' master? By
what Michał said I guess Kalle's but I ask to be sure.

Also to be clear: I'm using Linus' sources at the moment, as provided
by Fedora rawhide.

For me it's the same, so let me know what you prefer and is more
useful to solve this issue.

On 29 July 2015 at 08:54, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>>> This wont work for bisecting. I have to setup something else. Is
>>> it ok if I restrict the bisect on the ath10k tree? That has enough
>>> commit already to begin with, plus I'm going to be on the road in less
>>> than two weeks.
>>
>> As long as you establish a working and a non-working commit id on
>> kvalo tree it should be fine I guess.
>
> And you can always limit the bisect to a certain directory, but the risk
> here is that if the regression is outside ath10k bisect won't find it.
> So you need to carefully consider is it safe to do or not. From the man
> page:
>
> "Cutting down bisection by giving more parameters to bisect start
>
>        You can further cut down the number of trials, if you know what
>        part of the tree is involved in the problem you are tracking
>        down, by specifying path parameters when issuing the bisect start
>        command:
>
>            $ git bisect start -- arch/i386 include/asm-i386"
>
> Also if you can even just narrow down the regression to a smaller set of
> patches, let's say few hundred, might make it easier to find the
> regression.
>
> --
> Kalle Valo

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Kalle Valo]

Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:

> Yeah that's what I meant. My idea was to first bisect only the ath10k
> directory, so restricting the bisect on the commits touching stuff
> there. I guess if the issue is more broad it will come up somewhere
> else as well, so this is a good starting point, I hope. Thank you for
> pointing it out though, this will actually be the first time I do a
> proper bisect.

And remember to always to mention if you have restricted the bisect
somehow, that's important information. And better if you provide 'git
bisect log' output as well.

> Also do you want me to bisect Kalle's sources or Linus' master? By
> what Michał said I guess Kalle's but I ask to be sure.
>
> Also to be clear: I'm using Linus' sources at the moment, as provided
> by Fedora rawhide.
>
> For me it's the same, so let me know what you prefer and is more
> useful to solve this issue.

Good that you brought this up. As ath.git master branch gets rebased
every rc1 release you really cannot use that for bisect. Either you
should use ath.git ath-next branch or Linus' tree. To be on the safe
side I always recommend to use Linus' tree if at all possible.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Kalle Valo]

Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:

> Yeah that's what I meant. My idea was to first bisect only the ath10k
> directory, so restricting the bisect on the commits touching stuff
> there. I guess if the issue is more broad it will come up somewhere
> else as well, so this is a good starting point, I hope. Thank you for
> pointing it out though, this will actually be the first time I do a
> proper bisect.

And remember to always to mention if you have restricted the bisect
somehow, that's important information. And better if you provide 'git
bisect log' output as well.

> Also do you want me to bisect Kalle's sources or Linus' master? By
> what Michał said I guess Kalle's but I ask to be sure.
>
> Also to be clear: I'm using Linus' sources at the moment, as provided
> by Fedora rawhide.
>
> For me it's the same, so let me know what you prefer and is more
> useful to solve this issue.

Good that you brought this up. As ath.git master branch gets rebased
every rc1 release you really cannot use that for bisect. Either you
should use ath.git ath-next branch or Linus' tree. To be on the safe
side I always recommend to use Linus' tree if at all possible.

-- 
Kalle Valo

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Sound! I'll keep a copy of the log then. If the bisect on ath10k
folder will lead nowhere I'll see if I can make it over the whole
tree. At least by doing it on the ath10k tree I hope to narrow down
the number of commit.

Ok then I'll use Linus' master, no problem with this.

I hope to at least get started this weekend.

On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>
>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>> directory, so restricting the bisect on the commits touching stuff
>> there. I guess if the issue is more broad it will come up somewhere
>> else as well, so this is a good starting point, I hope. Thank you for
>> pointing it out though, this will actually be the first time I do a
>> proper bisect.
>
> And remember to always to mention if you have restricted the bisect
> somehow, that's important information. And better if you provide 'git
> bisect log' output as well.
>
>> Also do you want me to bisect Kalle's sources or Linus' master? By
>> what Michał said I guess Kalle's but I ask to be sure.
>>
>> Also to be clear: I'm using Linus' sources at the moment, as provided
>> by Fedora rawhide.
>>
>> For me it's the same, so let me know what you prefer and is more
>> useful to solve this issue.
>
> Good that you brought this up. As ath.git master branch gets rebased
> every rc1 release you really cannot use that for bisect. Either you
> should use ath.git ath-next branch or Linus' tree. To be on the safe
> side I always recommend to use Linus' tree if at all possible.
>
> --
> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Sound! I'll keep a copy of the log then. If the bisect on ath10k
folder will lead nowhere I'll see if I can make it over the whole
tree. At least by doing it on the ath10k tree I hope to narrow down
the number of commit.

Ok then I'll use Linus' master, no problem with this.

I hope to at least get started this weekend.

On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>
>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>> directory, so restricting the bisect on the commits touching stuff
>> there. I guess if the issue is more broad it will come up somewhere
>> else as well, so this is a good starting point, I hope. Thank you for
>> pointing it out though, this will actually be the first time I do a
>> proper bisect.
>
> And remember to always to mention if you have restricted the bisect
> somehow, that's important information. And better if you provide 'git
> bisect log' output as well.
>
>> Also do you want me to bisect Kalle's sources or Linus' master? By
>> what Michał said I guess Kalle's but I ask to be sure.
>>
>> Also to be clear: I'm using Linus' sources at the moment, as provided
>> by Fedora rawhide.
>>
>> For me it's the same, so let me know what you prefer and is more
>> useful to solve this issue.
>
> Good that you brought this up. As ath.git master branch gets rebased
> every rc1 release you really cannot use that for bisect. Either you
> should use ath.git ath-next branch or Linus' tree. To be on the safe
> side I always recommend to use Linus' tree if at all possible.
>
> --
> Kalle Valo

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi there,

I got 4.2 rc4 running and I'm going to start the bisect. Before
compiling I enabled ath10k debug and this is the output for with
default irq_mode:

enrico@alientux ~ $ dmesg | grep ath
[   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
[   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
[   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
[   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
[   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
[   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
[   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
[   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
[   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
[   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
[   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
[   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
[   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
[   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
[   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
[   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
[   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
[   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
[   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
[   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
[   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
[   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
[   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
version 0x5010000
[   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
error -2
[   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
file, falling back to generic: -2
[   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
[   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
[   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
[   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
[   16.384385] ath10k_pci 0000:03:00.0: features
[   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
00                          ........
[   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
[   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
[   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
[   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
[   16.384394] ath10k_pci 0000:03:00.0: bmi start
[   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
[   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
[   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
[   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
[   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
[   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
calibration file, try DT next: -2
[   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
try OTP next: -2
[   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
[   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
[   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
[   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
[   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
[   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
[   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
0x1234 buffer 0xffffc9000166f64c length 29533
[   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
[   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffffc9000166f64c length 29532
[   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffff8800c4763d2c length 4
[   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
[   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
[   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
[   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
[   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
[   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
ffffc900015fe044 len 464383 mode normal
[   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
0x1234 buffer 0xffffc900015fe044 length 464383
[   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
[   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffffc900015fe044 length 464380
[   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffff8800c4763d2c length 4
[   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
[   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
[   17.548871] ath10k_pci 0000:03:00.0: bmi done
[   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
[   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
[   17.548923] ath10k_pci 0000:03:00.0: boot hif start
[   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
response completion, polling..
[   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
pipe 0 dl pipe 1 eid 0 ready
[   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
[   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
0 TX flow control disabled
[   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
not allocate target credits
[   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
[   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
[   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
[   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
[   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
[   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
[   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
[   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
[   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
[   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
[   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
[   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
[   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
[   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
[   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)

Maybe this trigger some bell.

On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> Sound! I'll keep a copy of the log then. If the bisect on ath10k
> folder will lead nowhere I'll see if I can make it over the whole
> tree. At least by doing it on the ath10k tree I hope to narrow down
> the number of commit.
>
> Ok then I'll use Linus' master, no problem with this.
>
> I hope to at least get started this weekend.
>
> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>
>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>> directory, so restricting the bisect on the commits touching stuff
>>> there. I guess if the issue is more broad it will come up somewhere
>>> else as well, so this is a good starting point, I hope. Thank you for
>>> pointing it out though, this will actually be the first time I do a
>>> proper bisect.
>>
>> And remember to always to mention if you have restricted the bisect
>> somehow, that's important information. And better if you provide 'git
>> bisect log' output as well.
>>
>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>> what Michał said I guess Kalle's but I ask to be sure.
>>>
>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>> by Fedora rawhide.
>>>
>>> For me it's the same, so let me know what you prefer and is more
>>> useful to solve this issue.
>>
>> Good that you brought this up. As ath.git master branch gets rebased
>> every rc1 release you really cannot use that for bisect. Either you
>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>> side I always recommend to use Linus' tree if at all possible.
>>
>> --
>> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi there,

I got 4.2 rc4 running and I'm going to start the bisect. Before
compiling I enabled ath10k debug and this is the output for with
default irq_mode:

enrico@alientux ~ $ dmesg | grep ath
[   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
[   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
[   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
[   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
[   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
[   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
[   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
[   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
[   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
[   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
[   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
[   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
[   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
[   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
[   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
[   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
[   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
[   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
[   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
[   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
[   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
[   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
[   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
[   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
[   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
version 0x5010000
[   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/cal-pci-0000:03:00.0.bin failed with error -2
[   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
error -2
[   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
file, falling back to generic: -2
[   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
[   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
[   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
[   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
[   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
[   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
[   16.384385] ath10k_pci 0000:03:00.0: features
[   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
00                          ........
[   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
[   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
[   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
[   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
[   16.384394] ath10k_pci 0000:03:00.0: bmi start
[   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
[   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
[   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
[   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
[   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
[   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
calibration file, try DT next: -2
[   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
try OTP next: -2
[   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
[   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
[   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
[   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
[   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
[   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
[   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
0x1234 buffer 0xffffc9000166f64c length 29533
[   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
[   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffffc9000166f64c length 29532
[   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffff8800c4763d2c length 4
[   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
[   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
[   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
[   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
[   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
[   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
ffffc900015fe044 len 464383 mode normal
[   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
0x1234 buffer 0xffffc900015fe044 length 464383
[   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
[   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffffc900015fe044 length 464380
[   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
0xffff8800c4763d2c length 4
[   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
[   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
[   17.548871] ath10k_pci 0000:03:00.0: bmi done
[   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
[   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
[   17.548923] ath10k_pci 0000:03:00.0: boot hif start
[   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
response completion, polling..
[   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
pipe 0 dl pipe 1 eid 0 ready
[   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
[   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
0 TX flow control disabled
[   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
not allocate target credits
[   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
[   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
[   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
[   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
[   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
[   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
[   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
[   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
[   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
entries 16 base_addr ffff88003f00a000
[   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
512 base_addr ffff88003f3c8000
[   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
128 base_addr ffff88003eb6a000
[   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
entries 32 base_addr ffff88003f349000
[   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
entries 4096 base_addr ffff8800ba940000
[   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
entries 2 base_addr ffff8800c4888000
[   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
2 base_addr ffff8800ba889000
[   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
[   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
[   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
[   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
[   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
[   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
[   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
[   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
[   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)

Maybe this trigger some bell.

On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
> Sound! I'll keep a copy of the log then. If the bisect on ath10k
> folder will lead nowhere I'll see if I can make it over the whole
> tree. At least by doing it on the ath10k tree I hope to narrow down
> the number of commit.
>
> Ok then I'll use Linus' master, no problem with this.
>
> I hope to at least get started this weekend.
>
> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>
>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>> directory, so restricting the bisect on the commits touching stuff
>>> there. I guess if the issue is more broad it will come up somewhere
>>> else as well, so this is a good starting point, I hope. Thank you for
>>> pointing it out though, this will actually be the first time I do a
>>> proper bisect.
>>
>> And remember to always to mention if you have restricted the bisect
>> somehow, that's important information. And better if you provide 'git
>> bisect log' output as well.
>>
>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>> what Michał said I guess Kalle's but I ask to be sure.
>>>
>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>> by Fedora rawhide.
>>>
>>> For me it's the same, so let me know what you prefer and is more
>>> useful to solve this issue.
>>
>> Good that you brought this up. As ath.git master branch gets rebased
>> every rc1 release you really cannot use that for bisect. Either you
>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>> side I always recommend to use Linus' tree if at all possible.
>>
>> --
>> Kalle Valo

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Bisect is done, unfortunately I think there is no good news

$ git bisect log
git bisect start '--' 'drivers/net/wireless/ath/ath10k/'
# bad: [86ea07ca846a7c352f39dd0b7d81f15f403c7db8] Merge branch
'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
git bisect bad 86ea07ca846a7c352f39dd0b7d81f15f403c7db8
# good: [b953c0d234bc72e8489d3bf51a276c5c4ec85345] Linux 4.1
git bisect good b953c0d234bc72e8489d3bf51a276c5c4ec85345
# good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
wait_for_completion_timeout return type
git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
# good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
wait_for_completion_timeout return type
git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
# good: [0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0] ath10k: enable ibss-rsn
git bisect good 0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0
# good: [48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6] ath10k: add new
4addr related fw_feature
git bisect good 48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6
# good: [163f52647a0f7e34e803b51456c60deedd26ca1d] ath10k: bypass PLL
setting on target init for QCA9888
git bisect good 163f52647a0f7e34e803b51456c60deedd26ca1d
# good: [d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9] ath10k: fix
ar->rx_channel updating logic
git bisect good d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9
# good: [0e6eb417fc1facda1c9a9189be85f16cb5b8b69f] ath10k: fix channel switching
git bisect good 0e6eb417fc1facda1c9a9189be85f16cb5b8b69f
# good: [30686bf7f5b3c30831761e188a6e3cb33580fa48] mac80211: convert
HW flags to unsigned long bitmap
git bisect good 30686bf7f5b3c30831761e188a6e3cb33580fa48
# good: [469d479f91b8277cc921d7525f31c832b25d9efb] ath10k: prevent
memory leak in wmi rx ops
git bisect good 469d479f91b8277cc921d7525f31c832b25d9efb
# good: [fa433354f042105fc7a299253f904bb48dae0950] Merge tag
'wireless-drivers-next-for-davem-2015-06-18' of
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
git bisect good fa433354f042105fc7a299253f904bb48dae0950

as you can see I tried to restrict the bisect to the ath10k folder
only and none of the commit was faulty. Probably because all the
commit were actually still on kernel 4.1 rc, none of them was on 4.2
except the starting bad one (which was the latest when I cloned the
repo for rc4).

So I guess we are switching to plan B here and bisecting the entire
tree right? If so, starting from the same bad commit as for this one
and using the newest good commit I tested (so last entry in the bisect
I just did)

$ git bisect good fa433354f042105fc7a299253f904bb48dae0950
Bisecting: 6373 revisions left to test after this (roughly 13 steps)
[4aa705b18bf17c4ff33ff7bbcd3f0c596443fa81] Merge tag 'armsoc-soc' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc

13 steps are not crazy.... sigh. Give me enough days, in the weekend
I'll be on the road the I'll see if I can get few quiet hours to get
this done.

Any last minute advise or question before I reset this bisect?

On 1 August 2015 at 14:30, Enrico Tagliavini
<enrico.tagliavini@gmail.com> wrote:
> Hi there,
>
> I got 4.2 rc4 running and I'm going to start the bisect. Before
> compiling I enabled ath10k debug and this is the output for with
> default irq_mode:
>
> enrico@alientux ~ $ dmesg | grep ath
> [   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
> [   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
> [   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
> [   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
> [   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
> [   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
> [   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
> [   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
> [   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
> [   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
> [   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
> [   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
> [   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
> [   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
> [   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
> [   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
> [   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
> version 0x5010000
> [   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
> error -2
> [   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
> file, falling back to generic: -2
> [   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
> [   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
> [   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
> [   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
> [   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
> [   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
> [   16.384385] ath10k_pci 0000:03:00.0: features
> [   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
> 00                          ........
> [   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
> [   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
> [   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
> [   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
> [   16.384394] ath10k_pci 0000:03:00.0: bmi start
> [   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
> [   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
> [   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
> [   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
> [   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
> [   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
> calibration file, try DT next: -2
> [   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
> try OTP next: -2
> [   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
> [   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
> [   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
> [   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
> [   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
> [   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
> [   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
> 0x1234 buffer 0xffffc9000166f64c length 29533
> [   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
> [   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffffc9000166f64c length 29532
> [   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffff8800c4763d2c length 4
> [   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
> [   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
> [   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
> [   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
> [   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
> [   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
> ffffc900015fe044 len 464383 mode normal
> [   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
> 0x1234 buffer 0xffffc900015fe044 length 464383
> [   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
> [   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffffc900015fe044 length 464380
> [   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffff8800c4763d2c length 4
> [   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
> [   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
> [   17.548871] ath10k_pci 0000:03:00.0: bmi done
> [   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
> [   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
> [   17.548923] ath10k_pci 0000:03:00.0: boot hif start
> [   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
> response completion, polling..
> [   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
> pipe 0 dl pipe 1 eid 0 ready
> [   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
> [   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
> 0 TX flow control disabled
> [   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
> not allocate target credits
> [   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
> [   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
> [   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
> [   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
> [   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
> [   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
> [   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
> [   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
> [   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
> [   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>
> Maybe this trigger some bell.
>
> On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>> Sound! I'll keep a copy of the log then. If the bisect on ath10k
>> folder will lead nowhere I'll see if I can make it over the whole
>> tree. At least by doing it on the ath10k tree I hope to narrow down
>> the number of commit.
>>
>> Ok then I'll use Linus' master, no problem with this.
>>
>> I hope to at least get started this weekend.
>>
>> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>>
>>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>>> directory, so restricting the bisect on the commits touching stuff
>>>> there. I guess if the issue is more broad it will come up somewhere
>>>> else as well, so this is a good starting point, I hope. Thank you for
>>>> pointing it out though, this will actually be the first time I do a
>>>> proper bisect.
>>>
>>> And remember to always to mention if you have restricted the bisect
>>> somehow, that's important information. And better if you provide 'git
>>> bisect log' output as well.
>>>
>>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>>> what Michał said I guess Kalle's but I ask to be sure.
>>>>
>>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>>> by Fedora rawhide.
>>>>
>>>> For me it's the same, so let me know what you prefer and is more
>>>> useful to solve this issue.
>>>
>>> Good that you brought this up. As ath.git master branch gets rebased
>>> every rc1 release you really cannot use that for bisect. Either you
>>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>>> side I always recommend to use Linus' tree if at all possible.
>>>
>>> --
>>> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Bisect is done, unfortunately I think there is no good news

$ git bisect log
git bisect start '--' 'drivers/net/wireless/ath/ath10k/'
# bad: [86ea07ca846a7c352f39dd0b7d81f15f403c7db8] Merge branch
'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
git bisect bad 86ea07ca846a7c352f39dd0b7d81f15f403c7db8
# good: [b953c0d234bc72e8489d3bf51a276c5c4ec85345] Linux 4.1
git bisect good b953c0d234bc72e8489d3bf51a276c5c4ec85345
# good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
wait_for_completion_timeout return type
git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
# good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
wait_for_completion_timeout return type
git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
# good: [0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0] ath10k: enable ibss-rsn
git bisect good 0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0
# good: [48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6] ath10k: add new
4addr related fw_feature
git bisect good 48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6
# good: [163f52647a0f7e34e803b51456c60deedd26ca1d] ath10k: bypass PLL
setting on target init for QCA9888
git bisect good 163f52647a0f7e34e803b51456c60deedd26ca1d
# good: [d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9] ath10k: fix
ar->rx_channel updating logic
git bisect good d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9
# good: [0e6eb417fc1facda1c9a9189be85f16cb5b8b69f] ath10k: fix channel switching
git bisect good 0e6eb417fc1facda1c9a9189be85f16cb5b8b69f
# good: [30686bf7f5b3c30831761e188a6e3cb33580fa48] mac80211: convert
HW flags to unsigned long bitmap
git bisect good 30686bf7f5b3c30831761e188a6e3cb33580fa48
# good: [469d479f91b8277cc921d7525f31c832b25d9efb] ath10k: prevent
memory leak in wmi rx ops
git bisect good 469d479f91b8277cc921d7525f31c832b25d9efb
# good: [fa433354f042105fc7a299253f904bb48dae0950] Merge tag
'wireless-drivers-next-for-davem-2015-06-18' of
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
git bisect good fa433354f042105fc7a299253f904bb48dae0950

as you can see I tried to restrict the bisect to the ath10k folder
only and none of the commit was faulty. Probably because all the
commit were actually still on kernel 4.1 rc, none of them was on 4.2
except the starting bad one (which was the latest when I cloned the
repo for rc4).

So I guess we are switching to plan B here and bisecting the entire
tree right? If so, starting from the same bad commit as for this one
and using the newest good commit I tested (so last entry in the bisect
I just did)

$ git bisect good fa433354f042105fc7a299253f904bb48dae0950
Bisecting: 6373 revisions left to test after this (roughly 13 steps)
[4aa705b18bf17c4ff33ff7bbcd3f0c596443fa81] Merge tag 'armsoc-soc' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc

13 steps are not crazy.... sigh. Give me enough days, in the weekend
I'll be on the road the I'll see if I can get few quiet hours to get
this done.

Any last minute advise or question before I reset this bisect?

On 1 August 2015 at 14:30, Enrico Tagliavini
<enrico.tagliavini@gmail.com> wrote:
> Hi there,
>
> I got 4.2 rc4 running and I'm going to start the bisect. Before
> compiling I enabled ath10k debug and this is the output for with
> default irq_mode:
>
> enrico@alientux ~ $ dmesg | grep ath
> [   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
> [   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
> [   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
> irq_mode 0 reset_mode 0
> [   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
> [   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
> [   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
> [   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
> [   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
> [   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
> [   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
> [   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
> [   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
> [   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
> [   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
> [   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
> [   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
> [   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
> [   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
> [   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
> version 0x5010000
> [   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
> error -2
> [   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
> file, falling back to generic: -2
> [   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
> [   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
> [   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
> [   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
> [   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
> [   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
> [   16.384385] ath10k_pci 0000:03:00.0: features
> [   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
> 00                          ........
> [   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
> [   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
> [   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
> [   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
> [   16.384394] ath10k_pci 0000:03:00.0: bmi start
> [   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
> [   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
> [   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
> [   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
> [   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
> [   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
> calibration file, try DT next: -2
> [   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
> try OTP next: -2
> [   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
> [   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
> [   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
> [   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
> [   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
> [   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
> [   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
> 0x1234 buffer 0xffffc9000166f64c length 29533
> [   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
> [   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffffc9000166f64c length 29532
> [   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffff8800c4763d2c length 4
> [   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
> [   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
> [   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
> [   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
> [   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
> [   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
> ffffc900015fe044 len 464383 mode normal
> [   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
> 0x1234 buffer 0xffffc900015fe044 length 464383
> [   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
> [   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffffc900015fe044 length 464380
> [   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
> 0xffff8800c4763d2c length 4
> [   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
> [   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
> [   17.548871] ath10k_pci 0000:03:00.0: bmi done
> [   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
> [   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
> [   17.548923] ath10k_pci 0000:03:00.0: boot hif start
> [   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
> response completion, polling..
> [   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
> pipe 0 dl pipe 1 eid 0 ready
> [   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
> [   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
> 0 TX flow control disabled
> [   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
> not allocate target credits
> [   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
> [   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
> [   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
> [   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
> [   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
> [   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
> [   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
> entries 16 base_addr ffff88003f00a000
> [   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
> 512 base_addr ffff88003f3c8000
> [   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
> 128 base_addr ffff88003eb6a000
> [   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
> entries 32 base_addr ffff88003f349000
> [   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
> entries 4096 base_addr ffff8800ba940000
> [   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
> entries 2 base_addr ffff8800c4888000
> [   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
> 2 base_addr ffff8800ba889000
> [   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
> [   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
> [   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
> [   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
> [   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
> [   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
> [   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
> [   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>
> Maybe this trigger some bell.
>
> On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>> Sound! I'll keep a copy of the log then. If the bisect on ath10k
>> folder will lead nowhere I'll see if I can make it over the whole
>> tree. At least by doing it on the ath10k tree I hope to narrow down
>> the number of commit.
>>
>> Ok then I'll use Linus' master, no problem with this.
>>
>> I hope to at least get started this weekend.
>>
>> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>>
>>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>>> directory, so restricting the bisect on the commits touching stuff
>>>> there. I guess if the issue is more broad it will come up somewhere
>>>> else as well, so this is a good starting point, I hope. Thank you for
>>>> pointing it out though, this will actually be the first time I do a
>>>> proper bisect.
>>>
>>> And remember to always to mention if you have restricted the bisect
>>> somehow, that's important information. And better if you provide 'git
>>> bisect log' output as well.
>>>
>>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>>> what Michał said I guess Kalle's but I ask to be sure.
>>>>
>>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>>> by Fedora rawhide.
>>>>
>>>> For me it's the same, so let me know what you prefer and is more
>>>> useful to solve this issue.
>>>
>>> Good that you brought this up. As ath.git master branch gets rebased
>>> every rc1 release you really cannot use that for bisect. Either you
>>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>>> side I always recommend to use Linus' tree if at all possible.
>>>
>>> --
>>> Kalle Valo

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi there,

sorry for the late and still no results. Life never goes as planned
does it? I will still try to find the time to bisect this, however I
cannot foresee when this might happen. If anybody has urgency to fix
this might as well bisecting instead of waiting for me. My apologize
:(

Best regards.
Enrico

On 5 August 2015 at 19:52, Enrico Tagliavini
<enrico.tagliavini@gmail.com> wrote:
> Bisect is done, unfortunately I think there is no good news
>
> $ git bisect log
> git bisect start '--' 'drivers/net/wireless/ath/ath10k/'
> # bad: [86ea07ca846a7c352f39dd0b7d81f15f403c7db8] Merge branch
> 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
> git bisect bad 86ea07ca846a7c352f39dd0b7d81f15f403c7db8
> # good: [b953c0d234bc72e8489d3bf51a276c5c4ec85345] Linux 4.1
> git bisect good b953c0d234bc72e8489d3bf51a276c5c4ec85345
> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
> wait_for_completion_timeout return type
> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
> wait_for_completion_timeout return type
> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
> # good: [0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0] ath10k: enable ibss-rsn
> git bisect good 0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0
> # good: [48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6] ath10k: add new
> 4addr related fw_feature
> git bisect good 48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6
> # good: [163f52647a0f7e34e803b51456c60deedd26ca1d] ath10k: bypass PLL
> setting on target init for QCA9888
> git bisect good 163f52647a0f7e34e803b51456c60deedd26ca1d
> # good: [d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9] ath10k: fix
> ar->rx_channel updating logic
> git bisect good d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9
> # good: [0e6eb417fc1facda1c9a9189be85f16cb5b8b69f] ath10k: fix channel switching
> git bisect good 0e6eb417fc1facda1c9a9189be85f16cb5b8b69f
> # good: [30686bf7f5b3c30831761e188a6e3cb33580fa48] mac80211: convert
> HW flags to unsigned long bitmap
> git bisect good 30686bf7f5b3c30831761e188a6e3cb33580fa48
> # good: [469d479f91b8277cc921d7525f31c832b25d9efb] ath10k: prevent
> memory leak in wmi rx ops
> git bisect good 469d479f91b8277cc921d7525f31c832b25d9efb
> # good: [fa433354f042105fc7a299253f904bb48dae0950] Merge tag
> 'wireless-drivers-next-for-davem-2015-06-18' of
> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
> git bisect good fa433354f042105fc7a299253f904bb48dae0950
>
> as you can see I tried to restrict the bisect to the ath10k folder
> only and none of the commit was faulty. Probably because all the
> commit were actually still on kernel 4.1 rc, none of them was on 4.2
> except the starting bad one (which was the latest when I cloned the
> repo for rc4).
>
> So I guess we are switching to plan B here and bisecting the entire
> tree right? If so, starting from the same bad commit as for this one
> and using the newest good commit I tested (so last entry in the bisect
> I just did)
>
> $ git bisect good fa433354f042105fc7a299253f904bb48dae0950
> Bisecting: 6373 revisions left to test after this (roughly 13 steps)
> [4aa705b18bf17c4ff33ff7bbcd3f0c596443fa81] Merge tag 'armsoc-soc' of
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
>
> 13 steps are not crazy.... sigh. Give me enough days, in the weekend
> I'll be on the road the I'll see if I can get few quiet hours to get
> this done.
>
> Any last minute advise or question before I reset this bisect?
>
> On 1 August 2015 at 14:30, Enrico Tagliavini
> <enrico.tagliavini@gmail.com> wrote:
>> Hi there,
>>
>> I got 4.2 rc4 running and I'm going to start the bisect. Before
>> compiling I enabled ath10k debug and this is the output for with
>> default irq_mode:
>>
>> enrico@alientux ~ $ dmesg | grep ath
>> [   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>> [   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
>> [   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>> [   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>> [   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
>> [   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
>> [   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
>> [   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
>> [   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>> [   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
>> [   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>> [   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
>> [   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
>> [   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
>> [   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
>> [   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>> [   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
>> [   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
>> version 0x5010000
>> [   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>> [   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
>> error -2
>> [   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
>> file, falling back to generic: -2
>> [   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
>> [   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>> [   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>> [   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
>> [   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
>> [   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
>> [   16.384385] ath10k_pci 0000:03:00.0: features
>> [   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
>> 00                          ........
>> [   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
>> [   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
>> [   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
>> [   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
>> [   16.384394] ath10k_pci 0000:03:00.0: bmi start
>> [   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
>> [   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
>> [   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
>> [   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
>> [   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
>> [   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
>> calibration file, try DT next: -2
>> [   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
>> try OTP next: -2
>> [   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
>> [   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
>> [   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
>> [   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
>> [   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
>> [   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
>> [   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
>> 0x1234 buffer 0xffffc9000166f64c length 29533
>> [   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>> [   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffffc9000166f64c length 29532
>> [   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffff8800c4763d2c length 4
>> [   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>> [   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
>> [   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
>> [   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
>> [   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
>> [   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
>> ffffc900015fe044 len 464383 mode normal
>> [   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
>> 0x1234 buffer 0xffffc900015fe044 length 464383
>> [   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>> [   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffffc900015fe044 length 464380
>> [   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffff8800c4763d2c length 4
>> [   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>> [   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
>> [   17.548871] ath10k_pci 0000:03:00.0: bmi done
>> [   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
>> [   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
>> [   17.548923] ath10k_pci 0000:03:00.0: boot hif start
>> [   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
>> response completion, polling..
>> [   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
>> pipe 0 dl pipe 1 eid 0 ready
>> [   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
>> [   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
>> 0 TX flow control disabled
>> [   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
>> not allocate target credits
>> [   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
>> [   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
>> [   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
>> [   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
>> [   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
>> [   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
>> [   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
>> [   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
>> [   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
>> [   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>>
>> Maybe this trigger some bell.
>>
>> On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>>> Sound! I'll keep a copy of the log then. If the bisect on ath10k
>>> folder will lead nowhere I'll see if I can make it over the whole
>>> tree. At least by doing it on the ath10k tree I hope to narrow down
>>> the number of commit.
>>>
>>> Ok then I'll use Linus' master, no problem with this.
>>>
>>> I hope to at least get started this weekend.
>>>
>>> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>>>
>>>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>>>> directory, so restricting the bisect on the commits touching stuff
>>>>> there. I guess if the issue is more broad it will come up somewhere
>>>>> else as well, so this is a good starting point, I hope. Thank you for
>>>>> pointing it out though, this will actually be the first time I do a
>>>>> proper bisect.
>>>>
>>>> And remember to always to mention if you have restricted the bisect
>>>> somehow, that's important information. And better if you provide 'git
>>>> bisect log' output as well.
>>>>
>>>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>>>> what Michał said I guess Kalle's but I ask to be sure.
>>>>>
>>>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>>>> by Fedora rawhide.
>>>>>
>>>>> For me it's the same, so let me know what you prefer and is more
>>>>> useful to solve this issue.
>>>>
>>>> Good that you brought this up. As ath.git master branch gets rebased
>>>> every rc1 release you really cannot use that for bisect. Either you
>>>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>>>> side I always recommend to use Linus' tree if at all possible.
>>>>
>>>> --
>>>> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi there,

sorry for the late and still no results. Life never goes as planned
does it? I will still try to find the time to bisect this, however I
cannot foresee when this might happen. If anybody has urgency to fix
this might as well bisecting instead of waiting for me. My apologize
:(

Best regards.
Enrico

On 5 August 2015 at 19:52, Enrico Tagliavini
<enrico.tagliavini@gmail.com> wrote:
> Bisect is done, unfortunately I think there is no good news
>
> $ git bisect log
> git bisect start '--' 'drivers/net/wireless/ath/ath10k/'
> # bad: [86ea07ca846a7c352f39dd0b7d81f15f403c7db8] Merge branch
> 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
> git bisect bad 86ea07ca846a7c352f39dd0b7d81f15f403c7db8
> # good: [b953c0d234bc72e8489d3bf51a276c5c4ec85345] Linux 4.1
> git bisect good b953c0d234bc72e8489d3bf51a276c5c4ec85345
> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
> wait_for_completion_timeout return type
> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
> wait_for_completion_timeout return type
> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
> # good: [0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0] ath10k: enable ibss-rsn
> git bisect good 0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0
> # good: [48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6] ath10k: add new
> 4addr related fw_feature
> git bisect good 48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6
> # good: [163f52647a0f7e34e803b51456c60deedd26ca1d] ath10k: bypass PLL
> setting on target init for QCA9888
> git bisect good 163f52647a0f7e34e803b51456c60deedd26ca1d
> # good: [d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9] ath10k: fix
> ar->rx_channel updating logic
> git bisect good d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9
> # good: [0e6eb417fc1facda1c9a9189be85f16cb5b8b69f] ath10k: fix channel switching
> git bisect good 0e6eb417fc1facda1c9a9189be85f16cb5b8b69f
> # good: [30686bf7f5b3c30831761e188a6e3cb33580fa48] mac80211: convert
> HW flags to unsigned long bitmap
> git bisect good 30686bf7f5b3c30831761e188a6e3cb33580fa48
> # good: [469d479f91b8277cc921d7525f31c832b25d9efb] ath10k: prevent
> memory leak in wmi rx ops
> git bisect good 469d479f91b8277cc921d7525f31c832b25d9efb
> # good: [fa433354f042105fc7a299253f904bb48dae0950] Merge tag
> 'wireless-drivers-next-for-davem-2015-06-18' of
> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
> git bisect good fa433354f042105fc7a299253f904bb48dae0950
>
> as you can see I tried to restrict the bisect to the ath10k folder
> only and none of the commit was faulty. Probably because all the
> commit were actually still on kernel 4.1 rc, none of them was on 4.2
> except the starting bad one (which was the latest when I cloned the
> repo for rc4).
>
> So I guess we are switching to plan B here and bisecting the entire
> tree right? If so, starting from the same bad commit as for this one
> and using the newest good commit I tested (so last entry in the bisect
> I just did)
>
> $ git bisect good fa433354f042105fc7a299253f904bb48dae0950
> Bisecting: 6373 revisions left to test after this (roughly 13 steps)
> [4aa705b18bf17c4ff33ff7bbcd3f0c596443fa81] Merge tag 'armsoc-soc' of
> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
>
> 13 steps are not crazy.... sigh. Give me enough days, in the weekend
> I'll be on the road the I'll see if I can get few quiet hours to get
> this done.
>
> Any last minute advise or question before I reset this bisect?
>
> On 1 August 2015 at 14:30, Enrico Tagliavini
> <enrico.tagliavini@gmail.com> wrote:
>> Hi there,
>>
>> I got 4.2 rc4 running and I'm going to start the bisect. Before
>> compiling I enabled ath10k debug and this is the output for with
>> default irq_mode:
>>
>> enrico@alientux ~ $ dmesg | grep ath
>> [   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>> [   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
>> [   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>> [   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>> [   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
>> [   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
>> [   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
>> [   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
>> [   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>> [   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
>> [   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>> [   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
>> [   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
>> [   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
>> [   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
>> [   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
>> [   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>> [   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
>> [   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
>> version 0x5010000
>> [   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>> [   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
>> error -2
>> [   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
>> file, falling back to generic: -2
>> [   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
>> [   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>> [   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>> [   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
>> [   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
>> [   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
>> [   16.384385] ath10k_pci 0000:03:00.0: features
>> [   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
>> 00                          ........
>> [   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
>> [   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
>> [   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
>> [   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
>> [   16.384394] ath10k_pci 0000:03:00.0: bmi start
>> [   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
>> [   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
>> [   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
>> [   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
>> [   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
>> [   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
>> calibration file, try DT next: -2
>> [   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
>> try OTP next: -2
>> [   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
>> [   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
>> [   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
>> [   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
>> [   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
>> [   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
>> [   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
>> 0x1234 buffer 0xffffc9000166f64c length 29533
>> [   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>> [   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffffc9000166f64c length 29532
>> [   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffff8800c4763d2c length 4
>> [   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>> [   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
>> [   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
>> [   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
>> [   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
>> [   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
>> ffffc900015fe044 len 464383 mode normal
>> [   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
>> 0x1234 buffer 0xffffc900015fe044 length 464383
>> [   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>> [   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffffc900015fe044 length 464380
>> [   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
>> 0xffff8800c4763d2c length 4
>> [   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>> [   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
>> [   17.548871] ath10k_pci 0000:03:00.0: bmi done
>> [   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
>> [   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
>> [   17.548923] ath10k_pci 0000:03:00.0: boot hif start
>> [   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
>> response completion, polling..
>> [   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
>> pipe 0 dl pipe 1 eid 0 ready
>> [   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
>> [   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
>> 0 TX flow control disabled
>> [   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
>> not allocate target credits
>> [   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>> [   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
>> [   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
>> [   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
>> [   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
>> [   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
>> [   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>> entries 16 base_addr ffff88003f00a000
>> [   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>> 512 base_addr ffff88003f3c8000
>> [   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>> 128 base_addr ffff88003eb6a000
>> [   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>> entries 32 base_addr ffff88003f349000
>> [   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>> entries 4096 base_addr ffff8800ba940000
>> [   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>> entries 2 base_addr ffff8800c4888000
>> [   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>> 2 base_addr ffff8800ba889000
>> [   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>> [   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
>> [   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
>> [   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
>> [   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
>> [   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
>> [   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
>> [   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>>
>> Maybe this trigger some bell.
>>
>> On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>>> Sound! I'll keep a copy of the log then. If the bisect on ath10k
>>> folder will lead nowhere I'll see if I can make it over the whole
>>> tree. At least by doing it on the ath10k tree I hope to narrow down
>>> the number of commit.
>>>
>>> Ok then I'll use Linus' master, no problem with this.
>>>
>>> I hope to at least get started this weekend.
>>>
>>> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>>>
>>>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>>>> directory, so restricting the bisect on the commits touching stuff
>>>>> there. I guess if the issue is more broad it will come up somewhere
>>>>> else as well, so this is a good starting point, I hope. Thank you for
>>>>> pointing it out though, this will actually be the first time I do a
>>>>> proper bisect.
>>>>
>>>> And remember to always to mention if you have restricted the bisect
>>>> somehow, that's important information. And better if you provide 'git
>>>> bisect log' output as well.
>>>>
>>>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>>>> what Michał said I guess Kalle's but I ask to be sure.
>>>>>
>>>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>>>> by Fedora rawhide.
>>>>>
>>>>> For me it's the same, so let me know what you prefer and is more
>>>>> useful to solve this issue.
>>>>
>>>> Good that you brought this up. As ath.git master branch gets rebased
>>>> every rc1 release you really cannot use that for bisect. Either you
>>>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>>>> side I always recommend to use Linus' tree if at all possible.
>>>>
>>>> --
>>>> Kalle Valo

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi there,

it's been a while, but I have good news: tried Kernel 4.2.3 from
Fedora and it just works! No need to use irq_mode=1 (and I also
removed skip_opt), tested with firmware API 5 from ath10k-firmware
since a couple of days now. No issue so far.

Thank you for the help and the work, and sorry for not being very
useful in investigating this eheheh.

Cheers!
Enrico

On 8 September 2015 at 10:17, Enrico Tagliavini
<enrico.tagliavini@gmail.com> wrote:
> Hi there,
>
> sorry for the late and still no results. Life never goes as planned
> does it? I will still try to find the time to bisect this, however I
> cannot foresee when this might happen. If anybody has urgency to fix
> this might as well bisecting instead of waiting for me. My apologize
> :(
>
> Best regards.
> Enrico
>
> On 5 August 2015 at 19:52, Enrico Tagliavini
> <enrico.tagliavini@gmail.com> wrote:
>> Bisect is done, unfortunately I think there is no good news
>>
>> $ git bisect log
>> git bisect start '--' 'drivers/net/wireless/ath/ath10k/'
>> # bad: [86ea07ca846a7c352f39dd0b7d81f15f403c7db8] Merge branch
>> 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
>> git bisect bad 86ea07ca846a7c352f39dd0b7d81f15f403c7db8
>> # good: [b953c0d234bc72e8489d3bf51a276c5c4ec85345] Linux 4.1
>> git bisect good b953c0d234bc72e8489d3bf51a276c5c4ec85345
>> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
>> wait_for_completion_timeout return type
>> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
>> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
>> wait_for_completion_timeout return type
>> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
>> # good: [0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0] ath10k: enable ibss-rsn
>> git bisect good 0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0
>> # good: [48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6] ath10k: add new
>> 4addr related fw_feature
>> git bisect good 48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6
>> # good: [163f52647a0f7e34e803b51456c60deedd26ca1d] ath10k: bypass PLL
>> setting on target init for QCA9888
>> git bisect good 163f52647a0f7e34e803b51456c60deedd26ca1d
>> # good: [d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9] ath10k: fix
>> ar->rx_channel updating logic
>> git bisect good d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9
>> # good: [0e6eb417fc1facda1c9a9189be85f16cb5b8b69f] ath10k: fix channel switching
>> git bisect good 0e6eb417fc1facda1c9a9189be85f16cb5b8b69f
>> # good: [30686bf7f5b3c30831761e188a6e3cb33580fa48] mac80211: convert
>> HW flags to unsigned long bitmap
>> git bisect good 30686bf7f5b3c30831761e188a6e3cb33580fa48
>> # good: [469d479f91b8277cc921d7525f31c832b25d9efb] ath10k: prevent
>> memory leak in wmi rx ops
>> git bisect good 469d479f91b8277cc921d7525f31c832b25d9efb
>> # good: [fa433354f042105fc7a299253f904bb48dae0950] Merge tag
>> 'wireless-drivers-next-for-davem-2015-06-18' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
>> git bisect good fa433354f042105fc7a299253f904bb48dae0950
>>
>> as you can see I tried to restrict the bisect to the ath10k folder
>> only and none of the commit was faulty. Probably because all the
>> commit were actually still on kernel 4.1 rc, none of them was on 4.2
>> except the starting bad one (which was the latest when I cloned the
>> repo for rc4).
>>
>> So I guess we are switching to plan B here and bisecting the entire
>> tree right? If so, starting from the same bad commit as for this one
>> and using the newest good commit I tested (so last entry in the bisect
>> I just did)
>>
>> $ git bisect good fa433354f042105fc7a299253f904bb48dae0950
>> Bisecting: 6373 revisions left to test after this (roughly 13 steps)
>> [4aa705b18bf17c4ff33ff7bbcd3f0c596443fa81] Merge tag 'armsoc-soc' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
>>
>> 13 steps are not crazy.... sigh. Give me enough days, in the weekend
>> I'll be on the road the I'll see if I can get few quiet hours to get
>> this done.
>>
>> Any last minute advise or question before I reset this bisect?
>>
>> On 1 August 2015 at 14:30, Enrico Tagliavini
>> <enrico.tagliavini@gmail.com> wrote:
>>> Hi there,
>>>
>>> I got 4.2 rc4 running and I'm going to start the bisect. Before
>>> compiling I enabled ath10k debug and this is the output for with
>>> default irq_mode:
>>>
>>> enrico@alientux ~ $ dmesg | grep ath
>>> [   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>>> [   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
>>> [   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>>> irq_mode 0 reset_mode 0
>>> [   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>>> [   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
>>> [   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
>>> [   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
>>> [   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
>>> [   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>>> [   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
>>> [   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>>> [   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
>>> [   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
>>> [   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
>>> [   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
>>> [   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>>> [   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
>>> [   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
>>> version 0x5010000
>>> [   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>>> [   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
>>> error -2
>>> [   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
>>> file, falling back to generic: -2
>>> [   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
>>> [   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>>> [   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
>>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>>> [   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
>>> [   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
>>> [   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
>>> [   16.384385] ath10k_pci 0000:03:00.0: features
>>> [   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
>>> 00                          ........
>>> [   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
>>> [   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
>>> [   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
>>> [   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
>>> [   16.384394] ath10k_pci 0000:03:00.0: bmi start
>>> [   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
>>> [   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
>>> [   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
>>> [   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
>>> [   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
>>> [   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
>>> calibration file, try DT next: -2
>>> [   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
>>> try OTP next: -2
>>> [   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
>>> [   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
>>> [   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
>>> [   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
>>> [   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
>>> [   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
>>> [   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
>>> 0x1234 buffer 0xffffc9000166f64c length 29533
>>> [   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>>> [   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffffc9000166f64c length 29532
>>> [   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffff8800c4763d2c length 4
>>> [   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>>> [   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
>>> [   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
>>> [   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
>>> [   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
>>> [   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
>>> ffffc900015fe044 len 464383 mode normal
>>> [   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
>>> 0x1234 buffer 0xffffc900015fe044 length 464383
>>> [   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>>> [   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffffc900015fe044 length 464380
>>> [   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffff8800c4763d2c length 4
>>> [   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>>> [   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
>>> [   17.548871] ath10k_pci 0000:03:00.0: bmi done
>>> [   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
>>> [   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
>>> [   17.548923] ath10k_pci 0000:03:00.0: boot hif start
>>> [   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
>>> response completion, polling..
>>> [   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
>>> pipe 0 dl pipe 1 eid 0 ready
>>> [   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
>>> [   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
>>> 0 TX flow control disabled
>>> [   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
>>> not allocate target credits
>>> [   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
>>> [   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
>>> [   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
>>> [   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
>>> [   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
>>> [   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
>>> [   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
>>> [   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>>>
>>> Maybe this trigger some bell.
>>>
>>> On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>>>> Sound! I'll keep a copy of the log then. If the bisect on ath10k
>>>> folder will lead nowhere I'll see if I can make it over the whole
>>>> tree. At least by doing it on the ath10k tree I hope to narrow down
>>>> the number of commit.
>>>>
>>>> Ok then I'll use Linus' master, no problem with this.
>>>>
>>>> I hope to at least get started this weekend.
>>>>
>>>> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>>>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>>>>
>>>>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>>>>> directory, so restricting the bisect on the commits touching stuff
>>>>>> there. I guess if the issue is more broad it will come up somewhere
>>>>>> else as well, so this is a good starting point, I hope. Thank you for
>>>>>> pointing it out though, this will actually be the first time I do a
>>>>>> proper bisect.
>>>>>
>>>>> And remember to always to mention if you have restricted the bisect
>>>>> somehow, that's important information. And better if you provide 'git
>>>>> bisect log' output as well.
>>>>>
>>>>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>>>>> what Michał said I guess Kalle's but I ask to be sure.
>>>>>>
>>>>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>>>>> by Fedora rawhide.
>>>>>>
>>>>>> For me it's the same, so let me know what you prefer and is more
>>>>>> useful to solve this issue.
>>>>>
>>>>> Good that you brought this up. As ath.git master branch gets rebased
>>>>> every rc1 release you really cannot use that for bisect. Either you
>>>>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>>>>> side I always recommend to use Linus' tree if at all possible.
>>>>>
>>>>> --
>>>>> Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: QCA6174 hw2.1 irq_mode=0 broken on 4.2-rc3, working on 4.1.2

[Enrico Tagliavini]

Hi there,

it's been a while, but I have good news: tried Kernel 4.2.3 from
Fedora and it just works! No need to use irq_mode=1 (and I also
removed skip_opt), tested with firmware API 5 from ath10k-firmware
since a couple of days now. No issue so far.

Thank you for the help and the work, and sorry for not being very
useful in investigating this eheheh.

Cheers!
Enrico

On 8 September 2015 at 10:17, Enrico Tagliavini
<enrico.tagliavini@gmail.com> wrote:
> Hi there,
>
> sorry for the late and still no results. Life never goes as planned
> does it? I will still try to find the time to bisect this, however I
> cannot foresee when this might happen. If anybody has urgency to fix
> this might as well bisecting instead of waiting for me. My apologize
> :(
>
> Best regards.
> Enrico
>
> On 5 August 2015 at 19:52, Enrico Tagliavini
> <enrico.tagliavini@gmail.com> wrote:
>> Bisect is done, unfortunately I think there is no good news
>>
>> $ git bisect log
>> git bisect start '--' 'drivers/net/wireless/ath/ath10k/'
>> # bad: [86ea07ca846a7c352f39dd0b7d81f15f403c7db8] Merge branch
>> 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux
>> git bisect bad 86ea07ca846a7c352f39dd0b7d81f15f403c7db8
>> # good: [b953c0d234bc72e8489d3bf51a276c5c4ec85345] Linux 4.1
>> git bisect good b953c0d234bc72e8489d3bf51a276c5c4ec85345
>> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
>> wait_for_completion_timeout return type
>> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
>> # good: [8e9904f5b9e5e0a126020211218c401d601ef74b] ath10k: mac: match
>> wait_for_completion_timeout return type
>> git bisect good 8e9904f5b9e5e0a126020211218c401d601ef74b
>> # good: [0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0] ath10k: enable ibss-rsn
>> git bisect good 0cd9bc147f0b8d805972cbb4b7b5e5529f9624e0
>> # good: [48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6] ath10k: add new
>> 4addr related fw_feature
>> git bisect good 48f4ca34f36bb947d8a7cd4ff8c8e282f14d51e6
>> # good: [163f52647a0f7e34e803b51456c60deedd26ca1d] ath10k: bypass PLL
>> setting on target init for QCA9888
>> git bisect good 163f52647a0f7e34e803b51456c60deedd26ca1d
>> # good: [d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9] ath10k: fix
>> ar->rx_channel updating logic
>> git bisect good d7bf4b4aba056f3e7eb88a3d8d45ee1a6f4873e9
>> # good: [0e6eb417fc1facda1c9a9189be85f16cb5b8b69f] ath10k: fix channel switching
>> git bisect good 0e6eb417fc1facda1c9a9189be85f16cb5b8b69f
>> # good: [30686bf7f5b3c30831761e188a6e3cb33580fa48] mac80211: convert
>> HW flags to unsigned long bitmap
>> git bisect good 30686bf7f5b3c30831761e188a6e3cb33580fa48
>> # good: [469d479f91b8277cc921d7525f31c832b25d9efb] ath10k: prevent
>> memory leak in wmi rx ops
>> git bisect good 469d479f91b8277cc921d7525f31c832b25d9efb
>> # good: [fa433354f042105fc7a299253f904bb48dae0950] Merge tag
>> 'wireless-drivers-next-for-davem-2015-06-18' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next
>> git bisect good fa433354f042105fc7a299253f904bb48dae0950
>>
>> as you can see I tried to restrict the bisect to the ath10k folder
>> only and none of the commit was faulty. Probably because all the
>> commit were actually still on kernel 4.1 rc, none of them was on 4.2
>> except the starting bad one (which was the latest when I cloned the
>> repo for rc4).
>>
>> So I guess we are switching to plan B here and bisecting the entire
>> tree right? If so, starting from the same bad commit as for this one
>> and using the newest good commit I tested (so last entry in the bisect
>> I just did)
>>
>> $ git bisect good fa433354f042105fc7a299253f904bb48dae0950
>> Bisecting: 6373 revisions left to test after this (roughly 13 steps)
>> [4aa705b18bf17c4ff33ff7bbcd3f0c596443fa81] Merge tag 'armsoc-soc' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
>>
>> 13 steps are not crazy.... sigh. Give me enough days, in the weekend
>> I'll be on the road the I'll see if I can get few quiet hours to get
>> this done.
>>
>> Any last minute advise or question before I reset this bisect?
>>
>> On 1 August 2015 at 14:30, Enrico Tagliavini
>> <enrico.tagliavini@gmail.com> wrote:
>>> Hi there,
>>>
>>> I got 4.2 rc4 running and I'm going to start the bisect. Before
>>> compiling I enabled ath10k debug and this is the output for with
>>> default irq_mode:
>>>
>>> enrico@alientux ~ $ dmesg | grep ath
>>> [   16.234853] ath10k_pci 0000:03:00.0: enabling device (0000 -> 0002)
>>> [   16.234979] ath10k_pci 0000:03:00.0: boot pci_mem 0xffffc90002000000
>>> [   16.235351] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8
>>> irq_mode 0 reset_mode 0
>>> [   16.235517] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>>> [   16.235518] ath10k_pci 0000:03:00.0: boot cold reset
>>> [   16.239030] ath10k_pci 0000:03:00.0: boot cold reset complete
>>> [   16.239032] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.239037] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.249046] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.249055] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.249057] ath10k_pci 0000:03:00.0: boot warm reset
>>> [   16.271106] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.271128] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.271146] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.271166] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.271187] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.271207] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.271223] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.271224] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.271229] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.281316] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.281373] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.292100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.292169] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.292186] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.292206] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.292228] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.292248] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.292265] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.292267] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.292272] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.302326] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.302335] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.302336] ath10k_pci 0000:03:00.0: boot warm reset complete
>>> [   16.302337] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>>> [   16.302350] ath10k_pci 0000:03:00.0: boot hif power up
>>> [   16.302408] ath10k_pci 0000:03:00.0: boot qca6174 chip reset
>>> [   16.302409] ath10k_pci 0000:03:00.0: boot cold reset
>>> [   16.306030] ath10k_pci 0000:03:00.0: boot cold reset complete
>>> [   16.306033] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.306037] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.316044] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.316056] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.316057] ath10k_pci 0000:03:00.0: boot warm reset
>>> [   16.338057] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.338075] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.338092] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.338111] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.338132] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.338152] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.338169] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.338169] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.338174] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.348187] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.348196] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.359038] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.359055] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.359072] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.359092] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.359113] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.359133] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.359149] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.359150] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   16.359155] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   16.369166] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   16.369174] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   16.369175] ath10k_pci 0000:03:00.0: boot warm reset complete
>>> [   16.369175] ath10k_pci 0000:03:00.0: boot qca6174 chip reset complete (cold)
>>> [   16.369195] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   16.369212] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   16.369228] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   16.369248] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   16.369268] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   16.369288] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   16.369304] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   16.380484] ath10k_pci 0000:03:00.0: bmi get target info
>>> [   16.380731] ath10k_pci 0000:03:00.0: Hardware name qca6174 hw2.1
>>> version 0x5010000
>>> [   16.381072] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
>>> [   16.382103] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
>>> error -2
>>> [   16.382107] ath10k_pci 0000:03:00.0: failed to load spec board
>>> file, falling back to generic: -2
>>> [   16.383013] ath10k_pci 0000:03:00.0: trying fw api 5
>>> [   16.383028] ath10k_pci 0000:03:00.0: Direct firmware load for
>>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>>> [   16.383030] ath10k_pci 0000:03:00.0: could not fetch firmware file
>>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>>> [   16.383032] ath10k_pci 0000:03:00.0: trying fw api 4
>>> [   16.384382] ath10k_pci 0000:03:00.0: found fw version killer-n1525-fw
>>> [   16.384384] ath10k_pci 0000:03:00.0: found firmware features ie (4 B)
>>> [   16.384385] ath10k_pci 0000:03:00.0: features
>>> [   16.384387] ath10k_pci 0000:03:00.0: 00000000: 00 00 00 00 00 00 00
>>> 00                          ........
>>> [   16.384388] ath10k_pci 0000:03:00.0: found fw ie wmi op version 4
>>> [   16.384390] ath10k_pci 0000:03:00.0: found fw image ie (464383 B)
>>> [   16.384391] ath10k_pci 0000:03:00.0: found otp image ie (29533 B)
>>> [   16.384392] ath10k_pci 0000:03:00.0: using fw api 4
>>> [   16.384394] ath10k_pci 0000:03:00.0: bmi start
>>> [   16.384395] ath10k_pci 0000:03:00.0: bmi write address 0x400800 length 4
>>> [   16.384414] ath10k_pci 0000:03:00.0: bmi read address 0x400810 length 4
>>> [   16.384497] ath10k_pci 0000:03:00.0: bmi write address 0x400810 length 4
>>> [   16.384507] ath10k_pci 0000:03:00.0: bmi write address 0x400844 length 4
>>> [   16.384556] ath10k_pci 0000:03:00.0: bmi write address 0x400904 length 4
>>> [   16.384598] ath10k_pci 0000:03:00.0: boot did not find a
>>> calibration file, try DT next: -2
>>> [   16.384600] ath10k_pci 0000:03:00.0: boot did not find DT entry,
>>> try OTP next: -2
>>> [   16.384601] ath10k_pci 0000:03:00.0: bmi read address 0x4008ac length 4
>>> [   16.384678] ath10k_pci 0000:03:00.0: boot push board extended data addr 0x0
>>> [   16.384679] ath10k_pci 0000:03:00.0: bmi read address 0x400854 length 4
>>> [   16.384732] ath10k_pci 0000:03:00.0: bmi write address 0x401d40 length 8124
>>> [   16.400967] ath10k_pci 0000:03:00.0: bmi write address 0x400858 length 4
>>> [   16.401133] ath10k_pci 0000:03:00.0: boot upload otp to 0x1234 len 29533
>>> [   16.401134] ath10k_pci 0000:03:00.0: bmi fast download address
>>> 0x1234 buffer 0xffffc9000166f64c length 29533
>>> [   16.401135] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>>> [   16.401173] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffffc9000166f64c length 29532
>>> [   16.463523] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffff8800c4763d2c length 4
>>> [   16.463602] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>>> [   16.463647] ath10k_pci 0000:03:00.0: bmi execute address 0x1234 param 0x0
>>> [   16.465226] ath10k_pci 0000:03:00.0: bmi execute result 0x3
>>> [   16.465231] ath10k_pci 0000:03:00.0: boot otp execute result 3
>>> [   16.465232] ath10k_pci 0000:03:00.0: boot using calibration mode otp
>>> [   16.465234] ath10k_pci 0000:03:00.0: boot uploading firmware image
>>> ffffc900015fe044 len 464383 mode normal
>>> [   16.465235] ath10k_pci 0000:03:00.0: bmi fast download address
>>> 0x1234 buffer 0xffffc900015fe044 length 464383
>>> [   16.465237] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x1234
>>> [   16.465257] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffffc900015fe044 length 464380
>>> [   17.548533] ath10k_pci 0000:03:00.0: bmi lz data buffer
>>> 0xffff8800c4763d2c length 4
>>> [   17.548792] ath10k_pci 0000:03:00.0: bmi lz stream start address 0x0
>>> [   17.548837] ath10k_pci 0000:03:00.0: bmi write address 0x400814 length 4
>>> [   17.548871] ath10k_pci 0000:03:00.0: bmi done
>>> [   17.548913] ath10k_pci 0000:03:00.0: htt tx max num pending tx 1056
>>> [   17.548922] ath10k_pci 0000:03:00.0: htt rx ring size 2048 fill_level 1023
>>> [   17.548923] ath10k_pci 0000:03:00.0: boot hif start
>>> [   17.548959] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   17.548981] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   18.549028] ath10k_pci 0000:03:00.0: failed to receive control
>>> response completion, polling..
>>> [   18.549192] ath10k_pci 0000:03:00.0: boot htc service 'Control' ul
>>> pipe 0 dl pipe 1 eid 0 ready
>>> [   18.549193] ath10k_pci 0000:03:00.0: boot htc ep 0 ul polled 0 dl polled 0
>>> [   18.549194] ath10k_pci 0000:03:00.0: boot htc service 'Control' eid
>>> 0 TX flow control disabled
>>> [   18.549195] ath10k_pci 0000:03:00.0: boot htc service HTT Data does
>>> not allocate target credits
>>> [   18.549280] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   18.549294] ath10k_pci 0000:03:00.0: received unsolicited fw crash interrupt
>>> [   19.549038] ath10k_pci 0000:03:00.0: Service connect timeout
>>> [   19.549042] ath10k_pci 0000:03:00.0: failed to connect htt (-110)
>>> [   19.549044] ath10k_pci 0000:03:00.0: boot hif stop
>>> [   19.549045] ath10k_pci 0000:03:00.0: boot warm reset
>>> [   19.571100] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   19.571117] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   19.571133] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   19.571153] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   19.571172] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   19.571190] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   19.571206] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   19.571207] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   19.571212] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   19.581273] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   19.581282] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   19.592126] ath10k_pci 0000:03:00.0: boot init ce src ring id 0
>>> entries 16 base_addr ffff88003f00a000
>>> [   19.592202] ath10k_pci 0000:03:00.0: boot ce dest ring id 1 entries
>>> 512 base_addr ffff88003f3c8000
>>> [   19.592222] ath10k_pci 0000:03:00.0: boot ce dest ring id 2 entries
>>> 128 base_addr ffff88003eb6a000
>>> [   19.592245] ath10k_pci 0000:03:00.0: boot init ce src ring id 3
>>> entries 32 base_addr ffff88003f349000
>>> [   19.592269] ath10k_pci 0000:03:00.0: boot init ce src ring id 4
>>> entries 4096 base_addr ffff8800ba940000
>>> [   19.592294] ath10k_pci 0000:03:00.0: boot init ce src ring id 7
>>> entries 2 base_addr ffff8800c4888000
>>> [   19.592314] ath10k_pci 0000:03:00.0: boot ce dest ring id 7 entries
>>> 2 base_addr ffff8800ba889000
>>> [   19.592316] ath10k_pci 0000:03:00.0: boot waiting target to initialise
>>> [   19.592321] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   19.602378] ath10k_pci 0000:03:00.0: boot target indicator 0
>>> [   19.612445] ath10k_pci 0000:03:00.0: boot target indicator 2
>>> [   19.612455] ath10k_pci 0000:03:00.0: boot target initialised
>>> [   19.612456] ath10k_pci 0000:03:00.0: boot warm reset complete
>>> [   19.612779] ath10k_pci 0000:03:00.0: could not init core (-110)
>>> [   19.612810] ath10k_pci 0000:03:00.0: boot hif power down
>>> [   19.612811] ath10k_pci 0000:03:00.0: could not probe fw (-110)
>>>
>>> Maybe this trigger some bell.
>>>
>>> On 29 July 2015 at 16:22, Enrico Tagliavini <enrico.tagliavini@gmail.com> wrote:
>>>> Sound! I'll keep a copy of the log then. If the bisect on ath10k
>>>> folder will lead nowhere I'll see if I can make it over the whole
>>>> tree. At least by doing it on the ath10k tree I hope to narrow down
>>>> the number of commit.
>>>>
>>>> Ok then I'll use Linus' master, no problem with this.
>>>>
>>>> I hope to at least get started this weekend.
>>>>
>>>> On 29 July 2015 at 11:30, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>>>> Enrico Tagliavini <enrico.tagliavini@gmail.com> writes:
>>>>>
>>>>>> Yeah that's what I meant. My idea was to first bisect only the ath10k
>>>>>> directory, so restricting the bisect on the commits touching stuff
>>>>>> there. I guess if the issue is more broad it will come up somewhere
>>>>>> else as well, so this is a good starting point, I hope. Thank you for
>>>>>> pointing it out though, this will actually be the first time I do a
>>>>>> proper bisect.
>>>>>
>>>>> And remember to always to mention if you have restricted the bisect
>>>>> somehow, that's important information. And better if you provide 'git
>>>>> bisect log' output as well.
>>>>>
>>>>>> Also do you want me to bisect Kalle's sources or Linus' master? By
>>>>>> what Michał said I guess Kalle's but I ask to be sure.
>>>>>>
>>>>>> Also to be clear: I'm using Linus' sources at the moment, as provided
>>>>>> by Fedora rawhide.
>>>>>>
>>>>>> For me it's the same, so let me know what you prefer and is more
>>>>>> useful to solve this issue.
>>>>>
>>>>> Good that you brought this up. As ath.git master branch gets rebased
>>>>> every rc1 release you really cannot use that for bisect. Either you
>>>>> should use ath.git ath-next branch or Linus' tree. To be on the safe
>>>>> side I always recommend to use Linus' tree if at all possible.
>>>>>
>>>>> --
>>>>> Kalle Valo