From owner-freebsd-current@FreeBSD.ORG Thu Jul 21 00:01:25 2005 Return-Path: X-Original-To: current@freebsd.org 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 A912616A41F for ; Thu, 21 Jul 2005 00:01:25 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BA02E43D67 for ; Thu, 21 Jul 2005 00:01:14 +0000 (GMT) (envelope-from nakal@nurfuerspam.de) Received: (qmail invoked by alias); 21 Jul 2005 00:01:09 -0000 Received: from p5090F065.dip.t-dialin.net (EHLO klotz.local) [80.144.240.101] by mail.gmx.net (mp023) with SMTP; 21 Jul 2005 02:01:09 +0200 X-Authenticated: #989277 Received: from [192.168.0.2] (booky.local [192.168.0.2]) by klotz.local (8.13.3/8.13.3) with ESMTP id j6L00mZ8001107; Thu, 21 Jul 2005 02:00:49 +0200 (CEST) (envelope-from nakal@nurfuerspam.de) Message-ID: <42DEE5BE.7080706@nurfuerspam.de> Date: Thu, 21 Jul 2005 02:01:02 +0200 From: Martin User-Agent: Mozilla Thunderbird 1.0.5 (X11/20050715) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: sam@errno.com Subject: ath(4) hostap problems (still) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 21 Jul 2005 00:01:25 -0000 Hi, when running ath(4) on -CURRENT/-RELENG_6 as client and hostap on FreeBSD-5 on another box, you will notice that the box locks up (it's stuck in a busy loop inside the kernel somewhere, if I'm lucky I can get enough cpu-time to press the reboot-kombo). I've described this problem already in my earlier mails. Today I tried to run the hostap box on FreeBSD-6. The problem still exists, but the client seems to recover from the lock after a few seconds and I can get some information out of it. The connection cannot be established once after the short lock has happened and any try to ifconfig down/up, will lock up the client for another few seconds. I could start athstats after the client recovered from the lock-situation: 3 beacon miss interrupts 22 mib overflow interrupts 62 tx management frames 180 tx frames discarded prior to association 6 tx failed 'cuz too many retries 69 long on-chip tx retries 55 tx frames with no ack marked 96 tx frames with short preamble 3 periodic calibrations avg recv rssi: 30 1 switched default/rx antenna Antenna profile: [1] tx 101 rx 0 [2] tx 0 rx 70 The value of "tx frames discarded prior to association" several times a minute. The antenna profiles change sometimes, but everything else does not change, if you run athstats multiple times. I hope it helps to investigate the problem. Client: Thinkpad R40 with Netgear WG511T PCMCIA. HostAP: Sempron 2200+, Asrock K7VT4A+, Netgear WG311T PCI. Martin