All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris <cpollock@embarqmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: *ERROR* Hangcheck timer elapsed... render ring idle
Date: Mon, 23 May 2016 17:28:57 +0300	[thread overview]
Message-ID: <871t4setli.fsf@intel.com> (raw)
In-Reply-To: <1464012539.2852.9.camel@embarqmail.com>

On Mon, 23 May 2016, Chris <cpollock@embarqmail.com> wrote:
> On Mon, 2016-05-23 at 11:06 +0300, Jani Nikula wrote:
>> On Fri, 20 May 2016, Chris <cpollock@embarqmail.com> wrote:
>> > I'm still seeing this periodically, previous to today it happened on
>> > April 24th. Doesn't matter what I'm doing the video will freeze however
>> > the cursor will still move. Only option is to SSH in to the system from
>> > my tablet and do a reboot.
>> >
>> > Note: This has been going on since Sept 13, 2014. There could be as
>> > little as a few hours between freezes or as much as 30 or more days. 
>> 
>> Your report is lacking in details... like which kernel you're running,
>> and have you tried a recent kernel.
>> 
>> Please file a bug at [1], and attach dmesg with drm.debug=14 on the bug.
>> 
>> BR,
>> Jani.
>> 
>> 
>> [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
>> 
> Jani, I have previously filed a bug or added information to a bug on
> this:

How was I supposed to know...?

> [1] https://bugs.freedesktop.org/show_bug.cgi?id=75394
> [2] https://bugs.freedesktop.org/show_bug.cgi?id=91495
>
> The kernel being run at the time of the freeze was when this post was
> made - 3.19.0-59-generic #65~14.04.1-Ubuntu SMP Tue Apr 19 18:57:09 UTC
> 2016
>
> The video froze again this morning, however the 'Hangcheck..render ring
> idle' error was not noted in my syslog. The kernel being run at the time
> this happened - 3.19.0-59-generic #66~14.04.1-Ubuntu SMP Fri May 13
> 17:27:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> I've added drm.debug=14 to my grub.cfg file to get the output you asked
> for in the next freeze. Do you want me to open a new bug or add to [1]
> or [2]?

If you keep running 3.19, neither. Please grab the latest kernel, and
run that, and update your existing bug when it occurs on that one.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-05-23 14:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 22:35 *ERROR* Hangcheck timer elapsed... render ring idle Chris
2016-05-23  8:06 ` Jani Nikula
2016-05-23 14:08   ` Chris
2016-05-23 14:28     ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-03-24 13:35 Chris
2015-03-25 13:38 ` Daniel Vetter
2015-03-27 17:13   ` 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=871t4setli.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=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.