From owner-freebsd-stable  Wed Aug 23  3:19:47 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from mix.unicon.ru (mix.unicon.ru [195.239.106.158])
	by hub.freebsd.org (Postfix) with ESMTP id 8F3A637B422
	for <freebsd-stable@freebsd.org>; Wed, 23 Aug 2000 03:19:38 -0700 (PDT)
Received: (from strange@localhost)
	by mix.unicon.ru (8.8.8/8.8.8) id RAA02918
	for freebsd-stable@freebsd.org; Wed, 23 Aug 2000 17:19:37 +0700 (NSS)
	(envelope-from strange)
Message-Id: <200008231019.RAA02918@mix.unicon.ru>
Subject: SMP problems (was: How can I obtain -stable for previous date)
In-Reply-To: <20000822173013.M20036@strontium.scientia.demon.co.uk> from Ben Smithurst at "Aug 22, 2000  5:30:13 pm"
To: freebsd-stable@freebsd.org
Date: Wed, 23 Aug 2000 17:19:36 +0700 (NSS)
From: strange@unicon.ru
X-Class: Fast
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > But after  Aug 20, the system became unstable ;(
> > It locks on hard loading (hard HDD usage),
> > like a make release or even make buildworld ;(
> > No panic, no crashdump, nothing, full lock...
> > Just many HDD problems after hard reboot ;(
> 
> or something to get the code from midnight on the 20th August.  But
> ideally you should try to find what is causing the problem, of course.

It seems to me, the problem is in SMP code, because
in 1 CPU configuration with the same kernel all works fine.
And when 2 CPU is installed, simple make -j4 buildworld
lock the system after little period of time...
Unfortunatelly I cant find what changes was made in smp stuff...

	WBR SA


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message