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 ~~
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Thu Dec 07, 2017 20:05 Post subject:
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
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Dec 12, 2017 11:24 Post subject:
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
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
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...
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...
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.
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...
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
just with fq_codel on only and htb, with my services removed. ya no problem whatsoever..
ps: my modem's bufferbloat is about 150ms.. qos isnt just broken, its reversed
Hmmm, I would have to say that is getting in the unacceptable range
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
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...
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.