On 7/22/07, Daniel Melameth <[EMAIL PROTECTED]> wrote: > On 7/22/07, Stuart Henderson <[EMAIL PROTECTED]> wrote: > > On 2007/07/20 15:20, Daniel Melameth wrote: > > > then go back to the broken behavior sometime later. A reboot of the box > > > or > > > removing altq is the only way to resolve the issue, temporarily. I've > > > tried > > > both priq and cbq, adjusting tbrsize, recompiling the kernel with a higher > > > HZ value and using different hardware and different Internet connections, > > > but the issue persists. > > > > Try a snapshot, i386 moved to the new timecounter code after 4.1. > > > > Though I note there is also an XXX about variable cpu frequency (in > > sys/altq/altq_subr.c) which might affect you if you adjust cpu speed > > (manually or by apmd). > > Thanks for taking the time to reply. I can't readily do a snapshot > now, but since I am using apmd, I'll try this avenue first and see > what happens.
Thanks to Stuart's review of the altq code, I have, finally, resolved this issue which has affected me for years. Disabling apmd did not resolve the issue, but disabling the Dynamically Switchable setting for CPU Frequency in the BIOS appears to have addressed this problem. I have been using the system for a couple of months now and altq has been very solid.
