From owner-freebsd-wireless@FreeBSD.ORG Wed Aug 14 17:13:52 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 20BA892A for ; Wed, 14 Aug 2013 17:13:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A1B5E284F for ; Wed, 14 Aug 2013 17:13:51 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u55so7935975wes.41 for ; Wed, 14 Aug 2013 10:13:49 -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=hpBFcctP4pxjpM6HknTwNzt8wBSwYxQryA3FoFeB4Zo=; b=n0reFxuf+J9gbXgMIJyKYm653/Kjz4BQy2cpar5ZGW0sQGLKxCFF8IJyCZek6lLhxH QsPx0yAZDSL6BVTu39QjbGlnj458/LjUGtLmapnjJHAOEjiJJjMNqXBNdb4GBehLOVUH iAwP1CFaNRTMqzg+678iUKk9FnjHjAWRuQe+osBXSluTg6rUZ0+D+PuqFaBWqdtAJJ2f 7ToySkHl+GyQOXuvYMRDqz4UaCW9DY+yzqIyLrBpkbqxgVe2DTZbJg5s5jZG9eKpEfmw Ml1vB+H4JpKRxPXm+QVk2GXoMKEV4GWcifGoZmZDYkNcidlzcPfPoIDDae5BFv6rT610 06Tw== MIME-Version: 1.0 X-Received: by 10.180.211.206 with SMTP id ne14mr6846859wic.30.1376500429594; Wed, 14 Aug 2013 10:13:49 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.116.136 with HTTP; Wed, 14 Aug 2013 10:13:49 -0700 (PDT) In-Reply-To: References: <201308111650.r7BGo1Qt048071@freefall.freebsd.org> <52099CF4.7050101@meroh.net> Date: Wed, 14 Aug 2013 10:13:49 -0700 X-Google-Sender-Auth: fga-tmcRsF1qqMEbHfe0rbAL5RE Message-ID: Subject: Re: kern/181100: [bwi] Turning up bwi0 crashes / deadlocks the kernel From: Adrian Chadd To: Julio Merino Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Wed, 14 Aug 2013 17:13:52 -0000 Hi, Can you please work with Justin to figure out the IP of that panic inside _bwi_txeof(), and then map it back to a line number? I've no idea where the panic is actually triggering. Thanks, -adrian On 13 August 2013 19:45, Julio Merino wrote: > On Tue, Aug 13, 2013 at 5:58 AM, Adrian Chadd wrote: > > Hi! > > > > Please update to the latest -HEAD and try again. > > No luck. It gets a bit further now (ifconfig wlan0 up returns to the > shell) but then panics: > > panic: ring_idx 0 > cpuid = 1 > KDB: stack backtrace: > kdb_backtrace > vpanic > kassert_panic > _bwi_txeof > bwi_txeof_status32 > bwi_intr > intr_event_execute_handlers > ithread_loop > fork_exit > fork_trampoline > > (blindly typed while reading from kdb) > > -- > Julio Merino / @jmmv >