From owner-freebsd-stable@FreeBSD.ORG Fri Apr 12 10:17:20 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1938B8DD for ; Fri, 12 Apr 2013 10:17:20 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) by mx1.freebsd.org (Postfix) with ESMTP id BF6551D93 for ; Fri, 12 Apr 2013 10:17:19 +0000 (UTC) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.69) (envelope-from ) id 1UQb2c-0002FW-KN for stable@freebsd.org; Fri, 12 Apr 2013 17:17:10 +0700 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id r3CAHqel070852 for ; Fri, 12 Apr 2013 17:17:52 +0700 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id r3CAHlrJ070842 for stable@freebsd.org; Fri, 12 Apr 2013 17:17:47 +0700 (NOVT) (envelope-from danfe) Date: Fri, 12 Apr 2013 17:17:46 +0700 From: Alexey Dokuchaev To: stable@freebsd.org Subject: Re: fusefs-kmod does not work on 8-STABLE? Message-ID: <20130412101746.GA68687@regency.nsu.ru> References: <20130410052710.GA36137@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130410052710.GA36137@regency.nsu.ru> User-Agent: Mutt/1.4.2.1i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Apr 2013 10:17:20 -0000 On Wed, Apr 10, 2013 at 12:27:10PM +0700, Alexey Dokuchaev wrote: > I've got puzzled with the fact that fusefs-kmod apparently does not on > recent 8-STABLE: it builds and loads, but I don't see normal "fuse4bsd: > version 0.3.9-pre1, FUSE ABI 7.19" like I do on 9-STABLE (installed on the > same laptop with almost identical kernel config). > > The result is that /dev/fuse0 never gets created, and any fuse mount > attempt results in this message: > > fuse: failed to open fuse device: No such file or directory I've traced the problem down a bit, it seems to be due to some weird brokenness of building modules outside the kernel: .ko file loads, but modevent() functions apparently does not execute at all. Also, nvidia.ko can reveal this (or related) bug by spitting messages like this: link_elf: symbol linux_ioctl_unregister_handler undefined This behavior was reported by arundel@ back in 2009 on -current@, but the root cause was never found. http://lists.freebsd.org/pipermail/freebsd-current/2009-September/011975.html http://markmail.org/message/7opthxniqc5ncv6h ./danfe