From owner-freebsd-wireless@FreeBSD.ORG Sun Feb 17 20:48:40 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 638F43DD for ; Sun, 17 Feb 2013 20:48:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id D7E0482C for ; Sun, 17 Feb 2013 20:48:39 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hi8so2804616wib.13 for ; Sun, 17 Feb 2013 12:48:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=kbdy4Z5Ou+uIMpFCjlzR13IFdH1nM2rIQ0LTaJwkLJU=; b=I0R3/nhP0fkA9DE4CYMkY+9cxd9aCHC8tV2uYfNSMGJX2avXpG8zVqZYv/NO9DWs52 xT1Z6Igos2PcoPegvjpoF4lrlkzAOb808/KgsgL3t777DIX9XwDOuR3Hol7t7/qcRVYG +fQEpvaosEh55Wr8FGBe5IMIIqkXRLFBUcLY8RfpZe8MzbLApLpfl4Vkf17foPM4dBQX ELHHbgsGtRi+1ZnjXtEiqDgibSu0LLmYUIUYk+8si9v6SnzRg+3pd/S7JpjlO0KFm9x/ m7u+vVhmNg5rDLvilSOcT1vo0v10cJdFe0wlqU+kUZ2NqB+xspXTpReNZrHKlXrGOzMh kP7Q== MIME-Version: 1.0 X-Received: by 10.180.99.227 with SMTP id et3mr14690938wib.6.1361134118463; Sun, 17 Feb 2013 12:48:38 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.236.88 with HTTP; Sun, 17 Feb 2013 12:48:38 -0800 (PST) In-Reply-To: References: Date: Sun, 17 Feb 2013 12:48:38 -0800 X-Google-Sender-Auth: _NlJ-jWMGjtd_J2kpw4iUtCQzAc Message-ID: Subject: Re: Problems with an older Acer Aspire One From: Adrian Chadd To: Kurt Buff 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: Sun, 17 Feb 2013 20:48:40 -0000 Hi, So "hal status 3" is HAL_EIO - which means the hardware didn't respond as expected. So maybe the hardware is getting all angry during reset. Compile up athpeek and athregs from src/tools/tools/ath/, compile your kernel with: ATH_DEBUG AH_DEBUG ATH_DIAGAPI and then when it happens again, do this: # athregs which will dump out a snapshot of useful registers. Adrian