From owner-freebsd-net@FreeBSD.ORG Tue Mar 17 09:16:12 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 4BBB81065675 for ; Tue, 17 Mar 2009 09:16:12 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 2147F8FC15 for ; Tue, 17 Mar 2009 09:16:12 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id A677B2F1937; Tue, 17 Mar 2009 05:16:11 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 17 Mar 2009 05:16:11 -0400 X-Sasl-enc: OW+9GDa+aaQxC3uhZ20l1Sc5L/afLmwpRvzlNmaSO/7l 1237281371 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 2442753932; Tue, 17 Mar 2009 05:16:11 -0400 (EDT) Message-ID: <49BF6A59.6090801@incunabulum.net> Date: Tue, 17 Mar 2009 09:16:09 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.19 (X11/20090125) MIME-Version: 1.0 To: Matthias Apitz References: <200903170900.n2H90C9Y077742@freefall.freebsd.org> In-Reply-To: <200903170900.n2H90C9Y077742@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@FreeBSD.org Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work 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: Tue, 17 Mar 2009 09:16:12 -0000 Hi, One crucial piece of info missing is exactly which Atheros part you are using, can you please attach this to the PR? you can get this from pciconf -lv and look for the ath0, also please post your boot time dmesg / or when you insert the part. thanks. Matthias Apitz wrote: > The following reply was made to PR kern/132722; it has been noted by GNATS. > > From: Matthias Apitz > To: bug-followup@FreeBSD.org, guru@unixarea.de > Cc: > Subject: Re: kern/132722: [ath] Wifi ath0 associates fine with AP, but DHCP or IP does not work > Date: Tue, 17 Mar 2009 09:42:43 +0100 > > I forgot to mention that I've applied this patch from Sam to my RELENG_7 > kernel: > > http://article.gmane.org/gmane.os.freebsd.stable/60383/match=cft+ath+hal+src > > I think, updating to > > Date: Thu Mar 12 03:09:11 2009 > New Revision: 189720 > URL: http://svn.freebsd.org/changeset/base/189720 > > as suggested will not change anything, or I'm wrong? > I didn't make many changes apart from fixups in a few files for the diff, so if you're running with the updated HAL, then in theory an svn update/cvsup should make no change. Of course the only way to be sure is to look under the hood. I didn't see any issues with the backported HAL, and I don't really know enough about ath(4) to suggest any workarounds at this point other than reversing your application of the patch, and cvsupping to before the date the patch was MFCed, can we be absolutely sure that the regression you observe happens with the new HAL? Sam would know more, but of course one of the reasons I've taken this on is because a project I'm involved with needs working ath(4) on pci-e in 7.x, I don't know about chip specific problems at this point in time, so I'm just as in the dark as you are! thanks, BMS