Subject: Re: wpi on NetBSD-4
To: Stephen Borrill <netbsd@precedence.co.uk>
From: Daniel Carosone <dan@geek.com.au>
List: tech-net
Date: 06/21/2007 10:34:28
--fb42B6XxWAcmD3wU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 15, 2007 at 03:27:15PM +0100, Stephen Borrill wrote:
>  I'm using NetBSD 4.0_BETA2 to build modular xorg packages with pkgsrc (l=
ocal=20
>  work dirs) mounted with NFS using a wpi(4) interface (i.e. reasonably he=
avy=20
>  use). After a while, the network status went to inactive and so I got nf=
s=20
>  send error 50.=20

There may be updates to the driver soon; perhaps they will help this.

>  I tried to ifconfig down/ifconfig up but got the following errors:
>  wpi0: could not allocate firmware DMA memory wpi0: could not load firmwa=
re
>=20
>  The firmware was clearly already loaded as I'd built up about 60 package=
s=20
>  using it!

The firmware is reloaded each time the chip is started, and the chip is
stopped (and I think/hope mostly powered off) when ifconfig'd down.

Unfortunately, the firmware loader has an annoying requirement to
allocate memory in a contiguous chunk, and that can fail after some
running time.  One way to work around this is to free up or page out
enough memory that there's a suitable chunk free.  Quitting a big app,
or something like:

 dd if=3D/dev/zero of=3D/dev/null bs=3D512m count=3D2

usually does the trick.  adjust bs according to the amount of physical
ram in the machine (ie don't make it larger so you're paging dd
itself).

Hopefully the underlying issue will be fixed with a smarter loader.

--
Dan.

--fb42B6XxWAcmD3wU
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (NetBSD)

iD8DBQFGeceTEAVxvV4N66cRAp7oAKDBbkj0lPxhzAWwO56F1KqYBOb9ygCfcg3O
elr0IfLsFeJJ4hAlcza+YW8=
=Cqe0
-----END PGP SIGNATURE-----

--fb42B6XxWAcmD3wU--