Re: CT firmware crashes randomly

[Ben Greear <greearb@candelatech.com>]

On 05/11/2015 11:55 AM, Costa Molero Edgar wrote:
> Do you know how can I reset fw_stats content without the "hw-reset" ? If there is a way I will definitely use it instead of making the firmware crash.

No, but you can store the values and calculate the differences.

You can also admin down all station/ap interfaces, and when you start them
again I think the firmware will be restarted (but more gracefully that
just causing FW to crash).

Thanks,
Ben

> ________________________________________
> De: Ben Greear [greearb@candelatech.com]
> Enviat el: dilluns, 11 / maig / 2015 20:48
> Per a: Costa Molero  Edgar
> A/c: ath10k@lists.infradead.org
> Tema: Re: CT firmware crashes randomly
> 
> On 05/11/2015 11:37 AM, Costa Molero Edgar wrote:
>> Hi,
>>
>> I am running some tests using a wle900vx nic, and the commercial firmware CT 10.4.467-ct-com-full-013-b5b14.
>>
>> For the tests I am modifying the transmission rates and number of spatial streams I use. MCS 0-9, SS 1-3 ("iw wlanX set bitrates legacy-5 ht-mcs-5 vht-mcs-5 x:y).
>> Every time I modify the transmission rate I disconnect and connect from the Access Point. Then I found that if I want to reset the values of "fw_stats" file I need to reload the firmware, or I can do a (echo "hw-restart" > simulate_fw_crash).
> 
> I think you should find a better way to
> clear the stats...like snapshot the values and then just calculate the differences in
> your script.
> 
>> The test should take around 4-6h but some times randomly the script I am running is not able to set bit rates anymore. (-22 error). When this happen the script tries to reload the ath10k driver (modprobe -r ath10k + modprobe ath10k). But after that I can not connect to the access point anymore until I reboot the computer.  Could it be because I do "hw-restart" too many times?.
>>
>>
>> Here a slice of dmesg : at the end you will see that I restart it several times. (However, in the part you can not see I was doing the same as well)
>>
>> [   17.248265] ath10k_pci 0000:0c:00.0: irq 43 for MSI/MSI-X
>> [   17.248297] ath10k_pci 0000:0c:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0
>> [   17.945015] ath10k_pci 0000:0c:00.0: Direct firmware load failed with error -2
>> [   17.945020] ath10k_pci 0000:0c:00.0: Falling back to user helper
>> [   18.243890] ath10k_pci 0000:0c:00.0: Direct firmware load failed with error -2
>> [   18.243899] ath10k_pci 0000:0c:00.0: Falling back to user helper
>> [   18.244959] ath10k_pci 0000:0c:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-4.bin': -12
>> [   18.244999] ath10k_pci 0000:0c:00.0: Direct firmware load failed with error -2
>> [   18.245003] ath10k_pci 0000:0c:00.0: Falling back to user helper
>> [   18.246260] ath10k_pci 0000:0c:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-3.bin': -12
>> [   19.444502] ath10k_pci 0000:0c:00.0: qca988x hw2.0 (0x4100016c, 0x043202ff) fw 10.1.467-ct-com-full-013-b5b14a api 2 htt 2.1 wmi 2 cal otp max_sta 128
>> [   19.444509] ath10k_pci 0000:0c:00.0: debug 1 debugfs 1 tracing 0 dfs 0 testmode 0
>> [  149.913555] ath10k_pci 0000:0c:00.0: user requested hw restart
>> [  151.026791] ath10k_pci 0000:0c:00.0: device successfully recovered
>> [  154.925661] WARNING: CPU: 0 PID: 2365 at /home/wimo/backports_kernel3.16/backports-4.0.1-1/drivers/net/wireless/ath/ath10k/htt_rx.c:968 ath10k_htt_rx_h_mpdu.isra.39+0x699/0x710 [ath10k_core]()
>> [  154.925665] Modules linked in: rfcomm bnep bluetooth 6lowpan_iphc arc4 carl9170(OE) dell_wmi sparse_keymap gpio_ich ath10k_pci(OE) dell_laptop pcmcia ath10k_core(OE) coretemp dcdbas kvm ath(OE) mac80211(OE) joydev yenta_socket serio_raw pcmcia_rsrc pcmcia_core cfg80211(OE) compat(OE) wmi snd_hda_codec_idt snd_hda_codec_generic mac_hid i915 drm_kms_helper irda crc_ccitt snd_hda_intel drm snd_hda_controller snd_hda_codec snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event lpc_ich video snd_rawmidi i2c_algo_bit snd_seq snd_seq_device snd_timer snd soundcore shpchp parport_pc ppdev lp parport psmouse firewire_ohci b44 firewire_core crc_itu_t ssb pata_acpi mii
>> [  154.925844]  [<ffffffffc0852b69>] ath10k_htt_rx_h_mpdu.isra.39+0x699/0x710 [ath10k_core]
>> [  154.925865]  [<ffffffffc08533ff>] ? ath10k_htt_rx_h_ppdu+0x1ef/0x240 [ath10k_core]
>> [  154.925879]  [<ffffffffc0854051>] ath10k_htt_txrx_compl_task+0x391/0xde0 [ath10k_core]
>> [  155.044138] ath10k_pci 0000:0c:00.0: rx ring became corrupted: -5
> 
> That is interesting...I don't think I've seen that rx-ring issue in any of my testing, but we
> also do not see many firmware crashes in our testing.
> 
> Possibly this is a driver issue, or maybe it exposes some firmware issue.
> 
> Either way, I suggest to fix your script to not have to crash or restart the firmware.
> 
> If you do get un-requested firmware crashes, please send me full crash log, which
> should have a register dump from the firmware so I can decode where the crash
> happens...
> 
> Thanks,
> Ben
> 
> 
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
> 


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


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