On Sat, Oct 02, 2010 at 10:46:59PM -0600, Devin Reade wrote: > I've got a problem where I have a couple of OpenBSD firewalls > running in a redundant configuration using carp, and have found > that CentOS 5.5 (Linux) boxes running on a protected network, if > they have avahi-daemon running, will cause the OpenBSD kernels to lock > up hard. This is very reproducable. > > While I can avoid the problem by not running avahi-daemon on the > Linux machines, I'd really prefer to find the source of the problem > on the OpenBSD side and fix it. From my perspective, there is nothing > that a remote host should be able to do that should lock up a > an OpenBSD kernel. (And lest anyone be offended by my calling it a > problem on the OpenBSD side, I'm quite willing to believe that there > is bad ju-ju in my config and am not necessarily blaming OpenBSD per se.) > > If anyone has suggestions on how I can proceed to diagnose the problem, > I would appreciate it. > > Details follow.
You seem to be using a custom compiled kernel. I didn't spot any explanation of that (-stable patches? changes to kernel config?). Non-GENERIC kernels make developers nervous. You could try to set ddb.console=1 in /etc/sysctl.conf. Then when the problem occurs <ctrl><alt><esc> may get you into ddb>. This in turn may show where the system is hanging. 'ps' will at least show who is waiting on what. Finally you could try a -current snapshot to verify that the problem has not already been fixed. .... Ken
