xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Steve Freitas <sflist@ihonk.com>
To: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
Subject: Re: Regression, host crash with 4.5rc1
Date: Mon, 03 Nov 2014 13:52:53 -0800	[thread overview]
Message-ID: <5457F935.8040806@ihonk.com> (raw)
In-Reply-To: <5457F79B.2020300@ihonk.com>

On 11/3/2014 13:46, Steve Freitas wrote:
> Hi all,
>
> 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.

Whoops, neglected to include the following log which, I expect, is useless:

root@g2:/var/log/xen# cat qemu-dm-clippy2.log
char device redirected to /dev/pts/2 (label serial0)

  reply	other threads:[~2014-11-03 21:52 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 [this message]
2014-11-04 14:01   ` Don Slutz
2014-11-04  8:20 ` Pasi Kärkkäinen
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=5457F935.8040806@ihonk.com \
    --to=sflist@ihonk.com \
    --cc=dslutz@verizon.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 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).