From: Firenza <firenza@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: time freeze under 2.4.9
Date: Wed, 19 Nov 2003 02:25:42 -0800 [thread overview]
Message-ID: <20031119022542.J777@telecoma.net> (raw)
Hello,
Pretext: 4-way server runs on plain vanilla redhat 2.4.9-21
kernel for almost 2 years without any problems. Two weeks ago,
applications start to behave "strangely", which is traced
back to the fact that time "froze" on that server.
# strace sleep 1
...
nanosleep({1, 0}, <unfinished ...> (never returns)
date shows the freezing time, hwclock shows that the hardware
clock is still working and no suspicious kernel messages are
found in the logs.
Discouragingly, the same thing happened to a different server
(same kernel, very similar hardware) a couple of days later.
Additionally that server is not in use, which makes it less
likely that this behaviour is caused by a freshly introduced
application.
Rebooting fixed the problem, but the same behaviour surfaced
again for the first server a couple of hours ago.
What circumstances could cause this behaviour?
Is there a way to further pinpoint the cause?
cheers,
Firenza
reply other threads:[~2003-11-19 10:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20031119022542.J777@telecoma.net \
--to=firenza@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/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