dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Kasak <d.j.kasak.dk@gmail.com>, dri-devel@lists.freedesktop.org
Subject: Re: Intel HD Graphics 4000 - hard lockups
Date: Mon, 03 Mar 2014 16:26:48 +0200	[thread overview]
Message-ID: <87ob1npdcn.fsf@intel.com> (raw)
In-Reply-To: <CAF73Y=RGNvgNsWov3ZEi_eJkhFnB2=KsEFAFbTSkDv8B97Y4sw@mail.gmail.com>

On Sat, 01 Mar 2014, Daniel Kasak <d.j.kasak.dk@gmail.com> wrote:
> Hi all.
>
> I've had quite a decent run with stability on my laptop, until recently.
> I've been running realtime kernels for audio work, and up to 3.10.6-rt3,
> it's been rock solid. After this, something has gone horribly wrong. I get
> hard lockups from anything later I've built ( 3.12.10-rt15 and 3.12.11-rt17
> ). Sometimes it won't lock up right away, but will pause for a long period,
> and when it starts responding again ( dropping to console, and back into X
> will sometimes free it ) shows a bunch of 'stuck in render loop' / 'render
> ring' ... or something ... kind of errors. I have followed instructions to
> get more info on this if someone wants it.
>
> Chrome seems to trigger lockups more than other things. I run a 3D
> composited desktop ( Enlightenment-0.19 dev builds ), but I've tried with
> Gnome-3.10 and this also gives lockups. I currently have mesa-10.0.3.
>
> What can I do to try to debug this? Often, the magic sysrq keys don't
> respond, but *occasionally* I can at least do an emergency sync.
>
> Switching back to 3.10.6-rt3 makes things *rock* solid, but for various
> reasons, I'd like to get to at least 3.12.x ( other driver issues ).
>
> What's the state of Intel DRM drivers in the kernel? Should I be avoiding
> building from the kernel, and using a git branch? Are there known issues
> with the realtime patches?
>
> Any help appreciated.

I think the first step would be to try vanilla non-rt kernels, maybe a
kernel matching what you've tried, or the latest v3.13 or v3.14-rc's. It
will be easier to proceed from there depending on the outcome.

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

      reply	other threads:[~2014-03-03 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01  4:18 Intel HD Graphics 4000 - hard lockups Daniel Kasak
2014-03-03 14:26 ` Jani Nikula [this message]

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=87ob1npdcn.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=d.j.kasak.dk@gmail.com \
    --cc=dri-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox