From owner-freebsd-smp Mon Dec 2 17:27:25 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA27227 for smp-outgoing; Mon, 2 Dec 1996 17:27:25 -0800 (PST) Received: from kvikk.uit.no (kvikk.Uit.No [129.242.4.32]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA27216 for ; Mon, 2 Dec 1996 17:27:22 -0800 (PST) Received: from sprint.cc.uit.no (sprint.Cc.Uit.No [129.242.5.198]) by kvikk.uit.no (8.7.3/8.7.1) with ESMTP id CAA03460; Tue, 3 Dec 1996 02:27:12 +0100 (MET) Received: from slibo.cc.uit.no (slibo.Cc.Uit.No [129.242.5.36]) by sprint.cc.uit.no (8.8.0/8.8.0) with ESMTP id CAA17481; Tue, 3 Dec 1996 02:27:11 +0100 (MET) Received: from localhost (terjem@localhost) by slibo.cc.uit.no (8.7.3/8.7.3) with ESMTP id CAA26717; Tue, 3 Dec 1996 02:27:10 +0100 (MET) Message-Id: <199612030127.CAA26717@slibo.cc.uit.no> X-Mailer: exmh version 1.6.9 8/22/96 To: Hogan Whittall cc: freebsd-smp@freebsd.org Subject: Re: Still system slowdowns with certain apps In-reply-to: Your message of "Sun, 01 Dec 1996 22:08:03 MET." <199612020508.WAA02550@mystic.sedona.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Dec 1996 02:27:10 +0100 From: Terje Normann Marthinussen Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >The new kernel works great and I've yet to have a program seg fault on >me...but ever since I got the latest source on Thursday night I've >experienced a major system slowdown whenever I compile something. The >compile itself moves right along and gets done fast, but everything else >on the system takes forever to respond until the compile is done. Before >Thursday everything worked fine whencompiling and there were still seg >faults...but this slowdown is new and I was hoping code I got today would >fix it...but it's still there. Has anyone else experienced this or know >of a fix? > Well, I have experienced the same slowdown. And it seems like things are a lot worse than just a slowdown. Thought I should run a couple of parallell dhrystones just for fun before I went home to my bed. Never got that far. The system locked up the moment I started the first and didn't allow me to do anything else until it had finished running. Then I just wrote: main() { while(1); } It didn't start so well, but just when I typed ctrl-c, it froze the system. Reset button only way out. Tried again, seems like ctrl-c doesn't have anything to do with it at least. But the second time I ran the program, things froze quite quickly. Reset button next.... Seems like it's not as effective as dhrystone (well, that loop by it self is probably not a very efficient cpu consumer, should be easy enough to improve it), but when it locks, it locks well ;) Terje Marthinussen terjem@cc.uit.no