dstumbler errors

I sent out an email about this a while back and didn't get any responses.
If anyone can confirm this behavior, please let me know.  I want to know if
it's just me and my machines, or something larger.

If I run dstumbler long enough, eventually I'll start getting these errors:

Jan 10 19:30:04  /kernel: wi0: timeout in wi_cmd 0x0002; event status 0x8000
Jan 10 19:30:04  /kernel: wi0: init failed
Jan 10 19:30:04  /kernel: wi0: wi_cmd: busy bit won't clear.
Jan 10 19:30:04  last message repeated 21 times
Jan 10 19:30:04  /kernel: wi0: failed to allocate 1594 bytes on NIC
Jan 10 19:30:04  /kernel: wi0: tx buffer allocation failed
Jan 10 19:30:04  /kernel: wi0: mgmt. buffer allocation failed

Sometimes these will start happening after 1 minute of running dstumbler,
sometimes after 10, but sooner or later, they start.  It's just a matter of
time.  And when it happens, it locks up the entire computer.  Other network
interfaces in the same machine stop responding to pings, I can't switch
virtual terminals, type anything in the keyboard, or do anything but pull
the power cord.  This has happened to me on my Compaq Prolinea 5500 desktop
machine, and my Dell Latitude CPi laptop.  It's happened with FreeBSD 4.5,
4.6.2, and 4.7.  It's also happened to me with SMC2632 card, as well as a
Linksys WPC11, and a D-Link DWL650.

Can anyone confirm this, or offer any solutions or suggestions?  I'd really
like to try to track down the problem to see if some kind of bug report
needs to be sent to the FreeBSD team, or if there is something h1kari can do
in a new release, etc.

Thanks!
Aaron