Hi,
I am trying to use ath10k driver from the latest backports-4.4-rc.2-1 with
kernel 3.10.65 and qca6174 based wlan module. Could you give me some hints
about possible problem.
ath10k_core.ko module loaded with skip_otp=y and debug_mask=0xffffffff.
I get following error message:
[ 5301.614749] ath10k_pci 0000:01:00.0: wmi unified ready event not
received
[ 5301.614749] ath10k_pci 0000:01:00.0: device has crashed during init
[ 5301.644767] ath10k_pci 0000:01:00.0: device has crashed during init
[ 5301.651025] ath10k_pci 0000:01:00.0: failed to wait for target init: -70
[ 5301.661134] ath10k_pci 0000:01:00.0: could not init core (-110)
[ 5301.667310] ath10k_pci 0000:01:00.0: could not probe fw (-110)
Some other important debug messages (I can also provide the whole log if
needed):
ath10k_pci 0000:01:00.0: found fw version WLAN.RM.2.0-00180-QCARMSWPZ-1
[...]
ath10k_pci 0000:01:00.0: boot get otp board id result 0x00000001 board_id 0
chip_id 0
ath10k_pci 0000:01:00.0: boot using board name
'bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-
device=0000'
[...]
ath10k_pci 0000:01:00.0: Target ready! transmit resources: 2 size:1792
[...]
ath10k_pci 0000:01:00.0: HTC Service HTT Data connect response: status:
0x0, assigned ep: 0x1
[...]
ath10k_pci 0000:01:00.0: HTC Service WMI connect response: status: 0x0,
assigned ep: 0x2
[...]
ath10k_pci 0000:01:00.0: wmi event service ready min_tx_power 0x0000003f
max_tx_power 0x0000003f ht_cap 0x0000085b vht_cap 0x339011b2 sw_ver0
0x01000000 sw_ver1 0x0000008f fw_build 0x200700b4 phy_capab 0x00000003
num_rf_chains 0x00000002 eeprom_rd 0x00000000 num_mem_reqs 0x00000000
ath10k_pci 0000:01:00.0: firmware WLAN.RM.2.0-00180-QCARMSWPZ-1 booted
[...]
ath10k_pci 0000:01:00.0: ath10k_htc_notify_tx_completion: ep 2 skb 8cc3b6c0
ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
ath10k_pci 0000:01:00.0: wmi unified ready event not received
ath10k_pci 0000:01:00.0: boot hif stop
[...]
ath10k_pci 0000:01:00.0: boot init ce src ring id 0 entries 16 base_addr
8e053000
ath10k_pci 0000:01:00.0: boot ce dest ring id 1 entries 512 base_addr
8e054000
ath10k_pci 0000:01:00.0: boot ce dest ring id 2 entries 128 base_addr
8e056000
ath10k_pci 0000:01:00.0: boot init ce src ring id 3 entries 32 base_addr
8e057000
ath10k_pci 0000:01:00.0: boot init ce src ring id 4 entries 4096 base_addr
8e060000
ath10k_pci 0000:01:00.0: boot ce dest ring id 5 entries 512 base_addr
8e058000
ath10k_pci 0000:01:00.0: boot init ce src ring id 7 entries 2 base_addr
8e05a000
ath10k_pci 0000:01:00.0: boot ce dest ring id 7 entries 2 base_addr
8e05b000
ath10k_pci 0000:01:00.0: boot waiting target to initialise
ath10k_pci 0000:01:00.0: boot target indicator 0
ath10k_pci 0000:01:00.0: boot target indicator 1
ath10k_pci 0000:01:00.0: device has crashed during init
ath10k_pci 0000:01:00.0: failed to wait for target init: -70
ath10k_pci 0000:01:00.0: could not init core (-110)
ath10k_pci 0000:01:00.0: boot hif power down
ath10k_pci 0000:01:00.0: could not probe fw (-110)
ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
Thank you
Bartek
Hi,
I have already tried with backports 4.2.6 and different combinations
of firmware.bin / board.bin. With differnt results, but none of them
works. I will redo the tests and summarize them.
Loading with irq_mode=1 gives me following result:
[55416.824364] ath10k_pci 0000:01:00.0: limiting irq mode to: 1
[55416.830102] ath10k_pci 0000:01:00.0: pci irq legacy interrupts 0
irq_mode 1 reset_mode 0
[55417.212048] ath10k_pci 0000:01:00.0: could not fetch firmware file
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[55424.394422] ath10k_pci 0000:01:00.0: wmi unified ready event not received
[55424.436023] ath10k_pci 0000:01:00.0: firmware crashed! (uuid
e082ac60-7c2d-4d14-9c49-fd5b0591c95c)
[55424.445008] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000,
0x00340aff sub 0000:0000) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4
bdapi 1 htt-ver 0.0 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad
[55424.466652] ath10k_pci 0000:01:00.0: debug 1 debugfs 1 tracing 0
dfs 0 testmode 0
[55424.476163] ath10k_pci 0000:01:00.0: firmware register dump:
[55424.481817] ath10k_pci 0000:01:00.0: [00]: 0x05030000 0x00000000
0x80914913 0x00000058
[55424.489740] ath10k_pci 0000:01:00.0: [04]: 0x80914913 0x0040EAB8
0x80000000 0x00000000
[55424.497661] ath10k_pci 0000:01:00.0: [08]: 0x80000000 0x00404070
0x00000000 0x00000010
[55424.505582] ath10k_pci 0000:01:00.0: [12]: 0x8091071F 0x0040EA88
0x00060523 0x00910940
[55424.513491] ath10k_pci 0000:01:00.0: [16]: 0x00002580 0x00000004
0x00000000 0x00952A00
[55424.521411] ath10k_pci 0000:01:00.0: [20]: 0x8091097C 0x0040EAE8
0x00400000 0x004117E0
[55424.529333] ath10k_pci 0000:01:00.0: [24]: 0x00000800 0x004117E0
0xFFFFFFFB 0x0091810C
[55424.537253] ath10k_pci 0000:01:00.0: [28]: 0x80914540 0x0040EAC8
0x0000001F 0x00400000
[55424.545174] ath10k_pci 0000:01:00.0: [32]: 0x00000000 0x00400000
0x00400000 0x004111B8
[55424.553082] ath10k_pci 0000:01:00.0: [36]: 0x00000000 0x00000000
0x00000000 0x00000000
[55424.561002] ath10k_pci 0000:01:00.0: [40]: 0x00000000 0x00000000
0x00000000 0x00000000
[55424.568922] ath10k_pci 0000:01:00.0: [44]: 0x00000000 0x00000000
0x00000000 0x00000000
[55424.576842] ath10k_pci 0000:01:00.0: [48]: 0x00000000 0x00000000
0x00000000 0x00000000
[55424.584763] ath10k_pci 0000:01:00.0: [52]: 0x00000000 0x00000000
0x00000000 0x00000000
[55424.592671] ath10k_pci 0000:01:00.0: [56]: 0x00000000 0x00000000
0x00000000 0x00000000
[55427.439381] ath10k_pci 0000:01:00.0: failed to receive initialized
event from target: 00000000
[55427.467842] ath10k_pci 0000:01:00.0: firmware crashed! (uuid
6b37f354-65c8-4c76-a0ff-694f67a9d731)
[55427.476825] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000,
0x00340aff sub 0000:0000) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4
bdapi 1 htt-ver 0.0 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0
hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad
[55427.498468] ath10k_pci 0000:01:00.0: debug 1 debugfs 1 tracing 0
dfs 0 testmode 0
[55427.507975] ath10k_pci 0000:01:00.0: firmware register dump:
[55427.513628] ath10k_pci 0000:01:00.0: [00]: 0x05030000 0x00000000
0x80914913 0x00000058
[55427.521551] ath10k_pci 0000:01:00.0: [04]: 0x80914913 0x0040EAB8
0x80000000 0x00000000
[55427.529473] ath10k_pci 0000:01:00.0: [08]: 0x80000000 0x00404070
0x00000000 0x00000010
[55427.537395] ath10k_pci 0000:01:00.0: [12]: 0x8091071F 0x0040EA88
0x00060523 0x00910940
[55427.545316] ath10k_pci 0000:01:00.0: [16]: 0x00002580 0x00000004
0x00000000 0x00952A00
[55427.553225] ath10k_pci 0000:01:00.0: [20]: 0x8091097C 0x0040EAE8
0x00400000 0x004117E0
[55427.561145] ath10k_pci 0000:01:00.0: [24]: 0x00000800 0x004117E0
0xFFFFFFFB 0x0091810C
[55427.569066] ath10k_pci 0000:01:00.0: [28]: 0x80914540 0x0040EAC8
0x0000001F 0x00400000
[55427.576987] ath10k_pci 0000:01:00.0: [32]: 0x00000000 0x00400000
0x00400000 0x004111B8
[55427.584907] ath10k_pci 0000:01:00.0: [36]: 0x00000000 0x00000000
0x00000000 0x00000000
[55427.592816] ath10k_pci 0000:01:00.0: [40]: 0x00000000 0x00000000
0x00000000 0x00000000
[55427.600736] ath10k_pci 0000:01:00.0: [44]: 0x00000000 0x00000000
0x00000000 0x00000000
[55427.608657] ath10k_pci 0000:01:00.0: [48]: 0x00000000 0x00000000
0x00000000 0x00000000
[55427.616578] ath10k_pci 0000:01:00.0: [52]: 0x00000000 0x00000000
0x00000000 0x00000000
[55427.624498] ath10k_pci 0000:01:00.0: [56]: 0x00000000 0x00000000
0x00000000 0x00000000
[55430.470669] ath10k_pci 0000:01:00.0: failed to receive initialized
event from target: 00000000
[55430.479287] ath10k_pci 0000:01:00.0: failed to wait for target init: -110
[55430.489524] ath10k_pci 0000:01:00.0: could not init core (-110)
[55430.495709] ath10k_pci 0000:01:00.0: could not probe fw (-110)
[55430.534414] ath10k_pci 0000:01:00.0: cannot restart a device that
hasn't been started
2015-12-01 9:26 GMT+01:00 Michal Kazior <[email protected]>:
> On 1 December 2015 at 09:13, Bartlomiej Grzeskowiak
> <[email protected]> wrote:
>> Hi,
>>
>> Unfortunately I do have this patch in my code (backports-4.4-rc.2-1).
>> I have also tested the old reg_address/mask value (0x00009028) but the
>> result is the same.
>
> The problem actually looks a little different. The mentioned patch
> fixed a problem which would occur during early device init/probing.
> Your problem seems to occur while booting and configuring firmware.
>
> Did you try using older backports, firmware and/or board/board-2.bin
> files? This could be some sort of regression you're seeing with the
> exact combination you're testing.
>
> You could also try loading ath10k_pci with irq_mode=1.
>
>
> Michal
Hi,
Unfortunately I do have this patch in my code (backports-4.4-rc.2-1).
I have also tested the old reg_address/mask value (0x00009028) but the
result is the same.
BR,
Bartek
2015-12-01 7:26 GMT+01:00 Janusz Dziedzic <[email protected]>:
> On 1 December 2015 at 07:20, Bartlomiej Grzeskowiak
> <[email protected]> wrote:
>> Hi,
>>
>> I am trying to use ath10k driver from the latest backports-4.4-rc.2-1 with
>> kernel 3.10.65 and qca6174 based wlan module. Could you give me some hints
>> about possible problem.
>> ath10k_core.ko module loaded with skip_otp=y and debug_mask=0xffffffff.
>>
>> I get following error message:
>> [ 5301.614749] ath10k_pci 0000:01:00.0: wmi unified ready event not
>> received
>> [ 5301.614749] ath10k_pci 0000:01:00.0: device has crashed during init
> Seems Bartosz already fix this in this patch:
> [PATCH] ath10k: fix QCA61X4 boot up
>
> BR
> Janusz
>
>> [ 5301.644767] ath10k_pci 0000:01:00.0: device has crashed during init
>> [ 5301.651025] ath10k_pci 0000:01:00.0: failed to wait for target init: -70
>> [ 5301.661134] ath10k_pci 0000:01:00.0: could not init core (-110)
>> [ 5301.667310] ath10k_pci 0000:01:00.0: could not probe fw (-110)
>>
>> Some other important debug messages (I can also provide the whole log if
>> needed):
>> ath10k_pci 0000:01:00.0: found fw version WLAN.RM.2.0-00180-QCARMSWPZ-1
>> [...]
>> ath10k_pci 0000:01:00.0: boot get otp board id result 0x00000001 board_id 0
>> chip_id 0
>> ath10k_pci 0000:01:00.0: boot using board name
>> 'bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-
>> device=0000'
>> [...]
>> ath10k_pci 0000:01:00.0: Target ready! transmit resources: 2 size:1792
>> [...]
>> ath10k_pci 0000:01:00.0: HTC Service HTT Data connect response: status:
>> 0x0, assigned ep: 0x1
>> [...]
>> ath10k_pci 0000:01:00.0: HTC Service WMI connect response: status: 0x0,
>> assigned ep: 0x2
>> [...]
>> ath10k_pci 0000:01:00.0: wmi event service ready min_tx_power 0x0000003f
>> max_tx_power 0x0000003f ht_cap 0x0000085b vht_cap 0x339011b2 sw_ver0
>> 0x01000000 sw_ver1 0x0000008f fw_build 0x200700b4 phy_capab 0x00000003
>> num_rf_chains 0x00000002 eeprom_rd 0x00000000 num_mem_reqs 0x00000000
>> ath10k_pci 0000:01:00.0: firmware WLAN.RM.2.0-00180-QCARMSWPZ-1 booted
>> [...]
>> ath10k_pci 0000:01:00.0: ath10k_htc_notify_tx_completion: ep 2 skb 8cc3b6c0
>> ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
>> ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
>> ath10k_pci 0000:01:00.0: wmi unified ready event not received
>> ath10k_pci 0000:01:00.0: boot hif stop
>> [...]
>> ath10k_pci 0000:01:00.0: boot init ce src ring id 0 entries 16 base_addr
>> 8e053000
>> ath10k_pci 0000:01:00.0: boot ce dest ring id 1 entries 512 base_addr
>> 8e054000
>> ath10k_pci 0000:01:00.0: boot ce dest ring id 2 entries 128 base_addr
>> 8e056000
>> ath10k_pci 0000:01:00.0: boot init ce src ring id 3 entries 32 base_addr
>> 8e057000
>> ath10k_pci 0000:01:00.0: boot init ce src ring id 4 entries 4096 base_addr
>> 8e060000
>> ath10k_pci 0000:01:00.0: boot ce dest ring id 5 entries 512 base_addr
>> 8e058000
>> ath10k_pci 0000:01:00.0: boot init ce src ring id 7 entries 2 base_addr
>> 8e05a000
>> ath10k_pci 0000:01:00.0: boot ce dest ring id 7 entries 2 base_addr
>> 8e05b000
>> ath10k_pci 0000:01:00.0: boot waiting target to initialise
>> ath10k_pci 0000:01:00.0: boot target indicator 0
>> ath10k_pci 0000:01:00.0: boot target indicator 1
>> ath10k_pci 0000:01:00.0: device has crashed during init
>> ath10k_pci 0000:01:00.0: failed to wait for target init: -70
>> ath10k_pci 0000:01:00.0: could not init core (-110)
>> ath10k_pci 0000:01:00.0: boot hif power down
>> ath10k_pci 0000:01:00.0: could not probe fw (-110)
>> ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
>> ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
>>
>> Thank you
>> Bartek
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
On 1 December 2015 at 09:42, Michal Kazior <[email protected]> wrote:
> On 1 December 2015 at 09:38, Bartlomiej Grzeskowiak
> <[email protected]> wrote:
>> Hi,
>>
>> I have already tried with backports 4.2.6 and different combinations
>> of firmware.bin / board.bin. With differnt results, but none of them
>> works. I will redo the tests and summarize them.
>>
>> Loading with irq_mode=1 gives me following result:
>> [55416.824364] ath10k_pci 0000:01:00.0: limiting irq mode to: 1
>> [55416.830102] ath10k_pci 0000:01:00.0: pci irq legacy interrupts 0
>> irq_mode 1 reset_mode 0
>> [55417.212048] ath10k_pci 0000:01:00.0: could not fetch firmware file
>> 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>> [55424.394422] ath10k_pci 0000:01:00.0: wmi unified ready event not received
>> [55424.436023] ath10k_pci 0000:01:00.0: firmware crashed! (uuid
>> e082ac60-7c2d-4d14-9c49-fd5b0591c95c)
>> [55424.445008] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000,
>
> Oh, wait.
>
> You have hw3.2? I haven't noticed that earlier.
>
> If memory serves right it needs a different board.bin (compared to
> e.g. hw3.0). I'm not sure if it's available in Kalle's repository.
> Wrong board.bin can cause firmware to hang or crash during init.
Could you give a try to the board-2.bin file, which is sort of a
container for the board bins, ath10k shall support.. and say if it
solves your card problem?
*) https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/board-2.bin
--
Bartosz
On 1 December 2015 at 09:38, Bartlomiej Grzeskowiak
<[email protected]> wrote:
> Hi,
>
> I have already tried with backports 4.2.6 and different combinations
> of firmware.bin / board.bin. With differnt results, but none of them
> works. I will redo the tests and summarize them.
>
> Loading with irq_mode=1 gives me following result:
> [55416.824364] ath10k_pci 0000:01:00.0: limiting irq mode to: 1
> [55416.830102] ath10k_pci 0000:01:00.0: pci irq legacy interrupts 0
> irq_mode 1 reset_mode 0
> [55417.212048] ath10k_pci 0000:01:00.0: could not fetch firmware file
> 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
> [55424.394422] ath10k_pci 0000:01:00.0: wmi unified ready event not received
> [55424.436023] ath10k_pci 0000:01:00.0: firmware crashed! (uuid
> e082ac60-7c2d-4d14-9c49-fd5b0591c95c)
> [55424.445008] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000,
Oh, wait.
You have hw3.2? I haven't noticed that earlier.
If memory serves right it needs a different board.bin (compared to
e.g. hw3.0). I'm not sure if it's available in Kalle's repository.
Wrong board.bin can cause firmware to hang or crash during init.
Michał
On Tue, Dec 01, 2015 at 11:28:25AM +0100, Bartlomiej Grzeskowiak wrote:
> I have tested borad-2.bin file with my module, by forcing
> ar->id.subsystem_vendor = 0x168c;
> ar->id.subsystem_device = 0x3363; (1,2,3)
> in ath/ath10k/pci.c file.
>
> All the tests failed with:
> ath10k_pci 0000:01:00.0: failed to receive initialized event from
> target: 00000000
> ath10k_pci 0000:01:00.0: firmware crashed! (uuid
> 5506e81c-d538-4492-91d7-dc899fed8d8c)
>
> Does it mean, that this module is not supported?
> I will need to dump firmware from windows driver, when I get it from
> the vendor ?
>
Can you please apply below changes in your rc2 backports.
https://github.com/kvalo/ath/commit/2727a743e9eeb3d4063d4077afee3fd2a5e198ca
https://github.com/kvalo/ath/commit/6419fdbb6f90e147690f8833cba59d289d613da5
or try with latest backports.
https://www.kernel.org/pub/linux/kernel/projects/backports/2015/11/20/backports-20151120.tar.gz
-Rajkumar
On 1 December 2015 at 07:20, Bartlomiej Grzeskowiak
<[email protected]> wrote:
> Hi,
>
> I am trying to use ath10k driver from the latest backports-4.4-rc.2-1 with
> kernel 3.10.65 and qca6174 based wlan module. Could you give me some hints
> about possible problem.
> ath10k_core.ko module loaded with skip_otp=y and debug_mask=0xffffffff.
>
> I get following error message:
> [ 5301.614749] ath10k_pci 0000:01:00.0: wmi unified ready event not
> received
> [ 5301.614749] ath10k_pci 0000:01:00.0: device has crashed during init
Seems Bartosz already fix this in this patch:
[PATCH] ath10k: fix QCA61X4 boot up
BR
Janusz
> [ 5301.644767] ath10k_pci 0000:01:00.0: device has crashed during init
> [ 5301.651025] ath10k_pci 0000:01:00.0: failed to wait for target init: -70
> [ 5301.661134] ath10k_pci 0000:01:00.0: could not init core (-110)
> [ 5301.667310] ath10k_pci 0000:01:00.0: could not probe fw (-110)
>
> Some other important debug messages (I can also provide the whole log if
> needed):
> ath10k_pci 0000:01:00.0: found fw version WLAN.RM.2.0-00180-QCARMSWPZ-1
> [...]
> ath10k_pci 0000:01:00.0: boot get otp board id result 0x00000001 board_id 0
> chip_id 0
> ath10k_pci 0000:01:00.0: boot using board name
> 'bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-
> device=0000'
> [...]
> ath10k_pci 0000:01:00.0: Target ready! transmit resources: 2 size:1792
> [...]
> ath10k_pci 0000:01:00.0: HTC Service HTT Data connect response: status:
> 0x0, assigned ep: 0x1
> [...]
> ath10k_pci 0000:01:00.0: HTC Service WMI connect response: status: 0x0,
> assigned ep: 0x2
> [...]
> ath10k_pci 0000:01:00.0: wmi event service ready min_tx_power 0x0000003f
> max_tx_power 0x0000003f ht_cap 0x0000085b vht_cap 0x339011b2 sw_ver0
> 0x01000000 sw_ver1 0x0000008f fw_build 0x200700b4 phy_capab 0x00000003
> num_rf_chains 0x00000002 eeprom_rd 0x00000000 num_mem_reqs 0x00000000
> ath10k_pci 0000:01:00.0: firmware WLAN.RM.2.0-00180-QCARMSWPZ-1 booted
> [...]
> ath10k_pci 0000:01:00.0: ath10k_htc_notify_tx_completion: ep 2 skb 8cc3b6c0
> ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
> ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
> ath10k_pci 0000:01:00.0: wmi unified ready event not received
> ath10k_pci 0000:01:00.0: boot hif stop
> [...]
> ath10k_pci 0000:01:00.0: boot init ce src ring id 0 entries 16 base_addr
> 8e053000
> ath10k_pci 0000:01:00.0: boot ce dest ring id 1 entries 512 base_addr
> 8e054000
> ath10k_pci 0000:01:00.0: boot ce dest ring id 2 entries 128 base_addr
> 8e056000
> ath10k_pci 0000:01:00.0: boot init ce src ring id 3 entries 32 base_addr
> 8e057000
> ath10k_pci 0000:01:00.0: boot init ce src ring id 4 entries 4096 base_addr
> 8e060000
> ath10k_pci 0000:01:00.0: boot ce dest ring id 5 entries 512 base_addr
> 8e058000
> ath10k_pci 0000:01:00.0: boot init ce src ring id 7 entries 2 base_addr
> 8e05a000
> ath10k_pci 0000:01:00.0: boot ce dest ring id 7 entries 2 base_addr
> 8e05b000
> ath10k_pci 0000:01:00.0: boot waiting target to initialise
> ath10k_pci 0000:01:00.0: boot target indicator 0
> ath10k_pci 0000:01:00.0: boot target indicator 1
> ath10k_pci 0000:01:00.0: device has crashed during init
> ath10k_pci 0000:01:00.0: failed to wait for target init: -70
> ath10k_pci 0000:01:00.0: could not init core (-110)
> ath10k_pci 0000:01:00.0: boot hif power down
> ath10k_pci 0000:01:00.0: could not probe fw (-110)
> ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
> ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
>
> Thank you
> Bartek
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I have tested borad-2.bin file with my module, by forcing
ar->id.subsystem_vendor = 0x168c;
ar->id.subsystem_device = 0x3363; (1,2,3)
in ath/ath10k/pci.c file.
All the tests failed with:
ath10k_pci 0000:01:00.0: failed to receive initialized event from
target: 00000000
ath10k_pci 0000:01:00.0: firmware crashed! (uuid
5506e81c-d538-4492-91d7-dc899fed8d8c)
Does it mean, that this module is not supported?
I will need to dump firmware from windows driver, when I get it from
the vendor ?
Thank you for the support
2015-12-01 10:53 GMT+01:00 Bartlomiej Grzeskowiak
<[email protected]>:
> HI,
>
> Yes, I am testing it now:
>
> ath10k_pci 0000:01:00.0: boot get otp board id result 0x00000001
> board_id 0 chip_id 0
> ath10k_pci 0000:01:00.0: boot using board name
> 'bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000'
> ath10k_pci 0000:01:00.0: board name
> ath10k_pci 0000:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 76 65 6e 64
> 6f 72 3d 31 bus=pci,vendor=1
> ath10k_pci 0000:01:00.0: 00000010: 36 38 63 2c 64 65 76 69 63 65 3d 30
> 30 33 65 2c 68c,device=003e,
> ath10k_pci 0000:01:00.0: 00000020: 73 75 62 73 79 73 74 65 6d 2d 76 65
> 6e 64 6f 72 subsystem-vendor
> ath10k_pci 0000:01:00.0: 00000030: 3d 31 36 38 63 2c 73 75 62 73 79 73
> 74 65 6d 2d =168c,subsystem-
> ath10k_pci 0000:01:00.0: 00000040: 64 65 76 69 63 65 3d 33 33 36 31
> device=3361
> ath10k_pci 0000:01:00.0: board name
> ath10k_pci 0000:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 76 65 6e 64
> 6f 72 3d 31 bus=pci,vendor=1
> ath10k_pci 0000:01:00.0: 00000010: 36 38 63 2c 64 65 76 69 63 65 3d 30
> 30 33 65 2c 68c,device=003e,
> ath10k_pci 0000:01:00.0: 00000020: 73 75 62 73 79 73 74 65 6d 2d 76 65
> 6e 64 6f 72 subsystem-vendor
> ath10k_pci 0000:01:00.0: 00000030: 3d 31 36 38 63 2c 73 75 62 73 79 73
> 74 65 6d 2d =168c,subsystem-
> ath10k_pci 0000:01:00.0: 00000040: 64 65 76 69 63 65 3d 33 33 36 32
> device=3362
> ath10k_pci 0000:01:00.0: board name
> ath10k_pci 0000:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 76 65 6e 64
> 6f 72 3d 31 bus=pci,vendor=1
> ath10k_pci 0000:01:00.0: 00000010: 36 38 63 2c 64 65 76 69 63 65 3d 30
> 30 33 65 2c 68c,device=003e,
> ath10k_pci 0000:01:00.0: 00000020: 73 75 62 73 79 73 74 65 6d 2d 76 65
> 6e 64 6f 72 subsystem-vendor
> ath10k_pci 0000:01:00.0: 00000030: 3d 31 36 38 63 2c 73 75 62 73 79 73
> 74 65 6d 2d =168c,subsystem-
> ath10k_pci 0000:01:00.0: 00000040: 64 65 76 69 63 65 3d 33 33 36 33
> device=3363
> ath10k_pci 0000:01:00.0: failed to fetch board data for
> ath10k/QCA6174/hw3.0 from
> bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000/board-2.bin,
> board_len= 0, board_data= 0x0
> ath10k_pci 0000:01:00.0: failed to fetch board data
> ath10k_pci 0000:01:00.0: failed to fetch board file: -2
> ath10k_pci 0000:01:00.0: boot hif power down
> ath10k_pci 0000:01:00.0: could not probe fw (-2)
> ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
> ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
>
> Strange that my card is subsystem-vendor=0000,subsystem-device=0000...
>
> 2015-12-01 10:43 GMT+01:00 Bartosz Markowski <[email protected]>:
>> On 1 December 2015 at 09:42, Michal Kazior <[email protected]> wrote:
>>> On 1 December 2015 at 09:38, Bartlomiej Grzeskowiak
>>> <[email protected]> wrote:
>>>> Hi,
>>>>
>>>> I have already tried with backports 4.2.6 and different combinations
>>>> of firmware.bin / board.bin. With differnt results, but none of them
>>>> works. I will redo the tests and summarize them.
>>>>
>>>> Loading with irq_mode=1 gives me following result:
>>>> [55416.824364] ath10k_pci 0000:01:00.0: limiting irq mode to: 1
>>>> [55416.830102] ath10k_pci 0000:01:00.0: pci irq legacy interrupts 0
>>>> irq_mode 1 reset_mode 0
>>>> [55417.212048] ath10k_pci 0000:01:00.0: could not fetch firmware file
>>>> 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>>>> [55424.394422] ath10k_pci 0000:01:00.0: wmi unified ready event not received
>>>> [55424.436023] ath10k_pci 0000:01:00.0: firmware crashed! (uuid
>>>> e082ac60-7c2d-4d14-9c49-fd5b0591c95c)
>>>> [55424.445008] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000,
>>>
>>> Oh, wait.
>>>
>>> You have hw3.2? I haven't noticed that earlier.
>>>
>>> If memory serves right it needs a different board.bin (compared to
>>> e.g. hw3.0). I'm not sure if it's available in Kalle's repository.
>>> Wrong board.bin can cause firmware to hang or crash during init.
>>
>> Could you give a try to the board-2.bin file, which is sort of a
>> container for the board bins, ath10k shall support.. and say if it
>> solves your card problem?
>>
>> *) https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/board-2.bin
>>
>> --
>> Bartosz
HI,
Yes, I am testing it now:
ath10k_pci 0000:01:00.0: boot get otp board id result 0x00000001
board_id 0 chip_id 0
ath10k_pci 0000:01:00.0: boot using board name
'bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000'
ath10k_pci 0000:01:00.0: board name
ath10k_pci 0000:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 76 65 6e 64
6f 72 3d 31 bus=pci,vendor=1
ath10k_pci 0000:01:00.0: 00000010: 36 38 63 2c 64 65 76 69 63 65 3d 30
30 33 65 2c 68c,device=003e,
ath10k_pci 0000:01:00.0: 00000020: 73 75 62 73 79 73 74 65 6d 2d 76 65
6e 64 6f 72 subsystem-vendor
ath10k_pci 0000:01:00.0: 00000030: 3d 31 36 38 63 2c 73 75 62 73 79 73
74 65 6d 2d =168c,subsystem-
ath10k_pci 0000:01:00.0: 00000040: 64 65 76 69 63 65 3d 33 33 36 31
device=3361
ath10k_pci 0000:01:00.0: board name
ath10k_pci 0000:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 76 65 6e 64
6f 72 3d 31 bus=pci,vendor=1
ath10k_pci 0000:01:00.0: 00000010: 36 38 63 2c 64 65 76 69 63 65 3d 30
30 33 65 2c 68c,device=003e,
ath10k_pci 0000:01:00.0: 00000020: 73 75 62 73 79 73 74 65 6d 2d 76 65
6e 64 6f 72 subsystem-vendor
ath10k_pci 0000:01:00.0: 00000030: 3d 31 36 38 63 2c 73 75 62 73 79 73
74 65 6d 2d =168c,subsystem-
ath10k_pci 0000:01:00.0: 00000040: 64 65 76 69 63 65 3d 33 33 36 32
device=3362
ath10k_pci 0000:01:00.0: board name
ath10k_pci 0000:01:00.0: 00000000: 62 75 73 3d 70 63 69 2c 76 65 6e 64
6f 72 3d 31 bus=pci,vendor=1
ath10k_pci 0000:01:00.0: 00000010: 36 38 63 2c 64 65 76 69 63 65 3d 30
30 33 65 2c 68c,device=003e,
ath10k_pci 0000:01:00.0: 00000020: 73 75 62 73 79 73 74 65 6d 2d 76 65
6e 64 6f 72 subsystem-vendor
ath10k_pci 0000:01:00.0: 00000030: 3d 31 36 38 63 2c 73 75 62 73 79 73
74 65 6d 2d =168c,subsystem-
ath10k_pci 0000:01:00.0: 00000040: 64 65 76 69 63 65 3d 33 33 36 33
device=3363
ath10k_pci 0000:01:00.0: failed to fetch board data for
ath10k/QCA6174/hw3.0 from
bus=pci,vendor=168c,device=003e,subsystem-vendor=0000,subsystem-device=0000/board-2.bin,
board_len= 0, board_data= 0x0
ath10k_pci 0000:01:00.0: failed to fetch board data
ath10k_pci 0000:01:00.0: failed to fetch board file: -2
ath10k_pci 0000:01:00.0: boot hif power down
ath10k_pci 0000:01:00.0: could not probe fw (-2)
ath10k_pci 0000:01:00.0: pci ps timer refcount 0 awake 1
ath10k_pci 0000:01:00.0: pci ps sleep reg refcount 0 awake 1
Strange that my card is subsystem-vendor=0000,subsystem-device=0000...
2015-12-01 10:43 GMT+01:00 Bartosz Markowski <[email protected]>:
> On 1 December 2015 at 09:42, Michal Kazior <[email protected]> wrote:
>> On 1 December 2015 at 09:38, Bartlomiej Grzeskowiak
>> <[email protected]> wrote:
>>> Hi,
>>>
>>> I have already tried with backports 4.2.6 and different combinations
>>> of firmware.bin / board.bin. With differnt results, but none of them
>>> works. I will redo the tests and summarize them.
>>>
>>> Loading with irq_mode=1 gives me following result:
>>> [55416.824364] ath10k_pci 0000:01:00.0: limiting irq mode to: 1
>>> [55416.830102] ath10k_pci 0000:01:00.0: pci irq legacy interrupts 0
>>> irq_mode 1 reset_mode 0
>>> [55417.212048] ath10k_pci 0000:01:00.0: could not fetch firmware file
>>> 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
>>> [55424.394422] ath10k_pci 0000:01:00.0: wmi unified ready event not received
>>> [55424.436023] ath10k_pci 0000:01:00.0: firmware crashed! (uuid
>>> e082ac60-7c2d-4d14-9c49-fd5b0591c95c)
>>> [55424.445008] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000,
>>
>> Oh, wait.
>>
>> You have hw3.2? I haven't noticed that earlier.
>>
>> If memory serves right it needs a different board.bin (compared to
>> e.g. hw3.0). I'm not sure if it's available in Kalle's repository.
>> Wrong board.bin can cause firmware to hang or crash during init.
>
> Could you give a try to the board-2.bin file, which is sort of a
> container for the board bins, ath10k shall support.. and say if it
> solves your card problem?
>
> *) https://github.com/kvalo/ath10k-firmware/blob/master/QCA6174/hw3.0/board-2.bin
>
> --
> Bartosz
On 1 December 2015 at 09:13, Bartlomiej Grzeskowiak
<[email protected]> wrote:
> Hi,
>
> Unfortunately I do have this patch in my code (backports-4.4-rc.2-1).
> I have also tested the old reg_address/mask value (0x00009028) but the
> result is the same.
The problem actually looks a little different. The mentioned patch
fixed a problem which would occur during early device init/probing.
Your problem seems to occur while booting and configuring firmware.
Did you try using older backports, firmware and/or board/board-2.bin
files? This could be some sort of regression you're seeing with the
exact combination you're testing.
You could also try loading ath10k_pci with irq_mode=1.
Michal
Hi Rajkumar,
Great. It works now.
I do not have a fully functional wlan yet, but at least the insmod goes through.
This issue is solved.
BR
Bartek
2015-12-07 10:08 GMT+01:00 Rajkumar Manoharan <[email protected]>:
> On Tue, Dec 01, 2015 at 11:28:25AM +0100, Bartlomiej Grzeskowiak wrote:
>> I have tested borad-2.bin file with my module, by forcing
>> ar->id.subsystem_vendor = 0x168c;
>> ar->id.subsystem_device = 0x3363; (1,2,3)
>> in ath/ath10k/pci.c file.
>>
>> All the tests failed with:
>> ath10k_pci 0000:01:00.0: failed to receive initialized event from
>> target: 00000000
>> ath10k_pci 0000:01:00.0: firmware crashed! (uuid
>> 5506e81c-d538-4492-91d7-dc899fed8d8c)
>>
>> Does it mean, that this module is not supported?
>> I will need to dump firmware from windows driver, when I get it from
>> the vendor ?
>>
> Can you please apply below changes in your rc2 backports.
>
> https://github.com/kvalo/ath/commit/2727a743e9eeb3d4063d4077afee3fd2a5e198ca
> https://github.com/kvalo/ath/commit/6419fdbb6f90e147690f8833cba59d289d613da5
>
> or try with latest backports.
>
> https://www.kernel.org/pub/linux/kernel/projects/backports/2015/11/20/backports-20151120.tar.gz
>
> -Rajkumar