From owner-freebsd-current@FreeBSD.ORG  Wed Nov 26 23:40:29 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B3848F66
 for <freebsd-current@freebsd.org>; Wed, 26 Nov 2014 23:40:29 +0000 (UTC)
Received: from mail.palmen-it.de (stef.palmen-it.de [IPv6:2a01:198:49d:1::1])
 (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 75D343E5
 for <freebsd-current@freebsd.org>; Wed, 26 Nov 2014 23:40:29 +0000 (UTC)
Received: from nexus.home.palmen-it.de ([192.168.99.2] helo=nexus.localnet)
 by mail.palmen-it.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <felix@palmen-it.de>) id 1XtmCB-0002LT-Hc
 for freebsd-current@freebsd.org; Wed, 26 Nov 2014 23:40:27 +0000
From: Felix Palmen <felix@palmen-it.de>
To: freebsd-current@freebsd.org
Subject: Re: iwn(4) crashing when wlan device is brought up, CA-N-6200
Date: Thu, 27 Nov 2014 00:40:23 +0100
Message-ID: <708524702.PpP0DOIPdV@nexus>
User-Agent: KMail/4.14.1 (Linux/3.16.1-ck1; KDE/4.14.2; x86_64; ; )
In-Reply-To: <CAJ-Vmo=uNPBS-HEzm-y1k5HicxQEYXC6ueGPz2iLhGtBXUWvDw@mail.gmail.com>
References: <1734439.MVPFiyHCOv@nexus>
 <CAJ-Vmo=uNPBS-HEzm-y1k5HicxQEYXC6ueGPz2iLhGtBXUWvDw@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-SA-Exim-Connect-IP: 192.168.99.2
X-SA-Exim-Rcpt-To: freebsd-current@freebsd.org
X-SA-Exim-Mail-From: felix@palmen-it.de
X-SA-Exim-Scanned: No (on mail.palmen-it.de); SAEximRunCond expanded to false
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Nov 2014 23:40:29 -0000

Hi Adrian,

Am Mittwoch, 26. November 2014, 09:27:32 schrieb Adrian Chadd:
> Oh! Please file a PR for this.

Done, https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=195433

> This is two problems:
> 
> * the NIC isn't being setup fully correctly - I'll see if i have an
> Intel 6200 in my pile-o-nics;
> * .. and the re-initialise path is slightly broken it seems and it's
> panicing. :)

I thought so, the page fault leading to the panic happens during a re-
initialization attempt. A single PR is still ok? I guess further conversation 
should take place through the PR now ... just in case, if it helps debugging, 
I could build the kernel with full debugging capabilities and provide the 
dumped core.

Thanks for your reply!

BR, Felix