From owner-freebsd-wireless@freebsd.org Tue Mar 8 13:29:51 2016 Return-Path: Delivered-To: freebsd-wireless@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB560AC7027 for ; Tue, 8 Mar 2016 13:29:51 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::107]) by mx1.freebsd.org (Postfix) with ESMTP id BA678B1D for ; Tue, 8 Mar 2016 13:29:51 +0000 (UTC) (envelope-from eric@metricspace.net) Received: from [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9] (unknown [IPv6:2001:470:1f11:617:8fe:6a13:797b:e9c9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id 0137011AB for ; Tue, 8 Mar 2016 13:29:44 +0000 (UTC) Subject: Atheros 9462 detected but nonfunctional From: Eric McCorkle Content-Type: text/plain; charset=us-ascii X-Mailer: iPad Mail (13D15) Message-Id: <86B2B57E-A595-490E-9A9A-67F14EA5BB90@metricspace.net> Date: Tue, 8 Mar 2016 08:29:43 -0500 To: freebsd-wireless@freebsd.org Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.21 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, 08 Mar 2016 13:29:52 -0000 Hello, I am trying to diagnose an issue with an Atheros 9462 card. The card is bei= ng detected, and seemingly works (reports no errors with wpa_supplicant and f= riends), however, the radios seem completely nonfunctional, as the card does= n't actually transmit or receive anything (I checked by turning on packet lo= gging and running scans/wpa_supplicant). There are errors reported in pciconf (it claims they are correctable errors)= : receiver error, bad tlp, bad dllp. The Bluetooth subsystem also suffered t= imeouts (very likely related). I have confirmed this is not a hardware problem by booting into Linux with a= live memstick and running a scan. I'm looking for advise on likely root causes and how to go about diagnosing t= he problem (I've never diagnosed a problem on a *supported* card in FreeBSD b= efore, so I'm relatively unfamiliar with the process). Best, Eric=