Hi,
Well, I am now puzzled quite a bit more. Another problem
on this UML box is that if I do tail -f on some file,
I ocassionally get an assertion:
tail: xnanosleep.c:67: xnanosleep: Assertion `0 <= seconds' failed.
This seems to happen more often (or at all) when I am
doing something using the openssl - tail -f on an apache
access log runs fine when I am doing http accesses
and fails quite repeatedly when I am doing https
or starting/terminating new SSL connection from/to the box.
I also have a few strace-s from the failing sshd,
where I can't really understand how the code got there.
These two have one thing in common - a double variable
that got initialized long ago and at the time of the
problem it looks like it mysteriously changed value:
"entropy" in the case of openssl and "sleep_interval"
in tail.
Am I seeing ghosts? Anyone got other mysterious
problems with current UML kernel? Could it be that
some state-saving method is corrupting fp registers
or something like that? Was there some change in the
UML / vanilla kernel recently?
To the openssl-ers: I am starting to think that openssl
is fine here and that the problem is indeed in the
UML kernel.
Regards
--
Stano
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
