-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TPM2 luks-seal, out of memory for object contexts #159
Comments
that's unfortunate. we are making assumptions about how many resources are available for the various TPM operations and seem to have guessed wrongly. we do a maybe we need an additional one between the |
Interesting that sounds likely, hopefully the TPM on this machine isn't too limited. Was also wondering if there's a means to provision more memory to the TPM but don't know where to look if it's set by the kernel, a driver, the firmware, or a hardware limitation. Dell also originally released this machine with TPM1.2 but then upgraded it to TPM2 so there may be implementation limitations. I will be away from the machine a few days but will try patching it there with a tpm2_flushall and report back. |
Unfortunately it it is a hardware constraint, not something that the kernel or firmware can allocate more memory for. The TCG allows tpm2 to have very limited memory and their idea is that there is a kernel resource allocator that handles freeing resources. We're running in a raw mode, which means we have to keep track of how many things are available (I'm not sure if we even have a way to query it), and as a result sometimes run into this sort of issue. |
Fix for the TPM memory error "out of memory for object contexts" at luks-seal (osresearch#159 osresearch#159)
Dell Optiplex 5050 with TPM2 is providing this TPM error "out of memory for object contexts" at luks-seal. Not sure what could be wrong or where to turn, did a TPM clear prior to running it. Any suggestions on troubleshooting commands?
It seems like the TPM is available:
The text was updated successfully, but these errors were encountered: