All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastian Blank <waldi@debian.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: pvops: i915 kms crashs with corrupt page table
Date: Sat, 27 Feb 2010 01:45:18 +0100	[thread overview]
Message-ID: <20100227004518.GA491@wavehammer.waldi.eu.org> (raw)
In-Reply-To: <4B880EC0.8000803@goop.org>

On Fri, Feb 26, 2010 at 10:11:12AM -0800, Jeremy Fitzhardinge wrote:
> Yes.  Why is there no debug info?  Have you disabled frame pointers and  
> symbols?  What does 00007ffff3c5d0a0  correspond to?  Are there any  
> messages on the Xen console?

Please take a look at the memory layout of x86-64 linux, the lower half
of the memory is userspace.

The trap happened while userspace code was running, Xorg in this case.

Bastian

-- 
Respect is a rational process
		-- McCoy, "The Galileo Seven", stardate 2822.3

  parent reply	other threads:[~2010-02-27  0:45 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 [this message]
2010-02-27  1:17                   ` Jeremy Fitzhardinge
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=20100227004518.GA491@wavehammer.waldi.eu.org \
    --to=waldi@debian.org \
    --cc=jeremy@goop.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 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.