Date: Mon, 28 Jun 1999 08:04:08 +0200 From: Bernd Walter <ticso@cicely.de> To: Thomas David Rivers <rivers@dignus.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: setiathome crashes 3.2? Message-ID: <19990628080407.A43878@cicely8.cicely.de> In-Reply-To: <199906280209.WAA76016@lakes.dignus.com>; from Thomas David Rivers on Sun, Jun 27, 1999 at 10:09:22PM -0400 References: <199906280209.WAA76016@lakes.dignus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 27, 1999 at 10:09:22PM -0400, Thomas David Rivers wrote: > > I seem to recall seeing this someone (this may not be the > right list.) > > But - I downloaded the 3.2 Seti@home and starting running it > on a left-over 75mhz laptop I have. > > It seems to crash the laptop (silently lock it up, actually) > fairly quickly. > > Did I recall someone else mentioning that? > > Would everyone agree that it's not a "good thing" for a user-mode > program to be able to lock up the OS? > There are severall resons. One of them is that I got panics with a to high set MAXUSER in kernel options. I don't know if it's a problem with 3.2. The other possible reason might be a CPU overheating. CPUs used under FreeBSD are typicall suspended during idle-time - when running seti or other permanent running programms there is no idle time. I asume there are several more possbilities. But it sounds like there is something broken with your configuration. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de 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?19990628080407.A43878>