From owner-freebsd-wireless@freebsd.org Mon Jun 20 17:58:22 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 49CCDA7A49A for ; Mon, 20 Jun 2016 17:58:22 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 996081E02 for ; Mon, 20 Jun 2016 17:58:21 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 24718441; Mon, 20 Jun 2016 19:58:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=U48juyM971RVQa2dZ6R1gAkjqrA=; b=t3OBylLmo0FaIq4KsSe0V3wtdbz9 lLToFpbNTt5ZU3bIEvj6Kn2W3ZNWXobtRyTwEzVexEEpAP8KF9oh0gx34XWn0399 CEJ51k6nUVZTv6LhcE9V2x6WHSgV4yDAI4ZpU7+Pqpcl9nG6X45dSiP2/6C8nDGX 2CLiJVis2zUkTOE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; q=dns; s= mail; b=cJ7oQSwMPL2wXZddiG0Uumr4jrmEIg0wv4T6VADJIIZGO2/Ukhb9cF7e evh/dZ+dYgQIdei4C0OzJ8LXsnIB05QqeQRIqax5b/MvLk6Q7BOH0ZD3aNoF/krz 25Rr+cXg7tRLyZuSKOZWqj+5Lx0P+rk0op7JylfhDw0zz4Moyhw= Received: from knuckles.blih.net (ip-54.net-82-216-203.roubaix.rev.numericable.fr [82.216.203.54]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 7daf0f28 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Mon, 20 Jun 2016 19:58:13 +0200 (CEST) Date: Mon, 20 Jun 2016 19:58:13 +0200 From: Emmanuel Vadot To: Ben Woods Cc: "freebsd-wireless@freebsd.org" Subject: Re: [CFT] iwm driver synced with DragonflyBSD Message-Id: <20160620195813.f1de85a52eedcd36c35356ec@bidouilliste.com> In-Reply-To: <20160620174632.GA1234@shinto.woods.am> References: <20160619172035.020eacde012a13c0c5f9b90d@bidouilliste.com> <20160620132224.0d52ff7a9bb9f64bc4a0ffe1@bidouilliste.com> <20160620174632.GA1234@shinto.woods.am> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:58:22 -0000 On Mon, 20 Jun 2016 19:46:32 +0200 Ben Woods wrote: > 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 No it's really panic while cloning the wlan0 interface (probably because of some devd rule, see current process = ifconfig). After reboot a kernel dump should be in /var/crash/, could you do : kgdb /boot/kernel/kernel /var/crash/vmcore.X ? Thanks, -- Emmanuel Vadot