Date: Wed, 23 Sep 2020 12:17:57 -0500 From: "Brandon Bergren" <bdragon@FreeBSD.org> To: "Mark Millard" <marklmi@yahoo.com> Cc: "FreeBSD PowerPC ML" <freebsd-ppc@freebsd.org> Subject: =?UTF-8?Q?Re:_head_-r365932_on_PowerMac_G5_(2_dual-core_sockets):_Crashe?= =?UTF-8?Q?s_before_login_prompt_if_powerd_is_enabled_in_/etc/rc.conf?= Message-ID: <4e63a5ee-a452-4f04-99f2-3ab99c68944c@www.fastmail.com> In-Reply-To: <07E0C1EE-647C-4BFD-A60F-71B02EA3FB13@yahoo.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> <07E0C1EE-647C-4BFD-A60F-71B02EA3FB13@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 23, 2020, at 11:47 AM, Mark Millard wrote: > > 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. OK, you would have likely tripped over it by now then if any of your machines were affected by the bug, as it was breaking things on and off for *years* on specific machines until I finally went in and figured out what was ACTUALLY going on there. (FWIW, this had also been breaking Linux for years, especially where GRUB 2 was involved.) > >>>> 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 > > What is your boot command? Is it just the usual "boot hd:,\\:tbxi" or are you manually invoking boot1? (i.e. "boot hd:2,\ppc\boot1.elf /boot/loader") > > 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.) My normal procedure is to do cd release; make release TARGET=powerpc TARGET_ARCH=powerpc KERNCONF=GENERIC after doing a world / kernel build so I have fresh install media to burn to cd / usb. (Except for the machines that netboot. For those, I just installworld DESTDIR=/path/to/nfs/mount and use mergemaster to manage config file updates) > > > 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? May 1. I fixed a load address problem. Actually, now that I think about it, I think that that's actually what you're tripping over here. It seems like identical symptoms. See https://reviews.freebsd.org/rS360537 This was previously only working by accident. -- Brandon Bergren bdragon@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e63a5ee-a452-4f04-99f2-3ab99c68944c>