<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Richard,<div><br></div><div><br><div><div>On Nov 12, 2013, at 18:26 , Richard E. Brown <<a href="mailto:richb.hanover@gmail.com">richb.hanover@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><blockquote type="cite">On Nov 12, 2013, at 4:11 AM, Sebastian Moeller <<a href="mailto:moeller0@gmx.de">moeller0@gmx.de</a>> wrote:<br><br><blockquote type="cite"><blockquote type="cite">- Had to enable and set AQM parameters, since they’re saved differently from the QoS settings in the 3.7.5-2 firmware. Set parameters to ~ 90% of link speeds <br></blockquote><br><span class="Apple-tab-span" style="white-space:pre"> </span>Just curious, did you specify overhead and encapsulation?<br></blockquote></blockquote><br>No, I simply used the defaults on that page.<br></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Ah, you might want to try setting the link layer adaptation mechanism to tc_stab, the link layer to adls or atm and the overhead to 40 (or look at <a href="http://ace-host.stuart.id.au/russell/files/tc/tc-atm/">http://ace-host.stuart.id.au/russell/files/tc/tc-atm/</a> to figure out the fixed per packet overhead of your link). This should allow you to specify a larger percentage of your link rate as shaped rate… But see the attached screenshot of my AQM tab</div><div><br></div><div><br></div><div><img id="0f944f9a-6159-4255-a3dc-fe376eec9989" height="664" width="1167" apple-width="yes" apple-height="yes" src="cid:DB4502E2-E9C7-4035-9B6F-CC294893A3E4@home.lan"></div><br><blockquote type="cite"><br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">- The kernel.log shows lots of the stack traces below: 2-5 per second on a long-term basis. <br></blockquote><br><span class="Apple-tab-span" style="white-space:pre"> </span>These look quite weird, the error is a slow patch warning from hfsc_schedule_watchdog . But, hfsc is the queuing discipline used by stock OpenWrt, cerowrt , so far, has only used HTB (last I checked was cerowrt 3.10.11-3). So my guess is that you were running the default QOS system instead (or worse in addition) to cerowrt's. It would be great to see the output of:<br>tc -d qdisc ; tc -s class show dev ifb0 ; tc -s class show dev ge00<br>to check what is up with the AQM system...<br><br>Did you by any change use the QOS tab in 3.7.5-2 instead of running AQM or simple_qos.sh from rc.local/ifup? If so did you direct sys upgrade to keep the old configuration files?<br></blockquote></blockquote><br>Yes, I was using QoS in 3.7.5-2, and I kept the old configuration files (so I didn’t have to re-enter credentials for my DSL link, etc.) I guess it seems likely that I may have been running *both* (!)<br></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Probably just QOS, as I think both QOS and AQM start out by tearing down all discs… but the hfsc error should not affect AQM since it uses HTB.</div><br><blockquote type="cite"><br>Would a better upgrade path be to start with 3.7.5-2, then disable the QoS, then flash with 3.10.18-1? (My intuition tells me that this would remove the QoS settings from the loop…)<br></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Mhhh, I guess that should work.</div><blockquote type="cite"><br>It’s pretty easy to re-flash with 3.10.18-1 and run the tc commands. If disabling QoS makes sense, then after I do the ’tc’ experiment, I’ll re-flash with 3.7.5-2, turn off QoS, then reflash to 3.10.18-1.</blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span> This should not fix your PPPoE issues though… so maybe it is not the best time to switch…</div><br><blockquote type="cite"> But it’ll have to wait ’til dark so no one else is using it. :-)<br></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Hihi, same issue on my side :) No "playing" with the network while my wife is using it </div><div><br></div><div>Best</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Sebastian</div><div><br></div><br><blockquote type="cite"><br>Rich<br><br><br></blockquote></div><br></div></body></html>