From owner-freebsd-current@freebsd.org Sat Feb 15 18:12:30 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B09A5242B78 for ; Sat, 15 Feb 2020 18:12:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48KddB49DCz4XM6 for ; Sat, 15 Feb 2020 18:12:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 8EBEF242B72; Sat, 15 Feb 2020 18:12:30 +0000 (UTC) Delivered-To: current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8D846242B6B for ; Sat, 15 Feb 2020 18:12:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48KddB2HfRz4XM4; Sat, 15 Feb 2020 18:12:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.not-for.work (onlyone.not-for.work [IPv6:2a01:4f8:201:6350::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: lev/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 2907019917; Sat, 15 Feb 2020 18:12:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:c94d:4c28:4507:5e5a]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.not-for.work (Postfix) with ESMTPSA id EB0C9111F; Sat, 15 Feb 2020 21:12:26 +0300 (MSK) Date: Sat, 15 Feb 2020 21:12:27 +0300 From: Lev Serebryakov Reply-To: lev@FreeBSD.org Organization: FreeBSD Message-ID: <1256487134.20200215211227@serebryakov.spb.ru> To: David Wolfskill CC: current@freebsd.org Subject: Re: CURRENT panciks right after kernel load (r357966) In-Reply-To: <20200215180253.GW1238@albert.catwhisker.org> References: <241831336.20200215205415@serebryakov.spb.ru> <20200215180253.GW1238@albert.catwhisker.org> 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.29 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: Sat, 15 Feb 2020 18:12:30 -0000 Hello David, Saturday, February 15, 2020, 9:02:53 PM, you wrote: >> CURRENT r357966 on amd64, on host with 4G of memory (and Atom CPU) panics >> with page fault right after kernel load (before any kernel output). >> >> Stacktrace (typed from photo of screen, all trap-related functions are >> omitted): >> >> uma_zalloc_arg() >> malloc() >> sysctl_handle_string() >> sysctl_netisr_dispatch_policy() >> sysctl_root_handler_locked() >> sysctl_register_oid() >> sysctl_register_all() >> mi_startup() >> ..... > My last CURRENT build was at r357959 (and which booted without issue -- > though the systems in question don't use ZFS); only commits I see to > head after r357959 are r357962 & r357967. I've tried r357763 and it panics exactly same way. My system doesn't have ZFS too (it is NanoBSD image for small router). I didn't update this "firmware" for almost a year, and don't have results for revision between r349299 (works) and r357763 (panics). It is too much for bi-sect :-( I'll try r357508, which works for me on other host, but I suspect it is HW-related and not universal. But, again, r349299 works rock-solid. -- Best regards, Lev mailto:lev@FreeBSD.org