From owner-freebsd-current@FreeBSD.ORG Sat Jul 5 13:45:24 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 E47FE37B401; Sat, 5 Jul 2003 13:45:24 -0700 (PDT) Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D926544015; Sat, 5 Jul 2003 13:45:23 -0700 (PDT) (envelope-from l.ertl@univie.ac.at) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id h65KjA1S120922; Sat, 5 Jul 2003 22:45:13 +0200 Date: Sat, 5 Jul 2003 22:45:05 +0200 (CEST) From: Lukas Ertl To: freebsd-current@freebsd.org In-Reply-To: <20030705192426.U3328@korben.in.tern> Message-ID: <20030705224250.I12753@korben.in.tern> References: <20030705122054.H693@korben.in.tern> <20030705192426.U3328@korben.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-DCC-ZID-Univie-Metrics: mailbox 4246; Body=0 Fuz1=0 Fuz2=0 cc: sam@freebsd.org 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: Sat, 05 Jul 2003 20:45:25 -0000 On Sat, 5 Jul 2003, Lukas Ertl wrote: > 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 !=3D 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" :-) 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 regards, le --=20 Lukas Ertl eMail: l.ertl@univie.ac.at UNIX-Systemadministrator Tel.: (+43 1) 4277-14073 Zentraler Informatikdienst (ZID) Fax.: (+43 1) 4277-9140 der Universit=E4t Wien http://mailbox.univie.ac.at/~le/