Date: Tue, 31 Dec 2002 11:30:51 +0200 From: Ants Aader <ants@aader.com> To: Juli Mallett <jmallett@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: My wi(4) ate itself (or Fun with no memory). Message-ID: <20021231093051.GA4633@urr.aader.com>
next in thread | raw e-mail | index | archive | help
I have had almost exactly same problems about year ago. Orinoco silver stopped two times after 25 - 28 day working with freebsd current under somewhat strong load. Even after reboot it didn't work anymore. I burned two times new firmware and the card started to work again. The problem was gone if I put this card at third time to another machine. Ants 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: 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 ........ > 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021231093051.GA4633>