Bug 102140 - [G4X] Latitude E5400 GPU crash
Summary: [G4X] Latitude E5400 GPU crash
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-10 16:36 UTC by walter
Modified: 2018-02-13 16:37 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features: GPU hang


Attachments
dump saved to /sys/class/drm/card0/error (736.60 KB, text/plain)
2017-08-10 16:36 UTC, walter
no flags Details

Description walter 2017-08-10 16:36:44 UTC
Created attachment 133426 [details]
dump saved to /sys/class/drm/card0/error

[16400.805170] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[16400.805171] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[16400.805172] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[16400.805172] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[16400.805173] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[16400.805221] drm/i915: Resetting chip after gpu hang

Linux 4.4.76-1-default
NAME="openSUSE Leap"
VERSION="42.3"
08: PCI 02.0: 0300 VGA compatible controller (VGA)              
  [Created at pci.378]
  Unique ID: _Znp.SC10w_jNeU9
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x2a42 "Mobile 4 Series Chipset Integrated Graphics Controller"
  SubVendor: pci 0x1028 "Dell"
  SubDevice: pci 0x0262 
  Revision: 0x07
  Driver: "i915"
  Driver Modules: "i915"
  Memory Range: 0xf6c00000-0xf6ffffff (rw,non-prefetchable)
  Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
  I/O Ports: 0xefe8-0xefef (rw)
  IRQ: 27 (1645 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00002A42sv00001028sd00000262bc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
Comment 1 Chris Wilson 2017-08-10 16:57:59 UTC
Active (render ring) [6]:
    00000000_7edec000     4096 7e 00 [ 2a70 00 00 00 00 ] 00 dirty uncached
    00000000_7edd7000    86016 37 00 [ 2a70 00 00 00 00 ] 00 dirty uncached
    00000000_001cf000   286720 76 00 [ 2a70 00 00 00 00 ] 00 X dirty uncached (fence: 3)
    00000000_00838000  5554176 02 00 [ 2a71 00 00 00 00 ] 2a71 X dirty render uncached (name: 3) (fence: 0)
    00000000_7eded000  5554176 36 00 [ 2a71 00 00 00 00 ] 2a70 X dirty render uncached
    00000000_7edd3000    16384 3f 00 [ 2a71 00 00 00 00 ] 00 dirty uncached
batch (render ring (submitted by X [1588])) at 0x00000000_7edec000
0x7edec000:      0x69040000: 3DSTATE_PIPELINE_SELECT
0x7edec004:      0x61010004: STATE_BASE_ADDRESS
0x7edec008:      0x01eff001:    general state base address 0x01eff000
0x7edec00c:      0x7edad001:    surface state base address 0x7edad000
0x7edec010:      0x00000000:    indirect state base not updated
0x7edec014:      0x00000001:    general state upper bound disabled
0x7edec018:      0x00000000:    indirect state upper bound not updated


The oddity here is that the general state buffer is not listed as part of the GTT. Missed relocation?

I cannot stress enough the importance of checking with 4.12 as we fixed quite a few bugs that may be related.
Comment 2 walter 2017-08-10 17:04:42 UTC
Give me some time i will retry with 4.12 tomorrow
Comment 3 walter 2017-08-11 17:23:45 UTC
no obvoius problems with (pulled rpm from suse).
Linux version 4.12.5-2.g4d38c27-vanilla 

cat /sys/class/drm/card0/error
No error state collected
Comment 4 Jari Tahvanainen 2017-08-18 12:38:48 UTC
Verified by Reporter. See previous comment.
Comment 5 Elizabeth 2018-02-13 16:37:45 UTC
Closing old verified.


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.