On 2016-06-19 10:06, Konstantin Belousov wrote:
> On Sun, Jun 19, 2016 at 09:10:08AM +0200, Daniel Engberg wrote:
>> Hi,
>>
>> Decided to try ALPHA4 and Samba 4.3 and 4.4 doesn't seem very happy.
>>
>> Fatal error 'mutex 0x8013ec000 own 0x18cdc is on list 0x8112161a0 0x0' at 
>> line 153 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 4)
>> [2016/06/19 01:14:47.689256,  0] ../lib/util/fault.c:78(fault_report)
>>   ===============================================================
>> [2016/06/19 01:14:47.689450,  0] ../lib/util/fault.c:79(fault_report)
>>   INTERNAL ERROR: Signal 6 in pid 45222 (4.4.3)
>>   Please read the Trouble-Shooting section of the Samba HOWTO
>> [2016/06/19 01:14:47.689479,  0] ../lib/util/fault.c:81(fault_report)
>>   ===============================================================
>> [2016/06/19 01:14:47.689498,  0] ../source3/lib/util.c:791(smb_panic_s3)
>>   PANIC (pid 45222): internal error
>> [2016/06/19 01:14:47.690577,  0] ../source3/lib/util.c:902(log_stack_trace)
>>   BACKTRACE: 6 stack frames:
>>    #0 0x803c16fe8 <log_stack_trace+0x28> at 
>> /usr/local/lib/samba4/libsmbconf.so.0
>>    #1 0x803c16ed2 <smb_panic_s3+0x52> at 
>> /usr/local/lib/samba4/libsmbconf.so.0
>>    #2 0x801696dad <smb_panic+0x13d> at 
>> /usr/local/lib/samba4/libsamba-util.so.0
>>    #3 0x801696c57 <fault_setup+0x157> at 
>> /usr/local/lib/samba4/libsamba-util.so.0
>>    #4 0x8014616df <pthread_sigmask+0x4ff> at /lib/libthr.so.3
>>    #5 0x801460cbf <pthread_getspecific+0xe9f> at /lib/libthr.so.3
>> [2016/06/19 01:14:47.690686,  0] ../source3/lib/dumpcore.c:313(dump_core)
>>   unable to change to %N.core
>>   refusing to dump core
>>
>> Fatal error 'mutex 0x8013eb000 own 0x18d3d is on list 0x812e161a0 0x0' at 
>> line 153 in file /usr/src/lib/libthr/thread/thr_mutex.c (errno = 4)
>> [2016/06/19 01:26:41.063681,  0] ../lib/util/fault.c:78(fault_report)
>>   ===============================================================
>> [2016/06/19 01:26:41.063827,  0] ../lib/util/fault.c:79(fault_report)
>>   INTERNAL ERROR: Signal 6 in pid 61297 (4.3.9)
>>   Please read the Trouble-Shooting section of the Samba HOWTO
>> [2016/06/19 01:26:41.063844,  0] ../lib/util/fault.c:81(fault_report)
>>   ===============================================================
>> [2016/06/19 01:26:41.063855,  0] ../source3/lib/util.c:789(smb_panic_s3)
>>   PANIC (pid 61297): internal error
>> [2016/06/19 01:26:41.064679,  0] ../source3/lib/util.c:900(log_stack_trace)
>>   BACKTRACE: 6 stack frames:
>>    #0 0x803846eb8 <log_stack_trace+0x28> at /usr/local/lib/libsmbconf.so.0
>>    #1 0x803846da2 <smb_panic_s3+0x52> at /usr/local/lib/libsmbconf.so.0
>>    #2 0x80168c12d <smb_panic+0x13d> at /usr/local/lib/libsamba-util.so.0
>>    #3 0x80168bfd7 <fault_setup+0x157> at /usr/local/lib/libsamba-util.so.0
>>    #4 0x8014606df <pthread_sigmask+0x4ff> at /lib/libthr.so.3
>>    #5 0x80145fcbf <pthread_getspecific+0xe9f> at /lib/libthr.so.3
>> [2016/06/19 01:26:41.064747,  0] ../source3/lib/dumpcore.c:313(dump_core)
>>   unable to change to %N.core
>>   refusing to dump core
>>
>> This occurs immediately when you start Samba so it's easy to replicate.
>> I know that 4.3 worked on r298887 for sure, I'm going to try this in VM too 
>> but I'd apperciate if anyone else could give this a go.
>>
>> I noticed that there were some changes in libthr which might be a clue....
>>
> 
> Please convince samba to allow to dump core on assert (I have no idea how),
> then get a backtrace from the core, using ports/devel/gdb.  After that I
> may know where to look next.
> 
Hi,

Thanks for the quick reply, I'm not familiar to gdb but from what I found this 
seems to be correct way.

sysctl kern.corefile=/var/log/samba4/%N.core (for whatever reason %N.core only 
doesn't seem to make Samba happy)

/usr/local/bin/gdb /usr/local/sbin/smbd /var/log/samba4/smbd.core
GNU gdb (GDB) 7.11.1 [GDB v7.11.1 for FreeBSD]
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd11.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/sbin/smbd...done.
[New LWP 101688]
Core was generated by `smbd'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00000008055ed10a in ?? ()
(gdb) bt
#0  0x00000008055ed10a in ?? ()
#1  0x00000008055ed0db in ?? ()
#2  0x0000000000018d38 in ?? ()
#3  0x8979efeec3bd9290 in ?? ()
#4  0x00007fffffffd2a4 in ?? ()
#5  0x00000008020f6020 in ?? ()
#6  0x00007fffffffd2c0 in ?? ()
#7  0x00000008055ed049 in ?? ()
#8  0x0000000000000000 in ?? ()

I guess that doesn't help much.... (debug option enabled in Samba port)

Disabled following lines in /etc/make.conf and recompiled Samba

# WITHOUT_DEBUG=YES
# MK_PROFILE=no

/usr/ports/net/samba44 # gdb /usr/local/sbin/smbd /var/log/samba4/smbd.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 "amd64-marcel-freebsd"...
Core was generated by `smbd'.
Program terminated with signal 6, Aborted.
#0  0x0000000805ce110a in ?? ()
(gdb) bt
#0  0x0000000805ce110a in ?? ()
#1  0x0000000805ce10db in ?? ()
#2  0x0000000000018d31 in ?? ()
#3  0x3a0c606c1a35133b in ?? ()
#4  0x00007fffffffce04 in ?? ()
#5  0x0000000000000006 in ?? ()
#6  0x00007fffffffce20 in ?? ()
#7  0x0000000805ce1049 in ?? ()
#8  0x0000000000000000 in ?? ()

I have the following in /etc/src.conf

MALLOC_PRODUCTION=yes
WITHOUT_DEBUG_FILES=1
WITHOUT_LIB32=1
WITHOUT_KERNEL_SYMBOLS=yes

and disabled the following in kernel config

#makeoptions    DEBUG=-g                # Build kernel with gdb(1) debug symbols
#makeoptions    WITH_CTF=1              # Run ctfconvert(1) for DTrace support

# Debugging support.  Always need this:
#options        KDB                     # Enable kernel debugger support.
#options        KDB_TRACE               # Print a stack trace for a panic.
# For full debugger support use (turn off in stable branch):
#options        DDB                     # Support DDB.
#options        GDB                     # Support remote GDB.
#options        DEADLKRES               # Enable the deadlock resolver
#options        INVARIANTS              # Enable calls of extra sanity checking
#options        INVARIANT_SUPPORT       # Extra sanity checks of internal 
structures, required by INVARIANTS
#options        WITNESS                 # Enable checks to detect deadlocks and 
cycles
#options        WITNESS_SKIPSPIN        # Don't run witness on spinlocks for 
speed
#options        MALLOC_DEBUG_MAXZONES=8 # Separate malloc(9) zones

So I guess I need to turn all this on again and recompile everything *sigh*, 
I'll do that and in the meantime try to replicate this in a VM.

Best regards,
Daniel
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to