Re: Potential glibc 2.43 regression on big-endian targets

On Sun, 2026-08-23 at 07:12 +0100, Sam James wrote:
> John Paul Adrian Glaubitz <[email protected]> writes:
> 
> > Hi,
> > 
> > On Sun, 2026-08-23 at 06:51 +0200, John Paul Adrian Glaubitz wrote:
> > > On Sat, 2026-08-22 at 16:23 -0300, Adhemerval Zanella Netto wrote:
> > > > I run tests on powerpc64/powerpc32 from time to time on cfarm121 and I haven't
> > > > see any other than the usual regressions [1][2]. Did it started with 2.43?
> > > 
> > > Yes, I'm quite confident that it started with 2.43.
> > 
> > I just noticed the following message on the kernel buffer, it might be related:
> > 
> > [ 1814.130181] cgroup: fork rejected by pids controller in /system.slice/cron.service
> 
> I am not seeing this yet. This sounds a bit like some system-wide limits
> gone haywire?
> 
> https://serverfault.com/questions/1032747/cgroup-fork-rejected-by-pids-controller
> mentions something like it too.

There seem to be two issues. One is processes running out of memory and the other
is the fork issue. I was able to resolve the former by editing the corresponding
service file, not sure about the memory issue though [1]:

dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory
dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory
dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory
dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory
dpkg-deb (subprocess): compressing tar member: lzma error: Cannot allocate memory

Adrian

> [1] https://buildd.debian.org/status/fetch.php?pkg=imagemagick&arch=sparc64&ver=8%3A7.1.2.29%2Bdfsg2-1%2Bb1&stamp=1787459818&raw=0

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913