[coreboot] Memory corruption on Resume from S3 Baytrail
Gailu Singh
gailu96 at gmail.com
Fri Nov 21 06:23:57 CET 2014
Hi Stefan,
I am using FSP. My cbfs prints are below.
Name Offset Type Size
cmos_layout.bin 0x200000 cmos_layout 1132
pci8086,0f31.rom 0x2004c0 optionrom 65536
fallback/romstage 0x210500 stage 27813
fallback/ramstage 0x217200 stage 68181
fallback/payload 0x227cc0 payload 269102
config 0x269840 raw 4540
(empty) 0x26aa40 null 4871576
cpu_microcode_blob.bin 0x710000 microcode 208896
(empty) 0x743040 null 53080
mrc.cache 0x74ffc0 (unknown) 65536
(empty) 0x760000 null 393112
fsp.bin 0x7bffc0 (unknown) 229376
(empty) 0x7f8000 null 31640
On Fri, Nov 21, 2014 at 2:06 AM, Stefan Reinauer <
stefan.reinauer at coreboot.org> wrote:
> * Gailu Singh <gailu96 at gmail.com> [141119 20:36]:
> > Hi Experts,
> >
> > I am using Baytrail SoC board (Bayleybay CRB) and testing suspend/resume
> from
> > Linux (kernel 3.10). I can suspend with pm-suspend and resume with power
> > button; however after resuming I get following logs in Linux
> > Corrupted low memory at c0001004 (1004 phys) = 0008eaea
> > Corrupted low memory at c0001008 (1008 phys) = b0606600
> > ...
> > Corrupted low memory at c00018fc (18fc phys) = 000008ea
> >
> > This seems to be caused by coreboot as I do not see these logs if I use
> BIOS
> > instead of coreboot.
> > Is it true that during resume coreboot uses RAM portion already mapped
> by Linux
> > and thus corrupting it. How to I avoid the RAM conflict?
>
> Hi Gailu,
>
> is this happening with FSP or mrc.bin?
>
> Stefan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20141121/4ba8445f/attachment.html>
More information about the coreboot
mailing list