From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <waldi@debian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: pvops: i915 kms crashs with corrupt page table
Date: Fri, 26 Feb 2010 17:17:36 -0800 [thread overview]
Message-ID: <4B8872B0.2040807@goop.org> (raw)
In-Reply-To: <20100227004518.GA491@wavehammer.waldi.eu.org>
On 02/26/2010 04:45 PM, Bastian Blank wrote:
> The trap happened while userspace code was running, Xorg in this case.
>
The changes in xen/next should help with this.
J
next prev parent reply other threads:[~2010-02-27 1:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 17:55 pvops: i915 kms crashs with corrupt page table Bastian Blank
2010-02-24 19:23 ` Jeremy Fitzhardinge
2010-02-25 10:06 ` Bastian Blank
2010-02-25 10:32 ` Bastian Blank
2010-02-26 0:37 ` Jeremy Fitzhardinge
2010-02-26 12:44 ` Bastian Blank
2010-02-26 17:29 ` Jeremy Fitzhardinge
[not found] ` <20100226180545.GC21871@wavehammer.waldi.eu.org>
[not found] ` <4B880EC0.8000803@goop.org>
2010-02-27 0:45 ` Bastian Blank
2010-02-27 1:17 ` Jeremy Fitzhardinge [this message]
2010-02-28 12:27 ` Bastian Blank
2010-03-01 8:43 ` Ian Campbell
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=4B8872B0.2040807@goop.org \
--to=jeremy@goop.org \
--cc=waldi@debian.org \
--cc=xen-devel@lists.xensource.com \
/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).