It's hard to image in a hardware problem for something as simple as flushspecific, but you never know. The trace seems to show the response being received but tddl expecting/reading something more.
To isolate the issue, you might try the IBM TPM utilities at https://sourceforge.net/projects/ibmswtpm/ This isn't production code, but is useful for debugging. It could indicate whether the problem is within tcsd or the device driver/TPM. On 8/18/2015 7:03 PM, Mike Gerow wrote: > > I'm really at a loss for how to continue diagnosing this, though. It > might be a hardware issue, but even if that's the case it'd be nice to > find a way to try to prevent it from happening as often as it does > (currently when the TPM breaks like this the only course of action users > have is to restart their machine). I can probably provide some more > detailed logs if they would help. ------------------------------------------------------------------------------ _______________________________________________ TrouSerS-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-users
