From owner-freebsd-hackers Sun May 19 20:43:27 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA21905 for hackers-outgoing; Sun, 19 May 1996 20:43:27 -0700 (PDT) Received: from io.org (io.org [198.133.36.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA21893 for ; Sun, 19 May 1996 20:43:21 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by io.org (8.6.12/8.6.12) with SMTP id XAA28983; Sun, 19 May 1996 23:42:42 -0400 Date: Sun, 19 May 1996 23:42:25 -0400 (EDT) From: Brian Tao To: Bruce Evans cc: FREEBSD-HACKERS-L Subject: Re: Slow tty updates and high load, but idle CPU In-Reply-To: <199605200254.MAA00774@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 20 May 1996, Bruce Evans wrote: > > ttwrite() is probably sleeping on lbolt. This should be easy to check > by looking at the sleep address in ps output. Tell me if I'm on the right track: "nm /kernel | fgrep lbolt" gives me the address 0xf01d605c. Judging by the output of "ps axO nwchan", I should look for processes waiting at 1d605c? > ttwrite() sleeps on lbolt when the system runs out of clists. clists > may run out because they are broken as designed or because of a bug > that was fixed in -current on 1995/12/15 and in -stable on 1996/01/03. I'll check back on this in a couple of weeks, perhaps upgrade one of the machines to the May 1 snapshot. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"