From owner-freebsd-current@freebsd.org Sun Aug 27 04:51:54 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60B3FDE74D2; Sun, 27 Aug 2017 04:51:54 +0000 (UTC) (envelope-from rlibby@gmail.com) Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36318653FC; Sun, 27 Aug 2017 04:51:54 +0000 (UTC) (envelope-from rlibby@gmail.com) Received: by mail-pf0-x230.google.com with SMTP id r62so6687389pfj.0; Sat, 26 Aug 2017 21:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=V5IiacMvApYtqoP6AfNVrCyHRg+tv7rMabWHTy9F11k=; b=hY0f0zoZ/cMSCuMVtBYmULy7uRcM41we9MGvq0UrWSLMUURfeibREJhNv2HklosSu/ BUzNvPCIqprCegrF1rj43XFCI0aH1C/Y68sfIuGwv2j9ksehkQE7BU4WRN+DxRvX7AgY LFC1yHwC3mXChu3VOE3T1K7VixV6blr/B4g3p0sgHqKEfJvs8d9kaWavKWpZgnB9AF71 At85HMg5bM4VMZmB5UMgdtXl7PrrGSNtmOqATfSHEDwjAPeEx3xE+YHVK/o4P13RfE8y XflE1qbZVSeAxLE7SWkYJ7/e/JWajbQW6gzg2X8mzc27vI7RU25VGLm8Fvxd5TlsbTA5 pQ+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=V5IiacMvApYtqoP6AfNVrCyHRg+tv7rMabWHTy9F11k=; b=K9XwzFH+GmsdapH/cCJywdQAc1S5iCYb7NHGFXs0NViKWYNfqA2gNajFSNK0TSho2C MMwXRO0PJTAss9Bsm7hV2Z83TWwJp9juygCav7HJsJHDd9tH6QTQzo0QpzxwvVr5se78 RYBCS0Kij2GjaREpxBmSwirjaVW+D1vcAqoL18X62IwZSmIYMLpdWR6vF4u3ynKS1JOs otGJk5ZGYP/iCPElTd3tdNlAj03ROV/mvfd690pvnQmHANjTa4IRuInB6S4S2j0kl0sX mgQzdRS69ZSV40HC9xgOdmhDrI/DHIIqZgYXoNHSVNUs4RoqQ78ZgwE/bZ1O7aCegEPJ 41eA== X-Gm-Message-State: AHYfb5jQMCJcxRoG+SoBopNlrHd7N9x2PWy/V+GDmwSvnC3InutbZO20 lttqW5Q1xHMV3HlE2z8YFER7sr2rFA== X-Received: by 10.84.232.10 with SMTP id h10mr3778390plk.261.1503809513373; Sat, 26 Aug 2017 21:51:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.207.193 with HTTP; Sat, 26 Aug 2017 21:51:52 -0700 (PDT) In-Reply-To: References: From: Ryan Libby Date: Sat, 26 Aug 2017 21:51:52 -0700 Message-ID: Subject: Re: Compiling the kernel using GCC To: Aijaz Baig Cc: FreeBSD Hackers , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Aug 2017 04:51:54 -0000 On Sat, Aug 26, 2017 at 2:41 AM, Aijaz Baig wrote: > Has anyone been able to successfully compile the kernel using GCC as > against CLANG the default compiler on most later versions of FreeBSD? I was > able to successfully buildworld. After which I reboot and now /usr/bin/cc > points to GCC as requested. However kernel fails to link [...] > make -D KERNFAST -m /usr/src/share/mk KERNEL=kernel all -DNO_MODULES_OBJ > linking kernel.full > ck_array.o: In function `ck_cc_popcount': > /usr/src/sys/contrib/ck/include/gcc/ck_cc.h:139: undefined reference to > `__popcountdi2' [...] Do you need ck? Can you share your KERNCONF? And the branch and revision you are building? I have been building an amd64 GENERIC kernel on head with various gccs. I think that does not build ck. The main method I have been focusing on for now is make CROSS_TOOLCHAIN=amd64-gcc TARGET=amd64 TARGET_ARCH=amd64 buildkernel with the amd64-xtoolchain-gcc-0.2 package installed. But I have also built kernel-only successfully with gcc 6 with src.conf e.g. as below. % cat /etc/src.conf.gcc6 WITH_GCC=yes WITH_GCC_BOOTSTRAP=yes WITH_GCC_IS_CC=yes WITHOUT_CLANG=yes WITHOUT_CLANG_BOOTSTRAP=yes WITHOUT_CLANG_IS_CC=yes WITHOUT_FORMAT_EXTENSIONS=yes CC=/usr/local/bin/gcc6 CXX=/usr/local/bin/g++6 From owner-freebsd-current@freebsd.org Mon Aug 28 06:55:11 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3D1FE074E6 for ; Mon, 28 Aug 2017 06:55:11 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D31E6B911 for ; Mon, 28 Aug 2017 06:55:11 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-yw0-x22c.google.com with SMTP id s187so12068387ywf.2 for ; Sun, 27 Aug 2017 23:55:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DvodAsPZpi2wonsgqc1V0TKjRmiLF0x3zShDcRQIQuw=; b=O9zCMtlK22rDzs/GFznZmXLiUSnwGnZN9OWsuGmuqHCVuxlUsSCwWrcFtFPZ8FT8NB 9PyCvdH6nYRwlnmN767kQMdbPyARuVFduIhl7FZ+/qyrZsU5LjO2QajJ3/yNW6u9BPS0 AeDWxRWXPkeajxgFmWtyv+tS4RAhQNTGMCZMFcQPzmUhr7e0YeF0RuRqYVUuwieUkkXb Ivd1TAM6Dy00HAcf6kXLHci8fDL3+KT8TR+SB3t5ATQHb0Se5yLU1vPETrly7lU/0zHE AQ4+QdJ7RTiISH/0082nfmusdq49x0MRLGJm+IpwA/qeSZG3AQ1n9zEjj6iSE0TXlv1H Wfhw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DvodAsPZpi2wonsgqc1V0TKjRmiLF0x3zShDcRQIQuw=; b=QmT7+zxty0O0hanPfrTWYO1PV/zaLWTCHSt5Ev+/4o7nndjUw1SXm4zmSmzjFdWAxP 5cAY+jTRaKsJnBb9jpXD9MzRcSNlY1Rz9BuD19UdkO1bWF6tVBsoSWF1rz1My6DNFguI t+mh8icJM92dcWBlUtNC5aYOuFVDe0rISJqzqjSKEhRY/WddmEaCwRjXbbSTRMDq3G1A /qaamfTyqwXowAXLvjctovBgmnV7z75XZh9g0L+AxE/rJlEkCiP9W08EJKteeQNA92fp jnTdKmBRY0QRfRYsoddab5N0/Z7w350jahTuF97P20BTISHDKcGB/RSz32zR6NwgqV0Y R+Lg== X-Gm-Message-State: AHYfb5jIiN96dK8QbsW4o3w2LJgH1MGJA3h/AMqDHAikFLRXR1A3lOkb zJnhRw0ajMopjCGaSJdcDyu+cyKSntf7 X-Received: by 10.129.50.206 with SMTP id y197mr2857517ywy.314.1503903310687; Sun, 27 Aug 2017 23:55:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.227.193 with HTTP; Sun, 27 Aug 2017 23:54:40 -0700 (PDT) In-Reply-To: References: <1C5A448F-C91A-4599-8500-E4E46E6F5205@dsl-only.net> From: Ed Schouten Date: Mon, 28 Aug 2017 08:54:40 +0200 Message-ID: Subject: Re: svn commit: r322875 - head/sys/dev/nvme To: Mark Millard Cc: David Chisnall , Warner Losh , svn-src-head@freebsd.org, FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 06:55:12 -0000 Mark, 2017-08-25 14:53 GMT+02:00 Ed Schouten : > 2017-08-25 9:46 GMT+02:00 Mark Millard : >> It appears that at least 11.1-STABLE -r322807 does not handle >> -std=c++98 styles of use of _Static_assert for g++7 in that >> g++7 reports an error: > > Maybe we need to do something like this? > > Index: sys/sys/cdefs.h > =================================================================== > --- sys/sys/cdefs.h (revision 322887) > +++ sys/sys/cdefs.h (working copy) > @@ -294,7 +294,7 @@ > #if (defined(__cplusplus) && __cplusplus >= 201103L) || \ > __has_extension(cxx_static_assert) > #define _Static_assert(x, y) static_assert(x, y) > -#elif __GNUC_PREREQ__(4,6) > +#elif __GNUC_PREREQ__(4,6) && !defined(__cplusplus) > /* Nothing, gcc 4.6 and higher has _Static_assert built-in */ > #elif defined(__COUNTER__) > #define _Static_assert(x, y) __Static_assert(x, __COUNTER__) Could you let me know whether this patch fixes the build for you? If so, I'll commit it! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 From owner-freebsd-current@freebsd.org Mon Aug 28 09:02:14 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE689E09403 for ; Mon, 28 Aug 2017 09:02:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-57.reflexion.net [208.70.210.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9DA486EFCA for ; Mon, 28 Aug 2017 09:02:14 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 2936 invoked from network); 28 Aug 2017 09:02:07 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 28 Aug 2017 09:02:07 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.2) with SMTP; Mon, 28 Aug 2017 05:02:07 -0400 (EDT) Received: (qmail 3497 invoked from network); 28 Aug 2017 09:02:07 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 28 Aug 2017 09:02:07 -0000 Received: from [192.168.1.109] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 54F3EEC8816; Mon, 28 Aug 2017 02:02:06 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: svn commit: r322875 - head/sys/dev/nvme From: Mark Millard In-Reply-To: Date: Mon, 28 Aug 2017 02:02:05 -0700 Cc: David Chisnall , Warner Losh , svn-src-head@freebsd.org, FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers Content-Transfer-Encoding: 7bit Message-Id: <0639EC0E-1F0F-4CB0-A3FE-4E8CD814B6D3@dsl-only.net> References: <1C5A448F-C91A-4599-8500-E4E46E6F5205@dsl-only.net> To: Ed Schouten X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 09:02:15 -0000 On 2017-Aug-27, at 11:54 PM, Ed Schouten wrote: > 2017-08-25 14:53 GMT+02:00 Ed Schouten : >> 2017-08-25 9:46 GMT+02:00 Mark Millard : >>> It appears that at least 11.1-STABLE -r322807 does not handle >>> -std=c++98 styles of use of _Static_assert for g++7 in that >>> g++7 reports an error: >> >> Maybe we need to do something like this? >> >> Index: sys/sys/cdefs.h >> =================================================================== >> --- sys/sys/cdefs.h (revision 322887) >> +++ sys/sys/cdefs.h (working copy) >> @@ -294,7 +294,7 @@ >> #if (defined(__cplusplus) && __cplusplus >= 201103L) || \ >> __has_extension(cxx_static_assert) >> #define _Static_assert(x, y) static_assert(x, y) >> -#elif __GNUC_PREREQ__(4,6) >> +#elif __GNUC_PREREQ__(4,6) && !defined(__cplusplus) >> /* Nothing, gcc 4.6 and higher has _Static_assert built-in */ >> #elif defined(__COUNTER__) >> #define _Static_assert(x, y) __Static_assert(x, __COUNTER__) > > Could you let me know whether this patch fixes the build for you? If > so, I'll commit it! As a variant of stable/11 -r322807 . . . buildworld and buildkernel seem to work fine. (I did not try any port [re-]builds.) Based on the same main.cc as before . . . g++7 -std=c++98 main.cc g++7 -Wpedantic -std=c++98 main.cc g++7 -std=c++03 main.cc g++7 -Wpedantic -std=c++03 main.cc no longer complain (so no error, no warning). clang++ -Wpedantic -std=c++11 main.cc clang++ -Wpedantic -std=c++98 main.cc clang++ -Wpedantic -std=c++03 main.cc each still give the warning but no error. g++7 -Wpedantic -std=c++11 main.cc g++7 -std=c++11 main.cc clang++ -std=c++11 main.cc clang++ -std=c++98 main.cc clang++ -std=c++03 main.cc are still silent, no errors, no warnings. Note that clang here is version 4 --the same as in my original report that had the g++7 rejection example. This is because of the stable/11 context that I used. (An intended MFC had been listed.) If needed I could probably try under some version of head (and so test clang version 5). === Mark Millard markmi at dsl-only.net From owner-freebsd-current@freebsd.org Mon Aug 28 09:36:49 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3EECE09D3A for ; Mon, 28 Aug 2017 09:36:49 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F03D70174 for ; Mon, 28 Aug 2017 09:36:49 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-yw0-x230.google.com with SMTP id h127so26197848ywf.3 for ; Mon, 28 Aug 2017 02:36:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u/B4CIKTIpXtJTDiWp0pYzBNCK+pwX/dz8cXZe59aU8=; b=OwN4Jvtgsv4wQf6E8c3As7Ou7Z1YkhCYLnKYu8zHXGLKeyX+xTCHlpOBDvhVe10Zvq ElF9ntamn5VUAT/O7Ez2jGTc0rpMacYEWoo6q6BMzQjcfUp+d96BwKq664r9s5MHIkvJ xxfTWcZ4M36HU7iv5qlXL82htQWtiGdhaAtf2Irc8hLIJUVgf9LP48HZ1TNMrM7yjWVA 3nK2iFESEU1UiAlnzZu669y9XN63++gj2rilZo/Qf0hhsMSY2/fq/j/avj/qX1V8ZUJX lXIHdMsBMYYslASPcMxtYzzYv1IHHwyK9mEfjqZD5oRw4+gBERdnYINkmcCvEOPAtk1M 0LZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u/B4CIKTIpXtJTDiWp0pYzBNCK+pwX/dz8cXZe59aU8=; b=EsVoK/8dgZoucSjjDld4WiJMbtQzhYFmQKb7WGMY5vGw5TSnhrTyCQJDlg+zCsh9BY ayiPU4rHP+Q56v79LT0R5aQ3SMUbu9nk7LCyDhM3rPqU7SaiGaQ9o+R64tSKn3tkPeHy rcwl1qxqX9JuhLAJNIacuvA7211G8whIPvspXeBkuiggC1OPRFLjWB7F3q/jxHylS6f/ dM6OAkYMtXPtH/PnyaCuJnfAEp4pveRsOUucclMnXpUXVodx0Zqq5ol1DOh8wZRs4gYN T2OQ/ZQbnk5/QwAT1fEHFSOV6SK3lmgLxXhwGDkG8+qa+Hmkq8dsG43ZVXH/JmAU/X0L AR3w== X-Gm-Message-State: AHYfb5i4rAtDGkO3gcsm7ocjrV/dzw30D6rW9C3RmM4xxQFKxl9aBDqT LQ02ojrWrGxQqCaaoYlAKKaK/zHtjA9W X-Received: by 10.37.171.208 with SMTP id v74mr5173459ybi.99.1503913008729; Mon, 28 Aug 2017 02:36:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.227.193 with HTTP; Mon, 28 Aug 2017 02:36:18 -0700 (PDT) In-Reply-To: <0639EC0E-1F0F-4CB0-A3FE-4E8CD814B6D3@dsl-only.net> References: <1C5A448F-C91A-4599-8500-E4E46E6F5205@dsl-only.net> <0639EC0E-1F0F-4CB0-A3FE-4E8CD814B6D3@dsl-only.net> From: Ed Schouten Date: Mon, 28 Aug 2017 11:36:18 +0200 Message-ID: Subject: Re: svn commit: r322875 - head/sys/dev/nvme To: Mark Millard Cc: David Chisnall , Warner Losh , svn-src-head@freebsd.org, FreeBSD Current , FreeBSD-STABLE Mailing List , freebsd-hackers Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2017 09:36:49 -0000 2017-08-28 11:02 GMT+02:00 Mark Millard : > Based on the same main.cc as before . . . > > g++7 -std=c++98 main.cc > g++7 -Wpedantic -std=c++98 main.cc > g++7 -std=c++03 main.cc > g++7 -Wpedantic -std=c++03 main.cc > > no longer complain (so no error, no > warning). Perfect! I've committed this change as r322965. Thanks for testing! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands KvK-nr.: 62051717 From owner-freebsd-current@freebsd.org Tue Aug 29 17:28:31 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF12EDE1161 for ; Tue, 29 Aug 2017 17:28:31 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id B75346AE43 for ; Tue, 29 Aug 2017 17:28:31 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: by mailman.ysv.freebsd.org (Postfix) id B34E6DE1160; Tue, 29 Aug 2017 17:28:31 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2DD1DE115F for ; Tue, 29 Aug 2017 17:28:31 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp.rcn.com (smtp.rcn.com [69.168.97.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 811946AE41 for ; Tue, 29 Aug 2017 17:28:31 +0000 (UTC) (envelope-from roberthuff@rcn.com) X_CMAE_Category: , , X-CNFS-Analysis: v=2.2 cv=GvQAwQ9C c=1 sm=1 tr=0 a=9TgA2UwI6Wy+6BV4wQM/cQ==:117 a=9TgA2UwI6Wy+6BV4wQM/cQ==:17 a=L9H7d07YOLsA:10 a=kj9zAlcOel0A:10 a=pv7qRjvMeqzY1ZAfz2AA:9 a=CjuIK1q_8ugA:10 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine X-Authed-Username: cm9iZXJ0aHVmZkByY24uY29t Authentication-Results: smtp01.rcn.cmh.synacor.com smtp.mail=roberthuff@rcn.com; spf=neutral; sender-id=neutral Authentication-Results: smtp01.rcn.cmh.synacor.com smtp.user=roberthuff; auth=pass (PLAIN) Received-SPF: neutral (smtp01.rcn.cmh.synacor.com: 209.6.230.48 is neither permitted nor denied by domain of rcn.com) Received: from [209.6.230.48] ([209.6.230.48:14529] helo=jerusalem.litteratus.org.litteratus.org) by smtp.rcn.com (envelope-from ) (ecelerity 3.6.23.54417 r(Core:3.6.23.0)) with ESMTPSA (cipher=AES256-GCM-SHA384) id D1/1C-18918-D34A5A95; Tue, 29 Aug 2017 13:28:29 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <22949.42044.875179.603888@jerusalem.litteratus.org> Date: Tue, 29 Aug 2017 13:28:28 -0400 To: current@freebsd.org CC: roberthuff@rcn.com Subject: questions re updating to -CURRENT X-Mailer: VM 8.2.0b under 25.2.1 (amd64-portbld-freebsd11.0) X-Mailman-Approved-At: Tue, 29 Aug 2017 17:54:08 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 17:28:31 -0000 Hello: I finally get to update a system from: FreeBSD 11.0-RC2 #0 r304729: Wed Aug 24 06:59:03 UTC 2016 amd64 to -CURRENT. After reading src/UPDATING, I understand everything (I think) _except_: 20170311: The old drm (sys/dev/drm/) drivers for i915 and radeon have been removed as the userland we provide cannot use them. The KMS version (sys/dev/drm2) supports the same hardware. I assume the new kernel bits will be automatically built and installed. Are there any changes I need to make elsewhere, e.g. loader,conf or ports? Also: as part of the "safest in-place upgrade" ... how do rm -rf /usr/obj/* and make cleanworld differ? Respectfully, Robert Huff From owner-freebsd-current@freebsd.org Tue Aug 29 23:54:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1A5BDE8D3F for ; Tue, 29 Aug 2017 23:54:06 +0000 (UTC) (envelope-from monty11ez@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 39B4075FAD for ; Tue, 29 Aug 2017 23:54:06 +0000 (UTC) (envelope-from monty11ez@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id t201so649270wmt.1 for ; Tue, 29 Aug 2017 16:54:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=6GMVQAhsnm1Xs8m8CHbRKNmaq3ybDcfLBTEWzNrsVzA=; b=UtjtuEnhzBUXyiw+ceZrvUsHcNVwzGAOEZurC9vfHJnBhQqmmwOxJ0jcL5m0IFR26C E7KyoW1KWWYuUHNR1iKijN1WUM4UZXKsTzSfnvLwPm1VNOJzLwkiJFVouICyVTZaWu84 oHf06hbEwtxKg+O3T4K2P8ikOUy/LBYACdG8w+AyAd6VKH0Ot+9qX+ITF9la4p6mM46E P6vwvW7brerhed7lwS4O3lPCYR1GgFV1gAczusTmthl8lG5+WxRlaB/P5f19sc0LR259 /HfD1J4wgczo+nPat0jdsLkmsBQymO9+ymAQSW97zz9r0s1rLOnNb+P7dp+nKC8wnCyM qfUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6GMVQAhsnm1Xs8m8CHbRKNmaq3ybDcfLBTEWzNrsVzA=; b=GmZPBQzW7NAO7jvOBosJBYJL+5zTHgXSnAxtx/v0fptJ1fqXASUyIZ3E6tdR6Ycy6F fHUzvmpupDgqM14lYAsA3DPmYCullPWo8hXhQULT5AplkExy1xvJ6rHtOifPusbP5TDL BLEYBScpZ/Mab1EwF7xxsOZPhIba7s6QbdyGXQwbTaYlk+WsK/MwOBZjKW366UzAV3d4 scb0U/OnTQBgFduqkyO7bggfOzbhVq5FOLY1WaptzWPYBlitQlJiyL2MdwBcVPe2I8h6 JAmEZRaIftK6ck3QCujPjw0HFaIIRJdBHiswIqsnCiRDcHBV2wsW1YAdspHVYuvHp3My c1WA== X-Gm-Message-State: AHYfb5hJaolEJpMcjXYlECHg7+g8q7Py0R6HIgKliXrjXswj1kKILkjp lSQJ6oS7wEkr+kyibIvJVpJ7YpQXZNgj X-Received: by 10.80.134.228 with SMTP id 33mr93543edu.89.1504050843714; Tue, 29 Aug 2017 16:54:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.80.221.4 with HTTP; Tue, 29 Aug 2017 16:54:03 -0700 (PDT) From: Monty Chaney-Geib Date: Tue, 29 Aug 2017 19:54:03 -0400 Message-ID: Subject: Custom Kernel Fail To: freebsd-current@freebsd.org X-Mailman-Approved-At: Wed, 30 Aug 2017 01:11:47 +0000 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2017 23:54:06 -0000 I'm getting a failure building a custom kernel on arm64. "/usr/src/sys/dev/mii/smcphy.c:49:10: fatal error: 'miidevs.h' file not found" Let me know what you guys recommend. -Monty From owner-freebsd-current@freebsd.org Wed Aug 30 01:35:46 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA406DEB332 for ; Wed, 30 Aug 2017 01:35:46 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from bat.oak.relay.mailchannels.net (bat.oak.relay.mailchannels.net [23.83.215.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 620697D908 for ; Wed, 30 Aug 2017 01:35:45 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id D765D10784D for ; Wed, 30 Aug 2017 01:26:44 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.129.223]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id 3B6F9107178 for ; Wed, 30 Aug 2017 01:26:44 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.104.49]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Wed, 30 Aug 2017 01:26:44 +0000 X-MC-Relay: Junk X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Industry-Cooperative: 713c77105639642a_1504056404718_851894284 X-MC-Loop-Signature: 1504056404718:4096257281 X-MC-Ingress-Time: 1504056404718 X-MHO-User: 45f5665e-8d22-11e7-83af-a91f44540cb3 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id 45f5665e-8d22-11e7-83af-a91f44540cb3; Wed, 30 Aug 2017 01:26:41 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v7U1Qc5n002390; Tue, 29 Aug 2017 19:26:38 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1504056398.56799.76.camel@freebsd.org> Subject: Re: Custom Kernel Fail From: Ian Lepore To: Monty Chaney-Geib , freebsd-current@freebsd.org Date: Tue, 29 Aug 2017 19:26:38 -0600 In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 01:35:46 -0000 On Tue, 2017-08-29 at 19:54 -0400, Monty Chaney-Geib wrote: > I'm getting a failure building a custom kernel on arm64. > > "/usr/src/sys/dev/mii/smcphy.c:49:10: fatal error: 'miidevs.h' file > not > found" > > Let me know what you guys recommend. > -Monty Add "device mii" to your config. -- Ian From owner-freebsd-current@freebsd.org Wed Aug 30 23:54:09 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C397E0D125 for ; Wed, 30 Aug 2017 23:54:09 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6ECCD7DA for ; Wed, 30 Aug 2017 23:54:09 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-oi0-x22a.google.com with SMTP id w10so63498858oie.1 for ; Wed, 30 Aug 2017 16:54:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=LOnSg4ftZGdcYCgIWSQ/Z12w/jBnauSSs4EU6dn/cGA=; b=OjiTC0ietVtG3ZIqzJDSRLKJ+0qUxkzLpk1tCGIO2ms9BBv7GzlVLEvrWkBZVjA71S RGYfUpynjW75QAgQS2W0tciPe1DNbtCl3NQmP+ba0DADEU1HXuJ9eEWA2m6RGcyyey5h v1qwPl7TUG4MwcXkgoAQF2UZzGE6ma5K+LrxY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=LOnSg4ftZGdcYCgIWSQ/Z12w/jBnauSSs4EU6dn/cGA=; b=fPBzlic2qZl6PJ3WzWOmZsRgthJvuOEUC6ytWcsXwMdIHN9E6CXsGLtu2DzBVYvngM 2o68R4qFIuHMP1Ti5P85osG/arp8mVJ0tvtzUQC/L+AZ4zxPtclk3nVYKM4Kt/ewnXKn wF5Hws/x523auD1oNnrpO4xMLJF9M4vItlw7QYYzmuZz6OGlmL76IThXxiNBjYFZtMnR OASEGOA2LgwemBFUUsvBw6xrVtrzxArkuc5tbxOWSau5YLrs7/kss5w2A94+uar5uLLl ljuAUddIbDMGNF5jV2UOO4hBs+FojYTkhFJYZC98x4F0uFlQR6SBXsm5CiHv9BaMyjvy Yk1w== X-Gm-Message-State: AHYfb5i4uKb1SupC4WTUlxp5E1Zj+PFE5+wZJjN9tjGh4X9sanRPm4vU AWH+mu6bDPgUqMd34vD4RBb3MBZa5Yv9y5Y= X-Received: by 10.202.252.201 with SMTP id a192mr3401238oii.273.1504137248422; Wed, 30 Aug 2017 16:54:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.57.165 with HTTP; Wed, 30 Aug 2017 16:54:07 -0700 (PDT) From: Kevin Bowling Date: Wed, 30 Aug 2017 16:54:07 -0700 Message-ID: Subject: !EARLY_AP_STARTUP and -CURRENT To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2017 23:54:09 -0000 I'm dealing with a shit sandwich right now where the mps(4) or cam_da reorders drives on a few thousand legacy MBR machines I have (and I can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have regressed. I'd like to be able to run w/o EARLY_AP_STARTUP right quick so I can take a more leisurely approach to fixing mps(4) boot probe correctly (freebsd-scsi@ has that thread). With WITNESS and !EARLY_AP_STARTUP I hit an assert in sched_setpreempt in kern/sched_ule.c 100% of the time. Here are a couple invocations, with oddness around a different CPU holding the curthread lock but somehow a different AP is runnable in the function: Tracing pid 11 tid 100020 td 0xfffff80128cd1560 kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e653dcc10 vpanic() at vpanic+0x1b9/frame 0xfffffe3e653dcc90 panic() at panic+0x43/frame 0xfffffe3e653dccf0 __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e653dcd00 sched_add() at sched_add+0x152/frame 0xfffffe3e653dcd40 intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame 0xfffffe3e653dcd80 swi_sched() at swi_sched+0x6c/frame 0xfffffe3e653dcdc0 softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e653dce70 callout_process() at callout_process+0x1f9/frame 0xfffffe3e653dcef0 handleevents() at handleevents+0x1a4/frame 0xfffffe3e653dcf30 cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e653dcf60 init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e653dcf90 init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e653dcff0 db> show thread 0xfffff80128cd1560 Thread 100020 at 0xfffff80128cd1560: proc (pid 11): 0xfffff80128cb5000 name: idle: cpu17 stack: 0xfffffe3e5cd88000-0xfffffe3e5cd8bfff flags: 0x40024 pflags: 0x200000 state: CAN RUN priority: 255 container lock: sched lock 0 (0xffffffff81c39800) db> show lock 0xffffffff81c39800 class: spin mutex name: sched lock 0 flags: {SPIN, RECURSE} state: {OWNED} owner: 0xfffff80128cca000 (tid 100017, pid 11, "idle: cpu14") db> bt Tracing pid 11 tid 100021 td 0xfffff80128cd2000 kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e655e4c10 vpanic() at vpanic+0x1b9/frame 0xfffffe3e655e4c90 panic() at panic+0x43/frame 0xfffffe3e655e4cf0 __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e655e4d00 sched_add() at sched_add+0x152/frame 0xfffffe3e655e4d40 intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame 0xfffffe3e655e4d80 swi_sched() at swi_sched+0x6c/frame 0xfffffe3e655e4dc0 softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e655e4e70 callout_process() at callout_process+0x1f9/frame 0xfffffe3e655e4ef0 handleevents() at handleevents+0x1a4/frame 0xfffffe3e655e4f30 cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e655e4f60 init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e655e4f90 init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e655e4ff0 db> show thread 0xfffff80128cd2000 Thread 100021 at 0xfffff80128cd2000: proc (pid 11): 0xfffff80128cb6000 name: idle: cpu18 stack: 0xfffffe3e5cf17000-0xfffffe3e5cf1afff flags: 0x40024 pflags: 0x200000 state: CAN RUN priority: 255 container lock: sched lock 0 (0xffffffff81c39800) db> show lock 0xffffffff81c39800 class: spin mutex name: sched lock 0 flags: {SPIN, RECURSE} state: {OWNED} owner: 0xfffff80128cdb560 (tid 100028, pid 11, "idle: cpu25") Regards, Kevin From owner-freebsd-current@freebsd.org Thu Aug 31 08:32:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA9AEE18FFD for ; Thu, 31 Aug 2017 08:32:06 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7D6B86E808 for ; Thu, 31 Aug 2017 08:32:06 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id u26so4134777wma.5 for ; Thu, 31 Aug 2017 01:32:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=/R91uHVpBA/oJ3F8nH0VxdDF8YV1pqOiklgAX8iHKs8=; b=sVBPEWUxw51BSK0CcIJLbCyGU50TegFJ5WJt9Z7gSlW8hLchW3S8RJkm+qDo0sWoDy QtXfPxvWAC/nBkTo/45FzUKEoFQKUBSLIyd9+c9Eh5Wj/CuKGQsFVv3aWCTPl0mwgiRz kvbzHzrfWnRDlxCN8kgAb2rUtpi9UngjtTqslsv//vSoLisKRGEmEHzqNWQZP+kXvXkl DyOGaTZ763X1Gn7JXoIDvEBOdZcpRtWV7kM5tpl7jkZ5vXXz0Yoefn51zFPbaL+JSBwO hNy3aXkuUSfoVWirJe7kEGehS3ooZJ2lilcrYHV8nRWZ/kfUBH63zrPygs2HVGMDIWzL +gdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=/R91uHVpBA/oJ3F8nH0VxdDF8YV1pqOiklgAX8iHKs8=; b=ErIDDwrMWxBpEsIfwxBFP5iGh2b973JRC9dNEoyB++lHhFn6DVkshBMKu+HqLKbBNc 833Tbi0eriv5VQjxjdMIRItwk3RltDLoLMJFm+/LyMlMspMP0U4zcWlhRRZwILlCCzuG 4joP8GWZVqb+9Z2pN0wgBbDDpzcRSCb8OmEhAa9QnX6w95HEYJ1shavQZ8YCEdNyZU1D SU9mnfohTJscd6pr17rQRz+bjenJ6WwVN27t0HExkszU6pd9Q7J3ZYSUJUsyUlI/uS8g 2ryDfIyT02WWK/4OYSM6Jts5bVIvobIOrc76GSxeAIFexvxDGaC9N2lRFZu/8jQuTr2C 8rQw== X-Gm-Message-State: AHYfb5imp96fU+5g0+gcHz0XF0wdQM8qC+UNdE40M+t0ab8xG4JEMfIh 3kqz44hwZnkbckUc X-Received: by 10.28.156.146 with SMTP id f140mr2670431wme.32.1504168324886; Thu, 31 Aug 2017 01:32:04 -0700 (PDT) Received: from ernst.home (p4FCA62DB.dip0.t-ipconnect.de. [79.202.98.219]) by smtp.gmail.com with ESMTPSA id k10sm3109583wre.38.2017.08.31.01.32.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 Aug 2017 01:32:03 -0700 (PDT) Date: Thu, 31 Aug 2017 10:31:57 +0200 From: Gary Jennejohn To: Kevin Bowling Cc: freebsd-current@freebsd.org Subject: Re: !EARLY_AP_STARTUP and -CURRENT Message-ID: <20170831103157.0eecbcba@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 08:32:07 -0000 On Wed, 30 Aug 2017 16:54:07 -0700 Kevin Bowling wrote: > I'm dealing with a shit sandwich right now where the mps(4) or cam_da > reorders drives on a few thousand legacy MBR machines I have (and I > can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have > regressed. I'd like to be able to run w/o EARLY_AP_STARTUP right > quick so I can take a more leisurely approach to fixing mps(4) boot > probe correctly (freebsd-scsi@ has that thread). > > With WITNESS and !EARLY_AP_STARTUP I hit an assert in sched_setpreempt > in kern/sched_ule.c 100% of the time. Here are a couple invocations, > with oddness around a different CPU holding the curthread lock but > somehow a different AP is runnable in the function: > You might consider using SCHED_4BSD until this problem can be resolved. I tried booting a system with WITNESS and !EARLY_AP_STARTUP, but using SCHED_4BSD, and it at least reaches multi-user mode. Since it isn't clear under what circumstances your problem arises I didn't pursue it any further, but this approach may at least allow you to continue on. > Tracing pid 11 tid 100020 td 0xfffff80128cd1560 > kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e653dcc10 > vpanic() at vpanic+0x1b9/frame 0xfffffe3e653dcc90 > panic() at panic+0x43/frame 0xfffffe3e653dccf0 > __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e653dcd00 > sched_add() at sched_add+0x152/frame 0xfffffe3e653dcd40 > intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame > 0xfffffe3e653dcd80 > swi_sched() at swi_sched+0x6c/frame 0xfffffe3e653dcdc0 > softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e653dce70 > callout_process() at callout_process+0x1f9/frame 0xfffffe3e653dcef0 > handleevents() at handleevents+0x1a4/frame 0xfffffe3e653dcf30 > cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e653dcf60 > init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e653dcf90 > init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e653dcff0 > > > db> show thread 0xfffff80128cd1560 > Thread 100020 at 0xfffff80128cd1560: > proc (pid 11): 0xfffff80128cb5000 > name: idle: cpu17 > stack: 0xfffffe3e5cd88000-0xfffffe3e5cd8bfff > flags: 0x40024 pflags: 0x200000 > state: CAN RUN > priority: 255 > container lock: sched lock 0 (0xffffffff81c39800) > db> show lock 0xffffffff81c39800 > class: spin mutex > name: sched lock 0 > flags: {SPIN, RECURSE} > state: {OWNED} > owner: 0xfffff80128cca000 (tid 100017, pid 11, "idle: cpu14") > > > db> bt > Tracing pid 11 tid 100021 td 0xfffff80128cd2000 > kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e655e4c10 > vpanic() at vpanic+0x1b9/frame 0xfffffe3e655e4c90 > panic() at panic+0x43/frame 0xfffffe3e655e4cf0 > __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e655e4d00 > sched_add() at sched_add+0x152/frame 0xfffffe3e655e4d40 > intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame > 0xfffffe3e655e4d80 > swi_sched() at swi_sched+0x6c/frame 0xfffffe3e655e4dc0 > softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e655e4e70 > callout_process() at callout_process+0x1f9/frame 0xfffffe3e655e4ef0 > handleevents() at handleevents+0x1a4/frame 0xfffffe3e655e4f30 > cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e655e4f60 > init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e655e4f90 > init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e655e4ff0 > db> show thread 0xfffff80128cd2000 > Thread 100021 at 0xfffff80128cd2000: > proc (pid 11): 0xfffff80128cb6000 > name: idle: cpu18 > stack: 0xfffffe3e5cf17000-0xfffffe3e5cf1afff > flags: 0x40024 pflags: 0x200000 > state: CAN RUN > priority: 255 > container lock: sched lock 0 (0xffffffff81c39800) > db> show lock 0xffffffff81c39800 > class: spin mutex > name: sched lock 0 > flags: {SPIN, RECURSE} > state: {OWNED} > owner: 0xfffff80128cdb560 (tid 100028, pid 11, "idle: cpu25") > > Regards, > Kevin > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu Aug 31 15:03:12 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61A63E20B2E for ; Thu, 31 Aug 2017 15:03:12 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2142B7FCCD for ; Thu, 31 Aug 2017 15:03:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by mail.baldwin.cx (Postfix) with ESMTPSA id 1485210AB01; Thu, 31 Aug 2017 11:03:04 -0400 (EDT) From: John Baldwin To: Kevin Bowling Cc: freebsd-current@freebsd.org Subject: Re: !EARLY_AP_STARTUP and -CURRENT Date: Thu, 31 Aug 2017 07:38:29 -0700 Message-ID: <2607331.p0nfSuSmN8@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Thu, 31 Aug 2017 11:03:04 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 15:03:12 -0000 On Wednesday, August 30, 2017 04:54:07 PM Kevin Bowling wrote: > I'm dealing with a shit sandwich right now where the mps(4) or cam_da > reorders drives on a few thousand legacy MBR machines I have (and I > can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have > regressed. I'd like to be able to run w/o EARLY_AP_STARTUP right > quick so I can take a more leisurely approach to fixing mps(4) boot > probe correctly (freebsd-scsi@ has that thread). > > With WITNESS and !EARLY_AP_STARTUP I hit an assert in sched_setpreempt > in kern/sched_ule.c 100% of the time. Here are a couple invocations, > with oddness around a different CPU holding the curthread lock but > somehow a different AP is runnable in the function: Do you have the panic messages? > Tracing pid 11 tid 100020 td 0xfffff80128cd1560 > kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e653dcc10 > vpanic() at vpanic+0x1b9/frame 0xfffffe3e653dcc90 > panic() at panic+0x43/frame 0xfffffe3e653dccf0 > __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e653dcd00 > sched_add() at sched_add+0x152/frame 0xfffffe3e653dcd40 > intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame > 0xfffffe3e653dcd80 > swi_sched() at swi_sched+0x6c/frame 0xfffffe3e653dcdc0 > softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e653dce70 > callout_process() at callout_process+0x1f9/frame 0xfffffe3e653dcef0 > handleevents() at handleevents+0x1a4/frame 0xfffffe3e653dcf30 > cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e653dcf60 > init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e653dcf90 > init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e653dcff0 > > > db> show thread 0xfffff80128cd1560 > Thread 100020 at 0xfffff80128cd1560: > proc (pid 11): 0xfffff80128cb5000 > name: idle: cpu17 > stack: 0xfffffe3e5cd88000-0xfffffe3e5cd8bfff > flags: 0x40024 pflags: 0x200000 > state: CAN RUN > priority: 255 > container lock: sched lock 0 (0xffffffff81c39800) > db> show lock 0xffffffff81c39800 > class: spin mutex > name: sched lock 0 > flags: {SPIN, RECURSE} > state: {OWNED} > owner: 0xfffff80128cca000 (tid 100017, pid 11, "idle: cpu14") > > > db> bt > Tracing pid 11 tid 100021 td 0xfffff80128cd2000 > kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e655e4c10 > vpanic() at vpanic+0x1b9/frame 0xfffffe3e655e4c90 > panic() at panic+0x43/frame 0xfffffe3e655e4cf0 > __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e655e4d00 > sched_add() at sched_add+0x152/frame 0xfffffe3e655e4d40 > intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame > 0xfffffe3e655e4d80 > swi_sched() at swi_sched+0x6c/frame 0xfffffe3e655e4dc0 > softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e655e4e70 > callout_process() at callout_process+0x1f9/frame 0xfffffe3e655e4ef0 > handleevents() at handleevents+0x1a4/frame 0xfffffe3e655e4f30 > cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e655e4f60 > init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e655e4f90 > init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e655e4ff0 > db> show thread 0xfffff80128cd2000 > Thread 100021 at 0xfffff80128cd2000: > proc (pid 11): 0xfffff80128cb6000 > name: idle: cpu18 > stack: 0xfffffe3e5cf17000-0xfffffe3e5cf1afff > flags: 0x40024 pflags: 0x200000 > state: CAN RUN > priority: 255 > container lock: sched lock 0 (0xffffffff81c39800) > db> show lock 0xffffffff81c39800 > class: spin mutex > name: sched lock 0 > flags: {SPIN, RECURSE} > state: {OWNED} > owner: 0xfffff80128cdb560 (tid 100028, pid 11, "idle: cpu25") > > Regards, > Kevin -- John Baldwin From owner-freebsd-current@freebsd.org Thu Aug 31 11:12:37 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2110CE1C13A; Thu, 31 Aug 2017 11:12:37 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A8FA073A86; Thu, 31 Aug 2017 11:12:36 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id v7VBCUhj044682 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 31 Aug 2017 13:12:31 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: ycyc321@gmail.com Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTP id v7VBCQg4021630; Thu, 31 Aug 2017 18:12:26 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: How to know the address ranges of kernel stacks, for user processes and kernel threads? To: Yue Chen , freebsd-hackers@freebsd.org, freebsd-current@freebsd.org References: From: Eugene Grosbein Message-ID: <59A7EF1A.7020502@grosbein.net> Date: Thu, 31 Aug 2017 18:12:26 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: Yes, score=5.5 required=5.0 tests=BAYES_00, DATE_IN_FUTURE_96_Q, LOCAL_FROM,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * 3.3 DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-Spam-Flag: YES X-Spam-Level: ***** X-Mailman-Approved-At: Thu, 31 Aug 2017 17:41:34 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 11:12:37 -0000 On 29.01.2015 07:54, Yue Chen wrote: > It seems that each kernel stack has two pages (IA-32) to use. Does x86_64 > still have two pages or more? One can change number of kernel stack pages for i386 and amd64 platforms by means of /boot/loader.conf without need to rebuild a kernel using kern.kstack_pages tunnable. It equals to 2 for i386 and to 4 for amd64 by default but I change it from 2 to 4 for my i386 systems running IPSEC tunnels and/or wifi due to these subsystems being stack-greedy. See also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219476 From owner-freebsd-current@freebsd.org Thu Aug 31 21:51:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C58F9E06793 for ; Thu, 31 Aug 2017 21:51:16 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AECE693D9 for ; Thu, 31 Aug 2017 21:51:16 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-oi0-x233.google.com with SMTP id t75so7751632oie.3 for ; Thu, 31 Aug 2017 14:51:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5Gxt1bRKaPS2J4Pqxp24QRaU+/dq5bN39mxhbGaUYgQ=; b=imaHIlAbhJELIioSRAnDbFNZHnLon73PNyDzCxqnz8G7Trr51WjIpBXHPMxSwP821H pa/8MgNPhYUAdyTHZTdWp8XjHX7ncCB6ihCh2SSjbcf6ACeNSRAjqpBzRXaW7bcsrl6T F7HwliFCmHlUsOMEiZnp7cD7aCO8B/Q00p5hw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5Gxt1bRKaPS2J4Pqxp24QRaU+/dq5bN39mxhbGaUYgQ=; b=cb1fzVOMKdapsaJ3J3XakhVBjAwEwnWyET4m6VUI0OqohhJ/RCx2zvQ8451N3JtAaM Y9hebxZGgcdj0jvpAWIHD8k4kv+a38b7RD19QyLUcMDvwa16Xt6UoRv7tRTkpyxniA78 agJOwcKryF5ScJVyu8wPqyseXpkXGnLxCyDHJ8V5G2ztonWL46Cy9uVXhSmSNgdfMvCt BDZ/A7GwJPCK/ZRD6ny9JIWBHKbNIYu/FX2P4MXN2oEJNOmtHLGW8pc0hkIur9ilsWKM QoTjCgaRwUIP2aZlZovW2q+YwSspagP231Tn4GMEAJgGk9OgPNEGFuvLrAIIXZTj6qQr eAHA== X-Gm-Message-State: AHYfb5iQlr0kdh1UFqnB3jhiuup+hvD5YVhHMtrXn5ObChl9HeTeoUuK aICia6T5BxmOgfhr/tYr/hRruA0sWyva X-Google-Smtp-Source: ADKCNb5CxYk3ibJ5dORgjvOMMFqjK1M1P47ZizDfiT4VzP3hRC8YJgQh/OEl041MbSD8peI1+EbImF6IsLP0109uIfc= X-Received: by 10.202.87.78 with SMTP id l75mr7607455oib.137.1504216275754; Thu, 31 Aug 2017 14:51:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.57.165 with HTTP; Thu, 31 Aug 2017 14:51:15 -0700 (PDT) In-Reply-To: <2607331.p0nfSuSmN8@ralph.baldwin.cx> References: <2607331.p0nfSuSmN8@ralph.baldwin.cx> From: Kevin Bowling Date: Thu, 31 Aug 2017 14:51:15 -0700 Message-ID: Subject: Re: !EARLY_AP_STARTUP and -CURRENT To: John Baldwin Cc: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 21:51:16 -0000 panic: mutex sched lock 0 not owned at /d0/kev/freebsd/sys/kern/sched_ule.c:2379 On Thu, Aug 31, 2017 at 7:38 AM, John Baldwin wrote: > On Wednesday, August 30, 2017 04:54:07 PM Kevin Bowling wrote: >> I'm dealing with a shit sandwich right now where the mps(4) or cam_da >> reorders drives on a few thousand legacy MBR machines I have (and I >> can't easily install glabel ATM), and !EARLY_AP_STARTUP seems to have >> regressed. I'd like to be able to run w/o EARLY_AP_STARTUP right >> quick so I can take a more leisurely approach to fixing mps(4) boot >> probe correctly (freebsd-scsi@ has that thread). >> >> With WITNESS and !EARLY_AP_STARTUP I hit an assert in sched_setpreempt >> in kern/sched_ule.c 100% of the time. Here are a couple invocations, >> with oddness around a different CPU holding the curthread lock but >> somehow a different AP is runnable in the function: > > Do you have the panic messages? > >> Tracing pid 11 tid 100020 td 0xfffff80128cd1560 >> kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e653dcc10 >> vpanic() at vpanic+0x1b9/frame 0xfffffe3e653dcc90 >> panic() at panic+0x43/frame 0xfffffe3e653dccf0 >> __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e653dcd00 >> sched_add() at sched_add+0x152/frame 0xfffffe3e653dcd40 >> intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame >> 0xfffffe3e653dcd80 >> swi_sched() at swi_sched+0x6c/frame 0xfffffe3e653dcdc0 >> softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e653dce70 >> callout_process() at callout_process+0x1f9/frame 0xfffffe3e653dcef0 >> handleevents() at handleevents+0x1a4/frame 0xfffffe3e653dcf30 >> cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e653dcf60 >> init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e653dcf90 >> init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e653dcff0 >> >> >> db> show thread 0xfffff80128cd1560 >> Thread 100020 at 0xfffff80128cd1560: >> proc (pid 11): 0xfffff80128cb5000 >> name: idle: cpu17 >> stack: 0xfffffe3e5cd88000-0xfffffe3e5cd8bfff >> flags: 0x40024 pflags: 0x200000 >> state: CAN RUN >> priority: 255 >> container lock: sched lock 0 (0xffffffff81c39800) >> db> show lock 0xffffffff81c39800 >> class: spin mutex >> name: sched lock 0 >> flags: {SPIN, RECURSE} >> state: {OWNED} >> owner: 0xfffff80128cca000 (tid 100017, pid 11, "idle: cpu14") >> >> >> db> bt >> Tracing pid 11 tid 100021 td 0xfffff80128cd2000 >> kdb_enter() at kdb_enter+0x3b/frame 0xfffffe3e655e4c10 >> vpanic() at vpanic+0x1b9/frame 0xfffffe3e655e4c90 >> panic() at panic+0x43/frame 0xfffffe3e655e4cf0 >> __mtx_assert() at __mtx_assert+0xb4/frame 0xfffffe3e655e4d00 >> sched_add() at sched_add+0x152/frame 0xfffffe3e655e4d40 >> intr_event_schedule_thread() at intr_event_schedule_thread+0xca/frame >> 0xfffffe3e655e4d80 >> swi_sched() at swi_sched+0x6c/frame 0xfffffe3e655e4dc0 >> softclock_call_cc() at softclock_call_cc+0x155/frame 0xfffffe3e655e4e70 >> callout_process() at callout_process+0x1f9/frame 0xfffffe3e655e4ef0 >> handleevents() at handleevents+0x1a4/frame 0xfffffe3e655e4f30 >> cpu_initclocks_ap() at cpu_initclocks_ap+0xc8/frame 0xfffffe3e655e4f60 >> init_secondary_tail() at init_secondary_tail+0x1e3/frame 0xfffffe3e655e4f90 >> init_secondary() at init_secondary+0x2b3/frame 0xfffffe3e655e4ff0 >> db> show thread 0xfffff80128cd2000 >> Thread 100021 at 0xfffff80128cd2000: >> proc (pid 11): 0xfffff80128cb6000 >> name: idle: cpu18 >> stack: 0xfffffe3e5cf17000-0xfffffe3e5cf1afff >> flags: 0x40024 pflags: 0x200000 >> state: CAN RUN >> priority: 255 >> container lock: sched lock 0 (0xffffffff81c39800) >> db> show lock 0xffffffff81c39800 >> class: spin mutex >> name: sched lock 0 >> flags: {SPIN, RECURSE} >> state: {OWNED} >> owner: 0xfffff80128cdb560 (tid 100028, pid 11, "idle: cpu25") >> >> Regards, >> Kevin > > > -- > John Baldwin