From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4jF41w5WCdz30Ch for ; Wed, 28 Oct 2026 10:52:20 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "YR1" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4jF41s1K77z2xHd for ; Wed, 28 Oct 2026 10:52:17 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4jF41r3rgbz9S; Wed, 28 Oct 2026 10:52:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1793184736; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ss1PfjS6vbLH2MkbZkZ/AAKgse/jm7xEZvBBSZbgM3U=; b=KLevUSJAk6aoqt/n5Q5xra45tsOWRaOhcNM+WW2F5l51kua+4MGhX92Z/jjmFcwJTzLkNu ouU4IHU6AN+9WUFkWqkfmTQuHHeZiQ159dGtp34c2dotoSJu8QmsPoCot/mstjiB/v80Y9 1nmWNXl8+o752jHO1uRStg4h8vJc+t5cBPLWThZbs8UOXUSZfUe0qa24tov7G3f64gbESy aclqBVBPzIBwsHrjv+HnQZzkD/cREERaBgk+VFdfAMkJ3QJLV8e2AuD8lQ82Wfzw0ltRO+ +Gl55k4gKDrE0bWor5TmWSlZlgGxp/k335FZuPLdOKs4dC9O86CAclsq8e9vvg== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1793184736; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Ss1PfjS6vbLH2MkbZkZ/AAKgse/jm7xEZvBBSZbgM3U=; b=4pSS9C1Vd5g+BbQFrNAsGD82VbuaDD8nH7dh/qIT3oOYgxVc/ZQe68nNCWwDLnyKFojHnZ sq3MhVAYFnpW9hAA== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Potential glibc 2.44 bug for loongarch64 From: Michael Tremer In-Reply-To: Date: Wed, 28 Oct 2026 10:52:15 +0000 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Vincent Li Hello, Just to keep things up to date, there has indeed been a problem here: https://sourceware.org/bugzilla/show_bug.cgi?id=3D34861 It affected dracut which has already been updated by Adolf: = https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D9387983a7af0= a04fd16f9259ebb80dd03c09c701 I independently ran into the same problem and added a patch, but that = commit was never pushed because the new release includes the patch. -Michael > On 24 Oct 2026, at 01:25, Vincent Li wrote: >=20 >=20 >=20 > On Fri, 23 Oct 2026, Michael Tremer wrote: >=20 >> Hello Vincent, >>=20 >> I am not sure we are looking at a glibc issue here - not in the sense = of something being miscompiled. >=20 > It is possible something being miscompiled. >=20 >>=20 >> I have successfully installed the ISO from here in a virtual machine = using UTM: >>=20 >> https://nightly.ipfire.org/next/latest/loongarch64/ >=20 > Good to hear you can install the ISO in a virtual machine, maybe = physical machine could act differently? I tried IPFire nightly build = ISO, the loongson machine could not start from the ISO because the BIOS = is not updated according to Loongson community. I don't know if anyone = else has tried the nightly ISO on a Loongson machine with updated BIOS. >=20 >> It was definitely able to detect the disk and complete the = installation. What branch are you building against? Can you confirm that = the system has successfully detected all disks? >>=20 > the loongfire repo is clone of IPFire core190 when I started to port = to loongarch64 with updated kernel 7.1.1 and many other addon = customization, I manually started to sync loongfire repo from IPFire = till core205 so the IPFire core installer code has never being changed. = There are many variable factors here in the loongfire repo, but I am = sure now that it is only glibc 2.43 to 2.44 update change triggering = this issue, I have started to bisect process from 2.43 to 2.44, = hopefully I can pinpoint the commit in glibc that triggers this behavior = change. >=20 >> -Michael >>=20 >>> On 23 Oct 2026, at 03:23, Vincent Li = wrote: >>>=20 >>> Hi Michael, >>>=20 >>> I mirrored your core205 toochain upgrade including glibc 2.43 to = 2.44 update to the loongfire repo which is fork of ipfire on = loongarch64. I noticed I could not install the ISO on loongarch machine = after glibc update, if I only revert glibc 2.44 back to 2.43 in the = toolchain, no installation issue. I assume IPFire loongarch port would = have same issue since the loongfire fork has exact same installer code = as IPFire. I filed a bugzilla report to sourceware for glibc. >>> https://sourceware.org/bugzilla/show_bug.cgi?id=3D34861 >>>=20 >>> Best, >>>=20 >>> Vincent >>=20 >>=20 >=20