From: Don Slutz <dslutz@verizon.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU
Date: Wed, 19 Mar 2014 15:44:13 -0400 [thread overview]
Message-ID: <5329F38D.6090308@terremark.com> (raw)
I just noticed these messages from a 4.5-unstable build (a03984e + xenctx changes):
(XEN) Xen version 4.5-unstable (don@culpepper.cloudswitch.com) (gcc (GCC) 4.7.2 20120921 (Red Hat 4.7.2-2)) debug=y Tue Mar 18 14:00:04 EDT 2014
(XEN) Latest ChangeSet: Thu Dec 12 19:17:03 2013 +0000 git:a03984e
...
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479270] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU1
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479328] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU2
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479346] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU3
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479366] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU4
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479381] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU5
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479398] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU6
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479411] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU7
Mar 19 15:31:16 dcs-xen-54 kernel: [ 92.479427] xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU8
This related to no-cpuidle that I have specified. Is this a bug or is it expected?
-Don Slutz
next reply other threads:[~2014-03-19 19:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 19:44 Don Slutz [this message]
2014-03-19 20:04 ` xen-acpi-processor: (CX): Hypervisor error (-38) for ACPI CPU Konrad Rzeszutek Wilk
2014-03-19 20:07 ` Andrew Cooper
2014-03-19 20:20 ` Konrad Rzeszutek Wilk
2014-03-20 2:38 ` Don Slutz
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=5329F38D.6090308@terremark.com \
--to=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 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.