Date: Wed, 17 Aug 2011 07:52:51 -0700 From: =?iso-8859-1?Q?Ask_Bj=F8rn_Hansen?= <ask@develooper.com> To: net@freebsd.org, embedded@freebsd.org Subject: Re: system locks up with vr driver on alix board Message-ID: <F1B3D7C0-6AC7-4C10-9C99-AAC6A89D8415@develooper.com> In-Reply-To: <C64CDCB3-A1DE-48CF-BEE5-54BA7084B3CB@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>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_6413ECB9-93A9-41EC-9BEC-95B1379028E3 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi everyone, The box crashed early this morning. I didn't have BREAK_TO_DEBUGGER = enabled in the kernel so I couldn't get into the debugger. I fixed that = so hopefully I can get that next time. I haven't seen any vr errors (thanks for telling me how to). Indeed as = someone else pointed out, it's likely not related to 'vr' at all. When = it last hung the 'top' execution stopped about 15 minutes before the box = stopped routing packets; but during the last runs the interrupt "busy %" = according to top was only 30-ish percent. I didn't log the interrupt rate when it was crashing; but the ifconfig = and dmesg outputs didn't show anything. (Though my logging jobs might = have stopped well before the system failed, similar to the shell running = top). 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". - ask --Apple-Mail=_6413ECB9-93A9-41EC-9BEC-95B1379028E3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F1B3D7C0-6AC7-4C10-9C99-AAC6A89D8415>