From owner-freebsd-current@FreeBSD.ORG Mon Oct 27 22:46:27 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A087622D for ; Mon, 27 Oct 2014 22:46:27 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 37860F7A for ; Mon, 27 Oct 2014 22:46:26 +0000 (UTC) Received: from pluto.sol.local ([188.102.183.116]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MSp1l-1XZEQ03pZt-00Rpqp; Mon, 27 Oct 2014 23:46:18 +0100 Message-ID: <544ECB39.1000507@gmx.net> Date: Mon, 27 Oct 2014 23:46:17 +0100 From: Michael Schmiedgen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ryan Stone Subject: Re: Mounting ZFS with error 5 failed, since r271963 callout convert References: <544EA961.2090508@gmx.net> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:UdiIOsQeGpHTIV7Co7a5ylMJm9+f0Q4SskUN1OAuKM1Me62O5SN ATnS/YcpAxqzjTQLhK+6KoaAGcfwxOEL4GS6wtRKkmpfVIluU5yhOI47YYNIji6WN4947yQ XI5aeuebVGtbIi51ApSDwrKNm3AVF0q9K/XePRKjaVuQEyxEapbsynQX8SPtk4/xzngxmpO TcQMCyHjkcVMXV3WVGPnQ== X-UI-Out-Filterresults: notjunk:1; Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 27 Oct 2014 22:46:27 -0000 On 10/27/2014 22:29, Ryan Stone wrote: > On Mon, Oct 27, 2014 at 4:21 PM, Michael Schmiedgen wrote: >> Hi List, >> >> my ZFS does not mount. I bifurcated to r271963 that >> does not work anymore. The commit seems not directly >> related to ZFS, but is rather a conversion from timeout(9) >> to callout(9). >> >> After booting the kernel it drops to the mount prompt, >> stating that ZFS cannot be mounted because of 'error 5'. >> >> Any hints? Can I provide some more information? >> >> Thanks, >> Michael > > The changes to the 3 files there look to be independent, so can you > narrow this down further by applying the patch to only a single file? > Of those three only ACPI looks like it could affect ZFS or disks, so > this will be the patch to try first: > > https://svnweb.freebsd.org/base/head/sys/dev/acpica/acpi.c?view=patch&r1=271889&r2=271963&pathrev=271963 > > If you can get a verbose boot log from the machine that would be > helpful, but you'd need a serial console to capture that. > I applied first acpi.c, then atkbd.c and at last kern_cons.c that triggered the error. https://svnweb.freebsd.org/base/head/sys/kern/kern_cons.c?r1=271963&r2=271962&pathrev=271963 In previous months I had already the same problem with ZFS if nvidia driver was loaded via /boot/loader.conf. It triggered the same error. So I loaded the driver on demand with kldload after login and everything (X + stuff) worked fine. Very strange... Does anyone have a clue what is going on here? Thanks, Michael