[Prism54-devel] Re: TxDescriptors -> 1024 default. Please not for every NIC!

[Luis R. Rodriguez]

--GVLQrlG8+/jMfW4X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, May 22, 2004 at 10:08:20PM +0300, Pekka Pietikainen wrote:
> On Thu, May 20, 2004 at 09:38:11AM -0700, Jean Tourrilhes wrote:
> > > Considering 802.11b's peak is at 11Mbit and standard 802.11g is at 54=
Mbit
> > > (some manufacturers are using two channels and getting 108Mbit now) I=
'd
> > > think we should stick at 100, as the patch proposes. Jean?
> > 	I personally would stick with 100. The IrDA stack runs
> > perfectly fine with 15 buffers at 4 Mb/s. If 100 is not enough, I
> > think the problem is not the number of buffers, but somewhere else.
> > For example, we might want to think about explicit socket callbacks
> > (like I did in IrDA).
> [removed netdev from Cc:]
>=20
> Ok, after some more debugging it seems like WEP (104-bit key) is the prob=
lem=20
> and not txqueuelen =3D=3D 1000 since WEP+txqueue =3D=3D 100 breaks too
>=20
> eth1: timeout waiting for mgmt response 1000, trigging device
> eth1: timeout waiting for mgmt response
> eth1: timeout waiting for mgmt response 1000, trigging device
> eth1: timeout waiting for mgmt response
> eth1: timeout waiting for mgmt response 1000, trigging device
> eth1: timeout waiting for mgmt response
>=20
> and without it it seems fine for days, with it and it sometimes hangs
> within hours...
>=20
> Any hints on where to start debugging? printk displaying what exactly
> it's waiting for etc?

Put the driver in debug and review printk's.

--=20
GnuPG Key fingerprint =3D 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

--GVLQrlG8+/jMfW4X
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAsDOTat1JN+IKUl4RAtvJAJ9MViUgYJaaqhCcuE3W1GW5jdNW3gCghGoy
g7TOXgs2XteOocy903tyoC4=
=DATK
-----END PGP SIGNATURE-----

--GVLQrlG8+/jMfW4X--