R7800 Discussion - 2017

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3 ... 31, 32, 33 ... 35, 36, 37  Next
Author Message
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5405
Location: Texas

PostPosted: Fri Nov 24, 2017 16:57    Post subject: Reply with quote
tatsuya46 wrote:
ath10k fw downgrade brought the return of this spam as well..

[167956.377923] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167956.377953] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167956.385172] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[167956.393369] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.398164] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.398193] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.405391] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.413621] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.421867] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.430055] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.438362] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.446609] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168115.454867] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168172.404539] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168172.404569] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168172.411693] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168172.419997] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168358.421533] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168358.421565] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168358.428737] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168358.436993] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168406.426045] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168406.426075] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168406.433262] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168406.441444] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168457.431876] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.444206] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.444235] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.451365] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.459676] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.467917] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.476161] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.484410] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168559.492656] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168874.482007] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168874.482036] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168874.489178] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168874.497479] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168874.505699] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168940.489348] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168940.489379] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168940.496598] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[168940.504826] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.500860] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.500888] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.508082] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.516326] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.524560] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.532808] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.541000] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169039.549302] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169213.518506] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169213.518536] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169213.525738] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[169213.533956] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode

Rebooted couple days ago after some changes but EA8500 still getting some that w/r33784 ~~

[ 40.341483] br1: port 3(vlan4) entered forwarding state
[ 43.291279] Ebtables v2.0 registered
[ 66.179405] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
[12956.046761] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[12956.077927] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[12956.079941] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[12956.112136] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[14440.517331] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[14440.517372] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[14440.524587] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[14440.532716] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[26497.657048] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[26497.671431] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[26497.672132] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[26497.683911] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[26517.702075] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[26517.745522] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[26595.707843] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[26595.744208] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61377.198247] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61377.234437] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61378.375654] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61378.414768] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61384.741030] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61384.779328] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61386.649709] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61386.687776] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61387.192261] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61387.227480] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61388.183059] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61388.219187] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61389.159383] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61389.198071] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61389.977948] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61390.024788] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61391.315325] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61391.352168] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61392.123006] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61392.159285] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61393.098626] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61393.139052] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61393.788068] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61393.825466] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61395.225117] ath10k_warn: 2 callbacks suppressed
[61395.225165] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[61395.266329] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
[105505.570463] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.578088] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.578121] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.585338] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.593537] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.601794] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.609992] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.618279] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105511.626527] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105532.603474] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105532.603508] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105532.610698] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
[105532.618933] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
:~# uptime
10:49:57 up 2 days, 17:26, load average: 0.14, 0.06, 0.02 Twisted Evil
Sponsor
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7467
Location: YWG, Canada

PostPosted: Wed Nov 29, 2017 22:12    Post subject: Reply with quote
tatsuya46 wrote:
in r33782 ath10k fw was silently downgraded back to 10.4-3.4-00082 for whatever reason...

love to hear why... it also nullifies http://svn.dd-wrt.com/ticket/6059


found the answer.. http://www.spinics.net/lists/linux-wireless/msg168051.html

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r46681 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r46350 std
[BROADCOM] DIR-860L A1 ----------------------------> r46329 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
Nilugeator
DD-WRT Novice


Joined: 31 Jul 2016
Posts: 32

PostPosted: Thu Dec 07, 2017 14:17    Post subject: Re: SFE + OpenVPN bug Reply with quote
hi,

Is the SFE bug incompatibility with Policy Based Routing going to be corrected?
still KO with the last release

http://svn.dd-wrt.com/ticket/5986

thx in advance
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7467
Location: YWG, Canada

PostPosted: Thu Dec 07, 2017 20:05    Post subject: Reply with quote
like all of these dirty nat related tricks, its looking pretty dead (and buggy in its existing state). knew this would happen thats why i had zero hope for it when it appeared.. still no pbr fix, no downlink qos fix etc.. the real fix will remain as it has been, brute cpu power
_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r46681 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r46350 std
[BROADCOM] DIR-860L A1 ----------------------------> r46329 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7467
Location: YWG, Canada

PostPosted: Mon Dec 11, 2017 23:44    Post subject: Reply with quote
http://svn.dd-wrt.com/changeset/34039

Shocked

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r46681 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r46350 std
[BROADCOM] DIR-860L A1 ----------------------------> r46329 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5405
Location: Texas

PostPosted: Tue Dec 12, 2017 0:09    Post subject: Reply with quote
tatsuya46 wrote:
http://svn.dd-wrt.com/changeset/34039

Shocked

'bout damn time Cool
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7467
Location: YWG, Canada

PostPosted: Tue Dec 12, 2017 11:24    Post subject: Reply with quote
well its disappointing so far.. qos is a total mess.. PIE, the only decent working one for high speed cable modems is gone not even listed now. fq_codel performance is crap, high latency, tc -d qdisc now gives a bunch of different [unknown qdisc] entries. wan led is always off. wifi leds on the far right is always off both of them.

thats with htb.. use hfsc which already has throughput problems along with fq_codel, now gets a poor 93mbps out of my 150mbps.. and its not even close to saturating the cpu. i get this feeling this is going to just get left like this.. and kong will be left to try & quickly patch up qos again.. just like around a year ago when it had that htb etc problem..

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r46681 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r46350 std
[BROADCOM] DIR-860L A1 ----------------------------> r46329 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5405
Location: Texas

PostPosted: Tue Dec 12, 2017 13:25    Post subject: Reply with quote
tatsuya46 wrote:
well its disappointing so far.. qos is a total mess.. PIE, the only decent working one for high speed cable modems is gone not even listed now. fq_codel performance is crap, high latency, tc -d qdisc now gives a bunch of different [unknown qdisc] entries. wan led is always off. wifi leds on the far right is always off both of them.

thats with htb.. use hfsc which already has throughput problems along with fq_codel, now gets a poor 93mbps out of my 150mbps.. and its not even close to saturating the cpu. i get this feeling this is going to just get left like this.. and kong will be left to try & quickly patch up qos again.. just like around a year ago when it had that htb etc problem..

Well golly geez I couldn't even play with it on the EA8500 --- they killed it's switch again with the new kernel update ..... starting to feel like that redheaded step-child they never let out of the house/closet
Razz
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7467
Location: YWG, Canada

PostPosted: Tue Dec 12, 2017 22:45    Post subject: Reply with quote
guess he doesnt understand it so we'll be having to enforce our idle frq again.. http://svn.dd-wrt.com/changeset/34072

tickets made for newly created issues from the kernel port. (the last has been there for a long time but now its instantly amplified to the unusable point) now we wait...

http://svn.dd-wrt.com/ticket/6113
http://svn.dd-wrt.com/ticket/6114
http://svn.dd-wrt.com/ticket/6115

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r46681 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r46350 std
[BROADCOM] DIR-860L A1 ----------------------------> r46329 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5405
Location: Texas

PostPosted: Wed Dec 13, 2017 3:38    Post subject: Reply with quote
tatsuya46 wrote:
guess he doesnt understand it so we'll be having to enforce our idle frq again.. http://svn.dd-wrt.com/changeset/34072

tickets made for newly created issues from the kernel port. (the last has been there for a long time but now its instantly amplified to the unusable point) now we wait...

http://svn.dd-wrt.com/ticket/6113
http://svn.dd-wrt.com/ticket/6114
http://svn.dd-wrt.com/ticket/6115

EA8500-r34074
Haven't done much with it but let it blow the cobwebs off the CPUs.
It takes two terminal windows, both running 'openssl speed' to get CPU-0 lazy ass off 384.... then both will
stay ramped up to 1400 all time openssl speed is running.



Of course had to have the 3rd terminal running 'top' plus also moved 2GB across 5GHz at same time just to get it all warmed up.
Nothin broke yet --- so that's a good sign ... I think the K4.9 will be a keeper....
I see they killed my 'Linksys' light. He don't come on now in any mode type -- blinks couple times at boot and that's it.
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7467
Location: YWG, Canada

PostPosted: Wed Dec 13, 2017 3:43    Post subject: Reply with quote
mrjcd wrote:
tatsuya46 wrote:
guess he doesnt understand it so we'll be having to enforce our idle frq again.. http://svn.dd-wrt.com/changeset/34072

tickets made for newly created issues from the kernel port. (the last has been there for a long time but now its instantly amplified to the unusable point) now we wait...

http://svn.dd-wrt.com/ticket/6113
http://svn.dd-wrt.com/ticket/6114
http://svn.dd-wrt.com/ticket/6115

EA8500-r34074
Haven't done much with it but let it blow the cobwebs off the CPUs.
It takes two terminal windows, both running 'openssl speed' to get CPU-0 lazy ass off 384.... then both will
stay ramped up to 1400 all time openssl speed is running.



Of course had to have the 3rd terminal running 'top' plus also moved 2GB across 5GHz at same time just to get it all warmed up.
Nothin broke yet --- so that's a good sign ... I think the K4.9 will be a keeper....
I see they killed my 'Linksys' light. He don't come on now in any mode type -- blinks couple times at boot and that's it.


wont be touched besides checking builds until AT LEAST 6115 is fixed but... feel like im going to be stuck on r34036 for a very, long time.. going by attention that qos gets around here.

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r46681 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r46350 std
[BROADCOM] DIR-860L A1 ----------------------------> r46329 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7467
Location: YWG, Canada

PostPosted: Wed Dec 13, 2017 10:44    Post subject: Reply with quote
LOL.. Rolling Eyes https://www.dslreports.com/speedtest/26691021

just with fq_codel on only and htb, with my services removed. ya no problem whatsoever..

ps: my modem's bufferbloat is about 150ms.. Evil or Very Mad qos isnt just broken, its reversed

_________________
LATEST FIRMWARE(S)

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150/QCA9984/QCA9882 ------> r46681 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
[QUALCOMM] DIR-862L --------------------------------> r46671 std
▲ ACTIVE / INACTIVE ▼
[QUALCOMM] WNDR4300 v1 --------------------------> r46350 std
[BROADCOM] DIR-860L A1 ----------------------------> r46329 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 5405
Location: Texas

PostPosted: Wed Dec 13, 2017 12:43    Post subject: Reply with quote
tatsuya46 wrote:
LOL.. Rolling Eyes https://www.dslreports.com/speedtest/26691021

just with fq_codel on only and htb, with my services removed. ya no problem whatsoever..

ps: my modem's bufferbloat is about 150ms.. Evil or Very Mad qos isnt just broken, its reversed

Hmmm, I would have to say that is getting in the unacceptable range Razz
I'm sure they'll do some tweaks there after other bugs are worked out.....
... or you can always go back to a 30/5 line Twisted Evil
vit5421
DD-WRT User


Joined: 12 Nov 2015
Posts: 413

PostPosted: Wed Dec 13, 2017 14:58    Post subject: Reply with quote
The speed test looks not as bad at my end http://www.dslreports.com/speedtest/26697872
_________________
Netgear R7800
hotbbq
DD-WRT Novice


Joined: 14 Apr 2012
Posts: 10

PostPosted: Thu Dec 14, 2017 1:49    Post subject: Reply with quote
tatsuya46 wrote:
mrjcd wrote:
tatsuya46 wrote:
guess he doesnt understand it so we'll be having to enforce our idle frq again.. http://svn.dd-wrt.com/changeset/34072

tickets made for newly created issues from the kernel port. (the last has been there for a long time but now its instantly amplified to the unusable point) now we wait...

http://svn.dd-wrt.com/ticket/6113
http://svn.dd-wrt.com/ticket/6114
http://svn.dd-wrt.com/ticket/6115

EA8500-r34074
Haven't done much with it but let it blow the cobwebs off the CPUs.
It takes two terminal windows, both running 'openssl speed' to get CPU-0 lazy ass off 384.... then both will
stay ramped up to 1400 all time openssl speed is running.



Of course had to have the 3rd terminal running 'top' plus also moved 2GB across 5GHz at same time just to get it all warmed up.
Nothin broke yet --- so that's a good sign ... I think the K4.9 will be a keeper....
I see they killed my 'Linksys' light. He don't come on now in any mode type -- blinks couple times at boot and that's it.


wont be touched besides checking builds until AT LEAST 6115 is fixed but... feel like im going to be stuck on r34036 for a very, long time.. going by attention that qos gets around here.


Dude, relax a bit. Nobody is getting paid to do this. If it was an easy fix I'm sure BS or Kong would fix it.
Goto page Previous  1, 2, 3 ... 31, 32, 33 ... 35, 36, 37  Next Display posts from previous:    Page 32 of 37
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum