From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754981AbcJUQr2 (ORCPT ); Fri, 21 Oct 2016 12:47:28 -0400 Received: from mail.skyhub.de ([78.46.96.112]:57243 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752432AbcJUQr1 (ORCPT ); Fri, 21 Oct 2016 12:47:27 -0400 Date: Fri, 21 Oct 2016 18:47:23 +0200 From: Borislav Petkov To: sonofagun@openmailbox.org Cc: linux-kernel@vger.kernel.org, Nikos Barkas Subject: Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix Message-ID: <20161021164723.c5rh7kgulba2aq6i@pd.tnic> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/ (1.7.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Ioannis, first of all, when you reply to a mail on lkml, please use the "reply-to-all" functionality of your mail client - otherwise replies might get missed on such a high volume mailing list. On Fri, Oct 21, 2016 at 07:19:07PM +0300, sonofagun@openmailbox.org wrote: > Sorry for the late reply! This machine has caused nothing but trouble. HP > will not fix it and we will not choose their laptops anymore... You're not the only one making this experience. > My brother told me that we apply a quirk to the last Ontario APUs that do > not need it but I did not think it would be an issue since they have fixed > the error. No, you need to apply the fix only on the models which need it. > It seems better this way so that only affected APUs are patched. Be patient, > we are compiling the new patch right now but compiling is run on a different > high end AMD machine of my brother. Tomorrow I will have access to the > laptop and I will update the kernel and send you the V2 patch. Compiling to > that laptop would possibly need a whole day even with AC power! You can build somewhere else and copy the kernel to the laptop. That's how I do it. > Do you want /proc/cpuinfo on the V2 patch e-mail? Both CPUs needed? No, I just wanted to see them and you've pasted them here. Thanks. > Here is a dump from an older installation some months ago I kept on my > disk(tomorrow I will dump it again if you want): No need, one is enough :) > > Then, keep that *whole* changelog above when sending v2 of the patch > What do you mean? It is not clear to me, Do you mean all the info we wrote > on the e-mail, your comments or both? All the info you wrote in the first mail. > We have many AMD machines and we will need your help next week to patch our > Phenom(tm) II X6. Why, what's wrong with that one? That one should be all fixed! :-) I have such box too and it runs fine. > Let's finish this patch first and we will fix that too but it appears > to be much more difficult... Don't hesitate to ask if you need help... HTH. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.