From nobody Tue Jul 23 13:56:49 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WSzGb05QQz5S0Y0; Tue, 23 Jul 2024 13:56:55 +0000 (UTC) (envelope-from meloun.michal@gmail.com) Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WSzGZ5C0jz4NtZ; Tue, 23 Jul 2024 13:56:54 +0000 (UTC) (envelope-from meloun.michal@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-wm1-x32f.google.com with SMTP id 5b1f17b1804b1-4266dc7591fso40104235e9.0; Tue, 23 Jul 2024 06:56:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721743011; x=1722347811; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:reply-to:user-agent:mime-version:date :message-id:sender:from:to:cc:subject:date:message-id:reply-to; bh=K+bkz3os13tF1KhOCkX9VL//Zhni8qgaW7tYz0nVjEg=; b=OftVqNtriYLrF5Pej9Bb/+gdtUAvVpO3qzSFmg4yjAbTCIpQ6zdkRqzNAfNwgaFVhL DZkNvcQ5aI50SWW6MG9Pz5YTkOu5vM7KSpxDj+5Jp4HeyB0oZvC2eduzlgr3Cavt0fnW e5RgjIJtC601TKKvwYDvdXW/OsbmqGjUDCpxwmfkNtPyQ4gxkoR0FoQnAdo8PDc9tIms jtfzAD8R4IG6K/Ejm7mqr0ZeJkwIpg0X1l+EyYuYgHe5MZB0295Setr5d+CO3SI6Tf2J hdUvQAlxR1WTkvuSiBmpT/NE7gMbFfzQDUPKcn4r6kcC40DGli8lXvIMoGJCdTGxIOLy tcnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721743011; x=1722347811; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:reply-to:user-agent:mime-version:date :message-id:sender:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=K+bkz3os13tF1KhOCkX9VL//Zhni8qgaW7tYz0nVjEg=; b=SxvhDTsGMf0mtLtq24RLVwqZ6kbHbylqx47hG/4XxYXR4kn4sRgv7/LZhdn26tBaWK iT52b/+JRyx2HTXi07/sMBD2p1Md87XCH4KgvhmBUk1NdxW9ZA9iL3TobqQKCJQC/PQi 3+t0jghWyA3rGORYGm/ox1dMaygII/Ock88VHXyNYA2UwG2ZbZ7s+MCyf2nCQvXwzTR0 ASDZldUrp3sYv6hcGKkNP473rTYonaS1ZciAx9W4ZRiXQMHuJf3E+yISE9pODfUH9mhZ 2LUIBnUPX4GZIT6bZLhNUZ/QKOPGAP95CxAnWLbD6gnA6suyq4KTX1Pz0puAJEvT+gI7 T5Fw== X-Forwarded-Encrypted: i=1; AJvYcCVF7blH/BgVEZpKkFpFsJpOKKL/wb5sf1jKcUSO91KBeTxlD2cM1MHCOrSe6+UwSeewxb+6G8zzVbhuzKGW1ufmThqNVH7AuFrgoqYwkQjLmyxhIaR8Xu7pVxQpBgQlAkHppS4g/DbKYoEhsy6TWLwY34p640Hy X-Gm-Message-State: AOJu0Yx3jK6YCuDtNKf+GGrNIE1vdzI+fEWjiulyFqLbrfr58qLEwq0i FqQhVakMZe6YjIYgDccfdkrasYTTSGxqxrQFuzFhPajMB9oB7N4W8GTFo5iW X-Google-Smtp-Source: AGHT+IFCqbkG3eLYs88M/sUpKzllR1IAs7qdUIA+vG0TJNXuNDfAlpqioraduzh64AHhKqKR41883g== X-Received: by 2002:a05:600c:3c88:b0:426:6e93:4ad0 with SMTP id 5b1f17b1804b1-427deff7426mr55976005e9.17.1721743010356; Tue, 23 Jul 2024 06:56:50 -0700 (PDT) Received: from ?IPV6:2001:67c:14a0:5fe0:55eb:52e:1154:1d18? ([2001:67c:14a0:5fe0:55eb:52e:1154:1d18]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-427d2a3c0fasm206380195e9.7.2024.07.23.06.56.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 Jul 2024 06:56:49 -0700 (PDT) Message-ID: <31690db8-e563-491f-ae91-f235aec8c24c@gmail.com> Date: Tue, 23 Jul 2024 15:56:49 +0200 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: meloun.michal@gmail.com Subject: Re: armv7-on-aarch64 stuck at urdlck To: Konstantin Belousov Cc: Mark Millard , mmel@freebsd.org, FreeBSD Current , "freebsd-arm@freebsd.org" References: <724db42b-5550-4381-8277-2971e6b3e8f1@freebsd.org> <86185657-e521-466b-89e2-f291aaac10a6@freebsd.org> <0EF18174-8735-46A4-BD71-FFA3472B319F@yahoo.com> <33251aa3-681f-4d17-afe9-953490afeaf0@gmail.com> <0DD19771-3AAB-469E-981B-1203F1C28233@yahoo.com> Content-Language: cs, en-US From: Michal Meloun In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4WSzGZ5C0jz4NtZ On 23.07.2024 11:36, Konstantin Belousov wrote: > On Tue, Jul 23, 2024 at 09:53:41AM +0200, Michal Meloun wrote: >> The good news is that I'm finally able to generate a working/locking >> test case. The culprit (at least for me) is if "-mcpu" is used when >> compiling libthr (e.g. indirectly injected via CPUTYPE in /etc/make.conf). >> If it is not used, libthr is broken (regardless of -O level or debug/normal >> build), but -mcpu=cortex-a15 will always produce a working libthr. > > I think this is very significant progress. > > Do you plan to drill down more to see what is going on? Sure. Fortunately, I have some free time now. I've just almost finished a two-years project (unrelated to FBSD or computers) that took up all my time. Another symptom is that: Breakpoint 2.2, _umtx_op_err (obj=0x20135cc0, op=UMTX_OP_RW_RDLOCK, val=0, uaddr=0x0, uaddr2=0x0) at /usr/src/lib/libsys/_umtx_op_err.c:36 where obj=0x20135cc0 ---> {rw_state = URWLOCK_WRITE_OWNER , rw_flags = 2, rw_blocked_readers = 0, rw_blocked_writers = 0, rw_spare = {0, 0, 0, 0}} always return EINTR.