From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Vitaliy Tomin <highwaystar.ru@gmail.com>
Cc: xen-devel@lists.xensource.com, Jan Beulich <JBeulich@suse.com>,
SuraveeSuthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: HVM crash system on AMD APU A8-6600K
Date: Mon, 3 Feb 2014 14:09:08 +0000 [thread overview]
Message-ID: <52EFA304.4000206@citrix.com> (raw)
In-Reply-To: <CABPT1Ls8zmXLDuhwxtnTSndBLVvVS2_chokQs-WGg0_THJ663Q@mail.gmail.com>
On 03/02/14 13:58, Vitaliy Tomin wrote:
> lspci output attached.
>
> I have never managed to crash system with debug=y, but I can provide
> serial log captured with debug=y and HVM domain running up.
That is a curious data point - it would imply that debug mode is doing
something which non-debug mode fails to do.
Could you provide the log please?
Can you explain "=== whole system crashed ===" a little more.
Given the lack of stack trace or any hint of a problem from Xen, is it a
system hang? Does adding "watchdog" to the Xen command line cause the
failure to change?
Looking back at the debug=n serial log in combination with the PCI topology,
(XEN) AMD-Vi: No iommu for device 0000:00:00.2
(XEN) setup 0000:00:00.2 for d0 failed (-19)
Device 00:00.2 is the IOMMU itself. I would have thought applying IOMMU
translation to the IOMMU is going to end in tears. Suravee; Can you
comment about this? is the IOMMU expected to have an IVRS entry?
~Andrew
next prev parent reply other threads:[~2014-02-03 14:09 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 [this message]
[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
-- 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=52EFA304.4000206@citrix.com \
--to=andrew.cooper3@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 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.