From owner-freebsd-current@FreeBSD.ORG Tue Oct 28 18:26:39 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 3435A9A for ; Tue, 28 Oct 2014 18:26:39 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (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 0A576228 for ; Tue, 28 Oct 2014 18:26:39 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E0A13B980; Tue, 28 Oct 2014 14:26:37 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: Mounting ZFS with error 5 failed, since r271963 callout convert Date: Tue, 28 Oct 2014 13:28:21 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <544EA961.2090508@gmx.net> <544ECB39.1000507@gmx.net> In-Reply-To: <544ECB39.1000507@gmx.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201410281328.21798.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 28 Oct 2014 14:26:38 -0400 (EDT) Cc: Ryan Stone , Michael Schmiedgen 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: Tue, 28 Oct 2014 18:26:39 -0000 On Monday, October 27, 2014 6:46:17 pm Michael Schmiedgen wrote: > 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? So not loading the nvidia driver during boot fixed it? That seems odd indeed. Did you recompile the driver after updating? -- John Baldwin