EA8500
DD-WRT v3.0-r40863 std (08/30/19)
Linux 4.9.190 #463 SMP Fri Aug 30 07:54:55 CEST 2019 armv7l
I only installed on 2nd EA8500 ...switch / VLAN / ovpn server / samba share ext4
It is all working ok but the silly thing has both cores on 1400 MHz all time.
I shot the
Code:
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n ondemand > $CPUFREQ; done
to it so its back to its normal self and all good -- Uptime 20:06
I ain't gonna put on main router ...don't see the need and r40854Uptime 2 days, 9:52 is doing dang good for me
#
WRT160NL
DD-WRT v3.0-r40863 std (08/31/19)
Linux 3.10.108-d8 #20556 Sat Aug 31 01:42:38 +04 2019 mips
GUI install over r40854.
switch / samba share
He's all good.
#
WNDR3700v4
DD-WRT v3.0-r40863 std (08/31/19)
Linux 3.18.140 #52357 Sat Aug 31 03:06:21 +04 2019 mips
GUI install over r40854.
switch / ovpn server / samba share
All working good.
Joined: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Sun Sep 01, 2019 0:22 Post subject:
I guess my suggestion didn't quite work as expected and the generic cpu* works correctly. OR, something else in the cpu frequency mechanism is being tricky.
On my EA8500 I have the startup command:
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n ondemand > $CPUFREQ; done
With r40854 this worked ok, with cpu's swapping around with 800/800,1400/800,800/1400 and 1400/1400.
But with r40863, it's either 800 or 1000 - 1400 doesn't appear at all. _________________ ------------------------------------
Linksys WRT3200ACM DD-WRT r55819 (Gateway)
Linksys EA8500 OpenWrt-23.05.3 (Wired AP)
Netgear WNDR3700v4 DD-WRT r55819 (spare Gateway)
Photos: https://www.flickr.com/photos/nickant44/albums
On my EA8500 I have the startup command:
for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n ondemand > $CPUFREQ; done
With r40854 this worked ok, with cpu's swapping around with 800/800,1400/800,800/1400 and 1400/1400.
But with r40863, it's either 800 or 1000 - 1400 doesn't appear at all.
Well Sir, If you give her something to really think on she will ramp-up to 1400.
Note: this unit is set to ondemand and is always normally at 800/800
'all openssl speed tests'
Beware --- if you let such a thing run till all is done tis takes a while ...
...and prolly should NOT have the cat sleeping on top of the EA8500 while such is running
mrjcd,
well, I gave her a good hiding via torrents, and neither cpu got to 1400 here, only 1000.
I've never even seen it show 1000 before, only 800 or 1400.
That was with load ave at 0.66 - it usually never gets much above 0.50 here.
And no, the cat is next to the fire! _________________ ------------------------------------
Linksys WRT3200ACM DD-WRT r55819 (Gateway)
Linksys EA8500 OpenWrt-23.05.3 (Wired AP)
Netgear WNDR3700v4 DD-WRT r55819 (spare Gateway)
Photos: https://www.flickr.com/photos/nickant44/albums
Posted: Mon Sep 02, 2019 17:27 Post subject: Maybe it's my imagination
R7800
no QoS
uptime 1 day
Just upgraded to this build yesterday. Getting the best dslreports speedtest results I've seen:
Or maybe they upgraded the servers nearby.
Getting some weird warnings about jffs2 ECC errors and a bunch of "received unexpected tx_fetch_ind event: in push mode" warnings. But she's definitely pushing the gigabit fiber.
Posted: Mon Sep 02, 2019 18:57 Post subject: Re: Maybe it's my imagination
Drjjr wrote:
Getting some weird warnings about jffs2 ECC errors and a bunch of "received unexpected tx_fetch_ind event: in push mode" warnings. But she's definitely pushing the gigabit fiber.
EA8500 running r40854
just started see this few weeks back but it looks like only at startup after the install.
I only have JFFS enabled to use for the fixed unbound.conf
Code:
[ 32.568006] jffs2: mtd->read(0x74c bytes from 0x20400b4) returned ECC error
[ 32.568516] jffs2: mtd->read(0x800 bytes from 0x2040000) returned ECC error
[ 32.574242] jffs2: mtd->read(0x44 bytes from 0x2040000) returned ECC error
[ 32.584353] jffs2: mtd->read(0x790 bytes from 0x2040070) returned ECC error
[ 32.588215] jffs2: mtd->read(0x44 bytes from 0x2040070) returned ECC error
I also always see few of these guys with most DD-WRT builds but they ain't never killed a thing.
This is current groups of them in dmesg
Code:
[93435.743775] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.743818] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.751049] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.759205] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.767341] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.775419] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.783648] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.791803] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.799987] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[93435.808140] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[109975.111396] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[109975.115157] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[109975.123344] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[109975.131596] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[111775.762753] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[111775.762796] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[111775.770017] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[111775.778252] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[113084.130258] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[113084.130301] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[113084.137505] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[113084.145682] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[292815.715217] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
[292815.715260] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
[292815.722501] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
[292815.730704] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode
--
EDIT: gonna tell ya don't worry with the
received unexpected tx_fetch_ind event: in push mode
lots of really smart peoples have tried to sort that for several years
I've moved my EA8500 back to r40854.
I'm continuing to use the "ondemand" cpu speed command at startup.
CPU speed in r40863 ocassionally hits 1000, despite significant use.
With r40854 it is much more responsive to loads and goes from 800 to 1400 much earlier and changes more often, as needed. _________________ ------------------------------------
Linksys WRT3200ACM DD-WRT r55819 (Gateway)
Linksys EA8500 OpenWrt-23.05.3 (Wired AP)
Netgear WNDR3700v4 DD-WRT r55819 (spare Gateway)
Photos: https://www.flickr.com/photos/nickant44/albums