All of lore.kernel.org
 help / color / mirror / Atom feed
From: sonofagun@openmailbox.org
To: Borislav Petkov <bp@alien8.de>
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: Mon, 24 Oct 2016 16:13:25 +0300	[thread overview]
Message-ID: <714acbaa1350bfe8927ccbea2425f4a9@openmailbox.org> (raw)
In-Reply-To: <20161024093510.od57fbvn5rsgxcua@pd.tnic>


> Sure, give me the exact command you're executing so that I can do it 
> here.
No command needed, just type:
sudo perf stat -a
and immediately exit with ctrl+C. That will give you a glimpse. See "% 
of all branches"
next open firefox, rerun the same command after firefox launches and 
immediately exit with ctrl+C
On that piece of crap I get branch-misses above 10% from boot without 
executing anything and perf does not like it so it displays it with red 
colour.
On my quad core kabini APU, in order to get 9% branch-misses I have to 
open 50 tabs on firefox. Something is terribly wrong here.

> Out of pure interest: do you remember how exactly you did reproduce 
> this
> issue?
Yes, using Ubuntu 16.04 will just crash everything! For example I had 
crashes with the software updater program. Moreover firefox would become 
unresponsive even with one tab.
Luckily initial tests of 16.10 seem promising as it is lighter and 
consumes 3~5% less RAM! Debian which was lighter was more responsive and 
had no crashes except an oops from adobe flash.
I believe that the bug is triggered by the unusually high branch-misses 
specific to this machine. After the fix, I got better OS and program 
responsiveness.

  reply	other threads:[~2016-10-24 13:13 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
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 [this message]
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=714acbaa1350bfe8927ccbea2425f4a9@openmailbox.org \
    --to=sonofagun@openmailbox.org \
    --cc=bp@alien8.de \
    --cc=levelwol@gmail.com \
    --cc=linux-kernel@vger.kernel.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.