From owner-freebsd-wireless@FreeBSD.ORG Sat Aug 17 22:57:24 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 BFA897CD for ; Sat, 17 Aug 2013 22:57:24 +0000 (UTC) (envelope-from julio@meroh.net) Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 40FBA20D1 for ; Sat, 17 Aug 2013 22:57:23 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id u10so2166068lbi.14 for ; Sat, 17 Aug 2013 15:57:15 -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=KBl0bSD8aaD7MP1MbADJ5dXtRpJJ6HXnWBqhUGRHRrs=; b=JtH/RNUR5XkH8CLlLUga6ULgsB2VUEOwpsRph1PlhnkDKHBrwCjbbgQ73ZfxZjQPej zny4XFLLsxwlBXTl8uiDcT6EyCQ5Wg4Hx50D5ssJnHN2LUrWsP2WhtRGW2H6JarLm7pW CdUJ6wM21L3ki8c1ICZzRJJlZyAC7xk2XH8SzIOV1wIG8y7xH0Qv4lK2FN2onrbschF1 US/m2PkvlZNa46BXXkzvDk4ZSJtvWzJ0VeK9/3FAYF2sXA2t+4IZImyA1d9tWVFLE8Vg 1bJnGG5g7fQvyyC3dFlKHYf2mFj3bcv6KgHwjRDgSbeT4UzmuhYOL9UkwIezSO9cM9Ue XaRA== X-Gm-Message-State: ALoCoQn3SaKGnIy949YBUQ4Os6Pg9u7fs1IJO20HZAjsqUDMzJPLkWr95XuFtlp21zbMCKuBSqF6 X-Received: by 10.112.168.170 with SMTP id zx10mr3705344lbb.0.1376780235718; Sat, 17 Aug 2013 15:57:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.149.2 with HTTP; Sat, 17 Aug 2013 15:56:54 -0700 (PDT) X-Originating-IP: [108.176.158.82] In-Reply-To: References: <201308111650.r7BGo1Qt048071@freefall.freebsd.org> <52099CF4.7050101@meroh.net> From: Julio Merino Date: Sat, 17 Aug 2013 18:56:54 -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: Sat, 17 Aug 2013 22:57:24 -0000 On Wed, Aug 14, 2013 at 1:13 PM, Adrian Chadd wrote: > 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. There is only one KASSERT within _bwi_txeof() mentioning "ring_idx", and that's the line triggering the panic. (And yes, I've verified this... not with a core dump, because I cannot get one, but by putting printfs() around the various KASSERTS that yield this message.) Does that help? -- Julio Merino / @jmmv