From owner-freebsd-current Wed Sep 23 23:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA08833 for freebsd-current-outgoing; Wed, 23 Sep 1998 23:34:01 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA08796; Wed, 23 Sep 1998 23:33:47 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id IAA22256; Thu, 24 Sep 1998 08:33:22 +0200 (SAT) From: John Hay Message-Id: <199809240633.IAA22256@zibbi.mikom.csir.co.za> Subject: Re: Weired top display at smp current kernel from today In-Reply-To: <199809240454.GAA20856@zibbi.mikom.csir.co.za> from John Hay at "Sep 24, 98 06:54:51 am" To: jhay@mikom.csir.co.za (John Hay) Date: Thu, 24 Sep 1998 08:33:22 +0200 (SAT) Cc: peter@netplex.com.au, freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > 2: Try (humor me :-) booting up into single user, running a few commands > > (eg: sync; sync; sync; fsck -p; ls) and then doing a ctrl-D to go into > > multi-user. > > > > If this (#2) is the key to making your system work properly, then you are > > seeing the same problem I've been unable to put a finger on for ages. > > None of the other SMP folks saw it, but only I was running ELF at the time. > > > > Somebody else (John Hay) mentioned that this fixes his problem, but it's > > not clear whether (or when) he's using elf. > > Yes I'm using elf. I never saw it before I changed to elf. Another way I > found is to use an aout /sbin/init. These problems is on a dual 266MHz PII > with onboard adaptec scsi. Last night I upgraded our dual 400Mhz PII with > Intel N440BX motherboard (ncr scsi onboard) to elf and up to now it hasn't > displayed the same problems, but then I haven't rebooted it too many times > yet. Correction, the dual 400Mhz PII also have the problem and booting with an aout /sbin/init solves it. Can there be something in the elf image loader missing or not initialized that effects things if the first process is elf? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message