From owner-freebsd-stable@FreeBSD.ORG Mon Jan 31 18:38:14 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B10216A4D0 for ; Mon, 31 Jan 2005 18:38:14 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADE8343D39 for ; Mon, 31 Jan 2005 18:38:13 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 01D39514F6; Mon, 31 Jan 2005 10:38:12 -0800 (PST) Date: Mon, 31 Jan 2005 10:38:12 -0800 From: Kris Kennaway To: Billy Newsom Message-ID: <20050131183812.GB81428@xor.obsecurity.org> References: <41FE5468.3000804@leadhill.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IrhDeMKUP4DT/M7F" Content-Disposition: inline In-Reply-To: <41FE5468.3000804@leadhill.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: 5.3 STABLE kernel compilation oddity X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jan 2005 18:38:14 -0000 --IrhDeMKUP4DT/M7F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 31, 2005 at 09:53:12AM -0600, Billy Newsom wrote: > I have a similar system to yours, but a dual processor. One thing I see = is=20 > that as the days have gone by since the original 5.3-Release, the SMP cod= e=20 > has had some code changes that have alternately caused crashes or=20 > compile-time errors, at least from my point of view. I am beginning to= =20 > regret using 5.3, but all of the press releases nudged me to believe that= =20 > 5.3 ws ready for live systems. I have to admit that I had problems with= =20 > 4.7 and 4.9, but not like the 5.3-STABLE track. I hope all of this doesn= 't=20 > give FreeBSD a bad reputation, although it might earn it if it continues = to=20 > be so buggy for SMP systems. Having no experience with 5.2, I almost wis= h=20 > I could provide more advice. But perhaps you can get the generic kernel= =20 > off the CD and boot to it to recompile your kernel. >=20 > See this as one documented example: > ftp://ftp.freebsd.org/pub/FreeBSD/ERRATA/notices/FreeBSD-EN-05:03.ipi.asc Err, that's a *fix* to the SMP code, not breakage introduced after 5.3-RELEASE as you claimed above. If you are seeing panics, you must submit appropriate bug reports (see the developers' handbook chapter on kernel debugging), or no-one can possibly help you. Kris --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB/nsUWry0BWjoQKURApaWAKDp8kYfYsPYXQp5iWfBaYnW6vPkzQCgrBj/ 448RR4rMY7PBwEoRVQN1Arw= =X1uc -----END PGP SIGNATURE----- --IrhDeMKUP4DT/M7F--