Re: Failed attempt to boot a (non-debug) head -r339076 on an old PowerMac G5 "Quad Core" (built via devel/powerpc64-gcc): Waking up CPU 1

Mark Millard via freebsd-ppc <[email protected]>
Newsgroups gmane.os.freebsd.devel.ppc
Message-ID <[email protected]>
[The stable/head mix seems to be a wrong idea: 11.2 gets past
the SMP: messages just fine on the so-called G5 "Quad Core".]

On 2018-Oct-8, at 5:14 PM, Mark Millard <marklmi at yahoo.com> wrote:

> On 2018-Oct-8, at 1:27 PM, Justin Hibbits <chmeeedalf at gmail.com> wrote:
> 
>> On Mon, 8 Oct 2018 15:37:43 -0400
>> Dennis Clarke <dclarke blastwave.org> wrote:
>> 
>>> On 10/08/2018 03:04 PM, Mark Millard via freebsd-ppc wrote:
>>>> On 2018-Oct-8, at 10:25 AM, Michael Tuexen <tuexen at
>>>> fh-muenster.de> wrote: 
>>>>>> On 8. Oct 2018, at 19:00, Mark Millard <marklmi at yahoo.com>
>>>>>> wrote:
>>>>>> 
>>>>>> [kern.smp.disabled=1 is confirmed to enable booting
>>>>>> my head -r339076 build on teh "Quad Core", much like
>>>>>> the 11.2 reports for "2MHz dual-core".]  
>>>>> Does 11.2 run with smp enabled?  
>>>> 
>>>> [My wording was poor: "reports" in "11.2 reports with
>>>> smp enabled" was referring to reports by you and others
>>>> on the lists, not screen messages from attempting a
>>>> 11.2 boot.]
>>>> 
>>>> No clue at this point for the G5 "Quad Core". I have no
>>>> 11.x context established, and have not since head
>>>> went from 11 to 12, as I remember. Would trying to boot
>>>> an installer/live for 11.2 be sufficient to test
>>>> this?  
>>> 
>>> 
>>> I have tried over and over to install 11.2 on a G5 with dual PPC970
>>> sockets wherein both are dual core. There is no quad core. Never was.
>>> Anyways, the install simply doesn't work.
>>> 
>>> Dennis
>> 
>> It would be helpful to know the last known-good SVN revision, both for
>> Head and 11.x, as well as the oldest failing one.  Since my G5 bit the
>> dust, I can't check locally.
> 
> Admittedly, it is a mix of 11 and 12 but bounds might be:
> 
> Earliest known failing (so far):
> 11.2 Release is -r335563 (by which point 11 possibly picked up
> something bad from head)
> 
> Latest known working (so far):
> head -r333594 (too soon for 11 to have picked up something from
> head)
> 
> From https://artifact.ci.freebsd.org/snapshot/stable-11/r*/powerpc/powerpc64/kernel.txz
> (presuming holding a base.txz constant and just swapping kernels)
> In that range for stable-11 I see matches for * of just:
> 
> 334634
> 334654
> 334698
> 334956
> 335204
> 335406
> 335436
> 335472
> 335488
> 335492
> 335496
> 335508
> 335514
> 335556
> 
> So about 14 versions of 11's kernel seem to be available
> in a pre-built form for powerpc64 under the assumption of
> "common problem, moved from head to 11".
> 
> Of course 11.2's release -r335563 could be included. There
> do not seem to be earlier powerpc64 snapshots anywhere near
> -r333594's time frame.
> 
> That could possibly be used to narrow the range more for 11
> without doing builds.

To start on this I took enough from:

http://ftp1.freebsd.org/pub/FreeBSD/snapshots/powerpc/powerpc64/11.2-STABLE/

to see if it would get past the SMP: messages that head is not
reaching. It produced the SMP messages just fine and kept going
past that point.

So I tried:

http://ftp1.freebsd.org/pub/FreeBSD/releases/powerpc/11.2-RELEASE/

and it did the same. 11.2-Release does not fail during the same
activity as head (if it fails at all).

So I'm not exploring the artifact.ci.freebsd.org stable-11 material
that I listed.

I may explore head via:

https://artifact.ci.freebsd.org/snapshot/head/r*/powerpc/powerpc64/kernel.txz

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.