Bug 649860
| Summary: | [Bearlake] Intel i915 GPU hung | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | udayb <udayreddy> | ||||||||||
| Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | low | ||||||||||||
| Version: | 13 | CC: | ajax, christof, dougsland, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mcepl, sclark46, wallberg, xgl-maint | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i686 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-06-28 10:51:36 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
udayb
2010-11-04 17:27:56 UTC
Here are more logs.
From /var/log/messages
Nov 15 00:06:54 localhost kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Nov 15 00:06:54 localhost kernel: [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 19253102 at 19253099)
Nov 15 00:06:54 localhost kernel: ------------[ cut here ]------------
Nov 15 00:06:54 localhost kernel: WARNING: at drivers/gpu/drm/i915/i915_gem_tiling.c:337 i915_gem_set_tiling+0x156/0x1ad [i915]()
Nov 15 00:06:54 localhost kernel: Hardware name: DW137A-ABA A445W
Nov 15 00:06:54 localhost kernel: failed to reset object for tiling switch
Nov 15 00:06:54 localhost kernel: Modules linked in: vfat fat nls_utf8 fuse aes_i586 aes_generic tun ipv6 p4_clockmod arc4 snd_intel8x0 ecb snd_ac97_codec ac
97_bus snd_seq 8139too snd_seq_device 8139cp snd_pcm iTCO_wdt zd1211rw iTCO_vendor_support mii snd_timer snd ppdev i2c_i801 soundcore mac80211 snd_page_alloc parport_pc cfg80211 rfkill parport microcode serio_raw joydev usb_storage firewire_ohci firewire_core crc_itu_t i915 drm_kms_helper drm i2c_algo_bit i2c_core video output [last unloaded: scsi_wait_scan]
Nov 15 00:06:54 localhost kernel: Pid: 1276, comm: Xorg Not tainted 2.6.34.7-61.fc13.i686 #1
Nov 15 00:06:54 localhost kernel: Call Trace:
Nov 15 00:06:54 localhost kernel: [<c0438802>] warn_slowpath_common+0x6a/0x81
Nov 15 00:06:54 localhost kernel: [<f7dc4570>] ? i915_gem_set_tiling+0x156/0x1ad [i915]
Nov 15 00:06:54 localhost kernel: [<c0438857>] warn_slowpath_fmt+0x29/0x2c
Nov 15 00:06:54 localhost kernel: [<f7dc4570>] i915_gem_set_tiling+0x156/0x1ad [i915]
Nov 15 00:06:54 localhost kernel: [<f7d33ad8>] drm_ioctl+0x26d/0x359 [drm]
Nov 15 00:06:54 localhost kernel: [<f7dc441a>] ? i915_gem_set_tiling+0x0/0x1ad [i915]
Nov 15 00:06:54 localhost kernel: [<c04095cf>] ? restore_i387_fxsave+0x68/0x79
Nov 15 00:06:54 localhost kernel: [<c04dc67d>] vfs_ioctl+0x2c/0x96
Nov 15 00:06:54 localhost kernel: [<f7d3386b>] ? drm_ioctl+0x0/0x359 [drm]
Nov 15 00:06:54 localhost kernel: [<c04dcc13>] do_vfs_ioctl+0x488/0x4c6
Nov 15 00:06:54 localhost kernel: [<c0409ba4>] ? restore_i387_xstate+0x1a9/0x1e0
Nov 15 00:06:54 localhost kernel: [<c04d16d3>] ? fsnotify_access+0x54/0x5f
Nov 15 00:06:54 localhost kernel: [<c0479579>] ? audit_syscall_entry+0x118/0x13a
Nov 15 00:06:54 localhost kernel: [<c04dcc97>] sys_ioctl+0x46/0x66
Nov 15 00:06:54 localhost kernel: [<c0790944>] syscall_call+0x7/0xb
Nov 15 00:06:54 localhost kernel: ---[ end trace f54bddefbf123cf4 ]---
Nov 15 00:08:34 localhost abrt: Kerneloops: Reported 1 kernel oopses to Abrt
Nov 15 00:08:34 localhost abrtd: Directory 'kerneloops-1289797714-1143-1' creation detected
Nov 15 00:08:35 localhost abrtd: Crash is in database already (dup of /var/spool/abrt/kerneloops-1287954753-1190-1)
Nov 15 00:08:35 localhost abrtd: Deleting crash kerneloops-1289797714-1143-1 (dup of kerneloops-1287954753-1190-1), sending dbus signal
Trying to start a basic X session (xinit) yields
X.Org X Server 1.8.2
Release Date: 2010-07-01
X Protocol Version 11, Revision 0
Build Operating System: x86-10 2.6.32-44.el6.x86_64
Current Operating System: Linux localhost.localdomain 2.6.34.7-61.fc13.i686 #1 SMP Tue Oct 19 04:42:47 UTC 2010 i686
Kernel command line: ro root=UUID=a79881e9-6359-42ae-a184-287c7d3927a7 rhgb quiet SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8 KEYTABLE=us
Build Date: 13 September 2010 07:04:27PM
Build ID: xorg-x11-server 1.8.2-4.fc13
Current version of pixman: 0.18.0
Before reporting problems, check http://bodhi.fedoraproject.org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Mon Nov 15 00:10:36 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) Microsoft Natural® Ergonomic Keyboard 4000: failed to initialize for relative axes.
(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Input/output error.
We could use more context on your logs. Could we get complete ones, please? Specifically, 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. Do you want these logs (esp. the system log, dmesg output, Xorg logs) when/immediately after this issue has occurred? yes, after crash and before reboot, if possible. Thank you Not sure this is related but with 2.6.34.7-63.fc13.x86_64 and wine-1.3.8-1.fc15.x86_64 and trying to play Myst V I get a GPU hung check at a certain point, very early, in the game. 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller]) I have Xorg.0.log, messages and an intel_gpu_dump if you are interested. I tried the kernel in rawhide 2.6.37-0.rc5.git2.1.fc15.x86_64 it was worse, I couldn't even get the game started. Have to reboot to get X to work which says to me it is in the kernel modesetting driver not X11. Created attachment 476846 [details]
output from dmesg
Created attachment 476847 [details]
/var/log/messages
edited down to most recent boot w/ crash
Created attachment 476848 [details]
/etc/x11/xorg.conf
Created attachment 476849 [details]
/var/log/Xorg.0.log
I'm experiencing identical symptoms and have supplied the requested files. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |