Date: Mon, 30 Dec 2002 23:06:50 +0100 From: Christian Brueffer <chris@unixpages.org> To: Juli Mallett <jmallett@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: My wi(4) ate itself (or Fun with no memory). Message-ID: <20021230220649.GA575@unixpages.org> In-Reply-To: <20021230113644.A17112@FreeBSD.org> References: <20021230113644.A17112@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Mon, Dec 30, 2002 at 11:36:45AM -0800, Juli Mallett wrote: > Hey, > > 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: > > 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 > > 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 some > insight into how exactly my wi(4) blew up, and whether this is an acceptable > failure case :) > > Thanx, > juli. > -- > Juli Mallett <jmallett@FreeBSD.org> > AIM: BSDFlata IRC: juli@EFnet#flata > OpenDarwin, Mono, FreeBSD Developer. > ircd-hybrid Developer, EFnet addict. > FreeBSD on MIPS-Anything on FreeBSD. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > I get those messages when running dstumbler and then trying to do other stuff with the device. The bad thing is, that the chip is integrated in my notebook so i can't simply take it out and back in again :-) Is there any other way to reinitialize the card? - Christian -- http://www.unixpages.org chris@unixpages.org GPG Pub-Key : www.unixpages.org/cbrueffer.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D GPG Key ID : 0xA0ED982D [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+EMN5bHYXjKDtmC0RAngmAJ9iaFMaJMRaUzUdAKpJggQ8RqyNKQCgsNOe gVU1F4vEBEspomEPb9sOo78= =EDGu -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021230220649.GA575>