Compex WLE600VX firmware crash
Adrian Chadd
adrian at freebsd.org
Mon Aug 7 13:57:35 PDT 2017
Woo good catch!
Ok, I'll go ask.
-adrian
On 7 August 2017 at 13:44, Richard Toy <richard.toy at gmail.com> wrote:
> I have just noticed that firmware-5.bin_10.2.4.70.61-2 exists and that
> also appears to work so the delta of interest is between releases
> firmware-5.bin_10.2.4.70.61-2 and firmware-5.bin_10.2.4.70.63-2.
>
> / /\ _ ___ ___ ___
> / LE / \ | | | __| \| __|
> / DE / \ | |__| _|| |) | _|
> /________/ LE \ |____|___|___/|___| lede-project.org
> \ \ DE /
> \ LE \ / -----------------------------------------------------------
> \ DE \ / Reboot (17.01.2, r3435-65eec8bd5f)
> \________\/ -----------------------------------------------------------
>
> root at OpenWrt:~# dmesg | grep ath
> [ 10.755618] ath10k_pci 0000:01:00.0: pci irq legacy oper_irq_mode 1
> irq_mode 0 reset_mode 0
> [ 10.977711] ath10k_pci 0000:01:00.0: Direct firmware load for
> ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2
> [ 10.988596] ath10k_pci 0000:01:00.0: Falling back to user helper
> [ 11.121748] firmware ath10k!pre-cal-pci-0000:01:00.0.bin:
> firmware_loading_store: map pages failed
> [ 11.643858] ath10k_pci 0000:01:00.0: qca988x hw2.0 target
> 0x4100016c chip_id 0x043202ff sub 0000:0000
> [ 11.653215] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1
> tracing 0 dfs 1 testmode 1
> [ 11.666355] ath10k_pci 0000:01:00.0: firmware ver 10.2.4.70.61-2
> api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 af2517b8
> [ 11.678553] ath10k_pci 0000:01:00.0: Direct firmware load for
> ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
> [ 11.689152] ath10k_pci 0000:01:00.0: Falling back to user helper
> [ 11.783440] firmware ath10k!QCA988X!hw2.0!board-2.bin:
> firmware_loading_store: map pages failed
> [ 11.805158] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
> crc32 bebc7c08
> [ 13.080494] ath10k_pci 0000:01:00.0: htt-ver 2.1 wmi-op 5 htt-op 2
> cal file max-sta 128 raw 0 hwcrypto 1
> [ 13.484387] ath: EEPROM regdomain: 0x0
> [ 13.484402] ath: EEPROM indicates default country code should be used
> [ 13.484410] ath: doing EEPROM country->regdmn map search
> [ 13.484426] ath: country maps to regdmn code: 0x3a
> [ 13.484435] ath: Country alpha2 being used: US
> [ 13.484442] ath: Regpair used: 0x3a
> [ 13.769649] ath: EEPROM regdomain: 0x0
> [ 13.769666] ath: EEPROM indicates default country code should be used
> [ 13.769674] ath: doing EEPROM country->regdmn map search
> [ 13.769691] ath: country maps to regdmn code: 0x3a
> [ 13.769700] ath: Country alpha2 being used: US
> [ 13.769707] ath: Regpair used: 0x3a
> [ 20.483064] ath: EEPROM regdomain: 0x8210
> [ 20.487175] ath: EEPROM indicates we should expect a country code
> [ 20.493353] ath: doing EEPROM country->regdmn map search
> [ 20.498755] ath: country maps to regdmn code: 0x37
> [ 20.503623] ath: Country alpha2 being used: NL
> [ 20.508126] ath: Regpair used: 0x37
> [ 20.511666] ath: regdomain 0x8210 dynamically updated by user
> [ 20.517580] ath: EEPROM regdomain: 0x8210
> [ 20.521642] ath: EEPROM indicates we should expect a country code
> [ 20.527830] ath: doing EEPROM country->regdmn map search
> [ 20.533216] ath: country maps to regdmn code: 0x37
> [ 20.538083] ath: Country alpha2 being used: NL
> [ 20.542587] ath: Regpair used: 0x37
> [ 20.546136] ath: regdomain 0x8210 dynamically updated by user
>
> Richard
>
> On 7 August 2017 at 22:19, Adrian Chadd <adrian at freebsd.org> wrote:
>> oh I didn't mean for anything to come across as sarcastic. Well, maybe
>> to QCA, but not users. :-)
>>
>> At least we have two version strings to get a diff against. I
>> unfortunately don't have full history of anything so I can't check for
>> myself. I'll go see if I can find anyone who can fill in what the
>> diffs are between those two 10.2 firmware releases to see if there's
>> some obvious smoking bullet.
>>
>> The one thing I do remember changing recently-ish is a calibration
>> data layout change that's small and subtle and causes issues. I don't
>> know if it falls within the above window though.
>>
>> So please do keep testing and providing more info!
>>
>>
>> -adrian
>>
>>
>> On 7 August 2017 at 13:06, Richard Toy <richard.toy at gmail.com> wrote:
>>> Hi Adrian,
>>>
>>> Sorry, I'm not sure I understand the reason for the sarcasm.
>>>
>>> In my original bug report post that I made in July I was totally ignored.
>>>
>>> In that post I note that with firmware-5.bin_10.2.4.70.59-2 boot is ok
>>> and router works but upgrading to latest released
>>> firmware-5.bin_10.2.4.70.63-2 causes crash at boot.
>>>
>>> What I noticed from Sergey's post was that the firmware register dumps
>>> were identical between his crash at startup and my crash at startup on
>>> different hardware platforms and thought this might prove useful to
>>> somebody with more knowledge.
>>>
>>> If there is some useful test that I could perform to help the
>>> community further then please just ask.
>>>
>>> Kindest regards,
>>> Richard
>>>
>>> On 7 August 2017 at 21:52, Adrian Chadd <adrian at freebsd.org> wrote:
>>>> Hi,
>>>>
>>>> If you can point to some older version working and newer version not..
>>>> oh wait, hm, let me see if they changed the calibration data format
>>>> between those two firmware revisions. Sigh.
>>>>
>>>>
>>>>
>>>> -adrian
>>>>
>>>>
>>>> On 7 August 2017 at 12:47, Richard Toy <richard.toy at gmail.com> wrote:
>>>>> As I already said to Sergey, that dump looks identical to the one I
>>>>> posted last month for exactly the same version of firmware running on
>>>>> a TP AC1750. I never found a solution but the previous version (54?)
>>>>> works fine.
>>>>>
>>>>> http://lists.infradead.org/pipermail/ath10k/2017-July/009933.html
>>>>>
>>>>> Richard
>>>>>
>>>>> On 7 August 2017 at 14:26, svp <s.pooheer at gmail.com> wrote:
>>>>>>
>>>>>> On 05.08.2017 03:07, Adrian Chadd wrote:
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Is this being used as a STA? AP? What's it associating to? what
>>>>>>> channel, mode, etc
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -adrian
>>>>>>>
>>>>>>
>>>>>> Hi!
>>>>>> The device was not initialized. Driver failed to set up network interface.
>>>>>> If then I try to start driver as modprobe ath10k_pci - result is the same -
>>>>>> firware crash.
>>>>>> More accurate dmesg log here:
>>>>>>
>>>>>> [ 2.651496] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
>>>>>> [ 2.651731] ath10k_pci 0000:06:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
>>>>>> [ 2.677241] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
>>>>>> [ 2.688848] random: crng init done
>>>>>> [ 2.694209] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input17
>>>>>> [ 2.694237] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input18
>>>>>> [ 2.694259] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input19
>>>>>> [ 2.694280] input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/sound/card0/input20
>>>>>> [ 2.719901] fbcon: inteldrmfb (fb0) is primary device
>>>>>> [ 2.763642] Console: switching to colour frame buffer device 240x75
>>>>>> [ 2.785165] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
>>>>>> [ 2.808817] ath10k_pci 0000:06:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
>>>>>> [ 2.808818] ath10k_pci 0000:06:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>>>>>> [ 2.808960] ath10k_pci 0000:06:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
>>>>>> [ 2.849225] ath10k_pci 0000:06:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
>>>>>> [ 3.102190] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: data=ordered
>>>>>> [ 3.120930] nct6775: Enabling hardware monitor logical device mappings.
>>>>>> [ 3.120944] nct6775: Found NCT6791D or compatible chip at 0x2e:0x290
>>>>>> [ 3.403675] enp3s0: 0xffffa31883295000, 74:d0:2b:7e:f7:35, IRQ 30
>>>>>> [ 3.979192] ath10k_pci 0000:06:00.0: firmware crashed! (uuid 1773073a-6896-4834-91d4-6d0e9b026b06)
>>>>>> [ 3.979241] ath10k_pci 0000:06:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
>>>>>> [ 3.979244] ath10k_pci 0000:06:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>>>>>> [ 3.979456] ath10k_pci 0000:06:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
>>>>>> [ 3.979461] ath10k_pci 0000:06:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
>>>>>> [ 3.979463] ath10k_pci 0000:06:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
>>>>>> [ 3.981477] ath10k_pci 0000:06:00.0: firmware register dump:
>>>>>> [ 3.981501] ath10k_pci 0000:06:00.0: [00]: 0x4100016C 0x000015B3 0x009BFF84 0x00955B31
>>>>>> [ 3.981530] ath10k_pci 0000:06:00.0: [04]: 0x009BFF84 0x00060130 0x00000013 0x00000000
>>>>>> [ 3.981559] ath10k_pci 0000:06:00.0: [08]: 0x009C8EA4 0x00007170 0x00000001 0x00435300
>>>>>> [ 3.981588] ath10k_pci 0000:06:00.0: [12]: 0x00000009 0x00000000 0x00958360 0x0095836B
>>>>>> [ 3.981616] ath10k_pci 0000:06:00.0: [16]: 0x00958080 0x0094078E 0x00000000 0x00000000
>>>>>> [ 3.981645] ath10k_pci 0000:06:00.0: [20]: 0x409BFF84 0x0040AB44 0x004101E0 0x0000000C
>>>>>> [ 3.981675] ath10k_pci 0000:06:00.0: [24]: 0x809BFE1C 0x0040ABA4 0x00000006 0xC09BFF84
>>>>>> [ 3.981703] ath10k_pci 0000:06:00.0: [28]: 0x8098E907 0x0040ABD4 0x009C8E7C 0x0000016B
>>>>>> [ 3.982735] ath10k_pci 0000:06:00.0: [32]: 0x8098FD3B 0x0040ABF4 0x004209EC 0x00420B0C
>>>>>> [ 3.983755] ath10k_pci 0000:06:00.0: [36]: 0x8098A7DA 0x0040AC34 0x00420AA0 0x004062DC
>>>>>> [ 3.984763] ath10k_pci 0000:06:00.0: [40]: 0x80988785 0x0040AC94 0x00410760 0x00400000
>>>>>> [ 3.985763] ath10k_pci 0000:06:00.0: [44]: 0x8098AEC8 0x0040AD44 0x00410760 0x00000001
>>>>>> [ 3.986752] ath10k_pci 0000:06:00.0: [48]: 0x809B67C4 0x0040AD84 0x00410760 0x00411344
>>>>>> [ 3.987740] ath10k_pci 0000:06:00.0: [52]: 0x809B293C 0x0040ADA4 0x00400000 0x00416FA4
>>>>>> [ 3.988723] ath10k_pci 0000:06:00.0: [56]: 0x809C0C3D 0x0040ADE4 0x0040AE08 0x00412118
>>>>>> [ 3.989700] ath10k_pci 0000:06:00.0: Copy Engine register dump:
>>>>>> [ 3.990684] ath10k_pci 0000:06:00.0: [00]: 0x00057400 0 0 3 3
>>>>>> [ 3.991670] ath10k_pci 0000:06:00.0: [01]: 0x00057800 3 3 8 9
>>>>>> [ 3.992652] ath10k_pci 0000:06:00.0: [02]: 0x00057c00 1 1 0 1
>>>>>> [ 3.993628] ath10k_pci 0000:06:00.0: [03]: 0x00058000 1 1 2 1
>>>>>> [ 3.994587] ath10k_pci 0000:06:00.0: [04]: 0x00058400 0 0 40 0
>>>>>> [ 3.995529] ath10k_pci 0000:06:00.0: [05]: 0x00058800 0 0 0 0
>>>>>> [ 3.996454] ath10k_pci 0000:06:00.0: [06]: 0x00058c00 0 0 0 0
>>>>>> [ 3.997359] ath10k_pci 0000:06:00.0: [07]: 0x00059000 0 0 0 0
>>>>>> [ 5.501878] r8168: enp3s0: link up
>>>>>> [ 7.630654] usb 3-13: device descriptor read/64, error -110
>>>>>> [ 9.010685] ath10k_pci 0000:06:00.0: wmi unified ready event not received
>>>>>> [ 9.082483] ath10k_pci 0000:06:00.0: could not init core (-110)
>>>>>> [ 9.083167] ath10k_pci 0000:06:00.0: could not probe fw (-110)
>>>>>> [ 9.097304] ath10k_pci 0000:06:00.0: cannot restart a device that hasn't been started
>>>>>>
>>>>>>
>>>>>> Sergey
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> ath10k mailing list
>>>>>> ath10k at lists.infradead.org
>>>>>> http://lists.infradead.org/mailman/listinfo/ath10k
More information about the ath10k
mailing list