Date: Fri, 6 Dec 2002 15:52:41 +0300 (MSK) From: Varshavchick Alexander <alex@metrocom.ru> To: David Schultz <dschultz@uclink.Berkeley.EDU> Cc: Terry Lambert <tlambert2@mindspring.com>, <freebsd-questions@FreeBSD.ORG>, <freebsd-hackers@FreeBSD.ORG> Subject: Re: maxusers and random system freezes Message-ID: <Pine.GSO.4.33.0212061546090.15512-100000@apache.metrocom.ru> In-Reply-To: <20021206123440.GA16544@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Dec 2002, David Schultz wrote: > Thus spake Varshavchick Alexander <alex@metrocom.ru>: > > Well, now I made KVA space 2G, we'll see later on if it helps to get rid > > of the sudden system halts, but for some reason a side-effect has > > appeared: pthread_create function returns EAGAIN error now, so I had to > > recompile the software using it with linux threads to make it working. > > With the old kernel these pieces worked without problems. Can it be that > > somehow the enlarged KVA space messed up with the threads mechanism? > > I'm not a pthreads expert, but my best guess is that your program > tried to create a thread with a stack address that was too high. > Remember that with a 2 GB KVA, user processes have only 2 GB to > play with instead of 3 GB, so attempting to mmap() a stack above > about 2 GB would cause pthread_create() to return EAGAIN. > Yes this makes sense, however this call to pthread_create didn't specify any special addresses for the new thread. The pthread_create was called with the NULL attribute which means that the system defaults were being used. Something in the system has gone wrong... ---- Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)118-3322, 118-3115(fax) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.33.0212061546090.15512-100000>