From owner-freebsd-wireless@FreeBSD.ORG Fri May 16 20:05:57 2014 Return-Path: Delivered-To: freebsd-wireless@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 2D008A6B; Fri, 16 May 2014 20:05:57 +0000 (UTC) Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d: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 C0B5A23A9; Fri, 16 May 2014 20:05:56 +0000 (UTC) Received: by mail-qg0-f51.google.com with SMTP id q107so4950034qgd.38 for ; Fri, 16 May 2014 13:05:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=BoGSO8VQMODqNOzZiJ4YopPNtZDFdWt/Ak/pYRv1vGg=; b=iRvhhyouh0fdq8CrOJYXY+8G6eQBDofAUYdIiFY7TCxx7b+7BS3EUf1HstxzJbM/t4 qGTPnuvySwui2/83GMlFkYn+yBC6tvJ7KaiMMr2JZ1sjoyo5lxfIOOHdDzdM+PmxQjR5 xH1oX5MDnYQmRnThK3v48CNvkWepEx4I/l8E2zPfjqE2MthApEmOOy1Uh+zycE8jOvKb 87z4rQlvdsGyb6tHP5M4lD6IeGLmKqepsO3y9m741fxnSPmd8jGzPXaO8U0c9T9t28xJ 3K1Ipn3giwLlQKSt43I2EyVjC4CL1X+vVhmtEF70wruhqeVX98Q/fdaGxoFG8ReDBSzQ R1sA== MIME-Version: 1.0 X-Received: by 10.229.97.71 with SMTP id k7mr29246238qcn.4.1400270755868; Fri, 16 May 2014 13:05:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.191.201 with HTTP; Fri, 16 May 2014 13:05:55 -0700 (PDT) In-Reply-To: <201405161821.s4GILXit029854@mech-cluster241.men.bris.ac.uk> References: <8FB7D6BF-005A-41A1-9DCE-C8B09EA338EE@FreeBSD.org> <201405161821.s4GILXit029854@mech-cluster241.men.bris.ac.uk> Date: Fri, 16 May 2014 13:05:55 -0700 X-Google-Sender-Auth: qFBMNU3xQU3dEenwFLJDhm-q5Cw Message-ID: Subject: Re: Workaround for "fatal firmware error" iwn(4) problem. From: Adrian Chadd To: mexas@bris.ac.uk, "freebsd-wireless@freebsd.org" Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-hackers@freebsd.org" , =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.18 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: Fri, 16 May 2014 20:05:57 -0000 It's likely part the firmware and pat the driver. Yeah, we need a way to recover from a firmware crash. I and others in the open source community don't have documentation to know what the hell is or isn't permissable with firmware :( Ed - the reason why ieee80211_runtask() doesn't always run is because it can get paused during things like scanning and interface-down things. Your best bet is to create a new taskqueue in iwn and a task that runs on an iwn taskqueue. (And yeah, I really do need to rip out the taskqueue abuse by the net80211 scan code so a scan doesn't stop tasks from running. Grr.) -a On 16 May 2014 11:21, Anton Shterenlikht wrote: >>From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= >>Subject: Workaround for "fatal firmware error" iwn(4) problem. >>Date: Fri, 16 May 2014 20:06:02 +0200 >>To: "freebsd-hackers@freebsd.org" >> >>I've started using FreeBSD laptop and iwn(4) failing at random moments >>like this... > > see also > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/176104 > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/189802 > > BTW, I disabled iwn and tried pccard bwn device instead, > and the errors are gone. Also wireless doesn't disconnect > as it used to with iwn. This is just because I thought > my laptop or setup were to blame. So this is further > evidence that iwn driver is at fault. > > Anton > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"