Bug#1036818: [pkg-lxc-devel] Bug#1036818: Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat

2023-06-06 Thread Paul Gevers

Hi,

On 01-06-2023 13:28, Mathias Gibbens wrote:

   Some other things we can look at -- are there any errors/warnings in
the lxcfs service journal and/or the system's dmesg that is running
lxcfs? It might also be useful to start lxcfs with debugging (`-d`) if
there's nothing being logged about populating /proc/cpuinfo.


This maybe?

Jun 06 17:35:55 ci-worker-armhf-01 lxcfs[686]: ../src/proc_cpuview.c:
1055: proc_cpuinfo_read: Write to cache was truncated

On 06-06-2023 04:06, Mathias Gibbens wrote:
One other thing to double check on ci-worker-armhf-01 would be the 
contents of /var/lib/lxcfs/proc/cpuinfo, so we can see what lxcfs is

 doing from the host side.


debian@ci-worker-armhf-01:~$ cat /var/lib/lxcfs/proc/cpuinfo
processor   : 0
BogoMIPS: 50.00
Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics
fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x3
CPU part: 0xd0c
CPU revision: 1

processor   : 1
BogoMIPS: 50.00
Features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics
fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x3
CPU part: 0xd0c
CPU revision: 1

[ etc ]

Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1036818: [pkg-lxc-devel] Bug#1036818: Bug#1036818: linux on armel/armhf: Perl library unable to access get CPU info from /proc/cpu or kstat

2023-06-05 Thread Mathias Gibbens
On Thu, 2023-06-01 at 18:58 +0200, Pierre-Elliott Bécue wrote:
> >   I should have time this weekend when I can spin up a qemu vm to
> > test in, if we're not able to get a root cause identified before
> > then.

  I did try to reproduce the issue over the weekend with qemu. Using
qemu-user-static and systemd-nspawn was insufficient due to lxcfs
needing proper access to the fuse kernel api. After trying and failing
to bootstrap an armhf instance by hand, I grabbed a raspberry pi 2
bookworm image from raspi.d.n, and got it running under qemu-system-
arm. Within that environment, lxcfs appeared to work correctly
(/var/lib/lxcfs/proc/cpuinfo was correct, no obvious errors or warnings
noticed). I didn't spin up a full lxc container instance within that
environment.

> I can probably grant you privileges on abel as soon as I get an ack
> from my fellow DSA mates.

  If it's possible to get temporary permissions on abel, that would be
useful.

  One other thing to double check on ci-worker-armhf-01 would be the
contents of /var/lib/lxcfs/proc/cpuinfo, so we can see what lxcfs is
doing from the host side.

Mathias


signature.asc
Description: This is a digitally signed message part