From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: chipsec@lists.01.org
Subject: Re: [Luv] Results and a few questions
Date: Wed, 28 Oct 2015 15:25:58 -0700 [thread overview]
Message-ID: <1446071158.17978.1.camel@ranerica-desk01> (raw)
In-Reply-To: <1445889065.29566.56.camel@ranerica-desk01>
[-- Attachment #1: Type: text/plain, Size: 4481 bytes --]
Actually including the CHIPSEC mailing list this time.
On Mon, 2015-10-26 at 19:51 +0000, Neri, Ricardo wrote:
> +CHIPSEC mailing list
>
> Hi Jason,
>
> Thanks for your report.
>
> On Mon, 2015-10-26 at 12:04 -0700, Jason Barbier wrote:
> > Hey all,
> > I ran LUV-Live and my results are attached as a zip, I sort of was
> > wondering about the errors in the chipsec log though,
> > These were similar errors that I got last week that caused some issues
> > with my clock being reset using version 1.2, the latest RC seems to not
> > do that but It still can not seem to run all the tests.
> >
> > --
> > WARNING: 'SPIBAR' MMIO BAR definition not found/correct in XML config
> > [pci] reading B/D/F: 0/31/0, offset: 0xF0, value: 0xFED1C001
> > [spi] SPI MMIO base: 0x00000000FED1F800 (assuming below 4GB)
> > [spi] SPI MMIO base: 0x00000000FED1F800 (assuming below 4GB)
> > [-] Traceback (most recent call last):
> > File "/usr/lib/python2.7/site-packages/chipsec_main.py", line 291, in
> > run_module
> > result = modx.run( module_argv )
> > File "/usr/lib/python2.7/site-packages/chipsec/module.py", line 69, in
> > run
> > result = self.get_module_object()
> > File "/usr/lib/python2.7/site-packages/chipsec/module.py", line 101,
> > in get_module_object
> > self.mod_obj = iref()
> > File
> > "/usr/lib/python2.7/site-packages/chipsec/modules/common/bios_wp.py",
> > line 51, in __init__
> > self.spi = SPI( self.cs )
> > File "/usr/lib/python2.7/site-packages/chipsec/hal/spi.py", line 176,
> > in __init__
> > self.hsfs_off = int(chipsec.chipset.get_register_def( self.cs,
> > "HSFS" )['offset'],16)
> > File "/usr/lib/python2.7/site-packages/chipsec/chipset.py", line 467,
> > in get_register_def
> > return _cs.Cfg.REGISTERS[ reg_name ]
> > KeyError: 'HSFS'
> > --
> > [-] Traceback (most recent call last):
> > File "/usr/lib/python2.7/site-packages/chipsec_main.py", line 291, in
> > run_module
> > result = modx.run( module_argv )
> > File "/usr/lib/python2.7/site-packages/chipsec/module.py", line 80, in
> > run
> > result = self.mod_obj.run(module_argv)
> > File
> > "/usr/lib/python2.7/site-packages/chipsec/modules/common/spi_desc.py",
> > line 68, in run
> > return self.check_flash_access_permissions()
> > File
> > "/usr/lib/python2.7/site-packages/chipsec/modules/common/spi_desc.py",
> > line 48, in check_flash_access_permissions
> > frap = chipsec.chipset.read_register( self.cs, 'FRAP' )
> > File "/usr/lib/python2.7/site-packages/chipsec/chipset.py", line 470,
> > in read_register
> > reg = _cs.Cfg.REGISTERS[ reg_name ]
> > KeyError: 'FRAP'
> >
> > ERROR: Exception occurred during chipsec.modules.common.spi_desc.run():
> > ''FRAP''
> > --
> > [-] Traceback (most recent call last):
> > File "/usr/lib/python2.7/site-packages/chipsec_main.py", line 291, in
> > run_module
> > result = modx.run( module_argv )
> > File "/usr/lib/python2.7/site-packages/chipsec/module.py", line 80, in
> > run
> > result = self.mod_obj.run(module_argv)
> > File
> > "/usr/lib/python2.7/site-packages/chipsec/modules/common/spi_lock.py",
> > line 59, in run
> > return self.check_spi_lock()
> > File
> > "/usr/lib/python2.7/site-packages/chipsec/modules/common/spi_lock.py",
> > line 46, in check_spi_lock
> > hsfs_reg = chipsec.chipset.read_register( self.cs, 'HSFS' )
> > File "/usr/lib/python2.7/site-packages/chipsec/chipset.py", line 470,
> > in read_register
> > reg = _cs.Cfg.REGISTERS[ reg_name ]
> > KeyError: 'HSFS'
> >
> > ERROR: Exception occurred during chipsec.modules.common.spi_lock.run():
> > ''HSFS''
> > --
> >
> I added the CHIPSEC mailing list. Perhaps they can give further insight
> on what the problem might be.
>
> As per LUV, it seems that this exception somehow caused a crash in the
> LUV test manager and it prevented it from running the tests of the
> tests. It seems we need to add some safeguards so that LUV can handle
> these errors more gracefully.
>
> Thanks and BR,
> Ricardo
>
> >
> > _______________________________________________
> > Luv mailing list
> > Luv(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/luv
>
> _______________________________________________
> Luv mailing list
> Luv(a)lists.01.org
> https://lists.01.org/mailman/listinfo/luv
next parent reply other threads:[~2015-10-28 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1445889065.29566.56.camel@ranerica-desk01>
2015-10-28 22:25 ` Ricardo Neri [this message]
2015-10-29 0:54 ` [Luv] Results and a few questions Darren Bilby
2015-10-29 5:54 ` Loucaides, John
2015-10-29 6:12 ` Darren Bilby
2015-12-02 23:09 ` Loucaides, John
2015-12-04 6:41 ` Darren Bilby
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=1446071158.17978.1.camel@ranerica-desk01 \
--to=ricardo.neri-calderon@linux.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 NNTP newsgroup(s).