From owner-freebsd-questions@FreeBSD.ORG Sat Aug 18 03:03:05 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 3AC2D106566B; Sat, 18 Aug 2012 03:03:05 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id D46738FC15; Sat, 18 Aug 2012 03:03:04 +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 q7I334tL004551; Fri, 17 Aug 2012 21:03:04 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) Message-ID: <502F05E7.3080301@dreamchaser.org> Date: Fri, 17 Aug 2012 21:03:03 -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: Matthew Navarre References: <502C7AFB.2020303@dreamchaser.org> <502C8D88.9040901@FreeBSD.org> <502EA0AB.9050708@dreamchaser.org> <502EE033.8020402@dreamchaser.org> <2884687D-E263-4E07-A013-BCA1CEC7E9E6@gmail.com> In-Reply-To: <2884687D-E263-4E07-A013-BCA1CEC7E9E6@gmail.com> 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]); Fri, 17 Aug 2012 21:03:05 -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 Reply-To: freebsd@dreamchaser.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2012 03:03:05 -0000 On 08/17/12 20:29, Matthew Navarre wrote: > > > On Aug 17, 2012, at 7:00 PM, Warren Block wrote: > >> 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. > > Just as a data point, I had the same thing happen on PC-BSD 9.0. The system would hang after just a couple minutes of inactivity, but would wake up again on keyboard input. Top showed X.org taking 100% of CPU and load averages got up to some seriously ridiculous levels. The workaround I found was to turn off the "Dim Screen" option in KDE. Never filed a bug report, since I didn't know if it was FreeBSD, PC-BSD or X.org. That's not my issue; what I'm seeing is a screen that never wakes up; or, more accurately, a system which appears to have crashed completely, since I can't rlogin either. I would guess the high load averages you saw may be related to everything in the world woken up at the same time for repaints. I would expect x.org to take 100% of cpu when woken up.