| Summary: | [IVB] GPU hang after resume | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Marcin Slusarz <marcin.slusarz> |
| Component: | Drivers/DRI/i965 | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | bblanco, intel-gfx-bugs, stu.axon |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | IVB | i915 features: | GPU hang |
| Attachments: |
/sys/class/drm/card0/error
full dmesg dmesg 4.4-rc6 gpu crash dump |
||
|
Description
Marcin Slusarz
2015-12-15 19:34:09 UTC
Created attachment 120532 [details]
/sys/class/drm/card0/error
Created attachment 120533 [details]
full dmesg
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0578 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 30 Region 0: Memory at f1000000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 4000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0100c Data: 4122 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 I'm on 4.4-rc6 and the hangs occur at least once a day, even without suspend & resume cycle. 2 or 3 times I also lost mouse cursor (X restart restores it). Do you need any information? Created attachment 120725 [details]
dmesg 4.4-rc6
I started seeing this ~4.4rc7 (might have been on rc6 but i don't think so... for sure it was there in rc8). I am on kubuntu 15.10 on Intel i5-3317U, using ubuntu kernel-mainline 4.4 Its not clear that suspend/resume is involved. It will happen while using it w/o a resume, but may happen on each resume too(?) its relatively frequent, ~1-2 times / hr. $ uname -a Linux don-s9 4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux don@don-s9:~$ dmesg |grep -i drm [ 1.719271] [drm] Initialized drm 1.1.0 20060810 [ 1.760871] [drm] Memory usable by graphics device = 2048M [ 1.760875] [drm] Replacing VGA console driver [ 1.767520] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 1.767523] [drm] Driver supports precise vblank timestamp query. [ 1.791601] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0 [ 1.930190] fbcon: inteldrmfb (fb0) is primary device [ 3.441414] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [30372.607262] [drm] stuck on render ring [30372.607938] [drm] GPU HANG: ecode 7:0:0x85ffbff8, in chrome [2873], reason: Ring hung, action: reset [30372.607940] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [30372.607941] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [30372.607942] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [30372.607943] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [30372.607944] [drm] GPU crash dump saved to /sys/class/drm/card0/error [30372.608009] WARNING: CPU: 0 PID: 11390 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:11289 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() [30372.608059] snd_seq media iwlwifi x86_pkg_temp_thermal intel_powerclamp btrtl btbcm coretemp snd_seq_device snd_timer btintel joydev bluetooth input_leds serio_raw mei_me cfg80211 snd mei soundcore shpchp lpc_ich acpi_als kfifo_buf industrialio kvm_intel kvm mac_hid irqbypass arc4 ppp_mppe parport_pc ppdev lp parport autofs4 btrfs drbg ansi_cprng algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper i2c_algo_bit cryptd drm_kms_helper syscopyarea psmouse sysfillrect sysimgblt fb_sys_fops ahci drm libahci r8169 mii wmi fjes video [30372.610069] drm/i915: Resetting chip after gpu hang Created attachment 120986 [details]
gpu crash dump
gpu error dump
*** Bug 92862 has been marked as a duplicate of this bug. *** There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring. In the meantime, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang). From this error dump, hung is happening in render ring batch with active head at 0x7899c19c, with 0x7a000003 (PIPE_CONTROL) as IPEHR. Kernel: 4.4.0-rc4 Platform: IvyBridge (pci id: 0x0166) Mesa: [Please confirm your mesa version] Batch extract (around 0x7899c19c): 0x7899c16c: 0x780f0000: 3DSTATE_SCISSOR_POINTERS 0x7899c170: 0x00007d80: scissor rect offset 0x7899c174: 0x7a000003: PIPE_CONTROL 0x7899c178: 0x00002000: no write, depth stall, 0x7899c17c: 0x00000000: destination address 0x7899c180: 0x00000000: immediate dword low 0x7899c184: 0x00000000: immediate dword high 0x7899c188: 0x7a000003: PIPE_CONTROL 0x7899c18c: 0x00100001: no write, cs stall, depth cache flush, 0x7899c190: 0x00000000: destination address 0x7899c194: 0x00000000: immediate dword low 0x7899c198: 0x00000000: immediate dword high 0x7899c19c: 0x7a000003: PIPE_CONTROL 0x7899c1a0: 0x00002000: no write, depth stall, 0x7899c1a4: 0x00000000: destination address 0x7899c1a8: 0x00000000: immediate dword low 0x7899c1ac: 0x00000000: immediate dword high 0x7899c1b0: 0x78050005: 3DSTATE_DEPTH_BUFFER 0x7899c1b4: 0x204c17ff: dword 1 0x7899c1b8: 0x77b24000: dword 2 0x7899c1bc: 0x0dac5fe0: dword 3 0x7899c1c0: 0x00000001: dword 4 0x7899c1c4: 0x00000000: dword 5 0x7899c1c8: 0x00000000: dword 6 I can't re-test it, because I got rid of this laptop. (In reply to Marcin Slusarz from comment #11) > I can't re-test it, because I got rid of this laptop. thanks Marcin for your feedback. So let's mesa team decide how they want to proceed here :) (In reply to Marcin Slusarz from comment #11) > I can't re-test it, because I got rid of this laptop. Okay. Not much we can do. |
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.