From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Steve Freitas <sflist@ihonk.com>
Cc: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
Subject: Re: Regression, host crash with 4.5rc1
Date: Tue, 4 Nov 2014 10:20:12 +0200 [thread overview]
Message-ID: <20141104082012.GY12451@reaktio.net> (raw)
In-Reply-To: <5457F79B.2020300@ihonk.com>
On Mon, Nov 03, 2014 at 01:46:03PM -0800, Steve Freitas wrote:
> Hi all,
>
Hello,
> I've got a Windows 7 x64 VM that is stable on 4.4.1 but crashes the
> host after a few hours on 4.5rc1. The machine is a ThinkStation D20,
> an X5660 with 5500-series chipset with an Nvidia Quadro FX4800
> (genuine) passed through. Distro is Debian Jessie running stock
> distro kernel and seabios. Both 4.4.1 and 4.5rc1 were built from
> source. Apologies if this issue has already been spotted but I can't
> keep up with the traffic on this list! :-)
>
> It looks as if something is stepping on PCI devices when the crash
> happens. In the log included below, it's the SATA system that's
> complaining but I've seen it hit the ethernet chip first, then SATA
> after that. I'm happy to troubleshoot, apply patches, give more
> information, etc.
>
> I've seen the crash when running Windows Update, when running the
> Unigine graphics benchmark, when running an Avast anti-virus scan.
> Haven't found a common thread.
>
> Don, one curious thing I noted which may be of no value whatsoever:
> Under 4.4.1, I can't give the VM > 3.5 gigs of RAM without breaking
> VGA passthrough. Under 4.5rc1 I can give the VM more than 3.5 gigs,
> yet I *don't* need to use the "mmio_hole" settings in the VM config.
> Not sure why or what that might signify, if anything.
>
Does it run stable with Xen 4.5 without PCI/GPU passthru?
> Possibly useful information follows.
>
> Thanks,
>
> Steve
>
>
> (I was monitoring syslog over a network connection since nothing of
> value can be saved to disk under the circumstances.)
>
It'd be very helpful if you could set up a serial console to log all the Xen and dom0 Linux kernel messages,
so we could see where it actually crashes..
-- Pasi
next prev parent reply other threads:[~2014-11-04 8:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 21:46 Regression, host crash with 4.5rc1 Steve Freitas
2014-11-03 21:52 ` Steve Freitas
2014-11-04 14:01 ` Don Slutz
2014-11-04 8:20 ` Pasi Kärkkäinen [this message]
2014-11-04 10:15 ` Jan Beulich
2014-11-10 8:03 ` Steve Freitas
2014-11-10 8:51 ` Jan Beulich
2014-11-10 20:05 ` Steve Freitas
2014-11-11 8:05 ` Jan Beulich
2014-11-17 19:21 ` Steve Freitas
2014-11-18 7:54 ` Jan Beulich
2014-11-20 1:23 ` Steve Freitas
2014-11-20 7:59 ` Jan Beulich
2014-11-20 20:07 ` Steve Freitas
2014-11-21 8:42 ` Jan Beulich
2014-11-23 1:28 ` Steve Freitas
2014-11-24 8:45 ` Jan Beulich
2014-11-24 9:08 ` Steve Freitas
2014-11-24 9:15 ` Jan Beulich
2014-11-24 11:41 ` Jan Beulich
2014-11-24 22:17 ` Steve Freitas
2014-11-25 8:16 ` Jan Beulich
2014-11-25 9:38 ` Steve Freitas
2014-11-25 11:00 ` Jan Beulich
2014-11-27 5:29 ` Steve Freitas
2014-11-27 9:27 ` Jan Beulich
2014-11-28 8:24 ` Steve Freitas
2014-11-28 8:50 ` Jan Beulich
2014-11-28 9:44 ` Steve Freitas
2014-12-03 17:14 ` Dugger, Donald D
2015-02-27 17:25 ` Dugger, Donald D
2015-02-27 17:50 ` Brown, Len
2015-03-02 15:24 ` Jan Beulich
2015-03-09 0:45 ` Steve Freitas
2015-03-26 20:49 ` Brown, Len
2014-11-21 9:31 ` Jan Beulich
2014-11-04 18:35 ` Steve Freitas
2014-11-04 14:39 ` Don Slutz
2014-11-06 23:20 ` Steve Freitas
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=20141104082012.GY12451@reaktio.net \
--to=pasik@iki.fi \
--cc=dslutz@verizon.com \
--cc=sflist@ihonk.com \
--cc=xen-devel@lists.xen.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 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.