xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Vitaliy Tomin <highwaystar.ru@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: HVM crash system on AMD APU A8-6600K
Date: Tue, 8 Apr 2014 14:07:27 +0100	[thread overview]
Message-ID: <5343F48F.6070602@eu.citrix.com> (raw)
In-Reply-To: <5343CCEC02000078000066F8@nat28.tlf.novell.com>

On 04/08/2014 09:18 AM, Jan Beulich wrote:
>>>> On 07.04.14 at 17:36, <George.Dunlap@eu.citrix.com> wrote:
>> Suravee / Jan -- any ideas here?
>
> Not really, particularly not without a place where one can easily
> look up all relevant information in one go. I.e. I'm having trouble
> collecting together
> - the supposedly somewhere posted log with sync_console in place
> - the response to Andrew's question what "whole system crashed"
>    means (since in the so far provided logs there's no sign of a crash)
> - the answer to Sander's question regarding the behavior without
>    passing through the GPU
> - _if_ there really is no crash, a log with "watchdog" also in place,
>    as also requested by (I think) Andrew at some point
>
> If an old thread gets resumed after a longer period of silence, I
> think it would be very desirable if the reporter at least summarized
> or directly linked to all previously collected information.

FWIW, Vitaly first brought this up back in November, and then did 
summarize things, just as you describe, in the thread started in 
February.  It came up again because I had marked the one back in 
November as "look at at some point", and asked him about it. :-)

  -George

  parent reply	other threads:[~2014-04-08 13:07 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 13:47 HVM crash system on AMD APU A8-6600K Vitaliy Tomin
2014-02-03 13:51 ` Andrew Cooper
2014-02-03 13:58   ` Vitaliy Tomin
2014-02-03 14:08     ` Sander Eikelenboom
2014-02-03 14:09     ` Andrew Cooper
     [not found]       ` <CABPT1LscUZR_V1TOAzVmkvSms0M_Yucjp8WtUaeOADD_G-EbHA@mail.gmail.com>
2014-02-03 14:22         ` Vitaliy Tomin
2014-02-03 14:32         ` Andrew Cooper
2014-02-03 14:36           ` Vitaliy Tomin
2014-02-03 14:41             ` Andrew Cooper
2014-02-03 14:55             ` Konrad Rzeszutek Wilk
2014-02-03 15:18               ` Vitaliy Tomin
2014-02-03 15:47                 ` Boris Ostrovsky
2014-02-13 14:37                   ` Vitaliy Tomin
2014-04-07 15:36                     ` George Dunlap
2014-04-08  8:18                       ` Jan Beulich
2014-04-08  8:40                         ` Vitaliy Tomin
2014-04-08  9:14                           ` Jan Beulich
2014-04-08 12:53                             ` Vitaliy Tomin
2014-04-08 14:00                               ` Sander Eikelenboom
2014-04-08 15:23                                 ` Vitaliy Tomin
2014-04-08 16:02                                   ` Jan Beulich
2014-04-08 15:29                                 ` Vitaliy Tomin
2014-04-08 16:10                                   ` Sander Eikelenboom
2014-04-08 16:17                                     ` Konrad Rzeszutek Wilk
2014-04-09  1:43                                       ` Vitaliy Tomin
2014-04-10 13:01                                         ` Vitaliy Tomin
2014-04-10 13:30                                           ` Andrew Cooper
2014-04-10 13:56                                             ` Vitaliy Tomin
2014-04-10 13:59                                               ` Andrew Cooper
2014-04-10 14:33                                               ` Jan Beulich
2014-04-10 15:21                                                 ` Vitaliy Tomin
2014-04-10 15:23                                                   ` Andrew Cooper
2014-04-10 15:34                                                     ` Vitaliy Tomin
2014-04-10 15:39                                                       ` Andrew Cooper
     [not found]                                                         ` <CABPT1LuxW3cLrF74SN5FV41R6tGX6eq-5i2U7Tb712UDHStS7w@mail.gmail.com>
2014-04-10 15:59                                                           ` Andrew Cooper
2014-04-11 11:57                                                             ` Vitaliy Tomin
2014-04-11 13:30                                                               ` Jan Beulich
2014-05-03 15:43                                                                 ` Vitaliy Tomin
2014-05-05 11:06                                                                   ` Andrew Cooper
2014-05-05 11:24                                                                     ` Jan Beulich
2014-05-05 15:36                                                                       ` Vitaliy Tomin
2014-05-05 15:41                                                                         ` Jan Beulich
2014-04-08 13:07                         ` George Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-02  9:51 Vitaliy Tomin
2014-04-02 14:44 ` George Dunlap
2014-04-07 14:50   ` Vitaliy Tomin

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=5343F48F.6070602@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=highwaystar.ru@gmail.com \
    --cc=suravee.suthikulpanit@amd.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 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).