Re: regression(?) 3.3-rc4 -> 3.3-rc5: drm intel hangs

From: Daniel Vetter
Date: Tue Feb 28 2012 - 03:32:43 EST


On Tue, Feb 28, 2012 at 01:03:27PM +0900, Norbert Preining wrote:
> Dear all,
>
> (please Cc)
>
> since upgrade to 3.3-rc5 I see the following behaviour repeatedly:
>
> Feb 28 11:42:47 mithrandir kernel: [15627.756071]
> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
> Feb 28 11:42:47 mithrandir kernel: [15627.756087] [drm] capturing error
> event; look for more information in /debug/dri/0/i915_error_state

Wee need this i915_error_state file from debugfs (you might need to mount
that first again) to diagnose gpu hangs. Also, it only contains
information after a crash, so you need to rehang your machine if you've
rebooted since then.

Thanks, Daniel

> Feb 28 11:42:47 mithrandir kernel: [15627.758428] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 7 at 4, next 8)
> Feb 28 11:42:47 mithrandir kernel: [15628.260094] [drm:i915_reset] *ERROR* Failed to reset chip.
>
> Is this is known issue?
>
> hardware Intel GM45 Chipset
> more dmesg parts:
> [ 0.566805] agpgart-intel 0000:00:00.0: Intel GM45 Chipset
> [ 0.566925] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
> [ 0.569079] agpgart-intel 0000:00:00.0: detected 65536K stolen memory
> [ 0.569278] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
> ...
> [ 2.032297] [drm] Initialized drm 1.1.0 20060810
> [ 2.032372] i915 0000:00:02.0: power state changed by ACPI to D0
> [ 2.032429] i915 0000:00:02.0: power state changed by ACPI to D0
> [ 2.032489] i915 0000:00:02.0: setting latency timer to 64
> [ 2.085250] i915 0000:00:02.0: irq 43 for MSI/MSI-X
> [ 2.085260] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [ 2.085318] [drm] Driver supports precise vblank timestamp query.
> [ 2.085439] [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions
> [ 2.085527] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [ 2.769842] fbcon: inteldrmfb (fb0) is primary device
> [ 2.771391] [drm] Changing LVDS panel from (+hsync, +vsync) to (-hsync, -vsync)
> [ 3.304756] Console: switching to colour frame buffer device 200x56
> [ 3.308853] fb0: inteldrmfb frame buffer device
> [ 3.308855] drm: registered panic notifier
> [ 3.329552] acpi device:01: registered as cooling_device2
> [ 3.329713] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input2
> [ 3.329766] ACPI: Video Device [OVGA] (multi-head: yes rom: no post: no)
> [ 3.329881] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
>
>
> Best wishes
>
> Norbert
> ------------------------------------------------------------------------
> Norbert Preining preining@{jaist.ac.jp, logic.at, debian.org}
> JAIST, Japan TeX Live & Debian Developer
> DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
> ------------------------------------------------------------------------
> LUPPITT (n.)
> The piece of leather which hangs off the bottom of your shoe before
> you can be bothered to get it mended.
> --- Douglas Adams, The Meaning of Liff
>
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/dri-devel
> _______________________________________________
> dri-devel mailing list
> dri-devel@xxxxxxxxxxxxxxxxxxxxx
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

--
Daniel Vetter
Mail: daniel@xxxxxxxx
Mobile: +41 (0)79 365 57 48
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/