[ddaniel51]

http://www.desipro.de/ddwrt/K4-AC-ALPINE/

R9000 DD-WRT v3.0-r35945M std (05/14/1

Please report errors on this topic.


Release Notes:
http://svn.dd-wrt.com/timeline (with a grain of salt, kong doesnt always add all commits)


Router Model:

Status:
Reset:
Errors:

[labo]

Router: Netgear Nighthawk X10
Firmware: DD-WRT v3.0-r35945M std (05/14/18 )
Kernel: Linux 4.9.99 #25 SMP PREEMPT Mon May 14 00:16:28 CEST 2018 armv7l
Reset: No
Errors: Keep losing wireless every hour or so Will check for few more hours then reset if it continues and report back.

Edit update:
There were many connection dropouts on 5Ghz radio.
So Reverted back to BS build and stable for 6 hrs. Now going to reset and update to Kong's build. lets see.

[yodog]

[labo]

[labo]

Seeing lots of new errors and warnings in my R9000 AP router.
And no such errors in my WDS-Staion R9000 unit.

Dec 31 18:07:29 x10 kern.err kernel: [ 449.380550] wil6210 0003:01:00.0 giwifi0: wil_cfg80211_add_iface: virtual interfaces not supported
Dec 31 18:07:29 x10 kern.info kernel: [ 449.412762] wil6210 0003:01:00.0 giwifi0: wil_write_file_led_cfg: Enabling led 2
Dec 31 18:07:29 x10 kern.err kernel: [ 449.421434] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
Dec 31 18:07:29 x10 kern.err kernel: [ 449.841955] wil6210 0003:01:00.0 giwifi0: wmi_call: wmi_call(0x0858->0x1858) timeout 100 msec


May 16 20:20:39 x10 kern.warn kernel: [ 458.567212] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_exp_gre (err -2)
May 16 20:20:39 x10 kern.warn kernel: [ 458.574021] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_inbound (err -2)
May 16 20:20:39 x10 kern.warn kernel: [ 458.581107] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_outbound (err -2)
May 16 20:20:39 x10 kern.warn kernel: [ 458.588317] nf_nat_pptp: Unknown symbol nf_nat_pptp_hook_expectfn (err -2)


May 16 21:18:26 x10 kern.warn kernel: [ 3925.246778] ath10k_pci 0001:03:00.0: received unexpected tx_fetch_ind event: in push mode
May 16 21:18:26 x10 kern.warn kernel: [ 3925.254963] ath10k_pci 0001:03:00.0: received unexpected tx_fetch_ind event: in push mode
May 16 21:18:26 x10 kern.warn kernel: [ 3925.263140] ath10k_pci 0001:03:00.0: received unexpected tx_fetch_ind event: in push mode
May 16 21:18:26 x10 kern.warn kernel: [ 3925.271314] ath10k_pci 0001:03:00.0: received unexpected tx_fetch_ind event: in push mode


And 100s of these repeating now and then:

May 16 21:57:20 x10 kern.warn kernel: [ 6259.548214] nf_conntrack: nf_conntrack: table full, dropping packet
May 16 21:57:21 x10 kern.warn kernel: [ 6259.618199] nf_conntrack: nf_conntrack: table full, dropping packet
May 16 21:57:21 x10 kern.warn kernel: [ 6259.624521] nf_conntrack: nf_conntrack: table full, dropping packet
May 16 21:57:21 -10 kern.warn kernel: [ 6259.677925] nf_conntrack: nf_conntrack: table full, dropping packet
May 16 21:57:21 x10 kern.warn kernel: [ 6259.811294] nf_conntrack: nf_conntrack: table full, dropping packet
May 16 21:57:21 x10 kern.warn kernel: [ 6260.190111] nf_conntrack: nf_conntrack: table full, dropping packet
May 16 21:57:21 x10 kern.warn kernel: [ 6260.196393] nf_conntrack: nf_conntrack: table full, dropping packet

[labo]

For the f_conntrack: table full, warning, added the following temporarily.
(I doubled the hashsize to mitigate for now)

root@x10:~# more /sys/module/nf_conntrack/parameters/hashsize
16384
root@x10:~# echo 32768 > /sys/module/nf_conntrack/parameters/hashsize
root@x10:~# more /sys/module/nf_conntrack/parameters/hashsize
32768

[andonl]

Router: Netgear Nighthawk X10
Firmware: DD-WRT v3.0-r35945M std (05/14/18 )
Kernel: Linux 4.9.99 #25 SMP PREEMPT Mon May 14 00:16:28 CEST 2018 armv7l
Reset: Yes, before and after. Web upgrade from BS_r35681.

Using openvpn server, samba, minidlna( no segmentation fault), rsync, local DNS
Errors:

Could not get jffs file system enabled.

If kernel logging is enabled and 60 GHz is radio is disabled following messages are filling messages log, two rows every 5 seconds.

May 16 20:14:01 anr1 kern.err kernel: [ 2093.563220] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:01 anr1 kern.err kernel: [ 2093.575204] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:06 anr1 kern.err kernel: [ 2098.587739] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:06 anr1 kern.err kernel: [ 2098.599740] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:11 anr1 kern.err kernel: [ 2103.612358] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:11 anr1 kern.err kernel: [ 2103.624240] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:16 anr1 kern.err kernel: [ 2108.636753] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:16 anr1 kern.err kernel: [ 2108.648759] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:21 anr1 kern.err kernel: [ 2113.661158] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready
May 16 20:14:21 anr1 kern.err kernel: [ 2113.673088] wil6210 0003:01:00.0 giwifi0: __wmi_send: WMI: cannot send command while FW not ready

Currently I enabled 60 GHz radio.

2.4 GHz radio is disabled and there is no such messages.

[s1mf3r]

Router: Netgear Nighthawk X10
Firmware: DD-WRT v3.0-r35945M std (05/14/18 )
Kernel: Linux 4.9.99 #25 SMP PREEMPT Mon May 14 00:16:28 CEST 2018 armv7l
Reset: No
Errors:

[labo]

[labo]

@Kong, there are several issues with this new build.
I had to revert to BS build for work. I will test it over the weekend and provide details on each issue.
Thanks for the new build

[yodog]

Having issues with the latest build as well. I will be reverting to BS build for now. Thanks again Kong for the build, I really miss your builds I hope more time can be used for testing before releasing it as I'm having simple wifi issues with the 2.4 and 5ghz bands.

Oh, and when will channel 149 actually be channel 149? It always goes to 153.

[labo]