Bug 96507 - [I845G] GPU HANG: ecode 2:0:0x7dfbef03, in Xorg [1378], reason: Ring hung, action: reset
Summary: [I845G] GPU HANG: ecode 2:0:0x7dfbef03, in Xorg [1378], reason: Ring hung, ac...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i915 (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-13 12:10 UTC by SJ
Modified: 2019-09-18 19:39 UTC (History)
3 users (show)

See Also:
i915 platform: I845G
i915 features: GPU hang


Attachments
As described (299.69 KB, application/gzip)
2016-06-13 12:10 UTC, SJ
Details

Description SJ 2016-06-13 12:10:31 UTC
Created attachment 124500 [details]
As described

Hi,

I did a fresh install of Centos 7 (i686) on an old Dell Dimension 2400. The install itslef was successful and after the first reboot, it goes into Gnome Desktop where it asks me to do initial settings such as select keyboard layout, select cloud services etc.

After this point, GDM gives me the "Oh no! Something has gone wrong." error.

On reboot, I get the standard GDM login in which I login as any user, but gives the same error after login. Oddly, the error dissapears and then I am left with a white screen with just one line in the middle showing in black "Welcome" in different languages, but nothing else.

The OS: 
[root@knightshade ~]# uname -a
Linux knightshade 3.10.0-327.18.2.el7.i686 #1 SMP Fri May 13 02:29:38 UTC 2016 i686 i686 i386 GNU/Linux

Updates: Yum Update ran on Thu 09 June 2016 - so all updates installed up to this point. Same issue occured before I did the update.

The Hardware:
[root@knightshade ~]# lspci
00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
00:1d.0 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
01:06.0 Communication controller: LSI Corporation F-1156IV WinModem (V90, 56KFlex) (rev 01)
01:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)

Var Log Messages:
un  9 17:04:30 knightshade abrt-hook-ccpp: Not saving repeating crash in '/usr/bin/gnome-shell'
Jun  9 17:04:30 knightshade gnome-session: gnome-session[2814]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 5
Jun  9 17:04:30 knightshade gnome-session[2814]: WARNING: Application 'gnome-shell-classic.desktop' killed by signal 5
Jun  9 17:04:30 knightshade gnome-session[2814]: WARNING: App 'gnome-shell-classic.desktop' respawning too quickly
Jun  9 17:04:30 knightshade gnome-session: Unrecoverable failure in required component gnome-shell-classic.desktop
Jun  9 17:04:30 knightshade gnome-session: gnome-session[2814]: WARNING: App 'gnome-shell-classic.desktop' respawning too quickly
Jun  9 17:04:31 knightshade gnome-session: (gnome-settings-daemon:3000): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Jun  9 17:04:32 knightshade gnome-session: Entering running state
Jun  9 17:04:33 knightshade abrt-server: Generating core_backtrace
Jun  9 17:04:33 knightshade gnome-session: Initializing nautilus-open-terminal extension
Jun  9 17:04:33 knightshade gnome-session: (uint32 1,)
Jun  9 17:04:37 knightshade kernel: [drm] stuck on render ring
Jun  9 17:04:37 knightshade kernel: [drm] GPU HANG: ecode 2:0:0x7dfbef03, in Xorg [1378], reason: Ring hung, action: reset
Jun  9 17:04:37 knightshade kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jun  9 17:04:37 knightshade kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jun  9 17:04:37 knightshade kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jun  9 17:04:37 knightshade kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jun  9 17:04:37 knightshade kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jun  9 17:04:37 knightshade kernel: drm/i915: Resetting chip after gpu hang
Jun  9 17:04:37 knightshade kernel: [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -19
Jun  9 17:04:37 knightshade gnome-session: (nautilus:3066): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 34
Jun  9 17:04:38 knightshade gnome-session: Failed to play sound: File or data not found
Jun  9 17:04:38 knightshade gnome-keyring-daemon[3273]: another secret service is running

XOrg Log:
    87.665] AUDIT: Thu Jun  9 17:04:31 2016: 1378: client 8 connected from local host ( uid=0 gid=0 pid=3066 )
  Auth name: MIT-MAGIC-COOKIE-1 ID: 121
[    93.726] (EE) intel(0): Detected a hung GPU, disabling acceleration.
[    93.732] (EE) intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg.

Centos 6.x worked fine on this box.

Tried:
1) Restarting GDM as Root in another console.
2) Reinstall again.

Attached:
1) File /var/log/messages
2) File /var/log/Xorg.0.log
3) File /sys/class/drm/card0/error
4) File dmesgout.txt - Output of dmesg.
5) File abrtout.txt - Output of abrt-cli list

I filed a bug as requested in the above messages. Could help me with the next steps please?
Comment 1 SJ 2016-06-13 12:52:48 UTC
Just to add: 
1) I have two local users on this box. Root and a user called "localuser" - both fails with the same error.

2) Tried "Gnome", "Gnome Classic" and "Custom" - all with the same error.
Comment 2 yann 2016-09-01 12:31:11 UTC
We can note that you have some issue with your current system, especially with DBus and Gnome that may require you to reinstall or updgrade your system:

Jun  9 17:04:28 knightshade gnome-session: (gnome-shell:3032): Cogl-ERROR **: Failed to create texture 2d due to size/format constraints
Jun  9 17:04:29 knightshade gnome-session: (gnome-settings-daemon:3000): media-keys-plugin-WARNING **: 4: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)


Regarding this GPU Hang, assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head
at 0x00000130, with 0x7d0410c2 (3DSTATE_LOAD_STATE_IMMEDIATE_1) as IPEHR.

Batch extract (around 0x00000130):

0x000000f4:      0x7f1c000b: 3DPRIMITIVE inline RECTLIST
unknown vertex format
0x000000f8:      0x42ec0000:               vertex data (118.000000 float)
0x000000fc:      0x42680000:               vertex data (58.000000 float)
0x00000100:      0x3f800000:               vertex data (1.000000 float)
0x00000104:      0x3f800000:               vertex data (1.000000 float)
0x00000108:      0x44148000:               vertex data (594.000000 float)
0x0000010c:      0x44200000:               vertex data (640.000000 float)
0x00000110:      0x3f800000:               vertex data (1.000000 float)
0x00000114:      0x3f800000:               vertex data (1.000000 float)
0x00000118:      0x44148000:               vertex data (594.000000 float)
0x0000011c:      0x44180000:               vertex data (608.000000 float)
0x00000120:      0x00000000:               vertex data (0.000000 float)
0x00000124:      0x00000000:               vertex data (0.000000 float)
0x00000128:      0x7d0410c2: 3DSTATE_LOAD_STATE_IMMEDIATE_1
0x0000012c:      0x00000000:    S2: 0x00000000
0x00000130:      0x000024c0:    S3: 0x000024c0
0x00000134:      0x00008264:    S8: 0x00008264
0x00000138:      0x7d030081: 3DSTATE_LOAD_STATE_IMMEDIATE_2
0x0000013c:      0x860048c0:    TB0C
0x00000140:      0x060040c0:    TB0A
Comment 3 SJ 2016-10-28 19:00:21 UTC
This was a fresh install, the entire system was wiped twice. I have at the moment downgraded to Centos 6.8 and it appears to work fine.
Comment 4 yann 2016-11-04 15:05:42 UTC
Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 5 GitLab Migration User 2019-09-18 19:39:28 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/763.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.