From owner-freebsd-current@FreeBSD.ORG Mon Jul 7 16:43:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8294337B404 for ; Mon, 7 Jul 2003 16:43:31 -0700 (PDT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B61043FB1 for ; Mon, 7 Jul 2003 16:43:30 -0700 (PDT) (envelope-from sam@errno.com) Received: from melange.errno.com (melange.errno.com [66.127.85.82]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id h67NhT7N063663 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 7 Jul 2003 16:43:30 -0700 (PDT) (envelope-from sam@errno.com) Date: Mon, 07 Jul 2003 16:43:28 -0700 From: Sam Leffler To: Lukas Ertl , freebsd-current@freebsd.org Message-ID: <634680432.1057596208@melange.errno.com> In-Reply-To: <20030705224250.I12753@korben.in.tern> References: <20030705122054.H693@korben.in.tern> <20030705192426.U3328@korben.in.tern> <20030705224250.I12753@korben.in.tern> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Experiences with ath(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 07 Jul 2003 23:43:31 -0000 >> Ok, I've investigated this further. The strange thing is: whenever the >> connections to the outside drop, I can ping and connect to any host in my >> LAN (10.0.0.0/24), but I _cannot_ ping 10.0.0.138 from the WLAN client, >> which is the inside interface of the ADSL router and thus the default >> route. I can't explain why. "ifconfig ath0 down && ifconfig ath0 up" >> solves this lock-up. Could this be a driver bug? > > Another update: > > Jul 5 22:38:39 korben kernel: ath0: device timeout > Jul 5 22:38:40 korben kernel: ath_hal_wait: timeout on reg 0x8: > 0xffffffff & 0x00000004 != 0x00000000 > Jul 5 22:38:40 korben kernel: ieee80211_new_state: RUN -> INIT > Jul 5 22:38:40 korben kernel: ath0: unable to reset hardware; hal status > 3 Jul 5 22:39:02 korben kernel: ath0: unable to reset hardware; hal > status 3 > > Then the card is dead. According to the manpage, "this should not happen" > :-) > Never seen this sort of thing except when yanking a card while the driver was in the middle of talking to the hardware. Some more context would be helpful. > If I pull it out and plug it back in, I get: > > Jul 5 22:39:46 korben kernel: ath0: detached > Jul 5 22:39:57 korben kernel: ath0: mem > 0x20000000-0x2000ffff irq 11 at device 0.0 on cardbus1 > Jul 5 22:40:54 korben kernel: ath0: failed to allocate descriptors: 12 > Jul 5 22:40:54 korben kernel: device_probe_and_attach: ath0 attach > returned 12 > Jul 5 22:40:54 korben kernel: cbb1: CardBus card activation failed > Looks like memory didn't get free'd up when you yanked the card as reinserting should've found at least the same memory that was there before. Sam