summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2011-10-09 23:32:56 -0400
committerPaul Gortmaker <paul.gortmaker@windriver.com>2011-10-09 23:32:56 -0400
commit9b50654ef45469678a7484d8ff16bf387cb49b16 (patch)
tree0f505e43869e2ca30e85607248c033d494de5c06
parentd5e563ad8de0c622a7abf2a5725c19acdd0e87b3 (diff)
downloadlongterm-queue-2.6.34-9b50654ef45469678a7484d8ff16bf387cb49b16.tar.gz
delete AMD-e400 patch that was reverted in 32.41
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
-rw-r--r--queue/series3
-rw-r--r--queue/x86-AMD-Fix-APIC-timer-erratum-400-affecting-K8-Rev..patch44
2 files changed, 2 insertions, 45 deletions
diff --git a/queue/series b/queue/series
index 7927a48..d5d5995 100644
--- a/queue/series
+++ b/queue/series
@@ -116,7 +116,8 @@ put-stricter-guards-on-queue-dead-checks.patch
mmc-sdhci-pci-Fix-error-case-in-sdhci_pci_probe_slot.patch
mmc-sdhci-Check-mrq-cmd-in-sdhci_tasklet_finish.patch
mmc-sdhci-Check-mrq-NULL-in-sdhci_tasklet_finish.patch
-x86-AMD-Fix-APIC-timer-erratum-400-affecting-K8-Rev..patch
+# reverted in .41
+# x86-AMD-Fix-APIC-timer-erratum-400-affecting-K8-Rev..patch
af_unix-Only-allow-recv-on-connected-seqpacket-socke.patch
ARM-6891-1-prevent-heap-corruption-in-OABI-semtimedo.patch
i8k-Tell-gcc-that-regs-gets-clobbered.patch
diff --git a/queue/x86-AMD-Fix-APIC-timer-erratum-400-affecting-K8-Rev..patch b/queue/x86-AMD-Fix-APIC-timer-erratum-400-affecting-K8-Rev..patch
deleted file mode 100644
index 372d85e..0000000
--- a/queue/x86-AMD-Fix-APIC-timer-erratum-400-affecting-K8-Rev..patch
+++ /dev/null
@@ -1,44 +0,0 @@
-From a12d98a363169cfd35675946afa4a9a428215e77 Mon Sep 17 00:00:00 2001
-From: Boris Ostrovsky <ostr@amd64.org>
-Date: Fri, 29 Apr 2011 17:47:43 -0400
-Subject: [PATCH] x86, AMD: Fix APIC timer erratum 400 affecting K8 Rev.A-E
- processors
-
-commit e20a2d205c05cef6b5783df339a7d54adeb50962 upstream.
-
-Older AMD K8 processors (Revisions A-E) are affected by erratum
-400 (APIC timer interrupts don't occur in C states greater than
-C1). This, for example, means that X86_FEATURE_ARAT flag should
-not be set for these parts.
-
-This addresses regression introduced by commit
-b87cf80af3ba4b4c008b4face3c68d604e1715c6 ("x86, AMD: Set ARAT
-feature on AMD processors") where the system may become
-unresponsive until external interrupt (such as keyboard input)
-occurs. This results, for example, in time not being reported
-correctly, lack of progress on the system and other lockups.
-
-Reported-by: Joerg-Volker Peetz <jvpeetz@web.de>
-Tested-by: Joerg-Volker Peetz <jvpeetz@web.de>
-Acked-by: Borislav Petkov <borislav.petkov@amd.com>
-Signed-off-by: Boris Ostrovsky <Boris.Ostrovsky@amd.com>
-Link: http://lkml.kernel.org/r/1304113663-6586-1-git-send-email-ostr@amd64.org
-Signed-off-by: Ingo Molnar <mingo@elte.hu>
-Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
-
-diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
-index d618dc1..89e2071 100644
---- a/arch/x86/kernel/cpu/amd.c
-+++ b/arch/x86/kernel/cpu/amd.c
-@@ -652,7 +652,7 @@ cpu_dev_register(amd_cpu_dev);
- */
-
- const int amd_erratum_400[] =
-- AMD_OSVW_ERRATUM(1, AMD_MODEL_RANGE(0xf, 0x41, 0x2, 0xff, 0xf),
-+ AMD_OSVW_ERRATUM(1, AMD_MODEL_RANGE(0x0f, 0x4, 0x2, 0xff, 0xf),
- AMD_MODEL_RANGE(0x10, 0x2, 0x1, 0xff, 0xf));
-
-
---
-1.7.7
-