From owner-freebsd-current Mon Dec 30 14:39:14 2002 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 A390137B401 for ; Mon, 30 Dec 2002 14:39:12 -0800 (PST) Received: from smtp.inode.at (goliath.inode.at [195.58.161.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AE4143EA9 for ; Mon, 30 Dec 2002 14:39:12 -0800 (PST) (envelope-from mranner@inode.at) Received: from line-f-178.adsl-dynamic.inode.at ([62.99.193.178] helo=dwarf.jawa.at) by smtp.inode.at with esmtp (Exim 3.34 #1) id 18T8Yv-0005Fq-00 for freebsd-current@freebsd.org; Mon, 30 Dec 2002 23:39:10 +0100 Content-Type: text/plain; charset="iso-8859-1" From: Michael Ranner To: freebsd-current@freebsd.org Subject: Re: My wi(4) ate itself (or Fun with no memory). Date: Mon, 30 Dec 2002 23:39:00 +0100 User-Agent: KMail/1.4.3 References: <200212302210.gBUMAKZc068550@castle.org> In-Reply-To: <200212302210.gBUMAKZc068550@castle.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200212302328.46783.mranner@inode.at> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am Montag, 30. Dezember 2002 23:10 schrieb Lee Damon: > I have the same problems on an IBM T30 with integrated wi running > 4.7-STABLE. In fact, I've had this problem since 4.5 (which is where I > started on this system.) I think the "wi0: timeout in wi_cmd 0x0000; event status 0x8000" messages started around 4.4, 4.5 or so. With my old FreeBSD 4 I had no "visible" problems, but after upgrading to 4.7 I have tons of wi_timeout's I fixed it with: 1359c1359 < DELAY(WI_DELAY); --- > /*DELAY(WI_DELAY);*/ 1363,1364c1363,1364 < device_printf(sc->dev, "timeout in wi_seek to %x/%x; last status %x\n", < id, off, status); --- > /*device_printf(sc->dev, "timeout in wi_seek to %x/%x; last status %x\n", > id, off, status);*/ The big problem was the "DELAY", because this call freezes the system and that was not acceptable for a router, but I also increased the value of the surrounding loop. > > > wi0: watchdog timeout > > > wi0: tiwi0: wi_cmeout in wi_cmd 0x0000; event status 0x8000 > > > wi0: wi_cmd: busy bit won't clear. > > > wi0: init failed ... I've seen this kind of problems with my Netgear, D-Link (both Prism2.5) and US-Robotis (Prism2) cards in access point mode. I have no such messages and problems in ad-hoc mode. Regards, /\/\ichael Ranner mranner@jawa.at - mranner@bitonline.cc - webmaster@mariazell.at ---------------------------------------------------------------------- JAWA Management Software GmbH - http://www.jawa.at/ Liebenauer Hauptstrasse 2oo - A-8041 Graz Tel +43 316 403274 21 - Fax +43 316 403274 10 ---------------------------------------------------------------------- Mariazell Online - http://www.mariazell.at/ ---------------------------------------------------------------------- -----BEGIN GEEK CODE BLOCK----- GIT/CS/AT dx(-) s+:(++:) a- C++ UBLVS++++$ P++>+++$ L-(+)$ E--- W+++$ N+(++) o-- K- w--()$ O-(--) M@ V-(--) PS+>++ PE(-) Y+ PGP(-) t+ 5+ X+++(++++) R* tv++ b+(++) DI++ D-(--) G- e h--(*) r++ y? ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message