From owner-freebsd-fs@FreeBSD.ORG Fri Sep 12 07:18:31 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42D7080 for ; Fri, 12 Sep 2014 07:18:31 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC7605F6 for ; Fri, 12 Sep 2014 07:18:30 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id p9so363854lbv.10 for ; Fri, 12 Sep 2014 00:18:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=76mmBmAjRut9P/F/PAQn5CAqd8c/3ZVio8j4SV614Ao=; b=GihNBGN72dP6/HzXjvVcve/mjvgR9qS/dXJPUFpb+Lkts7LcMQftw4uRcCmowHi2BQ 1VocJV4FqTrmeU6R8CNXFn0fK3/5WWtr7+s6exxDjJ22xOpQATyXiRGC+2CUnra8za8C 9KvtzFm0zQEA1V6DXaFZtyWUoR8yaoVI0lD6F26vwND6YRr22cWP3Rx5OBXAR8YmLBZl HX6U8omt+tUDQFzx8MVF12oyGy9HPXQFdg55UKeS/y4bxp/BGSo1cWfrWwWSk5PExljX JzcZLyaie1XJXkkyJPX/IgRE3jgxUxeR7iiSp5UramN9/XvYPau3M3ladnvLj8EX2pg6 dv0Q== X-Received: by 10.152.7.8 with SMTP id f8mr6571798laa.27.1410506307178; Fri, 12 Sep 2014 00:18:27 -0700 (PDT) Received: from pc5.home (abws48.neoplus.adsl.tpnet.pl. [83.8.242.48]) by mx.google.com with ESMTPSA id ue1sm969869lac.48.2014.09.12.00.18.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 12 Sep 2014 00:18:26 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 12 Sep 2014 09:18:24 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Michael Dexter Subject: Re: iscsi_initiator.ko failure on 10.0 snapshot Message-ID: <20140912071824.GA4692@pc5.home> Mail-Followup-To: Michael Dexter , freebsd-fs@freebsd.org References: <54122225.8070502@callfortesting.org> <54122E52.1050202@callfortesting.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54122E52.1050202@callfortesting.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2014 07:18:31 -0000 On 0911T1620, Michael Dexter wrote: > > Hello, > >I am attempting to load the iscsi_initiator.ko kernel module on the > >FreeBSD-10.1-PRERELEASE-amd64-20140907-r271243-memstick.img snapshot and > >get an error with the following in /var/log/messages: > > > >... kernel: >>> iscsi_start: iscsi_initiator: make_dev_credf failed > >... kernel: module_register_init: MOD_LOAD (iscsi_initiator, > >0xffffffff82e43000, 0) error 17 > > I have found that this error appears if one loads iscsi.ko before > iscsi_initiator.ko. After the error, iscsi.ko appears to be loaded > but not usable. Unloading iscsi.ko will allow iscsi_initiator.ko to > load but trying iscsi.ko will result in the error. > > Both appear to create /dev/iscsi when loaded > > Is this the expected behavior? The fact that both use the same device node is expected, yes. Two other things you've mentioned are not, though: the fact that iscsi.ko ends up being not usable, and ctld panics. Can you show the exact command sequence that leads to the first problem, ie iscsi.ko being unusable, even though it's loaded? Do you have a backtrace for ctld panics? Thanks!