From owner-freebsd-stable@FreeBSD.ORG Thu Dec 11 01:38:25 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4712C43C for ; Thu, 11 Dec 2014 01:38:25 +0000 (UTC) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id 9ACE9324 for ; Thu, 11 Dec 2014 01:38:23 +0000 (UTC) Received: from ppp14-2-30-215.lns21.adl2.internode.on.net (HELO leader.local) ([14.2.30.215]) by ipmail05.adl6.internode.on.net with ESMTP; 11 Dec 2014 12:08:21 +1030 Message-ID: <5488F58D.7060708@ShaneWare.Biz> Date: Thu, 11 Dec 2014 12:08:21 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: FreeBSD stable Subject: Help debugging stable/10 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2014 01:38:25 -0000 Since upgrading to 10.1 (RC2) I have had trouble getting uptimes greater than 1 day. I have little experience debugging the OS so could use some help. # uname -a FreeBSD leader.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r275364: Tue Dec 2 08:13:06 ACDT 2014 root@leader.local:/usr/obj/usr/src-stable/sys/GENERIC amd64 This is on an ASUS P8H61-M LE/USB3 corei5 8GB with 3x 2TB Seagate drives in raidz. Full backtraces and dmesg at http://shaneware.biz/freebsddebugdata/ The thing that breaks which forces me to reset the machine is that I am unable to start new processes. Existing processes continue to work I just can't start new ones. Some simple commands do work but top ps procstat usbconfig all fail to start. I have been able use script to get some backtraces from kgdb before restarting. Back in RC2 and 3 I had it freeze up leaving me to reset, since RC4 and now on stable I have been able to close up most processes before resetting. I don't know how to re-create this issue on command, but I just had 4 days uptime which is the best I've had in the last month. How do I find what is preventing new processes starting? What can I do to get more data when things go south? I noticed an odd thing in the backtrace today - Thread 16 (Thread 101376): #0 sched_switch (td=0xfffff8011c1e7000, newtd=, flags=) at /usr/src-stable/sys/kern/sched_ule.c:1945 #1 0x0000000000000020 in ?? () #2 0xfffffe021e5a8200 in ?? () #3 0xffffffff80913166 in malloc (size=, mtp=, flags=) at /usr/src-stable/sys/kern/kern_malloc.c:352 #4 0xec81485354415541 in ?? () #5 0x4dce894d00000268 in ?? () #6 0xd58949cc8949c789 in ?? () #7 0x9358253c8148fb89 in ?? () #8 0x850f000000008164 in ?? () #16890 0x067ee8f68944df89 in ?? () #16891 0x8618251c8948fdd7 in ?? () #16892 0x415b10c4834882c1 in ?? () #16893 0x0000000000c35d5e in ?? () #16894 0x0000000000000000 in ?? () Yes there are nearly 17,000 lines in that backtrace, no idea what it is though. -- FreeBSD - the place to B...Software Developing Shane Ambler