[Bug 233863] Various PowerMac G5 models may require kern.smp.disabled=1 and must set usefdt=1 which causes net interface reorder

[email protected]
Newsgroups gmane.os.freebsd.devel.ppc
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233863

--- Comment #45 from Mark Millard <[email protected]> ---
(In reply to Justin Hibbits from comment #40)

All 5 of my attachments are tied to enabling
booting various old PowerMac models in at least
some mode (mostly usefdt mode).

3 of the 5 attachments are associated with
not being able to boot and operate various old
PowerMacs in usefdt mode. I originally started
because I could not follow the "must set usefdt"
part of the one line description on the old
PowerMac7,2 G5 (2-sockets/1-core-each) and some
G4s and a G3.

You may well not want those problems covered by
your new "in process" status for the defect. If
not, then we need to do something about keeping
the usefdt-mode-booting information someplace.
(I'm hoping that usefdt becomes official and the
default on the old PowerMacs.)

The aim/trap_subr32.S isync's patch you have already
been dealing with. It was tied to a lack of ability
to boot G3s: It avoided getting machine-checks, there
by allowing seeing the more informative type of
failure information. I'm not sure if it is MFC'd
everywhere yet.

Again, if not considered as part of the original
submittal's problems, we may need to do something
to be sure it is not lost (unless it is MFC'd
everywhere already?).

That is 4 of the 5 attachments, the 5th is my
original version of initializing sufficiently,
early enough, on ap's. That may be the only one
you want the "in progress" status to cover (using
your variant).

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[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.