Date: Wed, 27 Aug 2014 19:14:41 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 144234] [zfs] Cannot boot machine with recent gptzfsboot code [regression] 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-144234-3630-d0zAfZI0EL>