From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: dom0/xen boot problem
Date: Wed, 2 Mar 2011 16:25:18 -0500 [thread overview]
Message-ID: <20110302212518.GA21863@dumpdata.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D53019D874750@orsmsx505.amr.corp.intel.com>
On Fri, Feb 25, 2011 at 11:22:24AM -0800, Kay, Allen M wrote:
> Jeremy/Konrad,
>
> Thanks for Stefano's help, dom0/xen boot failure on my Sandybridge desktop SDP has been isolated to the following patch that is missing in both 2.6.32 and 2.6.37 PVOPS branches. According to PVOPS wiki 2.6.32 and 2.6.37 are suppose to be active branches. Can you back port this patch to both 2.6.32 and 2.6.37 branches?
So incidententaly.. Are you also using Xorg with the 2.6.37 (or 2.6.38?) on your Sandybridge SDP box? If so
what version of Xorg, libdrm, and libav?
I am curious whether you see this:
17.468595] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
[ 17.471533] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 3 at 0, next 4)
[ 17.998586] [drm:i915_reset] *ERROR* Failed to reset chip.
next prev parent reply other threads:[~2011-03-02 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <987664A83D2D224EAE907B061CE93D53019D7AD813@orsmsx505.amr.corp.intel.com>
[not found] ` <alpine.DEB.2.00.1102251147500.2156@kaball-desktop>
2011-02-25 19:22 ` dom0/xen boot problem Kay, Allen M
2011-02-25 19:36 ` Konrad Rzeszutek Wilk
2011-02-25 19:54 ` Kay, Allen M
2011-02-25 21:20 ` Konrad Rzeszutek Wilk
2011-03-02 21:25 ` Konrad Rzeszutek Wilk [this message]
2011-03-02 22:07 ` Kay, Allen M
2011-03-02 22:52 ` Konrad Rzeszutek Wilk
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=20110302212518.GA21863@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=allen.m.kay@intel.com \
--cc=jeremy@goop.org \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--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.