From owner-freebsd-current@FreeBSD.ORG Tue Oct 28 22:30:32 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 06601FB1; Tue, 28 Oct 2014 22:30:32 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 6F2FCE6; Tue, 28 Oct 2014 22:30:31 +0000 (UTC) Received: from pluto.sol.local ([88.74.238.41]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M85r3-1XwuPX0kGv-00vgL8; Tue, 28 Oct 2014 23:30:22 +0100 Message-ID: <545018F9.5020909@gmx.net> Date: Tue, 28 Oct 2014 23:30: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: John Baldwin , freebsd-current@freebsd.org Subject: Re: Mounting ZFS with error 5 failed, since r271963 callout convert References: <544EA961.2090508@gmx.net> <544ECB39.1000507@gmx.net> <201410281328.21798.jhb@freebsd.org> In-Reply-To: <201410281328.21798.jhb@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:1JQGZxAxPFxtBvO1/0W9huAEEjoMVyYR31NN6DJsIWPy/pEj/pp blgE8B9MU8eCii3QIEwr8hCO6ZtjZFqAgOtZkPc+6Bs6xqaKm+eZIIJuLA7h/A30QpBP8mX 1bB5QXGLwYvsmCpht168vAutc2BViRumq/F9GlYIaiFgRaBHVL6z/u4tstE1KnXonOZTeRc YhrCgEyQC5bS544C96/4A== X-UI-Out-Filterresults: notjunk:1; Cc: Ryan Stone 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 22:30:32 -0000 >> 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? > The nvidia driver problem started long before r271963. If I update my CURRENT, non base stuff will be deleted and ports will be completly new installed. The nvidia problem persisted some of these cycles before I gave up. I can test if the problem still exists. But now there is a similar problem with applying kern_cons.c in r271963. I do not know whether these two are related. Please let me know if you want to see some configuration or logs or anything. Thanks, Michael