From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel: [154858.820009] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed.
Date: Mon, 15 Dec 2014 10:01:54 -0800 [thread overview]
Message-ID: <20141215180154.GA4962@kroah.com> (raw)
In-Reply-To: <1418666367.2852.1.camel@embarqmail.com>
On Mon, Dec 15, 2014 at 11:59:27AM -0600, Chris wrote:
> On Mon, 2014-12-15 at 08:58 -0800, Greg KH wrote:
> > On Mon, Dec 15, 2014 at 08:02:13AM -0600, Chris wrote:
> > > I'm hoping I can get some advice/help here on this list with the above
> > > problem that is causing system lockups. I didn't want to post to the
> > > main list as I'm not sure it would be appropriate, I'm not even sure
> > > it's appropriate here but I'll give it a try. If someone has a better
> > > list to post to please let me know.
> > >
> > > I have noticed the lockups periodically since 09/13/2014. I can't
> > > remember what kernel version was in use then possibly kernel
> > > 3.13.0-35-generic or -36. It has continued periodically through versions
> > > -39; -40 and now to -43. The last time this has happened was Dec 13
> > > 14:40:57 localhost kernel: [154858.820009] [drm:i915_hangcheck_
> > > elapsed] *ERROR* Hangcheck timer elapsed... render ring idle. At times
> > > when it locks up I will have a cursor on a black screen and will have to
> > > press the power button to restart other times it will lockup whenever
> > > I'm in an application. At that time I can usually CTRL>ALT-F1 log in and
> > > run 'sudo reboot' to restart the system.
> > >
> > > Kernel version information is:
> > >
> > > Linux version 3.13.0-43-generic (buildd at tipua) (gcc version 4.8.2
> > > (Ubuntu 4.8.2-19ubuntu1) ) #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
> > > (Ubuntu 3.13.0-43.72-generic 3.13.11.11)
> >
> > That's a very old distro-specific kernel, try building a kernel.org
> > release (like 3.18) and see if the problem is still there or not. No
> > one in the community can help with old, distro-specific kernels, except
> > for the distro itself.
> >
> > There are lots of Intel graphic driver changes happening in the kernel,
> > I strongly recommend updating if you have an issue with your hardware.
> > I got 2 _hours_ battery life extension in the 3.17 kernel alone due to
> > Intel driver fixes.
> >
> > good luck,
> >
> > greg k-h
> >
> 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!
greg k-h
next prev parent reply other threads:[~2014-12-15 18:01 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 [this message]
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
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=20141215180154.GA4962@kroah.com \
--to=greg@kroah.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).