From: "Dieter Mummenschanz" <mummenschanz@gmx.net>
To: intel-gfx@lists.freedesktop.org
Subject: frequent x crashes with gen6/sna
Date: Thu, 13 Oct 2011 15:45:22 +0200 [thread overview]
Message-ID: <20111013134522.274480@gmx.net> (raw)
hello,
using latest drm-core-next git from Dave Airlie as well as the latest xf86-video-intel git my system (Sandybridge Mobile (GT2+)) still hangs frequently right before X dies. This happens every time the GPU is under considerable stress, like decoding a va-api stream and running OpenGL apps at the same time.
syslog records the hang:
kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
kernel: [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
kernel: [drm:i915_wait_request] *ERROR* i915_wait_request returns -11 (awaiting 3263296 at 3263293, next 3263297)
after 3-4 seconds the system resumes normal following the X crash a couple of minutes later:
kernel: [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
kernel: [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
gpu related module opts are:
i915.i915_enable_rc6=1 pcie_aspm=force i915.i915_enable_fbc=1 i915.lvds_downclock=1
at least rc6 enabled is mandatory for me since I ran a mobile gpu.
any ideas?
regards
Dieter
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
next reply other threads:[~2011-10-13 13:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 13:45 Dieter Mummenschanz [this message]
2011-10-13 14:00 ` frequent x crashes with gen6/sna Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2011-10-13 14:55 Dieter Mummenschanz
2011-10-13 16:24 ` Daniel Vetter
2011-10-13 16:36 Nicolas Kalkhof
2011-10-13 17:00 Dieter Mummenschanz
2011-10-14 12:52 Dieter Mummenschanz
2011-10-14 16:01 ` Daniel Vetter
2011-10-14 16:03 ` Daniel Vetter
2011-10-14 19:27 ` Dieter Mummenschanz
2011-10-14 20:00 ` Daniel Vetter
2011-10-16 9:22 Dieter Mummenschanz
2011-10-16 16:18 ` Daniel Vetter
2011-10-16 17:06 ` Daniel Vetter
2011-10-17 11:45 ` Dieter Mummenschanz
2011-10-17 11:58 ` Daniel Vetter
2011-10-17 11:59 ` Daniel Vetter
2011-10-17 12:37 Dieter Mummenschanz
2011-10-17 13:16 ` [Intel-gfx] " Daniel Vetter
2011-10-17 13:54 ` Dieter Mummenschanz
2011-10-17 14:50 ` [Intel-gfx] " Daniel Vetter
2011-10-17 15:13 ` Dieter Mummenschanz
2011-10-17 15:48 ` Daniel Vetter
2011-10-17 16:01 ` Dieter Mummenschanz
2011-10-17 20:20 Dieter Mummenschanz
2011-10-17 20:46 ` [Intel-gfx] " Daniel Vetter
2011-10-18 7:52 ` Dieter Mummenschanz
2011-10-18 18:47 ` Daniel Vetter
2011-10-24 7:22 ` Daniel Vetter
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=20111013134522.274480@gmx.net \
--to=mummenschanz@gmx.net \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.