From owner-freebsd-questions@FreeBSD.ORG Thu Aug 16 05:11:01 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 705D1106564A for ; Thu, 16 Aug 2012 05:11:01 +0000 (UTC) (envelope-from ah@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 3BB568FC0A for ; Thu, 16 Aug 2012 05:11:00 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id q7G4jmv1096651 for ; Wed, 15 Aug 2012 22:45:48 -0600 (MDT) (envelope-from ah@dreamchaser.org) Message-ID: <502C7AFB.2020303@dreamchaser.org> Date: Wed, 15 Aug 2012 22:45:47 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120609 Thunderbird/13.0 MIME-Version: 1.0 To: FreeBSD Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Wed, 15 Aug 2012 22:45:48 -0600 (MDT) Subject: 9.0 release hang in quiescent X X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2012 05:11:01 -0000 I've been struggling trying to ignore something and it refuses to go away :-(. Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/, /usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon hd5550). As long as I am using the system, things seem to be fine. However, when I leave the system idle for an extended period of time (e.g. overnight, out for the day, etc.), it often refuses to return from whatever state it is in. The screen is blank and in standby for power saving, and Fn won't get me a console prompt. The only way I know to recover is to power off and reboot. When this first happened, the file systems would come up trashed and I needed to manually fsck everything. I've gotten in the habit of doing a sync prior to leaving the system, and they now seem to come up clean when I have to reboot, but that's obviously not a solution to the problem. Xorg.0.log shows the following errors: (EE) RADEON(0): Acceleration initialization failed However, the display works fine and I'm assuming I'm just getting slow rendering, which is ok in this case. Can someone suggest a good way to proceed to figure out what's going on? Gary