From owner-freebsd-hackers@freebsd.org Mon Dec 5 13:43:05 2016 Return-Path: Delivered-To: freebsd-hackers@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 3F622C66F52 for ; Mon, 5 Dec 2016 13:43:05 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05F551E43 for ; Mon, 5 Dec 2016 13:43:05 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-io0-x22b.google.com with SMTP id j65so596039680iof.0 for ; Mon, 05 Dec 2016 05:43:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yMNJwq65JsVow6xXWZvAtjKzeMfYxsooZPXLq8pTjRE=; b=mAcKHYoqC6UIBLqd0WqwOAQJNKI1aTgr+zrRYN+6jjurwB/uMO2YC6oyQIBB9sxEfQ i+51G9m/6PxTQnQ3LuaV7zl3YS0VCYJCdzyn9hHI52AAHgJ6sdidIgPbfvPHIJQCBkH7 RJce68gZ+og8BVexdpeS7Z+alaQJSfTqE249R2v08yNVmPEhMBbNZSobntWCGqGKCF/Q 5o8+otWn6lTTQuryYZKocLpDWtib4BU4D7cyO2rr9y9BvPPwTpShRWMAnP5rlTasLJ8n 5IU47M3PyQpCvjYVMTyau+wGLEFZ4F+cULh8ZMJoRBcciFIiMK7kqjp5TzsOk0gLpURo JX0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yMNJwq65JsVow6xXWZvAtjKzeMfYxsooZPXLq8pTjRE=; b=O0t4cHX8Hn/onVZzby9VM1SJSc67ETdnRODo9kYwIsJTlxSVHM0PlbVjAqfDw7XFwJ yx5joeE0bSQ8Q2S6dlYOuPVRnCnBxJgXCu7xopQW4oe6OtwFF6lu9oUFTRZFptCWwBkk zCPM3WO9k8I7dHYqqZtiN7wKysbq124qyjXinRA/1MYfdqXAO4V0K14uycfQvxh7743r JdkQ0CH7UKhowtdiiXTuUcci3H6bOmPl/6zAiEVmDh5q/igMnFh+VSQlURdOmHOG8LJr KchNbLyyLYVRjkNR62yvF3fukwD71g7vTaV73TrXymQV091e6x9nsSsI8rAQzuAxMcI0 IjJA== X-Gm-Message-State: AKaTC00YB5No89ae9oav3alyVyfJkeysWmKNB/1f36yeVJgPejYa9Gy2r1kwdhtgPIQ5kIzO0wfSNIUwVBxxCQ== X-Received: by 10.107.57.131 with SMTP id g125mr18457410ioa.108.1480945384327; Mon, 05 Dec 2016 05:43:04 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.136.197 with HTTP; Mon, 5 Dec 2016 05:43:03 -0800 (PST) In-Reply-To: References: <675cb468-f599-a31b-a82c-c0f892136cfc@metricspace.net> From: Ben Woods Date: Mon, 5 Dec 2016 21:43:03 +0800 Message-ID: Subject: Re: CFT EFI Boot Refactoring To: Eric McCorkle Cc: freebsd-hackers@freebsd.org X-Mailman-Approved-At: Mon, 05 Dec 2016 14:40:40 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2016 13:43:05 -0000 On 4 December 2016 at 10:59, Eric McCorkle wrote: > You don't have a UFS filesystem anywhere, so we can rule that out. It > might be tsoome's bug, and it might just be that the bug is sporadic, > which would explain why I'm not seeing it on my setup with a dosfs. > > The only other obvious commonality between you and tsoome that doesn't > overlap my setup is multiple ZFS datasets, or ZFS data vdevs (mirrors, > stripes, etc) spread across multiple disks (my setup only has a log and > a cache on the ssd). > > > Here's what I'll do. I'll create an "extra_logging" branch off of > efize_new in my github repo, wherein I'll add a bunch of extra logging > into the detection process. It ought to be enough to print out device > paths and filesystem drivers just before it tries them. Ok, I have tested with the extra_logging branch, and can report that the text on the screen at the time of the hang was: >> FreeBSD EFI boot block Loader path: /boot/loader.efi Initializing modules: FS BackendProbing all handles for ZFS Done Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85bff18 Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85bfc18 Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85bf998 Probing all filesystems Probing dosfs _ Following that, I tried a combination of the old (unmodified) BOOTX64.EFI with the new (modified) files in /boot/. This produced the following output on the screen before it also hung: >> FreeBSD EFI boot block Loader path: /boot/loader.efi Initializing modules: ZFS UFS Probing 10 block devices............* done ZFS found the following pools: zroot UFS found no paritions Consoles: EFI console Probing all handles for ZFS Done Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85c9718 Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85c9418 Binding SIMPLE_FILESYSTEM_PROTOCOL to 0xb85c9198 Probing all filesystems Probing dosfs _ Hope this is helpful for debugging this issue. Note that once again I did NOT run any command to update my freebsd-boot partition (such as gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada1). Is this required? Regards, Ben -- From: Benjamin Woods woodsb02@gmail.com