From: Udo Steinberg <udo@hypervisor.org>
To: <keithp@keithp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: i915 screen corruption
Date: Fri, 11 Nov 2011 23:30:18 +0100 [thread overview]
Message-ID: <20111111233018.629c864b@x220> (raw)
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
Hi,
On a Lenovo Thinkpad X220 with Gen6 (SNB) integrated graphics, I occasionally
get screen corruption under X. Every time this happens I'm seeing the
following in dmesg. This is a vanilla Linux 3.1 kernel.
Cheers,
- Udo
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/i915/i915_drv.c:387 __gen6_gt_wait_for_fifo+0x63/0x6e()
Hardware name: 4290W4H
Pid: 1671, comm: X Not tainted 3.1.0 #1
Call Trace:
[<ffffffff81036028>] ? warn_slowpath_common+0x73/0x87
[<ffffffff811efe99>] ? __gen6_gt_wait_for_fifo+0x63/0x6e
[<ffffffff81223835>] ? gen6_ring_put_irq+0x66/0xa6
[<ffffffff8120001c>] ? i915_wait_request+0x2e0/0x3b9
[<ffffffff812250ea>] ? render_ring_flush+0xa1/0xac
[<ffffffff8104bdd1>] ? abort_exclusive_wait+0x79/0x79
[<ffffffff8120014e>] ? i915_gem_flush_ring+0x24/0xdc
[<ffffffff812053f0>] ? i915_gem_do_execbuffer.clone.8+0xd7b/0x11cf
[<ffffffff81205ccf>] ? i915_gem_execbuffer2+0x12b/0x1ac
[<ffffffff811dfbb6>] ? drm_ioctl+0x251/0x306
[<ffffffff81205ba4>] ? i915_gem_execbuffer+0x360/0x360
[<ffffffff81008734>] ? init_fpu+0x10b/0x124
[<ffffffff81008b38>] ? check_for_xstate+0x1c/0x71
[<ffffffff810b1761>] ? do_vfs_ioctl+0x404/0x445
[<ffffffff81001b25>] ? sys_rt_sigreturn+0x196/0x1c5
[<ffffffff810b17de>] ? sys_ioctl+0x3c/0x5e
[<ffffffff813c1bfb>] ? system_call_fastpath+0x16/0x1b
---[ end trace 63d59cd44de45e89 ]---
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-11-11 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 22:30 Udo Steinberg [this message]
2011-11-22 14:27 ` i915 screen corruption Udo Steinberg
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=20111111233018.629c864b@x220 \
--to=udo@hypervisor.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--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