Re: [stable] [0/9] 184.108.40.206-stable review
From: Greg KH
Date: Sun Jan 17 2010 - 10:38:12 EST
On Sat, Jan 16, 2010 at 09:03:52PM +0200, Ozan ??a??layan wrote:
> Greg KH wrote:
> > This is the start of the stable review cycle for the 220.127.116.11 release.
> > There are 9 patches in this series, all will be posted as a response to
> > this one. If anyone has any issues with these being applied, please let
> > us know. If anyone is a maintainer of the proper subsystem, and wants
> > to add a Signed-off-by: line to the patch, please respond with it.
> Hi Greg,
> 1. There's this "mce: native_apic_write_dummy()" WARNING which causes governor failures on
> some of systems.
> Here's what I wrote in the last comment of the bug:
> The following 2 commits from linux-2.6 fixes the issue on 18.104.22.168 on my
> system. I think they should at least be sent to stable@xxxxxxxxxx for 2.6.32.y
> inclusion if they are the correct/complete fixes:
> >From 485a2e1973fd9f98c2c6776e66ac4721882b69e0 Mon Sep 17 00:00:00 2001
> From: Cyrill Gorcunov <gorcunov@xxxxxxxxxx>
> Date: Mon, 14 Dec 2009 17:56:34 +0900
> Subject: [PATCH] x86, mce: Thermal monitoring depends on APIC being enabled
> >From 70fe440718d9f42bf963c2cffe12008eb5556165 Mon Sep 17 00:00:00 2001
> From: Hidetoshi Seto <seto.hidetoshi@xxxxxxxxxxxxxx>
> Date: Mon, 14 Dec 2009 17:57:00 +0900
> Subject: [PATCH] x86, mce: Clean up thermal init by introducing
I'll review them for the next round of .32 patches.
> 2. Boot hangs on old AMD Athlon XP Processors (not 64, not X2) with CONFIG_X86_CPU_DEBUG enabled kernels:
> Reverting the following commit fixes the problem:
> >From 5095f59bda6793a7b8f0856096d6893fe98e0e51 Mon Sep 17 00:00:00 2001
> From: Jaswinder Singh Rajput <jaswin...@xxxxxxxxxx>
> Date: Fri, 5 Jun 2009 23:27:17 +0530
> Subject: [PATCH] x86: cpu_debug: Remove model information to reduce encoding-decoding
> Remove model information, encoding/decoding and reduce bookkeeping.
> This, besides removing a lot of code and cleaning up the code, also
> enables these features on many more CPUs that were enumerated before.
As this is going to be the last .31 release, and all users should really
be moving to .32, I'm not going to worry about this one. Is that ok
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/