3.18 builds will follow, for those that think they need a 3.18 build:-)
Most people probably won't have any issues with 4.9. 3.18 has a known issue where clients that connect to the router via ipsec cannot reach wan. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Linksys EA8500
DD-WRT v3.0-r37120M kongat 10/03/18
Linux 4.9.130 #205 SMP PREEMPT Wed Oct 3 11:51:42 CEST 2018 armv7l
GUI install over a BS build.
main router
samba share
unbound
HTB FQ_CODEL
VLAN on port 4 + ath0.1 + ath1.1 via br1
29 static leases...4 which are leases on the br1 network
ovpn server
All appears to be worky very well
Posted: Wed Oct 03, 2018 14:45 Post subject: Re: New (KONG) Test Build - 10/03/2018
<Kong> wrote:
3.18 builds will follow, for those that think they need a 3.18 build:-)
Most people probably won't have any issues with 4.9. 3.18 has a known issue where clients that connect to the router via ipsec cannot reach wan.
The file for 3.18 build of the r7500v2 is exactly the same as 4.9. md5 checked
Posted: Wed Oct 03, 2018 16:36 Post subject: Linksys EA-8500
Has anyone tried the EA-8500 firmware under load? is it stable? wifi @ >161 with LL channel is working? last one under cpu load was crashing and needed powercycling the router.
3.18 builds will follow, for those that think they need a 3.18 build:-)
Most people probably won't have any issues with 4.9. 3.18 has a known issue where clients that connect to the router via ipsec cannot reach wan.
Router ModelNetgear R7500v2
Firmware Version DD-WRT v3.0-r37120M kongat (10/03/18 )
Kernel VersionLinux 3.18.123 #353 SMP PREEMPT Wed Oct 3 14:35:59 CEST 2018
dnssec still failed. QoS back to 3.18 awesomeness. Btw the 3.18 and 4.9 builds are flipped in the folders for the r7500v2 ie. the test-3.18 folder is actually 4.9 build, and test is 3.18
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Oct 03, 2018 20:39 Post subject:
Router Model: r7800
Status k3.18: it runs, highspeed qos latency is normal
Status k4.9: qos latency bad, abnormally high cpu qos load
Reset: no/yes (restored after yes did nothing)
Errors: see tickets below
included tickets are only those affecting r7800 and kong build only.
both kernels: still cant remove hostapd entries from wifi security config box, only nvram wipe removes them. multicast_to_unicast=0 works to disable it and go back to using multicast which still appears fixed so far..
both kernels: jffs2 usage is wrong, i have a 11.6 MB ad/track/etc block file, jffs says 23.96 MB / 19.58 MB.
both kernels: wpa3 is missing on both radios.
k4.9, for some reason eth1 affinity defaults to core 1, have to move it back to core 0, or move wan to core 1 (both must be on the same core), to prevent high *LAN* latency spikes to the router when under heavy torrent/p2p load when both down/uploads are maxed. local latency to router spikes over 45ms, when both affinities same core, spikes are <12ms. this is on all builds both kernels, 3.18 just defaults all affinities to core 0.
k4.9, qos bad still. im now convinced if/once cpu qos load issue is fixed, the latency will be too. there is still abnormal cpu load with all qos configs on k4.9. idle time @ 155mbps is 0.0% on the core with wan regardless how much i spread affinities. this is with htb+pie which is the least on cpu. k3.18 idle time is 6.5~7%, i think the problem is in there. hfsc is harder than htb on cpu, no wonder its throughput on k4.9 is a slug. cpu load issue seems fixed for all other loads except qos.
all routers/builds/tests i do have /proc/sys/net/ipv4/tcp_slow_start_after_idle at 0 from now on. no other tweaks. is the latest board-2.bin included? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
r7500v2
Firmware Version DD-WRT v3.0-r37120M kongat (10/03/18 )
Kernel Version Linux 3.18.123 #353 SMP PREEMPT Wed Oct 3
Reset none
Upgrade via ddup
Errors Several never seen before NB:
Code:
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.594181] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for vddcx
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.594185] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for v3p3
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.594189] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for v1p8
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.596629] qcom-dwc3-ssphy 100f8830.phy: cannot set voltage for vddcx
Oct 3 16:59:56 7500v2 kern.err kernel: [ 0.200686] pcie_init: pcie_init: unable to create IPC log context for pcie0-short
Oct 3 16:59:56 7500v2 kern.err kernel: [ 0.200701] pcie_init: pcie_init: unable to create IPC log context for pcie0-long
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.887074] Frequency table not initialized.
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.975670] UBI error: ubi_auto_attach: no valid UBI magic found inside mtd5
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.975724] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.990422] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
Oct 3 16:59:56 7500v2 kern.err kernel: [ 5.361594] UBIFS error (pid 476): ubifs_mount: cannot open "ubi0:rootfs_data", error -19
Oct 3 16:59:56 7500v2 kern.err kernel: [ 8.966746] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Oct 03, 2018 22:04 Post subject:
bushant wrote:
r7500v2
Firmware Version DD-WRT v3.0-r37120M kongat (10/03/18 )
Kernel Version Linux 3.18.123 #353 SMP PREEMPT Wed Oct 3
Reset none
Upgrade via ddup
Errors Several never seen before NB:
Code:
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.594181] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for vddcx
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.594185] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for v3p3
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.594189] qcom-dwc3-hsphy 100f8800.phy: cannot set voltage for v1p8
Oct 3 16:59:56 7500v2 kern.err kernel: [ 15.596629] qcom-dwc3-ssphy 100f8830.phy: cannot set voltage for vddcx
Oct 3 16:59:56 7500v2 kern.err kernel: [ 0.200686] pcie_init: pcie_init: unable to create IPC log context for pcie0-short
Oct 3 16:59:56 7500v2 kern.err kernel: [ 0.200701] pcie_init: pcie_init: unable to create IPC log context for pcie0-long
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.887074] Frequency table not initialized.
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.975670] UBI error: ubi_auto_attach: no valid UBI magic found inside mtd5
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.975724] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Oct 3 16:59:56 7500v2 kern.err kernel: [ 2.990422] UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
Oct 3 16:59:56 7500v2 kern.err kernel: [ 5.361594] UBIFS error (pid 476): ubifs_mount: cannot open "ubi0:rootfs_data", error -19
Oct 3 16:59:56 7500v2 kern.err kernel: [ 8.966746] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=0040,subsystem-vendor=168c,subsystem-device=0002 from ath10k/QCA99X0/hw2.0/board-2.bin
Working fine
more boot up junk thats been there for a long time _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
