From owner-freebsd-net@FreeBSD.ORG Fri Jan 30 23:30:38 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B746106567E for ; Fri, 30 Jan 2009 23:30:38 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 77D828FC1A for ; Fri, 30 Jan 2009 23:30:37 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from volatile.chemikals.org (morganw-1-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:47e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id 9AAC8A1DDA90; Fri, 30 Jan 2009 17:30:34 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id n0UNUSn2071928; Fri, 30 Jan 2009 17:30:29 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Fri, 30 Jan 2009 17:30:28 -0600 (CST) From: Wes Morgan To: Adam K Kirchhoff In-Reply-To: <200901300858.12029.adamk@voicenet.com> Message-ID: References: <200901300858.12029.adamk@voicenet.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org Subject: Re: atheros 5212 problems on -STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2009 23:30:38 -0000 On Fri, 30 Jan 2009, Adam K Kirchhoff wrote: > > Since the iwi driver doesn't want to join the wireless network at work (I opened up a pr for it), I decided to try the ath driver instead. > The card is an Atheros 5212. > > Unfortunately, I'm having even more serious problems with this card: > > ath0: ath_chan_set: unable to reset channel 7 (2442 Mhz, flags 0x480 hal flags 0xc0), hal status 3302560252 > ath0: ath_chan_set: unable to reset channel 52 (5260 Mhz, flags 0x140 hal flags 0x140), hal status 3296823488 > ath0: ath_chan_set: unable to reset channel 56 (5280 Mhz, flags 0x140 hal flags 0x140), hal status 0 > ath0: ath_chan_set: unable to reset channel 60 (5300 Mhz, flags 0x140 hal flags 0x140), hal status 3304978572 > > It cycles through various channels till: > > ath0: device timeout > ath0: ath_reset: unable to reset hardware; hal status 3232887468 > > And then it starts with the "unable to reset channel" errors again. This continues till I run '/etc/rc.d/netif stop ath0' > > When I go to remove the card, the kernel panics: > > panic: resource_list_release: resource entry is not busy > cpuid = 0 > KDB: enter: panic > [thread pid 34 tid 100033 ] > Stopped at kdb_enter_why+0x3a: movl $0,kdb_why > db> bt > Tracing pid 34 tid 100033 td 0xc4988690 > kdb_enter_why(c0b5759f,c0b5759f,c0b591cd,e5070bc4,0,...) at kdb_enter_why+0x3a > panic(c0b591cd,3,10,0,c49f91c0,...) at panic+0x136 > resource_list_release(c4b6bc04,c494ab80,c49f8900,3,10,...) at resource_list_release+0xc2 > bus_generic_rl_release_resource(c494ab80,c49f8900,3,10,c49f9480) at bus_generic_rl_release_resource+0x77 > bus_release_resource(c49f8900,3,10,c49f9480,c49f8900,...) at bus_release_resource+0x67 > ath_pci_detach(c49f8900,c48a1858,c0c15b60,c07c8125,4,...) at ath_pci_detach+0xb2 > device_detach(c49f8900,e5070cac,e5070cb0,c4988690,e5070cc0,...) at device_detach+0x68 > cardbus_detach_card(c494ab80,c48b08e0,c0bd2bfc,0,0,...) at cardbus_detach_card+0xcd > cbb_event_thread(c4913800,e5070d38,0,0,0,...) at cbb_event_thread+0x1ac > fork_exit(c0661a50,c4913800,e5070d38) at fork_exit+0x99 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xe5070d70, ebp = 0 --- Are you running sysutils/hal? I've been told it's due to a kernel bug of some kind that is fixed in -current, but hal makes my atheros card do something similar if it scans it. I had to force it to ignore the cardbus device to stop it from happening, but I have other issues with HAL and the new xorg, so I just flat out disabled it. Doesn't seem to be ready for prime time on my laptop.