Re: panic: data storage interrupt trap when building world on PowerMac G5

Michael Tuexen <[email protected]>
Newsgroups gmane.os.freebsd.devel.ppc
Message-ID <[email protected]>
> On 24. Jan 2020, at 13:27, Francis Little <[email protected]> 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 Power9.

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 ([email protected]:llvm/llvm-project.git c1a0a213378a458fbea1a5c77b315c7dce08fd05) (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.freebsd.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 <[email protected]> wrote:
> > On 23. Jan 2020, at 22:09, Francis Little <[email protected]> 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 mine?
> 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 <[email protected]> wrote:
> > 
> >> On Thu, 23 Jan 2020 12:32:03 +0100
> >> Michael Tuexen <[email protected]> wrote:
> >> 
> >>> Dear all,
> >>> 
> >>> when trying to build world on a G5 with SMP disabled
> >>> (kern.smp.disabled=1 in /boot/loader.conf), I get the following panic:
> >>> 
> >>> 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 encoding
> >> of ASCII we get " user ad".
> >> 
> >> Is there a reason you still have kern.smp.disabled=1?  I fixed the bug
> >> for that (at least in head) back around May, or at least *a* bug for it.
> >> 
> >> - Justin
> >> _______________________________________________
> >> [email protected] mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> >> To unsubscribe, send any mail to "[email protected]"
> >> 
> > _______________________________________________
> > [email protected] mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
> > To unsubscribe, send any mail to "[email protected]"
> 

_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.