freeze with drm/i915

Wed Mar 20 05:39:24 PDT 2013

On Wed, Mar 20, 2013 at 12:34 PM, Francesco Allertsen
<fallertsen at gmail.com> wrote:
> I have experienced since few kernel releases some freezes of my PC. The
> freeze is totally random, it can happen two times in one hour or nothing
> for an entire week, and the open programs are never the same (except
> maybe for Chromium).
>
> Last week I had the time to bisect the problem to try to solve it,
> because I found that since few releases I get the following report on
> dmesg:

Yeah, that's a different issue and actually a long-standing bug in our
display code, at least on ironlake. Which seems to be your system (I
can never remember the marketing names, lspci -nn would clarify ...).
We've only recently added the more obnoxious warning for it. So not
really a regression. Also, this only tends to happen with a DP screen.

Note that on ironlake the known hard-hang is caused by enabling rc6
(disabled by default). So if you have that set, please disable it.

If that's not your hang I think we should try to capture the dying
breadths of your system with netconsole to check whether anything
interesting is in there.

Thanks, Daniel

>
> [   15.993547] ------------[ cut here ]------------
> [   15.993577] WARNING: at drivers/gpu/drm/i915/intel_display.c:1028 intel_wait_for_pipe_off+0x11b/0x126 [i915]()
> [   15.993579] Hardware name: 5129CTO
> [   15.993581] pipe_off wait timed out
> [   15.993582] Modules linked in: vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) snd_hda_codec_hdmi snd_hda_codec_conexant i915 snd_hda_intel snd_hda_codec snd_hwdep drm_kms_helper
> [   15.993593] Pid: 1566, comm: X Tainted: G           O 3.8.1 #1
> [   15.993595] Call Trace:
> [   15.993604]  [<c102b501>] warn_slowpath_common+0x68/0x7d
> [   15.993617]  [<f862bffb>] ? intel_wait_for_pipe_off+0x11b/0x126 [i915]
> [   15.993621]  [<c102b589>] warn_slowpath_fmt+0x2b/0x2f
> [   15.993635]  [<f862bffb>] intel_wait_for_pipe_off+0x11b/0x126 [i915]
> [   15.993649]  [<f862c11b>] intel_disable_pipe+0x115/0x11d [i915]
> [   15.993662]  [<f862c6ab>] ironlake_crtc_disable+0xb2/0x688 [i915]
> [   15.993677]  [<f8631e84>] intel_set_mode+0x398/0x7b0 [i915]
> [   15.993683]  [<c104c0b7>] ? should_resched+0x8/0x22
> [   15.993688]  [<c1538632>] ? _cond_resched+0xd/0x21
> [   15.993694]  [<c10f3317>] ? __getblk+0x28/0x282
> [   15.993697]  [<c10f24af>] ? __find_get_block_slow+0x11c/0x12a
> [   15.993713]  [<f863277a>] intel_crtc_set_config+0x4de/0x651 [i915]
> [   15.993718]  [<c12bcde2>] drm_mode_setcrtc+0x34b/0x39d
> [   15.993721]  [<c12bca97>] ? drm_mode_setplane+0x27a/0x27a
> [   15.993725]  [<c12b217b>] drm_ioctl+0x275/0x323
> [   15.993727]  [<c12bca97>] ? drm_mode_setplane+0x27a/0x27a
> [   15.993730]  [<c12b1f06>] ? drm_version+0x8b/0x8b
> [   15.993734]  [<c10dcc84>] vfs_ioctl+0x20/0x2a
> [   15.993736]  [<c10dd656>] do_vfs_ioctl+0x3eb/0x429
> [   15.993740]  [<c10d1598>] ? fsnotify_modify+0x48/0x53
> [   15.993743]  [<c10d122e>] ? wait_on_retry_sync_kiocb+0x44/0x44
> [   15.993745]  [<c10d18ff>] ? vfs_write+0x8a/0xac
> [   15.993748]  [<c10dd6d5>] sys_ioctl+0x41/0x60
> [   15.993751]  [<c1539274>] syscall_call+0x7/0xb
> [   15.993753] ---[ end trace fe4cfed2900ae9cb ]---
>
> Then after the bisect the following is the first commit that trigger
> this warning:
>
> 284637d9229dc1115947bb04008730844afbc059 is the first bad commit
> commit 284637d9229dc1115947bb04008730844afbc059
> Author: Daniel Vetter <daniel.vetter at ffwll.ch>
> Date:   Mon Jul 9 09:51:57 2012 +0200
>
>     drm/i915: WARN if the pipe won't turn off
>
>     This seems to be the symptom of a few neat bugs, hence be more
>     obnoxious when this fails.
>
> So, it seems that there is some other bug somewhere. If you have any
> idea or you need more tests from me I'm happy to figure it out.
>
> Currently I am using the kernel 3.8.1, but I would like to test the
> latest git soon if someone has already solved it or not. My laptop is a
> Lenovo X201s and this is my video card:
>
> 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller])
>         Subsystem: Lenovo Device 215a
>         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 44
>         Region 0: Memory at f2000000 (64-bit, non-prefetchable) [size=4M]
>         Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
>         Region 4: I/O ports at 1800 [size=8]
>         Expansion ROM at <unassigned> [disabled]
>         Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
>                 Address: fee0f00c  Data: 41d1
>         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
>
> If you need more information please just let me know.
>
> Thank you.
>
> Regards,
> Francesco

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch