From: Jason Cooper <jason@lakedaemon.net>
To: Gene Heskett <gheskett@wdtv.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG BISECTED] Phenom microcode revision mis-applied
Date: Mon, 30 Dec 2013 07:37:00 -0500 [thread overview]
Message-ID: <20131230123700.GS19878@titan.lakedaemon.net> (raw)
In-Reply-To: <201312292202.02236.gheskett@wdtv.com>
On Sun, Dec 29, 2013 at 10:02:02PM -0500, Gene Heskett wrote:
...
> Finally done with the forward bisect:
>
> gene@coyote:~/linux-stable$ dmesg|grep -A2 microcode
> microcode: CPU0: patch_level=0x01000065
> microcode: CPU0: new patch_level=0x01000083
> microcode: CPU1: patch_level=0x01000065
> microcode: CPU1: new patch_level=0x01000083
> microcode: CPU2: patch_level=0x01000065
> microcode: CPU2: new patch_level=0x01000083
> microcode: CPU3: patch_level=0x01000065
> microcode: CPU3: new patch_level=0x01000083
> microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
>
> gene@coyote:~/linux-stable$ git bisect good
> 1a45c310b2102c58e37f84abba67fe21d5d6edcf is the first bad commit
> commit 1a45c310b2102c58e37f84abba67fe21d5d6edcf
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date: Thu Mar 14 11:27:14 2013 -0700
>
> Linux 3.8.3
>
> :100644 100644 20d53183508e8f49253ec7e5ede0a12b4556fc32 8c49fc9b45a993a8e78cde4f9621b727b9121eac M Makefile
>
> The v3.8.3 Makefile? Its just about the only thing that would be bad
> every step from v3.8.3 to v3.8.2, and good all the way from v3.8.2 to
> the last patch that made the v3.8.3 release. Bisected twice, once in
> each direction.
When it works, which CONFIG_MICROCODE* options are set? And unset when it
fails?
Also, what is the driving problem here? I know the log entry 'new
patch_level=...' is missing, but what regression are you seeing that is
caused by not updating the microcode?
thx,
Jason.
next prev parent reply other threads:[~2013-12-30 12:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 17:24 [BUG BISECTED] Gene Heskett
2013-12-29 17:47 ` [BUG BISECTED FAILED] Gene Heskett
2013-12-29 19:14 ` [BUG BISECTED FAILED] Phenom microcode revision mis-identified Jason Cooper
2013-12-29 19:49 ` Gene Heskett
2013-12-29 20:17 ` Gene Heskett
2013-12-29 20:19 ` Jason Cooper
2013-12-29 21:24 ` Gene Heskett
2013-12-30 3:02 ` [BUG BISECTED] Phenom microcode revision mis-applied Gene Heskett
2013-12-30 12:37 ` Jason Cooper [this message]
2013-12-30 14:56 ` Gene Heskett
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=20131230123700.GS19878@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=gheskett@wdtv.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®