From owner-freebsd-stable  Fri Sep 10 18:10: 7 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48])
	by hub.freebsd.org (Postfix) with ESMTP
	id B682314C10; Fri, 10 Sep 1999 18:09:53 -0700 (PDT)
	(envelope-from niels@bakker.net)
Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82])
	by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id DAA29071;
	Sat, 11 Sep 1999 03:09:52 +0200 (CEST)
Received: from localhost (niels@localhost)
	by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id DAA12018;
	Sat, 11 Sep 1999 03:09:50 +0200
Date: Sat, 11 Sep 1999 03:09:50 +0200 (CEST)
From: N <niels@bakker.net>
X-Sender: niels@liquid.tpb.net
To: stable@FreeBSD.ORG
Cc: smp@FreeBSD.ORG
Subject: Re: URGENT! HEADS UP: 3.3-RC SMP + APM -> FIX
In-Reply-To: <199909101230.VAA12112@tasogare.imasy.or.jp>
Message-ID: <9909110305220.11927-100000@liquid.tpb.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mitsuru IWASAKI wrote:

> If you have problems on 3.3-RC SMP system with APM enabled, 
> please test the attached patch and give feedback to me ASAP.
> 
> The problem I was reported is that a lot of userland programs get
> signal 11 and core dumped on startup.  It seems my bad MCF (8/24) 
> breaks extra GDT entries for SMP.

I think I just spent an entire Friday evening wondering why with 3.3-RC
/bin/csh kept coring immediately upon startup when the system was in
multi-user mode, and inetd coring after having spawned telnetd once,
and other various ugly stuff...

I'd test your patch but I've just gotten home and I don't really feel like
having that server down for another few hours right now, so unfortunately 
I won't be testing your patch.


	-- Niels.



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