From owner-freebsd-current@FreeBSD.ORG Tue Aug 12 16:54:47 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 D9DF237B401 for ; Tue, 12 Aug 2003 16:54:47 -0700 (PDT) Received: from xyzzy.wireless.snsonline.net (dhcp.looksmart.com.au [210.9.52.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 465ED43F75 for ; Tue, 12 Aug 2003 16:54:44 -0700 (PDT) (envelope-from msergeant@snsonline.net) Received: from xyzzy.wireless.snsonline.net (localhost [127.0.0.1]) h7CC1CoH001651; Tue, 12 Aug 2003 22:01:12 +1000 (EST) (envelope-from msergeant@snsonline.net) Received: (from sarge@localhost)h7CC1Aws001650; Tue, 12 Aug 2003 22:01:10 +1000 (EST) X-Authentication-Warning: xyzzy.wireless.snsonline.net: sarge set sender to msergeant@snsonline.net using -f From: Mark Sergeant To: Martin Blapp In-Reply-To: <20030812130551.Y2686@cvs.imp.ch> References: <20030812104605.G2686@cvs.imp.ch> <1060684879.912.2.camel@xyzzy.wireless.snsonline.net> <20030812130551.Y2686@cvs.imp.ch> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SNSOnline Technical Services Message-Id: <1060689669.912.18.camel@xyzzy.wireless.snsonline.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 12 Aug 2003 22:01:10 +1000 cc: freebsd-current@freebsd.org Subject: Re: Problem with dhclient & wi0 on resume. 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: Tue, 12 Aug 2003 23:54:48 -0000 On Tue, 2003-08-12 at 21:10, Martin Blapp wrote: > Hi, > > > Unfortunately this system hasn't worked for me. As it is I have a script > I've put the sleep command in rc.suspend and the wake in rc.resume but they didn't help. I also tried to use these commands manually and again no luck. Killing dhclient and restarting manually works though. > Have you tested it and included theses commands in rc.resume and rc.suspend ? > > > which lives in rc.d which starts up dhclient with the appropriate > > wireless options. Unfortunately after each suspend and resume this is > > what I have to use. > > > > If anyone comes up with a solution to this it'd be much appreciated. > > Which "script" do you use ? The dhclient script in /etc/rc.d ? > The script I use is a "homemade" one, after looking at /etc/rc.d/dhclient it seems that this will do the job nicely enough, thanks for this tip. My main problem now comes back to the wi driver spitting up a whole lot of errors, it's now quite often freezing up entirely with the following ... wi0: timeout in wi_cmd 0x0002; event status 0x8080 wi0: timeout in wi_cmd 0x0121; event status 0x8080 wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: failed to allocate 2372 bytes on NIC wi0: tx buffer allocation failed (error 12) wi0: interface not running wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. The machine then has to be hard reset when this happens. > Martin -- Mark Sergeant SNSOnline Technical Services