From owner-freebsd-mobile Tue Aug 13 7: 2:38 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E6ED37B401 for ; Tue, 13 Aug 2002 07:02:34 -0700 (PDT) Received: from itworks.com.au (dsl-210-15-242-5.Melbourne.netspace.net.au [210.15.242.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 705A643E3B for ; Tue, 13 Aug 2002 07:02:32 -0700 (PDT) (envelope-from gavin@itworks.com.au) Received: (qmail 618 invoked from network); 13 Aug 2002 14:01:07 -0000 Received: from unknown (HELO bugs) (192.168.1.100) by chip.gav.itworks.com.au with SMTP; 13 Aug 2002 14:01:07 -0000 Message-ID: <009a01c242d2$0d9fd860$6401a8c0@bugs> From: "Gavin Cameron" To: Subject: Latest wi0 crashes with stable Date: Wed, 14 Aug 2002 00:02:25 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I decided tonight to change the way my wireless network works to see if I could get around the wi0 crashes on my 4.6-STABLE box. I've turned off WEP, after seeing a suggestion to do so in -CURRENT but the network crashes continue to occur. After the last crash I decided to down the wi0 interface to see if I could get networking working again. The ifconfig wi0 down command came back with the error wi0: wi_cmd: busy bit won't clear. The other network interfaces started working again after a little while but the wi0 interface will not start up again and immediately upon trying to up the interface starts spewing out messages like chip# ifconfig wi0 up 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: init failed wi0: timeout in wi_seek to fc07/0; last status 800b wi0: timeout in wi_seek to fc00/0; last status 800b wi0: timeout in wi_seek to fc81/0; last status 800b wi0: timeout in wi_seek to fc83/0; last status 800b wi0: timeout in wi_seek to fc83/0; last status 800b wi0: timeout in wi_seek to fc06/0; last status 800b wi0: timeout in wi_seek to fc09/0; last status 800b wi0: timeout in wi_seek to fc0c/0; last status 800b wi0: timeout in wi_seek to fc2d/0; last status 800b wi0: timeout in wi_seek to fc04/0; last status 800b wi0: timeout in wi_seek to fc02/0; last status 800b wi0: timeout in wi_seek to fc03/0; last status 800b wi0: timeout in wi_seek to fc0e/0; last status 800b wi0: timeout in wi_seek to fc2a/0; last status 800b wi0: timeout in wi_seek to fc01/0; last status 800b wi0: timeout in wi_seek to fc85/0; last status 800b wi0: timeout in wi_seek to fc28/0; last status 800b wi0: timeout in wi_seek to fc23/0; last status 800b wi0: timeout in wi_seek to fc24/0; last status 800b wi0: timeout in wi_seek to fc80/0; last status 800b wi0: wi_cmd: busy bit won't clear. wi0: wi_cmd: busy bit won't clear. wi0: failed to allocate 1594 bytes on NIC wi0: tx buffer allocation failed wi0: wi_cmd: busy bit won't clear. wi0: failed to allocate 1594 bytes on NIC wi0: mgmt. buffer allocation failed My wi0 card is a Netgear MA401 in a MA301 PCI cradle. Anyone know how I can check old versions of the wi driver out using cvsup? Things were working great a month ago! Thanks in advance for any advice. Cheers Gavin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message