All of lore.kernel.org
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: Robert Richter <rric@kernel.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400
Date: Tue, 21 Jan 2014 14:36:11 +0100	[thread overview]
Message-ID: <52DE77CB.6060003@gmail.com> (raw)
In-Reply-To: <20140115153446.GA5701@rric.localhost>

On 15.01.2014 16:34, Robert Richter wrote:
> On 10.01.14 04:21:11, poma wrote:
>>
>> Robert, is there a patch for this case?
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152484/comments/12
> 
> I just sent a patch to lkml that fixes this:
> 
>  https://lkml.kernel.org/r/1389797849-5565-1-git-send-email-rric.net@gmail.com
> 
> -Robert
> 

All right!
…
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
LVT offset 1 assigned for vector 0x400
IBS: LVT offset 1 assigned
microcode: CPU0: new patch_level=0x010000c8
Enabling non-boot CPUs ...
x86: Booting SMP configuration:
smpboot: Booting Node 0 Processor 1 APIC 0x1
kvm: enabling virtualization on CPU1
process: Switch to broadcast mode on CPU1
microcode: CPU1: new patch_level=0x010000c8
CPU1 is up
smpboot: Booting Node 0 Processor 2 APIC 0x2
kvm: enabling virtualization on CPU2
process: Switch to broadcast mode on CPU2
microcode: CPU2: new patch_level=0x010000c8
CPU2 is up
smpboot: Booting Node 0 Processor 3 APIC 0x3
kvm: enabling virtualization on CPU3
process: Switch to broadcast mode on CPU3
microcode: CPU3: new patch_level=0x010000c8
CPU3 is up
ACPI: Waking up from system sleep state S3
…
Lookin good!
Thanks!


poma



      reply	other threads:[~2014-01-21 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10  3:21 [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400 poma
2014-01-15 15:34 ` Robert Richter
2014-01-21 13:36   ` poma [this message]

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=52DE77CB.6060003@gmail.com \
    --to=pomidorabelisima@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rric@kernel.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.