From owner-freebsd-current Sun Sep 17 6:57:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D6BC037B423; Sun, 17 Sep 2000 06:57:30 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e8HDvIN78781; Sun, 17 Sep 2000 15:57:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: Alexander Leidinger , current@FreeBSD.ORG, jhb@FreeBSD.ORG Subject: Re: 100% system time? (SMPng on UP system) In-Reply-To: Your message of "Mon, 18 Sep 2000 00:52:41 +1100." Date: Sun, 17 Sep 2000 15:57:18 +0200 Message-ID: <78779.969199038@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce Ev ans writes: >> > Perhaps it really is a system process :-[. idprio on a pure cpu hog prevents >> > other user processes from running like a system process might do: >> > >> > idprio 31 sh -c "while :; do :; done" >> > >> > System processes actually hang the entire system until they complete: >> >> Are you mixing idprio with rtprio or did I not understand what you >> explain? > >You didn't understand :-). Try the example. It only uses idprio. > >rtprio certainly causes system hangs, and the supergiant lock may >increase the problem. Before SMPng, rtprio processes prevented all >non-rtprio processes including important daemons (and I think even kernel processes) from running. Starting an infinite loop at rtprio >while remotely logged in was fatal because a ^C (character, not signal) >to kill the process couldn't be delivered. I can confirm this one, ntpd has for a long time pointlessly raised it's priority to the absolute maximum, and if during debugging it went into a spin it would freeze the system. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message