From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Vitaliy Tomin <highwaystar.ru@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: HVM crash system on AMD APU A8-6600K
Date: Mon, 3 Feb 2014 14:41:56 +0000 [thread overview]
Message-ID: <52EFAAB4.4010607@citrix.com> (raw)
In-Reply-To: <CABPT1LvjDJVy1d-GyjZxFPzYnJ0bfuQWqvd56u2zZ0Z_EL8ozA@mail.gmail.com>
On 03/02/14 14:36, Vitaliy Tomin wrote:
>> What about without PCI passthrough? In all cases you appear to be
> passing the embedded graphics through to an HVM domain
>
> Next log captured with following hvm domain config:
>
> name = 'blank'
> builder = 'hvm'
> memory = 1024
>
> Only 3 lines. It takes longer to crash, about 5-10 minutes, with OS in
> hvm it takes less than a minute.
>
> Now trying to make log with watchdog added
Don't bother - my suggestion of watchdog was for a hang, not a reset.
Looking further through the logs,
(XEN) APIC error on CPU1: 00(40)
(XEN) APIC error on CPU0: 00(40)
(XEN) APIC error on CPU2: 00(40)
(XEN) APIC error on CPU3: 00(40)
Show that "Received illegal vector" has been indicated on all cpus,
beside a comment in the code which states "This interrupt should never
happen with our APIC/SMP architecture"
This appears to consistently happen after updating the PCI routing
entries on the first IOAPIC.
~Andrew
next prev parent reply other threads:[~2014-02-03 14:41 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 [this message]
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=52EFAAB4.4010607@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=highwaystar.ru@gmail.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).