From owner-freebsd-current@FreeBSD.ORG Mon Oct 10 02:59:31 2005 Return-Path: X-Original-To: freebsd-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 237FE16A41F; Mon, 10 Oct 2005 02:59:31 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B646643D45; Mon, 10 Oct 2005 02:59:30 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9A2vJJO013364; Sun, 9 Oct 2005 20:57:19 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 09 Oct 2005 20:58:20 -0600 (MDT) Message-Id: <20051009.205820.129710153.imp@bsdimp.com> To: avatar@mmlab.cse.yzu.edu.tw From: "M. Warner Losh" In-Reply-To: <0510091447540.81426@www.mmlab.cse.yzu.edu.tw> References: <200510081630.j98GU1Sf021682@sakura.ninth-nine.com> <0510091447540.81426@www.mmlab.cse.yzu.edu.tw> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 09 Oct 2005 20:57:19 -0600 (MDT) Cc: freebsd-current@FreeBSD.org, nork@FreeBSD.org Subject: Re: dhclient with if_wi&wep 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: Mon, 10 Oct 2005 02:59:31 -0000 In message: <0510091447540.81426@www.mmlab.cse.yzu.edu.tw> Tai-hwa Liang writes: : On Sun, 9 Oct 2005, Norikatsu Shigemura wrote: : > dhclient with if_wi&WEP will freeze on 7-current. : > : > I am using following if_wi and WEP. : [...] : > Oct 8 22:01:08 pelsia kernel: Oct 8 22:01:08 pelsia kernel: wi0: timeout in wi_cmd 0x0000; event status 0x8008 : > Oct 8 22:01:08 pelsia kernel: wi0: wi_cmd: busy bit won't clear. : > Oct 8 22:01:08 pelsia kernel: wi0: init failed : > Oct 8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc00/0 : > Oct 8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc81/0 : > Oct 8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc85/0 : > Oct 8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc2a/0 : > Oct 8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc28/0 : > Oct 8 22:01:08 pelsia kernel: wi0: timeout in wi_seek to fc80/0 : > Oct 8 22:01:08 pelsia kernel: wi0: failed to allocate 2372 bytes on NIC : > Oct 8 22:01:08 pelsia kernel: wi0: tx buffer allocation failed (error 12) : > Oct 8 22:01:08 pelsia kernel: wi0: interface not running : [...] : : Sometimes I run into this whilst running "ifconfig wi0 up" w/o if_wi.ko : loaded; that is, the "busy bit won't clear, init failed" happens to my : R40(builtin wi miniPCI) regardless of whether or not the WEP is enabled. : : It looks to me that the firmware doesn't ack. properly at that moment : (unfortunately I have no idea about how to fix this); however, the second : retry("kldunload if_wi" then "ifconfig wi0 up" again) works for me. ifconfig wi0 down; ifconfig wi0 up causes wi_stop and wi_init to be called, which does a pretty good job at resetting the card. It does everything except a COR reset to the card, which is rarely (but sometimes) needed to unwedge the card. Warner