Date: Sun, 21 Jul 2002 14:57:30 -0500 From: Dan Nelson <dnelson@allantgroup.com> To: Stefan Schwarzer <sschwarzer@sschwarzer.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: top(1) blocks Message-ID: <20020721195730.GH40625@dan.emsphone.com> In-Reply-To: <3D3AD89E.3000104@sschwarzer.net> References: <3D3AD89E.3000104@sschwarzer.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Jul 21), Stefan Schwarzer said: > On one of our FreeBSD server invoking top(1) blocks (as if had > entered cat instead of top). Something about the machine: > > purpurea# uname -a > FreeBSD purpurea.rz.tu-clausthal.de 4.6-RELEASE-p1 FreeBSD 4.6-RELEASE-p1 #4: Tue Jul 16 19:01:33 CEST 2002 root@purpurea.rz.tu-clausthal.de:/usr/obj/usr/src/sys/PURPUREA i386 > > (This is an AMD double processor system (AMD Athlon XP 1600+). SMP is > activated in the kernel configuration. According to dmesg, the second > CPU is enabled on boot.) > > The problem: > > purpurea# top > ^C Hit ^T here instead of ^C. That will print a status line saying where top is blocking in the kernel. Also try ktrace'ing it, hit ^C, and use kdump to see what top was doing when you hit ^C. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020721195730.GH40625>