From: Ingo Molnar <mingo@elte.hu>
To: Dmitry Adamushko <dmitry.adamushko@gmail.com>
Cc: Thomas Meyer <thomas@m3y3r.de>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
Subject: Re: 2.6.30-rc4: microcode: failed to init CPU1
Date: Tue, 19 May 2009 11:11:11 +0200 [thread overview]
Message-ID: <20090519091111.GA31404@elte.hu> (raw)
In-Reply-To: <1242588528.4814.6.camel@earth>
* Dmitry Adamushko <dmitry.adamushko@gmail.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@gmail.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
next prev parent reply other threads:[~2009-05-19 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 19:28 2.6.30-rc4: microcode: failed to init CPU1 Dmitry Adamushko
2009-05-19 9:11 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-06 18:09 Thomas Meyer
2009-05-16 21:04 ` Rafael J. Wysocki
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=20090519091111.GA31404@elte.hu \
--to=mingo@elte.hu \
--cc=dmitry.adamushko@gmail.com \
--cc=jaswinderrajput@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=thomas@m3y3r.de \
/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.