Bug 887512

Created attachment 664114 [details]
/sys/debugfs/dri/0/i915_error_state log

Dec 15 16:47:58 fedora kernel: [  178.844222] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Dec 15 16:47:58 fedora kernel: [  178.844230] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
Dec 15 16:48:05 fedora kernel: [  185.884221] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Dec 15 16:48:05 fedora kernel: [  185.936246] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 head 00001000 tail 00000000 start 00001000
Dec 15 16:48:06 fedora kernel: [  187.516237] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Dec 15 16:48:06 fedora kernel: [  187.516572] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
Dec 15 16:48:06 fedora kernel: [  187.516576] [drm:i915_reset] *ERROR* Failed to reset chip.

Ilyes Gouta reports on devel mailing list :  
"Just testing the 2.20.16 release and everything looks good so far on GM45." 

so, Ajax, please update xorg-x11-drv-intel to 2.20.16  

Thanks,

xorg-x11-drv-intel-2.20.17-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.20.17-1.fc17

Package xorg-x11-drv-intel-2.20.17-1.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-intel-2.20.17-1.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-0242/xorg-x11-drv-intel-2.20.17-1.fc17
then log in and leave karma (feedback).

I just had a re-occurence while writing a Fedora image to a USB flash drive and scrolling in Google Chrome:

Jan  5 02:47:11 slayer kernel:[ 2015.920015] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Jan  5 02:47:11 slayer kernel:[ 2015.920021] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
Jan  5 02:47:17 slayer kernel:[ 2021.940013] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Jan  5 02:47:17 slayer kernel:[ 2021.992015] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 head 00003000 tail 00000000 start 00003000
Jan  5 02:47:19 slayer kernel:[ 2023.496013] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
Jan  5 02:47:19 slayer kernel:[ 2023.496106] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
Jan  5 02:47:19 slayer kernel:[ 2023.496111] [drm:i915_reset] *ERROR* Failed to reset chip.
Jan  5 02:47:21 slayer kernel:[ 2025.448636] chrome[14351]: segfault at 218 ip 00007faf910070ac sp 00007fff0167c5b0 error 4 in i965_dri.so[7faf90f8a000+3f6000]
Jan  5 02:47:21 slayer kernel:[ 2025.681673] chrome[14388]: segfault at 218 ip 00007f00658c10ac sp 00007ffff9857c80 error 4 in i965_dri.so[7f0065844000+3f6000]


Running on Intel 4500HD on a fully updated Fedora 17 x86_64 system with:

$ uname -r
3.7.1-1.fc19.x86_64

$ rpm -q xorg-x11-drv-intel
xorg-x11-drv-intel-2.20.17-1.fc17.x86_64

Hi Mace,

(In reply to comment #6)
> I just had a re-occurence while writing a Fedora image to a USB flash drive
> and scrolling in Google Chrome:
> 
> Jan  5 02:47:11 slayer kernel:[ 2015.920015] [drm:i915_hangcheck_hung]
> *ERROR* Hangcheck timer elapsed... GPU hung
> Jan  5 02:47:11 slayer kernel:[ 2015.920021] [drm] capturing error event;
> look for more information in /debug/dri/0/i915_error_state
> Jan  5 02:47:17 slayer kernel:[ 2021.940013] [drm:i915_hangcheck_hung]
> *ERROR* Hangcheck timer elapsed... GPU hung
> Jan  5 02:47:17 slayer kernel:[ 2021.992015] [drm:init_ring_common] *ERROR*
> render ring initialization failed ctl 0001f001 head 00003000 tail 00000000
> start 00003000
> Jan  5 02:47:19 slayer kernel:[ 2023.496013] [drm:i915_hangcheck_hung]
> *ERROR* Hangcheck timer elapsed... GPU hung
> Jan  5 02:47:19 slayer kernel:[ 2023.496106] [drm:i915_reset] *ERROR* GPU
> hanging too fast, declaring wedged!
> Jan  5 02:47:19 slayer kernel:[ 2023.496111] [drm:i915_reset] *ERROR* Failed
> to reset chip.
> Jan  5 02:47:21 slayer kernel:[ 2025.448636] chrome[14351]: segfault at 218
> ip 00007faf910070ac sp 00007fff0167c5b0 error 4 in
> i965_dri.so[7faf90f8a000+3f6000]
> Jan  5 02:47:21 slayer kernel:[ 2025.681673] chrome[14388]: segfault at 218
> ip 00007f00658c10ac sp 00007ffff9857c80 error 4 in
> i965_dri.so[7f0065844000+3f6000]
> 
> 
> Running on Intel 4500HD on a fully updated Fedora 17 x86_64 system with:
> 
> $ uname -r
> 3.7.1-1.fc19.x86_64

That's from rawhide?

> 
> $ rpm -q xorg-x11-drv-intel
> xorg-x11-drv-intel-2.20.17-1.fc17.x86_64

Otherwise, would it be possible to attach your Xorg.0.log log and /sys/debugfs/dri/0/i915_error_state log to the ticket?

Please also consider filing the bug upstream (https://bugs.freedesktop.org/enter_bug.cgi?product=xorg).

-Ilyes

Created attachment 672992 [details]
Xorg.0.log

>> $ uname -r
>> 3.7.1-1.fc19.x86_64
>
>That's from rawhide?

From the fedora-rawhide-kernel-nodebug.repo, per:

http://fedoraproject.org/wiki/RawhideKernelNodebug

The Xorg.0.log is attached; I didn't collect the i915_error_state at the time of the failure.

Another recurrence after completing the upgrade to Fedora 18-rc1 today, while rsyncing files to another system.  I'll attach the Xorg.0.log and i915_error_state.

Ignore the above.  The upgrade to Fedora 18 downgraded the xorg-x11-drv-intel.  Sigh.

xorg-x11-drv-intel-2.20.18-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.20.18-1.fc17

xorg-x11-drv-intel-2.21.2-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.21.2-1.fc17

xorg-x11-drv-intel-2.21.2-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.