Date: Mon, 30 Dec 2002 14:10:20 -0800 From: Lee Damon <nomad@castle.org> To: current@freebsd.org Subject: Re: My wi(4) ate itself (or Fun with no memory). Message-ID: <200212302210.gBUMAKZc068550@castle.org> 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
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 <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?
>
> - 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212302210.gBUMAKZc068550>