linux-kernel - Re: i915 drm GPU hung errors with kernel 2.6.38.2 on 82865G chipset

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1bdc18$k8bgo3@fmsmga002.fm.intel.com>
Date:	Sat, 16 Apr 2011 07:07:35 +0100
From:	Chris Wilson <chris@...is-wilson.co.uk>
To:	wzab@....pw.edu.pl, linux-kernel@...r.kernel.org
Subject: Re: i915 drm GPU hung errors with kernel 2.6.38.2 on  82865G chipset

On Fri, 15 Apr 2011 23:07:51 +0200, wzab <wzab@....pw.edu.pl> wrote:
> Today I have experienced two "GPU hungs" on machine with 82865G chipset 
> working with 2.6.38.2 kernel
> In the /var/log/syslog I have found the following errors:
> 
> Apr 15 22:50:51 wzab kernel: [drm:i915_hangcheck_elapsed] *ERROR* 
> Hangcheck timer elapsed... GPU hung

As Bruno said there is a /sys/kernel/debug/dri/0/i915_error_state file
that contains a GPU dump at the time of the error which often contains the
vital clue at to what went wrong. If you can also think back to what was
happening on the machine at the time of the hang, that can also help
identify the trigger and the suspect code.

Thanks,
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/