From owner-freebsd-current@freebsd.org Mon Sep 26 18:05:03 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 10944BEAF8C for ; Mon, 26 Sep 2016 18:05:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (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 C2605C20 for ; Mon, 26 Sep 2016 18:05:02 +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 mail.baldwin.cx (Postfix) with ESMTPSA id 78F9810AF7D; Mon, 26 Sep 2016 14:04:55 -0400 (EDT) From: John Baldwin To: Murthy Bhat Cc: "freebsd-current@freebsd.org" Subject: Re: FreeBSD 11.0-RC1 boot prompt kernel load issue. Date: Mon, 26 Sep 2016 10:29:01 -0700 Message-ID: <30103979.W3ao9sU9hK@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.0-PRERELEASE; KDE/4.14.10; amd64; ; ) In-Reply-To: References: <2592873.DC5MXn4URJ@ralph.baldwin.cx> 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.4.3 (mail.baldwin.cx); Mon, 26 Sep 2016 14:04:55 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 26 Sep 2016 18:05:03 -0000 As I said, the only way I know to debug this is to start adding printfs in various parts of the boot loader to find out which EFI or BIOS call triggers the panic and then trying to infer from that what the BIOS routine might not like. If you think it is disk related, then the sys/boot/i386/libi386/biosdisk.c (for non-EFI) and sys/boot/efi/libefi/efipart.c are good places to start. On Wednesday, September 21, 2016 03:12:05 PM Murthy Bhat wrote: > Hi, > > I checked both FreeBSD 11 RC2 and RC3 latest stable releases. Same issue exists. When loading the kernel from USB pen drive at boot prompt, system gets switched off. > > Could you please help? > > Regards/Ram > > -----Original Message----- > From: Murthy Bhat > Sent: Tuesday, August 30, 2016 8:03 PM > To: 'John Baldwin' > Cc: freebsd-current@freebsd.org; FreeBSD-current@FreeBSD.org > Subject: RE: FreeBSD 11.0-RC1 boot prompt kernel load issue. > > Hi John, > > Thanks for your quick response. > > I did the same exercise on a super micro(X59SRL model) server, to segregate the issue. The same issue is reproduced again. > > So IMHO this may not be the system UEFI firmware issue due to following two reasons. > 1. "load kernel" does not work on 2 different hardware platforms. > 2. On FreeBSD 10.3 and 10.2, both the hardware platforms (HP ProLiant ML110 Gen9 and Super micro X59SRL) work without problem. > > Could you please advise some work around or any other exercise to narrow down the issue. > > Regards/Ram > > > -----Original Message----- > From: John Baldwin [mailto:jhb@freebsd.org] > Sent: Tuesday, August 30, 2016 3:57 AM > To: Murthy Bhat > Cc: freebsd-current@freebsd.org; FreeBSD-current@FreeBSD.org > Subject: Re: FreeBSD 11.0-RC1 boot prompt kernel load issue. > > EXTERNAL EMAIL > > > On Monday, August 29, 2016 05:37:57 PM Murthy Bhat wrote: > > Thanks for the response. > > > > It is UEFI boot. As such there is no stack dumped on the console > > during crash. System restarts from the FreeBSD boot prompt without any > > message on the console. Still I have a picture where monitor goes off > > during data load. PFA(sorry for the flash) > > Ugh. I don't have a good suggestion on debugging this besides adding printfs to the EFI loader code and/or moving an infinite loop around in the code to narrow down exactly when it resets. It is quite possibly specific to the EFI firmware on your machine (at least, reproducing the issue might be). > > > Regards/Murthy Bhat > > > > -----Original Message----- > > From: John Baldwin [mailto:jhb@freebsd.org] > > Sent: Monday, August 29, 2016 10:52 PM > > To: freebsd-current@freebsd.org > > Cc: Murthy Bhat ; > > FreeBSD-current@FreeBSD.org > > Subject: Re: FreeBSD 11.0-RC1 boot prompt kernel load issue. > > > > EXTERNAL EMAIL > > > > > > 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 > > > -- > John Baldwin -- John Baldwin