From owner-freebsd-current@freebsd.org Mon Aug 29 17:29:15 2016 Return-Path: Delivered-To: freebsd-current@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 539AEBC71AA for ; Mon, 29 Aug 2016 17:29:15 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2470DF1 for ; Mon, 29 Aug 2016 17:29:15 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E103BB962; Mon, 29 Aug 2016 13:29:12 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Cc: Murthy Bhat , "FreeBSD-current@FreeBSD.org" Subject: Re: FreeBSD 11.0-RC1 boot prompt kernel load issue. Date: Mon, 29 Aug 2016 10:22:23 -0700 Message-ID: <1718101.L4sIdq1KVZ@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.3-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 29 Aug 2016 13:29:13 -0400 (EDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2016 17:29:15 -0000 On Wednesday, August 24, 2016 01:35:08 PM Murthy Bhat wrote: > > Hi, > > This is regarding issue faced during OS(FreeBSD 11.0-RC1) installation on the storage behind our smartpqi storage controller. Are you using EFI or legacy boot? Also, can you capture a screenshot of the crash messages? If it is not EFI, we probably crashed in the BIOS routines used to read data from the USB drive. It may be a BIOS bug (which isn't easily fixable), but we would need the register dump from the crash to figure anything out. -- John Baldwin