This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-23.23~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem still exists, change the tag
'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See for documentation how
to enable and use -proposed. Thank you!

** Tags added: kernel-spammed-jammy-linux-hwe-6.2 verification-needed-jammy

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  udev fails to make prctl() syscall with apparmor=0 (as used by maas by

Status in AppArmor:
Status in MAAS:
  Fix Committed
Status in maas-images:
Status in apparmor package in Ubuntu:
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
Status in apparmor source package in Lunar:
Status in linux source package in Lunar:
  Fix Committed
Status in systemd source package in Lunar:

Bug description:
  I'm assuming the image being used for these deploys is 20230417 or
  20230417.1 based on the fact that I saw a 6.2 kernel being used which
  I don't believe was part of the 20230319 serial. I don't have access
  to the maas server, so I can't directly check any log files.

  MAAS Version: 3.3.2

  Here's where the serial log indicates it can't download the squashfs. The 
full log is attached as scobee-lunar-no-squashfs.log (there are some other 
console message intermixed):
  no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf 
  date/squa[  206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, 
  :: mount_squash downloading
  4/lunar/candidate/squashfs to /root.tmp.img
  Connecting to (
  wget: can't connect to remote host ( Network is unreachable
  :: mount -t squashfs -o loop  '/root.tmp.img' '/root.tmp'
  mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory

  Still gathering logs and info and will update as I go.

  Kernel Bug / Apparmor

  $ wget
  $ wget
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

  #start the VM
  Starting systemd-udevd version 252.5-2ubuntu3
  Spawning shell within the initramfs

  BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
  Enter 'help' for a list of built-in commands.

  (initramfs) udevadm info --export-db
  Failed to set death signal: Invalid argument

  Observe that udevadm fails to setup death signal, with in systemd code
  is this

                  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
                          log_full_errno(prio, errno, "Failed to set death 
signal: %m");

  workaround set kernel commandline to `apparmor=1`

  MAAS bug
  Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor. 
Even for deployment and commisioning.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to