From nobody Fri Sep 09 16:08:57 2022 X-Original-To: freebsd-ppc@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MPLXG4MjSz4bknt for ; Fri, 9 Sep 2022 16:09:02 +0000 (UTC) (envelope-from jhibbits@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MPLXG3tlnz3wjB; Fri, 9 Sep 2022 16:09:02 +0000 (UTC) (envelope-from jhibbits@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1662739742; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Yum33aipTIqLv0OxtsVYCS5W6D/AjKeBpNVWoSDsHKU=; b=te9OY28lRVrivWhjLdf+HYScWJVb41zbtq4Km0o1SeMraS4lBSF0j3F+ldT7LYxfxdowcv 1jmHjYWDEjiNOcAubFwuGfe9BYxOXJcpIeHBt0E0mRQFjrAooEj+Kg2JDs6kr3nzXgaUHX SXqwJ2CYD1APhhDY2+EZCK49YWNUDBo6IUcXlzTOG7tT0IPBt4ss+02u2nkPJyFTdE1/tb elISvqjarFUZ50RjosE3GgHLE8w00F1Ime64rWbVCYHhvM4jco0YuERbSX8cB3qmXkrEbx HKryQWSNov8p8J3bEO0E3fBSDjXvwp1bbgA9PyPKaD8yTvtyApucQBXDfjoo7w== Received: from ralga-linux (dsl-74-83-251-217.fuse.net [74.83.251.217]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: jhibbits) by smtp.freebsd.org (Postfix) with ESMTPSA id 4MPLXG21m9z1F5d; Fri, 9 Sep 2022 16:09:02 +0000 (UTC) (envelope-from jhibbits@FreeBSD.org) Date: Fri, 9 Sep 2022 12:08:57 -0400 From: Justin Hibbits To: Julio Merino Cc: "freebsd-ppc@freebsd.org" Subject: Re: PowerMac G5 crashes with "instruction storage interrupt" on recent 13 Message-ID: <20220909120857.61f65069@ralga-linux> In-Reply-To: References: X-Mailer: Claws Mail 4.1.0 (GTK 3.24.34; powerpc64le-unknown-linux-gnu) List-Id: Porting FreeBSD to the PowerPC List-Archive: https://lists.freebsd.org/archives/freebsd-ppc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1662739742; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Yum33aipTIqLv0OxtsVYCS5W6D/AjKeBpNVWoSDsHKU=; b=JURH5JTpxqoYIZ6oYrzmtV0hEmbpI6mdJqhDyE278Wthmx4nRgQbwXllyLCurA+e+aZvXb /HSIdDIRGNvma6TNqvx2uaKVjJf2vXLXTRjel9AAsAFZHXzfSPShLvDDR5d9AdU7xCqFp5 HntXZCEwROVrCRdxG06rcOqkkvCQy1ZcWhwj/W9RhY6XwjMVZ9JhIW29IUGy+sup7/I5hz R1ukg7T831/2nqIQI8jySQaWPEoBOgcvHBqiUFkmL6QGsTrgn12yoIbQdGR8MtaM/+ZOwp Asvjl1pmJZPmeqnFPe+XxDn3PUMGz7V1DYsAX53dumWmhNDFoC3Nwa6ZkGlTPw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1662739742; a=rsa-sha256; cv=none; b=oMDwGE0FwTCdivWt2QEGVGTebWkrhs9uYvYLLFfA5xnUjAak6/sBUcqT42HJhjVGMl82wa SW5BDDju+V85JyR8AG3G+SkjDMlsO/uZ+eVXlRzdQESnWsaNX7qJoHqj/bhFPdv2X3xmVb cvX9XwtDVZuv3oU3RKLpZiydOFONYvcbPReQKuvPR0zyOi0irqyvYcYHfQmu+gNvcmuehI edsqR97czZ0jjOBDokc/A7VNZeXA3XI4dX9L7fU9bbXbYjlud7H+F/EpK+xcnx43hnOgO4 VUSVKgEPV5VLbvYGurcWjM6kT/+Tgl5rrhqmigbcqWr6pVW1GPlBGKZoQB2RTw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N Hi Julio, 971cb62e0b23 is the likely culprit. Alfredo has a patch at https://reviews.freebsd.org/D36234 that you can use until the problem is solved. The alternative is you could build everything into the kernel instead of using modules. The problem appears to be in either lld or the kernel linker. - Justin On Fri, 9 Sep 2022 16:00:33 +0000 Julio Merino wrote: > Armed with a lot of patience, I was able to bisect where the crashes > are coming from. They seem to be due to these three consecutive and > related commits (because the first one broke the build and required > two extra fixes for powerpc=E2=80=99s GENERIC64 to build): >=20 > 9171b8068b92 cpuset: Fix the KASAN and KMSAN builds > 01f281d0ee52 Fix the build after 47a57144 > 971cb62e0b23 cpuset: Byte swap cpuset for compat32 on big endian > architectures >=20 > Any idea on how to look into these crashes further? >=20 > Thank you! >=20 >=20 > From: Julio Merino > Sent: Sunday, July 31, 2022 07:45 > To: freebsd-ppc@freebsd.org > Subject: PowerMac G5 crashes with "instruction storage interrupt" on > recent 13 >=20 > Hi all, >=20 > I have a PowerMac G5 that=E2=80=99s running an old build of FreeBSD 13 st= able > (from around October of last year) that I=E2=80=99m trying to upgrade to > recent stable/13. >=20 > Booting into a new kernel brings two issues: the first is that the > fans spin up to jet engine levels right before transferring control > to userspace. An old patch I have locally to mitigate this (which I > got from whichever outstanding bug exists for this in the bug > tracker) doesn=E2=80=99t seem to work any longer. >=20 > The second is that the kernel crashes (apparently) as soon as it > tries to mount a ZFS pool during early stages of the boot process, > but after successfully transferring control to userspace. Typing this > from a photo of the crash so omitting details that I think aren=E2=80=99t > going to be relevant here, like addresses, here is what I get: >=20 > ---- > Setting hostid: =E2=80=A6 > ZFS filesystem version: 5 > ZFS storage pool version: features support (500) >=20 > Fatal kernel trap: >=20 > Exception =3D 0x400 (instruction storage interrupt) > =E2=80=A6 > pid =3D 64, comm =3D zpool >=20 > panic: instruction storage interrupt trap > cpuid =3D 1 > time =3D =E2=80=A6 > KDB: stack backtrace: > #0 kdb_backtrace > #1 vpanic > #2 panic > #3 trap > #4 powerpc_interrupt > Uptime: 7s > ---- >=20 > Any thoughts about what I could look into? Any =E2=80=9Crecent=E2=80=9D c= ommits that > you think may be at fault? >=20 > Thanks! >=20