Skip to contentSkip to conversation

"Hangcheck timer elapsed... GPU hung" in 3.8.0-rc2

DISCUSSION J. Bruce Fields 3 participants 7 messages Jan 3, 2013 – Jan 9, 2013

lore
Share & tools
lore
#0 lore raw

I got a crash after a few minutes of running 3.8.0-rc2, was able to switch to a vt and look at dmesg:

  [  490.962545] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  490.963019] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
  [  492.961446] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  492.965613] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
  [  492.965621] [drm:i915_reset] *ERROR* Failed to reset chip.  

Previously I was on 3.6.10-2.fc17.x86_64, which didn't have any such problem.

dmesg, config, and i915_error_state available from:

	http://fieldses.org/~bfields/3.8-hang/

--b.

#1 lore raw
Quoted 11 lines · J. Bruce Fields

I got a crash after a few minutes of running 3.8.0-rc2, was able to switch to a vt and look at dmesg:

  [  490.962545] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  490.963019] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
  [  492.961446] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  492.965613] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
  [  492.965621] [drm:i915_reset] *ERROR* Failed to reset chip.

Previously I was on 3.6.10-2.fc17.x86_64, which didn't have any such problem.

I'm not questioning that you haven't seen that error in F17, but we have had quite a few bug reports with similar error messages for a while now. Apparently there are lots of ways GPUs can get hung, so they might be different from what you're seeing. Just wanted to point out that it might not be a new 3.8 change that caused it.

josh

#2 lore raw
Quoted 10 lines · Josh Boyer
Quoted 9 lines · J. Bruce Fields

I got a crash after a few minutes of running 3.8.0-rc2, was able to switch to a vt and look at dmesg:

  [  490.962545] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  490.963019] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
  [  492.961446] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  492.965613] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
  [  492.965621] [drm:i915_reset] *ERROR* Failed to reset chip.
Quoted 8 lines
Quoted 2 lines

Previously I was on 3.6.10-2.fc17.x86_64, which didn't have any such problem.

I'm not questioning that you haven't seen that error in F17, but we have had quite a few bug reports with similar error messages for a while now. Apparently there are lots of ways GPUs can get hung, so they might be different from what you're seeing. Just wanted to point out that it might not be a new 3.8 change that caused it.

OK, sure. It reproduced very quickly after the upgrade, so I assumed it was a regression.

I'm running 3.7.0 now which hasn't shown any problem.

I'll try a newer kernel again to see if it's really that easy for me to reproduce.

--b.

#3 lore raw
Quoted 20 lines · J. Bruce Fields
Quoted 10 lines · Josh Boyer
Quoted 9 lines · J. Bruce Fields

I got a crash after a few minutes of running 3.8.0-rc2, was able to switch to a vt and look at dmesg:

  [  490.962545] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  490.963019] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
  [  492.961446] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  492.965613] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
  [  492.965621] [drm:i915_reset] *ERROR* Failed to reset chip.
Quoted 8 lines
Quoted 2 lines

Previously I was on 3.6.10-2.fc17.x86_64, which didn't have any such problem.

I'm not questioning that you haven't seen that error in F17, but we have had quite a few bug reports with similar error messages for a while now. Apparently there are lots of ways GPUs can get hung, so they might be different from what you're seeing. Just wanted to point out that it might not be a new 3.8 change that caused it.

Quoted 7 lines

OK, sure. It reproduced very quickly after the upgrade, so I assumed it was a regression.

I'm running 3.7.0 now which hasn't shown any problem.

I'll try a newer kernel again to see if it's really that easy for me to reproduce.

If you hit this again (even better if you have a way to reproduce) please grab the i915_error_state file from debugfs and file a bug on bugs.freedesktop.org against DRM - DRI (Intel). We do know of a few recent issues introduced around 3.7 kernels, preliminary patches are floating around. The error state should be good enough to decide whether you're hitting the same issues.

Thanks, Daniel

Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
#4 lore raw
Quoted 24 lines · Daniel Vetter
Quoted 23 lines · J. Bruce Fields
Quoted 10 lines · Josh Boyer
Quoted 9 lines · J. Bruce Fields

I got a crash after a few minutes of running 3.8.0-rc2, was able to switch to a vt and look at dmesg:

  [  490.962545] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  490.963019] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
  [  492.961446] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
  [  492.965613] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
  [  492.965621] [drm:i915_reset] *ERROR* Failed to reset chip.
Quoted 8 lines
Quoted 2 lines

Previously I was on 3.6.10-2.fc17.x86_64, which didn't have any such problem.

I'm not questioning that you haven't seen that error in F17, but we have had quite a few bug reports with similar error messages for a while now. Apparently there are lots of ways GPUs can get hung, so they might be different from what you're seeing. Just wanted to point out that it might not be a new 3.8 change that caused it.

OK, sure. It reproduced very quickly after the upgrade, so I assumed it was a regression.

Quoted 6 lines
Quoted 4 lines

I'm running 3.7.0 now which hasn't shown any problem.

I'll try a newer kernel again to see if it's really that easy for me to reproduce.

If you hit this again (even better if you have a way to reproduce)

Unfortunately I wasn't able to reproduce after working a couple more hours on 3.8 again. However:

Quoted 1 line

please grab the i915_error_state file from debugfs

As I said in the original mail, I've already done that:

	http://fieldses.org/~bfields/3.8-hang/
Quoted 2 lines

and file a bug on
bugs.freedesktop.org against DRM - DRI (Intel).

Would it still be useful for me to file a bug? (Just going through the new-account confirmation dance now.)

--b.

Quoted 10 lines

We do know of a few recent
issues introduced around 3.7 kernels, preliminary patches are floating around. The error state should be good enough to decide whether you're hitting the same issues.

Thanks, Daniel

Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
#5 lore raw
Quoted 5 lines · J. Bruce Fields
Quoted 1 line

please grab the i915_error_state file from debugfs

As I said in the original mail, I've already done that:

        http://fieldses.org/~bfields/3.8-hang/

Sorry, missed that the first time around.

Quoted 5 lines
Quoted 2 lines

and file a bug on
bugs.freedesktop.org against DRM - DRI (Intel).

Would it still be useful for me to file a bug? (Just going through the new-account confirmation dance now.)

Looks like the ilk bug tracked at
https://bugs.freedesktop.org/show_bug.cgi?id=55984

-Daniel

Signature · 3 lines
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
#6 lore raw
Quoted 9 lines · Daniel Vetter
Quoted 5 lines · J. Bruce Fields
Quoted 1 line

please grab the i915_error_state file from debugfs

As I said in the original mail, I've already done that:

        http://fieldses.org/~bfields/3.8-hang/

Sorry, missed that the first time around.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

and file a bug on
bugs.freedesktop.org against DRM - DRI (Intel).

Would it still be useful for me to file a bug? (Just going through the new-account confirmation dance now.)

Looks like the ilk bug tracked at
https://bugs.freedesktop.org/show_bug.cgi?id=55984

OK, I'll add something there if I'm available to find a reproducer. Thanks!

--b.