Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Jul 2017 16:38:44 -0600
From:      Alan Braslau <braslau.list@comcast.net>
To:        Justin Hibbits <chmeeedalf@gmail.com>
Cc:        Mark Millard <markmi@dsl-only.net>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: powerpc64 update from source kernel panic (11.0)
Message-ID:  <20170704163844.2afcd745@zoo.hsd1.co.comcast.net>
In-Reply-To: <CAHSQbTDqYewkBav8tzvL8AUoA_aneq_z=4qQV9pEb31vNF%2BAFA@mail.gmail.com>
References:  <AFE787D7-EFCB-4265-B2FB-6A4587DAD4FA@dsl-only.net> <20170704145456.6d8c095e@zoo.hsd1.co.comcast.net> <CAHSQbTDqYewkBav8tzvL8AUoA_aneq_z=4qQV9pEb31vNF%2BAFA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 4 Jul 2017 17:16:39 -0500
Justin Hibbits <chmeeedalf@gmail.com> wrote:

> On Jul 4, 2017 15:55, "Alan Braslau" <braslau.list@comcast.net> wrote:
> 
> On Tue, 4 Jul 2017 13:36:08 -0700
> Mark Millard <markmi@dsl-only.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?
> >
> >
> >
> > 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170704163844.2afcd745>