Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-22 Thread Sebastian Gottschall
btw. you can do the backup also with openwrt of course. i just need a 
backup of the flash memory. ben already wrote that my guess about a 
different location for the calibration data storage might be true. so 
find out the correct location i need to analyse the flash dump


Am 21.09.2018 um 11:35 schrieb Sebastian Gottschall:
you may use the backup function at Administration->backup which 
creates a file for download


or from commandline use "nvram backup /tmp/mybackup.bin"

for full flash backup on the r7800 do

cat /proc/mtd which shows

mtd0: 00c8 0002 "qcadata"
mtd1: 0050 0002 "APPSBL"
mtd2: 0008 0002 "APPSBLENV"
mtd3: 0014 0002 "art"
mtd4: 0014 0002 "artbak"
mtd5: 01e0 0002 "linux"
mtd6: 01be 0002 "rootfs"
mtd7: 0020 0002 "nvram"
mtd8: 0200 0002 "ddwrt"
mtd9: 0064 0002 "reserved"


then do a backup of all partitions with

cat /dev/mtdblock0 > /tmp/mtdblock0.bin and so on

then copy them with scp to your local computer. you may need to enable 
ssh server first at services->ssh


Am 20.09.2018 um 14:02 schrieb Bruno Rosset:

Hi Sebastian,

OK no problem. I can do that.
Can you just tell me what you need ; I mean which commands to export 
data ?

For nvram I guess you need 'nvram show' results ?

How I can do a "full flash transfer" ?

As you're dd-wrt dev,  I add that I try last dd-wrt build  (this one :
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/08-22-2018-r36698/netgear-r7800/factory-to-ddwrt.img) 


which not even boot. Same with kong one (this one :
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Test/R7800-factory-to-ddwrt.img) 



thats not the latest

ftp://ftp.dd-wrt.com/betas/2018/09-19-2018-r36995/netgear-r7800/factory-to-ddwrt.img 



i tested this also on my devices

so if these other versions you mentioned wont boot on your device it 
already looks strange since i test the r7800 always with each released 
build. the builds from desipro.de are external and not watched by me


these are test builds by a contributor




What I made is that I extract the board-2.bin & fiurmware-5.bin from
the ddwrt's squashfs image and try them on the openWRT install, but
without success also.


the board-2.bin is not the one you need. the real board data is 
generated at /tmp folder from flash partition content and named 
/tmp/board1.bin and /tmp/board2.bin for each of both wireless devices





Best regards,
Bruno
Le jeu. 20 sept. 2018 à 13:07, Sebastian Gottschall
 a écrit :
since i'm mainly the dd-wrt developer and you tested it as well with 
the

same reproduceable crash it would be nice if you could provide me a
nvram backup with a reproduceable crash (you should change passwords of
course) to my private email. so i can apply it to my device and to see
whats happen. if you have a beta device i just can guess that the
calibration data which is stored in flash memory has maybe a different
location, so openwrt as well as dd-wrt uses crap to initialize the
hardware. this is just a guess. but i have 2 r7800 factory models. you
can also send me a full flash backup of your device using 
wetransfer, so

i can compare the content with my device and check if there is a flash
layout specific different. this would help to track down the problem
cause and maybe find a specific workaround for such devices by 
detecting

them well

Sebastian

Am 20.09.2018 um 09:44 schrieb Bruno Rosset:

HI Sebastian,

I just flash the r7800 with the openwrt 18.06.1 factory image (here :
https://downloads.openwrt.org/releases/18.06.1/targets/ipq806x/generic/openwrt-18.06.1-ipq806x-netgear_r7800-squashfs-factory.img) 



I forgot to mention that I get a beta hardware of the R7800, perhaps
there is something different in my hardware compared to the released
one.

Regards,
Bruno
Le jeu. 20 sept. 2018 à 08:36, Sebastian Gottschall
 a écrit :
can you tell me how to reproduce this crash? i have 2 r7800 
running with

dd-wrt but no crashes

Am 19.09.2018 um 22:37 schrieb Bruno Rosset:

Hi all,

I get a firmware crash using latest openwrt 18.06.1 on the Netgear
R7800 with stock firmware
Dmesg is :
[   13.804366] ath10k_pci :01:00.0: assign IRQ: got 67
[   13.804805] ath10k_pci :01:00.0: enabling device (0140 -> 
0142)

[   13.804887] ath10k_pci :01:00.0: enabling bus mastering
[   13.805346] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[   13.974787] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[   13.974827] ath10k_pci :01:00.0: Falling back to user helper
[   14.304794] ath10k_pci :01:00.0: Direct firmware load for
ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
[   14.304857] ath10k_pci :01:00.0: Falling back to user helper
[   14.337111] firmware ath10k!QCA9984!hw1.0!firmware-6.bin:
firmware_loading_store: map pages failed
[   14.702947] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 1

Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-21 Thread Ben Greear




On 09/19/2018 01:56 PM, Bruno Rosset wrote:

Hi,

Done, thanks
Le mer. 19 sept. 2018 à 22:45, Ben Greear  a écrit :


On 09/19/2018 01:37 PM, Bruno Rosset wrote:

Hi all,




Various tests with others firmware from candelatech , stock LEDE 17.01
or dd-wrt give me firmware crash also


The crash in my firmware decodes to something that looks probably like
the calibration data is wrong.

This is probably some issue with how the board data is selected, or maybe
the wrong board data is installed on the file system.

Thanks,
Ben



Please open a bug for the candela firmware crash, I might be able to figure
out why it crashes:

https://github.com/greearb/ath10k-ct/issues

https://www.candelatech.com/ath10k-bugs.php

Thanks,
Ben


--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com





--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com


Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-21 Thread Sebastian Gottschall
you may use the backup function at Administration->backup which creates 
a file for download


or from commandline use "nvram backup /tmp/mybackup.bin"

for full flash backup on the r7800 do

cat /proc/mtd which shows

mtd0: 00c8 0002 "qcadata"
mtd1: 0050 0002 "APPSBL"
mtd2: 0008 0002 "APPSBLENV"
mtd3: 0014 0002 "art"
mtd4: 0014 0002 "artbak"
mtd5: 01e0 0002 "linux"
mtd6: 01be 0002 "rootfs"
mtd7: 0020 0002 "nvram"
mtd8: 0200 0002 "ddwrt"
mtd9: 0064 0002 "reserved"


then do a backup of all partitions with

cat /dev/mtdblock0 > /tmp/mtdblock0.bin and so on

then copy them with scp to your local computer. you may need to enable 
ssh server first at services->ssh


Am 20.09.2018 um 14:02 schrieb Bruno Rosset:

Hi Sebastian,

OK no problem. I can do that.
Can you just tell me what you need ; I mean which commands to export data ?
For nvram I guess you need 'nvram show' results ?

How I can do a "full flash transfer" ?

As you're dd-wrt dev,  I add that I try last dd-wrt build  (this one :
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/08-22-2018-r36698/netgear-r7800/factory-to-ddwrt.img)
which not even boot. Same with kong one (this one :
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Test/R7800-factory-to-ddwrt.img)


thats not the latest

ftp://ftp.dd-wrt.com/betas/2018/09-19-2018-r36995/netgear-r7800/factory-to-ddwrt.img

i tested this also on my devices

so if these other versions you mentioned wont boot on your device it 
already looks strange since i test the r7800 always with each released 
build. the builds from desipro.de are external and not watched by me


these are test builds by a contributor




What I made is that I extract the board-2.bin & fiurmware-5.bin from
the ddwrt's squashfs image and try them on the openWRT install, but
without success also.


the board-2.bin is not the one you need. the real board data is 
generated at /tmp folder from flash partition content and named 
/tmp/board1.bin and /tmp/board2.bin for each of both wireless devices





Best regards,
Bruno
Le jeu. 20 sept. 2018 à 13:07, Sebastian Gottschall
 a écrit :

since i'm mainly the dd-wrt developer and you tested it as well with the
same reproduceable crash it would be nice if you could provide me a
nvram backup with a reproduceable crash (you should change passwords of
course) to my private email. so i can apply it to my device and to see
whats happen. if you have a beta device i just can guess that the
calibration data which is stored in flash memory has maybe a different
location, so openwrt as well as dd-wrt uses crap to initialize the
hardware. this is just a guess. but i have 2 r7800 factory models. you
can also send me a full flash backup of your device using wetransfer, so
i can compare the content with my device and check if there is a flash
layout specific different. this would help to track down the problem
cause and maybe find a specific workaround for such devices by detecting
them well

Sebastian

Am 20.09.2018 um 09:44 schrieb Bruno Rosset:

HI Sebastian,

I just flash the r7800 with the openwrt 18.06.1 factory image (here :
https://downloads.openwrt.org/releases/18.06.1/targets/ipq806x/generic/openwrt-18.06.1-ipq806x-netgear_r7800-squashfs-factory.img)

I forgot to mention that I get a beta hardware of the R7800, perhaps
there is something different in my hardware compared to the released
one.

Regards,
Bruno
Le jeu. 20 sept. 2018 à 08:36, Sebastian Gottschall
 a écrit :

can you tell me how to reproduce this crash? i have 2 r7800 running with
dd-wrt but no crashes

Am 19.09.2018 um 22:37 schrieb Bruno Rosset:

Hi all,

I get a firmware crash using latest openwrt 18.06.1 on the Netgear
R7800 with stock firmware
Dmesg is :
[   13.804366] ath10k_pci :01:00.0: assign IRQ: got 67
[   13.804805] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
[   13.804887] ath10k_pci :01:00.0: enabling bus mastering
[   13.805346] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[   13.974787] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[   13.974827] ath10k_pci :01:00.0: Falling back to user helper
[   14.304794] ath10k_pci :01:00.0: Direct firmware load for
ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
[   14.304857] ath10k_pci :01:00.0: Falling back to user helper
[   14.337111] firmware ath10k!QCA9984!hw1.0!firmware-6.bin:
firmware_loading_store: map pages failed
[   14.702947] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[   14.702997] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   14.716459] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
crc32 4c56a386
[   15.973104] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
crc32 dd6d039c
[

Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-20 Thread Bruno Rosset
Hi Sebastian,

OK no problem. I can do that.
Can you just tell me what you need ; I mean which commands to export data ?
For nvram I guess you need 'nvram show' results ?

How I can do a "full flash transfer" ?

As you're dd-wrt dev,  I add that I try last dd-wrt build  (this one :
https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/08-22-2018-r36698/netgear-r7800/factory-to-ddwrt.img)
which not even boot. Same with kong one (this one :
http://www.desipro.de/ddwrt/K3-AC-IPQ806X/Test/R7800-factory-to-ddwrt.img)

What I made is that I extract the board-2.bin & fiurmware-5.bin from
the ddwrt's squashfs image and try them on the openWRT install, but
without success also.

Best regards,
Bruno
Le jeu. 20 sept. 2018 à 13:07, Sebastian Gottschall
 a écrit :
>
> since i'm mainly the dd-wrt developer and you tested it as well with the
> same reproduceable crash it would be nice if you could provide me a
> nvram backup with a reproduceable crash (you should change passwords of
> course) to my private email. so i can apply it to my device and to see
> whats happen. if you have a beta device i just can guess that the
> calibration data which is stored in flash memory has maybe a different
> location, so openwrt as well as dd-wrt uses crap to initialize the
> hardware. this is just a guess. but i have 2 r7800 factory models. you
> can also send me a full flash backup of your device using wetransfer, so
> i can compare the content with my device and check if there is a flash
> layout specific different. this would help to track down the problem
> cause and maybe find a specific workaround for such devices by detecting
> them well
>
> Sebastian
>
> Am 20.09.2018 um 09:44 schrieb Bruno Rosset:
> > HI Sebastian,
> >
> > I just flash the r7800 with the openwrt 18.06.1 factory image (here :
> > https://downloads.openwrt.org/releases/18.06.1/targets/ipq806x/generic/openwrt-18.06.1-ipq806x-netgear_r7800-squashfs-factory.img)
> >
> > I forgot to mention that I get a beta hardware of the R7800, perhaps
> > there is something different in my hardware compared to the released
> > one.
> >
> > Regards,
> > Bruno
> > Le jeu. 20 sept. 2018 à 08:36, Sebastian Gottschall
> >  a écrit :
> >> can you tell me how to reproduce this crash? i have 2 r7800 running with
> >> dd-wrt but no crashes
> >>
> >> Am 19.09.2018 um 22:37 schrieb Bruno Rosset:
> >>> Hi all,
> >>>
> >>> I get a firmware crash using latest openwrt 18.06.1 on the Netgear
> >>> R7800 with stock firmware
> >>> Dmesg is :
> >>> [   13.804366] ath10k_pci :01:00.0: assign IRQ: got 67
> >>> [   13.804805] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
> >>> [   13.804887] ath10k_pci :01:00.0: enabling bus mastering
> >>> [   13.805346] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2
> >>> irq_mode 0 reset_mode 0
> >>> [   13.974787] ath10k_pci :01:00.0: Direct firmware load for
> >>> ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
> >>> [   13.974827] ath10k_pci :01:00.0: Falling back to user helper
> >>> [   14.304794] ath10k_pci :01:00.0: Direct firmware load for
> >>> ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
> >>> [   14.304857] ath10k_pci :01:00.0: Falling back to user helper
> >>> [   14.337111] firmware ath10k!QCA9984!hw1.0!firmware-6.bin:
> >>> firmware_loading_store: map pages failed
> >>> [   14.702947] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
> >>> 0x0100 chip_id 0x sub 168c:cafe
> >>> [   14.702997] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
> >>> tracing 0 dfs 1 testmode 1
> >>> [   14.716459] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
> >>> api 5 features 
> >>> no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
> >>> crc32 4c56a386
> >>> [   15.973104] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
> >>> crc32 dd6d039c
> >>> [   19.753460] ath10k_pci :01:00.0: firmware crashed! (guid
> >>> ca7089d2-df9a-4f9d-8fa6-d1b908cf3220)
> >>> [   19.753494] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
> >>> 0x0100 chip_id 0x sub 168c:cafe
> >>> [   19.761307] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
> >>> tracing 0 dfs 1 testmode 1
> >>> [   19.773202] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
> >>> api 5 features 
> >>> no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
> >>> crc32 4c56a386
> >>> [   19.779887] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
> >>> crc32 dd6d039c
> >>> [   19.793511] ath10k_pci :01:00.0: htt-ver 0.0 wmi-op 6 htt-op 4
> >>> cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
> >>> [   19.803176] ath10k_pci :01:00.0: firmware register dump:
> >>> [   19.810956] ath10k_pci :01:00.0: [00]: 0x0100 0x15B3
> >>> 0x009CBB38 0x00975B31
> >>> [   19.816861] ath10k_pci :01:00.0: [04]: 0x009CBB38 0x00060530
> >>> 0x0011 0x00415760
> >>> [   19.824587] ath10k_pci :01:00.0: [08]: 0x00417E6C 0x0040
> >>> 0x0001 0x00422990
> >>> 

Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-20 Thread Sebastian Gottschall
since i'm mainly the dd-wrt developer and you tested it as well with the 
same reproduceable crash it would be nice if you could provide me a 
nvram backup with a reproduceable crash (you should change passwords of 
course) to my private email. so i can apply it to my device and to see 
whats happen. if you have a beta device i just can guess that the 
calibration data which is stored in flash memory has maybe a different 
location, so openwrt as well as dd-wrt uses crap to initialize the 
hardware. this is just a guess. but i have 2 r7800 factory models. you 
can also send me a full flash backup of your device using wetransfer, so 
i can compare the content with my device and check if there is a flash 
layout specific different. this would help to track down the problem 
cause and maybe find a specific workaround for such devices by detecting 
them well


Sebastian

Am 20.09.2018 um 09:44 schrieb Bruno Rosset:

HI Sebastian,

I just flash the r7800 with the openwrt 18.06.1 factory image (here :
https://downloads.openwrt.org/releases/18.06.1/targets/ipq806x/generic/openwrt-18.06.1-ipq806x-netgear_r7800-squashfs-factory.img)

I forgot to mention that I get a beta hardware of the R7800, perhaps
there is something different in my hardware compared to the released
one.

Regards,
Bruno
Le jeu. 20 sept. 2018 à 08:36, Sebastian Gottschall
 a écrit :

can you tell me how to reproduce this crash? i have 2 r7800 running with
dd-wrt but no crashes

Am 19.09.2018 um 22:37 schrieb Bruno Rosset:

Hi all,

I get a firmware crash using latest openwrt 18.06.1 on the Netgear
R7800 with stock firmware
Dmesg is :
[   13.804366] ath10k_pci :01:00.0: assign IRQ: got 67
[   13.804805] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
[   13.804887] ath10k_pci :01:00.0: enabling bus mastering
[   13.805346] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[   13.974787] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[   13.974827] ath10k_pci :01:00.0: Falling back to user helper
[   14.304794] ath10k_pci :01:00.0: Direct firmware load for
ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
[   14.304857] ath10k_pci :01:00.0: Falling back to user helper
[   14.337111] firmware ath10k!QCA9984!hw1.0!firmware-6.bin:
firmware_loading_store: map pages failed
[   14.702947] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[   14.702997] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   14.716459] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
crc32 4c56a386
[   15.973104] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
crc32 dd6d039c
[   19.753460] ath10k_pci :01:00.0: firmware crashed! (guid
ca7089d2-df9a-4f9d-8fa6-d1b908cf3220)
[   19.753494] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[   19.761307] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   19.773202] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
crc32 4c56a386
[   19.779887] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
crc32 dd6d039c
[   19.793511] ath10k_pci :01:00.0: htt-ver 0.0 wmi-op 6 htt-op 4
cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[   19.803176] ath10k_pci :01:00.0: firmware register dump:
[   19.810956] ath10k_pci :01:00.0: [00]: 0x0100 0x15B3
0x009CBB38 0x00975B31
[   19.816861] ath10k_pci :01:00.0: [04]: 0x009CBB38 0x00060530
0x0011 0x00415760
[   19.824587] ath10k_pci :01:00.0: [08]: 0x00417E6C 0x0040
0x0001 0x00422990
[   19.832485] ath10k_pci :01:00.0: [12]: 0x0009 0x
0x00973B25 0x00973B47
[   19.840384] ath10k_pci :01:00.0: [16]: 0x009CBB38 0x000CEEA7
0x 0x
[   19.848284] ath10k_pci :01:00.0: [20]: 0x409CBB38 0x004068DC
0x0001 0x00403628
[   19.856183] ath10k_pci :01:00.0: [24]: 0x809814EF 0x0040693C
0x0049 0xC09CBB38
[   19.864083] ath10k_pci :01:00.0: [28]: 0x800DF216 0x004069AC
0x0004 0x00415300
[   19.871983] ath10k_pci :01:00.0: [32]: 0x800C383A 0x004069DC
0x00415160 0x0040
[   19.879881] ath10k_pci :01:00.0: [36]: 0x809800A3 0x00406A0C
0x00415170 0x009C41F8
[   19.887781] ath10k_pci :01:00.0: [40]: 0x8098003A 0x00406A5C
0x0040 0x00400600
[   19.895680] ath10k_pci :01:00.0: [44]: 0x809607C1 0x00406A8C
0xD8400100 0x00406A9C
[   19.903579] ath10k_pci :01:00.0: [48]: 0x80960892 0x00406AAC
0x 0x0008
[   19.911479] ath10k_pci :01:00.0: [52]: 0x80960E39 0x00406ACC
0x0040 0x00400600
[   19.919378] ath10k_pci :01:00.0: [56]: 0x80960E9D 0x00406AEC
0x 0x00400600
[   19.927277] ath10k_pci :01:00.0: Copy Engine register dump:
[   19.

Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-20 Thread Bruno Rosset
HI Sebastian,

I just flash the r7800 with the openwrt 18.06.1 factory image (here :
https://downloads.openwrt.org/releases/18.06.1/targets/ipq806x/generic/openwrt-18.06.1-ipq806x-netgear_r7800-squashfs-factory.img)

I forgot to mention that I get a beta hardware of the R7800, perhaps
there is something different in my hardware compared to the released
one.

Regards,
Bruno
Le jeu. 20 sept. 2018 à 08:36, Sebastian Gottschall
 a écrit :
>
> can you tell me how to reproduce this crash? i have 2 r7800 running with
> dd-wrt but no crashes
>
> Am 19.09.2018 um 22:37 schrieb Bruno Rosset:
> > Hi all,
> >
> > I get a firmware crash using latest openwrt 18.06.1 on the Netgear
> > R7800 with stock firmware
> > Dmesg is :
> > [   13.804366] ath10k_pci :01:00.0: assign IRQ: got 67
> > [   13.804805] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
> > [   13.804887] ath10k_pci :01:00.0: enabling bus mastering
> > [   13.805346] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2
> > irq_mode 0 reset_mode 0
> > [   13.974787] ath10k_pci :01:00.0: Direct firmware load for
> > ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
> > [   13.974827] ath10k_pci :01:00.0: Falling back to user helper
> > [   14.304794] ath10k_pci :01:00.0: Direct firmware load for
> > ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
> > [   14.304857] ath10k_pci :01:00.0: Falling back to user helper
> > [   14.337111] firmware ath10k!QCA9984!hw1.0!firmware-6.bin:
> > firmware_loading_store: map pages failed
> > [   14.702947] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
> > 0x0100 chip_id 0x sub 168c:cafe
> > [   14.702997] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
> > tracing 0 dfs 1 testmode 1
> > [   14.716459] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
> > api 5 features 
> > no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
> > crc32 4c56a386
> > [   15.973104] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
> > crc32 dd6d039c
> > [   19.753460] ath10k_pci :01:00.0: firmware crashed! (guid
> > ca7089d2-df9a-4f9d-8fa6-d1b908cf3220)
> > [   19.753494] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
> > 0x0100 chip_id 0x sub 168c:cafe
> > [   19.761307] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
> > tracing 0 dfs 1 testmode 1
> > [   19.773202] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
> > api 5 features 
> > no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
> > crc32 4c56a386
> > [   19.779887] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
> > crc32 dd6d039c
> > [   19.793511] ath10k_pci :01:00.0: htt-ver 0.0 wmi-op 6 htt-op 4
> > cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
> > [   19.803176] ath10k_pci :01:00.0: firmware register dump:
> > [   19.810956] ath10k_pci :01:00.0: [00]: 0x0100 0x15B3
> > 0x009CBB38 0x00975B31
> > [   19.816861] ath10k_pci :01:00.0: [04]: 0x009CBB38 0x00060530
> > 0x0011 0x00415760
> > [   19.824587] ath10k_pci :01:00.0: [08]: 0x00417E6C 0x0040
> > 0x0001 0x00422990
> > [   19.832485] ath10k_pci :01:00.0: [12]: 0x0009 0x
> > 0x00973B25 0x00973B47
> > [   19.840384] ath10k_pci :01:00.0: [16]: 0x009CBB38 0x000CEEA7
> > 0x 0x
> > [   19.848284] ath10k_pci :01:00.0: [20]: 0x409CBB38 0x004068DC
> > 0x0001 0x00403628
> > [   19.856183] ath10k_pci :01:00.0: [24]: 0x809814EF 0x0040693C
> > 0x0049 0xC09CBB38
> > [   19.864083] ath10k_pci :01:00.0: [28]: 0x800DF216 0x004069AC
> > 0x0004 0x00415300
> > [   19.871983] ath10k_pci :01:00.0: [32]: 0x800C383A 0x004069DC
> > 0x00415160 0x0040
> > [   19.879881] ath10k_pci :01:00.0: [36]: 0x809800A3 0x00406A0C
> > 0x00415170 0x009C41F8
> > [   19.887781] ath10k_pci :01:00.0: [40]: 0x8098003A 0x00406A5C
> > 0x0040 0x00400600
> > [   19.895680] ath10k_pci :01:00.0: [44]: 0x809607C1 0x00406A8C
> > 0xD8400100 0x00406A9C
> > [   19.903579] ath10k_pci :01:00.0: [48]: 0x80960892 0x00406AAC
> > 0x 0x0008
> > [   19.911479] ath10k_pci :01:00.0: [52]: 0x80960E39 0x00406ACC
> > 0x0040 0x00400600
> > [   19.919378] ath10k_pci :01:00.0: [56]: 0x80960E9D 0x00406AEC
> > 0x 0x00400600
> > [   19.927277] ath10k_pci :01:00.0: Copy Engine register dump:
> > [   19.935181] ath10k_pci :01:00.0: [00]: 0x0004a000  11  11  12  11
> > [   19.940994] ath10k_pci :01:00.0: [01]: 0x0004a400  11  11  10  11
> > [   19.947590] ath10k_pci :01:00.0: [02]: 0x0004a800   0   0  63   0
> > [   19.954014] ath10k_pci :01:00.0: [03]: 0x0004ac00   0   0   0   0
> > [   19.960439] ath10k_pci :01:00.0: [04]: 0x0004b000   0   0   0   0
> > [   19.966862] ath10k_pci :01:00.0: [05]: 0x0004b400   0   0   0   0
> > [   19.973285] ath10k_pci :01:00.0: [06]: 0x0004b800   0   0   0   0
> > [   19.979709] ath10k_pci :01:00.0: [07]: 0x0004bc00   1   1   1   1
> > [   19.98

Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-19 Thread Sebastian Gottschall
can you tell me how to reproduce this crash? i have 2 r7800 running with 
dd-wrt but no crashes


Am 19.09.2018 um 22:37 schrieb Bruno Rosset:

Hi all,

I get a firmware crash using latest openwrt 18.06.1 on the Netgear
R7800 with stock firmware
Dmesg is :
[   13.804366] ath10k_pci :01:00.0: assign IRQ: got 67
[   13.804805] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
[   13.804887] ath10k_pci :01:00.0: enabling bus mastering
[   13.805346] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[   13.974787] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[   13.974827] ath10k_pci :01:00.0: Falling back to user helper
[   14.304794] ath10k_pci :01:00.0: Direct firmware load for
ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
[   14.304857] ath10k_pci :01:00.0: Falling back to user helper
[   14.337111] firmware ath10k!QCA9984!hw1.0!firmware-6.bin:
firmware_loading_store: map pages failed
[   14.702947] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[   14.702997] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   14.716459] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
crc32 4c56a386
[   15.973104] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
crc32 dd6d039c
[   19.753460] ath10k_pci :01:00.0: firmware crashed! (guid
ca7089d2-df9a-4f9d-8fa6-d1b908cf3220)
[   19.753494] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[   19.761307] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   19.773202] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
crc32 4c56a386
[   19.779887] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
crc32 dd6d039c
[   19.793511] ath10k_pci :01:00.0: htt-ver 0.0 wmi-op 6 htt-op 4
cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[   19.803176] ath10k_pci :01:00.0: firmware register dump:
[   19.810956] ath10k_pci :01:00.0: [00]: 0x0100 0x15B3
0x009CBB38 0x00975B31
[   19.816861] ath10k_pci :01:00.0: [04]: 0x009CBB38 0x00060530
0x0011 0x00415760
[   19.824587] ath10k_pci :01:00.0: [08]: 0x00417E6C 0x0040
0x0001 0x00422990
[   19.832485] ath10k_pci :01:00.0: [12]: 0x0009 0x
0x00973B25 0x00973B47
[   19.840384] ath10k_pci :01:00.0: [16]: 0x009CBB38 0x000CEEA7
0x 0x
[   19.848284] ath10k_pci :01:00.0: [20]: 0x409CBB38 0x004068DC
0x0001 0x00403628
[   19.856183] ath10k_pci :01:00.0: [24]: 0x809814EF 0x0040693C
0x0049 0xC09CBB38
[   19.864083] ath10k_pci :01:00.0: [28]: 0x800DF216 0x004069AC
0x0004 0x00415300
[   19.871983] ath10k_pci :01:00.0: [32]: 0x800C383A 0x004069DC
0x00415160 0x0040
[   19.879881] ath10k_pci :01:00.0: [36]: 0x809800A3 0x00406A0C
0x00415170 0x009C41F8
[   19.887781] ath10k_pci :01:00.0: [40]: 0x8098003A 0x00406A5C
0x0040 0x00400600
[   19.895680] ath10k_pci :01:00.0: [44]: 0x809607C1 0x00406A8C
0xD8400100 0x00406A9C
[   19.903579] ath10k_pci :01:00.0: [48]: 0x80960892 0x00406AAC
0x 0x0008
[   19.911479] ath10k_pci :01:00.0: [52]: 0x80960E39 0x00406ACC
0x0040 0x00400600
[   19.919378] ath10k_pci :01:00.0: [56]: 0x80960E9D 0x00406AEC
0x 0x00400600
[   19.927277] ath10k_pci :01:00.0: Copy Engine register dump:
[   19.935181] ath10k_pci :01:00.0: [00]: 0x0004a000  11  11  12  11
[   19.940994] ath10k_pci :01:00.0: [01]: 0x0004a400  11  11  10  11
[   19.947590] ath10k_pci :01:00.0: [02]: 0x0004a800   0   0  63   0
[   19.954014] ath10k_pci :01:00.0: [03]: 0x0004ac00   0   0   0   0
[   19.960439] ath10k_pci :01:00.0: [04]: 0x0004b000   0   0   0   0
[   19.966862] ath10k_pci :01:00.0: [05]: 0x0004b400   0   0   0   0
[   19.973285] ath10k_pci :01:00.0: [06]: 0x0004b800   0   0   0   0
[   19.979709] ath10k_pci :01:00.0: [07]: 0x0004bc00   1   1   1   1
[   19.986132] ath10k_pci :01:00.0: [08]: 0x0004c000   0   0 127   0
[   19.992556] ath10k_pci :01:00.0: [09]: 0x0004c400   1   1   1   1
[   19.998980] ath10k_pci :01:00.0: [10]: 0x0004c800   0   0   0   0
[   20.005403] ath10k_pci :01:00.0: [11]: 0x0004cc00   0   0   0   0
[   20.795948] ath10k_pci :01:00.0: failed to receive control
response completion, polling..
[   21.835766] ath10k_pci :01:00.0: ctl_resp never came in (-110)
[   21.835810] ath10k_pci :01:00.0: failed to connect to HTC: -110
[   21.915174] ath10k_pci :01:00.0: could not init core (-110)
[   21.915620] ath10k_pci :01:00.0: could not probe fw (-110)
[   21.920266] ath10k_pci 0001:01:00.0: assign IRQ: got 100
[   21.921197] ath10k_pci 0001:01:00.0: enabling device (0140 ->

Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-19 Thread Bruno Rosset
Hi,

Done, thanks
Le mer. 19 sept. 2018 à 22:45, Ben Greear  a écrit :
>
> On 09/19/2018 01:37 PM, Bruno Rosset wrote:
> > Hi all,
> >
>
> > Various tests with others firmware from candelatech , stock LEDE 17.01
> > or dd-wrt give me firmware crash also
>
> Please open a bug for the candela firmware crash, I might be able to figure
> out why it crashes:
>
> https://github.com/greearb/ath10k-ct/issues
>
> https://www.candelatech.com/ath10k-bugs.php
>
> Thanks,
> Ben
>
>
> --
> Ben Greear 
> Candela Technologies Inc  http://www.candelatech.com
>


Re: Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-19 Thread Ben Greear

On 09/19/2018 01:37 PM, Bruno Rosset wrote:

Hi all,




Various tests with others firmware from candelatech , stock LEDE 17.01
or dd-wrt give me firmware crash also


Please open a bug for the candela firmware crash, I might be able to figure
out why it crashes:

https://github.com/greearb/ath10k-ct/issues

https://www.candelatech.com/ath10k-bugs.php

Thanks,
Ben


--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com



Netgear R7800 - ath10k QCA 9984 firmware crash

2018-09-19 Thread Bruno Rosset
Hi all,

I get a firmware crash using latest openwrt 18.06.1 on the Netgear
R7800 with stock firmware
Dmesg is :
[   13.804366] ath10k_pci :01:00.0: assign IRQ: got 67
[   13.804805] ath10k_pci :01:00.0: enabling device (0140 -> 0142)
[   13.804887] ath10k_pci :01:00.0: enabling bus mastering
[   13.805346] ath10k_pci :01:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 reset_mode 0
[   13.974787] ath10k_pci :01:00.0: Direct firmware load for
ath10k/pre-cal-pci-:01:00.0.bin failed with error -2
[   13.974827] ath10k_pci :01:00.0: Falling back to user helper
[   14.304794] ath10k_pci :01:00.0: Direct firmware load for
ath10k/QCA9984/hw1.0/firmware-6.bin failed with error -2
[   14.304857] ath10k_pci :01:00.0: Falling back to user helper
[   14.337111] firmware ath10k!QCA9984!hw1.0!firmware-6.bin:
firmware_loading_store: map pages failed
[   14.702947] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[   14.702997] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   14.716459] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
crc32 4c56a386
[   15.973104] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
crc32 dd6d039c
[   19.753460] ath10k_pci :01:00.0: firmware crashed! (guid
ca7089d2-df9a-4f9d-8fa6-d1b908cf3220)
[   19.753494] ath10k_pci :01:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[   19.761307] ath10k_pci :01:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs 1 testmode 1
[   19.773202] ath10k_pci :01:00.0: firmware ver 10.4-3.5.3-00053
api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
crc32 4c56a386
[   19.779887] ath10k_pci :01:00.0: board_file api 2 bmi_id 0:31
crc32 dd6d039c
[   19.793511] ath10k_pci :01:00.0: htt-ver 0.0 wmi-op 6 htt-op 4
cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[   19.803176] ath10k_pci :01:00.0: firmware register dump:
[   19.810956] ath10k_pci :01:00.0: [00]: 0x0100 0x15B3
0x009CBB38 0x00975B31
[   19.816861] ath10k_pci :01:00.0: [04]: 0x009CBB38 0x00060530
0x0011 0x00415760
[   19.824587] ath10k_pci :01:00.0: [08]: 0x00417E6C 0x0040
0x0001 0x00422990
[   19.832485] ath10k_pci :01:00.0: [12]: 0x0009 0x
0x00973B25 0x00973B47
[   19.840384] ath10k_pci :01:00.0: [16]: 0x009CBB38 0x000CEEA7
0x 0x
[   19.848284] ath10k_pci :01:00.0: [20]: 0x409CBB38 0x004068DC
0x0001 0x00403628
[   19.856183] ath10k_pci :01:00.0: [24]: 0x809814EF 0x0040693C
0x0049 0xC09CBB38
[   19.864083] ath10k_pci :01:00.0: [28]: 0x800DF216 0x004069AC
0x0004 0x00415300
[   19.871983] ath10k_pci :01:00.0: [32]: 0x800C383A 0x004069DC
0x00415160 0x0040
[   19.879881] ath10k_pci :01:00.0: [36]: 0x809800A3 0x00406A0C
0x00415170 0x009C41F8
[   19.887781] ath10k_pci :01:00.0: [40]: 0x8098003A 0x00406A5C
0x0040 0x00400600
[   19.895680] ath10k_pci :01:00.0: [44]: 0x809607C1 0x00406A8C
0xD8400100 0x00406A9C
[   19.903579] ath10k_pci :01:00.0: [48]: 0x80960892 0x00406AAC
0x 0x0008
[   19.911479] ath10k_pci :01:00.0: [52]: 0x80960E39 0x00406ACC
0x0040 0x00400600
[   19.919378] ath10k_pci :01:00.0: [56]: 0x80960E9D 0x00406AEC
0x 0x00400600
[   19.927277] ath10k_pci :01:00.0: Copy Engine register dump:
[   19.935181] ath10k_pci :01:00.0: [00]: 0x0004a000  11  11  12  11
[   19.940994] ath10k_pci :01:00.0: [01]: 0x0004a400  11  11  10  11
[   19.947590] ath10k_pci :01:00.0: [02]: 0x0004a800   0   0  63   0
[   19.954014] ath10k_pci :01:00.0: [03]: 0x0004ac00   0   0   0   0
[   19.960439] ath10k_pci :01:00.0: [04]: 0x0004b000   0   0   0   0
[   19.966862] ath10k_pci :01:00.0: [05]: 0x0004b400   0   0   0   0
[   19.973285] ath10k_pci :01:00.0: [06]: 0x0004b800   0   0   0   0
[   19.979709] ath10k_pci :01:00.0: [07]: 0x0004bc00   1   1   1   1
[   19.986132] ath10k_pci :01:00.0: [08]: 0x0004c000   0   0 127   0
[   19.992556] ath10k_pci :01:00.0: [09]: 0x0004c400   1   1   1   1
[   19.998980] ath10k_pci :01:00.0: [10]: 0x0004c800   0   0   0   0
[   20.005403] ath10k_pci :01:00.0: [11]: 0x0004cc00   0   0   0   0
[   20.795948] ath10k_pci :01:00.0: failed to receive control
response completion, polling..
[   21.835766] ath10k_pci :01:00.0: ctl_resp never came in (-110)
[   21.835810] ath10k_pci :01:00.0: failed to connect to HTC: -110
[   21.915174] ath10k_pci :01:00.0: could not init core (-110)
[   21.915620] ath10k_pci :01:00.0: could not probe fw (-110)
[   21.920266] ath10k_pci 0001:01:00.0: assign IRQ: got 100
[   21.921197] ath10k_pci 0001:01:00.0: enabling device (0140 -> 0142)
[   21.926032] ath10k_pci 0001:01:00.0: enabling bus mastering
[   21.926715] ath10k_pci 0001:01:00.0: pci irq msi oper_irq_mode 2
irq_mo