Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 9 Sep 2022 16:00:33 +0000
From:      Julio Merino <julio@meroh.net>
To:        "freebsd-ppc@freebsd.org" <freebsd-ppc@freebsd.org>, "jhibbits@freebsd.org" <jhibbits@freebsd.org>
Subject:   RE: PowerMac G5 crashes with "instruction storage interrupt" on recent 13
Message-ID:  <PH0PR20MB37041E9776E86D61EB63FEBFC0439@PH0PR20MB3704.namprd20.prod.outlook.com>
In-Reply-To: <PH0PR20MB3704882DD6DC53BB1CF2F5D2C09B9@PH0PR20MB3704.namprd20.prod.outlook.com>
References:  <PH0PR20MB3704882DD6DC53BB1CF2F5D2C09B9@PH0PR20MB3704.namprd20.prod.outlook.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--_000_PH0PR20MB37041E9776E86D61EB63FEBFC0439PH0PR20MB3704namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Armed with a lot of patience, I was able to bisect where the crashes are co=
ming from. They seem to be due to these three consecutive and related commi=
ts (because the first one broke the build and required two extra fixes for =
powerpc=92s GENERIC64 to build):

9171b8068b92 cpuset: Fix the KASAN and KMSAN builds
01f281d0ee52 Fix the build after 47a57144
971cb62e0b23 cpuset: Byte swap cpuset for compat32 on big endian architectu=
res

Any idea on how to look into these crashes further?

Thank you!


From: Julio Merino<mailto:julio@meroh.net>
Sent: Sunday, July 31, 2022 07:45
To: freebsd-ppc@freebsd.org<mailto:freebsd-ppc@freebsd.org>
Subject: PowerMac G5 crashes with "instruction storage interrupt" on recent=
 13

Hi all,

I have a PowerMac G5 that=92s running an old build of FreeBSD 13 stable (fr=
om around October of last year) that I=92m trying to upgrade to recent stab=
le/13.

Booting into a new kernel brings two issues: the first is that the fans spi=
n up to jet engine levels right before transferring control to userspace. A=
n old patch I have locally to mitigate this (which I got from whichever out=
standing bug exists for this in the bug tracker) doesn=92t seem to work any=
 longer.

The second is that the kernel crashes (apparently) as soon as it tries to m=
ount a ZFS pool during early stages of the boot process, but after successf=
ully transferring control to userspace. Typing this from a photo of the cra=
sh so omitting details that I think aren=92t going to be relevant here, lik=
e addresses, here is what I get:

----
Setting hostid: =85
ZFS filesystem version: 5
ZFS storage pool version: features support (500)

Fatal kernel trap:

Exception =3D 0x400 (instruction storage interrupt)
=85
pid =3D 64, comm =3D zpool

panic: instruction storage interrupt trap
cpuid =3D 1
time =3D =85
KDB: stack backtrace:
#0 kdb_backtrace
#1 vpanic
#2 panic
#3 trap
#4 powerpc_interrupt
Uptime: 7s
----

Any thoughts about what I could look into? Any =93recent=94 commits that yo=
u think may be at fault?

Thanks!


--_000_PH0PR20MB37041E9776E86D61EB63FEBFC0439PH0PR20MB3704namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">;
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"#954F72" style=3D"word-wrap:bre=
ak-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Armed with a lot of patience, I was able to bisect w=
here the crashes are coming from. They seem to be due to these three consec=
utive and related commits (because the first one broke the build and requir=
ed two extra fixes for powerpc=92s GENERIC64
 to build):</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">9171b8068b92 cpuset: Fix the KASAN and KMSAN builds<=
/p>
<p class=3D"MsoNormal">01f281d0ee52 Fix the build after 47a57144</p>
<p class=3D"MsoNormal">971cb62e0b23 cpuset: Byte swap cpuset for compat32 o=
n big endian architectures</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Any idea on how to look into these crashes further?<=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thank you!</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"mso-element:para-border-div;border:none;border-top:solid #E1E=
1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class=3D"MsoNormal" style=3D"border:none;padding:0in"><b>From: </b><a hr=
ef=3D"mailto:julio@meroh.net">Julio Merino</a><br>
<b>Sent: </b>Sunday, July 31, 2022 07:45<br>
<b>To: </b><a href=3D"mailto:freebsd-ppc@freebsd.org">freebsd-ppc@freebsd.o=
rg</a><br>
<b>Subject: </b>PowerMac G5 crashes with &quot;instruction storage interrup=
t&quot; on recent 13</p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have a PowerMac G5 that=92s running an old build o=
f FreeBSD 13 stable (from around October of last year) that I=92m trying to=
 upgrade to recent stable/13.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Booting into a new kernel brings two issues: the fir=
st 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=92t seem to work any longer.<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The second is that the kernel crashes (apparently) a=
s soon as it tries to mount a ZFS pool during early stages of the boot proc=
ess, but after successfully transferring control to userspace. Typing this =
from a photo of the crash so omitting
 details that I think aren=92t going to be relevant here, like addresses, h=
ere is what I get:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">----<o:p></o:p></p>
<p class=3D"MsoNormal">Setting hostid: =85<o:p></o:p></p>
<p class=3D"MsoNormal">ZFS filesystem version: 5<o:p></o:p></p>
<p class=3D"MsoNormal">ZFS storage pool version: features support (500)<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Fatal kernel trap:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Exception =3D 0x400 (instruction storage interrupt)<=
o:p></o:p></p>
<p class=3D"MsoNormal">=85<o:p></o:p></p>
<p class=3D"MsoNormal">pid =3D 64, comm =3D zpool<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">panic: instruction storage interrupt trap<o:p></o:p>=
</p>
<p class=3D"MsoNormal">cpuid =3D 1<o:p></o:p></p>
<p class=3D"MsoNormal">time =3D =85<o:p></o:p></p>
<p class=3D"MsoNormal">KDB: stack backtrace:<o:p></o:p></p>
<p class=3D"MsoNormal">#0 kdb_backtrace<o:p></o:p></p>
<p class=3D"MsoNormal">#1 vpanic<o:p></o:p></p>
<p class=3D"MsoNormal">#2 panic<o:p></o:p></p>
<p class=3D"MsoNormal">#3 trap<o:p></o:p></p>
<p class=3D"MsoNormal">#4 powerpc_interrupt<o:p></o:p></p>
<p class=3D"MsoNormal">Uptime: 7s<o:p></o:p></p>
<p class=3D"MsoNormal">----<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Any thoughts about what I could look into? Any =93re=
cent=94 commits that you think may be at fault?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks!<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_PH0PR20MB37041E9776E86D61EB63FEBFC0439PH0PR20MB3704namp_--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PH0PR20MB37041E9776E86D61EB63FEBFC0439>