From: Chris <cpollock@embarqmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Video freezes continue to plague me
Date: Tue, 15 Mar 2016 17:43:29 -0500 [thread overview]
Message-ID: <1458081809.2460.25.camel@embarqmail.com> (raw)
In-Reply-To: <56E87298.9040201@earthlink.net>
On Tue, 2016-03-15 at 16:37 -0400, Felix Miata wrote:
> Chris composed on 2016-03-15 14:50 (UTC-0500):
>
> > My system is a Dell Optiplex 780.
>
> Which? Tower? Desktop? SFF? USFF?
Sorry, it's a desktop
>
> > I've filed several bug reports both
> > with the Intel Graphics Bugzilla and the Ubuntu Launchpad pages.
> > Initially back when this started in 2014 every 'freeze' would result in
> > an error of [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer
> > elapsed... render ring idle' in syslog. It would happen every few days
> > or so and nothing that was done would correct the problem....
>
> Was ensuring heat is a non-issue also done? SFF & USFF models tend to run
> rather hot, so accumulated dust, and especially tobacco tar, within,
> especially within the power supply, can become an intermittent problem for
> software.
Currently it's 87F outside. I have a window open directly behind the
system and a fan blowing on the front of it. We're just not ready to
turn the AC on yet. CPU0 is running around 116F and CPU1 109F. This
whole issue of the video freezing whether it's with or without the
Hangcheck error has been ongoing here on my system since 13 Sept 2014.
The last time the video froze with the Hangcheck error was Jan 17 2016.
Since then the video has frozen without the error on 1/21/16; 1/27/16;
2/25/16; 3/08/16; 3/11/16; and today 3/15/16 at 09:50am. I came back to
the desktop at around 11am to find it frozen at 9:50. I moved the mouse,
the video flickered and the clock caught up and came unfrozen. The only
thing in my syslog for that time is:
09:50:07 localhost kernel: [347769.284331] [drm:drm_mode_addfb2] [FB:60]
09:50:07 localhost kernel: [347769.303256] [drm:drm_mode_addfb2] [FB:62]
09:50:07 localhost kernel: [347769.324369] [drm:drm_mode_addfb2] [FB:63]
--
Chris
KeyID 0xE372A7DA98E6705C
31.11°N 97.89°W (Elev. 1092 ft)
17:25:15 up 5:37, 1 user, load average: 0.85, 0.58, 0.44
Ubuntu 14.04.4 LTS, kernel 3.19.0-56-generic #62~14.04.1-Ubuntu SMP Fri
Mar 11 11:03:15 UTC 2016
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-15 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 19:50 Video freezes continue to plague me Chris
2016-03-15 20:37 ` Felix Miata
2016-03-15 22:43 ` Chris [this message]
2016-03-15 23:17 ` Felix Miata
2016-03-16 0:29 ` Chris
2016-03-16 10:08 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1458081809.2460.25.camel@embarqmail.com \
--to=cpollock@embarqmail.com \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.