From owner-freebsd-current@FreeBSD.ORG Fri Jun 13 19:36:40 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B1B155EE; Fri, 13 Jun 2014 19:36:40 +0000 (UTC) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (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 204CE2E45; Fri, 13 Jun 2014 19:36:39 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b13so3199935wgh.35 for ; Fri, 13 Jun 2014 12:36:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=MVTASqCjdJrd83SkekXQy3VuIJcm8Kh6mLRYnMjsbOg=; b=tdt7ALp7vETSnysixKia1otHtxpr7ntwKjhOyktTPRYK3OqoiWFP2Tikf3dS+QwJVi U0G7bPc7OO77qexuxagzlK9X851fEKLs8fxVM64bd7ndtwtqyTO54QcModML0CqUCObP t//4s4gcQ1Xt3LVONYq2JaPP3W84bLBRLiMLB787/tAgDF6tXLSRCjFUwuUU6Gbc/qUj VOow6mpfaBV4hB3CQWuxiqlVyl2VbG7dviOAoF+VHAf67oqlaANC8NxJkN7B5KxPP2WD 5w0PG04Liz+rmbDCxn03yPc4ktN09+//B5V2BGX+U9VKktT9gsUwptmhelg/UUnAA0Az D6lw== X-Received: by 10.181.11.193 with SMTP id ek1mr7498372wid.15.1402688198353; Fri, 13 Jun 2014 12:36:38 -0700 (PDT) Received: from brick.home (adhd245.neoplus.adsl.tpnet.pl. [79.184.159.245]) by mx.google.com with ESMTPSA id y8sm13816684eef.5.2014.06.13.12.36.37 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 13 Jun 2014 12:36:37 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 13 Jun 2014 21:36:35 +0200 From: Edward Tomasz Napiera??a To: David Wolfskill , Adrian Chadd , Stefan Parvu , freebsd-current Subject: Re: iwn driver issue Message-ID: <20140613193635.GC1607@brick.home> Mail-Followup-To: David Wolfskill , Adrian Chadd , Stefan Parvu , freebsd-current References: <20140613112624.bef131c3b84e5e4ad38ed84f@systemdatarecorder.org> <20140613163644.GA1291@brick.home> <20140613165216.GZ1180@albert.catwhisker.org> <20140613175819.GA1180@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140613175819.GA1180@albert.catwhisker.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2014 19:36:40 -0000 On 0613T1058, David Wolfskill wrote: > On Fri, Jun 13, 2014 at 12:34:00PM -0500, Adrian Chadd wrote: > > This isn't this first time this has been reported, right? > > > > I think we may need to back this patch out until it's better resolved. > > .... > > I normally don't spend a huge amount of time in head -- enough to build > it & do a quick smoke-test. So it's certainly possible that it merits > further exploration. And I'm willing experiment, but I cannot test it > while I'm at work (as I don't use the wireless NIC at work -- I use it > almost exclusively while I'm at home (and other places), though). It would be great if you could help me with this. Basically you need to enable crashdumps, as described below, and obtain a backtrace. http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html Just for the record, the easiest way to make iwn firmware panic is to enter ddb (ctrl-alt-esc), wait five seconds and exit it ("c").