Date: Tue, 15 Nov 2005 22:18:11 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: "Andrew P." <infofarmer@gmail.com> Cc: amd64@freebsd.org Subject: Re: IPSec panic? Message-ID: <Pine.BSF.4.53.0511152206060.49213@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <cb5206420511151350n306305f4m806fa8884e3afdba@mail.gmail.com> References: <cb5206420511151350n306305f4m806fa8884e3afdba@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Nov 2005, 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. is it fast_ispec? best place to contriubte might be: http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/73211 I just gave it a try w/o any policy loaded and the bt looks like this: y2k# setkey -D [thread pid 471 tid 100057 ] Stopped at kdebug_sockaddr+0xb0: decl 0xffffffffffffff8d(%rax) db> where Tracing pid 471 tid 100057 td 0xffffff010bfc7750 kdebug_sockaddr() at kdebug_sockaddr+0xb0 raw_usend() at raw_usend+0x74 key_send() at key_send+0xa sosend() at sosend+0x726 kern_sendit() at kern_sendit+0x12f sendit() at sendit+0x1d3 sendto() at sendto+0x52 syscall() at syscall+0x350 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (133, FreeBSD ELF64, sendto), rip = 0x8007e9a6c, rsp = 0x7fffffff6b98, rbp = 0x2 --- db> show alllocks db> -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0511152206060.49213>