Re: bind fails with sig11 on start / pthread failure on ARM?

On Mon, Feb 15, 2010 at 10:39:07PM +0100, Bernd Walter wrote:
> [62]# uname -a
> FreeBSD  9.0-CURRENT FreeBSD 9.0-CURRENT #0 r203927: Mon Feb 15 19:12:36 CET 2010     ticso_at_cicely14.cicely.de:/data/builder/arm-current/head/sys/arm/compile/FBOX  arm
> [64]# /etc/rc.d/named start
> Starting named.
> /etc/rc.d/named: WARNING: failed to start named
> 1.000u 0.000s 0:03.94 54.0%     7446+33509k 0+0io 17pf+0w
> Exit 1
> 
> [65]# tail /var/log/messages 
> ...
> Feb 15 21:29:51  named[2567]: starting BIND 9.6.1-P3 -u bind
> Feb 15 21:29:51  named[2567]: built with '--prefix=/usr' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--enable-threads' '--disable-ipv6' '--enable-getifaddrs' '--disable-linux-caps' '--with-openssl=/usr' '--with-randomdev=/dev/random' '--without-idn' '--without-libxml2'
> Feb 15 21:29:51  kernel: pid 2567 (named), uid 0: exited on signal 11
> Feb 15 21:29:51  ticso: /etc/rc.d/named: WARNING: failed to start named
> 
> [66]# cat /etc/rc.conf 
> hostname="Please.tell.me.who.am.I"
> tmpmfs="AUTO"
> tmpsize="4m"
> tmpmfs_flags="-S -M"
> varmfs="AUTO"
> varsize="5m"
> varmfs_flags="-S -M"
> sshd_enable="YES"
> ntpdate_enable="YES"
> ntpdate_program="ntpdate"
> ntpd_enable="YES"
> thttpd_enable="NO"
> fsck_y_enable="YES"
> background_fsck="NO"
> gateway_enable="YES"
> named_enable="YES"
> named_chrootdir=""
> ifconfig_ate0="up"
> mpd_enable="NO"
> mpd_flags="-b"
> dhcpd_enable="NO"
> dhcpd_ifaces="vlan0"
> firewall_enable="YES"
> firewall_script="/etc/rc.ipfw"
> cloned_interfaces="vlan0 vlan1 vlan2 vlan3"
> ifconfig_vlan0="192.168.53.1/24 vlan 256 vlandev ate0"
> ifconfig_vlan1="vlan 257 vlandev ate0"
> ifconfig_vlan2="vlan 258 vlandev ate0"
> ifconfig_vlan3="vlan 259 vlandev ate0"
> 
> /etc/namedb isn't changed from distribution yet

[55]Please.tell.me.who.am.I# gdb /usr/sbin/named named.core 
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "arm-marcel-freebsd"...(no debugging symbols found)...
Core was generated by `named'.
Program terminated with signal 5, Trace/breakpoint trap.
Reading symbols from /lib/libcrypto.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libcrypto.so.6
Reading symbols from /lib/libthr.so.3...(no debugging symbols found)...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x203571b0 in _thread_bp_create () from /lib/libthr.so.3
[New Thread 20804280 (LWP 100062)]
[New Thread 20804140 (LWP 100052)]
(gdb) bt
#0  0x203571b0 in _thread_bp_create () from /lib/libthr.so.3
#1  0x203572b8 in _thread_bp_death () from /lib/libthr.so.3
#2  0x20349da4 in pthread_create () from /lib/libthr.so.3
#3  0x00164cb8 in ?? ()
(gdb) 

Do we have a general threading problem on ARM?

-- 
B.Walter <bernd_at_bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.