From: Borislav Petkov <bp@amd64.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Hans Rosenfeld <hans.rosenfeld@amd.com>,
"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: Regression in 2.6.36-rc1 bisected to commit 9d8888c
Date: Fri, 20 Aug 2010 09:51:25 +0200 [thread overview]
Message-ID: <20100820075125.GA23650@aftab> (raw)
In-Reply-To: <4C6DE7E3.4030702@lwfinger.net>
From: Larry Finger <Larry.Finger@lwfinger.net>
Date: Thu, Aug 19, 2010 at 09:26:43PM -0500
> With 2.6.36-rc1 from the mainline git tree, my x86_64 system running on an AMD
> Turion 64 x2 TL-60 has required pressing keys to get booting to advance. This
> behavior begins as soon as the kernel is loaded. I bisected the problem to:
>
> commit 9d8888c2a214aece2494a49e699a097c2ba9498b
> Author: Hans Rosenfeld <hans.rosenfeld@amd.com>
> Date: Wed Jul 28 19:09:31 2010 +0200
>
> x86, cpu: Clean up AMD erratum 400 workaround
>
> Remove check_c1e_idle() and use the new AMD errata checking framework
> instead.
>
> Signed-off-by: Hans Rosenfeld <hans.rosenfeld@amd.com>
> LKML-Reference: <1280336972-865982-2-git-send-email-hans.rosenfeld@amd.com>
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
>
> Reverting this patch allows the current 2.6.36-rc1+ to boot normally.
>
> This problem is entered into the Kernel Bugzilla as Bug #16636.
Fix is already upstream: http://git.kernel.org/tip/07a7795ca2e6e66d00b184efb46bd0e23d90d3fe
Can you verify it fixes your issue too please?
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2010-08-20 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 2:26 Regression in 2.6.36-rc1 bisected to commit 9d8888c Larry Finger
2010-08-20 7:51 ` Borislav Petkov [this message]
2010-08-20 13:54 ` Larry Finger
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=20100820075125.GA23650@aftab \
--to=bp@amd64.org \
--cc=Larry.Finger@lwfinger.net \
--cc=hans.rosenfeld@amd.com \
--cc=hpa@linux.intel.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 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.