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