From owner-freebsd-hackers@freebsd.org Mon Jul 17 09:11:34 2017 Return-Path: Delivered-To: freebsd-hackers@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 E9080D14EDB for ; Mon, 17 Jul 2017 09:11:34 +0000 (UTC) (envelope-from netch@netch.kiev.ua) Received: from vpa.nn.kiev.ua (078.vps.ho.ua [91.228.147.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 A501E7D634 for ; Mon, 17 Jul 2017 09:11:33 +0000 (UTC) (envelope-from netch@netch.kiev.ua) Received: by vpa.nn.kiev.ua (Postfix, from userid 1000) id 607779443ACA; Mon, 17 Jul 2017 12:11:25 +0300 (EEST) Date: Mon, 17 Jul 2017 12:11:25 +0300 From: Valentin Nechayev To: Nicolas Embriz Cc: "freebsd-hackers@freebsd.org" Subject: Re: GEOM: ada0: the secondary GPT header is not in the last LBA or random: unblocking device. when using more than 2 cores Message-ID: <20170717091125.GA8450@netch.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-42: On X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jul 2017 09:11:35 -0000 hi, Sun, Jul 16, 2017 at 12:16:14, nbari wrote about "Re: GEOM: ada0: the secondary GPT header is not in the last LBA or random: unblocking device. when using more than 2 cores": > Setting up harvesting: > [UMA],[FS_ATIME],SWI,INTERRUPT,NET_NG,NET_ETHER,NET_TUN,MOUSE,KEYBOARD,ATTACH,CACHED > Feeding entropy: . > spin lock 0xffffffff80db45c0 (smp rendezvous) held by 0xfffff80004378560 Are you using a custom kernel? I had experienced panics just with random device on transition 10.2 -> 10.3 by source, and they were solved by temporary disabling of rdrand_rng, despite following reenabling of this device settled normal working. (Regrettably, I haven't got the panic details.) -netch-