Date: Wed, 23 Sep 2020 09:47:57 -0700 From: Mark Millard <marklmi@yahoo.com> To: Brandon Bergren <bdragon@FreeBSD.org> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: head -r365932 on PowerMac G5 (2 dual-core sockets): Crashes before login prompt if powerd is enabled in /etc/rc.conf Message-ID: <07E0C1EE-647C-4BFD-A60F-71B02EA3FB13@yahoo.com> In-Reply-To: <88052e3f-4b79-45ca-8ebb-9fc19cbc558b@www.fastmail.com> References: <52783D16-5DCA-45BC-9238-2518326454A1@yahoo.com> <6E99EE39-D2B8-415A-A5BF-823C0F0C22D6@yahoo.com> <cd9d2b72-219f-4550-a437-4ac3aa1da66d@www.fastmail.com> <AF27169A-00FC-4984-83C2-307EA885D7A1@yahoo.com> <11fe573a-24c3-47be-95ed-c601ec54f168@www.fastmail.com> <E23CF7F6-B69C-44C7-B356-4AB65E011268@yahoo.com> <B4D16405-1B0C-4500-866F-75F32FED235A@yahoo.com> <92f57afb-33cb-4d38-be17-4b8c81cb9c89@www.fastmail.com> <D6DC1C60-E50D-4A12-9F3B-6CEBA6A76748@yahoo.com> <6a0ade9d-26f2-4448-b066-0b06ed3ba5ef@www.fastmail.com> <9D4314E7-92C9-4BDD-B023-8C9BC3DCCAB0@yahoo.com> <E1EEDF91-42B1-4319-9513-7DE6FDE6E5F3@yahoo.com> <F1808C34-3C1A-44DC-BB23-2F0959AC64F5@yahoo.com> <db3de197-eb27-40ef-89ac-433b7fa72fe4@www.fastmail.com> <5E79BB07-D54B-4A8E-B592-F480211D0B92@yahoo.com> <88052e3f-4b79-45ca-8ebb-9fc19cbc558b@www.fastmail.com>
index | next in thread | previous in thread | raw e-mail
On 2020-Sep-23, at 09:09, Brandon Bergren <bdragon at FreeBSD.org> wrote: > On Wed, Sep 23, 2020, at 3:58 AM, Mark Millard wrote: >> On 2020-Sep-23, at 00:04, Brandon Bergren <bdragon at FreeBSD.org> wrote: >> >>> On Tue, Sep 22, 2020, at 7:50 PM, Mark Millard wrote: >>>> >>>> >>>> On 2020-Sep-22, at 17:18, Mark Millard <marklmi at yahoo.com> wrote: >>>>> By "immediately" I mean I do not even get close to >>>>> seeing the loader prompt. The display still shows >>>>> OpenFirmware content: it has not been cleared yet. >>>>> >>>> >>>> Just to be explicit: the dual socket G4 is the only type >>>> of G3/G4 that does make it to the loader prompt (and a >>>> little beyond). The G5 2 dual-core sockets is the only >>>> context that I've tried that gets very far past the >>>> loader prompt. >>> >>> This is strange. Loader works just fine on all of my G4 equipment. >>> >>> Are you making sure to use the "dev /memory@0 100000 1000 do-unmap" trick on 4.8.7f1 devices? >> >> I know nothing about that and have never had to do such a thing >> historically. I've never had to identify "4.8.7f1 devices". > > There is a bug in some versions of the PowerMac BootROM where a memory page at 0x100000 would remain mapped without being properly listed in the mmu properties (likely due to the way Open Firmware was initialized) that breaks bootloaders that touch that page. > > It is known to be a thing on at least 4.8.7f1 BootROM, but may also affect other versions. You can see the BootROM version on the OpenFirmware screen when the machine turns on. > > On affected devices, the bug can be permanently repaired using nvedit to execute the workaround automatically, or it can be typed in by hand every time. > > This is described on https://wiki.freebsd.org/powerpc I've been doing things this way with the SSDs since sometime in 2014 on the same machines since then. I've never run into the problem prior to now. >>> How are you starting loader? >> >> Turn the PowerMac on with the SSD already plugged onto the >> IDE adapter that I have in place. (The G3 is configured >> such that I also have to type mac-boot to OpenFirmware.) >> >> It is the same SSD being moved between the 2 dual-core socket G5, >> 2 socket G4, 1 socket G4, and the G3. So it is significant that >> the 2 socket G4/G5 do get to the loader prompt but the others >> do not. >> >> 1-socket G4/G3 example lines: >> >> QUOTE >> ofw_close: devh=0x0 >> >>>> FreeBSD/powerpc Open Firmware boot block >> Boot path: /pci@f2000000/mac-io@17/ata-4@1f000/@0: >> Boot loader: /boot/loader >> Boot volume: /pci@f2000000/mac-io@17/ata-4@1f000/@0:3 >> END QUOTE > > How was this SSD set up? The build is my own (cross build). For the kernel I install on the host to a directory, tar that to a PowerMac, and later expand the tar to the SSD in question. Like I've been doing since 2014 on the same set of PowerMacs. (The procedure avoids the little-endian host vs. big-endian UFS on the PowerMacs.) > When was the last time you reinstalled boot1.hfs? It been a while but this setup was working before the update to head -r365932 . When was the last time boot1.hfs had a required change? Recently? The same boot1.hfs on the same SSD gets to the loader prompt on any 2 socket PowerMac that I try. (I do not have access to a 1 socket 2-core PowerMac.) And, again, this same boot1.hfs on the same SSD worked before the update to head -r365932 . > You aren't trying to use memstick.img, correct? That's known to be be broken currently. I'm doing my own builds, the same as I did with the version installed and in use before I updated to head -r365932 . I've been doing my own builds since 2014. >> >> No more shows up for the 1 socket PowerMacs. >> >>> Is this on cdrom, network, or usb? >> >> SSD hanging off the IDE bus via an adapter. >> >>> To confirm, it doesn't get as far as the kernel loading spinner? >> >> It does not. See above. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07E0C1EE-647C-4BFD-A60F-71B02EA3FB13>