From owner-freebsd-smp Sun Sep 20 01:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12114 for freebsd-smp-outgoing; Sun, 20 Sep 1998 01:53:20 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12107 for ; Sun, 20 Sep 1998 01:53:16 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.8.8/8.8.8/Spinner) with ESMTP id QAA05006; Sun, 20 Sep 1998 16:51:43 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199809200851.QAA05006@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay cc: smp@FreeBSD.ORG Subject: Re: Only 50% idle with current -current? In-reply-to: Your message of "Sat, 19 Sep 1998 14:14:13 +0200." <199809191214.OAA25265@zibbi.mikom.csir.co.za> Date: Sun, 20 Sep 1998 16:51:41 +0800 From: Peter Wemm Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org John Hay wrote: > Hi, > > I have updated our one SMP box to the latest -current and now I see on top > that it doesn't go below 50% idle anymore. I'm doing a make release and > for a while ran two rc5's, but it still stayed at 50% idle. I remember > someone else also noticed it a few days ago. > > Anyone have any ideas? Yes, just try booting "-s" and go into single user mode to start with. Give a few commands, eg: 'sync; sync; sync', do a fsck if it's needed and then start multiuser.. If it then works as expected, then I suspect you are seeing a manifestation of a long running problem. I've found that SMP and/or ELF are unhappy at boot under SMP (and have been for 12 months). If I have /usr/libexec/getty dynamically linked and have more than a couple enabled in ttys, I get a lockup. The same happens if running rc5des/rc564 from the rc scripts if I don't go into single user and run a few commands first. At the time I hacked init(8) to do a couple of fork/exec's at startup and the problem went away. I don't understand what's going on and spent a fair while last year trying to figure it out. I'm pretty sure it's not ELF itself, it's just triggering something else. > John > -- > John Hay -- John.Hay@mikom.csir.co.za > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message > Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message