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 14:19:32 -0600 [thread overview]
Message-ID: <1418674772.2852.5.camel@embarqmail.com> (raw)
In-Reply-To: <233694.1418668997@turing-police.cc.vt.edu>
On Mon, 2014-12-15 at 13:43 -0500, Valdis.Kletnieks at vt.edu wrote:
> On Mon, 15 Dec 2014 10:01:54 -0800, Greg KH said:
> > On Mon, Dec 15, 2014 at 11:59:27AM -0600, Chris wrote:
>
> > > That's what I thought Greg but wanted to make sure. AFAIK I'm not having
> > > any hardware related issues but I would like to know what the 'Hangcheck
> > > timer' is. Possibly you can enlighten me?
> >
> > That looks like a driver-specific timer, the code would tell you more,
> > take a look at it!
>
> 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?
Chris
--
Chris
KeyID 0xE372A7DA98E6705C
31.11?N 97.89?W (Elev. 1092 ft)
14:12:54 up 2:17, 1 user, load average: 0.26, 0.18, 0.15
Ubuntu 14.04.1 LTS, kernel 3.13.0-43-generic
next prev parent reply other threads:[~2014-12-15 20:19 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 [this message]
2014-12-15 21:11 ` Valdis.Kletnieks at vt.edu
2014-12-15 21:17 ` Chris
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=1418674772.2852.5.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).