From owner-freebsd-current@FreeBSD.ORG Tue Dec 11 23:36:18 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 25392AB1; Tue, 11 Dec 2012 23:36:18 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1.freebsd.org (Postfix) with ESMTP id 834558FC1B; Tue, 11 Dec 2012 23:36:17 +0000 (UTC) Received: by mail-wi0-f180.google.com with SMTP id hj13so27175wib.13 for ; Tue, 11 Dec 2012 15:36:16 -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=r1fNM3olyhwSXPPsfrVCB+DaVmarWo1GXWB4ttonG+s=; b=oi+raA1Anl8iR8qn8hnC1+TtfupP0lbYOCKVa++ZLo2jlkbwCwtegK9Hjnv49iURgz m/BRr+mH/6rYgndhaZ71tW1QI3hFJy7XGSHkcaPiuSvm2S0L8oMVu7UrH1ywf9sOMNOC agAJnAcSEGyKQR7DOE12Kat62SSAuAaeKQ6VYfNNbfZJ0JagiYqHkIURnfjESaWVR7fh hgJeETzN1FFTwvGt7tlSzwSQ6S3pEpJ2NgSv/IMrkXyWF3j2PlaOPpFarf4DO48Ipy1k miNt82eWJSUcWA0CVafv9rCeOJ/cqHpA12mI5G+2d0EqQFQ9Qr1BBOR6WdayHci9WAJi AZXQ== MIME-Version: 1.0 Received: by 10.194.179.34 with SMTP id dd2mr3412839wjc.1.1355268976176; Tue, 11 Dec 2012 15:36:16 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Tue, 11 Dec 2012 15:36:16 -0800 (PST) In-Reply-To: <201212111549.49942.jhb@freebsd.org> References: <20121123213551.C2CB9E6739@smtp.hushmail.com> <201212101437.54825.jhb@freebsd.org> <201212111549.49942.jhb@freebsd.org> Date: Tue, 11 Dec 2012 15:36:16 -0800 X-Google-Sender-Auth: puAHLI3Ar1rr3iFn6cvy95eqAuY Message-ID: Subject: Re: ath0: unable to attach hardware From: Adrian Chadd To: John Baldwin 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2012 23:36:18 -0000 On 11 December 2012 12:49, John Baldwin wrote: > Look, it's up to you to look at more registers if you want to debug this > further. PCI says everything is ok, so the ball is in your court. Right, that's why I've asked for those two above registers. There are other things that could be wrong - eg, the device may actually not have reset correctly. This isn't the first time that someone's come to me with a "linux works, freebsd doesn't" for an AR5212 era NIC. ath5k and FreeBSD do the same thing at probe/attach time. I believe they do the same thing during device power-on time too. There's some corner cases where the chip doesn't reset right because the BIOS PCI bus reset code does things in a brain dead manner (eg doing two PCI bus resets back to back with not enough time in between for the MAC to settle.) There may be PCI code differences in how Linux and FreeBSD does things like "reset the PCI bus." Adrian