On Fri, Aug 23, 2013, Mark Pietras wrote: > More information on our issue... it appears that the failure is occurring in > a SSL_read that had immediately followed a SSL_write on the > same SSL-instance/socket. Some instances of the issue are during the same > thread slice and some have a context-switch or two between them (for > whatever that's worth). Is there a case/need of some kind of "flush" > between transitions of reading and writing? I'm assuming not, but just > fishing for leads/ideas... >
Try disabling AES-NI. That can be done with an environment variable: OPENSSL_ia32cap=~0x200000200000000 Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
