Bug#811352: linux 4.4-rc8: i915: "[drm] stuck on render ring" on resume

2016-01-18 Thread Julian Andres Klode
Package: src:linux
Version: 4.4~rc8-1~exp1
Severity: normal

I'm not sure if that's the right package to report this bug, it could
also be mesa, the X11 driver, or maybe even gnome-shell. Anyway, I don't
think I have seen this with 4.3:

Often, when resuming the GPU hangs, and gnome-shell thus exits and then
restarts, delaying usable resume by about 13 seconds.

I'm running xserver-xorg-video-intel 2.99.917+git20151217-1~exp1 from
experimental (as unstable has a few bugs fixed in there), and libdrm
2.4.65-3. Neither have been upgraded recently, so it is
likely the kernel causing the issue, as this is a very recent
problem.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: LENOVO
product_name: 2325CN3
product_version: ThinkPad X230
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: G2ETA5WW (2.65 )
board_vendor: LENOVO
board_name: 2325CN3
board_version: Not Defined

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Lenovo 3rd Gen Core processor DRAM Controller [17aa:21fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Lenovo 7 Series/C210 Series Chipset Family USB xHCI Host 
Controller [17aa:21fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Lenovo 7 Series/C210 Series Chipset Family MEI Controller 
[17aa:21fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
Connection [8086:1502] (rev 04)
Subsystem: Lenovo 82579LM Gigabit Network Connection [17aa:21f3]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI])
Subsystem: Lenovo 7 Series/C210 Series Chipset Family USB Enhanced Host 
Controller [17aa:21fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset 
Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Lenovo 7 Series/C210 Series Chipset Family High Definition 
Audio Controller [17aa:21fa]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset 
Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation 7 

Bug#811352: linux 4.4-rc8: i915: "[drm] stuck on render ring" on resume

2016-01-18 Thread Julian Andres Klode
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=92998
Control: tag -1 upstream

On Mon, Jan 18, 2016 at 09:21:50AM +0100, Julian Andres Klode wrote:
> Package: src:linux
> Version: 4.4~rc8-1~exp1
> Severity: normal
> 
> I'm not sure if that's the right package to report this bug, it could
> also be mesa, the X11 driver, or maybe even gnome-shell. Anyway, I don't
> think I have seen this with 4.3:
> 
> Often, when resuming the GPU hangs, and gnome-shell thus exits and then
> restarts, delaying usable resume by about 13 seconds.
> 
> I'm running xserver-xorg-video-intel 2.99.917+git20151217-1~exp1 from
> experimental (as unstable has a few bugs fixed in there), and libdrm
> 2.4.65-3. Neither have been upgraded recently, so it is
> likely the kernel causing the issue, as this is a very recent
> problem.

This seems to be https://bugs.freedesktop.org/show_bug.cgi?id=92998,
which is caused by commit 101b506a7fc7be3f0d0a337ade270eb5eb5a2857:

  drm/i915: Wa32bitGeneralStateOffset & Wa32bitInstructionBaseOffset

at least according to some comments in the bug report.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.