https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
Bug ID: 216123
Summary: ofwfb: r269278 broke booting on Power Mac G4
Product: Base System
Version: CURRENT
Hardware: powerpc
OS: Any
Status: New
Sev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #1 from Tom Lane ---
Created attachment 178973
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178973&action=edit
Revert r269278, in a way that applies to CURRENT
Just for fun, I tried reverting r269278 against CURREN
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #2 from Kevin Bowling ---
Can you set 'sysctl debug.debugger_on_panic=1' and see if you can get a better
idea where it dies from the db> prompt or by switching to kgdb from that?
I don't have any G4 hw so maybe a dump of OFW tr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #3 from Tom Lane ---
Created attachment 178976
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=178976&action=edit
ofwdump -ap output
> I don't have any G4 hw so maybe a dump of OFW tree as well.
Here's ofwdump -ap ou
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #4 from Tom Lane ---
(In reply to Kevin Bowling from comment #2)
> Can you set 'sysctl debug.debugger_on_panic=1' and see if you can get a
> better idea
> where it dies from the db> prompt or by switching to kgdb from that?
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #5 from Kevin Bowling ---
Yeah the sysctl suggestion was to enable the in kernel debugger. There's a
rather esoteric feature to use firewire as a console
https://wiki.freebsd.org/DebugWithDcons, but you'd need another firewire
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #6 from Tom Lane ---
(In reply to Kevin Bowling from comment #5)
Hmm ... I lack a firewire cable, but that could be remedied. The only other
firewire machine I have is a G4 laptop, which I'm pretty sure won't boot 11 or
12 for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #7 from Kevin Bowling ---
I don't think they need to be the same version, but you could revert the one
commit on the display system. I've never used this though, so I can't validate
that it actually works still. But it seems w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
--- Comment #8 from Tom Lane ---
Created attachment 179069
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=179069&action=edit
Minimum part of reverting r269278 to get CURRENT to boot
I've not had any luck bringing a kernel debugg
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216123
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|freebsd-bu
10 matches
Mail list logo