Open ghost opened 7 years ago
This is the same symptom as #93 too isn't it?
Hostboot team needs their printk buffer to debug this much because it just indicates a process in Hostboot crashed.
The real esel might have the printk buffer too.
I think #93 may be a misnomer, and perhaps it's just a product of this same bug (that was built on the same machine and it looks awfully similar).
Ironically, in a world of reproducible builds, we'd be able to spot this without even attempting the boot.
I'll try and bisect down what change made this start occurring.
op-build 1b366c2de9d38cbcc9a25635a20961c95f976687 hostboot-a4b7bb77b3c152af89a57f904f323228ad24373d
Does not boot on habanero:
This is after a full power off of the machine, fresh flash and boot attempt.
This particular Habanero has a TPM.
Built on Fedora 25 ppc64 on a (large, 224 threads) POWER7 system.
Host GCC is gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)