From owner-freebsd-current Wed Feb 16 17:41:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E1DEE37B595 for ; Wed, 16 Feb 2000 17:41:43 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 0D6BA132E0 for ; Wed, 16 Feb 2000 17:40:58 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id SAA18035; Wed, 16 Feb 2000 18:09:40 -0800 (PST) Date: Wed, 16 Feb 2000 18:09:40 -0800 From: Alfred Perlstein To: Joao Pedras Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing Message-ID: <20000216180940.K3509@fw.wintelcom.net> References: <20000216175242.J3509@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jpedras@webvolution.net on Thu, Feb 17, 2000 at 01:38:21AM -0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joao Pedras [000216 18:07] wrote: > eheh > > I mean dead frozen, like if I was watching at a screeshot of a X session ]:) > > Alfred Perlstein wrote: > > > > Do you mean dead frozen, as in needs a reboot? or frozen for a second or > > so? > > > > The first one I haven't seen recently, the second I have noticed. > > > > -Alfred oy! well i guess you need to grab a serial console and see if you can get a crashdump/traceback. let us know if you find out, also check your machine's cooling devices to make sure they are functioning normally. good luck, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message