Re: [coreboot] [PUBLIC INFO] Intel's Atom C2000 chips are bricking products – and it's not just Cisco hit

Hm... The saga continues! As additional info to ones who are using C2000 (formerly known as Rangeley). http://www.fudzilla.com/news/processors/42876-intel-s-atom-c2000-chip-flaw-spreads-to-juniper Common sense would dictate QA and clock circuit designer get fired on spot. But, how now INTEL

[coreboot] KGPE-D16: More insights on the PCI hang failure

Hi folks, as we know, the KGPE-D16 is likely to hang during PCI init, especially if the serial console is enabled (Timothy mentioned that he did not observe failures with the debug level of the console lowered - however, for me this did not work). Typical symptoms look like the following:

Re: [coreboot] Understand vboot logic to select FW_B

On 2017-02-15 13:34, Aaron Durbin wrote: On Wed, Feb 15, 2017 at 3:20 PM, wrote: On 2017-02-15 09:45, Aaron Durbin via coreboot wrote: On Wed, Feb 15, 2017 at 11:38 AM, wrote: On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: On Tue,

Re: [coreboot] ASUS KGPE-D16 Automated Test Failure [master]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/15/2017 03:34 PM, Raptor Engineering Automated Coreboot Test Stand wrote: > The ASUS KGPE-D16 fails verification for branch master as of commit > 901efea8abbb3131685fd69fd4ad7c5093c8cb3c > > The following tests failed: > BOOT_FAILURE > >

[coreboot] ASUS KGPE-D16 Automated Test Failure [master]

The ASUS KGPE-D16 fails verification for branch master as of commit 901efea8abbb3131685fd69fd4ad7c5093c8cb3c The following tests failed: BOOT_FAILURE Commits since last successful test: 901efea libpayload: x86/exec - fix return value passing d42c38b libpayload: x86/exec - fix libpayload API

Re: [coreboot] Understand vboot logic to select FW_B

On Wed, Feb 15, 2017 at 3:20 PM, wrote: > On 2017-02-15 09:45, Aaron Durbin via coreboot wrote: >> >> On Wed, Feb 15, 2017 at 11:38 AM, wrote: >>> >>> On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: On Tue, Feb 14, 2017 at 8:26

Re: [coreboot] Understand vboot logic to select FW_B

On 2017-02-15 09:45, Aaron Durbin via coreboot wrote: On Wed, Feb 15, 2017 at 11:38 AM, wrote: On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: On Tue, Feb 14, 2017 at 8:26 PM, wrote: Folks, I'm working on coreboot on ARMv8

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

Hi, > > after a lengthy bisection run I was able to nail down the commit which is > > causing the MC4 errors in the configurations I tested. I reverted the > > commit on top of current master, and now my KGPE-D16 fully works without > > MC4 errors in both 1-CPU-package und 2-CPU-package

Re: [coreboot] Understand vboot logic to select FW_B

On Wed, Feb 15, 2017 at 11:38 AM, wrote: > On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: >> >> On Tue, Feb 14, 2017 at 8:26 PM, wrote: >>> >>> >>> Folks, >>> I'm working on coreboot on ARMv8 architecture and recently attempted to >>> verify

Re: [coreboot] Understand vboot logic to select FW_B

On 2017-02-15 07:46, Aaron Durbin via coreboot wrote: On Tue, Feb 14, 2017 at 8:26 PM, wrote: Folks, I'm working on coreboot on ARMv8 architecture and recently attempted to verify FW_B can be selected if FW_A is corrupted. In reviewing the code-path through coreboot

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/15/2017 08:07 AM, Daniel Kulesz via coreboot wrote: > Hi folks, > > after a lengthy bisection run I was able to nail down the commit which is > causing the MC4 errors in the configurations I tested. I reverted the commit > on top of current

Re: [coreboot] Understand vboot logic to select FW_B

On Tue, Feb 14, 2017 at 8:26 PM, wrote: > > Folks, > I'm working on coreboot on ARMv8 architecture and recently attempted to > verify FW_B can be selected if FW_A is corrupted. > > In reviewing the code-path through coreboot vboot wrapper and > vboot_reference library I'm

Re: [coreboot] KGPE-D16 and Samsung DDR3L memory sticks

Hi folks, after a lengthy bisection run I was able to nail down the commit which is causing the MC4 errors in the configurations I tested. I reverted the commit on top of current master, and now my KGPE-D16 fully works without MC4 errors in both 1-CPU-package und 2-CPU-package configurations -

[coreboot] Understand vboot logic to select FW_B

Folks, I'm working on coreboot on ARMv8 architecture and recently attempted to verify FW_B can be selected if FW_A is corrupted. In reviewing the code-path through coreboot vboot wrapper and vboot_reference library I'm not understanding the logic. The logic appears to be that