Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 12 Nov 2017 17:32:52 +0000
From:      Ben Lavery-Griffiths <ben.lavery@hashbang0.com>
To:        freebsd-x11@freebsd.org
Subject:   Intel graphics, GPU Hung
Message-ID:  <EB6123C8-3782-42F3-8732-A87D08A5E9D9@hashbang0.com>

next in thread | raw e-mail | index | archive | help

--Apple-Mail=_0BA4708A-8A38-4920-A986-B1CE8B9AC064
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi all,

Since upgrading to FreeBSD-RELEASE 11.1 I have noticed an intermittent =
issue where XDM isn=E2=80=99t displayed after booting.  A mouse pointer =
usually appears in the middle of the screen and I=E2=80=99m able to =
control it for a short while (less than a minute).  Switching back to =
the console I am greeted with the following message:

> error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer =
elapsed... GPU hung
> info: [drm] capturing error event; look for more information in sysctl =
hw.dri.0.info.i915_error_state
> error: [drm:pid0:i915_write64] *ERROR* Unknown unclaimed register =
before writing to 100000
> error: [drm:pid908:i915_write32] *ERROR* Unknown unclaimed register =
before writing to 20a8
> error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer =
elapsed... GPU hung
> error: [drm:pid0:__gen6_gt_force_wake_mt_get] *ERROR* Timed out =
waiting for forcewake old ack to clear.
> error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer =
elapsed... GPU hung
> error: [drm:pid0:i915_reset] *ERROR* GPU hanging too fast, declaring =
wedged!
> error: [drm:pid0:i915_reset] *ERROR* Failed to reset chip.

I have uploaded the following files to a gist on Github found here: =
https://gist.github.com/forquare/2a9e1c3e6a0ec32c3a27a768f1b50371

- dmesg.boot
- loader.conf
- messages
- rc.conf
- sysctl.conf
- Xorg.0.log
- Output of `sysctl hw.dri.0.info.i915_error_state`

I=E2=80=99ve seen a forum post =
(https://forums.freebsd.org/threads/62831/) stating that it is an =
=E2=80=98issue=E2=80=99, but haven=E2=80=99t managed to find anything =
else.  Is there some setting which is causing this?  Or a regression =
that will likely be remain unfixed for a time?

Many thanks,
Ben

--Apple-Mail=_0BA4708A-8A38-4920-A986-B1CE8B9AC064
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEpEFxlQLsjMAZmK8lHyTmPTeQW3EFAloIhcQACgkQHyTmPTeQ
W3HwUwgAsfjObDg3/JbzBUMc7XlRKiQtsYofAdn2U5s44Ar2UgD3qvrKsrvm/0nA
KoxsVTW1wihbVoF4epXf+roLtpgcDh7ETsMeU9HbXA5uW85SWJFeyRbFtUWfp7eP
Ok8wjsXegAADNhw7bgz22SXdYkq2SuB6siH3SNHym5dq5BZC0b3DzyBvJw2feaUa
Z5qm4PSWg1ggZAGKovR0wBGfq7jhKUoCiPcNuAMry4Fd61gDCbEnrKM9RkfHCzxD
gaLtx2Cw7AO1EbiUnqBHzbA0sKLLNiG7HG7eOQPM7JMXV0bhzSiwEDrbEzUAtHk0
x/xuJOk8wN9amO63FEFu15aWmwhjWA==
=cUys
-----END PGP SIGNATURE-----

--Apple-Mail=_0BA4708A-8A38-4920-A986-B1CE8B9AC064--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EB6123C8-3782-42F3-8732-A87D08A5E9D9>