From owner-freebsd-ppc@FreeBSD.ORG Sun Feb 1 08:04:53 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 198656ED for ; Sun, 1 Feb 2015 08:04:53 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA1AB344 for ; Sun, 1 Feb 2015 08:04:51 +0000 (UTC) Received: (qmail 13997 invoked from network); 1 Feb 2015 08:04:44 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 1 Feb 2015 08:04:44 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Sun, 01 Feb 2015 03:04:44 -0500 (EST) Received: (qmail 18607 invoked from network); 1 Feb 2015 08:04:41 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Feb 2015 08:04:41 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 5D68F1C43AD for ; Sun, 1 Feb 2015 00:04:40 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: RE: HEADS UP: powerpc64 kernel format change [booted a PowerMac G5 quad-core] Message-Id: <2AD25D1A-80C0-473B-BD04-9AA512811AF6@dsl-only.net> Date: Sun, 1 Feb 2015 00:04:38 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2015 08:04:53 -0000 Just an FYI, not a request for anything. I've booted my powerpc64 11.0-CURRENT -r277990 "GENERIC64vtsc" variant = on a PowerMac G5 quad core, but a little oddly. I've also used the new = loader to boot 10.1-RELEASE-p5 and 10.1-STABLE (-r277808), = 10.1-RELEASE-p5 being a normal boot but 10.1-STABLE also being odd in = the same way as 11.0-CURRENT. (The oddity is not new to the -r277990 = context.) Before attempting this I'd already adapted my = powermac-g5-more-reliable-booting-investigation-hacks to powerpc64 = 11-CURRENT after the relocatable kernel changes touched ofwcall64.S and = I had booted a with-hack 11.0-CURRENT kernel before this. (The recent = Justin H. patch for fan/pump RPMs is also present, although the problem = powermac is gone.) Like for 10.1-STABLE, for 11-CURRENT (-R277990) the sequence buildworld, = buildkernel, installkernel, installworld, reboot failed to boot before = getting to the "any other key for a command prompt" stage, although the = SRR0 figure was different. %SRR0: 00000000.01c287ac (10.1-STABLE reports 1c277fc) %SRR1: 10000000.00003030 But the same technique that allows me to boot 10.1-STABLE works for = 11-CURRENT as well. More below for what I did to have 11-CURRENT = kernel+world running despite the above. To make swapping contexts easier I've established copies of the 3 = vintages of loader, each copy established just after the matching = installworld: $ ls -F /boot/loader /boot/loader1* /boot/loader* /boot/loader10.1S_from_usr_obj* /boot/loader10.1RE* /boot/loader11C* /boot/loader10.1RE_from_usr_obj* /boot/loader11C_from_usr_obj* /boot/loader10.1S* and I copy /boot/loader11C to /boot/loader to test using it for whatever = I'm going to boot with it. (I've not tried any that I copied from = /usr/obj/... I may just delete those.) "RE" stands for RelEng, "S" for = Stable, "C" for Current. Note that 10.1RE here is 10.1-RELEASE-p5 (RELENG -r277807) but with my = original powermac-g5-more-reliable-booting-investigation-hacks and the = fan/pump RPM patch. (My 10.1-STABLE has those as well.) I also have separate kernel copies (via INSTKERNNAME use): $ ls -Fd /boot/kernel* /boot/kernel/ /boot/kernel10.1RE/ /boot/kernel10.1S/ = /boot/kernel11C/ (Ignore /boot/kernel here. I tend to use the other ones.) And I use /boot/loader.conf to control which kernel is initially = started, such as: $ more /boot/loader.conf=20 kernel=3D"kernel10.1RE" verbose_loading=3D"YES" kern.vty=3Dvt The kernel10.RE one boots and runs fine with any of the 3 vintages of = loader. Listing kernel10.1S or kernel11C in loader.conf instead gets the = SRR0/SRR1 failures referenced above, even when loader (and world) is = from the matching buildworld. So I boot as above (kernel10.1RE) but use the "any other key for a = command prompt" to stop it and then (for example): unload boot kernel11C and that boots and runs fine if I've done the 11-CURRENT installworld = before the reboot. (At this point 10.1-RELEASE-p5 and 10.1-STABLE buildworlds (loader = updated) do not mix very well with 11-CURRENT kernels. "init: getting = kqueues resource limit invalid argument" notices are an example. And I = had kernel panics after a while for such combinations. So far the above = 11-CURRENT kernel+world combination seems okay despite the boot sequence = having a 10.1-RELEASE-p5 kernel variant involved for a bit.) $ freebsd-version -ku; uname -a 10.1-RELEASE-p5 11.0-CURRENT FreeBSD FBSDG5M1 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r277990M: Sat Jan = 31 18:27:29 PST 2015 = root@FBSDG5M1:/usr/obj/usr/home/markmi/src_11_current/sys/GENERIC64vtsc = powerpc Other details controlling how things were built (all 3 are built = similarly): $ more /etc/make.conf WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D MALLOC_PRODUCTION=3D $ more /etc/src.conf #WITH_DEBUG_FILES=3D #WITHOUT_CLANG=3D (I have separate svn source directory trees for 10.1-RELEASE-p5, = 10.1-STABLE (-r277808), and 11.0-CURRENT (-r277990).) $ more ~markmi/src_11_current/sys/powerpc/conf/GENERIC64vtsc include GENERIC64 ident GENERIC64vtsc nooptions PS3 #Sony Playstation 3 = HACK!!! to allow sc options DDB # HACK!!! to dump early crash = info (but 11.0-CURRENT already has it) options GDB # HACK!!! ... #options KTR #options KTR_MASK=3DKTR_TRAP #options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable extra checking typically used for FreeBSD 11.0-CURRENT: nooptions DEADLKRES #Enable the deadlock resolver nooptions INVARIANTS #Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT #Extra sanity checks of internal = structures, required by INVARIANTS nooptions WITNESS #Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN #Don't run witness on spinlocks = for speed nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones (My 10.1-RELEASE-p5 and 10.1-STABLE variants use the same file contents = as above.) $ svnlite status ~markmi/src_11_current/ M /home/markmi/src_11_current/sys/ddb/db_main.c M /home/markmi/src_11_current/sys/ddb/db_script.c ? /home/markmi/src_11_current/sys/powerpc/conf/GENERIC64vtsc M /home/markmi/src_11_current/sys/powerpc/ofw/ofw_machdep.c M /home/markmi/src_11_current/sys/powerpc/ofw/ofwcall64.S M = /home/markmi/src_11_current/sys/powerpc/powermac/powermac_thermal.c $ svnlite info ~markmi/src_11_current/ Path: /home/markmi/src_11_current Working Copy Root Path: /home/markmi/src_11_current URL: https://svn0.us-west.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn0.us-west.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 277990 Node Kind: directory Schedule: normal Last Changed Author: nwhitehorn Last Changed Rev: 277990 Last Changed Date: 2015-01-31 11:16:51 -0800 (Sat, 31 Jan 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Sun Feb 1 16:02:58 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D7838A40 for ; Sun, 1 Feb 2015 16:02:58 +0000 (UTC) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BDB90620 for ; Sun, 1 Feb 2015 16:02:58 +0000 (UTC) Received: from zeppelin.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.14.9) with ESMTPSA id t11G2tsl028835 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 1 Feb 2015 08:02:56 -0800 Message-ID: <54CE4E2F.3080807@freebsd.org> Date: Sun, 01 Feb 2015 08:02:55 -0800 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Subject: Re: HEADS UP: powerpc64 kernel format change [booted a PowerMac G5 quad-core] References: <2AD25D1A-80C0-473B-BD04-9AA512811AF6@dsl-only.net> In-Reply-To: <2AD25D1A-80C0-473B-BD04-9AA512811AF6@dsl-only.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVZUImfMOvUY/Xu2jza9jdDkE1No1MLqUQPY5mbrGqihi+bteCcy9hlNHsIzl6jklLmuIly5K20AIeDPYcnkkYyRzsxg6BJAxIM= X-Sonic-ID: C;ZPrVyCuq5BGDUmS47jkJAQ== M;nrhGySuq5BGDUmS47jkJAQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2015 16:02:58 -0000 So this has to be some kind of icache issue. If you unload and reload the *same* kernel, does it also help? -Nathan On 02/01/15 00:04, Mark Millard wrote: > Just an FYI, not a request for anything. > > I've booted my powerpc64 11.0-CURRENT -r277990 "GENERIC64vtsc" variant on a PowerMac G5 quad core, but a little oddly. I've also used the new loader to boot 10.1-RELEASE-p5 and 10.1-STABLE (-r277808), 10.1-RELEASE-p5 being a normal boot but 10.1-STABLE also being odd in the same way as 11.0-CURRENT. (The oddity is not new to the -r277990 context.) > > Before attempting this I'd already adapted my powermac-g5-more-reliable-booting-investigation-hacks to powerpc64 11-CURRENT after the relocatable kernel changes touched ofwcall64.S and I had booted a with-hack 11.0-CURRENT kernel before this. (The recent Justin H. patch for fan/pump RPMs is also present, although the problem powermac is gone.) > > Like for 10.1-STABLE, for 11-CURRENT (-R277990) the sequence buildworld, buildkernel, installkernel, installworld, reboot failed to boot before getting to the "any other key for a command prompt" stage, although the SRR0 figure was different. > > %SRR0: 00000000.01c287ac (10.1-STABLE reports 1c277fc) > %SRR1: 10000000.00003030 > > But the same technique that allows me to boot 10.1-STABLE works for 11-CURRENT as well. More below for what I did to have 11-CURRENT kernel+world running despite the above. > > To make swapping contexts easier I've established copies of the 3 vintages of loader, each copy established just after the matching installworld: > > $ ls -F /boot/loader /boot/loader1* > /boot/loader* /boot/loader10.1S_from_usr_obj* > /boot/loader10.1RE* /boot/loader11C* > /boot/loader10.1RE_from_usr_obj* /boot/loader11C_from_usr_obj* > /boot/loader10.1S* > > and I copy /boot/loader11C to /boot/loader to test using it for whatever I'm going to boot with it. (I've not tried any that I copied from /usr/obj/... I may just delete those.) "RE" stands for RelEng, "S" for Stable, "C" for Current. > > Note that 10.1RE here is 10.1-RELEASE-p5 (RELENG -r277807) but with my original powermac-g5-more-reliable-booting-investigation-hacks and the fan/pump RPM patch. (My 10.1-STABLE has those as well.) > > I also have separate kernel copies (via INSTKERNNAME use): > > $ ls -Fd /boot/kernel* > /boot/kernel/ /boot/kernel10.1RE/ /boot/kernel10.1S/ /boot/kernel11C/ > > (Ignore /boot/kernel here. I tend to use the other ones.) > > And I use /boot/loader.conf to control which kernel is initially started, such as: > > $ more /boot/loader.conf > kernel="kernel10.1RE" > verbose_loading="YES" > kern.vty=vt > > The kernel10.RE one boots and runs fine with any of the 3 vintages of loader. Listing kernel10.1S or kernel11C in loader.conf instead gets the SRR0/SRR1 failures referenced above, even when loader (and world) is from the matching buildworld. > > So I boot as above (kernel10.1RE) but use the "any other key for a command prompt" to stop it and then (for example): > > unload > boot kernel11C > > and that boots and runs fine if I've done the 11-CURRENT installworld before the reboot. > > (At this point 10.1-RELEASE-p5 and 10.1-STABLE buildworlds (loader updated) do not mix very well with 11-CURRENT kernels. "init: getting kqueues resource limit invalid argument" notices are an example. And I had kernel panics after a while for such combinations. So far the above 11-CURRENT kernel+world combination seems okay despite the boot sequence having a 10.1-RELEASE-p5 kernel variant involved for a bit.) > > $ freebsd-version -ku; uname -a > 10.1-RELEASE-p5 > 11.0-CURRENT > FreeBSD FBSDG5M1 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r277990M: Sat Jan 31 18:27:29 PST 2015 root@FBSDG5M1:/usr/obj/usr/home/markmi/src_11_current/sys/GENERIC64vtsc powerpc > > > > Other details controlling how things were built (all 3 are built similarly): > > $ more /etc/make.conf > WRKDIRPREFIX=/usr/obj/portswork > WITH_DEBUG= > MALLOC_PRODUCTION= > > $ more /etc/src.conf > #WITH_DEBUG_FILES= > #WITHOUT_CLANG= > > (I have separate svn source directory trees for 10.1-RELEASE-p5, 10.1-STABLE (-r277808), and 11.0-CURRENT (-r277990).) > > $ more ~markmi/src_11_current/sys/powerpc/conf/GENERIC64vtsc > include GENERIC64 > ident GENERIC64vtsc > > nooptions PS3 #Sony Playstation 3 HACK!!! to allow sc > > options DDB # HACK!!! to dump early crash info (but 11.0-CURRENT already has it) > options GDB # HACK!!! ... > #options KTR > #options KTR_MASK=KTR_TRAP > #options KTR_CPUMASK=0xF > #options KTR_VERBOSE > > # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt historically mishandled during booting > device sc > #device kbdmux # HACK: already listed by vt > options SC_OFWFB # OFW frame buffer > options SC_DFLT_FONT # compile font in > makeoptions SC_DFLT_FONT=cp437 > > > # Disable extra checking typically used for FreeBSD 11.0-CURRENT: > nooptions DEADLKRES #Enable the deadlock resolver > nooptions INVARIANTS #Enable calls of extra sanity checking > nooptions INVARIANT_SUPPORT #Extra sanity checks of internal structures, required by INVARIANTS > nooptions WITNESS #Enable checks to detect deadlocks and cycles > nooptions WITNESS_SKIPSPIN #Don't run witness on spinlocks for speed > nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones > > (My 10.1-RELEASE-p5 and 10.1-STABLE variants use the same file contents as above.) > > $ svnlite status ~markmi/src_11_current/ > M /home/markmi/src_11_current/sys/ddb/db_main.c > M /home/markmi/src_11_current/sys/ddb/db_script.c > ? /home/markmi/src_11_current/sys/powerpc/conf/GENERIC64vtsc > M /home/markmi/src_11_current/sys/powerpc/ofw/ofw_machdep.c > M /home/markmi/src_11_current/sys/powerpc/ofw/ofwcall64.S > M /home/markmi/src_11_current/sys/powerpc/powermac/powermac_thermal.c > > $ svnlite info ~markmi/src_11_current/ > Path: /home/markmi/src_11_current > Working Copy Root Path: /home/markmi/src_11_current > URL: https://svn0.us-west.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 277990 > Node Kind: directory > Schedule: normal > Last Changed Author: nwhitehorn > Last Changed Rev: 277990 > Last Changed Date: 2015-01-31 11:16:51 -0800 (Sat, 31 Jan 2015) > > === > Mark Millard > markmi at dsl-only.net > > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@FreeBSD.ORG Sun Feb 1 23:26:53 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73921328 for ; Sun, 1 Feb 2015 23:26:53 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A3233C6 for ; Sun, 1 Feb 2015 23:26:52 +0000 (UTC) Received: (qmail 24346 invoked from network); 1 Feb 2015 23:26:51 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 1 Feb 2015 23:26:51 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Sun, 01 Feb 2015 18:26:51 -0500 (EST) Received: (qmail 477 invoked from network); 1 Feb 2015 23:26:50 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Feb 2015 23:26:50 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 842DF1C43DC; Sun, 1 Feb 2015 15:26:45 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: HEADS UP: powerpc64 kernel format change [boot-time kern.vty=vt temporary display oddity] From: Mark Millard In-Reply-To: <2AD25D1A-80C0-473B-BD04-9AA512811AF6@dsl-only.net> Date: Sun, 1 Feb 2015 15:26:48 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <38F3B8FD-A14C-4A48-9CC9-F140D3B21C89@dsl-only.net> References: <2AD25D1A-80C0-473B-BD04-9AA512811AF6@dsl-only.net> To: Nathan Whitehorn X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Feb 2015 23:26:53 -0000 I've done a bunch of PowerMac G5 quad-core boots and have some behavior = to report that might be of interest. For my 11.0-CURRENT (-r277990) boots (stop 10.1-RELASE-p5 then unload = then boot kernel11C, details later): During the kernel11C boot when kern.vty=3Dvt there is always a block of = boot message lines that get extra text on screen in odd positions, some = (all?) of the extra text with unusual (non-black) background colors, for = example. I've not noticed such in prior 11.0-CURRENT vintages that I've = booted. Such text does not show up in /var/log/messages or the like, = just on screen. The lines from the boot that get this are approximately = the range: Feb 1 13:22:40 FBSDG5M1 kernel: pci3: on pcib3 Feb 1 13:22:40 FBSDG5M1 kernel: bge0: mem 0xfa530000-0xfa53ffff,0xfa520000-0xfa52ffff irq 66 at = device 4.0 on pci3 Feb 1 13:22:40 FBSDG5M1 kernel: bge0: CHIP ID 0x00008003; ASIC REV = 0x08; CHIP REV 0x80; PCI-X 33 MHz Feb 1 13:22:40 FBSDG5M1 kernel: miibus0: on bge0 Feb 1 13:22:40 FBSDG5M1 kernel: brgphy0: PHY 1 on miibus0 Feb 1 13:22:40 FBSDG5M1 kernel: brgphy0: 10baseT, 10baseT-FDX, = 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, = 1000baseT-FDX-master, auto, auto-flow Feb 1 13:22:40 FBSDG5M1 kernel: bge0: Ethernet address: = 00:14:51:68:5a:44 Feb 1 13:22:40 FBSDG5M1 kernel: bge1: mem 0xfa510000-0xfa51ffff,0xfa500000-0xfa50ffff irq 67 at = device 4.1 on pci3 Feb 1 13:22:40 FBSDG5M1 kernel: bge1: CHIP ID 0x00008003; ASIC REV = 0x08; CHIP REV 0x80; PCI-X 33 MHz Feb 1 13:22:40 FBSDG5M1 kernel: miibus1: on bge1 Feb 1 13:22:40 FBSDG5M1 kernel: brgphy1: PHY 1 on miibus1 Feb 1 13:22:40 FBSDG5M1 kernel: brgphy1: 10baseT, 10baseT-FDX, = 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, = 1000baseT-FDX-master, auto, auto-flow Feb 1 13:22:40 FBSDG5M1 kernel: bge1: Ethernet address: = 00:14:51:68:5a:45 Feb 1 13:22:40 FBSDG5M1 kernel: pcib4: at device = 3.0 on pci1 As for the video card: The Radeon identified as... Chipset: "ATI Radeon = X1950" (ChipID =3D 0x7240). The screen used is small enough that the = historical 2560x1440 boot display issue for this card is not involved. With kern.vty=3Dsc used instead no such odd text appears. Booting 10.1-RELEASE-p5 (directly) and 10.1-STABLE (-r277808 via the = same sort of sequence as indicated below) do not get this display oddity = with any of the 3 loader versions [from 10.1-RELEASE-p5, 10.1-STABLE = (-r277808), and 11.0-CURRENT (-r277990)], be it vt or sc style. Context: using the /boot/loader file from 11.0-CURRENT (-r277990)... $ freebsd-version -ku; uname -a 10.1-RELEASE-p5 11.0-CURRENT FreeBSD FBSDG5M1 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r277990M: Sat Jan = 31 18:27:29 PST 2015 = root@FBSDG5M1:/usr/obj/usr/home/markmi/src_11_current/sys/GENERIC64vtsc = powerpc The 11.0-CURRENT build is not the usual debug build but is like my = 10.1-RELEASE-p5 and 10.1-STABLE builds: all use the same GENERIC64vtsc = content that adjusts the GENERIC64 that is included. There are explicit = nooptions to disable various potential debug options. $ ls -Fd /boot/kernel* /boot/kernel/ /boot/kernel10.1RE/ /boot/kernel10.1S/ = /boot/kernel11C/ $ more /boot/loader.conf=20 kernel=3D"kernel10.1RE" verbose_loading=3D"YES" kern.vty=3Dvt I boot as above (kernel10.1RE, i.e. a variant of 10.1-RELEASE-p5 from = RelEng) but use the "any other key for a command prompt" to stop it and = then I: unload boot kernel11C This sequence is because directly listing "kernel11C" in = /boot/loader.conf fails to boot far enough to reach the "any other key = for a command prompt" stage. (But its text=3D data=3D syms=3D[...] = loading line does show up before it fails when kernel11C is tried = directly.) The direct-booting issue is not new to -r277990 and = 10.1-STABLE also has had it and continues to. I'm not reporting this = aspect of things as part of a -r277990 problem but I figured the odd = boot style should be noted as part of the test context. $ svnlite status ~markmi/src_11_current/ M /home/markmi/src_11_current/sys/ddb/db_main.c M /home/markmi/src_11_current/sys/ddb/db_script.c ? /home/markmi/src_11_current/sys/powerpc/conf/GENERIC64vtsc M /home/markmi/src_11_current/sys/powerpc/ofw/ofw_machdep.c M /home/markmi/src_11_current/sys/powerpc/ofw/ofwcall64.S M = /home/markmi/src_11_current/sys/powerpc/powermac/powermac_thermal.c The *.[cS] files other than powermac_thermal.c and part of GENERIC64vtsc = are my hacks for investigating early-boot problems on PowerMac G5s and = avoiding the most frequent one from stopping my boots. = powermac_thermal.c is a Justin H. patch for making the fan/pump RPMs = more aggressive but the G5 it was used to test is gone. My = 10.1-RELEASE-p5 and 10.1-STABLE variants have the same hacks and patch, = other than the 11.0-CURRENT ofwcall64.S details were adjusted for the = relocatable kernel changes. (Stick with non-volitile register storage in = more places.) The below forward has some more context detail included. =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Feb-1, at 12:04 AM, Mark Millard wrote: Just an FYI, not a request for anything. I've booted my powerpc64 11.0-CURRENT -r277990 "GENERIC64vtsc" variant = on a PowerMac G5 quad core, but a little oddly. I've also used the new = loader to boot 10.1-RELEASE-p5 and 10.1-STABLE (-r277808), = 10.1-RELEASE-p5 being a normal boot but 10.1-STABLE also being odd in = the same way as 11.0-CURRENT. (The oddity is not new to the -r277990 = context.) Before attempting this I'd already adapted my = powermac-g5-more-reliable-booting-investigation-hacks to powerpc64 = 11-CURRENT after the relocatable kernel changes touched ofwcall64.S and = I had booted a with-hack 11.0-CURRENT kernel before this. (The recent = Justin H. patch for fan/pump RPMs is also present, although the problem = powermac is gone.) Like for 10.1-STABLE, for 11-CURRENT (-R277990) the sequence buildworld, = buildkernel, installkernel, installworld, reboot failed to boot before = getting to the "any other key for a command prompt" stage, although the = SRR0 figure was different. %SRR0: 00000000.01c287ac (10.1-STABLE reports 1c277fc) %SRR1: 10000000.00003030 But the same technique that allows me to boot 10.1-STABLE works for = 11-CURRENT as well. More below for what I did to have 11-CURRENT = kernel+world running despite the above. To make swapping contexts easier I've established copies of the 3 = vintages of loader, each copy established just after the matching = installworld: $ ls -F /boot/loader /boot/loader1* /boot/loader* /boot/loader10.1S_from_usr_obj* /boot/loader10.1RE* /boot/loader11C* /boot/loader10.1RE_from_usr_obj* /boot/loader11C_from_usr_obj* /boot/loader10.1S* and I copy /boot/loader11C to /boot/loader to test using it for whatever = I'm going to boot with it. (I've not tried any that I copied from = /usr/obj/... I may just delete those.) "RE" stands for RelEng, "S" for = Stable, "C" for Current. Note that 10.1RE here is 10.1-RELEASE-p5 (RELENG -r277807) but with my = original powermac-g5-more-reliable-booting-investigation-hacks and the = fan/pump RPM patch. (My 10.1-STABLE has those as well.) I also have separate kernel copies (via INSTKERNNAME use): $ ls -Fd /boot/kernel* /boot/kernel/ /boot/kernel10.1RE/ /boot/kernel10.1S/ = /boot/kernel11C/ (Ignore /boot/kernel here. I tend to use the other ones.) And I use /boot/loader.conf to control which kernel is initially = started, such as: $ more /boot/loader.conf=20 kernel=3D"kernel10.1RE" verbose_loading=3D"YES" kern.vty=3Dvt The kernel10.RE one boots and runs fine with any of the 3 vintages of = loader. Listing kernel10.1S or kernel11C in loader.conf instead gets the = SRR0/SRR1 failures referenced above, even when loader (and world) is = from the matching buildworld. So I boot as above (kernel10.1RE) but use the "any other key for a = command prompt" to stop it and then (for example): unload boot kernel11C and that boots and runs fine if I've done the 11-CURRENT installworld = before the reboot. (At this point 10.1-RELEASE-p5 and 10.1-STABLE buildworlds (loader = updated) do not mix very well with 11-CURRENT kernels. "init: getting = kqueues resource limit invalid argument" notices are an example. And I = had kernel panics after a while for such combinations. So far the above = 11-CURRENT kernel+world combination seems okay despite the boot sequence = having a 10.1-RELEASE-p5 kernel variant involved for a bit.) $ freebsd-version -ku; uname -a 10.1-RELEASE-p5 11.0-CURRENT FreeBSD FBSDG5M1 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r277990M: Sat Jan = 31 18:27:29 PST 2015 = root@FBSDG5M1:/usr/obj/usr/home/markmi/src_11_current/sys/GENERIC64vtsc = powerpc Other details controlling how things were built (all 3 are built = similarly): $ more /etc/make.conf WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D MALLOC_PRODUCTION=3D $ more /etc/src.conf #WITH_DEBUG_FILES=3D #WITHOUT_CLANG=3D (I have separate svn source directory trees for 10.1-RELEASE-p5, = 10.1-STABLE (-r277808), and 11.0-CURRENT (-r277990).) $ more ~markmi/src_11_current/sys/powerpc/conf/GENERIC64vtsc include GENERIC64 ident GENERIC64vtsc nooptions PS3 #Sony Playstation 3 = HACK!!! to allow sc options DDB # HACK!!! to dump early crash = info (but 11.0-CURRENT already has it) options GDB # HACK!!! ... #options KTR #options KTR_MASK=3DKTR_TRAP #options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable extra checking typically used for FreeBSD 11.0-CURRENT: nooptions DEADLKRES #Enable the deadlock resolver nooptions INVARIANTS #Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT #Extra sanity checks of internal = structures, required by INVARIANTS nooptions WITNESS #Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN #Don't run witness on spinlocks = for speed nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones (My 10.1-RELEASE-p5 and 10.1-STABLE variants use the same file contents = as above.) $ svnlite status ~markmi/src_11_current/ M /home/markmi/src_11_current/sys/ddb/db_main.c M /home/markmi/src_11_current/sys/ddb/db_script.c ? /home/markmi/src_11_current/sys/powerpc/conf/GENERIC64vtsc M /home/markmi/src_11_current/sys/powerpc/ofw/ofw_machdep.c M /home/markmi/src_11_current/sys/powerpc/ofw/ofwcall64.S M = /home/markmi/src_11_current/sys/powerpc/powermac/powermac_thermal.c $ svnlite info ~markmi/src_11_current/ Path: /home/markmi/src_11_current Working Copy Root Path: /home/markmi/src_11_current URL: https://svn0.us-west.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn0.us-west.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 277990 Node Kind: directory Schedule: normal Last Changed Author: nwhitehorn Last Changed Rev: 277990 Last Changed Date: 2015-01-31 11:16:51 -0800 (Sat, 31 Jan 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 2 00:04:36 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08F8F589 for ; Mon, 2 Feb 2015 00:04:36 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A83C6917 for ; Mon, 2 Feb 2015 00:04:35 +0000 (UTC) Received: (qmail 472 invoked from network); 2 Feb 2015 00:04:34 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 2 Feb 2015 00:04:34 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Sun, 01 Feb 2015 19:04:34 -0500 (EST) Received: (qmail 11530 invoked from network); 2 Feb 2015 00:04:33 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Feb 2015 00:04:33 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 93BFC1C43CD; Sun, 1 Feb 2015 16:04:28 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: HEADS UP: powerpc64 kernel format change [booted a PowerMac G5 quad-core] Date: Sun, 1 Feb 2015 16:04:31 -0800 Message-Id: <0FE686F0-64A5-4DD2-8C95-1A8E646FA55F@dsl-only.net> To: Nathan Whitehorn Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 00:04:36 -0000 Nathan W. suggested "If you unload and reload the *same* kernel, does it = also help?". I can not do that test for 10.1-STABLE or 11.0-CURRENT as the initial = kernel because either of the following lines in /boot/loader.conf fails = to get to the "any other key for a command prompt" stage: I get no valid = opportunity to try unload then boot if I start with these kernels. kernel=3D"kernel10.1S" kernel=3D"kernel11C" In other words: after the error one is back in the context for = "mac-boot" and "shut-down" and the like (Apple's context, not = FreeBSD's). For example "boot ud:2,\ppc\bootinfo.txt" at that point for = booting from a memory stick does not work, giving some message about = being unable to do the memory allocation it needs or some such. (I do = not remember the details.) The only one of the 3 buildworld build kernel installkernel installworld = sequences that lets me reboot far enough to get to the "any other key = for a command prompt" is: kernel=3D"kernel10.1RE" and from there the unload then boot sequence works for booting all 3. (Later power-off/power-on's get the same boot-attempt initial results as = the initial "shutdown -r now" for all 3 kernels. The initial reboot is = not unique.) kernel10.1RE also has no trouble booting if I do not stop it. I'll note that all 3 kernels do output the line that shows text=3D data=3D= syms=3D[...]. The crashing ones crash between that line and the = following "any other key for a command prompt" line. I had described how I boot the problematical kernels: > And I use /boot/loader.conf to control which kernel is initially = started, such as: > > $ more /boot/loader.conf > kernel=3D"kernel10.1RE" > verbose_loading=3D"YES" > kern.vty=3Dvt > > The kernel10.RE one boots and runs fine with any of the 3 vintages of = loader. Listing kernel10.1S or kernel11C in loader.conf instead gets the = SRR0/SRR1 failures referenced above, even when loader (and world) is = from the matching buildworld. > > So I boot as above (kernel10.1RE) but use the "any other key for a = command prompt" to stop it and then (for example): > > unload > boot kernel11C > > and that boots and runs fine if I've done the 11-CURRENT installworld = before the reboot. I had also described the errors reported for kernel10.1S and kernel11C: > Like for 10.1-STABLE, for 11-CURRENT (-R277990) the sequence = buildworld, buildkernel, installkernel, installworld, reboot failed to = boot before getting to the "any other key for a command prompt" stage, = although the SRR0 figure was different. > > %SRR0: 00000000.01c287ac (10.1-STABLE reports 1c277fc) > %SRR1: 10000000.00003030 Usually that is indicated as a Invalid memory access but sometimes as a = Decrementer exception. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 2 03:15:16 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E46522D for ; Mon, 2 Feb 2015 03:15:16 +0000 (UTC) Received: from sasl.smtp.pobox.com (pb-sasl1.int.icgroup.com [208.72.237.25]) by mx1.freebsd.org (Postfix) with ESMTP id EA2A0DB8 for ; Mon, 2 Feb 2015 03:15:15 +0000 (UTC) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id D6FB534051; Sun, 1 Feb 2015 22:15:08 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject :mime-version:content-type:from:in-reply-to:resent-from:date :content-transfer-encoding:resent-date:message-id:references :resent-to:to:resent-message-id; s=sasl; bh=btIB1SGToTEYja5a0YQn wdlX1vM=; b=hauCcmsUVXuz67/KRPMvESswpNoU3eE8OKQ23Av93q3xfanHyE7B iToCshJnEkcP/6xIRHLcT5GluH73IM+WTJ6OzeYz1FJ65aRjBSgtWYQ4sBscArr3 zv9Vi2aqTwmhYnPTLpDBcfPs/SIbo1oCmvpOnSXQL9j2LSuT9AS96+I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject :mime-version:content-type:from:in-reply-to:resent-from:date :content-transfer-encoding:resent-date:message-id:references :resent-to:to:resent-message-id; q=dns; s=sasl; b=YF4v3QO/khn+tw wn0DmJ8lgZckfXFhj21546CL8rykm5LUdDWV7nVYuTjXli4riCsZCsihJ6f2JWZD Vjw5KD6e4E1A3vh/6wZs1DzKljLA1ZPxOHByRXiaILeG2iuSERhV5Au0SrxsNJTa +FD1ku/kGl/ATfcdd7nLlCKHhzm0Y= Received: from pb-sasl1.int.icgroup.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id C2C7D34050; Sun, 1 Feb 2015 22:15:08 -0500 (EST) Received: from almini.rcthomas.org (unknown [208.53.120.31]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-sasl1.pobox.com (Postfix) with ESMTPSA id 1624E3404F; Sun, 1 Feb 2015 22:15:07 -0500 (EST) Subject: Successfully installed FreeBSD 10.1 on Apple PowerMac G5 -- BUT -- system freezes after a few minutes of running. Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Rick Thomas In-Reply-To: Resent-From: Rick Thomas Date: Mon, 26 Jan 2015 01:27:32 -0800 Content-Transfer-Encoding: quoted-printable Resent-Date: Sun, 1 Feb 2015 19:15:04 -0800 Message-Id: References: <8919F05D-3F70-4086-ACD5-7786D6437FE3@pobox.com> Resent-To: freebsd-ppc@freebsd.org To: freebsd-ppc-request@freebsd.org X-Mailer: Apple Mail (2.1878.6) X-Pobox-Relay-ID: B0FF1656-AA89-11E4-B191-B05EFC961345-02150157!pb-sasl1.pobox.com Resent-Message-Id: <20150202031508.C2C7D34050@pb-sasl1.pobox.com> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 03:15:16 -0000 I successfully installed my dual-core PowerMac G5 from the powerpc64 = FreeBSD 10.1 =93disk1=94 CD. However, when I boot the resulting setup, it works for a few minutes = then freezes; I get no response to the keyboard or to pings =97 both = were responsive during the few minutes until the freezup. Waiting for a few minutes more after the freezup, eventually the fans = start to run at top speed and I have to force-halt the machine by = pushing the power switch for 10 seconds. No messages appear on the console. Does anyone have any idea what=92s going on and what I can do about it? = How can I find out? Thanks! Rick From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 2 07:05:56 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 69EED91 for ; Mon, 2 Feb 2015 07:05:56 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 256307F4 for ; Mon, 2 Feb 2015 07:05:55 +0000 (UTC) Received: (qmail 514 invoked from network); 2 Feb 2015 07:05:53 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 2 Feb 2015 07:05:53 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Mon, 02 Feb 2015 02:05:53 -0500 (EST) Received: (qmail 4361 invoked from network); 2 Feb 2015 07:05:53 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Feb 2015 07:05:53 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 45B5C1C43B0 for ; Sun, 1 Feb 2015 23:05:46 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: powerpc64 10.1-RELEASE-p5 variant on PowerMac G5 Quad-Core: "DO-QUIESCE finished" notice displayed by openfirmware Message-Id: <8905A249-5E89-43B1-93C9-8F0CF36B3490@dsl-only.net> Date: Sun, 1 Feb 2015 23:05:51 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 07:05:56 -0000 powerpc64 PowerMac G5 quad-core (with lots of RAM) with a = 10.1-RELEASE-p5 variant context (shown as booted from the SSD): $ freebsd-version -ku; uname -a 10.1-RELEASE-p5 10.1-RELEASE-p5 FreeBSD FBSDG5M1 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5 #0 r277808M: = Fri Jan 30 00:58:33 PST 2015 = root@FBSDG5M1:/usr/obj/usr/home/markmi/src_10_1_releng/sys/GENERIC64vtsc = powerpc I produced a bootable memorystick from this context. (See below.) I got = a surprise when I booted the memory stick: It put out a "DO-QUIESCE finished" notice (white background and black = text) in the upper left corner of the screen during FreeBSD's boot = sequence, after the screen was cleared to a black background. It was = even after some FreeBSD text had been displayed (since I cause text to = show up earlier than the default build). As far as I can tell = 10.1-RELEASE-p5 has no such message of its own. (But it does call to = request the quiesce.) As far as I know this message has not historically = shown up under usual forms of FreeBSD booting. The message shows up every time I boot that memory stick (CMD-OPT-OF = boot of G5 then "boot ud:2,\ppc\bootinfo,txt"). It does not show up for = booting the 10.1-RELEASE-p5 variant from the SSD that the memory stick = was make from. No FreeBSD boot I've ever done before showed this = message. It leaves me wondering if lack of the message is an indication of = quiesce not completing. How did I produce the memory stick? Note: To use "make memstick" below successfully I first forced the = existence of the /usr/obj/.../sys/GENERIC/... paths by adding a symbolic = link to the real directory for my build: $ ls -Fpal /usr/obj/usr/home/markmi/src_10_1_releng/sys/ total 40 drwxr-xr-x 4 root wheel 512 Feb 1 20:17 ./ drwxr-xr-x 20 root wheel 512 Jan 31 09:19 ../ lrwxr-xr-x 1 root wheel 13 Feb 1 20:17 GENERIC64 -> = GENERIC64vtsc drwxr-xr-x 3 root wheel 28672 Jan 30 00:59 GENERIC64vtsc/ drwxr-xr-x 8 root wheel 512 Jan 31 07:50 boot/ With that in place I did: $ cd ~markmi/src_10_1_releng/release/ $ make memstick ... $ ls -Fpal *.img -rw-r--r-- 1 root wheel 878282752 Feb 1 20:56 memstick.img $ dd if=3Dmemstick.img of=3D/dev/da0 bs=3D10240 conv=3Dsync (So the stick was already plugged in but no file system from it was = mounted at the time.) Note: after the above ~markmi/src_10_1_releng/... had gone from around = 2G Bytes to more like 4.6G Bytes. (I do not know about peak usage.) Context details for the 10.1-RELEASE-p5 variant (not showing the ? = (extra) files for svnlite status): $ svnlite status ~markmi/src_10_1_releng/ M /home/markmi/src_10_1_releng/sys/ddb/db_main.c M /home/markmi/src_10_1_releng/sys/ddb/db_script.c M /home/markmi/src_10_1_releng/sys/powerpc/ofw/ofw_machdep.c M /home/markmi/src_10_1_releng/sys/powerpc/ofw/ofwcall64.S M = /home/markmi/src_10_1_releng/sys/powerpc/powermac/powermac_thermal.c There is the extra file = ~markmi/src_10_1_releng/sys/powerpc/conf/GENERIC64vtsc that I used via = KERNCONF=3DGENERIC64vtsc as well. $ more /etc/make.conf WRKDIRPREFIX=3D/usr/obj/portswork WITH_DEBUG=3D MALLOC_PRODUCTION=3D $ more /etc/src.conf #WITH_DEBUG_FILES=3D #WITHOUT_CLANG=3D $ more ~markmi/src_10_1_releng/sys/powerpc/conf/GENERIC64vtsc include GENERIC64 ident GENERIC64vtsc nooptions PS3 #Sony Playstation 3 = HACK!!! to allow sc options DDB # HACK!!! to dump early crash = info (but 11.0-CURRENT already has it) options GDB # HACK!!! ... #options KTR #options KTR_MASK=3DKTR_TRAP #options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable extra checking typically used for FreeBSD 11.0-CURRENT: nooptions DEADLKRES #Enable the deadlock resolver nooptions INVARIANTS #Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT #Extra sanity checks of internal = structures, required by INVARIANTS nooptions WITNESS #Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN #Don't run witness on spinlocks = for speed nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones (My 11.0-CURRENT and 10.1-STABLE variants use the same file contents as = above, other than ofwcall64.S details for 11.0-CURRENT.) $ more /boot/loader.conf kernel=3D"kernel" verbose_loading=3D"YES" kern.vty=3Dvt (I actually normally build and use kernel10.1RE but I happened to have = reconstructed /boot/kernel to be 10.1-RELEASE-p5 based just before this = experiment.) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 2 08:05:32 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 463E43C0 for ; Mon, 2 Feb 2015 08:05:32 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 016D5D45 for ; Mon, 2 Feb 2015 08:05:31 +0000 (UTC) Received: (qmail 23691 invoked from network); 2 Feb 2015 08:05:24 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 2 Feb 2015 08:05:24 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Mon, 02 Feb 2015 03:05:24 -0500 (EST) Received: (qmail 28794 invoked from network); 2 Feb 2015 08:05:24 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Feb 2015 08:05:24 -0000 X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 666A91C43B0 for ; Mon, 2 Feb 2015 00:05:23 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Successfully installed FreeBSD 10.1 on Apple PowerMac G5 -- BUT -- system freezes after a few minutes of running. Message-Id: <25A7C3E9-BEDB-4DA3-B9F7-08F2C299C119@dsl-only.net> Date: Mon, 2 Feb 2015 00:05:22 -0800 To: FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 08:05:32 -0000 If every boot gives some time before things freeze up you might be able = to extract and report the outputs of commands like: $ freebsd-version -ku; uname -a 10.1-RELEASE-p5 10.1-RELEASE-p5 FreeBSD FBSDG5M1 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5 #0 r277808M: = Fri Jan 30 00:58:33 PST 2015 = root@FBSDG5M1:/usr/obj/usr/home/markmi/src_10_1_releng/sys/GENERIC64vtsc = powerpc (There is more than one 'powerpc64 FreeBSD 10.1 "disk1" CD' that can be = burned, such 10.1-RELEASE vs., say, a recent 10.1-STABLE. But it turns = out that until very recently powerpc64 CD burns did not work for booting = PowerMac G5s so more than normal is known about which versions could = have be installed from a CD.) Despite the mention of there being no console messages I list some = basics below about dumping messages out anyway... $ tail /var/log/messages Feb 1 21:37:40 FBSDG5M1 kernel: uhid1: on usbus1 Feb 1 21:37:40 FBSDG5M1 kernel: hid_get_item: Number of items truncated = to 255 Feb 1 21:37:40 FBSDG5M1 last message repeated 2 times Feb 1 21:37:41 FBSDG5M1 ntpd[991]: ntpd 4.2.4p5-a (1) Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Activating service = name=3D'org.freedesktop.ConsoleKit' (using servicehelper) Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Activating service = name=3D'org.freedesktop.PolicyKit1' (using servicehelper) Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Successfully activated = service 'org.freedesktop.PolicyKit1' Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Successfully activated = service 'org.freedesktop.ConsoleKit' Feb 1 21:37:52 FBSDG5M1 ntpd[992]: time reset +1.748777 s Feb 1 21:38:01 FBSDG5M1 login: ROOT LOGIN (root) ON ttyv0 $ dmesg -a | tail Configuring vt: blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting sendmail_submit. Starting sendmail_msp_queue. Starting cron. Starting background file system checks in 60 seconds. Sun Feb 1 21:37:42 PST 2015 Feb 1 21:38:01 FBSDG5M1 login: ROOT LOGIN (root) ON ttyv0 tail by itself may not give enough context. Full copies would be nice = but I do not know about fitting the time before the hangup. The intent is to have a more complete specification of which 10.1 = variant and to see if problems are being logged before the complete = hangup. Others may well have better suggestions than mine for getting evidence. You should probably indicate if you are using just the console vs., say, = X11. (Although it is probably just the console if it never stayed up = long enough to establish more context.) Some folks may want to know the = video card involved or other configuration information, even for simple = console usage. Historically for a base system configuration (video card & monitor, SSD = appropriate to the SATA vintage, appropriate superdrive vintage/variant = that FreeBSD would tolerate) if I've made it to the login prompt and I = had not mixed and matched distinct kernel and world vintages for some = reason then I've had no later troubles with panics, hangups, or the like = for 10.0 or 10.1 vintages that I've installed. But that was after I removed all the PCI-Express cards (G5 quad-core) = but the video: My earlier attempts at using the pre-existing SATA cards = and SSD's/disks from them was unreliable even for simple console usage. = I took the direction of simplifying/removing stuff until what was left = just worked, such as the built-in SATA. I've not gone back yet to figure = out if I can make anything that I removed work well. (I'm still = learning/investigating other things for FreeBSD and am in no rush about = what I removed.) I temporarily had my hands on a PowerMac G5 that would overheat if kept = busy. But its fan would be going faster than normal after warming up = while idle. The fans would go full speed well before the shutdown when = it would overheat. So that sort of issue is not a match to what you = report. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 2 20:20:45 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA16A8EF for ; Mon, 2 Feb 2015 20:20:45 +0000 (UTC) Received: from sasl.smtp.pobox.com (pb-sasl1.int.icgroup.com [208.72.237.25]) by mx1.freebsd.org (Postfix) with ESMTP id A406BD1D for ; Mon, 2 Feb 2015 20:20:45 +0000 (UTC) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id A741E3410B; Mon, 2 Feb 2015 15:20:43 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=sasl; bh= bgnDGA2+1007ikd24Jkrn0EtfZE=; b=GyJ2pzlRVm+NskhhY5yeWAIMHuGGGQyo 2JqmFvWuPRQUxClNUuxT2vZNUzRkTEuyqKRNk9rpIohNLYEeYGMFKweqxvG1mZ/p yIngxvrNZs7xFWjhw2NKZb/wOdILZAxaj/S+UFOKxZCFQUu1qgVnj3VOiYsSeF+B f2q2G7MAjTs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= sasl; b=a3YELyYClY3BWJcVZBDqlLIxoWc+Msft2vUkI39CIIr2hSbb74xYl0fl DLqIRTOII3GXy4vGPEDBY/L5ldrugDgc6vOvFjjPoENBDVu2JQy9a01T7qT3XqG3 XlSJ3VwqwnuySUwYlgGAiORxYvveW8gYYRMpQVI5zotbXW8o/l4= Received: from pb-sasl1.int.icgroup.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id 9E3F83410A; Mon, 2 Feb 2015 15:20:43 -0500 (EST) Received: from almini.rcthomas.org (unknown [208.53.120.31]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-sasl1.pobox.com (Postfix) with ESMTPSA id 74E4534108; Mon, 2 Feb 2015 15:20:41 -0500 (EST) Subject: Re: Successfully installed FreeBSD 10.1 on Apple PowerMac G5 -- BUT -- system freezes after a few minutes of running. Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Rick Thomas In-Reply-To: <25A7C3E9-BEDB-4DA3-B9F7-08F2C299C119@dsl-only.net> Date: Mon, 2 Feb 2015 12:20:38 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <7CD2FBA0-45B9-441D-9333-47A0F005CF98@pobox.com> References: <25A7C3E9-BEDB-4DA3-B9F7-08F2C299C119@dsl-only.net> To: Mark Millard X-Mailer: Apple Mail (2.1878.6) X-Pobox-Relay-ID: F5DC33B4-AB18-11E4-9B79-B05EFC961345-02150157!pb-sasl1.pobox.com Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 20:20:45 -0000 Thanks! I hope to be able to get the log files by removing the disk and putting = it in a different machine, or by booting the install disk as a =93live=94 = system and extracting the log files from the disk to a USB stick. I=92ll = report when I have something. As for tracking down the specific versions of things, I installed from = unmodified FreeBSD-10.1-STABLE-powerpc-powerpc64-20150121-r277483-disc1.iso It was a plain vanilla install =97 nothing special. It=92s worth noting that the machine stayed up happily all through the = install process. I did check the MD5sum so I=92m pretty sure I got a good copy. And a big =93Thank You!=94 to Bill Sorenson for confirming that this is = the latest/best=85 I will follow up on your point about removing parts until I get a = working config. I=92ll start by stripping out all RAM above 2GB and any = unneeded PCI cards. Enjoy! Rick On Feb 2, 2015, at 12:05 AM, Mark Millard wrote: > If every boot gives some time before things freeze up you might be = able to extract and report the outputs of commands like: >=20 > $ freebsd-version -ku; uname -a > 10.1-RELEASE-p5 > 10.1-RELEASE-p5 > FreeBSD FBSDG5M1 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5 #0 r277808M: = Fri Jan 30 00:58:33 PST 2015 = root@FBSDG5M1:/usr/obj/usr/home/markmi/src_10_1_releng/sys/GENERIC64vtsc = powerpc >=20 > (There is more than one 'powerpc64 FreeBSD 10.1 "disk1" CD' that can = be burned, such 10.1-RELEASE vs., say, a recent 10.1-STABLE. But it = turns out that until very recently powerpc64 CD burns did not work for = booting PowerMac G5s so more than normal is known about which versions = could have be installed from a CD.) >=20 > Despite the mention of there being no console messages I list some = basics below about dumping messages out anyway... >=20 > $ tail /var/log/messages > Feb 1 21:37:40 FBSDG5M1 kernel: uhid1: on usbus1 > Feb 1 21:37:40 FBSDG5M1 kernel: hid_get_item: Number of items = truncated to 255 > Feb 1 21:37:40 FBSDG5M1 last message repeated 2 times > Feb 1 21:37:41 FBSDG5M1 ntpd[991]: ntpd 4.2.4p5-a (1) > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Activating service = name=3D'org.freedesktop.ConsoleKit' (using servicehelper) > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Activating service = name=3D'org.freedesktop.PolicyKit1' (using servicehelper) > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Successfully activated = service 'org.freedesktop.PolicyKit1' > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Successfully activated = service 'org.freedesktop.ConsoleKit' > Feb 1 21:37:52 FBSDG5M1 ntpd[992]: time reset +1.748777 s > Feb 1 21:38:01 FBSDG5M1 login: ROOT LOGIN (root) ON ttyv0 >=20 > $ dmesg -a | tail > Configuring vt: blanktime. > Performing sanity check on sshd configuration. > Starting sshd. > Starting sendmail_submit. > Starting sendmail_msp_queue. > Starting cron. > Starting background file system checks in 60 seconds. >=20 > Sun Feb 1 21:37:42 PST 2015 > Feb 1 21:38:01 FBSDG5M1 login: ROOT LOGIN (root) ON ttyv0 >=20 > tail by itself may not give enough context. Full copies would be nice = but I do not know about fitting the time before the hangup. >=20 > The intent is to have a more complete specification of which 10.1 = variant and to see if problems are being logged before the complete = hangup. >=20 > Others may well have better suggestions than mine for getting = evidence. >=20 >=20 > You should probably indicate if you are using just the console vs., = say, X11. (Although it is probably just the console if it never stayed = up long enough to establish more context.) Some folks may want to know = the video card involved or other configuration information, even for = simple console usage. >=20 >=20 >=20 > Historically for a base system configuration (video card & monitor, = SSD appropriate to the SATA vintage, appropriate superdrive = vintage/variant that FreeBSD would tolerate) if I've made it to the = login prompt and I had not mixed and matched distinct kernel and world = vintages for some reason then I've had no later troubles with panics, = hangups, or the like for 10.0 or 10.1 vintages that I've installed. >=20 > But that was after I removed all the PCI-Express cards (G5 quad-core) = but the video: My earlier attempts at using the pre-existing SATA cards = and SSD's/disks from them was unreliable even for simple console usage. = I took the direction of simplifying/removing stuff until what was left = just worked, such as the built-in SATA. I've not gone back yet to figure = out if I can make anything that I removed work well. (I'm still = learning/investigating other things for FreeBSD and am in no rush about = what I removed.) >=20 > I temporarily had my hands on a PowerMac G5 that would overheat if = kept busy. But its fan would be going faster than normal after warming = up while idle. The fans would go full speed well before the shutdown = when it would overheat. So that sort of issue is not a match to what you = report. >=20 >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net >=20 > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >=20 From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 2 22:34:31 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3CEB0777 for ; Mon, 2 Feb 2015 22:34:31 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EB5B7E77 for ; Mon, 2 Feb 2015 22:34:30 +0000 (UTC) Received: (qmail 13113 invoked from network); 2 Feb 2015 22:34:28 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 2 Feb 2015 22:34:28 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Mon, 02 Feb 2015 17:34:28 -0500 (EST) Received: (qmail 11709 invoked from network); 2 Feb 2015 22:34:28 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Feb 2015 22:34:28 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 760861C4052; Mon, 2 Feb 2015 14:34:23 -0800 (PST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Successfully installed FreeBSD 10.1 on Apple PowerMac G5 -- BUT -- system freezes after a few minutes of running. From: Mark Millard In-Reply-To: <7CD2FBA0-45B9-441D-9333-47A0F005CF98@pobox.com> Date: Mon, 2 Feb 2015 14:34:25 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <27304CFE-3A9C-4EAF-9987-5A32F9271D80@dsl-only.net> References: <25A7C3E9-BEDB-4DA3-B9F7-08F2C299C119@dsl-only.net> <7CD2FBA0-45B9-441D-9333-47A0F005CF98@pobox.com> To: Rick Thomas X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 22:34:31 -0000 Unfortunately when things fully-hang (e.g, both video and ssh stopped, = not just video failing) frequently log files are not flushed to media. = Before the crash buffered material might be accessible that would not = end up flushed out(?). (Probably very dependent on settings that I do = not know the defaults for.) Some more PowerMac G5 notes follow. They are just based on my experience = with G5 Quad-Core use (mostly) for FreeBSD 10.x-? (mostly). Likely burning any older powrpc64 .iso from the download areas would = have failed to boot. Memory stick booting likely would work for such. = Plain powerpc .iso's would also work but limit themselves to 2G Byte of = RAM even if more is present. Be warned for powerpc64 contexts: At least for PowerMac G5's with lots = of RAM (> 4GBytes?) there are intermittent early-boot-time-frame = problems that make for early hang-ups. I've never used less RAM (other = than just briefly on rare occasions) so I'm not sure if the "lots of = RAM" is actually a requirement for these problems. Others have reported = expecting that it is based on their experiences. Many times I've had to retry booting over a dozen times in a row (I've = been using lots of RAM), at least before... I've been gradually trying to get evidence about the = early-boot-time-frame issues. One discovery allowed detecting evidence = of a problem and retrying. But it is a PowerMac G5 specific hack that is = not appropriate to the normal FreeBSD code base. Especially true because = it deliberately continues from evidence of a corruption. Also the hack = is only based on observed call-return behavior, not on an analysis of = Apple's openfirmware code. For me this is fine but for more serious use? = I do not think so. With the hack in place I rarely have to retry booting = for an intermittent problem and I've not ever had the problem at the = most frequent place it had been happening before. (The actual evidence is the wrong stack pointer (r1) value when = openfirmware returns after it was called and/or an inappropriate status = return value in r3 from that same return. I only observed both being = wrong at the same time, in fact r1=3D=3Dr3 as well. I saw no evidence of = the 64-bit call standard's nonvolatile registers having been corrupted, = even considering full-width values despite the 64 vs. 32 bit environment = distinctions when Apple's openfirmware is involved.) With the relocatable powerpc64 kernel work that is going on in = 11.0-CURRENT one of the originally hacked source files had to be changed = for that context. The adjusted hack uses the 64-bit call standard's = nonvolatile registers for storage more then my original hack did, = depending on the non-volatile status where the original code did not. I = do not really use 11.0-CURRENT for anything but to periodically make = sure that I've got a form of the hack that is appropriate for my use in = that context. (Someday it will be the RELEASE/RELENG/STABLE context.) = Rarely someone has asked me for a PowerMac G5 experiment that involved = some 11.0-CURRENT variant. I should also note that in recent times my personal builds of world and = kernel boot normally only for 10.1-RELEASE based builds (currently = 10.1-RELEASE-p5 based). For 10.1-STABLE and 11.0-CURRENT I have to boot = those builds in two steps, where the first step uses my 10.1-RELEASE-p5 = build initially/part-way, then I unload and boot my kernel10.1S or my = kernel11C explicitly. I've no clue why this is yet. I have made my own = memory stick based on my 10.1-RELEASE-p5 so that I could boot reliably = from it if I mess up boot-ability on the SSD. My recent activities suggest that the 11.0-CURRENT's world is not fully = compatible with 10.1 kernels as stands, trying to use at least one = parameter value that does not exist for 10.1-? contexts: there were = messages reporting such. I've not used the other direction recently. In = my experiments I generally try to avoid such mixes (in either = direction). Nothing says that 11.0-CURRENT and 10.x-? should generally = mix usefully, although some folks may know more about the detailed = mixing-status at any given time. 11.0-CURRENT is normally built with = extensive debugging/validation software enabled. (My build is not that = way but is as close to my 10.1 builds as I can get for such properties.) =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Feb-2, at 12:20 PM, Rick Thomas wrote: Thanks! I hope to be able to get the log files by removing the disk and putting = it in a different machine, or by booting the install disk as a =93live=94 = system and extracting the log files from the disk to a USB stick. I=92ll = report when I have something. As for tracking down the specific versions of things, I installed from = unmodified FreeBSD-10.1-STABLE-powerpc-powerpc64-20150121-r277483-disc1.iso It was a plain vanilla install =97 nothing special. It=92s worth noting that the machine stayed up happily all through the = install process. I did check the MD5sum so I=92m pretty sure I got a good copy. And a big =93Thank You!=94 to Bill Sorenson for confirming that this is = the latest/best=85 I will follow up on your point about removing parts until I get a = working config. I=92ll start by stripping out all RAM above 2GB and any = unneeded PCI cards. Enjoy! Rick On Feb 2, 2015, at 12:05 AM, Mark Millard = wrote: > If every boot gives some time before things freeze up you might be = able to extract and report the outputs of commands like: >=20 > $ freebsd-version -ku; uname -a > 10.1-RELEASE-p5 > 10.1-RELEASE-p5 > FreeBSD FBSDG5M1 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5 #0 r277808M: = Fri Jan 30 00:58:33 PST 2015 = root@FBSDG5M1:/usr/obj/usr/home/markmi/src_10_1_releng/sys/GENERIC64vtsc = powerpc >=20 > (There is more than one 'powerpc64 FreeBSD 10.1 "disk1" CD' that can = be burned, such 10.1-RELEASE vs., say, a recent 10.1-STABLE. But it = turns out that until very recently powerpc64 CD burns did not work for = booting PowerMac G5s so more than normal is known about which versions = could have be installed from a CD.) >=20 > Despite the mention of there being no console messages I list some = basics below about dumping messages out anyway... >=20 > $ tail /var/log/messages > Feb 1 21:37:40 FBSDG5M1 kernel: uhid1: on usbus1 > Feb 1 21:37:40 FBSDG5M1 kernel: hid_get_item: Number of items = truncated to 255 > Feb 1 21:37:40 FBSDG5M1 last message repeated 2 times > Feb 1 21:37:41 FBSDG5M1 ntpd[991]: ntpd 4.2.4p5-a (1) > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Activating service = name=3D'org.freedesktop.ConsoleKit' (using servicehelper) > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Activating service = name=3D'org.freedesktop.PolicyKit1' (using servicehelper) > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Successfully activated = service 'org.freedesktop.PolicyKit1' > Feb 1 21:37:43 FBSDG5M1 dbus[924]: [system] Successfully activated = service 'org.freedesktop.ConsoleKit' > Feb 1 21:37:52 FBSDG5M1 ntpd[992]: time reset +1.748777 s > Feb 1 21:38:01 FBSDG5M1 login: ROOT LOGIN (root) ON ttyv0 >=20 > $ dmesg -a | tail > Configuring vt: blanktime. > Performing sanity check on sshd configuration. > Starting sshd. > Starting sendmail_submit. > Starting sendmail_msp_queue. > Starting cron. > Starting background file system checks in 60 seconds. >=20 > Sun Feb 1 21:37:42 PST 2015 > Feb 1 21:38:01 FBSDG5M1 login: ROOT LOGIN (root) ON ttyv0 >=20 > tail by itself may not give enough context. Full copies would be nice = but I do not know about fitting the time before the hangup. >=20 > The intent is to have a more complete specification of which 10.1 = variant and to see if problems are being logged before the complete = hangup. >=20 > Others may well have better suggestions than mine for getting = evidence. >=20 >=20 > You should probably indicate if you are using just the console vs., = say, X11. (Although it is probably just the console if it never stayed = up long enough to establish more context.) Some folks may want to know = the video card involved or other configuration information, even for = simple console usage. >=20 >=20 >=20 > Historically for a base system configuration (video card & monitor, = SSD appropriate to the SATA vintage, appropriate superdrive = vintage/variant that FreeBSD would tolerate) if I've made it to the = login prompt and I had not mixed and matched distinct kernel and world = vintages for some reason then I've had no later troubles with panics, = hangups, or the like for 10.0 or 10.1 vintages that I've installed. >=20 > But that was after I removed all the PCI-Express cards (G5 quad-core) = but the video: My earlier attempts at using the pre-existing SATA cards = and SSD's/disks from them was unreliable even for simple console usage. = I took the direction of simplifying/removing stuff until what was left = just worked, such as the built-in SATA. I've not gone back yet to figure = out if I can make anything that I removed work well. (I'm still = learning/investigating other things for FreeBSD and am in no rush about = what I removed.) >=20 > I temporarily had my hands on a PowerMac G5 that would overheat if = kept busy. But its fan would be going faster than normal after warming = up while idle. The fans would go full speed well before the shutdown = when it would overheat. So that sort of issue is not a match to what you = report. >=20 >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net >=20 > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >=20 From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 3 07:31:09 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CC590AE2 for ; Tue, 3 Feb 2015 07:31:09 +0000 (UTC) Received: from nk11p03mm-asmtp001.mac.com (nk11p03mm-asmtp001.mac.com [17.158.232.236]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B351DEA3 for ; Tue, 3 Feb 2015 07:31:09 +0000 (UTC) Received: from [10.4.109.18] (unknown [94.124.138.194]) by nk11p03mm-asmtp001.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NJ600D6EQ7EC620@nk11p03mm-asmtp001.mac.com> for freebsd-ppc@freebsd.org; Tue, 03 Feb 2015 07:30:53 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-02-03_03:2015-02-03,2015-02-03,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1502030076 From: Joseph Kakisina Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable Subject: support installing FreeBSD on PowerPC G5 Date: Tue, 03 Feb 2015 08:30:49 +0100 Message-id: <715016CC-74FF-4DF0-9BA0-EB2F72E8A8C6@me.com> To: freebsd-ppc@freebsd.org MIME-version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 07:31:09 -0000 Dear sir, I=E2=80=99ve purchased the FreeBSD 10.0 insulation CD=E2=80=99s and want = to install FreeBSD on my =E2=80=98old=E2=80=99 PowerPC G5. After starting up with cmd-option O-F I typed the command boot cd:,\ppc\chrp\loader cd:0 and hit return the system appends load-size=3D0 adler32=3D1 so I see on the screen boot cd:,\ppc\chrp\loader cd:0 load-size=3D0 adler32=3D1 I got the error message LOAD-SIZE is too small Anybody any suggestions what I should do to fix this error ? Kind regards, Joseph Kakisina= From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 3 10:48:35 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8129A8A for ; Tue, 3 Feb 2015 10:48:35 +0000 (UTC) Received: from sasl.smtp.pobox.com (pb-sasl1.int.icgroup.com [208.72.237.25]) by mx1.freebsd.org (Postfix) with ESMTP id 851AA7DC for ; Tue, 3 Feb 2015 10:48:34 +0000 (UTC) Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id 9E87C30461; Tue, 3 Feb 2015 05:48:27 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=sasl; bh= CdEpapk+4EI51yjfBX8dV3oqGqU=; b=iAGaBNnsYoArh6pbc5KS8hiXsf0/ZMHj 0Tt6A4BoJikI2iSiFhVut4z9TbDc+D0wu45lut0hy3vV2HjpV3tXYboURb+lfHE0 fN8ZAvm8QtdE6j8yYh8SbtffMtMymOLNyRA9+H9MPeSACgfT4DasIjEgOthDxI6h l41uC1SS5WM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= sasl; b=eqb+VXK56sbjV4S1eujU57rZb+9/FQHfkzfY4C/fh//Fm7Nig9l9V3l4 og9sYm4NR1TY71+cu3RJNmh28C7AiIfX1niLuffL2bMncmnifwh6eXRtdBbF+e4v Yc5WsakVdPmXbqVh2LwXslLweuExsn6jaQpqjgin21LypsJF8dM= Received: from pb-sasl1.int.icgroup.com (unknown [127.0.0.1]) by pb-sasl1.pobox.com (Postfix) with ESMTP id 9448730460; Tue, 3 Feb 2015 05:48:27 -0500 (EST) Received: from almini.rcthomas.org (unknown [208.53.120.31]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-sasl1.pobox.com (Postfix) with ESMTPSA id 968253045F; Tue, 3 Feb 2015 05:48:26 -0500 (EST) Subject: Re: support installing FreeBSD on PowerPC G5 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=windows-1252 From: Rick Thomas In-Reply-To: <715016CC-74FF-4DF0-9BA0-EB2F72E8A8C6@me.com> Date: Tue, 3 Feb 2015 02:48:23 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <575B47AD-5600-4E04-B05C-E71E6AE7202C@pobox.com> References: <715016CC-74FF-4DF0-9BA0-EB2F72E8A8C6@me.com> To: Joseph Kakisina X-Mailer: Apple Mail (2.1878.6) X-Pobox-Relay-ID: 2F1DA044-AB92-11E4-8C84-B05EFC961345-02150157!pb-sasl1.pobox.com Cc: freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 10:48:35 -0000 Hi Joseph, Welcome to the mailing list! Try the 10.1 STABLE iso at = http://ftp.freebsd.org/pub/FreeBSD/snapshots/powerpc/powerpc64/ISO-IMAGES/= 10.1/FreeBSD-10.1-STABLE-powerpc-powerpc64-20150121-r277483-disc1.iso There are reported to be some problems with powerpc64 (e.g. Macintosh = G5) disks prior to this one. Rick PS: Please report back to the freebsd-ppc mailing list and tell us = how/whether it worked for you=85 On Feb 2, 2015, at 11:30 PM, Joseph Kakisina wrote: > Dear sir, >=20 > I=92ve purchased the FreeBSD 10.0 insulation CD=92s and want to = install FreeBSD on my =91old=92 PowerPC G5. > After starting up with cmd-option O-F I typed the command >=20 > boot cd:,\ppc\chrp\loader cd:0 >=20 > and hit return > the system appends load-size=3D0 adler32=3D1 so I see on the screen >=20 > boot cd:,\ppc\chrp\loader cd:0 load-size=3D0 adler32=3D1 >=20 > I got the error message LOAD-SIZE is too small >=20 > Anybody any suggestions what I should do to fix this error ? >=20 > Kind regards, > Joseph Kakisina > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 3 17:57:42 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42CE3AA6 for ; Tue, 3 Feb 2015 17:57:42 +0000 (UTC) Received: from anacreon.physics.berkeley.edu (anacreon.Physics.Berkeley.EDU [128.32.117.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anacreon.physics.wisc.edu", Issuer "anacreon.physics.wisc.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 24790D84 for ; Tue, 3 Feb 2015 17:57:42 +0000 (UTC) Received: from anacreon.physics.berkeley.edu (localhost [127.0.0.1]) by anacreon.physics.berkeley.edu (8.14.9/8.14.9) with ESMTP id t13HtiN4093745 for ; Tue, 3 Feb 2015 09:55:44 -0800 (PST) (envelope-from nwhitehorn@freebsd.org) Message-ID: <54D10BA0.9040409@freebsd.org> Date: Tue, 03 Feb 2015 09:55:44 -0800 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD powerpc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Subject: Re: support installing FreeBSD on PowerPC G5 References: <715016CC-74FF-4DF0-9BA0-EB2F72E8A8C6@me.com> In-Reply-To: <715016CC-74FF-4DF0-9BA0-EB2F72E8A8C6@me.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Feb 2015 17:57:42 -0000 On 02/02/15 23:30, Joseph Kakisina wrote: > Dear sir, > > I’ve purchased the FreeBSD 10.0 insulation CD’s and want to install FreeBSD on my ‘old’ PowerPC G5. > After starting up with cmd-option O-F I typed the command > > boot cd:,\ppc\chrp\loader cd:0 > > and hit return > the system appends load-size=0 adler32=1 so I see on the screen > > boot cd:,\ppc\chrp\loader cd:0 load-size=0 adler32=1 > > I got the error message LOAD-SIZE is too small > > Anybody any suggestions what I should do to fix this error ? > > Kind regards, > Joseph Kakisina > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > Have you tried just inserting the disk and pressing "c"? That should work more reliably. You might also want to try a parameter RAM reset if some of your OF variables are screwy. -Nathan From owner-freebsd-ppc@FreeBSD.ORG Wed Feb 4 01:50:05 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 423699F0 for ; Wed, 4 Feb 2015 01:50:05 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E309DF41 for ; Wed, 4 Feb 2015 01:50:04 +0000 (UTC) Received: (qmail 29346 invoked from network); 4 Feb 2015 01:49:57 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 4 Feb 2015 01:49:57 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Tue, 03 Feb 2015 20:49:57 -0500 (EST) Received: (qmail 19494 invoked from network); 4 Feb 2015 01:49:57 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Feb 2015 01:49:57 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 142D91C43A6; Tue, 3 Feb 2015 17:49:51 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: support installing FreeBSD on PowerPC G5 Date: Tue, 3 Feb 2015 17:49:54 -0800 Message-Id: <70806D15-351B-4AFF-8533-4BF29B3E05B8@dsl-only.net> To: j.kakisina@me.com Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2015 01:50:05 -0000 You likely can hold down the C key to automatically try booting from the = CD instead of using Cmd-Option-O-F and "boot cd:,\boot\loader cd:0". = When it allows the boot to start it can avoid other things from = interfering. But specifically for = "FreeBSD-10.0-STABLE-powerpc-powerpc64-20140528-r266807-disc1.iso (md5 = validated) and burned it to a CD" I reported to this list back on = 2014-Jun-01: > For a C-key style boot it hangs shortly after displaying >=20 > loading /boot/defaults/loader.conf >=20 > and stops while displaying "/" from its progress indicator. The fans = then gradually spin up. >=20 > Trying the available PowerMac7,11 gets the same sort of results so = I'll not repeat the information. This is before it puts out the line about loading that lists data=3D and = syms=3D[...]. If anything else is blocking booting from such CDs then it = is a different issue then I'm dealing with in this note. All other forms = of booting from that image burned to CD also get this hang (if you get = that far in the first place). All 10.0-??? and 10.1-??? powerpc64 .iso's since then are that way until = recently. It may be that the problem started with = FreeBSD-10.0-RELEASE-powerpc-powerpc64-*.iso images, I'm not sure (do = not remember). The following is known to not hang that way: FreeBSD-10.1-STABLE-powerpc-powerpc64-20150121-r277483-disc1.iso and the more recent FreeBSD-10.1-STABLE-powerpc-powerpc64-20150201-r278028-disc1.iso likely does not either, but I've not tested that one. You can find such = for a time from: http://ftp1.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/10.1/ This area is updated periodically and older versions are then removed. The images at = http://ftp1.freebsd.org/pub/FreeBSD/ISO-IMAGES/10.1/FreeBSD-10.1-RELEASE-p= owerpc-powerpc64-*.iso have the hang problem. It may be that = http://ftp1.freebsd.org/pub/FreeBSD/ISO-IMAGES/10.0/FreeBSD-10.0-RELEASE-p= owerpc-powerpc64-*.iso images also have the hang problem. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 7 11:49:52 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B04E87BF for ; Sat, 7 Feb 2015 11:49:52 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 53D4DDBA for ; Sat, 7 Feb 2015 11:49:51 +0000 (UTC) Received: (qmail 12628 invoked from network); 7 Feb 2015 11:49:43 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 7 Feb 2015 11:49:43 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Sat, 07 Feb 2015 06:49:43 -0500 (EST) Received: (qmail 18606 invoked from network); 7 Feb 2015 11:49:43 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 7 Feb 2015 11:49:43 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 871F51C43A4; Sat, 7 Feb 2015 03:49:41 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: HEADS UP: powerpc64 kernel format change [booted a PowerMac G5 quad-core][those problems booting some kernel variants: new info] Date: Sat, 7 Feb 2015 03:49:41 -0800 Message-Id: <335C8DCD-33DF-4430-A0FA-77669C513C61@dsl-only.net> To: Nathan Whitehorn Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2015 11:49:52 -0000 Nathan, you had the below written about my problems with booting my = builds of, say, 10.1-STABLE (kernel=3D"kernel10.1S" in = /boot/loaderl.conf) without involving the kernel from my build of = 10.1-RELEASE-p5 (kernel=3D"kernel10.1RE" or sometimes kernel=3D"kernel" = in /boot/loader.conf), where kernel=3D"kernel10.1RE" in = /boot/loader.conf boots just fine... > So this has to be some kind of icache issue. If you unload and reload=20= > the *same* kernel, does it also help? > -Nathan (Part of the evidence was: Using kernel=3D"kernel10.1RE" in = /boot/loader.conf, stopping at the 10sec prompt, unloading, and doing = "boot kernel 10.1S" lets my 10.1-STABLE builds boot that will not boot = directly.) Well I've got a little more information from a different direction: A = way to create the problem when building my 10.1-RELEASE-p5 kernel is to = enable VERBOSE_SYSINIT. More specifically the comparison/contrast I've = done so far is... I added the following 3 lines to my GENERIC64vtsc for my 10.1-RELEASE-p5 = source tree (no other changes elsewhere at all) options VERBOSE_SYSINIT options BOOTVERBOSE=3D1 options BOOTHOWTO=3DRB_VERBOSE and rebuilt kernel the via KERNCONF=3DGENERIC64vtsc INSTKERNNAME=3Dkernel = the resulting kernel load fails if referenced by /boot/loader.conf via = kernel=3D"kernel" line. The %SRR0 address value listed is the same as = for kernel10.1S: 1c277fc. But booting using kernel=3D"kernel10.1RE" in = /boot/loader.conf, stopping at the 10sec wait, unloading, and typing = "boot kernel" boots fine --just like "boot kernel10.1S". Note: GENERIC64vtsc has option DDB enabled (and GBD too). (This is = associated my with my information gathering for early G5 boot = crashes/hangups.) Note: This is the first time I've ever tried any of those 3 options. My = kernel10.1S build was not based on them. Then I changed the 3 lines by just commenting out the first of the 3 = that I had added #options VERBOSE_SYSINIT options BOOTVERBOSE=3D1 options BOOTHOWTO=3DRB_VERBOSE and rebuilt via KERNCONF=3DGENERIC64vtsc INSTKERNNAME=3Dkernel again. = The resulting /boot/kernel/... boots just fine when kernel=3D"kernel" is = used in /boot/loader.conf : no need for using kernel10.1RE or for = stopping to do anything special. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 7 17:43:15 2015 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5FD01B7 for ; Sat, 7 Feb 2015 17:43:15 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 80606209 for ; Sat, 7 Feb 2015 17:43:14 +0000 (UTC) Received: (qmail 27526 invoked from network); 7 Feb 2015 17:43:13 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 7 Feb 2015 17:43:13 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Sat, 07 Feb 2015 12:43:13 -0500 (EST) Received: (qmail 9761 invoked from network); 7 Feb 2015 17:43:13 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 7 Feb 2015 17:43:13 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 94BAFB1E001; Sat, 7 Feb 2015 09:43:09 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: HEADS UP: powerpc64 kernel format change [booted a PowerMac G5 quad-core][those problems booting some kernel variants: new info] From: Mark Millard In-Reply-To: <335C8DCD-33DF-4430-A0FA-77669C513C61@dsl-only.net> Date: Sat, 7 Feb 2015 09:43:11 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <449E0C48-B57D-4873-B2E7-BC217D891897@dsl-only.net> References: <335C8DCD-33DF-4430-A0FA-77669C513C61@dsl-only.net> To: Nathan Whitehorn X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2015 17:43:16 -0000 Correction to earlier Email: VERBOSE_SYSINIT with DDB (and GDB) all = enabled (indirectly booted via using kernel10.1RE) got 0x1c277ec for the = %SRR0 value, not 0x1c277fc. So slightly different than Kernel10.1S's = 0x1c277fc (for this 10.1-STABLE variant). (I looked at the wrong notes = when composing the original Email.) More comparisons of kernel build options: VERBOSE_SYSINIT enabled with DDB (and GDB) disabled still has the = booting problem for my 10.1-RELEASE-p5 variant. It also still has the = 0x1c277ec for the %SRR0 value. For VERBOSE_SYSINIT disabled (DDB and GDB enabled) directly booted... Preloaded elf kernel "/boot/kernel/kernel" at 0x1106000. ... real memory =3D 17152118784 (16357 MB) available KVA =3D 7222611967 (6888 MB) Physical memory chunk(s): 0x0000000000024000 - 0x00000000000fffff, 901120 bytes (220 pages) 0x0000000001115000 - 0x00000000017fffff, 7254016 bytes (1771 pages) 0x0000000001814000 - 0x0000000001bfffff, 4112384 bytes (1004 pages) 0x0000000001c3d000 - 0x0000000001c3cfff, 0 bytes (0 pages) 0x0000000004cbd000 - 0x000000000fffffff, 187969536 bytes (45891 pages) 0x0000000020000000 - 0x000000007f5effff, 1600061440 bytes (390640 pages) 0x0000000100000000 - 0x0000000466827fff, 14604730368 bytes (3565608 = pages) 0x0000000200000000 - 0x00000001ffffffff, 0 bytes (0 pages) 0x0000000300000000 - 0x00000002ffffffff, 0 bytes (0 pages) 0x0000000400000000 - 0x00000003ffffffff, 0 bytes (0 pages) avail memory =3D 16374190080 (15615 MB) So 0x1c277ec is between the two: 0x0000000001814000 - 0x0000000001bfffff, 4112384 bytes (1004 pages) 0x0000000001c3d000 - 0x0000000001c3cfff, 0 bytes (0 pages) (But I do not know what most of the regions and holes are supposed to = be.) VERBOSE_SYSINIT, DDB, and GDB enabled but indirectly booted via = kernel10.1RE (via /boot/loader.conf's kernel=3D"kernel10.1RE"), = stopping, unloading, then doing "boot kernel": Preloaded elf kernel "/boot/kernel/kernel" at 0x1116000. ... real memory =3D 17152118784 (16357 MB) available KVA =3D 7222611967 (6888 MB) Physical memory chunk(s): 0x0000000000024000 - 0x00000000000fffff, 901120 bytes (220 pages) 0x0000000001105000 - 0x0000000001114fff, 65536 bytes (16 pages) 0x0000000001125000 - 0x00000000017fffff, 7188480 bytes (1755 pages) 0x0000000001814000 - 0x0000000001bfffff, 4112384 bytes (1004 pages) 0x0000000001c3d000 - 0x0000000001c3cfff, 0 bytes (0 pages) 0x0000000004cbd000 - 0x000000000fffffff, 187969536 bytes (45891 pages) 0x0000000020000000 - 0x000000007f5effff, 1600061440 bytes (390640 pages) 0x0000000100000000 - 0x0000000466827fff, 14604730368 bytes (3565608 = pages) 0x0000000200000000 - 0x00000001ffffffff, 0 bytes (0 pages) 0x0000000300000000 - 0x00000002ffffffff, 0 bytes (0 pages) 0x0000000400000000 - 0x00000003ffffffff, 0 bytes (0 pages) avail memory =3D 16374190080 (15615 MB) =3D=3D=3D Mark Millard markmi at dsl-only.net On 2015-Feb-7, at 03:49 AM, Mark Millard wrote: Nathan, you had the below written about my problems with booting my = builds of, say, 10.1-STABLE (kernel=3D"kernel10.1S" in = /boot/loaderl.conf) without involving the kernel from my build of = 10.1-RELEASE-p5 (kernel=3D"kernel10.1RE" or sometimes kernel=3D"kernel" = in /boot/loader.conf), where kernel=3D"kernel10.1RE" in = /boot/loader.conf boots just fine... > So this has to be some kind of icache issue. If you unload and reload=20= > the *same* kernel, does it also help? > -Nathan (Part of the evidence was: Using kernel=3D"kernel10.1RE" in = /boot/loader.conf, stopping at the 10sec prompt, unloading, and doing = "boot kernel 10.1S" lets my 10.1-STABLE builds boot that will not boot = directly.) Well I've got a little more information from a different direction: A = way to create the problem when building my 10.1-RELEASE-p5 kernel is to = enable VERBOSE_SYSINIT. More specifically the comparison/contrast I've = done so far is... I added the following 3 lines to my GENERIC64vtsc for my 10.1-RELEASE-p5 = source tree (no other changes elsewhere at all) options VERBOSE_SYSINIT options BOOTVERBOSE=3D1 options BOOTHOWTO=3DRB_VERBOSE and rebuilt kernel the via KERNCONF=3DGENERIC64vtsc INSTKERNNAME=3Dkernel = the resulting kernel load fails if referenced by /boot/loader.conf via = kernel=3D"kernel" line. The %SRR0 address value listed is the same as = for kernel10.1S: 1c277fc. But booting using kernel=3D"kernel10.1RE" in = /boot/loader.conf, stopping at the 10sec wait, unloading, and typing = "boot kernel" boots fine --just like "boot kernel10.1S". Note: GENERIC64vtsc has option DDB enabled (and GBD too). (This is = associated my with my information gathering for early G5 boot = crashes/hangups.) Note: This is the first time I've ever tried any of those 3 options. My = kernel10.1S build was not based on them. Then I changed the 3 lines by just commenting out the first of the 3 = that I had added #options VERBOSE_SYSINIT options BOOTVERBOSE=3D1 options BOOTHOWTO=3DRB_VERBOSE and rebuilt via KERNCONF=3DGENERIC64vtsc INSTKERNNAME=3Dkernel again. = The resulting /boot/kernel/... boots just fine when kernel=3D"kernel" is = used in /boot/loader.conf : no need for using kernel10.1RE or for = stopping to do anything special. =3D=3D=3D Mark Millard markmi at dsl-only.net