From owner-freebsd-chat Fri Sep 22 16:33:37 2000 Delivered-To: freebsd-chat@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 90B9E37B43F; Fri, 22 Sep 2000 16:33:32 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id QAA53920; Fri, 22 Sep 2000 16:33:32 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 22 Sep 2000 16:33:31 -0700 (PDT) From: Kris Kennaway To: John Baldwin Cc: Sergey Babkin , chat@Freebsd.org Subject: Re: VM troubles in -current ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 22 Sep 2000, John Baldwin wrote: > The symptoms you describe (runs fine for a while and then dies) are very > indicative of hardware that is overheating and then having errors, so you > also probably want to check your fans, etc. Running a buildworld pushes the > machine harder. :) Also, having gcc generate code that jumps into the > middle of an instruction is a very, very low probability. Apparently, the > solar activity is at one of its peaks this year, thus resulting a lot more > failures than usual. Significantly more failures from what I've been told. > Having tens of machines start spewwing ECC corrections and eventually > errors after only being up for a couple of days and stuff like that. Without wanting to make a comment about the possible likelihood of solar activity causing this particular problem: http://news.bbc.co.uk/hi/english/sci/tech/newsid_936000/936606.stm :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message