Processed: Re: Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat
Processing control commands: > reassign -1 src:lxcfs 5.0.3-1 Bug #1036818 [src:linux] linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat Bug reassigned from package 'src:linux' to 'src:lxcfs'. No longer marked as found in versions linux/6.1.1-1~exp1. Ignoring request to alter fixed versions of bug #1036818 to the same values previously set Bug #1036818 [src:lxcfs] linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat Marked as found in versions lxcfs/5.0.3-1. > forwarded -1 https://github.com/lxc/lxcfs/issues/553 Bug #1036818 [src:lxcfs] linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat Set Bug forwarded-to-address to 'https://github.com/lxc/lxcfs/issues/553'. > affects -1 src:mariadb Bug #1036818 [src:lxcfs] linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat Added indication that 1036818 affects src:mariadb -- 1036818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat
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
Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat
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 Regards, Salvatore
Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat
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? Regards, Salvatore
Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat
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 Helge
Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat
Package: linux
Version: 6.1.0
Hi!
I noticed that the autopkgtests on Debian on armhf and armel that run
the mariadb-test-run have been failing since the Linux kernel was
updated from 5.10.0 to 6.1.0. The failure is due to a Perl module not
being able to get from /proc/cpu the number of processors:
Last passing one:
2023-04-28
https://ci.debian.net/data/autopkgtest/unstable/armel/m/mariadb/33218554/log.gz
kernel: Linux 5.10.0-21-arm64 #1 SMP Debian 5.10.162-1 (2023-01-21)
perl 5.36.0-7
libdbi-perl armel 1.643-4
libconfig-inifiles-perl all 3.03-2
First failing one:
2023-05-05
https://ci.debian.net/data/autopkgtest/unstable/armel/m/mariadb/33379866/log.gz
kernel: Linux 6.1.0-7-arm64 #1 SMP Debian 6.1.20-2 (2023-04-08)
perl 5.36.0-7
libdbi-perl armhf 1.643-4
libconfig-inifiles-perl all 3.03-2
Error:
starting mysql-test-tun.pl...
Logging: ./mysql-test-run.pl --force --testcase-timeout=120
--suite-timeout=540 --retry=3 --
...
Collecting tests...
Installing system database...
Can't use an undefined value as an ARRAY reference at
lib/My/SysInfo.pm line 166.
This line 166 in src:mariadb/mysql-test/lib/My/SysInfo.pm has:
# Return the number of cpus found
sub num_cpus {
my ($self)= @_;
return int(@{$self->{cpus}}) or
confess "INTERNAL ERROR: No cpus in list";
}
The cpus is initialized to be an empty list on the line 119:
118 my $self= bless {
119cpus => (),
120 }, $class;
Then it tries to fill it from /proc/cpuinfo (line 67) and `kstat`
(line 95). If nothing worked it'll create one dummy cpu:
145 push(@{$self->{cpus}},
146 {
147 bogomips => DEFAULT_BOGO_MIPS,
148 model_name => "unknown",
149 });
See more discussion from MariaDB devs:
https://lists.launchpad.net/maria-developers/msg13356.html
Thus the primary suspect here is the kernel upgrade. Perl versions
have not changed. This only happens on armel/armhf, other archs are
fine.
Reproducing the environment on ci.debian.net / ci-worker-arm??-?? to
study how /proc/cpu etc looks like, so filing this against the Linux
package is somewhat of a guess, but at least we get a Bug# to
reference for further research.
