On Tue, Oct 31, 2017 at 09:04:59PM +0100, Alessandro Grassi wrote: > Hi Mike, > > On Tue, Oct 31, 2017 at 5:34 PM, Mike Larkin <[email protected]> wrote: > > Can you send me the output of "machine memory" at the boot> prompt please? > > Here you go: > > Region 0: type 1 at 0x0 for 639KB > Region 1: type 2 at 0x9fc00 for 1KB > Region 2: type 2 at 0xf0000 for 64KB > Region 3: type 1 at 0x100000 for 3139192KB > Region 4: type 2 at 0xbfa9e000 for 267656KB > Region 5: type 2 at 0xf0000000 for 65536KB > Region 6: type 1 at 0x100000000 for 786432KB > Low ram: 639KB High ram: 3139192KB > Total free memory: 3926263KB > > Regards, > Alessandro
Those regions look ok. Can you try a small test: 1. on next boot> , type: mach mem =256M 2. then 'boot' 3. ZZZ 4. power up the machine again and do step 1 again that time See if that makes any difference. It's telling the kernel to only use 256MB RAM. You need to do the same thing in step 4 after restarting or it will think the memory size changed and skip un-hibernate. If that doesn't work, I'd start to think it's some sort of coreboot/libreboot thing as hibernate has been pretty stable for most machines for quite some time. We did make a change at the recent hackathon to make things faster, but I don't see how that would be causing this. Also, when you unhibernate your 4GB machine as above, does it sit for some time with a black screen after loading the hibernated image or does it instantly restart after reading it? -ml
