Date: Tue, 4 Jul 2017 16:28:14 -0700 From: Mark Millard <markmi@dsl-only.net> To: Alan Braslau <braslau.list@comcast.net> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>, Justin Hibbits <jhibbits@FreeBSD.org> Subject: Re: powerpc64 update from source kernel panic (11.0) Message-ID: <7800C44D-8FD9-480B-8D53-D505F72F082E@dsl-only.net> In-Reply-To: <20170704165249.10d01228@zoo.hsd1.co.comcast.net> References: <AFE787D7-EFCB-4265-B2FB-6A4587DAD4FA@dsl-only.net> <20170704145456.6d8c095e@zoo.hsd1.co.comcast.net> <19637A8C-9C28-42D9-8E3E-E30E998D787A@dsl-only.net> <20170704165249.10d01228@zoo.hsd1.co.comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Jul-4, at 3:52 PM, Alan Braslau <braslau.list@comcast.net> wrote: > On Tue, 4 Jul 2017 15:37:31 -0700 > Mark Millard <markmi@dsl-only.net> wrote: > >> On 2017-Jul-4, at 1:54 PM, Alan Braslau <braslau.list@comcast.net> >> 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? >>> . . . >>> 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. >> >> I probably also should have asked if you are >> using 32-bit FreeBSD or 64-bit. (G5's can use >> either when things are working.) >> >> -r320623 is from head (not from releng/11.0/ ): >> >> https://svnweb.freebsd.org/base/head/?view=log s shows: >> >> Revision 320623 - Directory Listing >> Modified Mon Jul 3 23:27:57 2017 UTC (23 hours, 2 minutes ago) by >> jasone Update jemalloc to 5.0.1. >> >> If this is real then you have jumped to a binary incompatible >> kernel relative to your world. (That may not be the only >> problem and you might not have even got that far.) >> >> As of when I looked head was up to -r320659 . >> >> I list the below in case the 320623 is a typo or some such. . . >> >> https://svnweb.freebsd.org/base/releng/11.0/?view=log shows: >> >> -r317487 from 2017-Apr-27 >> -r316722 from 2017-Apr-12 >> -r314125 from 2017-Feb-23 >> (I'll stop there.) >> >> https://svnweb.freebsd.org/base/releng/11.1/?view=log shows: >> >> -r320654 from 2017-Jul-4 >> -r320639 from 2017-Jul-4 >> -r320608 from 2017-Jul-3 >> (I'll stop there.) >> >> https://svnweb.freebsd.org/base/stable/11/?view=log shows: >> >> -r320645 from 2017-Jul-4 >> -r320641 from 2017-Jul-4 >> -r320638 from 2017-Jul-4 >> -r320621 from 2017-Jul-3 >> (I'll stop there.) >> >> >> Can you report for sure what you actually got? >> >> === >> Mark Millard >> markmi at dsl-only.net >> > > 320623 seemed odd > and typing svn up gives 320659 > and svn info indeed gives 317487 (2017-04-27) as the last changed > revision. There are two revisions for svn. If you explicitly use update -r?????? the two will be equal, for example: # svnlite info /usr/src | grep "Re[plv]" Relative URL: ^/head Repository Root: svn://svn0.us-west.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 320570 Last Changed Rev: 320570 But if you just grab the most current without specifying then the "Last Changed Rev" number is what you want to reference. The other number will reflect the global svn state across branches and such and so frequently will appear more recent than what is actually checked out and also possibly pointing into the wrong branch. > (am I misusing svn?) > > Also, I thought that I specified powerpc64. I agree that I likely should have taken "freebsd 11.0 powerpc64" to mean: TARGET_ARCH=powerpc64 But, with things already being odd, I wanted to be sure it was just not the processor-type that was being specified. (In head TARGET_ARCH=powerpc recently has had extra problems that did not show up for TARGET_ARCH=powerpc64 .) > Indeed, the problem seems to be the loading of a kmod that does not get > updated until installworld. My fault (or some missing information in > the handbook). I've never used PORTS_MODULES or the like so I'm unsure of the details for avoiding compatibility issues. === Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7800C44D-8FD9-480B-8D53-D505F72F082E>