Potential glibc 2.44 bug for loongarch64

Potential glibc 2.44 bug for loongarch64

[Vincent Li]

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

Re: Potential glibc 2.44 bug for loongarch64

[Michael Tremer]

Hello Vincent,

I am not sure we are looking at a glibc issue here - not in the sense of something being miscompiled.

I have successfully installed the ISO from here in a virtual machine using UTM:

  https://nightly.ipfire.org/next/latest/loongarch64/

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?

-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

Re: Potential glibc 2.44 bug for loongarch64

[Vincent Li]

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
>
>