Date: Mon, 24 Sep 2007 00:38:33 -0700 From: Christopher Cowart <ccowart@rescomp.berkeley.edu> To: freebsd-net@freebsd.org Subject: Re: Racoon(ipsec-tools) enters sbwait state or 100% CPU utilization quite often on RELENG_1_2 Message-ID: <20070924073833.GM19429@hal.rescomp.berkeley.edu> In-Reply-To: <d5992baf0708200943h708f4a21xd111a5264a7f4f65@mail.gmail.com> References: <d5992baf0708171353j7e7563a8y8dca4475779bc410@mail.gmail.com> <20070818102803.GA1319@jayce.zen.inc> <d5992baf0708181258t501e5842y6b8bdee8a5c2e07c@mail.gmail.com> <m27ins2pby.wl%gnn@neville-neil.com> <20070820082728.GA28863@zen.inc> <d5992baf0708200943h708f4a21xd111a5264a7f4f65@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--fBvfXcdybK7Zhu+D Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 20, 2007 at 12:43:25PM -0400, Scott Ullrich wrote: > On 8/20/07, VANHULLEBUS Yvan <vanhu_bsd@zeninc.net> wrote: > > I tracked down the problem a few years ago, on FreeBSD 4.11, with > > KAME's IPSec stack. > > > > But the problem was not really in the stack itself, but rather in > > socket processing (in other words: not in netkey/*, but in > > kern/uipc_socket2.c). > > > > And as both IPSec stacks shares some PFKey constraints (for example > > one message per entry when dumping SADB / SPD), I guess the same > > problem existed in FAST_IPSEC. > > > > But when I had some time a few months ago to start filling a PR for > > the problem, I had a look at FreeBSD6 source code, and I noticed that > > sbspace macro (which was a quite important part of the problem) has > > changed, and I didn't have the required setup to do the test again, so > > I just can't be really sure the problem still exists... > > > > But the reported problem really has similar symptoms..... >=20 > Thank you Yvan and George! >=20 > The PR has been filed and the ID# is >=20 > kern/115651 >=20 > I have added some interesting notes that seem to affect NetBSD as well. >=20 > We will be happy to work with anyone to get this solved and access to > the machine in question is available if need be. I'd also like to express an interest in helping with this problem in any way possible. We're running into the same problem on our fileservers and have had to rollback a large project when we unexpectedly discovered the problem. Thanks, --=20 Chris Cowart Lead Systems Administrator Network & Infrastructure Services, RSSP-IT UC Berkeley --fBvfXcdybK7Zhu+D Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iQIVAwUBRvdpeSPHEDszU3zYAQIukQ/5ARJGBR5UNaKsurezCqlM9AvFNhAhEJm8 o6Yl1AEfZwNX0gsQAnANdYrftuo7+EjDyhtulL+dDWqAROHf9iDrvslXy61cZJY4 nnWLOTB2ygF/3LhRFpqggUCcjF8r3HfF9GeLsH7MqUkL6zkGeqnlmsZSMATCwbPv tS0rKMRXY92rx5XIl1Cb3OKGzfu1/4ARbBppMyWUN6c/zlISuJujrY8fkKlY+D/C vMQFQsT3/bqnK+yKoEfBZzVQZ8jS6YVfX89pEDDa4j1bm+FF9nA0ElW024m9qqE7 IrEsmU/2ot4pLYqV5mzqmpSupyg9x+gLxI+ByLpSnm4KrQhQQuts/0A278FikUZo Gsav1CF7g4zut5uz75hmHUrFySjYtQF9bulU+TZlsKK214fsQFLROv1T6qWhaEHu 9DradWNrIV/ySi3XIc2OMKn7IQ3phSqq3OVAJK1/eDF/CayaILQTScexO3434G+I ShnFtR0LvWudEhNR2Fq5ooYe6jLG+4ylGB5Tq98QFBysOXPKAZ8uduitp2Tgd7JS 2J4ljk1SjjIBCRKdvBInAcAKCXX+gxR6kqYSgIiDeX1X9nJxOQHLElQxkCd5FIRU sEhA9BlFVH6JDdfdsvyoFhTguwKvBgeJJHlZtxR42MzJzos04j8vLVvXLeRFoBgB oAwhvcm30tU= =MNBZ -----END PGP SIGNATURE----- --fBvfXcdybK7Zhu+D--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070924073833.GM19429>