Date: Fri, 9 Sep 2022 15:12:38 -0400 From: Justin Hibbits <jhibbits@FreeBSD.org> To: Julio Merino <julio@meroh.net> Cc: "freebsd-ppc@freebsd.org" <freebsd-ppc@freebsd.org> Subject: Re: PowerMac G5 crashes with "instruction storage interrupt" on recent 13 Message-ID: <20220909151238.5da8b63a@ralga-linux> In-Reply-To: <PH0PR20MB37043177835C8DD8B024A173C0439@PH0PR20MB3704.namprd20.prod.outlook.com> References: <PH0PR20MB3704882DD6DC53BB1CF2F5D2C09B9@PH0PR20MB3704.namprd20.prod.outlook.com> <PH0PR20MB37041E9776E86D61EB63FEBFC0439@PH0PR20MB3704.namprd20.prod.outlook.com> <20220909120857.61f65069@ralga-linux> <PH0PR20MB37043177835C8DD8B024A173C0439@PH0PR20MB3704.namprd20.prod.outlook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
That seems bizarre. There haven't been any changes to the controller thread (powermac_thermal.c) in more than 7 years. Are there any problems with sensors? I tested the change I made back in 2015 on my dual core G5, with the intent that it would ramp the fans up sooner (non-linear), and back them down with hysteresis. So when there's load that raises the temperature significantly it will ramp the fans up as quickly as it can, hitting 100% fan long before it can reach maximum temperature. - Justin On Fri, 9 Sep 2022 19:01:06 +0000 Julio Merino <julio@meroh.net> wrote: > Ah, thanks for the workaround. I applied it on top of 9171b8068b92 > and the kernel was able to boot successfully =E2=80=93 and it seems stabl= e so > far. >=20 > However, if I apply the hack on top of stable/13=E2=80=99s HEAD, there is > still the issue of the fans going crazy at the slightest increase in > CPU load but they do drop back down to quiet when the load subsumes. > (For example, a simple =E2=80=9Cgit log=E2=80=9D in /usr/src makes the fa= n spin up > within a couple of seconds and they stop soon after that.) Any ideas > on where this might come from? >=20 >=20 > From: Justin Hibbits<mailto:jhibbits@FreeBSD.org> > Sent: Friday, September 9, 2022 09:09 > To: Julio Merino<mailto:julio@meroh.net> > Cc: freebsd-ppc@freebsd.org<mailto:freebsd-ppc@freebsd.org> > Subject: Re: PowerMac G5 crashes with "instruction storage interrupt" > on recent 13 >=20 > Hi Julio, >=20 > 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. >=20 > The problem appears to be in either lld or the kernel linker. >=20 > - Justin >=20 > On Fri, 9 Sep 2022 16:00:33 +0000 > Julio Merino <julio@meroh.net> wrote: >=20 > > 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): > > > > 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 > > > > 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=E2=80=99s running an old build of FreeBSD 13 > > stable (from around October of last year) that I=E2=80=99m trying to > > upgrade to recent stable/13. > > > > 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. > > > > 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: > > > > ---- > > Setting hostid: =E2=80=A6 > > ZFS filesystem version: 5 > > ZFS storage pool version: features support (500) > > > > Fatal kernel trap: > > > > Exception =3D 0x400 (instruction storage interrupt) > > =E2=80=A6 > > pid =3D 64, comm =3D zpool > > > > 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 > > ---- > > > > Any thoughts about what I could look into? Any =E2=80=9Crecent=E2=80=9D= commits that > > you think may be at fault? > > > > Thanks! > > =20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220909151238.5da8b63a>