> I'm guessing this has something to do with coreboot, since that seems to be > the only large difference in play here. If you can find another machine > that's > the same model as yours w/o coreboot, and it still fails, let me know and I'll > dig further. But I tossed out all my hardware from this era a while ago.
I am sure coreboot is the problem. I suspect it skips some steps which a BIOS must do, or has some non-determinism on different powerups, or feeds our kernel AML + accessed data which results in different configuration being created by the bsd.booted kernel before hibernate-resume. Then when the original kernel starts running again, it hits something unexpected and explodes. We cannot tell what that is. The situation is that unhibernate is very reliable based upon an assumption that the underlaying hardware behaves the same on two seperate powerups. The only reports of failure I see are from those electing to run coreboot, so the people responsible for tracking this down are those people running coreboot.
