From: ralf@uni-koblenz.de
To: Trevor Schroeder <tschroed@cheetah.wsc.edu>
Cc: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Subject: Re: xntp
Date: Fri, 6 Mar 1998 19:25:14 +0100 [thread overview]
Message-ID: <19980306192514.14435@uni-koblenz.de> (raw)
In-Reply-To: <Pine.ULT.3.96.980306110037.5679B-100000@cheetah.wsc.edu>; from Trevor Schroeder on Fri, Mar 06, 1998 at 11:01:32AM -0600
On Fri, Mar 06, 1998 at 11:01:32AM -0600, Trevor Schroeder wrote:
> > Don't run xntpd; there is some bug in the MIPS stuff which locks the
> > machine, only the usual kernel hotkeys are still working. I don't
> > know why or if all platforms are affected. The crash happend on a
> > RM200. The time code is ripe for a complete overhaul anyway ...
>
> Do tell, what exactly is this bug? I'm using xntpd on a number of non-MIPS
> Linux hosts here and I'd like to verify that it's not going to be a problem.
I appears as if a syscall never terminates or so. xntpd just hangs in 'R'
(running) state in the process table. This happens immediately after
starting xntpd from the command line. For now I assume this to be a MIPS
only bug - Ulrich Windl posted some NTP4 related patches and that's about
everything I heared in the last time related to NTP bugs. So don't worry,
I'm going to fix it next week - there is something non-MIPSish on my to-do
list that is more urgent ...
On the other side xntpd builds right out of the box for Linux/MIPS and that's
already good news, given the complexity of the thing and how difficult it
builds for IRIX.
Ralf
next prev parent reply other threads:[~1998-03-06 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-06 16:46 xntp ralf
[not found] ` <Pine.ULT.3.96.980306110037.5679B-100000@cheetah.wsc.edu>
1998-03-06 18:25 ` ralf [this message]
1998-03-06 22:49 ` kernel Ulf Carlsson
1998-03-06 23:56 ` kernel ralf
1998-03-07 21:37 ` kernel Ulf Carlsson
1998-03-07 22:20 ` kernel Oliver Frommel
1998-03-08 9:58 ` kernel Ulf Carlsson
1998-03-07 1:40 ` xntp Trevor Schroeder
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=19980306192514.14435@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=linux-mips@fnet.fr \
--cc=linux@cthulhu.engr.sgi.com \
--cc=tschroed@cheetah.wsc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.