Date: Wed, 16 Nov 2005 08:43:14 +0100 From: "O. Hartmann" <ohartman@mail.uni-mainz.de> To: Michael Vince <mv@roq.com> Cc: amd64@freebsd.org Subject: Re: IPSec panic? Message-ID: <437AE312.4090709@mail.uni-mainz.de> In-Reply-To: <437A993B.8080204@roq.com> References: <cb5206420511151350n306305f4m806fa8884e3afdba@mail.gmail.com> <437A993B.8080204@roq.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. --------------040801010705030006020706 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Michael Vince wrote: > Andrew P. wrote: > >> I'm gravely sorry to annoy. I've googled for a little >> while and found out that IPSec panics are a known >> issue on amd64. Is it still so? >> >> I was surprised that setkey -D causes panic and >> a memory dump on my 6-Stable box. Come on, >> it's _FreeBSD_ for crying out loud. We can't live >> with that. >> >> I'm willing to help debugging this nasty thing if >> help's needed. >> _______________________________________________ >> >> > FAST_IPSEC broken on amd64 is still broken. As far as I know > VANHULLEBUS Yvan appears to be the most active IPSEC guy in FreeBSD > and he has talked about fixing it but probably hasn't got the time, > probably only money is a viable motivator if you wanted this problem > fixed soon. > > Mike Indeed, but IPSEC seems also to be broken. With IPSEC or FAST_IPSEC it is possible to force a crash as described further below in this thread. O. --------------040801010705030006020706--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?437AE312.4090709>