From owner-freebsd-current Mon Dec 30 14:10:30 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 176B737B401 for ; Mon, 30 Dec 2002 14:10:27 -0800 (PST) Received: from castle.org (castle.org [63.231.56.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FD6743ED1 for ; Mon, 30 Dec 2002 14:10:26 -0800 (PST) (envelope-from nomad@castle.org) Received: from castle.org (localhost.castle.org [127.0.0.1]) by castle.org (8.12.6/8.12.6) with ESMTP id gBUMAKZc068550 for ; Mon, 30 Dec 2002 14:10:20 -0800 (PST) (envelope-from nomad@castle.org) Message-Id: <200212302210.gBUMAKZc068550@castle.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: current@freebsd.org Subject: Re: My wi(4) ate itself (or Fun with no memory). In-reply-to: Your message of Mon, 30 Dec 2002 23:06:50 +0100. <20021230220649.GA575@unixpages.org> X-uri: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Dec 2002 14:10:20 -0800 From: Lee Damon 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 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.) nomad > On Mon, Dec 30, 2002 at 11:36:45AM -0800, Juli Mallett wrote: > > Hey, > >=20 > > I ran some stuff overnight which exhausted my system's memory fairly well, > > and was also thrashing around on my network, and I woke up to find that my > > wi(4) blew up more or less: > >=20 > > wi0: watchdog timeout > > wi0: timeout in wi_cmd 0x0002; event status 0x8000 > > wi0: timeout in wi_cmd 0x0000; event status 0x8000 > > wi0: wi_cmd: busy bit won't clear. > > wi0: wi_cmd: busy bit won't clear. > > wi0: init failed > > 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: 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 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 > > Expensive timeout(9) function: 0xc02aefa0(0) 127.445894221 > > wi0: timeout in wi_seek to 0/0; last status 4000 > > wi0: timeout in wi_seek to 0/44; last status 4044 > > wi0: wi_cmd: busy bit won't clear. > > wi0: xmit failed > > Expensive timeout(9) function: 0xc02cfde0(0xc1a08ccc) 7.384429976 > > wi0: watchdog timeout > > 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: init failed > > 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: 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 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 > > Expensive timeout(9) function: 0xc02aefa0(0) 135.098850348 > > wi0: timeout in wi_seek to 0/0; last status 4000 > > wi0: timeout in wi_seek to 0/44; last status 4044 > > wi0: wi_cmd: busy bit won't clear. > > wi0: xmit failed > >=20 > > Was how it started, and then a lot more of the 'busy bit won't clear' > > messages. I ejected the card after de-b0rking the rest of the system, and > > was able to bring it back up fine, but thought maybe someone might have s= > ome > > insight into how exactly my wi(4) blew up, and whether this is an accepta= > ble > > failure case :) > >=20 > > Thanx, > > juli. > > --=20 > > Juli Mallett > > AIM: BSDFlata IRC: juli@EFnet#flata > > OpenDarwin, Mono, FreeBSD Developer. > > ircd-hybrid Developer, EFnet addict. > > FreeBSD on MIPS-Anything on FreeBSD. > >=20 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > >=20 > >=20 > > I get those messages when running dstumbler and then trying to do other stu= > ff > with the device. > The bad thing is, that the chip is integrated in my notebook so i can't sim= > ply > take it out and back in again :-) > Is there any other way to reinitialize the card? > > - Christian > > --=20 nomad ----------- - Lee "nomad" Damon - \ play: nomad@castle.org or castle!nomad \ work: nomad@ee.washington.edu \ /\ Seneschal, Castle PAUS. / \ "Celebrate Diversity" / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message