From owner-freebsd-smp  Fri Mar 12  8:56: 1 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33])
	by hub.freebsd.org (Postfix) with ESMTP id 2338C14D28
	for <smp@FreeBSD.ORG>; Fri, 12 Mar 1999 08:55:59 -0800 (PST)
	(envelope-from luoqi@watermarkgroup.com)
Received: (from luoqi@localhost)
	by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA29937;
	Fri, 12 Mar 1999 11:55:08 -0500 (EST)
	(envelope-from luoqi)
Date: Fri, 12 Mar 1999 11:55:08 -0500 (EST)
From: Luoqi Chen <luoqi@watermarkgroup.com>
Message-Id: <199903121655.LAA29937@lor.watermarkgroup.com>
To: marcel@scc.nl, smp@FreeBSD.ORG
Subject: Re: oas fail under smp, work without
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Alan Cox wrote:
> > 
> > Try applying the patches under the very first bullet at
> > 
> >         http://www.freebsd.org/~luoqi/
> > 
> > If it's using linux threads, that could fix the problem.
> 
> The exact problem is in the fact that OAS forks with some shared memory
> allocated. The message you get is:
> 	shared address space fork attempted: pid: %d
> (in file: /sys/kern/kern_fork.c)
> 
No, this message means the process tries to fork a child that shares its
own address space (a linux clone() syscall), which is not possible without
the aforementioned patch under SMP. It has nothing to do with (SYSV) shared
memory.

-lq


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