Subject: Re: kernel panics since 3/1: m_copym errors
To: Kentaro A. Kurahone <kurahone@sigusr1.org>
From: Patrick Welche <prlw1@newn.cam.ac.uk>
List: tech-net
Date: 03/09/2005 18:47:22
On Mon, Mar 07, 2005 at 10:23:58AM +0000, Kentaro A. Kurahone wrote:
> 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.
> > 
> > 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.

Could it be related to the strange packet lengths observed in

  http://mail-index.netbsd.org/current-users/2005/03/07/0027.html

?

Cheers,

Patrick