linux-um archives
 help / color / mirror / Atom feed
From: Stanislav Meduna <stano@meduna.org>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: openssl-dev@openssl.org
Subject: Re: [uml-devel] /dev/random problems .. or FP registers corruption?!
Date: Thu, 07 Aug 2008 11:49:25 +0200	[thread overview]
Message-ID: <489AC525.3060305@meduna.org> (raw)
In-Reply-To: <48995D1A.6030203@meduna.org>

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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2008-08-07  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 12:40 [uml-devel] /dev/random problems _not_ solved in 2.6.26 Stanislav Meduna
2008-08-04 16:42 ` Jeff Dike
2008-08-05 19:37   ` Stanislav Meduna
2008-08-05 21:32     ` Brock, Anthony - NET
2008-08-06  8:13       ` Stanislav Meduna
2008-08-07  9:49         ` Stanislav Meduna [this message]
2008-08-07 12:13           ` [uml-devel] /dev/random problems .. or FP registers corruption?! Stanislav Meduna
2008-08-08 12:35             ` [uml-devel] FP registers corruption Stanislav Meduna
2008-08-25 21:51               ` Jeff Dike
2008-08-26  7:20                 ` Stanislav Meduna
2008-08-26 17:46                   ` Jeff Dike
2008-08-26 18:07                     ` Stanislav Meduna
2008-08-26 18:44                       ` Jeff Dike
2008-08-26 18:51                         ` Stanislav Meduna
2008-08-27 14:59                           ` Jeff Dike
2008-09-08 12:13                           ` Stanislav Meduna
2008-09-09 22:56                             ` Stanislav Meduna
2008-09-12 20:27                               ` Stanislav Meduna

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=489AC525.3060305@meduna.org \
    --to=stano@meduna.org \
    --cc=openssl-dev@openssl.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox