Bug 697693 - [Cantiga] GPU Hung
Summary: [Cantiga] GPU Hung
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:lockup]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-18 22:27 UTC by mattho.l2p
Modified: 2018-04-11 08:01 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:40:29 UTC
Type: ---


Attachments (Terms of Use)
dmesg (123.08 KB, text/plain)
2011-05-11 17:54 UTC, mattho.l2p
no flags Details
messages (109.06 KB, text/plain)
2011-05-11 17:55 UTC, mattho.l2p
no flags Details
Xorg.0.log (54.42 KB, text/plain)
2011-05-11 17:56 UTC, mattho.l2p
no flags Details

Description mattho.l2p 2011-04-18 22:27:19 UTC
Description of problem:
 GPU Hung often occurs with smplayer's "updating font cache". i.e. smplayer starts, writes out that I should wait because its updating font cache and then (1-3s) gpu crashes. Messages show this:

kernel: [46908.340024] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
kernel: [46908.344676] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 1632146 at 1632145, next 1632153)
kernel: [46910.012022] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
kernel: [46910.513042] [drm:i915_reset] *ERROR* Failed to reset chip.



Version-Release number of selected component (if applicable):
-kernel version:
  2.6.38-5.fc15.x86_64
-Graphics card:
  Intel GMA 4500MHD

How reproducible:
 Happens every time the "updating font cache" message in smplayer appears (at least for such time I'm able to detect it).


Steps to Reproduce:
1. start smplayer randomly
2. crash occurs
  
Actual results:
-


Expected results:
-

Additional info:
- Graphic-related oopses (drm_ht_insert_item) and gpu hangs aren't new with this kernel. It's just that this crash is associated with particular action. Before it was "random".
- I'm unable to start X after this crash so I reboot (WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors). Other than that everything seems ok.
-I have dump created with intel_gpu_dump after the crash. Will uplaod it if it might help.

Comment 1 mattho.l2p 2011-04-23 22:48:32 UTC
Tried standalone mplayer and vlc - crash occurs too.

Comment 2 Matěj Cepl 2011-04-27 23:04:48 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 mattho.l2p 2011-05-11 17:52:51 UTC
Ok, I've added drm.debug=0x04 to kernel command line. Attached files (will) contain:

* dmesg output after the crash occured
* messages from the time crash occured to after the boot (so there is crash, shutdown and subsequent boot)
* Xorg.0.log file. It is quite big as it is probably cummulative log. I only use one display most of the time so I guess other Xorg log files (1-5, 9) are unrelated.

I do not have xorg.conf file.

PS: I changed kernel build since. I now have 2.6.38.5-24.fc15.x86_64
(problem still occurs)

Comment 4 mattho.l2p 2011-05-11 17:54:39 UTC
Created attachment 498361 [details]
dmesg

Comment 5 mattho.l2p 2011-05-11 17:55:44 UTC
Created attachment 498364 [details]
messages

Comment 6 mattho.l2p 2011-05-11 17:56:12 UTC
Created attachment 498365 [details]
Xorg.0.log

Comment 7 Fedora End Of Life 2012-08-07 14:40:32 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.