From owner-freebsd-wireless@FreeBSD.ORG Tue Jan 28 22:34:45 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 2721F7F2 for ; Tue, 28 Jan 2014 22:34:45 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D2E4010FE for ; Tue, 28 Jan 2014 22:34:44 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id e9so1632601qcy.1 for ; Tue, 28 Jan 2014 14:34:44 -0800 (PST) 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=nILmHddoKVdayJSgFmoaErF6+b2HGmoh/pHrm3QAcnc=; b=Fzkb1A/cLYUBQ8zqZVmZo98YqkrjtTqcyf/I4c8WCAAb6B363I19jXQXi6KjTuDdDs sLJ85D4qNQbsbolTBbENSzkv7e3hdkeldi8pmg2OWxkEIpTET/TFTKe9adsIs9q6Jueg Dnk3tQm09lg9PiJJDAJs9GDViv3FSV5DCYHZw+SrYdmylZ6Z5d2EO8lKdsTEjHv2JKGs e1O2W2AFgI2TNO/sQXnmz0vr4kHu+cIVYralYeXTBgGkwQ7LsAqNdcs/0sR9Hfz5EQrC lRHDZ+qRkDz0Pivg3JqcRMrPWDxzYht3Wy5RiA6syAwBwR3xh6O2cuKcRjf6M3blKuyF TQVQ== MIME-Version: 1.0 X-Received: by 10.224.74.129 with SMTP id u1mr6711630qaj.49.1390948483979; Tue, 28 Jan 2014 14:34:43 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Tue, 28 Jan 2014 14:34:43 -0800 (PST) In-Reply-To: References: Date: Tue, 28 Jan 2014 14:34:43 -0800 X-Google-Sender-Auth: HMUDftrVQt7lIYHzLyhfTj4ULPI Message-ID: Subject: Re: FreeBSD 10.0: hostapd crash with Ralink 3070 From: Adrian Chadd To: Pedro Flynn Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 28 Jan 2014 22:34:45 -0000 Ok, fire up kgdb # kgdb /boot/kernel/kernel /var/crash/vmcore.0 then (gdb) list * (0xffffffff809b1163) (.. that's the "instruction pointer" at the time of the panic.) I bet it's iv_bss. -a