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: Sat, 22 Oct 2016 14:16:41 +0300 [thread overview]
Message-ID: <52b804e35d9e82a46b35409586475ee2@openmailbox.org> (raw)
In-Reply-To: <20161021230143.4wwop3giwwuzbkpr@pd.tnic>
Patch does not compile.
I tried to add pci.h but did nothing.
I converted pci_read_config to pci_read_config_dword but again nothing.
On 2016-10-22 02:01, Borislav Petkov wrote:
> Do you have a way to trigger that one?
To be honest I can't say. My brother's machine(s) has random crashes
from time to time. We suspect that this erratum is to blame. He must
have kept some information at least from one of those crashes but there
was no time to analyze them till now. Finding those logs on our disks
needs a big effort but it will be done! We are willing to discover the
trouble maker no matter what it takes. To do that the machine must be
stripped off from all cards and then put on quarantine. Then we can
connect it with a another machine with an RS-232 cable to see what is
wrong. After that we must test it on a different motherboard we have. I
think we have one with a BIOS from a different BIOS vendor. We will
surely inform you on this one as we can't do such a patch. So we will
focus on triggering this bug. One thing is sure, its BIOS has no
workaround for that erratum.
next prev parent reply other threads:[~2016-10-22 11:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 16:19 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 [this message]
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=52b804e35d9e82a46b35409586475ee2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome