From owner-freebsd-questions@FreeBSD.ORG Thu Apr 5 15:01:45 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B0B3D16A404 for ; Thu, 5 Apr 2007 15:01:45 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 97D9313C458 for ; Thu, 5 Apr 2007 15:01:45 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5E6E11A4D8D; Thu, 5 Apr 2007 08:01:45 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 98EA35154D; Thu, 5 Apr 2007 11:01:44 -0400 (EDT) Date: Thu, 5 Apr 2007 11:01:44 -0400 From: Kris Kennaway To: m yelle Message-ID: <20070405150144.GA6128@xor.obsecurity.org> References: <20070404231309.GA66183@xor.obsecurity.org> <356784.17129.qm@web63812.mail.re1.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <356784.17129.qm@web63812.mail.re1.yahoo.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org Subject: Re: kernel panic installing 5.4-release X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2007 15:01:45 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 04, 2007 at 08:28:56PM -0400, m yelle wrote: > Because it's an *old* server, and because 5.4-r should > be a mature enough distribution by now that any bugs > which were going to be fixed would already be fixed. Sorry, that's just not how it works :) FreeBSD 6.2 supports the same hardware, and has 2 years of further bug fixes. In addition 5.4 is no longer supported (it is not even the most recent 5.x release!) > I could only find one reference to a problem like this > one, and in that case it was happening in 6.x, which > indicates that whatever the problem is, it hasn't been > fixed. No, it indicates that there was another problem which:=20 * may or may not be the same as yours. "Similar panic string" is no indication of cause. * may or may not be fixed, because "6.x" encompasses several years of releases and bugfixes. > Which implies that it's either considered to be > not a problem by way of an easy workaround, or that > it's not an important problem due to not happening > very often. Either way, an answer to the question at > hand would be much appreciated. Please update to 6.2 and file a bug report if the problem persists. Kris --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGFQ9YWry0BWjoQKURAj8xAKCnETBnx05MEwRAswWEWShZCwezBACfZPh5 MYsc6+0ziZ4Z2Z7M7CXe2Mo= =J35u -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V--