lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 21 Jan 2014 14:36:11 +0100
From:	poma <pomidorabelisima@...il.com>
To:	Robert Richter <rric@...nel.org>
CC:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for
 vector 0x400

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists