From owner-freebsd-stable@freebsd.org Wed Aug 9 15:05:38 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 4E06DDCF1E8 for ; Wed, 9 Aug 2017 15:05:38 +0000 (UTC) (envelope-from raf@rafal.net) Received: from fallback-in2.mxes.net (fallback-out2.mxes.net [216.86.168.191]) (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 08132754EE for ; Wed, 9 Aug 2017 15:05:37 +0000 (UTC) (envelope-from raf@rafal.net) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by fallback-in2.mxes.net (Postfix) with ESMTP id 3404A2FD7E0 for ; Wed, 9 Aug 2017 11:05:30 -0400 (EDT) Received: from [172.20.10.2] (unknown [213.233.150.76]) (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 8232F22E2B7 for ; Wed, 9 Aug 2017 11:05:17 -0400 (EDT) From: Rafal Lukawiecki Mime-Version: 1.0 (1.0) Date: Wed, 9 Aug 2017 16:05:15 +0100 Subject: Re: Is it worth waiting for AMD Opteron X3000 support in FreeBSD? Bug [221350] Message-Id: <7B1C3028-EBD7-4671-AB6E-CD7EB72F99DF@rafal.net> References: <20170809130804.GG81427@home.opsec.eu> In-Reply-To: <20170809130804.GG81427@home.opsec.eu> To: freebsd-stable@freebsd.org X-Mailer: iPad Mail (14G60) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 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 15:05:38 -0000 Many thanks, Kurt, for pointing out those other 3 bug reports. On the face o= f it, they look different to mine. In my case, and in the case of another us= er who has reported this on the FreeNAS forum (affecting FreeBSD 11.0), the b= oot progresses past the point shown in the 3 reports that you have suggested= , by perhaps another 5-10 seconds. Kindly have a look at the screenshots I h= ave submitted within the bug report here: https://bugs.freebsd.org/bugzilla/= show_bug.cgi?id=3D221350 ...and you may notice that the boot process hangs just after it has displaye= d messages about pci0 acpi. The verbose boot (screenshot also above) shows t= hat the boot process seems to have just identified memory modules on pcib0. T= he remaining screenshots show kernel panics when I tried to disable ACPI. I will test the boot with the other releases of FreeBSD as suggested by Miro= slav Lachman, later today, and I will report back here, then I suppose I can= make a decision if to move this discussion to freebsd-current, as recommend= ed by @wishmaster. I apologise for confusing which list to keep reporting to= . Many thanks, Rafal Lukawiecki=