All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Rolu <rolu@roce.org>
Cc: xen-devel@lists.xensource.com, Paul S <pstroud@gmail.com>
Subject: Re: 4.2-Unstable Crash/Reboot(i5 2500/DQ67SW)
Date: Thu, 21 Jun 2012 10:34:58 -0400	[thread overview]
Message-ID: <20120621143458.GC23530@phenom.dumpdata.com> (raw)
In-Reply-To: <CABs9Ej=TpBUyLaPB0FMmL+oZUeZtJTjTAb=gX3nOJY9p5k5yiw@mail.gmail.com>

On Thu, Jun 21, 2012 at 01:25:24AM +0200, Rolu wrote:
> On Thu, Jun 21, 2012 at 12:16 AM, Paul S <pstroud@gmail.com> wrote:
> > Environment: Xen-4.2 Unstable - built about a week ago
> >              OS: Fedora 17
> >            CPU: i5 2500
> > Motherboard: DQ67SW latest bios
> >
> > Trying to get passthrough working, 4.1.2 Bluescreens going into windows,
> > figured I probably needed some of the patches in 4.2, built it and it just
> > crashes and reboots. Installed a Serial card, got the terminal working and
> > was able to capture the crash. I have also included the dmidecode CPU and
> > BIOS from the normal Fedora 17 kernel(non-xen).
> >
> 
> The crash you get with 4.2 looks like the issue I had recently, see
> http://lists.xen.org/archives/html/xen-devel/2012-06/msg00998.html
> 
> Add xsave=0 to the Xen kernel line in grub, or use a newer dom0 kernel.

Well, to be fair - he is using a new kernel. It is just that Fedora
adds a patch that half-way disables xsave.

      reply	other threads:[~2012-06-21 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 22:16 4.2-Unstable Crash/Reboot(i5 2500/DQ67SW) Paul S
2012-06-20 23:25 ` Rolu
2012-06-21 14:34   ` Konrad Rzeszutek Wilk [this message]

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=20120621143458.GC23530@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=pstroud@gmail.com \
    --cc=rolu@roce.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.