From owner-freebsd-current Tue Mar 3 13:48:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16436 for freebsd-current-outgoing; Tue, 3 Mar 1998 13:48:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16430 for ; Tue, 3 Mar 1998 13:48:37 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id VAA19201 for ; Tue, 3 Mar 1998 21:48:35 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id WAA01431; Tue, 3 Mar 1998 22:48:35 +0100 (MET) Message-ID: <19980303224835.36978@follo.net> Date: Tue, 3 Mar 1998 22:48:35 +0100 From: Eivind Eklund To: current@FreeBSD.ORG Subject: xlock freezes last two weeks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had 3 or 4 freezes while the computer is in xlock these last two weeks; never happened before. All of them have been while the screensaver was that large circle-like thing (lots of line forming a complex circular pattern) with cycling. I've also had two crashes while doing large compiles. FreeBSD has been completely locked; not even answering pings. Anybody have a clue as to what could cause this? (dmesgs etc available on request - interesting hardware is PPro 200, Asus MB, Adaptec 2940, and Miro PCTV (brooktree driver)). The Miro was not in use (at least some of the time). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message