All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: sonofagun@openmailbox.org
Cc: linux-kernel@vger.kernel.org, Nikos Barkas <levelwol@gmail.com>
Subject: Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix
Date: Fri, 21 Oct 2016 18:47:23 +0200	[thread overview]
Message-ID: <20161021164723.c5rh7kgulba2aq6i@pd.tnic> (raw)
In-Reply-To: <f91808d9d3929727a18e267e3081ff98@openmailbox.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.

  reply	other threads:[~2016-10-21 16:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 16:19 [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix sonofagun
2016-10-21 16:47 ` Borislav Petkov [this message]
2016-10-21 21:51   ` sonofagun
2016-10-21 23:01     ` Borislav Petkov
2016-10-22 11:16       ` sonofagun
2016-10-22 14:12         ` Borislav Petkov
2016-10-23  9:39           ` sonofagun
2016-10-23  9:57             ` Borislav Petkov
2016-10-23 17:06               ` sonofagun
2016-10-23 17:25                 ` Borislav Petkov
2016-10-23 21:02                   ` sonofagun
2016-10-23 21:39                     ` Borislav Petkov
2016-10-24 11:38                       ` sonofagun
2016-10-24  9:35                         ` Borislav Petkov
2016-10-24 13:13                           ` sonofagun
2016-10-24 17:14                             ` Borislav Petkov
2016-10-24 20:39                               ` sonofagun
2016-10-25  9:29                                 ` Borislav Petkov
2016-10-25 13:16                                   ` sonofagun
2016-10-28 16:21                               ` Borislav Petkov
2016-10-31 21:54                                 ` sonofagun
2016-10-31 22:59                                   ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2016-10-19 13:58 sonofagun
2016-10-19 15:00 ` Borislav Petkov

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=20161021164723.c5rh7kgulba2aq6i@pd.tnic \
    --to=bp@alien8.de \
    --cc=levelwol@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sonofagun@openmailbox.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.