Flyspray:: Flyspray::OpenWrt/LEDE Project: Recently opened tasks https://bugs.openwrt.org/ 2019-01-18T00:36:09Z FS#2062: MTU is not set to 1508/1500 when using PPPoE 2019-01-18T00:36:09Z 2019-01-18T00:36:09Z

TP-LINK Archer C7, OpenWrt 18.06.1 r7258-5eb055306f / LuCI openwrt-18.06 branch (git-18.228.31946-f64b152).

Use PPPoE for WAN. Set MTU to 1508.

Observe ifconfig result. MTU is set at 1492, it should be 1500.

Add

config interface ‘eth0’

option ifname 'eth0'
option mtu '1508'

to /etc/config/network, ensure PPPoE MTU (as above) is set to 1508 and restart the network/reboot the router.

Observe ifconfig result. MTU is set at 1500 as expected.

Alec Robertson https://bugs.openwrt.org/:2062
FS#2061: Different names for the same targets, let's decide: ALFA-NX, ALFANX or alfa-nx ? 2019-01-17T14:08:56Z 2019-01-17T14:08:56Z

I’m doing a tool that helps for compilation (I’m working based on lede 17.01.4). With these targets I had no problems, the name is the same everywhere. yay!, but with alfa-nx yes, this name is not clear, depends where you find it the name is different

here is ALFA-NX

# dmesg | grep -i board
[    0.000000] MyLoader: sysp=b9c9f1a8, boardp=9b949905, parts=b9c9f188
[    0.000000] Kernel command line:  board=ALFA-NX console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,6144k(rootfs),1600k(kernel),64k(nvram),64k(art)ro,7744k@0x50000(firmware) rootfstype=squashfs,jffs2 noinitrd

here is ALFANX

make info | grep 'ALFANX' -A2

ALFANX:
    ALFA Network N2/N5 board
    Packages: 

here is alfa-nx (the output target in compilation)

lede-imagebuilder-17.01.4-ar71xx-generic.Linux-x86_64/bin/targets/ar71xx/generic/lede-17.01.4-ar71xx-generic-alfa-nx-squashfs-sysupgrade.bin

Do you agree that the same name should be everywhere? I think it should be alfa-nx (as the other profiles are 100% lowercase)

I can solve this locally putting an if statement (doing an exception), but I think it is better to have good universal names everywhere.

guifipedro https://bugs.openwrt.org/:2061
FS#2060: Axis IP cameras do not get stateful IPv6 addresses anymore 2019-01-16T12:33:27Z 2019-01-15T20:43:55Z

Same report as in the GitHub issue I created, just opening one here as well in case this tracker is preferred:
https://github.com/openwrt/odhcpd/issues/121

Since updating to the latest OpenWRT a few weeks ago, I noticed that my Axis IP cameras do not get a stateful IPv6 anymore, which worked fine before.

Since they receive NOTONLINK responses, I have the feeling that the issue got introduced with commit a2ffc5986cd35bea983b81b28b8a656e3b81fdf1. Might be a shitty dhcpv6 implementation on the camera, I don’t know and I’m not familiar enough with DHCPv6 to see a bad implementation just from looking at the code.

The code of the “mdhcp6” client the camera uses is available in [this git repo](http://git.savannah.nongnu.org/cgit/mdhcp6.git/tree/src/dhcpv6.c). Not sure if it’s 100% up to date though, but I can reproduce the issue reliably.

Here’s a pcap on my older router running LEDE 17.01.3: [mdhcp6-lede-17.01.3.pcap.gz](https://github.com/openwrt/odhcpd/files/2761312/mdhcp6-lede-17.01.3.pcap.gz)
The advertise/request messages don’t contain anything related to the configured IP (via the ‘hostid’ option), but the final reply contains the correct IP.

And here’s a pcap on another router running the latest OpenWRT 18.06.1, coming from the exact same mdhcp6 client (just running on a different machine since they are different networks, hence the different DUID): [mdhcp6-openwrt-18.06.1.pcap.gz](https://github.com/openwrt/odhcpd/files/2761325/mdhcp6-openwrt-18.06.1.pcap.gz)

I’m not sure where the problem is - in the server or the client (more likely, since all other dhcpv6 clients work perfectly fine). But I’d appreciate some help - if it’s a bug in the client (not sending any IA_NA requests in the solicit seems strange to me), I’d like to forward details to the camera vendor. They release firmware updates quite often so I think the chance that they actually fix their dhcpv6 client if it’s broken is quite high.

Adrian https://bugs.openwrt.org/:2060
FS#2059: uclient-fetch not working at all on http (not https) connections. 2019-01-15T14:34:32Z 2019-01-15T14:34:32Z

I just tried today’s trunk snapshot on my Turris Omnia; everything’s working fine apart from uclient-fetch. I noticed the failure because the ddns updater stopped working. If I install wget, everything works, since wget replaces uclient-fetch. Sample output follows.

Bad:

root@heimdall:/tmp# uclient-fetch http://perdu.com/ Downloading ‘http://perdu.com/’ Failed to establish connection
root@heimdall:/tmp#

Good:

root@heimdall:/tmp# wget http://perdu.com/ –2019-01-15 14:31:09– http://perdu.com/ Resolving perdu.com... 208.97.177.124
Connecting to perdu.com|208.97.177.124|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 204 [text/html]
Saving to: ‘index.html’

index.html 100%[==================================================================================================================================================================>] 204 --.-KB/s in 0s 2019-01-15 14:31:10 (16.4 MB/s) - 'index.html' saved [204/204] root@heimdall:/tmp# Image builder command line: make image PROFILE=turris-omnia PACKAGES="-kmod-ath9k -dnsmasq -odhcpd -odhcpd-ipv6only -odhcp6c -ppp -ppp-mod-pppoe ddns-scripts dnsmasq-full ethtool haveged htop ipset kmod-ipt-raw kmod-ipt-raw6 kmod-nf-nathelper-extra kmod-wireguard nano sqm-scripts tcpdump tor wget wireguard-tools zram-swap"

rsalvaterra https://bugs.openwrt.org/:2059
FS#2058: ath79: valgrind fails to build for mip32 2019-01-13T19:01:52Z 2019-01-13T19:01:52Z

Building the core system (current master)

tip commit:

commit 0e8d5ff0fc1cd8eb5236e6e497c340ceb21340fe
Author: Felix Fietkau <nbd@nbd.name>
Date:   Fri Jan 11 17:23:29 2019 +0100

    mt76: fix typo in version number

    Signed-off-by: Felix Fietkau <nbd@nbd.name>

( only for mip32 (specifically ath79 for a variety of boards) with CONFIG_ALL=y fails on building valgrind with:

{standard input}:91723: Error: opcode not supported on this processor: mips32 (mips32) `floor.l.s $f24,$f24'                    
{standard input}:91740: Error: `fp=64' used with a 32-bit fpu
{standard input}:91744: Error: opcode not supported on this processor: mips32 (mips32) `floor.l.d $f24,$f24'                    
{standard input}:91761: Error: `fp=64' used with a 32-bit fpu
{standard input}:91765: Error: opcode not supported on this processor: mips32 (mips32) `round.l.s $f24,$f24'                    
{standard input}:91782: Error: `fp=64' used with a 32-bit fpu
{standard input}:91786: Error: opcode not supported on this processor: mips32 (mips32) `round.l.d $f24,$f24'                    
{standard input}:91803: Error: `fp=64' used with a 32-bit fpu
{standard input}:91807: Error: opcode not supported on this processor: mips32 (mips32) `trunc.l.s $f24,$f24'                    
{standard input}:91824: Error: `fp=64' used with a 32-bit fpu
{standard input}:91828: Error: opcode not supported on this processor: mips32 (mips32) `trunc.l.d $f24,$f24'                    
lto-wrapper: fatal error: mips-openwrt-linux-musl-gcc returned 1 exit status                                                    
compilation terminated.
/home/daniel/Build/openwrt-ath79/staging_dir/toolchain-mips_24kc_gcc-7.4.0_musl/lib/gcc/mips-openwrt-linux-musl/7.4.0/../../../../mips-openwrt-linux-musl/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
Daniel Dickinson https://bugs.openwrt.org/:2058
FS#2057: /etc/init.d/umount runs after other block devices must stop 2019-01-13T18:38:36Z 2019-01-13T18:38:36Z

Supply the following if possible:

- Device problem occurs on

All.

- Software versions of OpenWrt/LEDE release, packages, etc.

18.06.01 & snapshots

- Steps to reproduce

 

Setup another block device that should be stopped after umount, e.g. cryptsetup, lvm2, or mdadm

Performing umount as K99umount allows very few things to run afterwards. Ideally, it would be K96umount or K97umount, which would allow for running multiple levels of stops afterwards. There should be at least two levels after umount.

For example, setting K98umount would still cause problems for K99cryptsetup & K99lvm2 because lvm2 must stop before cryptsetup and both must stop after mount.

Changing S99umount may also affect these other packages:

STOP=98 boot
STOP=98 kdump.init
STOP=98 mdadm.init
STOP=99 conserver.init
STOP=99 kismet_drone.init
STOP=99 kismet_server.init
STOP=99 socat.init

Joseph Tingiris https://bugs.openwrt.org/:2057
FS#2056: odhcp misbehaves with multiple MACs for single host on DHCP configuration 2019-01-12T16:51:20Z 2019-01-12T16:51:20Z

According to the Static Leases section on DHCP's User Guide it should be possible to list several MAC addresses for the same host. Indeed everything works as expected with dnsmasq, and my host gets the expected IPv4 when using any of the listed MAC addresses.

However odhcp misbehaves when I list more than one MAC. With a single MAC on ‘option mac’, my host gets the expected IPv6, with the suffix defined under hostid. If I place two or more MACs on that option, odhcp fails to honor my rules and attributes a dynamic IPv6 with a random suffix.

Here is an example config that produces the erroneous behavior of odhcp.

config host
        option name 'host4'
        option ip '192.168.1.4'
        option hostid '4'
        option duid '00112233445566778899'
        option mac '00:11:22:33:44:55, 66:77:88:99:aa:bb'

(Separating the MACs list with either commas and spaces yields the same result. The DHCP User’s Guide has contradictory info on how the list should be separated, but it seems that both work for dnsmasq.)

dllud https://bugs.openwrt.org/:2056
FS#2055: conntrack -f ipv6 -L dumps IPv4 table, not IPv6 2019-01-11T14:08:30Z 2019-01-11T14:08:30Z

Supply the following if possible:
- Device problem occurs on
TP-LINK wdr4300

- Software versions of OpenWrt/LEDE release, packages, etc.
18.06.1 fully up-to-date as of writing

- Steps to reproduce

# conntrack -f ipv6 -L -nv

This produces the IPv4 table, as if

-f ipv6

was not even specified.

Brian J. Murrell https://bugs.openwrt.org/:2055
FS#2054: Ath9k RXORN storm 2019-01-11T03:24:10Z 2019-01-11T03:24:10Z

the ath9k don’t clear RXORN bit . I think The write maybe think

 RXEOL  and RXORN shuold come together

but I test found the RXORN come only , In this situation the driver not
clear the RXORN bit , so driver can not recevice any pakcet ,I just recevie
RXORN interrupt


李鹏 https://bugs.openwrt.org/:2054
FS#2053: Regular crashes of ath10k-ct driver on ZyXEL NBG6817 2019-01-10T10:04:06Z 2019-01-10T10:04:06Z

Model ZyXEL NBG6817
Architecture ARMv7 Processor rev 0 (v7l)
Firmware Version OpenWrt SNAPSHOT r9010-adc8b374e3 / LuCI Master (git-19.007.66460-4edac36)
Kernel Version 4.14.91
Local Time Thu Jan 10 10:57:42 2019
Uptime 16h 32m 57s
Load Average 0.40, 0.34, 0.18

Sadly there isn’t any simple way to reproduce, but they seem to be happening somewhat regularly. Since I put the device to use, 1 yesterday, 2 today.

Jan 10 09:26:10 hs14 kernel: [54084.922093] ath10k_pci 0001:01:00.0: firmware crashed! (guid ec43bc35-1369-4765-b62f-6ccef1fb3d02)
Jan 10 09:26:10 hs14 kernel: [54084.922155] ath10k_pci 0001:01:00.0: qca9984/qca9994 hw1.0 target 0x01000000 chip_id 0x00000000 sub 168c:cafe
Jan 10 09:26:10 hs14 kernel: [54084.929958] ath10k_pci 0001:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
Jan 10 09:26:10 hs14 kernel: [54084.942242] ath10k_pci 0001:01:00.0: firmware ver 10.4b-ct-9984-fW-012-81e1edd54 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,reg
dump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT crc32 0391c067
Jan 10 09:26:10 hs14 kernel: [54084.951289] ath10k_pci 0001:01:00.0: board_file api 2 bmi_id 0:2 crc32 cf58c3bc
Jan 10 09:26:10 hs14 kernel: [54084.972926] ath10k_pci 0001:01:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
Jan 10 09:26:10 hs14 kernel: [54084.982076] ath10k_pci 0001:01:00.0: firmware register dump:
Jan 10 09:26:10 hs14 kernel: [54084.990109] ath10k_pci 0001:01:00.0: [00]: 0x0000000A 0x000015B3 0x009A582B 0x00975B31
Jan 10 09:26:10 hs14 kernel: [54084.996013] ath10k_pci 0001:01:00.0: [04]: 0x009A582B 0x00060B30 0x00000000 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.003740] ath10k_pci 0001:01:00.0: [08]: 0x00000000 0x004602A4 0x00406764 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.011640] ath10k_pci 0001:01:00.0: [12]: 0x00000009 0x00000000 0x00973ABC 0x00973AD2
Jan 10 09:26:10 hs14 kernel: [54085.019537] ath10k_pci 0001:01:00.0: [16]: 0x00973AB0 0x0096398A 0x009606CA 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.027437] ath10k_pci 0001:01:00.0: [20]: 0x409A582B 0x0040660C 0x00000005 0x000000FF
Jan 10 09:26:10 hs14 kernel: [54085.035336] ath10k_pci 0001:01:00.0: [24]: 0x809A698A 0x0040666C 0x00000005 0xC09A582B
Jan 10 09:26:10 hs14 kernel: [54085.043235] ath10k_pci 0001:01:00.0: [28]: 0x809A7EF9 0x0040669C 0x0045F0D0 0x0045FCA8
Jan 10 09:26:10 hs14 kernel: [54085.051135] ath10k_pci 0001:01:00.0: [32]: 0x809A8D32 0x0040672C 0x0045FCE4 0x00406850
Jan 10 09:26:10 hs14 kernel: [54085.059035] ath10k_pci 0001:01:00.0: [36]: 0x809A8D62 0x0040684C 0x0042D864 0x0042EF70
Jan 10 09:26:10 hs14 kernel: [54085.066934] ath10k_pci 0001:01:00.0: [40]: 0x80985E4B 0x0040689C 0x00000000 0x0045A9F4
Jan 10 09:26:10 hs14 kernel: [54085.074833] ath10k_pci 0001:01:00.0: [44]: 0x80994A73 0x004068BC 0x0042ED20 0x0045A9F4
Jan 10 09:26:10 hs14 kernel: [54085.082732] ath10k_pci 0001:01:00.0: [48]: 0x8098FC30 0x004068DC 0x0042ED20 0x00000000
Jan 10 09:26:10 hs14 kernel: [54085.090631] ath10k_pci 0001:01:00.0: [52]: 0x80963AD3 0x00406A7C 0x0042ED20 0x0098FC28
Jan 10 09:26:10 hs14 kernel: [54085.098530] ath10k_pci 0001:01:00.0: [56]: 0x80960E80 0x00406A9C 0x0000001F 0x00400000
Jan 10 09:26:10 hs14 kernel: [54085.106429] ath10k_pci 0001:01:00.0: Copy Engine register dump:
Jan 10 09:26:10 hs14 kernel: [54085.114333] ath10k_pci 0001:01:00.0: [00]: 0x0004a000  13  13   3   3
Jan 10 09:26:10 hs14 kernel: [54085.120150] ath10k_pci 0001:01:00.0: [01]: 0x0004a400  10  10 432 433
Jan 10 09:26:10 hs14 kernel: [54085.126747] ath10k_pci 0001:01:00.0: [02]: 0x0004a800  46  46 109 110
Jan 10 09:26:10 hs14 kernel: [54085.133170] ath10k_pci 0001:01:00.0: [03]: 0x0004ac00  21  21  23  21
Jan 10 09:26:10 hs14 kernel: [54085.139594] ath10k_pci 0001:01:00.0: [04]: 0x0004b000 2043 1937  30  30
Jan 10 09:26:10 hs14 kernel: [54085.146018] ath10k_pci 0001:01:00.0: [05]: 0x0004b400   1   1 128 129
Jan 10 09:26:10 hs14 kernel: [54085.152441] ath10k_pci 0001:01:00.0: [06]: 0x0004b800  10  10  10  10
Jan 10 09:26:10 hs14 kernel: [54085.159039] ath10k_pci 0001:01:00.0: [07]: 0x0004bc00   1   1   1   1
Jan 10 09:26:10 hs14 kernel: [54085.165462] ath10k_pci 0001:01:00.0: [08]: 0x0004c000   0   0 127   0
Jan 10 09:26:10 hs14 kernel: [54085.171886] ath10k_pci 0001:01:00.0: [09]: 0x0004c400   1   1   1   1
Jan 10 09:26:10 hs14 kernel: [54085.178310] ath10k_pci 0001:01:00.0: [10]: 0x0004c800   0   0   0   0
Jan 10 09:26:10 hs14 kernel: [54085.184733] ath10k_pci 0001:01:00.0: [11]: 0x0004cc00   0   0   0   0
Jan 10 09:26:10 hs14 kernel: [54085.193175] ath10k_pci 0001:01:00.0: debug log header, dbuf: 0x423818  dropped: 0
Jan 10 09:26:10 hs14 kernel: [54085.198590] ath10k_pci 0001:01:00.0: [0] next: 0x423800 buf: 0x419610 sz: 1500 len: 252 count: 9 free: 0
Jan 10 09:26:10 hs14 kernel: [54085.206060] ath10k_pci 0001:01:00.0: ath10k_pci ATH10K_DBG_BUFFER:
Jan 10 09:26:10 hs14 kernel: [54085.214587] ath10k: [0000]: 034C7883 14004C01 71104441 01050F98 00019003 00000000 0000FFFF 034C7884
Jan 10 09:26:10 hs14 kernel: [54085.220581] ath10k: [0008]: 14004C01 71108880 00000000 00D80000 00000000 00000FF0 034C7884 14004C01
Jan 10 09:26:10 hs14 kernel: [54085.229521] ath10k: [0016]: 71108880 00010000 00D80000 00000000 00000000 034C7884 14004C01 71108880
Jan 10 09:26:10 hs14 kernel: [54085.238548] ath10k: [0024]: 00020000 00D80000 00000000 00000000 034C7884 14004C01 71108880 00030000
Jan 10 09:26:10 hs14 kernel: [54085.247576] ath10k: [0032]: 00D80000 00000000 00000000 034C7884 14004C01 71108880 00040000 00D80000
Jan 10 09:26:10 hs14 kernel: [54085.256604] ath10k: [0040]: 00000000 00000000 034C7884 14004C01 71108880 00050000 00D80000 00000000
Jan 10 09:26:10 hs14 kernel: [54085.265642] ath10k: [0048]: 00000000 034C7884 14004C01 71108880 00060000 00D80000 00000000 00000000
Jan 10 09:26:10 hs14 kernel: [54085.274659] ath10k: [0056]: 034C7885 17FC0001 009A582B 000015B3 000015B3 004064FC 91104569
Jan 10 09:26:10 hs14 kernel: [54085.283686] ath10k_pci 0001:01:00.0: ATH10K_END
Jan 10 09:26:10 hs14 kernel: [54085.293030] ath10k_pci 0001:01:00.0: [1] next: 0x423818 buf: 0x419020 sz: 1500 len: 0 count: 0 free: 0
Jan 10 09:26:10 hs14 kernel: [54085.336026] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Jan 10 09:26:10 hs14 kernel: [54085.361017] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1bf400 vdev: 0 addr: 48:45:20:c2:27:84
Jan 10 09:26:10 hs14 kernel: [54085.361055] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1be400 vdev: 0 addr: 64:a2:f9:31:0f:98
Jan 10 09:26:10 hs14 kernel: [54085.371034] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1be200 vdev: 0 addr: 84:c7:ea:8f:41:c7
Jan 10 09:26:10 hs14 kernel: [54085.381962] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1bf000 vdev: 0 addr: 6c:c7:ec:46:de:44
Jan 10 09:26:10 hs14 kernel: [54085.392896] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer da1bfc00 vdev: 0 addr: 88:d7:f6:9f:51:10
Jan 10 09:26:10 hs14 kernel: [54085.403829] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer dbd42e00 vdev: 1 addr: 5e:e2:8c:f2:fe:80
Jan 10 09:26:10 hs14 kernel: [54085.414796] ath10k_pci 0001:01:00.0: removing peer, cleanup-all, deleting: peer dbbdc200 vdev: 0 addr: 5c:e2:8c:f2:fe:80
Jan 10 09:26:10 hs14 kernel: [54085.516577] ieee80211 phy1: Hardware restart was requested
Jan 10 09:26:11 hs14 kernel: [54085.597874] ath10k_pci 0001:01:00.0: Invalid state: 3 in ath10k_htt_tx_32, warning will not be repeated.
Jan 10 09:26:11 hs14 kernel: [54085.597905] ------------[ cut here ]------------
Jan 10 09:26:11 hs14 kernel: [54085.606562] WARNING: CPU: 1 PID: 0 at /var/lib/buildbot/slaves/tictex-02/ipq806x_generic/build/build_dir/target-arm_cortex-a15+neon-vfpv4_musl_eabi/linux-ipq806x/ath10k-ct-2018-12-20-118e16da/ath10k-4.19/htt_tx.c:1250 ath10k_htt_tx_32+0xf0/0x9e0 [ath10k_core]
Jan 10 09:26:11 hs14 kernel: [54085.611507] Modules linked in: pppoe ppp_async ath10k_pci ath10k_core ath pppox ppp_generic nf_conntrack_ipv6 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_FLOWOFFLOAD xt_CT slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables crc_ccitt compat act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress ledtrig_usbport ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables leds_gpio
Jan 10 09:26:11 hs14 kernel: [54085.682720]  xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_of_simple ohci_platform ohci_hcd phy_qcom_dwc3 ahci ehci_platform sd_mod ahci_platform libahci_platform libahci libata scsi_mod ehci_hcd gpio_button_hotplug ext4 jbd2 mbcache crc32c_generic
Jan 10 09:26:11 hs14 kernel: [54085.704952] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.14.91 #0
Jan 10 09:26:11 hs14 kernel: [54085.726639] Hardware name: Generic DT based system
Jan 10 09:26:11 hs14 kernel: [54085.732654] [<c030f58c>] (unwind_backtrace) from [<c030b7a4>] (show_stack+0x14/0x20)
Jan 10 09:26:11 hs14 kernel: [54085.737240] [<c030b7a4>] (show_stack) from [<c07b26f8>] (dump_stack+0x88/0x9c)
Jan 10 09:26:11 hs14 kernel: [54085.745143] [<c07b26f8>] (dump_stack) from [<c0318ec4>] (__warn+0xf0/0x11c)
Jan 10 09:26:11 hs14 kernel: [54085.752167] [<c0318ec4>] (__warn) from [<c0318fb0>] (warn_slowpath_null+0x20/0x28)
Jan 10 09:26:11 hs14 kernel: [54085.759059] [<c0318fb0>] (warn_slowpath_null) from [<bf4a5c18>] (ath10k_htt_tx_32+0xf0/0x9e0 [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.766772] [<bf4a5c18>] (ath10k_htt_tx_32 [ath10k_core]) from [<bf48a0f8>] (ath10k_mac_op_set_bitrate_mask+0xc40/0xdac [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.776369] [<bf48a0f8>] (ath10k_mac_op_set_bitrate_mask [ath10k_core]) from [<bf48ff24>] (ath10k_mac_tx_push_txq+0x234/0x290 [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.788524] [<bf48ff24>] (ath10k_mac_tx_push_txq [ath10k_core]) from [<bf4901b4>] (ath10k_mac_op_wake_tx_queue+0x88/0x12c [ath10k_core])
Jan 10 09:26:11 hs14 kernel: [54085.801339] [<bf4901b4>] (ath10k_mac_op_wake_tx_queue [ath10k_core]) from [<bf3fefa4>] (ieee80211_unreserve_tid+0x658/0x718 [mac80211])
Jan 10 09:26:11 hs14 kernel: [54085.813569] [<bf3fefa4>] (ieee80211_unreserve_tid [mac80211]) from [<bf401c94>] (__ieee80211_subif_start_xmit+0x728/0x978 [mac80211])
Jan 10 09:26:11 hs14 kernel: [54085.825444] [<bf401c94>] (__ieee80211_subif_start_xmit [mac80211]) from [<bf4021d4>] (ieee80211_subif_start_xmit+0x2f0/0x310 [mac80211])
Jan 10 09:26:11 hs14 kernel: [54085.837553] [<bf4021d4>] (ieee80211_subif_start_xmit [mac80211]) from [<c069cd80>] (dev_hard_start_xmit+0xc8/0x154)
Jan 10 09:26:11 hs14 kernel: [54085.849828] [<c069cd80>] (dev_hard_start_xmit) from [<c069d54c>] (__dev_queue_xmit+0x630/0x7b0)
Jan 10 09:26:11 hs14 kernel: [54085.859983] [<c069d54c>] (__dev_queue_xmit) from [<c07917d4>] (br_dev_queue_push_xmit+0x144/0x168)
Jan 10 09:26:11 hs14 kernel: [54085.868662] [<c07917d4>] (br_dev_queue_push_xmit) from [<c0791830>] (br_forward_finish+0x38/0xa0)
Jan 10 09:26:11 hs14 kernel: [54085.877688] [<c0791830>] (br_forward_finish) from [<c0791980>] (__br_forward+0xe8/0x144)
Jan 10 09:26:11 hs14 kernel: [54085.886629] [<c0791980>] (__br_forward) from [<c0793624>] (br_handle_frame_finish+0x4fc/0x56c)
Jan 10 09:26:11 hs14 kernel: [54085.894788] [<c0793624>] (br_handle_frame_finish) from [<c0793a90>] (br_handle_frame+0x328/0x3c0)
Jan 10 09:26:11 hs14 kernel: [54085.903218] [<c0793a90>] (br_handle_frame) from [<c0698458>] (__netif_receive_skb_core+0x71c/0xbdc)
Jan 10 09:26:11 hs14 kernel: [54085.912154] [<c0698458>] (__netif_receive_skb_core) from [<c069a714>] (process_backlog+0xb0/0x164)
Jan 10 09:26:11 hs14 kernel: [54085.921008] [<c069a714>] (process_backlog) from [<c069e334>] (net_rx_action+0x144/0x31c)
Jan 10 09:26:11 hs14 kernel: [54085.930032] [<c069e334>] (net_rx_action) from [<c03015c8>] (__do_softirq+0xf0/0x264)
Jan 10 09:26:11 hs14 kernel: [54085.938285] [<c03015c8>] (__do_softirq) from [<c031d280>] (irq_exit+0xdc/0x148)
Jan 10 09:26:11 hs14 kernel: [54085.946006] [<c031d280>] (irq_exit) from [<c035a0d8>] (__handle_domain_irq+0xa8/0xc8)
Jan 10 09:26:11 hs14 kernel: [54085.953036] [<c035a0d8>] (__handle_domain_irq) from [<c0301488>] (gic_handle_irq+0x6c/0xb8)
Jan 10 09:26:11 hs14 kernel: [54085.961022] [<c0301488>] (gic_handle_irq) from [<c030c38c>] (__irq_svc+0x6c/0x90)
Jan 10 09:26:11 hs14 kernel: [54085.969176] Exception stack(0xdd45ff80 to 0xdd45ffc8)
Jan 10 09:26:11 hs14 kernel: [54085.976838] ff80: 00000001 00000000 00000000 c0315300 ffffe000 c0b03c74 c0b03c28 00000000
Jan 10 09:26:11 hs14 kernel: [54085.981876] ffa0: 00000000 512f04d0 00000000 00000000 dd45ffc8 dd45ffd0 c030884c c0308850
Jan 10 09:26:11 hs14 kernel: [54085.990018] ffc0: 60000013 ffffffff
Jan 10 09:26:11 hs14 kernel: [54085.998171] [<c030c38c>] (__irq_svc) from [<c0308850>] (arch_cpu_idle+0x38/0x44)
Jan 10 09:26:11 hs14 kernel: [54086.001477] [<c0308850>] (arch_cpu_idle) from [<c034ff08>] (do_idle+0xe8/0x1bc)
Jan 10 09:26:11 hs14 kernel: [54086.009111] [<c034ff08>] (do_idle) from [<c0350250>] (cpu_startup_entry+0x1c/0x20)
Jan 10 09:26:11 hs14 kernel: [54086.016142] [<c0350250>] (cpu_startup_entry) from [<423017cc>] (0x423017cc)
Jan 10 09:26:11 hs14 kernel: [54086.023843] ---[ end trace 452feb3a499a0195 ]---
Jan 10 09:26:11 hs14 kernel: [54086.030636] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.035568] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.042594] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.048636] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.054310] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.061524] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.081184] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.081230] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.087310] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.094688] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 1, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.101966] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
Jan 10 09:26:11 hs14 kernel: [54086.398043] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.398093] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.404163] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.410265] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:11 hs14 kernel: [54086.415885] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:11 hs14 kernel: [54086.423100] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:12 hs14 kernel: [54086.859493] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:12 hs14 kernel: [54086.859541] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:12 hs14 kernel: [54086.865611] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:12 hs14 kernel: [54087.668435] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:12 hs14 kernel: [54087.668484] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:12 hs14 kernel: [54087.674553] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:13 hs14 kernel: [54087.998516] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:13 hs14 kernel: [54087.998564] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.004648] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.010739] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:13 hs14 kernel: [54088.016359] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.023559] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.315168] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:13 hs14 kernel: [54088.315215] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:13 hs14 kernel: [54088.321286] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.199325] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.199378] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.205447] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.317048] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.317096] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.323165] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.399734] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.399767] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.405938] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.414260] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.417567] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.424841] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.442523] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
Jan 10 09:26:16 hs14 kernel: [54091.442587] ath10k_pci 0001:01:00.0: msdu-desc: 2500  skid: 32
Jan 10 09:26:16 hs14 kernel: [54091.474435] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.474465] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.480544] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.492287] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.492316] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.499467] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.524925] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
Jan 10 09:26:16 hs14 kernel: [54091.525752] ath10k_pci 0001:01:00.0: wmi print 'free: 87020 iram: 26788 sram: 18240'
Jan 10 09:26:16 hs14 kernel: [54091.578225] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:16 hs14 kernel: [54091.578254] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:16 hs14 kernel: [54091.584413] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54091.941028] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
Jan 10 09:26:17 hs14 kernel: [54092.060188] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:17 hs14 kernel: [54092.060235] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.066307] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.072884] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:17 hs14 kernel: [54092.078031] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.085315] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.092632] ath10k_pci 0001:01:00.0: failed to transmit packet, dropping: -19
Jan 10 09:26:17 hs14 kernel: [54092.096943] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.104226] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.110805] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.115940] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.122235] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.127668] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.194155] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.194197] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.199984] ath10k_pci 0001:01:00.0: failed to submit frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.204944] ath10k_pci 0001:01:00.0: failed to push frame: -19
Jan 10 09:26:17 hs14 kernel: [54092.263526] ath10k_pci 0001:01:00.0: device successfully recovered
Michal Soltys https://bugs.openwrt.org/:2053