linux-kernel - Re: 2.6.30-rc4: microcode: failed to init CPU1

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, 19 May 2009 11:11:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dmitry Adamushko <dmitry.adamushko@...il.com>
Cc:	Thomas Meyer <thomas@...3r.de>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jaswinder Singh Rajput <jaswinderrajput@...il.com>
Subject: Re: 2.6.30-rc4: microcode: failed to init CPU1


* Dmitry Adamushko <dmitry.adamushko@...il.com> wrote:

> 
> >> [ ... ]
> >> [ 6643.982900] microcode: failed to init CPU1
> >> [ 6643.983528] CPU1 is up
> >> [ 6643.984529] ACPI: Waking up from system sleep state S4
> >> [ 6644.290917] pci 0000:00:1e.0: power state changed by ACPI to D0
> >> [ 6644.291103] ata_piix 0000:00:1f.1: power state changed by ACPI to D0
> >> [ 6644.291139] ata_piix 0000:00:1f.1: restoring config space at offset 0x1 (was 0x2800001, writing 0x2800005)
> >> [ 6644.291187] ata_piix 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00003, writing 0x2b00007)
> >> [ 6644.297593] pci 0000:00:07.0: PME# disabled
> >>
> >> Is this an error/problem?
> >
> > Not sure.
> >
> > CCing the people who have worked with the Intel microcode code recently.
> 
> 
> does the error message disappear with the following patch applied?
> 
> Thanks in advance.
> 
> 
> ---
> 
> 
> Subject: error handling inconsistency
> 
> Don't report an error in case there is simply no cached microcode 
> update available when resuming.
> 
> p.s. the current version in -tip provides better error handling 
> and doesn't have this problem.
> 
> Signed-off-by: Dmitry Adamushko <dmitry.adamushko@...il.com>

We can do your fixlet for .30 as well (if it's tested by Thomas to 
solve the problem) - the reworked code in -tip is invasive changes 
aimed at .31.

	Ingo
--
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/