From owner-freebsd-wireless@freebsd.org Mon Jun 20 17:46:37 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 528EEA7A1E5 for ; Mon, 20 Jun 2016 17:46:37 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DA16F1A0D for ; Mon, 20 Jun 2016 17:46:36 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id c82so12898745wme.3 for ; Mon, 20 Jun 2016 10:46:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=RQlTiEh2axNCsTttPGuNi0sB69yIofo9O0i/TrYQ5+c=; b=OXEEq/j+hWojZdJTzPV23Rgapk4Lf4mhPuVWdD3bLX57XvFq2G9IxyXEym9dltYbvP mtLkMI4mcG8d3dNsypRjcGuGbcFGqyZHOT/wJP5VVjr0n8Fbz6ymIQkMbeUs5I2EOnZZ ltO1edmBEsKOs1UVKYZsUWsnY1wx/wyzAVlLAvspLpVecFndTsRrJ7O7dPj/zICkq1gL qUZPiFxMF5A7CJSxUAajRSrovUfIItxko4cT5X9SviqHJzUmIyz+0+fhyZc3ke3i7inY ihlec6aDytu1974c91DrVWmC1qDPYwYPao3/hu/+yae5MXpLMBHXkpX54totLljZT9Tm nzDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=RQlTiEh2axNCsTttPGuNi0sB69yIofo9O0i/TrYQ5+c=; b=lwKxQN6vM3/Z2kNdhb69X8EVa3GdxYztm9gZAKsaWxCK9CieS8IO6/83pnxLTjTbTb jMXrCImlEmVUgzgGfmFTUCQP5+8mHj6H90kzW2j98oGpf8I9taRQQKn6Ls1dv/VwqPMO lofh6mV3vYoRIDawH+DlUBIqtbAZ9UQAPDLbGeY0n1JY76GlnoY+XR41UL8I3qyLeLnI y5thFZpBo/lYgvF6S3QmRlCSl2KXkEefYuZfB1i5sppjNfFGH81sBquZLT9L79f4HhIH fAdajEQAqbjAcAzoDp0nb40eM/PSX85za5/BfZP11jQ1UAhHL81SKFAsMEQYHF9rIs77 KZWA== X-Gm-Message-State: ALyK8tLfeYTlOikh/J4Mo0bRc02vNANChYJnV0SDeoNWV1fy6rsrG0lOdz9HfVTdFugLEA== X-Received: by 10.28.21.140 with SMTP id 134mr12849631wmv.50.1466444794831; Mon, 20 Jun 2016 10:46:34 -0700 (PDT) Received: from shinto.woods.am (LFbn-1-7074-147.w90-116.abo.wanadoo.fr. [90.116.243.147]) by smtp.gmail.com with ESMTPSA id f196sm9414306wmg.15.2016.06.20.10.46.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Jun 2016 10:46:33 -0700 (PDT) Date: Mon, 20 Jun 2016 19:46:32 +0200 From: Ben Woods To: Emmanuel Vadot Cc: "freebsd-wireless@freebsd.org" Subject: Re: [CFT] iwm driver synced with DragonflyBSD Message-ID: <20160620174632.GA1234@shinto.woods.am> References: <20160619172035.020eacde012a13c0c5f9b90d@bidouilliste.com> <20160620132224.0d52ff7a9bb9f64bc4a0ffe1@bidouilliste.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160620132224.0d52ff7a9bb9f64bc4a0ffe1@bidouilliste.com> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2016 17:46:37 -0000 On Mon, Jun 20, 2016 at 01:22:24PM +0200, Emmanuel Vadot wrote: > On Mon, 20 Jun 2016 12:02:26 +0200 > Ben Woods wrote: > > > Upon reboot I got a kernel panic after it loaded the module. I took photos > > of my screen at the debug console, which you can find at the link below. If > > there is a way to get a better output for debugging, please let me know. > > http://imgur.com/a/TJ7i5 > > It seems that it kernel panic when creating the wlan0 interface. > I guess that the modules are loaded by the loader ? (i.e. in /boot/loader.conf) > > Could you test not loading them by the loader but by manually after login ? > > kldload iwmXXXXfw.ko && kldload if_iwm > > Then restart the netif service (or create the wlan0 directly). > > -- > Emmanuel Vadot Hi Emmanuel, Whilst I agree the screenshot looks like the failure occurs whilst creating the wlan0 interface, it in fact occurs when loading the if_iwm module. I have tested by stopping the netif service and then loading the modules manually, and you can see the screenshot here: http://i.imgur.com/2ftzhQa.jpg I never got a chance to restart netif service. Regards, Ben -- From: Benjamin Woods woodsb02@gmail.com