Date: Mon, 30 Dec 2002 16:11:34 -0800 From: "Kevin Oberman" <oberman@es.net> To: Christian Brueffer <chris@unixpages.org> Cc: Juli Mallett <jmallett@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: My wi(4) ate itself (or Fun with no memory). Message-ID: <20021231001134.42C0E5D04@ptavv.es.net> In-Reply-To: Your message of "Mon, 30 Dec 2002 23:06:50 %2B0100." <20021230220649.GA575@unixpages.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Date: Mon, 30 Dec 2002 23:06:50 +0100 > From: Christian Brueffer <chris@unixpages.org> > Sender: owner-freebsd-current@FreeBSD.ORG > > > --x+6KMIRAuhnl3hBn > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > 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 <jmallett@FreeBSD.org> > > 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? I see a possible fix posted by Michael Ranner and will try it next week. I have discovered that the problem seems to occur only when I am at work and receive signals from an encrypted access point to which I can't (and don't want to) associate. Something about this situation triggers the problem in FreeBSD while under Windows I am simply notified that a new base-station is being received. Clearly, FreeBSD is not handling something properly. As a work-around, I built a new kernel without the wi driver. When I want to use the wireless card (in my T30 with an Intersil Prism 2.5 miniPCI card), I can then either: (Only at boot time) # load if_wi or: (After the system has booted) # kldload if_wi # /etc/pccard_ether wi0 start # dhclient wi0 Either of these will leave me with an operational card when I want it with minimal effort. I am also playing with some trivial code in the driver to allow the me to turn off the radio on the 802.11b card which would allow me to permanently load the driver again as well as save some power when on batteries but not using the wireless network. I still hope that this gets fixed and I will try Michael's patch as soon as I am in my Berkeley office where the problem occurs. I should also point out that this applies to -stable and that is where I will be testing since I have been unable to get 5.0 to see ANY PCcard inserted. (This showed up between DP1 and DP2.) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 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?20021231001134.42C0E5D04>