Since this seems to be a communications issue, I was suggesting that you use the IBM TPM __utilities__ (not the SW TPM).
The utilities are a demo code simplified equivalent to trousers, but you can easily script them into loops for testing. It's divide and conquer: If the utilities work, you can blame trousers. If the utilities fail, blame the TPM or device driver. On 8/20/2015 5:51 PM, Mike Gerow wrote: > ...That said, I don't think we've actually tested our workload > for a significant amount of time using the IBM swtpm. I suppose there is > a chance the swtpm would pick up if trousers does something wrong that > the other TPMs just happen to handle better. I'll go ahead and do that! > > On Thu, Aug 20, 2015 at 7:51 AM, Ken Goldman <[email protected] > <mailto:[email protected]>> wrote: > > To isolate the issue, you might try the IBM TPM utilities at > ------------------------------------------------------------------------------ _______________________________________________ TrouSerS-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-users
