When my Skylake system comes out of S3 it fails to resume and ends up going back through the normal boot path. Console output durng resume:
coreboot-4.4-1781-g2fcabb8-heads Wed Oct 5 01:45:23 UTC 2016 ramstage starting... FSP_INFO_HEADER not set! Enumerating buses... Enabling Common Clock Configuration ASPM: Enabled L1 done Allocating resources... Reading resources... CPU_CLUSTER: 0 missing read_resources Done reading resources. Setting resources... PNP: 0c09.0 missing set_resources Done setting resources. Done allocating resources. (and then it reboots) My guess is that this is due to the hacks to disable the relocatable ramstage: > CONFIG_RELOCATABLE_RAMSTAGE: > The reloctable ramstage support allows for the ramstage to be built > as a relocatable module. The stage loader can identify a place > out of the OS way so that copying memory is unnecessary during an S3 > wake. When selecting this option the romstage is responsible for > determing a stack location to use for loading the ramstage. I filed an issue on the tracker related to the ramstage problem and am trying to debug it with Aaron: https://ticket.coreboot.org/issues/78 -- Trammell -- coreboot mailing list: [email protected] https://www.coreboot.org/mailman/listinfo/coreboot
