From owner-freebsd-current Thu Sep 24 01:58:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27754 for freebsd-current-outgoing; Thu, 24 Sep 1998 01:58:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from trinity.radio-do.de (trinity.Radio-do.de [193.101.164.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27747; Thu, 24 Sep 1998 01:58:31 -0700 (PDT) (envelope-from fn@trinity.radio-do.de) Received: (from fn@localhost) by trinity.radio-do.de (8.9.1/8.8.5/RADIO-1.1) id KAA08410; Thu, 24 Sep 1998 10:58:37 +0200 (CEST) Message-ID: <19980924105837.A8400@radio-do.de> Date: Thu, 24 Sep 1998 10:58:37 +0200 From: Frank Nobis To: freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Weired top display at smp current kernel from today References: <199809240704.JAA05414@sos.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Werner Griessl on Thu, Sep 24, 1998 at 09:55:03AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 24, 1998 at 09:55:03AM +0200, Werner Griessl wrote: > > On 24-Sep-98 S\xren Schmidt wrote: > > In reply to John Hay who wrote: > >> > > >> > 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? > > > > Strange, I remeber Peter having this problem, but I've never seen it here > > on any of my SMP machines and still dont, wierd.... I thought it was gone here, but... During a run of two cpu pigs and a top display with two times of 50% cpu usage and idle time again at 50% I suddenly have seen an init with 100% cpu and idle time now at 0%. This seems to be a good hint, when an aout init fixes that problem. Even after running in normal state, make -j4 world and idle tending to 0%, I have seen a fallback to the strange behaviour, but no boot in the meantime. There must be events that lets the system switch between those states. Regards Frank -- Frank Nobis Email: PGP AVAILABLE Landgrafenstr. 130 dg3dcn http://www.radio-do.de/~fn/ 44139 Dortmund Powered by SMP FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message