Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 9 Apr 2019 19:10:46 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   PowerMac11, 2 G5 (2 socket, 2 cores each) powerpc64: sometime between -r302214 and -r333594 owfdump -ap leads to 'timeout stopping cpus' and ddb> prompt
Message-ID:  <C328187B-03F0-4621-8097-D4D546B31F9E@yahoo.com>

next in thread | raw e-mail | index | archive | help
[32-bit powerpc FreeBSD booting the same machine
does not have the problem, just powerpc64 FreeBSD.
I've been using -ap with ofwdump but it might not
be essential to the observed problem.]

In trying to track down a problem, where I wanted to use
ofwdump -ap information, I ended up finding and checking
old  boot media that happen to be around that target
powerpc64.

The oldest failing: -r333594 (an 12.x-CURRENT time frame)
The newest working: -r302214 (an 11.x-CURRENT time frame)
(No versions around between those.)

(As almost always, my powerpc64 builds are experiments
targeted via toolchains more modern than gcc 4.2.1 and the
like.)

Those listed above long predate any useful usefdt
boots/operations in my context. The 2 powerpc64 builds
before -r302214 worked.

(The original problem that started this is that usefdt skips
some ofw nodes. Then I found that not having usefdt mode
lead to crashes for ofwdump -ap . So I went looking at
the few historical builds that I found.)

Modern powerpc64/head FreeBSD without use of usefdt mode fails
somewhat differently: scrolling console messages going by too
fast for me to read after starting ofwdump -ap. (It might be
back-traces.) No ability to get to the ddb> prompt and no
access via the network. But modern FreeBSD has various
blocking issues before one can even get this far.


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C328187B-03F0-4621-8097-D4D546B31F9E>