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

On Tue, Apr 19, 2005 at 02:20:36PM -0700, Hisashi T Fujinaka wrote:
> On Tue, 19 Apr 2005, Markus W Kilbinger wrote:
>=20
> >Sounds/looks very similar similar to my
> >
> > kern/29787
> >
> >where I could catch such a panic within a serial remote console in the
> >meantime.
> >
> >My presumed wm driver relation could be pure random though it's still
> >the only machine showing such panics.
> >
> >Setting net.inet.tcp{,6}.sack.enable=3D0 seems to avoid these panics.
>=20
> They changed it from net.inet.tcp.sack? Just FYI, this error occur for
> me on a single fxp, and also ocurred on a single Linksys (rtk? can't
> remember).

Yes, it got changed because there's more SACK related sysctls now.

FWIW, the nics that I've been using to test this the most are
rtk, iwi, and wi.  And I have yet to be able to reproduce this even
after moderately heavy use.

--=20
Kentaro A. Kurahone
SIGUSR1 Research and Development

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)

iQIVAwUBQmWJ72fp+SLSG+tuAQKmAw//btr3zE5159L806EmHrfN3EcSRikuPrf+
WFJacWcB89Y6VbJLW9qy+U6eQN3G/h3rhR0zHNZKhdb0EpZZopBwwLa595B69eh2
vi0j1T3FkPJQX1mHI9e+nMwFC9V9dwTOvWmy82+urixh9pL2C5iqqnLTY+tEzt+y
L4W/hjU8xqNs2nmMta6hKegppU45ks/lk2z8E8yya2ZHWqzM0VJsA0X6sB+vaR6v
PPJqSCmG7U3xfupXdDYnJOpuivPeYu60Dwp5szZ5Gcurbvr+nD7cfHSFi1zzS+VW
WMyV/fvDgzBLC+NaFyUJ8+xZLqgsat+qTW+qYrnp1pD+ToiKerp0th8CAaxmErVu
yTov5Y1CgblBm0LUSK1kw+LDAOJIK3qTRwJMdfgpHPbEF771ijfChAibIo1sLMto
poHOuHK4a1MsJpWLKlmL24CQi48P9dKfvDErMGMQUeZelh4dUbAqr8+oRYyd0IKe
6p7WuS1DbsBk4VGLwFAu+gy9AYZaCizelirx+o+i3GwoHiOHWMMRKpgf7znmMZVV
5MznuZL1HsSYUOQUFi4CoK/MB0Qop2P0SGOKtV0gXT/M4K/rjq2IfnibgBbVxamM
Shy5WVG252XQdh1O37D/CfN+rEU+blbx5+0FvFFUJfvK5gbdjyJpXPVw6zIbPeJQ
or4MAhDMV1U=
=c9VR
-----END PGP SIGNATURE-----

--vkogqOf2sHV7VnPd--