Followup:
This also affected Chromium; which was not just updated and worked before.
After a reboot, the given page works again in Chromium.
So the Backtrace may be triggered by a separate cause:
[ 7207.128086] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
elapsed... GPU hung
[
Package: xserver-xorg-video-intel
Version: 2:2.13.0-1
Severity: normal
Hi,
Today, Google Chrome started frequently killing Xorg altogether with a
segfault. Apparently, intel DRM is to blame.
Note that I'm running tons of stuff from experimental, so this might not yet
affect the next release.
Erich Schubert er...@debian.org (06/11/2010):
But obviously, not misbehaving application should ever be able to
trigger a segmentation fault in the X11 server, right?
Correct.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Hi,
another followup: I went to a YouTube video in HTML5 mode with latest dev
Google Chrome:
[18075.056020] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer
elapsed... GPU hung
[18075.057702] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request
returns -5 (awaiting 682206 at 682205)
Erich Schubert er...@debian.org (06/11/2010):
The 2.6.37-rc1 changelog has lot sof i915 related changes that
indicate the 2.6.36 kernel might have some issues.
You may want to check what happens since graphics stuff landed in the
kernel. There are always *lots* of issues. Hence the continuous
5 matches
Mail list logo
