From: Norbert Preining <preining@logic.at>
To: linux-kernel@vger.kernel.org
Cc: dri-devel@lists.sourceforge.net
Subject: regression(?) 3.3-rc4 -> 3.3-rc5: drm intel hangs
Date: Tue, 28 Feb 2012 13:03:27 +0900 [thread overview]
Message-ID: <20120228040327.GA9973@gamma.logic.tuwien.ac.at> (raw)
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
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
next reply other threads:[~2012-02-28 4:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 4:03 Norbert Preining [this message]
2012-02-28 8:14 ` regression(?) 3.3-rc4 -> 3.3-rc5: drm intel hangs Paul Menzel
2012-03-01 7:42 ` Norbert Preining
2012-02-28 8:18 ` Dave Airlie
2012-02-28 8:32 ` Daniel Vetter
2012-03-09 8:07 ` Norbert Preining
2012-03-30 1:20 ` Norbert Preining
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120228040327.GA9973@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=dri-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).