[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DBB04C1.30003@gmail.com>
Date: Fri, 29 Apr 2011 20:34:41 +0200
From: Jiri Slaby <jirislaby@...il.com>
To: "Ostrovsky, Boris" <Boris.Ostrovsky@....com>
CC: Jörg-Volker Peetz <peetz@...ato-kyma.net>,
Borislav Petkov <bp@...en8.de>,
Jörg-Volker Peetz <jvpeetz@....de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Herrmann3, Andreas" <Andreas.Herrmann3@....com>,
"Petkov, Borislav" <Borislav.Petkov@....com>,
the arch/x86 maintainers <x86@...nel.org>, stable@...nel.org
Subject: Re: Linux 2.6.38.4 : regression due to x86 AMD ARAT feature
On 04/24/2011 09:44 PM, Ostrovsky, Boris wrote:
> Borislav Petkov wrote, on 04/24/11 20:20:
>> On Sun, Apr 24, 2011 at 10:06:36AM +0200, Jörg-Volker Peetz wrote:
>>> With 2.6.38.4 the clock slows down and the affected laptop sometimes, e.g. for
>>> the output of "ps axuw" to appear, needs an input from the keyboard or the
>>> touchpad. Please find attached the kernel config file and the output of dmesg.
>>>
>>> Commenting out the the lines
>>>
>>> if (c->x86 >= 0xf && !cpu_has_amd_erratum(amd_erratum_400))
>>> set_cpu_cap(c, X86_FEATURE_ARAT);
>>>
>>> in arch/x86/kernel/cpu/amd.c makes this laptop work as before with kernel
>>> 2.6.38.3. I think these lines came with commit
>>> d7b7f0c401303dd7eafcff11752fe74d3b75c766.
> It's an old family fh processor (CPUID 00020F42) that
cpu_has_amd_erratum(amd_erratum_400) apparently hasn't picked up. Since
all fh processors are affected by this erratum I'll replace "c->x86 >=
0xf" with "c->x86 > 0xf" (and probably fix erratum formula anyway).
Hi, what's the status of this please?
I don't see the fix neither in the -next tree.
thanks,
--
js
--
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