From owner-freebsd-ppc@freebsd.org Tue Jul 4 22:40:44 2017 Return-Path: Delivered-To: freebsd-ppc@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 E758ED9C3F5 for ; Tue, 4 Jul 2017 22:40:44 +0000 (UTC) (envelope-from braslau.list@comcast.net) Received: from resqmta-po-10v.sys.comcast.net (resqmta-po-10v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "resqmta-po-01v.sys.comcast.net", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF4E765A94 for ; Tue, 4 Jul 2017 22:40:44 +0000 (UTC) (envelope-from braslau.list@comcast.net) Received: from resomta-po-05v.sys.comcast.net ([96.114.154.229]) by resqmta-po-10v.sys.comcast.net with SMTP id SWSwdz0Ja8ozzSWT2dhGDc; Tue, 04 Jul 2017 22:38:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1499207928; bh=2uGvbkLzvg1bGvNmnsAqb62OB2EmXmfhZh3GpMc86V8=; h=Received:Received:Date:From:To:Subject:Message-ID:MIME-Version: Content-Type; b=UhfgT08w79A0cK3CZKQ7rNFt68RjgaVyPR4ri8lr1WlEcp6XdxpCLQPTB5epkXXzr qw4qtweY8QIoFGOVRk8bTAsc+Du1FT4a8BUgiXhT5PtVMzLaaR70TUmf9YEDGzc7Ut OHeOps9yLpC7zbD812GwKZy4bFpy8q4YnfXWCJM1ETs4p+sEk4oSUueFQfZh5S2wbL qhj6xn8pUdWnUNf7jsXoGOPzOegeACwsy3h5XGLB1Dfkni22eGHSL+DD0wEJm2CFNu cy1GH00bb5+jCMZ1z+0TYh7ebx3d/vQ0R1VTs3TRslzMY16ICeIkDYG9OxQDq660uA izlrZmdBIkwxg== Received: from zoo.hsd1.co.comcast.net ([IPv6:2601:282:8000:7637:b0f6:5c54:9af2:6790]) by resomta-po-05v.sys.comcast.net with SMTP id SWT0dDgewQPoKSWT1dLWzT; Tue, 04 Jul 2017 22:38:48 +0000 Date: Tue, 4 Jul 2017 16:38:44 -0600 From: Alan Braslau To: Justin Hibbits Cc: Mark Millard , FreeBSD PowerPC ML Subject: Re: powerpc64 update from source kernel panic (11.0) Message-ID: <20170704163844.2afcd745@zoo.hsd1.co.comcast.net> In-Reply-To: References: <20170704145456.6d8c095e@zoo.hsd1.co.comcast.net> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-apple-darwin16.6.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfICLH0Mne+zaKaimEfrf4QEAxvqGabEhPCisCAv+jmOR0N8sQdx7zwo75QOfadqaOll252n0miSiayoHxAYZgVdfNRZ5EFbE7DINRl40Xqz2O5MJ8DdD y2AY3AgrSavFkjaT3jpCE8lFeQyDd8sXs6VeMuaVikCUTQjHJiVYlgOyP9TnECQXoni4oaPekJ/P0JCaYlhlVWz/sY7Jc+MFs7BApC3piHU/zuanDTx8uTQN axu+7lQuP/1z/1y+XojP4w== X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jul 2017 22:40:45 -0000 On Tue, 4 Jul 2017 17:16:39 -0500 Justin Hibbits wrote: > On Jul 4, 2017 15:55, "Alan Braslau" wrote: > > On Tue, 4 Jul 2017 13:36:08 -0700 > Mark Millard wrote: > > > Alan Braslau braslau.list at comcast.net wrote on > > Tue Jul 4 16:01:41 UTC 2017 : > > > > > I installed freebsd 11.0 powerpc64 on an iMac G5 without any > > > problems and have installed a fairly complete functional system. > > > > > > However, upgrading from source (unmodified configuration) results > > > in a kernel panic upon boot. Has anyone experienced this? > > > > > > > > It might help folks to be more explicit > > about. . . > > > > What specific version before the upgrade? > > > > release/11.0.0/ > > release/11.0.1/ > > releng/11.0/ for what -r3????? > > stable/11/ for what -r3????? > > > > What specific version for the attempted > > "upgrade to": > > > > release/11.0.1/ > > releng/11.0/ for what -r3????? > > releng/11.1/ for what -r3????? > > stable/11/ for what -r3????? > > > > > > I've assumed above that you did not > > try to upgrade to: > > > > head/ for some -r3????? > > > > (also called CURRENT or 12-CURRENT). > > But I could be wrong. head/ is more > > likely to end up with odd problems > > and has had some recent ones. > > > > > > === > > Mark Millard > > markmi at dsl-only.net > > > > I'm sorry, I thought that it could be assumed that I installed > RELEASE: I simply installed 11.0-RELEASE-p1 (from an iso image) and > updated the source from base/releng/11.0 which gave me revision > 320623. > > make buildworld > make kernel > shutdown -r now > -> kernel panic > then... > boot kernel.old > > I did not try anything custom. > > Alan > > > Do you have a backtrace from the panic? ... kldload: unexpected relocation type 1606324608 panic: vm_fault: fault on nofault entry, addr: c000000001c80000 cpuid = 0 KDB: stack backtrace #1 0x614874 at .vpanic+0x190 #1 0x614910 at .panic+0x38 #2 0x9dc298 at .vm_fault_hold+0x1ac #3 0x9dffe4 at .vm_fault+0x9c #4 0xa6d3dc at .trap_pfault+0xb0 #5 0xa6f1d0 at .trap+0x1b6c #6 0xa62850 at .powerpc_interrupt+0x1c4 Uptime: 1s Silly me - I think that I figured it out. I had if_bwn_load="YES" in /boot/loader.conf Removing this, the new kernel boots. I guess that the module is incompatible and gets updated with installworld. I'm testing this hypothesis... Maybe the handbook section 23.5 ought to be corrected to specify removing the loading of all modules in loader.conf? Alan