From owner-freebsd-mobile Wed Aug 7 6:32:52 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 BB82137B400 for ; Wed, 7 Aug 2002 06:32:47 -0700 (PDT) Received: from itworks.com.au (dsl-210-15-243-44.Melbourne.netspace.net.au [210.15.243.44]) by mx1.FreeBSD.org (Postfix) with SMTP id 4173543E5E for ; Wed, 7 Aug 2002 06:32:45 -0700 (PDT) (envelope-from gavin@itworks.com.au) Received: (qmail 406 invoked from network); 7 Aug 2002 13:31:05 -0000 Received: from unknown (HELO bugs) (192.168.1.100) by chip.gav.itworks.com.au with SMTP; 7 Aug 2002 13:31:05 -0000 Message-ID: <000701c23e16$e837d150$6401a8c0@bugs> From: "Gavin Cameron" To: "Warren Block" , "M. Warner Losh" Cc: References: Subject: Re: wi interface with Netgear 301/401 flakey Date: Wed, 7 Aug 2002 23:32:42 +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 My networking just crashed again with a whole heap of wi0 errors which I list below. Once wi0 became hosed all networking to the freebsd box died and a reboot was required. All I was doing across the wireless link was a ssh and an IMAP session. If nothing's changed in the wi0 driver what other changes could be causing this flakiness? Cheers, Gavin Here are the messages: Aug 7 23:20:32 chip /kernel: wi0: timeout in wi_cmd 0x010b; event status 0x0000 Aug 7 23:20:32 chip /kernel: wi0: xmit failed Aug 7 23:21:52 chip /kernel: wi0: watchdog timeout Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to 14b/0; last status 810b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to 14b/3c; last status 810b Aug 7 23:21:52 chip /kernel: wi0: wi_cmd: busy bit won't clear. Aug 7 23:21:52 chip /kernel: wi0: xmit failed Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to 14b/0; last status 810b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to 14b/3c; last status 810b Aug 7 23:21:52 chip /kernel: wi0: wi_cmd: busy bit won't clear. Aug 7 23:21:52 chip /kernel: wi0: xmit failed Aug 7 23:21:52 chip /kernel: wi0: wi_cmd: busy bit won't clear. Aug 7 23:21:52 chip /kernel: wi0: init failed Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc07/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc00/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc81/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc83/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc84/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc06/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc09/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc0c/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc2d/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc04/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc02/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc03/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc0e/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc2a/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc01/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc85/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc28/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc23/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc24/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc2a/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: timeout in wi_seek to fc80/0; last status 800b Aug 7 23:21:52 chip /kernel: wi0: wi_cmd: busy bit won't clear. Aug 7 23:21:52 chip /kernel: wi0: wi_cmd: busy bit won't clear. Aug 7 23:21:52 chip /kernel: wi0: failed to allocate 1594 bytes on NIC Aug 7 23:21:52 chip /kernel: wi0: tx buffer allocation failed Aug 7 23:21:52 chip /kernel: wi0: wi_cmd: busy bit won't clear. Aug 7 23:21:52 chip /kernel: wi0: failed to allocate 1594 bytes on NIC Aug 7 23:21:52 chip /kernel: wi0: mgmt. buffer allocation failed ----- Original Message ----- From: "Warren Block" To: "M. Warner Losh" Cc: ; Sent: Wednesday, August 07, 2002 9:50 AM Subject: Re: wi interface with Netgear 301/401 flakey > On Tue, 6 Aug 2002, M. Warner Losh wrote: > > > In message: <015701c23d9e$ffa51050$6401a8c0@bugs> > > "Gavin Cameron" writes: > > : The cards were working beautifully until I cvsuped in the weekend. > > > > But I've not changed anything that would change anything in this area. > > Maybe something else changed in the kernel, though? That's the same > error I was seeing with the RangeLAN cards, and I was using a very > recent Stable. > > -Warren Block * Rapid City, South Dakota USA > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message