Date: Fri, 24 Jan 2020 09:06:08 -0600 From: Jason Bacon <bacon4000@gmail.com> To: freebsd-ppc@freebsd.org Subject: Re: panic: data storage interrupt trap when building world on PowerMac G5 Message-ID: <bbd8aef2-d6d8-72b3-7958-92d406a77831@gmail.com> In-Reply-To: <DBE80843-E788-4365-861A-9265A86AAC71@freebsd.org> References: <7722F637-2C3D-4199-B2C9-F0616B0A5AE1@freebsd.org> <20200123134114.75d9c771@titan.knownspace> <CAGSRtz49L_AOqm-y0FtZR6Ejesb7Xs85-sy-YXn=2b59SE7UoA@mail.gmail.com> <4652291B-6D2B-4D21-9F01-576913DF0B54@macmic.franken.de> <CAGSRtz7Pj8ox5wBDBhYyzGPgmdHP_50Kvjbf4AZd5eJ=v6RgEw@mail.gmail.com> <DBE80843-E788-4365-861A-9265A86AAC71@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sort of a shot in the dark, but did you verify that your filesystems are = clean? UFS2 has an issue where the filesystem doesn't always get cleaned=20 completely on boot.=C2=A0 Repair using the journal can miss incorrect=20 reference counts if I remember correctly.=C2=A0 This can cause panics aft= er a=20 sudden outage like a power failure that leave the FS in a dirty state. Try booting to single-user mode and running "fsck -fy" on each FS.=C2=A0 = If=20 any of them report errors, this may have been your problem. =C2=A0=C2=A0=C2=A0 JB On 2020-01-24 06:36, Michael Tuexen wrote: >> On 24. Jan 2020, at 13:27, Francis Little <oggy@farscape.co.uk> wrote:= >> >> I'm not getting panics, I get similar errors to this: > I see. Thanks for providing the information. > I haven't seen such problems (neither userland nor kernelland) on Power= 9. > > Best regards > Michael >> cc: error: unable to execute command: Abort trap (core dumped) >> cc: error: clang frontend command failed due to signal (use -v to see = invocation) >> FreeBSD clang version 9.0.1 (git@github.com:llvm/llvm-project.git c1a0= a213378a458fbea1a5c77b315c7dce08fd05) (based on LLVM 9.0.1) >> Target: powerpc64-unknown-freebsd13.0 >> Thread model: posix >> InstalledDir: /usr/bin >> cc: note: diagnostic msg: PLEASE submit a bug report to https://bugs.f= reebsd.org/submit/ and include the crash backtrace, preprocessed source, = and associated run script. >> cc: note: diagnostic msg: >> ******************** >> >> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: >> Preprocessed source(s) and associated run script(s) are located at: >> cc: note: diagnostic msg: /tmp/addsf3-67691f.c >> cc: note: diagnostic msg: /tmp/addsf3-67691f.sh >> cc: note: diagnostic msg: >> >> ******************** >> *** [addsf3.o] Error code 254 >> >> make[4]: stopped in /usr/src/lib/libcompiler_rt >> 1 error >> >> make[4]: stopped in /usr/src/lib/libcompiler_rt >> *** [lib/libcompiler_rt__PL] Error code 2 >> >> make[3]: stopped in /usr/src >> 1 error >> >> make[3]: stopped in /usr/src >> *** [libraries] Error code 2 >> >> make[2]: stopped in /usr/src >> 1 error >> >> make[2]: stopped in /usr/src >> *** [_libraries] Error code 2 >> >> make[1]: stopped in /usr/src >> 1 error >> >> make[1]: stopped in /usr/src >> *** [buildworld] Error code 2 >> >> make: stopped in /usr/src >> >> make: stopped in /usr/src >> >> On Thu, 23 Jan 2020 at 21:21, Michael Tuexen <Michael.Tuexen@macmic.fr= anken.de> wrote: >>> On 23. Jan 2020, at 22:09, Francis Little <oggy@farscape.co.uk> wrote= : >>> >>> Hi, >>> >>> Same here, with smp enabled, fans go full speed every 60 sec, probing= >>> sysctl calms them for a min. >>> >>> buf*daemons time out shutting down and buildworlds fail. >> Could you specify how buildworlds fail? Is the system panic'ing like m= ine? >> On a Power9 system, buildworld works without a problem. But the system= has >> much more memory. >> >> Best regards >> Michael >>> Regards >>> >>> >>> >>> On Thu, 23 Jan 2020 at 19:41, Justin Hibbits <chmeeedalf@gmail.com> w= rote: >>> >>>> On Thu, 23 Jan 2020 12:32:03 +0100 >>>> Michael Tuexen <tuexen@freebsd.org> wrote: >>>> >>>>> Dear all, >>>>> >>>>> when trying to build world on a G5 with SMP disabled >>>>> (kern.smp.disabled=3D1 in /boot/loader.conf), I get the following p= anic: >>>>> >>>>> http://bsd14.fh-muenster.de/crash.jpeg >>>>> >>>>> It looks like this happens when memory is getting low (top was >>>>> running until the machine panics). The machine runs the kernel from= >>>>> r356950. >>>>> >>>>> Any idea what is going wrong? >>>>> >>>>> Best regards >>>>> Michael >>>> That fault address looks very suspicious. Reading it as hex encodin= g >>>> of ASCII we get " user ad". >>>> >>>> Is there a reason you still have kern.smp.disabled=3D1? I fixed the= bug >>>> for that (at least in head) back around May, or at least *a* bug for= it. >>>> >>>> - Justin >>>> _______________________________________________ >>>> freebsd-ppc@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.or= g" >>>> >>> _______________________________________________ >>> freebsd-ppc@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org= " > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" --=20 Earth is a beta site.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bbd8aef2-d6d8-72b3-7958-92d406a77831>