From: Bjorge, Erik C <erik.c.bjorge@intel.com>
To: chipsec@lists.01.org
Subject: Re: chipsec integrity check
Date: Fri, 01 Dec 2017 00:27:05 +0000 [thread overview]
Message-ID: <7FE3244EBB31F1449E4EC79CFE44E3F4A4C76099@ORSMSX108.amr.corp.intel.com> (raw)
In-Reply-To: <81566ee3ec07486cb8aa6d4bea467028@fmsmsx106.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
Thanks for sending the new logs. Give us a day or so to look them over and see if we can find anything new.
Thanks,
-Erik
From: chipsec [mailto:chipsec-bounces(a)lists.01.org] On Behalf Of Healer64
Sent: Thursday, November 30, 2017 4:23 PM
To: Bjorge, Erik C <erik.c.bjorge@intel.com>
Cc: chipsec(a)lists.01.org
Subject: Re: [chipsec] chipsec integrity check
After a reboot, I ran the tests again. New log is here:
https://pastebin.com/XCHrYYJF
https://pastebin.com/NiYcnxGG
Just for kicks I did a diff of the 2 instances.
https://pastebin.com/KLea3gVf
Some of the BAR values have changed again. No longer 0. That seems odd.
Sent with ProtonMail<https://protonmail.com> Secure Email.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4800 bytes --]
next parent reply other threads:[~2017-12-01 0:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81566ee3ec07486cb8aa6d4bea467028@fmsmsx106.amr.corp.intel.com>
2017-12-01 0:27 ` Bjorge, Erik C [this message]
2017-12-01 19:32 ` chipsec integrity check Healer64
2017-12-11 19:11 ` Bjorge, Erik C
2017-12-15 16:32 ` Healer64
2017-12-19 18:47 ` Bjorge, Erik C
[not found] <7FE3244EBB31F1449E4EC79CFE44E3F4A4C733FF@ORSMSX108.amr.corp.intel.com>
2017-11-30 14:52 ` Healer64
2017-12-01 0:23 ` Healer64
2017-11-27 23:07 Healer64
2017-11-29 7:48 ` cod
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=7FE3244EBB31F1449E4EC79CFE44E3F4A4C76099@ORSMSX108.amr.corp.intel.com \
--to=erik.c.bjorge@intel.com \
--cc=chipsec@lists.01.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).