Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat

[Salvatore Bonaccorso <carnil@debian.org>]

Control: reassign -1 src:lxcfs 5.0.3-1
Control: forwarded -1 https://github.com/lxc/lxcfs/issues/553
Control: affects -1 src:mariadb

Hi,

On Sat, May 27, 2023 at 11:51:26AM +0200, Salvatore Bonaccorso wrote:
> Hi,
> 
> On Sat, May 27, 2023 at 11:50:06AM +0200, Salvatore Bonaccorso wrote:
> > Hi Helge, hi Otto,
> > 
> > On Sat, May 27, 2023 at 09:26:06AM +0200, Helge Deller wrote:
> > > Just wondering / guessing:
> > > 
> > > Are the ARM machines on ci.debian.net (ci-worker-arm??-??)
> > > physical machines, or are they running on qemu-user VMs?
> > > 
> > > If they run qemu, this bug report
> > >  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024653
> > > might be similiar.
> > > 
> > > If so, then qemu probably needs fixing of the output of /proc/cpuinfo
> > > for ARM, e.g. like this:
> > > https://gitlab.com/qemu-project/qemu/-/commit/e0174afeea23e56765db56fbbe465ed1fcbdd07a
> > 
> > The suspect is that /proc/cpuinfo is empty or not readable, and this
> > seems to be a problem with lxcfs after mentioning the issue today to
> > Paul and Jochen.
> > 
> > Jochen, understanding you correctly there is already an upstream fix
> > which is supposed to addres the issue?
> 
> The upstream issue should be: https://github.com/lxc/lxcfs/issues/553

Now reassigning to the lxcfs package. lxcfs maintainers, can you
please adjust the severity as needed. It affects at least mariadb's
autopkgtests.

Otto, spaking of the issue, I guess Paul will agree, that you can
ignore it for now for the mariadb upload to unstable.

Regards,
Salvatore