From owner-freebsd-current@FreeBSD.ORG Fri Dec 14 13:41:37 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0705C72; Fri, 14 Dec 2012 13:41:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) by mx1.freebsd.org (Postfix) with ESMTP id 612868FC15; Fri, 14 Dec 2012 13:41:36 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id 12so1378322wgh.31 for ; Fri, 14 Dec 2012 05:41:35 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=JWYBdj5JR3VEj4FTfpwpWVVbLhjefJKWfYYDxqO77WM=; b=zq3SyrFncRzS0nkjsWGCbUEr3MKGe7M6WiAjimDwbULPbxTKjKf0knsuriwMLXu8Qt 6OgJ9RwJJ5h+UdihKXw8Sae79jIMP5d0lDYK+9dC3VJv8G53NUU1AeL1z/bSawexgSP7 og7qo8bYlc83chyAdImzwLNFpDjsPDjQ9Ddk5IGiLoN9RHvyAGEkkgMULUFsAl0ZZmvI 4B22NT7GGBZB0uPfzM/h5rpyThFJfEQf9VFGUJncdp9qE+rizYU+lDycL6ejK1azPXO2 HnppOC6tz2eDPOB8PHL/YQNxTMJQWlK0Vt9LtPE+oaIyS52NmXDM/1QHDbZNIk2NjN3i EZyA== MIME-Version: 1.0 Received: by 10.180.104.69 with SMTP id gc5mr2711451wib.13.1355492495241; Fri, 14 Dec 2012 05:41:35 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Fri, 14 Dec 2012 05:41:35 -0800 (PST) In-Reply-To: <20121214085607.3938D10E2C8@smtp.hushmail.com> References: <20121123213551.C2CB9E6739@smtp.hushmail.com> <201212101437.54825.jhb@freebsd.org> <201212111549.49942.jhb@freebsd.org> <20121213211100.5395F10E2C8@smtp.hushmail.com> <20121214085607.3938D10E2C8@smtp.hushmail.com> Date: Fri, 14 Dec 2012 05:41:35 -0800 X-Google-Sender-Auth: xrEoDSmdxYThJDv8sQDC2h4JBx0 Message-ID: Subject: Re: ath0: unable to attach hardware From: Adrian Chadd To: husyh@hush.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Dec 2012 13:41:37 -0000 Hi, Ok. I'm travelling for a little bit; if I don't reply in a few days, please poke me again. It may be that the device is asleep for a bit longer (failing this test) and has completed resetting at this point. It may be that the power on sequence is not quite right for some reason. Would you mind recompiling your kernel and making if_ath a kld, rather than statically in the kernel? Thanks, Adrian > > attached to this e-mail you find the output of dmesg. What I guess the most relevant lines could be is: > > ath0: mem 0xfdee0000-0xfdeeffff irq 16 at device 4.0 on pci2 > ar5212ChipTest: address test failed addr: 0x00008000 - wr:0x00000000 != rd:0xffffffff > ar5212Attach: hardware self-test failed > ath0: unable to attach hardware; HAL status 14 > device_attach: ath0 attach returned 6 > > I read the registers 4004 and 4010 again to make sure the values still are the same, which indeed they are. > > I hope this helps. > > Thanks! > > On Donnerstag, 13. Dezember 2012 at 10:18 PM, "Adrian Chadd" wrote: >> >>On 13 December 2012 13:11, wrote: >>> Hello everyone, >>> >>> I'm afraid I still don't know what exactly BAR is, or how I get >>its value that I'm supposed to plug into the line John provided: >>> dd if=/dev/mem bs=4 iseek=((start of bar + reg offset)/4) >>count=1 | hd >>> >>> I assumed that "start of bar" is 0xfdee0000 in my case, since >>dmesg reports >>> ath0: mem 0xfdee0000-0xfdeeffff irq 16 at device >>4.0 on pci2 >> >>Yup. >> >>> This is what I get: >>> # dd if=/dev/mem bs=4 iseek=`echo "ibase=16; (FDEE0000+4004)/4" >>| bc` count=1 | hd >>> 00 00 01 00 >>> # dd if=/dev/mem bs=4 iseek=`echo "ibase=16; (FDEE0000+4010)/4" >>| bc` count=1 | hd >>> 14 00 01 00 >>> >>> Please correct me if my assumption about "start of bar" was >>wrong and/or I made some other mistake. >>> Also, please don't hesitate to ask me to do anything else that >>might help you during debugging. >>> >>> Thank you very much for the effort. >> >>Hm. Wait, what's the rest of the ath0: output? >> >> >> >>Adrian