Date: Mon, 25 Nov 2024 23:15:20 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: Mark Millard <marklmi@yahoo.com> Cc: Guido Falsi <mad@madpilot.net>, =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org>, ports@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: port binary dumping core on recent head in poudriere Message-ID: <38658C0D-CA33-4010-BBE1-E68D253A3DF7@FreeBSD.org> In-Reply-To: <F64DB4E9-A210-4E1F-B333-C597F3DBED54@yahoo.com> References: <aa597431-54a8-4cde-8d4f-b75040b59bae@madpilot.net> <46E3A370-A3E0-4BAF-B707-87F94F98E248@FreeBSD.org> <5ee47c3d-f80e-4d50-9b6a-acb3c98e80e0@madpilot.net> <f9e32784-226a-4e1e-a24b-62f5e6d3d765@madpilot.net> <E4616829-D2DE-4EAF-B971-1EDA8B447F13@FreeBSD.org> <7c9c3cf5-bbd1-4642-8d04-33aa07a4db02@madpilot.net> <9df256a8-c6ed-46d9-b955-fc2657c12d36@madpilot.net> <5c502054-7353-4a1e-8350-c403482e9c0d@madpilot.net> <a203a89f-2eb7-4220-8dfb-648cd46fc6bb@madpilot.net> <3127C3BA-FC93-4636-ADDB-89518DE9C60D@FreeBSD.org> <86ed2zsp6l.fsf@ltc.des.dev> <5f24a570-26e0-4c0a-817f-591a234fd07b@madpilot.net> <5918C6A1-8FDB-40CA-8C86-EB7B7BE75A2E@yahoo.com> <86ed2zc8r5.fsf@ltc.des.dev> <45098ccf-4dc6-426c-849a-c923805d6723@madpilot.net> <F64DB4E9-A210-4E1F-B333-C597F3DBED54@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 Nov 2024, at 23:12, Mark Millard <marklmi@yahoo.com> wrote: >=20 > On Nov 25, 2024, at 13:27, Guido Falsi <mad@madpilot.net> wrote: >=20 >> On 25/11/24 22:18, Dag-Erling Sm=C3=B8rgrav wrote: >>> Mark Millard <marklmi@yahoo.com> writes: >>>> Guido Falsi <mad@madpilot.net> writes: >>>>> On 25/11/24 09:17, Dag-Erling Sm=C3=B8rgrav wrote: >>>>>> Dimitry Andric <dim@FreeBSD.org> writes: >>>>>>> Probably best to create a bugzilla ticket, but as I said before, = I >>>>>>> cannot reproduce this. >>>>>> I can. My builder is running 15 and sees segfaults while = building >>>>>> packages for 14 and 15 but not for 13. >>>>> BTW removing optimizations (CPUTYPE) for only the affected ports = made >>>>> guile2 work again. Did not solve the issue with sassc though. = [...] >>>>> I'm also using ccache, but that does not look relevant. >>>> I've never used ccache or analogous and get the libsass.so.1.0.0 >>>> .got.plt corruption that I've reported on the lists anyway. >>> I don't use ccache or optimizations. Here's an example of sassc >>> segfaulting in a 14.1-RELEASE-p6 jail: >>> = https://pkg.des.dev/logs/data/14amd64-default/2024-11-24_19h29m04s/logs/er= rors/plasma5-breeze-gtk-5.27.11.log >>> which matches the following entry from `/var/log/messages`: >>> Nov 24 21:23:06 pkg kernel: pid 71277 (sassc), jid 253, uid 65534: = exited on signal 11 (core dumped) >>> The poudriere host is a bhyve VM with 48 cores and 192 GB RAM on a >>> 32c/64t AMD EPYC 7502P with 256 GB RAM. >>=20 >> I sincerely hope this is not relevant but my CPU is also AMD: AMD = Ryzen 5 5600G >=20 > The amd64 system type that I have access to and used > for my testing: >=20 > AMD 7950X3D (16 core, 32 thread, so 32 FreeBSD-cpus) with 192 GiBytes = of RAM I'm on Intel, and I don't see any crashes at all. So, are we looking at = some CPU specific issue here? -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38658C0D-CA33-4010-BBE1-E68D253A3DF7>