From owner-freebsd-smp  Sun Dec  1 21:12:16 1996
Return-Path: owner-smp
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA01807
          for smp-outgoing; Sun, 1 Dec 1996 21:12:16 -0800 (PST)
Received: from mystic.sedona.net (hogan@mystic.sedona.net [204.157.202.250])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA01802
          for <freebsd-smp@freebsd.org>; Sun, 1 Dec 1996 21:12:14 -0800 (PST)
Received: (from hogan@localhost) by mystic.sedona.net (8.8.3/8.8.HW) id WAA02550 for freebsd-smp@freebsd.org; Sun, 1 Dec 1996 22:08:03 -0700 (MST)
From: Hogan Whittall <hogan@mystic.sedona.net>
Message-Id: <199612020508.WAA02550@mystic.sedona.net>
Subject: Still system slowdowns with certain apps
To: freebsd-smp@freebsd.org
Date: Sun, 1 Dec 1996 22:08:03 -0700 (MST)
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've got a Tyan TomCat (2) 150MHz with a 3940U controller, Stealth video,
and SMC ISA ethernet card using the SMP kernel with APIC_IO undefined
(won't work with it defined.  make depend fails) and
IGNORE_IDLEPROCS commented out of smptests.h...my problem is this...

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?

Also, in the proc list...

root         5 99.2  0.0     0   12  ??  RL   31Dec69    0:00.00 (cpuidle0)
root         6  0.0  0.0     0   12  ??  RL   31Dec69    0:00.00 (cpuidle1)

The 2 things I notice are broken start times and the % cpu being used by
these.  In the past they've always used about 49% each but now with this
kernel the majority is on one.  Ideas?

 -- 
 _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
| Hogan Whittall                   Systems & Networking Technician  |
| hogan@sedona.net                  Sedona Internet Services, Inc.  |
| http://cloofone.sedona.net/      Ph: (520) 204-2247 Pg: 282-8030  |
|-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-|