From: Vincent Li <vincent.mc.li@gmail.com>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: Vincent Li <vincent.mc.li@gmail.com>, development@lists.ipfire.org
Subject: Re: Potential glibc 2.44 bug for loongarch64
Date: Sat, 24 Oct 2026 00:25:15 +0000 (UTC) [thread overview]
Message-ID: <b4fbdc28-c059-6bc-542-79f7cec4fcbe@gmail.com> (raw)
In-Reply-To: <E636FEED-BC0F-4682-91B0-E7FDBE0ECC90@ipfire.org>
On Fri, 23 Oct 2026, Michael Tremer wrote:
> Hello Vincent,
>
> I am not sure we are looking at a glibc issue here - not in the sense of something being miscompiled.
It is possible something being miscompiled.
>
> I have successfully installed the ISO from here in a virtual machine using UTM:
>
> https://nightly.ipfire.org/next/latest/loongarch64/
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.
> 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?
>
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.
> -Michael
>
>> On 23 Oct 2026, at 03:23, Vincent Li <vincent.mc.li@gmail.com> wrote:
>>
>> Hi Michael,
>>
>> 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=34861
>>
>> Best,
>>
>> Vincent
>
>
prev parent reply other threads:[~2026-10-24 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 2:23 Vincent Li
2026-10-23 9:32 ` Michael Tremer
2026-10-24 0:25 ` Vincent Li [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4fbdc28-c059-6bc-542-79f7cec4fcbe@gmail.com \
--to=vincent.mc.li@gmail.com \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox