>> PS: /etc/rc.d/altqd stop doesn't run as expected. altqd only takes 100%
>> of a CPU and is not stopped after this command.
>
> 5. Can you use crash(8) to find the kernel stack trace of the process
> that's eating CPU?
Hello,
I a -10.0_BETA VM, I have rebuilt a kernel with ALTQ support and
configured altqd with following config file :
interface wm0 bandwidth 1000M priq
class priq wm0 high_class NULL priority 1
class priq wm0 low_class NULL priority 0 default
filter wm0 high_class 0 1194 0 0 17
filter wm0 high_class 0 0 0 1194 17
filter wm0 high_class 0 1195 0 0 17
filter wm0 high_class 0 0 0 10240 17
filter wm0 high_class 0 10000 0 0 17
filter wm0 high_class 0 0 0 10000 17
filter wm0 high_class 0 53 0 0 17
filter wm0 high_class 0 53 0 0 6
conditioner wm0 af41_agr0 <mark 0xb8>
filter wm0 af41_agr0 0 10000 0 0 17
filter wm0 af41_agr0 0 0 0 10000 17
filter wm0 af41_agr0 0 0 192.168.10.250 0 17
filter wm0 af41_agr0 0 0 192.168.10.253 0 17
/etc/rc.d/altqd onestart starts altqd. I have checked that packets are
modified (a bigger configuration runs for a long time on my main server
to add QoS for VoIP).
/etc/rc.d/altqd onestop doesn't stop altqd. top shows that altqd
remains on CPU (and takes 100% of a CPU).
gdb -p 1342 (altq) returns that altqd stalls in qop_clear() function (I
don't have altdq sources on this system).
Best regards,
JKB
