Taylor R Campbell a écrit :
>> Date: Fri, 6 Jan 2023 15:55:37 +0100
>> From: BERTRAND Joël <joel.bertr...@systella.fr>
>>
>> /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).
>
> Can you get a kernel stack trace with crash(8) on the running system
> when altqd(8) is taking 100% CPU? If the pid is 1342, you use the
> command `bt/t 0t1342' to get it:
I have tried, but without usable result.
netbsd-test1# ps auwx | grep altq
root 1779 98.5 0.2 20356 1433 ? Os 4:39PM 1:06.26 /usr/sbin/altqd
> # crash
> crash> bt/t 0t1342
netbsd-test1# crash
...
crash> bt/t 0t1779
crash: kvm_resad(0x7f7fff7738e8, 8): kvm_read: Bad address
trace: pid 1779 lid 1779
crash>
> While here, can you also provide output of:
>
> crash> ps
> crash> ps/w
I cannot copy these line (it's a virtual machine). I'll try to access
to thos virtual machine through serial line.
Regards,
JKB
