From owner-freebsd-current@FreeBSD.ORG  Mon Dec 10 22:20:55 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 CD01B938;
 Mon, 10 Dec 2012 22:20:55 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
 [209.85.212.170])
 by mx1.freebsd.org (Postfix) with ESMTP id 2CAC18FC12;
 Mon, 10 Dec 2012 22:20:54 +0000 (UTC)
Received: by mail-wi0-f170.google.com with SMTP id hq7so1591714wib.1
 for <multiple recipients>; Mon, 10 Dec 2012 14:20:54 -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=rXdwoRiRgxYiZlS8w9pmtJTgSQMjCvLFmc1OGflTJ2I=;
 b=m6XJsfJ70dhF5YkjEneBeT+NoN9JgD1vnm9WlYlD3IgDPm5SnFoxcdJOCP9NQptdVQ
 MSwwuaK1ZJjPevAtJZaX2qAh/JjEoOwhHVhKohz9Hgrc53GzDrDKPKzLFiX2CHuBNvMg
 eeU05y3IVm6qwnpSqjEr5r6dMfhP8BLzpZVZFqzNFUR8wALQapT+mXSeKu4zrTCK1UqE
 nSdeIB/+RDyQfrZ7EDjcVNF3g8Jyj91MCg+tCTpx3VOgUPD1AX5ThSLerhUEqWhZz86E
 ap5YPGAr1wmJA0C4l3BoD9LLYFv8sswbmZlZJ27y1ogak3OrB201ivDX7wF/PlE2+hJI
 p3/w==
MIME-Version: 1.0
Received: by 10.216.139.140 with SMTP id c12mr6256555wej.46.1355178053978;
 Mon, 10 Dec 2012 14:20:53 -0800 (PST)
Sender: adrian.chadd@gmail.com
Received: by 10.217.57.9 with HTTP; Mon, 10 Dec 2012 14:20:53 -0800 (PST)
In-Reply-To: <201212101437.54825.jhb@freebsd.org>
References: <20121123213551.C2CB9E6739@smtp.hushmail.com>
 <201212041106.50645.jhb@freebsd.org>
 <20121207095937.ECB38E6726@smtp.hushmail.com>
 <201212101437.54825.jhb@freebsd.org>
Date: Mon, 10 Dec 2012 14:20:53 -0800
X-Google-Sender-Auth: GcoW5_VjH8Ed-5_lwpmgDoPA80E
Message-ID: <CAJ-VmomM965-=QByhJZMPUn_PZAnSjafcm3cy3ojRaPc5fbWPg@mail.gmail.com>
Subject: Re: ath0: unable to attach hardware
From: Adrian Chadd <adrian@freebsd.org>
To: John Baldwin <jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: husyh@hush.com, 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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 22:20:56 -0000

Hi,

The fact the initial probe/attach fails by returning 0xffffffff means
the chip isn't "right" on the bus.

It's either just not mapped in correctly, or it's "powered off."

If it were just asleep, it'd return 0xdeadc0de or 0xdeadbeef or
something similar like that.

Try AR_SCR (0x4004) and AR_PCICFG (0x4010) .

Thanks,


Adrian