From owner-freebsd-questions@FreeBSD.ORG Sat Aug 18 02:00:33 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 211B6106564A; Sat, 18 Aug 2012 02:00:33 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id CFF2F8FC0A; Sat, 18 Aug 2012 02:00:32 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q7I20TFU001354; Fri, 17 Aug 2012 20:00:29 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q7I20Rfl001351; Fri, 17 Aug 2012 20:00:29 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Fri, 17 Aug 2012 20:00:27 -0600 (MDT) From: Warren Block To: Gary Aitken In-Reply-To: <502EE033.8020402@dreamchaser.org> Message-ID: References: <502C7AFB.2020303@dreamchaser.org> <502C8D88.9040901@FreeBSD.org> <502EA0AB.9050708@dreamchaser.org> <502EE033.8020402@dreamchaser.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Fri, 17 Aug 2012 20:00:29 -0600 (MDT) Cc: Matthew Seaman , freebsd-questions@freebsd.org Subject: Re: 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: Sat, 18 Aug 2012 02:00:33 -0000 On Fri, 17 Aug 2012, Gary Aitken wrote: > On 08/17/12 14:44, Warren Block wrote: > >> If that stops the lockups, then you could try setting each in turn to >> a non-zero value (minutes). Leave everything at zero except for the >> one being tested. But these also seem unlikely, as it's a hardware >> signal from the video board to the monitor. The suggestion of an X >> screensaver causing the lockup was excellent. Even if you have no >> screensavers, there are other things that could be triggered, like >> xlock. > > Not sure I understand what you're getting at. By "other things that > could be triggered" what do you mean? e.g. xclock obviously gets > "triggered" at least once per minute; you're suggesting that event > could be causinging an update request while blanked out that is > causing trouble? Other long-term events that happen might be to blame, not related to screen blanking at all. For example, a cron job.