Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Jul 2001 22:03:36 -0700
From:      "Eric Parusel" <lists@globalrelay.net>
To:        "Shawn Ramsey" <shawn@cpl.net>, <stable@freebsd.org>
Subject:   Re: Crashing every two hours!
Message-ID:  <003e01c11659$7e603820$0e944c18@cns>
References:  <20010726215545.A10382@cpl.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Well, If I were you I'd rather try RELENG_4_3 , since this tag
includes security fixes (including the telnetd fix)...
I'm running RELENG_4_3 on 12 boxes (all non-SMP, though) with no
problems...  (some "plain" SCSI and some hw RAID 1 or 5)

Eric Parusel


----- Original Message -----
From: "Shawn Ramsey" <shawn@cpl.net>
To: <stable@freebsd.org>
Sent: Thursday, July 26, 2001 9:55 PM
Subject: Crashing every two hours!


> I just upgraded one of our servers from 4.1.1. That server had never
> crashed, or even needed to be rebooted. We just upgraded it to
4.3-Stable.
> It was CVSupp'd around 10:00am yesterday. The world built w/o a
hitch and no
> errors during installation. Now, about every 2 and half hours, the
system is
> panicking. :( This is the error it gets :
>
> panic: vm_fault fault on nofault entry, address d0b24000
>
> I am about ready to try downgrading to 4.2-RELEASE. Will this be a
problem?
> Or does anyone know if telnetd in 4.1.1 can be patched against the
recent
> root exploit? This is the worst I have ever seen a FreeBSD machine
act...
> especially when the previous released OS had never crashed or even
hippoced
> once.
>
> Thanks for any insight...
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003e01c11659$7e603820$0e944c18>