Re: Clue on 2.0.33 crashes

Mark Harvey (markh@forcetech.com.au)
Sat, 21 Feb 1998 16:49:18 +1100

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Carsten Gross: "Hang in wait_on_inode with SMP 2.1.87"
Previous message: *Vic* P. Franck: "Can Kernel Compression Code make Sense?"
Maybe in reply to: Camm Maguire: "Clue on 2.0.33 crashes"

Doug Ledford wrote:
>
> Thomas Schenk Z wrote:
> >
> > Which version of xntpd are you running? We never saw this message until we
> > upgraded to xntp3-5.91 and then only after switching to 2.0.32 (when the
> > kernel code changed).
>
> rpm reports:
> xntp3-5.91_export-1
>
> > I asked the author about this message and he said
> > that it is harmless, but my experience tells me otherwise. The other thing
> > I would ask you is whether the machines on which you are running xntpd are
> > SMP or not. I think that the problem I am experiencing with xntpd may be
> > SMP specific.
>
> Nope, these systems of mine are non-SMP systems.
>
> --
>
> Doug Ledford <dledford@dialnet.net>
> Opinions expressed are my own, but
> they should be everybody's.
>

My 2c worth on xntp & lockups.

2.0.33 various intel machines from Pentiums down to 386sx. All run
xntp3-5.92.
No lockups here.

Best regards
Mark Harvey

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

Next message: Carsten Gross: "Hang in wait_on_inode with SMP 2.1.87"
Previous message: *Vic* P. Franck: "Can Kernel Compression Code make Sense?"
Maybe in reply to: Camm Maguire: "Clue on 2.0.33 crashes"