Date: Thu, 23 Jan 2020 13:42:39 -0800 From: Mark Millard <marklmi@yahoo.com> To: Michael Tuexen <tuexen@freebsd.org> Cc: Justin Hibbits <chmeeedalf@gmail.com>, "powerpc@freebsd.org" <powerpc@FreeBSD.org> Subject: Re: panic: data storage interrupt trap when building world on PowerMac G5 Message-ID: <A3B9B0D5-4303-4B23-AD30-9254CB32AB21@yahoo.com> In-Reply-To: <F8284D1F-B8BD-43F4-A1CD-916E423076F7@freebsd.org> References: <7722F637-2C3D-4199-B2C9-F0616B0A5AE1@freebsd.org> <20200123134114.75d9c771@titan.knownspace> <F8284D1F-B8BD-43F4-A1CD-916E423076F7@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Jan-23, at 12:29, Michael Tuexen <tuexen at freebsd.org> wrote: > On 23. Jan 2020, at 20:41, Justin Hibbits <chmeeedalf@gmail.com> = wrote: >=20 >> . . . >>=20 >> Is there a reason you still have kern.smp.disabled=3D1? I fixed the = bug > Without that, the fans get very loud, on reboot you get timeouts, and > I think (haven't tried recently) the network interfaces die. With = that, > no such problems. My experiments with controlling the mftb value relationships from cross-core (/cross-socket) contexts avoided the fan behavior and the shutdown/reboot timeouts in my testing. But I've no evidence associated with network interfaces being tied to that. In fact, I've never had ethernet interface problems, other than usefdt=3D1 swapping which was 0 vs. which was 1. (The fdt conversion reverses each sibling list but the code using the nodes is based on fixed traversals, independent of lack vs. presence of a usefdt definition or the value it is defined to.) I've basically only used ethernet, so I can not comment on other networking interfaces. (I also run with patched code so that the fdt conversion preserves the order of sibling lists, leaving the fixed traversals alone. I also have some OF_xref_from_node and OF_node_from_xref (lack of) usage corrections involved. I'll avoid listing more here. But I do not get distinct traversal results from usefdt mode.) > This is the first time I try to do a buildworld after moving to clang > (which was done by a reinstall). Before the switch, the machine did = multiple > buildworlds and was running very stable. (I've switched to ELFv2 for powerpc64, but, prior to that, my context was based on experimental system-clang ELFv1, either built by system-clang or, at the time, devel/powerpc64-gcc .) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A3B9B0D5-4303-4B23-AD30-9254CB32AB21>