From owner-freebsd-stable@freebsd.org Wed Aug 9 17:40:30 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB350DD1F78 for ; Wed, 9 Aug 2017 17:40:30 +0000 (UTC) (envelope-from raf@rafal.net) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7E2A7E63B for ; Wed, 9 Aug 2017 17:40:30 +0000 (UTC) (envelope-from raf@rafal.net) Received: from lucy.glencottage.net (unknown [86.40.118.125]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D37B9509B8; Wed, 9 Aug 2017 13:40:27 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350] From: Rafal Lukawiecki In-Reply-To: <598B0A0C.1040008@quip.cz> Date: Wed, 9 Aug 2017 18:40:25 +0100 Cc: artemrts@ukr.net Content-Transfer-Encoding: quoted-printable Message-Id: <3D6F0A37-6C88-42E7-B9D9-8EBB89483471@rafal.net> References: <598B0A0C.1040008@quip.cz> To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2017 17:40:30 -0000 Following suggestion by Miroslav Lachman I have tested a few other = releases of FreeBSD to see if this issue still persists, and if it was = perhaps a regression. Unfortunately, in all the tests, 9.3-12.0-CURRENT, = I get exactly the same error. The initial boot stops after displaying = messages about ACPI or pcib0 memory detection. To be precise, these are the versions that I have just tested, in all = cases having validated the integrity of the download: FreeBSD-9.3-RELEASE-amd64-memstick.img FreeBSD-11.1-RELEASE-amd64-memstick.img FreeBSD-11.1-STABLE-amd64-20170807-r322164-memstick.img FreeBSD-12.0-CURRENT-amd64-20170807-r322167-memstick.img I have updated the bug [221350] description at: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221350 Please advise me @wishmaster, and anyone else, if in your opinion I = should start a new discussion on another, more appropriate FreeBSD = mailing list. Thank you for your kind help.=