Last friday I upgraded to the (then) latest 3c59x.c dirver
(v0.49J-smpcheck 2/12/98). The machine stayed up fine until last
night (really only three working days), when I rebooted it to run
some diagnostics on HD and RAM. Did not find any problems with
the HW: moved root to the second disk after running a couple
of badblocks on that one and the running badblocks on the original
HD. I also ran memtest86 on the RAM. It did not find any problems
but might not have as the the version I had (1.3) does not support
my ECC RAM.
I also disabled the PCI_OPTIMIZE and SKB configuration options.
I need masquerading.
This morning I happened to experiment with xntpd (xntp3-5.92) on
the machine (before I read the e-mails about the potiential
problem). The machine reset about one hour later (no xntpd running
at the time).
I don't use gated.
So no still no clue where the problem is. I might throw out the
3C905 and replace it with another card, but won't be able to
do that for a couple of days.
Patrick
On Fri, 20 Feb 1998, 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.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu