Date: Sat, 6 May 2017 00:06:06 -0700 From: Mark Millard <markmi@dsl-only.net> To: FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: llvm FreeBSD powerpc ABI target bug fix: Re: [Bug 26519] Clang 4.0.0's "Target: powerpc-unknown-freebsd11.0" code generation is violating the SVR4 ABI (SEGV can result) Message-ID: <B6DCAA6B-8721-46F5-B331-E839B830E941@dsl-only.net> In-Reply-To: <C9CB8645-472E-40D9-B193-E977F842C37B@dsl-only.net> References: <bug-26519-7604@http.bugs.llvm.org/> <bug-26519-7604-UhFFHDCAay@http.bugs.llvm.org/> <0103401A-CEEA-4992-A45E-E60EA151119B@dsl-only.net> <893ECA11-7C80-4D24-A496-92ADC7978A07@FreeBSD.org> <8F708AD1-055E-41BD-BD92-6A87C5FBAA60@dsl-only.net> <78CD5050-2B2B-4213-AF11-7EF744F608B2@dsl-only.net> <E177E5EE-25EB-4CBA-9C0F-7209AFF30749@dsl-only.net> <C9CB8645-472E-40D9-B193-E977F842C37B@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-May-5, at 10:13 PM, Mark Millard <markmi@dsl-only.net> wrote: > On 2017-May-5, at 6:11 PM, Mark Millard <markmi@dsl-only.net> wrote: >=20 >>>> . . . >>>>=20 >>>> For the gcc 4.2.1 based kernel boot I have >>>> had one odd fatal kernel trap (0x903a64a, >>>> "unknown") where the lr showed 0x907f . It >>>> reported being stopped at: >>>>=20 >>>> ffs_truncate+0x1080 >>>>=20 >>>> It appears that "call doadump" worked but >>>> I've not looked at what was put in >>>> /var/crash/ . >>>=20 >>> If I leave the PowerMac idle running: It also happens when busy. >>> # uname -paKU >>> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc = powerpc 1200030 1200030 >>>=20 >>> it eventually gets the same ffs_truncate-tied fatal >>> kernel trap, with the same odd lr and the like. >>>=20 >>> So, while I cannot directly cause the problem >>> at a specific time, the problem is repeatable. >>>=20 >>> . . . >>=20 >> The ffs_truncate issue is odd: >>=20 >> A) It was gcc 4.2.1 based for both kernel and world. >> B) I built a gcc 4.2.1 based debug kernel and >> installed it but that does not get the problem. >>=20 >> I sam trying the gcc 4.2.1 debug kernel with the >> system clang 4 world now and will later switch >> to the gcc 4.2.1 non-debug kernel to see what >> happens. >>=20 >> But being a pure gcc 4.2.1 environment originally >> suggests that the ffs_truncate issue is not >> clang-toolchain related. >=20 > I found a bad (old) kernel module in /boot/kernel/ > and eliminating it appears to have removed the > ffs_truncate problem. >=20 > . . . For the ffs_truncate problem I spoke too soon: It happened again, this time while the old PowerMac was busy. The detail numbers and such were again the same. =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B6DCAA6B-8721-46F5-B331-E839B830E941>