Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Sep 1998 08:33:22 +0200 (SAT)
From:      John Hay <jhay@mikom.csir.co.za>
To:        jhay@mikom.csir.co.za (John Hay)
Cc:        peter@netplex.com.au, freebsd-smp@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject:   Re: Weired top display at smp current kernel from today
Message-ID:  <199809240633.IAA22256@zibbi.mikom.csir.co.za>
In-Reply-To: <199809240454.GAA20856@zibbi.mikom.csir.co.za> from John Hay at "Sep 24, 98 06:54:51 am"

next in thread | previous in thread | raw e-mail | index | archive | help
> > 
> > 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-smp" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809240633.IAA22256>