Bug 91661 - drm/i915 gpu stuck on render ring
Summary: drm/i915 gpu stuck on render ring
Status: CLOSED WONTFIX
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-17 01:19 UTC by aayla.secura.1138
Modified: 2017-03-04 05:45 UTC (History)
1 user (show)

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


Attachments
dmesg-4.1.5 (49.46 KB, text/plain)
2015-08-17 01:19 UTC, aayla.secura.1138
no flags Details
/sys/class/drm/card0/error (56 bytes, text/plain)
2015-08-17 01:26 UTC, aayla.secura.1138
no flags Details
dmesg-4.0.5 intel_iommu=ifgx_off (48.31 KB, text/plain)
2015-08-18 01:13 UTC, aayla.secura.1138
no flags Details
dmesg-4.1.5 intel_iommu=ifgx_off (47.63 KB, text/plain)
2015-08-18 01:14 UTC, aayla.secura.1138
no flags Details
Xorg.log.0-4.0.5 intel_iommu=ifgx_off (33.79 KB, text/plain)
2015-08-18 01:14 UTC, aayla.secura.1138
no flags Details
Xorg.log.0-4.1.5 intel_iommu=ifgx_off (28.04 KB, text/plain)
2015-08-18 01:14 UTC, aayla.secura.1138
no flags Details

Description aayla.secura.1138 2015-08-17 01:19:28 UTC
Created attachment 117723 [details]
dmesg-4.1.5

All is fine with version 4.0.5, upgrading to 4.1.5 gives reproducible gpu crash. It crashes immediately as the driver is loaded. I'm attaching the full dmesg output, the relevant part is at the end. I'll also attach /sys/class/drm/card0/error. Here's lspci's output for the graphics in case it's relevant:

00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Apple Inc. Broadwell-U Integrated Graphics
	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 c0000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 3000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee0f00c  Data: 4162
	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
	Kernel modules: i915
Comment 1 aayla.secura.1138 2015-08-17 01:26:52 UTC
Created attachment 117724 [details]
/sys/class/drm/card0/error
Comment 2 Chris Wilson 2015-08-17 09:58:17 UTC
Looks like an iommu related issue. Could you please try booting with intel_iommu=igfx_off?
Comment 3 aayla.secura.1138 2015-08-18 01:12:51 UTC
Hi and thanks for replying! I tried that and the errors were completely gone but my external monitor was not detected (properly). Meaning, on the virtual console the resolution for it was very low and when I start X it is not detected at all. I'm attaching dmesg and Xorg.log.0 from both 4.0.5 and 4.1.5. diffing them doesn't reveal any problem (apart from the fact that EDID for output DP2 which is the external monitor doesn't discover anything in 4.1.5's Xorg.log. I'm not sure if this problem is related to this bug at all, if you feel like it's not, please close the bug.
Comment 4 aayla.secura.1138 2015-08-18 01:13:46 UTC
Created attachment 117745 [details]
dmesg-4.0.5 intel_iommu=ifgx_off
Comment 5 aayla.secura.1138 2015-08-18 01:14:08 UTC
Created attachment 117746 [details]
dmesg-4.1.5 intel_iommu=ifgx_off
Comment 6 aayla.secura.1138 2015-08-18 01:14:38 UTC
Created attachment 117747 [details]
Xorg.log.0-4.0.5  intel_iommu=ifgx_off
Comment 7 aayla.secura.1138 2015-08-18 01:14:56 UTC
Created attachment 117748 [details]
Xorg.log.0-4.1.5  intel_iommu=ifgx_off
Comment 8 yann 2017-02-24 08:17:13 UTC
We seem to have neglected the bug a bit, apologies.

Aayla Secura, since There were improvements pushed in kernel that will benefit to your system, so please re-test with latest kernel and mark as REOPENED if you can reproduce (and attach fresh gpu error dump & kernel log) and RESOLVED/* if you cannot reproduce.
Comment 9 yann 2017-03-03 16:47:51 UTC
(In reply to yann from comment #8)
> We seem to have neglected the bug a bit, apologies.
> 
> Aayla Secura, since There were improvements pushed in kernel that will
> benefit to your system, so please re-test with latest kernel and mark as
> REOPENED if you can reproduce (and attach fresh gpu error dump & kernel log)
> and RESOLVED/* if you cannot reproduce.

Timeout. Assuming that this is not occurring anymore. If this issue happens again, re-test with latest kernel and REOPEN if you can reproduce (and attach fresh gpu error dump & kernel log)
Comment 10 aayla.secura.1138 2017-03-04 05:45:48 UTC
Many apologies, the previous post got past me. I tested it today with 4.8.4 and cannot reproduce the crash. Can't say anything about the external monitor issue as I have no access to a monitor at the moment.


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.