From owner-freebsd-wireless@FreeBSD.ORG Thu May 26 06:15:44 2011 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D7A7106564A for ; Thu, 26 May 2011 06:15:44 +0000 (UTC) (envelope-from dalibor.gudzic@gmail.com) Received: from mail-px0-f176.google.com (mail-px0-f176.google.com [209.85.212.176]) by mx1.freebsd.org (Postfix) with ESMTP id F167E8FC15 for ; Thu, 26 May 2011 06:15:43 +0000 (UTC) Received: by pxi11 with SMTP id 11so245381pxi.7 for ; Wed, 25 May 2011 23:15:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=ss7vXfQu8IP3hc4vspkLrxEJkA69M4EHpESA6TL5Lgk=; b=cJqd2XJViftZufsjhdCwkbRQVktYvNkmpGx2Wm4OK1o+US9IL21lGI76m1nEls682k UqHOskcxVtFfiup+Kw4im2fgMtNsQiK7R0L/0I7M/7tfjI+1pdkPlU5KZx2QI5w5OZWd dEmpo6xH416hLtdfvNiHH0X6DFM3ybh0NXdEs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=FDtObvos1vtoDpwuY9xEofXVdW0DiApNFxZ7fBFA/Um8A1qOWtdLFeV0X6k3fJk6dC 41vnrk3imskU71fCyW9wavM21fwO8ezUdnq4/Bbe0yzrbYDj1QhhS1X2K9ICmCvwfZBs xRsz5Og2MwMl6c4PBmJMTXS2VH8QmI/Z7VRfY= MIME-Version: 1.0 Received: by 10.143.26.42 with SMTP id d42mr69559wfj.215.1306390543392; Wed, 25 May 2011 23:15:43 -0700 (PDT) Received: by 10.142.194.6 with HTTP; Wed, 25 May 2011 23:15:43 -0700 (PDT) In-Reply-To: References: <201105241220.p4OCKEZc074668@freefall.freebsd.org> Date: Thu, 26 May 2011 08:15:43 +0200 Message-ID: From: Dalibor Gudzic To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: kern/140796: [ath] [panic] Cannot attach (unable to attach hardware; HAL status 3) under 8, panic in 7.x X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 26 May 2011 06:15:44 -0000 Hi Adrian, On Thu, May 26, 2011 at 3:46 AM, Adrian Chadd wrote: > That's odd: > > ar5212SetPowerModeAwake: Failed to wakeup in 40ms > > That means there's something off with the RTC in the card (that > controls power on/power off.) > > Can you try booting a -HEAD kernel ? It may be related to cardbus related stuff. > > > Adrian > I had some problem burning the media, but will try later for sure. In the mean time, here is the relevant section of dmesg with hw.ath.hal.debug in loader.conf (forgot to include it in previous message): ... pcib5: at device 19.1 on pci0 pci5: on pcib5 ath0: mem 0xc9000000-0xc900ffff irq 18 at device 1.0 on pci5 ath0: [ITHREAD] ar5212Attach: sc 0xc49a6000 st 0x1 sh 0xe4ee7000 ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerModeAwake: bogus SCR 0xffffffff, PCICFG 0xffffffff ar5212SetPowerModeAwake: Failed to wakeup in 40ms ar5212Attach: couldn't wakeup chip ar5212Detach: Detaching Ani ar5212SetPowerMode: AWAKE -> AWAKE (set chip ) ar5212SetPowerModeAwake: bogus SCR 0xffffffff, PCICFG 0xffffffff ar5212SetPowerModeAwake: Failed to wakeup in 40ms ar5212SetPowerMode: AWAKE -> FULL-SLEEP (set chip ) ath0: unable to attach hardware; HAL status 3 device_attach: ath0 attach returned 6 acpi_acad0: on acpi0 ... Card works without problem in Windows XP/Ubuntu 10.10. On NetBSD I get the same messages (unable to attach bla bla). It was the same on OpenBSD before 4.8, now there are no messages in dmesg. It spits something like device timeout when I 'ifconfig up' it though, but I think card is working (haven't thoroughly tested it). I don't know how similar code for ath(4) is between *BSD's. All best Dalibor