Date: Wed, 17 Aug 2011 11:03:53 -0400 From: Mike Tancsa <mike@sentex.net> To: =?windows-1252?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com> Cc: embedded@freebsd.org, net@freebsd.org Subject: Re: system locks up with vr driver on alix board Message-ID: <4E4BD859.5070301@sentex.net> In-Reply-To: <F1B3D7C0-6AC7-4C10-9C99-AAC6A89D8415@develooper.com> References: <D8B41107-90ED-4357-A7DA-4FF987C70567@develooper.com> <4E4AB3BE.4090603@sentex.net> <9255C71C-BB78-417E-A900-85140FC2050C@develooper.com> <20110817002911.GA7614@michelle.cdnetworks.com> <C64CDCB3-A1DE-48CF-BEE5-54BA7084B3CB@develooper.com> <F1B3D7C0-6AC7-4C10-9C99-AAC6A89D8415@develooper.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Grasping at straws here, but when enabling BREAK_TO_DEBUGGER I noticed that the kernel had ZERO_COPY_SOCKETS and TCP_SIGNATURE enabled. I disabled those, "just in case". I have a couple of boxes with TCP_SIGNATURE (and IPSEC) in the kernel and they work fine. ZERO_COPY... not so sure of. Do you have any other non standard options in your kernel ? ---Mike ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E4BD859.5070301>