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

On Mon, Mar 07, 2005 at 06:45:48AM +0000, Geoff Wing wrote:
> Hisashi T Fujinaka <htodd@twofifty.com> typed:
> : I have a hard time reliably reproducing the error, though it occurs more
> : than once a day. After a panic the system isn't completely locked up so
> : I can get a stack trace, but I haven't figured out how to save it. The
> : only thing I remember from the stack trace is soo_close.
>=20
> My three variants (sorry, don't have kernel dates for them):
[snip]

Thanks.  It looks like there's more to this than just the SACK code.
I'll look into it further.

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

--6Nae48J/T25AfBN4
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iQIVAwUBQiwrvWfp+SLSG+tuAQKh/g//W1ykaPclpKHOsk3M2PABGvjstGdK2eh1
INtirWOBxM04SEj3nnZe3SQaIB2mVpcED0q9qgW/Mskd8iFu4Z50llASP8RzB4pr
J1zNNpARYOdWBFeKu4cDyipPn0zqQY1b1PGd4eUFP6T4wDxU78Pbjb45QCk9g/ef
tvf9OO1xqqm4Vodz1MVbPbu026eYu4alHbF/dLTVFWFY29IY0F6KVhuShIaC13Lo
ktk31CkN+Jd3R0OUvtYglrRgM8U93mmKwt05z97ZZIQLEKnjroQAcI4MmPUkM99Y
CbGkvuqex3L65C+/Tc4e08QDR9+ObL9tmtlV3lP7FAJXxebylDRzjE4nZqIRTmg3
kuVciNBlcB9PEHMOzZ2q/9A2HDghYCeDf7wyzYryVmLsV5+jjXY5otGzQUL5f668
QaQhy/PdwBvMW99npqH3xfC8Km/M+ZJyNllehy6prlPvx8sZE2Gw2WCJ28wSVUMa
pm0jsKZpq8H93AJUY7wSLGCmucpo9KJPRbZ51AhgaUa4wMgOqFbfGcdYXLX4reRm
kfNGhsvfWH+g/MHZDbqMRAryqkImN/5tqKZLvD80HY4W6ayXNW1Nz4DxgyE4+o52
tUCpww5z9cXwzbsNCMcMNB3FnJ1js90cLaybcLom2NU3lmbQ2GjtyJZ9PGHw6HKx
K3+Hp4lkFxk=
=YyMA
-----END PGP SIGNATURE-----

--6Nae48J/T25AfBN4--