--pgp-sign-Multipart_Thu_Jul_21_20:20:11_2005-1
Content-Type: text/plain; charset=US-ASCII

>>>>> "mn" == Miles Nordin <carton@Ivy.NET> writes:

    mn> I found the problem also occurs with an hme card.

however, I get these messages in dmesg that i didn't get from gem:

hme0: status=400<MAXPKTERR>
hme0: status=400<MAXPKTERR>
hme0: status=400<MAXPKTERR>
hme0: status=400<MAXPKTERR>
hme0: status=500<SENTFRAME,MAXPKTERR>
hme0: status=400<MAXPKTERR>

There are ~30 of these over a day or so, many individual stalls.  I'm
not sure that every stall prints a console message, though.

3.0_BETA is still building.  There is no ALTQ patch for 3.0_BETA, and
PF/ALTQ still isn't integrated into NetBSD, so I'm not sure that's
ultimately going to work out for me, but I can at least report whether
it fixes these hme/gem problems before trying something else.

--pgp-sign-Multipart_Thu_Jul_21_20:20:11_2005-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iQCVAwUAQuA7u4nCBbTaW/4dAQLJ+wQApe3l7rgtNxsYPHMpWtEGf/xUhRcmcDsb
KZsI+BcIR0SeXk0c4KLiXdHKYVH0LTdub5yGU6TkUm8TCsiO8eK6sHAoY5IeSvty
bwklxzOiF++32cw9/KfZp8ppQAn34w1rvyXkmLvh7P+LtJ8G/9KxROOYQs7gDJXY
Z6csO1zfRJE=
=KoOO
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Thu_Jul_21_20:20:11_2005-1--