Date: Fri, 17 Aug 2012 20:00:27 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Gary Aitken <freebsd@dreamchaser.org> Cc: Matthew Seaman <matthew@freebsd.org>, freebsd-questions@freebsd.org Subject: Re: 9.0 release hang in quiescent X Message-ID: <alpine.BSF.2.00.1208171955020.1307@wonkity.com> In-Reply-To: <502EE033.8020402@dreamchaser.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1208171955020.1307>