From owner-freebsd-wireless@FreeBSD.ORG Mon Aug 12 03:02:43 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9F457E1 for ; Mon, 12 Aug 2013 03:02:43 +0000 (UTC) (envelope-from julio@meroh.net) Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 264B72532 for ; Mon, 12 Aug 2013 03:02:42 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id t13so4395568lbd.2 for ; Sun, 11 Aug 2013 20:02:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ImpO+jJ1wrqqKYE32Q+7HO3w/zEFBZnSUuWOOT0vEOc=; b=fR0HDkWr9qgnnMW+9HbAeAstDYU9+hvwuD5oOvtYFqAm0dbshR4bRE66MRxJDn4Bqy cm2RCx5P27IffXzB6Sg36Rvaz3h4l+R4A5FeXk69S8+b+YcoW68iFQceoCFkIn6U789B xaJit8Oj48d22/TYVJ5l2jyI3hl1O8483GZ1zWq9YBtlpBWLmXCMkQE4sKtS+gbrzhbJ StdaCnmQL5u0FPbV8F722bGE/YHRUzcCoxMkLM5jjxIe+tq8b5La9wy+8KAlGHW9TuK2 3HU9dElPwGS5j3pBSTMU2jDSnfQ26oGESr8pWVIYAz7YPeiE6Sy+GZNOcIidG/ggntL+ dnDQ== X-Gm-Message-State: ALoCoQnBGPNVJ1amSIhkc1mOYPDonv54GSia9xD55MoJvvdyIKE+1gUHZbe48cxZFuTQeEf0mvL5 X-Received: by 10.152.170.197 with SMTP id ao5mr4793681lac.35.1376276555026; Sun, 11 Aug 2013 20:02:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.149.2 with HTTP; Sun, 11 Aug 2013 20:02:14 -0700 (PDT) X-Originating-IP: [108.176.158.82] In-Reply-To: References: <201308111650.r7BGo1Qt048071@freefall.freebsd.org> From: Julio Merino Date: Sun, 11 Aug 2013 23:02:14 -0400 Message-ID: Subject: Re: kern/181100: [bwi] Turning up bwi0 crashes / deadlocks the kernel To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 12 Aug 2013 03:02:43 -0000 On Sun, Aug 11, 2013 at 1:07 PM, Adrian Chadd wrote: > Hi! > > THanks for the report! Hi Adrian, Thanks for getting back to me so quickly. > This is my fault. But, is bwi actually doing 11n rates? I don't know. Is there a way to tell for sure? This machine is from ~2005 so I don't think so, but Wikipedia claims that work on 11n started in 2002... > On 11 August 2013 09:50, Julio Merino wrote: > >> bwi0: firmware rev 0x0127, patch level 0x000e >> panic: rate 130 is basic/mcs? > > See, that's just odd. If it's a non-11n (MCS) rate, then it should be > 2x the speed, which is 65MBit - which is odd, as that looks more like > an MCS rate speed than what the NIC should do. But is that related? The crash / freezes seem due to a locking issue. >From a very quick look at the code, the ioctl handler is holding the bwi mutex and then calls firmware_get, which goes to sleep possibly waiting for the disk. > Can you get a crashdump? Sure, but any hints at how? When the system enters kdb, I type "panic" as described in section 10.4 of the guide... and the system immediately reboots, without dumping core. Thanks, -- Julio Merino / @jmmv