From: cpollock@embarqmail.com (Chris)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel: [154858.820009] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed.
Date: Mon, 15 Dec 2014 15:17:32 -0600 [thread overview]
Message-ID: <1418678252.2852.7.camel@embarqmail.com> (raw)
In-Reply-To: <241246.1418677915@turing-police.cc.vt.edu>
On Mon, 2014-12-15 at 16:11 -0500, Valdis.Kletnieks at vt.edu wrote:
> On Mon, 15 Dec 2014 14:19:32 -0600, Chris said:
> > On Mon, 2014-12-15 at 13:43 -0500, Valdis.Kletnieks at vt.edu wrote:
>
> > > I'm pretty sure that's a timer for the i915 driver that detects if the
> > > GPU has gone into an infinite loop due to (usually) buggy programming from
> > > the operating system....
> >
> > Thank you Valdis as far as the OS we're talking about Ubuntu not the
> > bios correct?
>
> More specifically, the i915 is actually a fully programmable CPU in its own
> right, but it's a crazy morass of interrupts and circular buggers
> and race conditions. The operating system (Ubuntu or what have you) actually
> send the i915 a program of what to display, and the i915 goes off and does it.
> Of course, missing a single interrupt or an off-by-one error in a circular
> buffer will cause the i915 to go off the rails and usually get hung in a hard
> loop.
>
> (It doesn't help that the i915 has a ton of wonky restrictions of the form "you
> can do this during a vertical retrace period, but only during the first half
> of a horizontal retrace". And yes, I'm pretty sure it actually enforces
> vertical and horizontal retrace timings on LCDs. Silly, huh? ;)
I believe I understand Valdis, what kind of actions would need to be
taken to track this down, if it's possible, or to simply fix the problem
once and for all?
--
Chris
KeyID 0xE372A7DA98E6705C
31.11?N 97.89?W (Elev. 1092 ft)
15:16:18 up 3:21, 3 users, load average: 0.17, 0.19, 0.18
Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
next prev parent reply other threads:[~2014-12-15 21:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 14:02 kernel: [154858.820009] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed Chris
2014-12-15 16:58 ` Greg KH
2014-12-15 17:59 ` Chris
2014-12-15 18:01 ` Greg KH
2014-12-15 18:43 ` Valdis.Kletnieks at vt.edu
2014-12-15 20:19 ` Chris
2014-12-15 21:11 ` Valdis.Kletnieks at vt.edu
2014-12-15 21:17 ` Chris [this message]
2014-12-15 22:54 ` Valdis.Kletnieks at vt.edu
2014-12-15 23:57 ` Chris
2014-12-16 2:04 ` Valdis.Kletnieks at vt.edu
2014-12-16 2:09 ` Chris
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=1418678252.2852.7.camel@embarqmail.com \
--to=cpollock@embarqmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).