All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Doe <securef33d@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Subject: Re: (XEN) APIC error on CPU0: 40(00)
Date: Wed, 4 Nov 2015 22:09:43 +0100	[thread overview]
Message-ID: <563A7417.8020805@gmail.com> (raw)
In-Reply-To: <563A3CC402000078000B1D49@prv-mh.provo.novell.com>

On 04/11/2015 17:13, Jan Beulich wrote:
>>>> On 04.11.15 at 16:15, <securef33d@gmail.com> wrote:
>> Hi,
>> i just build the latest 4.3.0 kernel and ran it on qubes-os with xen
>> 4.4.3. I get this error just before the reboot:
>>
>>  [(XEN) APIC error on CPU0: 40(00)
> 
> And this appeared with the switch to kernel 4.3? No other variable
> (e.g. all config options new in 4.3 turned off)? I ask because the
> APIC is driven by Xen, not the kernel, and hence the kernel should
> have no (direct) influence on APIC behavior.

This started with 4.3.0, with 4.3.0-rc7 the system was booting properly
(except for the xsave=0 workaround, without that i also get a crash dump
right before the APIC error).

> 
>>  (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.
>>
>> I can also see some weird acpi-related messages on the log i attached, like:
>>  (XEN) ACPI: Invalid sleep control/status register data: 0:0x8:0x3 0:0x8:0x3
>> (XEN) ERST table was not found
>>  [    3.608404] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup
>> failure, AE_NOT_FOUND (20150818/dswload-210)
>>  [    3.608410] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog
>> (20150818/psobject-227)
>>  [    3.608439] ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while
>> loading table (20150818/tbxfload-193)
>>  [    3.619914] ACPI Error: 1 table load failures, 5 successful
>> (20150818/tbxfload-214)
>>  [    3.679113] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
>> [    3.688942] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep
>> State [\_S1_] (20150818/hwxface-580)
>>  [    3.688948] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep
>> State [\_S2_] (20150818/hwxface-580)
>>  [    3.756027] PM-Timer failed consistency check  (0xffffff) - aborting.
>>
>> With older kernels (like 3.12 or 4.2.1) i always see those messages but
>> i'm able to boot without the acpi error.
> 
> I guess those latter messages are unrelated - not the difference
> between ACPI and APIC. Also I'm unsure about you saying "boot"
> here but "reboot" above?

The APIC error prevents me from booting the machine, causing a forced
reboot, the above messages won't. They are present even when the system
starts correctly with older kernels.


> 
>> My machine runs on skylake cpu with z170 chipset and the latest bios.
>> Any ideas on how to fix this?
> 
> Not without first figuring out what bad vector is being received
> by the APIC, which likely will involved quite a bit of debugging
> and code instrumentation.

Do you think that this could be caused by some sort of hardware/firmware
issue?

Thanks,
J.

> 
> Jan
> 

  reply	other threads:[~2015-11-04 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 15:15 (XEN) APIC error on CPU0: 40(00) John Doe
2015-11-04 16:13 ` Jan Beulich
2015-11-04 21:09   ` John Doe [this message]
2015-11-05  7:55     ` Jan Beulich

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=563A7417.8020805@gmail.com \
    --to=securef33d@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=xen-devel@lists.xenproject.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.