From: Tino Keitel <tino.keitel+xorg@tikei.de>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Character corruption with 2.6.37
Date: Wed, 19 Jan 2011 14:24:12 +0100 [thread overview]
Message-ID: <20110119132412.GA1923@mac.home> (raw)
In-Reply-To: <20110119085700.GA18294@mac.home>
On Wed, Jan 19, 2011 at 09:57:00 +0100, Tino Keitel wrote:
> Hi,
>
> I see character corruption in X with 2.6.37, libdrm 2.4.21 and 2.4.23,
> intel-xorg 2.13 and Xserver 1.7.7 (Debian Sid). In the kernel, I see
> such log entries:
>
> [drm:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer
>
> Xorg.0.log looks like this:
>
> (WW) intel(0): intel_uxa_prepare_access: bo map failed: Invalid argument
> (EE) intel(0): Failed to submit batch buffer, expect rendering
> corruption or even a frozen display: Invalid argument.
>
> This happens on a Mac mini Core Duo with i945 graphics.
Addition: I not only saw character corruption. Web browsers (tried
Firefox and Midori (webkit-based) show rendering errors at some point,
up to a completely garbled tab window.
Regards,
Tino
next prev parent reply other threads:[~2011-01-19 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 8:57 Character corruption with 2.6.37 Tino Keitel
2011-01-19 13:24 ` Tino Keitel [this message]
2011-01-22 17:55 ` Niccolò Belli
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=20110119132412.GA1923@mac.home \
--to=tino.keitel+xorg@tikei.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox