From owner-freebsd-fs@FreeBSD.ORG  Wed Aug 27 19:14:42 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2FF8BD3F
 for <freebsd-fs@FreeBSD.org>; Wed, 27 Aug 2014 19:14:42 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 166F83D79
 for <freebsd-fs@FreeBSD.org>; Wed, 27 Aug 2014 19:14:42 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7RJEf2E016915
 for <freebsd-fs@FreeBSD.org>; Wed, 27 Aug 2014 19:14:41 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 144234] [zfs] Cannot boot machine with recent gptzfsboot code
 [regression]
Date: Wed, 27 Aug 2014 19:14:41 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 9.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jhb@FreeBSD.org
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-144234-3630-d0zAfZI0EL@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-144234-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-144234-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Aug 2014 19:14:42 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234

John Baldwin <jhb@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jhb@FreeBSD.org

--- Comment #5 from John Baldwin <jhb@FreeBSD.org> ---
Created attachment 146387
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146387&action=edit
extra_debug_info.patch

Please try this patch.  It will not fix the problem, but it will provide more
details about the request that fails.  Error code 1 from the BIOS is roughly
equivalent to EINVAL.  This will hopefully dump enough details that we can
figure out the issue.  Given that the reporter claims the issue cropped up when
we started letting gptboot use memory above 1MB, my guess is that something in
ZFS is doing I/O using a buffer allocated via malloc().

Note that the biosdisk.c code in the loader has more complicated logic to use
bounce buffers to ensure that all I/O is done in a lower memory range. 
Probably this needs to be ported to drv.c for gptboot/gptzfsboot.

-- 
You are receiving this mail because:
You are the assignee for the bug.