Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Aug 2012 19:29:53 -0700
From:      Matthew Navarre <navarre.matthew@gmail.com>
To:        Warren Block <wblock@wonkity.com>
Cc:        Gary Aitken <freebsd@dreamchaser.org>, Matthew Seaman <matthew@freebsd.org>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: 9.0 release hang in quiescent X
Message-ID:  <2884687D-E263-4E07-A013-BCA1CEC7E9E6@gmail.com>
In-Reply-To: <alpine.BSF.2.00.1208171955020.1307@wonkity.com>
References:  <502C7AFB.2020303@dreamchaser.org> <502C8D88.9040901@FreeBSD.org> <502EA0AB.9050708@dreamchaser.org> <alpine.BSF.2.00.1208171437030.62252@wonkity.com> <502EE033.8020402@dreamchaser.org> <alpine.BSF.2.00.1208171955020.1307@wonkity.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help


On Aug 17, 2012, at 7:00 PM, Warren Block <wblock@wonkity.com> wrote:

> On Fri, 17 Aug 2012, Gary Aitken wrote:
>=20
>> On 08/17/12 14:44, Warren Block wrote:
>>=20
>>> If that stops the lockups, then you could try setting each in turn to a n=
on-zero value (minutes).  Leave everything at zero except for the one being t=
ested.  But these also seem unlikely, as it's a hardware signal from the vid=
eo board to the monitor.  The suggestion of an X screensaver causing the loc=
kup was excellent.  Even if you have no screensavers, there are other things=
 that could be triggered, like xlock.
>>=20
>> Not sure I understand what you're getting at.  By "other things that coul=
d 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 u=
pdate request while blanked out that is causing trouble?
>=20
> Other long-term events that happen might be to blame, not related to scree=
n 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 w=
ould 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 go=
t 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.

OK,
MCN=



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?2884687D-E263-4E07-A013-BCA1CEC7E9E6>