Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Clifton <pcjc2@cam.ac.uk>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: gpu freeze
Date: Sat, 30 Oct 2010 20:09:57 +0100	[thread overview]
Message-ID: <1288465797.26900.3.camel@pcjc2lap> (raw)
In-Reply-To: <1288462951.5285.7.camel@zwerg>

On Sat, 2010-10-30 at 20:22 +0200, Alexey Fisher wrote:
> What info should i collect if i get GPU hung?
> 
> I currently get one, with kernel 2.6.36-07532-gbbe2e11
> it happened after i started video. Interesting is my PC worked 15 hours,
> many things was done it was not first video. So fear i can't reproduce
> or bisect it. This is first hung for some weeks or months...

As a non-expert, non-canonical answer (in the non-commercial sense of
the word canonical), I would primarily be interested in saving the
contents of /sys/kernel/debug/dri/0/i915_error_state

You can decompile that with "intel_error_decode $file"

Also, note if there are any interesting messages in dmesg pertaining to
drm / gem / i915 (caps or non-caps for all), and anything unusual in the
end of /var/log/Xorg.0.log or /var/log/Xorg.0.log.old if your X server
has restarted.

The error state ought to be relevant to the hang assuming you've not
rebooted or had any subsequent hangs.

Best wishes,

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)

      reply	other threads:[~2010-10-30 19:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 18:22 gpu freeze Alexey Fisher
2010-10-30 19:09 ` Peter Clifton [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=1288465797.26900.3.camel@pcjc2lap \
    --to=pcjc2@cam.ac.uk \
    --cc=bug-track@fisher-privat.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox