[Kernel-packages] [Bug 2060560] [NEW] Remove obsolete kernels from noble

[Julian Andres Klode]

Public bug reported:

The starfive and laptop kernels are obsolete, on mantic release version
still, and should be removed per discussion with kernel team on
Mattermost.

$ reverse-depends src:linux-starfive  # some reverse-depends bug
$ reverse-depends src:linux-laptop
No reverse dependencies found
$ reverse-depends src:linux-meta-starfive
No reverse dependencies found

** Affects: linux-laptop (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-meta-starfive (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: linux-starfive (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Also affects: linux-starfive (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-meta-starfive (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- The starfive and laptop kernels are obsolete and should be removed per
- discussion with kernel team on Mattermost.
+ The starfive and laptop kernels are obsolete, on mantic release version
+ still, and should be removed per discussion with kernel team on
+ Mattermost.
  
  $ reverse-depends src:linux-starfive  # some reverse-depends bug
  $ reverse-depends src:linux-laptop
  No reverse dependencies found
  $ reverse-depends src:linux-meta-starfive
  No reverse dependencies found

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-starfive in Ubuntu.
https://bugs.launchpad.net/bugs/2060560

Title:
  Remove obsolete kernels from noble

Status in linux-laptop package in Ubuntu:
  Fix Released
Status in linux-meta-starfive package in Ubuntu:
  Fix Released
Status in linux-starfive package in Ubuntu:
  Fix Released

Bug description:
  The starfive and laptop kernels are obsolete, on mantic release
  version still, and should be removed per discussion with kernel team
  on Mattermost.

  $ reverse-depends src:linux-starfive  # some reverse-depends bug
  $ reverse-depends src:linux-laptop
  No reverse dependencies found
  $ reverse-depends src:linux-meta-starfive
  No reverse dependencies found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-laptop/+bug/2060560/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

[Julian Andres Klode]

Uploaded procps with the file; leaving gamemode task open because maybe
dynamic enhancements there still make some sense in 24.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057792

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in procps package in Ubuntu:
  Fix Committed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

[Julian Andres Klode]

I'm agreeing with desktop in following Fedora to bump to 1048576, the
precedence makes this safe, and this I consider this a bug fix for
crashing software and not a feature request.

** Changed in: procps (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: procps (Ubuntu)
   Status: Triaged => In Progress

** Changed in: procps (Ubuntu)
   Status: In Progress => Fix Committed

** No longer affects: ubuntu

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057792

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in gamemode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in procps package in Ubuntu:
  Fix Committed

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/2057792/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low

[Julian Andres Klode]

Subscribing Canonical desktop team to get their input.

Basically the ask is to ship this file:

https://src.fedoraproject.org/rpms/systemd/blob/f39/f/10-map-count.conf

I believe if we do it should be shipped in procps; or possibly, gamemode
should set that option?

** Also affects: procps (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gamemode (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057792

Title:
  Some Games are crashing linked to a vm_max_map_count too low

Status in Ubuntu:
  Confirmed
Status in gamemode package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in procps package in Ubuntu:
  New

Bug description:
  Hello there,

  I submit this request to improve the gaming experience in ubuntu for all 
users. 
  Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just 
not starting because the vm_max_map_count is locked at 65530. If we change this 
value to a value > 20, all games are working well and there is no bug 
linked to maps. 

  Some others distribution like Fedora or Pop OS, have already made the
  change few month before.

  It's time to Ubuntu to makes the change also.

  Thanks in advance for applying this request.

  How to make this change :

  One file to modify : 
  /etc/sysctl.conf
  Add this line :
  vm.max_map_count=2147483642
  Save
  Reboot and enjoy

  Best Regards
  Vinceff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2057792/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2051999] Re: Grub2 2.06 has upstream bug that results in Non-booting with ZFS after snapshot of bpool.

[Julian Andres Klode]

Oh but please don't use `[trusted=yes]`, just add the repository with
add-apt-repository ppa:ubuntu-uefi-team/backports-build.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051999

Title:
  Grub2 2.06 has upstream bug that results in Non-booting with ZFS after
  snapshot of bpool.

Status in grub2 package in Ubuntu:
  Confirmed
Status in grub2-unsigned package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  There is an upstream Bug with Grub where if you create snapshots of bpool, it 
results in a non-booting System. The problem was found to be an upstream Bug 
with Grub2:
  https://savannah.gnu.org/bugs/index.php?64297

  Multiple Ubuntu 22.04.3 Users Affected:
  https://ubuntuforums.org/showthread.php?t=2494397=zfs+grub+bug
  https://ubuntuforums.org/showthread.php?t=2494957

  Brought up as an issue at OpenZFS:
  https://github.com/openzfs/zfs/issues/13873

  If you look at this comment 
(https://github.com/openzfs/zfs/issues/13873#issuecomment-1892911836), if was 
found the Savanaugh at GNU released a fix for it in Grub2 2.12, here:
  https://git.savannah.gnu.org/cgit/grub.git/log/grub-core/fs/zfs/zfs.c

  Ubuntu Jammy 22.04.3 is Grub2 2.06. We need to backported this patch
  to Grub2 2.06 so that Users are not caught of in this bug for or
  currently supported LTS Release.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-amd64 2.06-2ubuntu14.4
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu Feb  1 16:40:28 2024
  InstallationDate: Installed on 2021-09-23 (861 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: grub2-unsigned
  UpgradeStatus: Upgraded to jammy on 2022-08-17 (533 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2051999/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support

[Julian Andres Klode]

There doesn't seem to be anything to sponsor here, so I'm unsubscribing
ubuntu-sponsors. Please make sure to keep your ubuntu-sponsors
subscriptions current so we don't waste time in complex multi package
bugs trying to figure out if there's anything to do for us.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090

Title:
  Orchid Bay MLK2/Maya Bay MLK soundwire support

Status in HWE Next:
  New
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-6.5 package in Ubuntu:
  Invalid
Status in firmware-sof source package in Jammy:
  Fix Committed
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.5 source package in Jammy:
  Fix Committed
Status in firmware-sof source package in Mantic:
  Fix Committed
Status in linux source package in Mantic:
  Fix Committed
Status in linux-oem-6.5 source package in Mantic:
  Invalid
Status in firmware-sof source package in Noble:
  Fix Released
Status in linux source package in Noble:
  In Progress
Status in linux-oem-6.5 source package in Noble:
  Invalid

Bug description:
  [SRU Justifications]

  == kernels ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, 
following upstream commits are mandatory:
  * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 
rt1316 config")
  * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 
support")
  * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct 
cards->components by name_prefix")
  * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic 
config"): linux-next

  [Test Case]

  1. enable -proposed pocket and install the latest kernel
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == firmware-sof ==

  [Impact]

  Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.

  [Fix]

  Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
  sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
  topology files").

  [Test Case]

  1. enable -proposed pocket and install firmware-sof-signed
  2. browse youtube, hold backspace on virtual terminal or whatever makes some 
noises
  3. expected sound system brought up and reacts accordingly

  [Where problems could occur]

  While this enables new devices on new platforms, we may bump into
  burst noises, power consumption problems at corner cases not covered
  by test program.

  [Other Info]

  This is to enable sof devices on Intel MTL platform, which is only
  supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
  Jammy.

  == original bug report ==

  The kernel patches has been applied in the ASoC tree.
  Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel 
(spinics.net) [spinics.net]
  https://www.spinics.net/lists/alsa-devel/msg167273.html
  We need 3/23, 4/23, 6/23, and 
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176

  And the UCM PR is submitted
  ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · 
alsa-project/alsa-ucm-conf (github.com) [github.com]
  https://github.com/alsa-project/alsa-ucm-conf/pull/363
  See bug 2042902.

  For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
  SOF2.7.2 topology files").

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

[Julian Andres Klode]

Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now
which is based on 6.6.3 which probably has all the fancy patches too

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045899

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

[Julian Andres Klode]

These ones I don't remember seeing before:

[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045899

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

[Julian Andres Klode]

I saw similar messages in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that
only caused hangs and not block the entire desktop (and Firefox is good
now so I don't know)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045899

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2045899] Re: More amdgpu crashes: pagefaults, ring timeouts and parser bugs

[Julian Andres Klode]

** Attachment added: "OlderDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt

** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045899

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2045899] [NEW] More amdgpu crashes: pagefaults, ring timeouts and parser bugs

[Julian Andres Klode]

Public bug reported:

I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level but
the GUI doesn't actually recover and I also can switch tty with the
keyboard.

I have attached the two crashes from yesterday, they look slightly
different but may be the same cause:


LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Dec  7 13:09:42 2023
InstallationDate: Installed on 2022-11-26 (376 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-14-generic N/A
 linux-backports-modules-6.5.0-14-generic  N/A
 linux-firmware20230919.git3672ccab-0ubuntu2.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2023
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET71W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.28
dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET71W(1.47):bd09/14/2023:br1.47:efr1.28:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble wayland-session

** Attachment added: "LastDmesg.txt"
   
https://bugs.launchpad.net/bugs/2045899/+attachment/5727244/+files/LastDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045899

Title:
  More amdgpu crashes: pagefaults, ring timeouts and parser bugs

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New

Bug description:
  I think running the Mattermost snap forced to Wayland rendering
  *eventually* seems to crash amdgpu, it recovers at the kernel level
  but the GUI doesn't actually recover and I also can switch tty with
  the keyboard.

  I have attached the two crashes from yesterday, they look slightly
  different but may be the same cause:

  
  LastDmesg.txt contains the journalctl -k -b of the last failed boot, 
OlderDmesg.txt contains the same for the crash before that.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Dec  7 13:09:42 2023
  InstallationDate: Installed on 2022-11-26 (376 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-14-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash zswap.enabled=1 
zswap.compressor=zstd zswap.max_pool_percent=20 zswap.zpool=zsmalloc 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-14-generic N/A
   linux-backports-modules-6.5.0-14-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2023
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET71W (1.47 )
  dmi.board.asset.tag: Not 

[Kernel-packages] [Bug 2042902] Re: ucm2: soundwire: add rt713 SDCA device

[Julian Andres Klode]

Unsubscribing ubuntu-sponsors, please resubscribe when you have new
debdiff(s).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2042902

Title:
  ucm2: soundwire: add rt713 SDCA device

Status in OEM Priority Project:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [ Impact ]
  Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack 
Codec-ALC713.
  Without correct configurations in userspace above codecs cannot be used. Thus 
in Settings > Sound > Output test doesn't produce sounds and Input device is 
greyed out.

  [ Fix ]
  Adding rt713 config files in ucm2 will allow to utilize those codecs.
  Upstream commit added support: 
https://github.com/alsa-project/alsa-ucm-conf/pull/363

  [ Test Plan ]
  Device with the soundwire card

  $ cat /proc/asound/cards
   0 [sofsoundwire   ]: sof-soundwire - sof-soundwire
    Intel Soundwire SOF

  Before fix:

  1. $ alsactl init
  alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration 
file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf
  alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file 
/usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2
  alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use 
case configuration -2
  Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" 
"HDA:8086281d,80860101,0010 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 
mic:rt713-dmic" "" ""
  Hardware is initialized using a generic method

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=off

  After fix: after adding patch files

  1. $ alsactl init
  alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf 
/var/lib/alsa/card0.conf.d' failed (exit code 1)

  (note: assuming that failed to remove the empty directory is not a
  critical problem)

  2. $ amixer contents
  ...
  numid=24,iface=MIXER,name='Headphone Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on
  ...
  numid=33,iface=MIXER,name='IEC958 Playback Switch'
    ; type=BOOLEAN,access=rw--,values=1
    : values=on

  [Where problems could occur]

   * This change adds new hardware support.

   * The change only adds new hardware support,
     it will not affect other codec device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Julian Andres Klode]

update-initramfs -c call by kernel postinst hook is not covered, but we
need to make sure the initramfs is there at kernel configuration point
because we need it to be there when updating boot loaders.

e.g. if we triggered both in that case, update-grub could run before
update-initramfs.

if we included an initramfs-tools hook to run update-grub, update-grub
could be run twice but update-initramfs only once.

I propose we keep this bug for grub2 change to match upstream, but it
may be worth revisiting how we can merge update-initramfs -c and update-
initramfs -u calls when updating kernels and other packages touching
initramfs in one session.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250109

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Julian Andres Klode]

Draft fix for update-grub: https://salsa.debian.org/grub-
team/grub/-/merge_requests/46

Still need to take care of grub-install at some point, haven't figured
out the best approach there yet.

** Changed in: grub2 (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: grub2 (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250109

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  In Progress
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1250109] Re: Please use dpkg-triggers for update-grub when installing or removing kernel packages

[Julian Andres Klode]

@Andy I'm unassigning you and changing the bug status as the initramfs
part has been resolved, update-initramfs does

if [ -n "$DPKG_MAINTSCRIPT_PACKAGE" ] && [ $# = 1 ] && [ "$1" = -u ]; then
if dpkg-trigger --no-await update-initramfs; then   
 
echo "update-initramfs: deferring update (trigger activated)"   
 
exit 0  
fi  
 
fi  
 

We can patch grub  to do the same

** Changed in: initramfs-tools (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: initramfs-tools (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

** Changed in: grub2 (Ubuntu)
 Assignee: Andy Whitcroft (apw) => (unassigned)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250109

Title:
  Please use dpkg-triggers for update-grub when installing or removing
  kernel packages

Status in grub2 package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in grub2 package in Debian:
  Won't Fix

Bug description:
  Currently the kernel package runs update-grub every time one is
  installed or removed.  This results in it being run a dozen times
  during a dist-upgrade, and this is rather time consuming and annoying.
  Please use a dpkg trigger to cause update-grub to be run only once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1250109/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Julian Andres Klode]

** Tags removed: rls-jj-incoming
** Tags added: foundations-todo

** Changed in: systemd (Ubuntu Jammy)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037667

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2036968] Re: Mantic minimized/minimal cloud images do not receive IP address during provisioning; systemd regression with wait-online

[Julian Andres Klode]

** Tags removed: rls-mm-incoming

** Changed in: systemd (Ubuntu)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036968

Title:
  Mantic minimized/minimal cloud images do not receive IP address during
  provisioning; systemd regression with wait-online

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Following a recent change from linux-kvm kernel to linux-generic
  kernel in the mantic minimized images, there is a reproducable bug
  where a guest VM does not have an IP address assigned as part of
  cloud-init provisioning.

  This is easiest to reproduce when emulating arm64 on amd64 host. The
  bug is a race condition, so there could exist fast enough
  virtualisation on fast enough hardware where this bug is not present
  but in all my testing I have been able to reproduce.

  The latest mantic minimized images from http://cloud-
  images.ubuntu.com/minimal/daily/mantic/ have force initrdless boot and
  no initrd to fallback to.

  This but is not present in the non minimized/base images @
  http://cloud-images.ubuntu.com/mantic/ as these boot with initrd with
  the required drivers present for virtio-net.

  Reproducer

  ```
  wget -O "launch-qcow2-image-qemu-arm64.sh" 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/launch-qcow2-image-qemu-arm64.sh

  chmod +x ./launch-qcow2-image-qemu-arm64.sh
  wget 
https://people.canonical.com/~philroche/20230921-cloud-images-mantic-fail-to-provision/livecd.ubuntu-cpc.img
  ./launch-qcow2-image-qemu-arm64.sh --password passw0rd --image 
./livecd.ubuntu-cpc.img
  ```

  You will then be able to log in with user `ubuntu` and password
  `passw0rd`.

  You can run `ip a` and see that there is a network interface present
  (separate to `lo`) but no IP address has been assigned.

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff

  ```

  This is because when cloud-init is trying to configure network
  interfaces it doesn't find any so it doesn't configure any. But by the
  time boot is complete the network interface is present but cloud-init
  provisioning has already completed.

  You can verify this by running `sudo cloud-init clean && sudo cloud-
  init init`

  You can then see a successfully configured network interface

  ```
  ubuntu@cloudimg:~$ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: enp0s1:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
  link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
  inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic enp0s1
     valid_lft 86391sec preferred_lft 86391sec
  inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr 
noprefixroute
     valid_lft 86393sec preferred_lft 14393sec
  inet6 fe80::5054:ff:fe12:3456/64 scope link
     valid_lft forever preferred_lft forever

  ```

  The bug is also reproducible with amd64 guest on adm64 host on
  older/slower hardware.

  The suggested fixes while debugging this issue are:

  * to include `virtio-net` as a built-in in the mantic generic kernel
  * understand what needs to change in cloud-init so that it can react to late 
additions of network interfaces

  I will file a separate bug against cloud-init to address the race
  condition on emulated guest/older hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036968/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2002226] Re: Add support for kernels compiled with CONFIG_EFI_ZBOOT

[Julian Andres Klode]

** Also affects: grub2 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: grub2 (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Lunar)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2002226

Title:
  Add support for kernels compiled with CONFIG_EFI_ZBOOT

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in grub2 source package in Focal:
  New
Status in grub2-unsigned source package in Focal:
  New
Status in linux source package in Focal:
  New
Status in grub2 source package in Jammy:
  New
Status in grub2-unsigned source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in grub2 source package in Lunar:
  New
Status in grub2-unsigned source package in Lunar:
  New
Status in linux source package in Lunar:
  New

Bug description:
  [Impact]
  Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the 
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header. 
Our GRUB fails to boot such a kernel.

  We should eliminate the following check:

  grub-core/loader/efi/linux.c:75:
    if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
  return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");

  This will allow any EFI binary to be run using the linux command.

  [Test plan]
  * check that grub and EFI based ARM64 machines boot
  * check that MAAS deployment works

  [Where problems could occur]
  * Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using 
piboot, u-boot, abootimg likely one still wants to build Image.gz and have 
CONFIG_EFI_ZBOOT disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2035028] Re: 6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

[Julian Andres Klode]

Another occurence in latest boot.

Actually the same call chain it seems.

** Attachment added: "Dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035028/+attachment/5700876/+files/Dmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035028

Title:
  6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
  between headset and handsfree profiles and I think also ended up
  cycling it on/off, causing a kernel bug in the memory management.

  Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
  Sep 08 15:54:45 jak-t14-g3 kernel: kernel BUG at mm/slub.c:440!
  Sep 08 15:54:45 jak-t14-g3 kernel: invalid opcode:  [#1] PREEMPT SMP NOPTI
  Sep 08 15:54:45 jak-t14-g3 kernel: CPU: 4 PID: 353971 Comm: kworker/u33:3 Not 
tainted 6.5.0-4-generic #4-Ubuntu
  Sep 08 15:54:45 jak-t14-g3 kernel: Hardware name: LENOVO 
21CF004PGE/21CF004PGE, BIOS R23ET65W (1.35 ) 03/21/2023
  Sep 08 15:54:45 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth] 
  Sep 08 15:54:45 jak-t14-g3 kernel: RIP: 0010:__slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel: Code: 8b 06 48 89 0c 24 48 c1 e8 36 48 8b 
84 c3 d8 00 00 00 48 89 c7 48 89 44 24 20 e8 65 6c cc 00 48 8b 0c 24 48 89 44 
24 08 eb 83 <0f> 0b f7 43 08 00 0d 21 00 75 ca eb bf f7 43 08 00 0d 21 00 0f 84
  Sep 08 15:54:45 jak-t14-g3 kernel: RSP: 0018:ae30a77fbc80 EFLAGS: 00010246
  Sep 08 15:54:45 jak-t14-g3 kernel: RAX: 9c11644bac00 RBX: 
9c0dc0042c00 RCX: 801f
  Sep 08 15:54:45 jak-t14-g3 kernel: RDX: 9c11644ba800 RSI: 
9c11644ba800 RDI: ae30a77fbcf0
  Sep 08 15:54:45 jak-t14-g3 kernel: RBP: ae30a77fbd20 R08: 
0001 R09: 8bfd9f77 
  Sep 08 15:54:45 jak-t14-g3 kernel: R10:  R11: 
 R12: 9c11644ba800
  Sep 08 15:54:45 jak-t14-g3 kernel: R13: 9c11644ba800 R14: 
ec1352912e00 R15: 
  Sep 08 15:54:45 jak-t14-g3 kernel: FS:  () 
GS:9c14def0() knlGS:
  Sep 08 15:54:45 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033 
  Sep 08 15:54:45 jak-t14-g3 kernel: CR2: 55ddb6efdcd8 CR3: 
00068703a000 CR4: 00750ee0
  Sep 08 15:54:45 jak-t14-g3 kernel: PKRU: 5554
  Sep 08 15:54:45 jak-t14-g3 kernel: Call Trace:
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? die+0x37/0xa0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_trap+0xd4/0xf0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_error_trap+0x71/0xb0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? exc_invalid_op+0x52/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  __kmem_cache_free+0x318/0x360
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree+0x78/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_release_data+0x159/0x200
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree_skb_reason+0x55/0x140
  Sep 08 15:54:45 jak-t14-g3 kernel:  hci_devcd_rx+0x99/0x580 [bluetooth]
  Sep 08 15:54:45 jak-t14-g3 kernel:  process_one_work+0x223/0x440
  Sep 08 15:54:45 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? _raw_spin_lock_irqsave+0xe/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  kthread+0xf2/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg snd_usb_audio snd_usbmidi_lib 
snd_ump bnep overlay btusb btrtl btbcm btintel btmtk binfmt_misc bluetooth 
ecdh_generic ecc qrtr_mhi uvcvideo videobuf2_vmalloc cdc_mbim uvc cdc_wdm 

[Kernel-packages] [Bug 2035590] Re: [6.5] BUG: kernel NULL pointer dereference, address: 0000000000000008; #PF: supervisor write access in kernel mode

[Julian Andres Klode]

FWIW, this was after this morning's UEFI firmware update.

Devices that have been updated successfully:

   
 • Battery (1.1.6 → 1.2.7)  

   
 • Embedded Controller (0.1.25 → 0.1.28)

   
 • UEFI dbx (217 → 371) 

   
 • System Firmware (0.1.41 → 0.1.46)
 
   ^ this was updated today


** Summary changed:

- [5.5] BUG: kernel NULL pointer dereference, address: 0008; #PF: 
supervisor write access in kernel mode
+ [6.5] BUG: kernel NULL pointer dereference, address: 0008; #PF: 
supervisor write access in kernel mode

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035590

Title:
  [6.5] BUG: kernel NULL pointer dereference, address: 0008;
  #PF: supervisor write access in kernel mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I was locking my screen, so my gnome-shell got killed
  (https://bugs.launchpad.net/ubuntu/+bug/2034619) but this time I
  logged in again and opened firefox and then everything froze except
  cursor and magic sysrq.

  (Of course after sysrq-b I rebooted and my USB hub failed to
  initialize again, and I had to power cycle).

  
  I have attached the dmesg from the previous boot, there are two traces in 
there:

  Sep 14 09:41:44 jak-t14-g3 kernel: BUG: kernel NULL pointer dereference, 
address: 0008
  Sep 14 09:41:44 jak-t14-g3 kernel: #PF: supervisor write access in kernel mode
  Sep 14 09:41:44 jak-t14-g3 kernel: #PF: error_code(0x0002) - not-present page
  Sep 14 09:41:44 jak-t14-g3 kernel: PGD 0 P4D 0 
  Sep 14 09:41:44 jak-t14-g3 kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
  Sep 14 09:41:44 jak-t14-g3 kernel: CPU: 2 PID: 2042 Comm: kworker/u33:2 Not 
tainted 6.5.0-5-generic #5-Ubuntu
  Sep 14 09:41:44 jak-t14-g3 kernel: Hardware name: LENOVO 
21CF004PGE/21CF004PGE, BIOS R23ET70W (1.40 ) 08/08/2023
  Sep 14 09:41:44 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth]
  Sep 14 09:41:44 jak-t14-g3 kernel: RIP: 0010:skb_dequeue+0x50/0x80
  Sep 14 09:41:44 jak-t14-g3 kernel: Code: 74 4b 4d 85 e4 74 46 8b 43 10 83 e8 
01 89 43 10 49 8b 14 24 49 8b 44 24 08 49 c7 04 24 00 00 00 00 49 c7 44 24 08 
00 00 00 00 <48> 89 42 08 48 89 10 4c 89 ef e8 d1 5e 34 00 4c 89 e0 5b 41 5c 41
  Sep 14 09:41:44 jak-t14-g3 kernel: RSP: 0018:b8ddc90d7df0 EFLAGS: 00010002
  Sep 14 09:41:44 jak-t14-g3 kernel: RAX:  RBX: 
9c1291790d98 RCX: 
  Sep 14 09:41:44 jak-t14-g3 kernel: RDX:  RSI: 
0246 RDI: 
  Sep 14 09:41:44 jak-t14-g3 kernel: RBP: b8ddc90d7e08 R08: 
 R09: 
  Sep 14 09:41:44 jak-t14-g3 kernel: R10:  R11: 
 R12: 9c1294985c00
  Sep 14 09:41:44 jak-t14-g3 kernel: R13: 9c1291790dac R14: 
0001 R15: 9c129179
  Sep 14 09:41:44 jak-t14-g3 kernel: FS:  () 
GS:9c197e68() knlGS:
  Sep 14 09:41:44 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Sep 14 09:41:44 jak-t14-g3 kernel: CR2: 0008 CR3: 
00068e43a000 CR4: 00750ee0
  Sep 14 09:41:44 jak-t14-g3 kernel: PKRU: 5554
  Sep 14 09:41:44 jak-t14-g3 kernel: Call Trace:
  Sep 14 09:41:44 jak-t14-g3 kernel:  
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? __die+0x24/0x80
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? page_fault_oops+0x99/0x1b0
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? do_user_addr_fault+0x316/0x6b0
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? __slab_free+0xf1/0x2e0
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? exc_page_fault+0x83/0x1b0
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? asm_exc_page_fault+0x27/0x30
  Sep 14 09:41:44 jak-t14-g3 kernel:  ? skb_dequeue+0x50/0x80
  Sep 14 09:41:44 jak-t14-g3 kernel:  hci_devcd_rx+0x38/0x580 [bluetooth]
  Sep 14 09:41:44 jak-t14-g3 kernel:  process_one_work+0x223/0x440
  Sep 14 09:41:44 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
  Sep 14 09:41:44 

[Kernel-packages] [Bug 2035590] [NEW] [6.5] BUG: kernel NULL pointer dereference, address: 0000000000000008; #PF: supervisor write access in kernel mode

[Julian Andres Klode]

Public bug reported:

I was locking my screen, so my gnome-shell got killed
(https://bugs.launchpad.net/ubuntu/+bug/2034619) but this time I logged
in again and opened firefox and then everything froze except cursor and
magic sysrq.

(Of course after sysrq-b I rebooted and my USB hub failed to initialize
again, and I had to power cycle).


I have attached the dmesg from the previous boot, there are two traces in there:

Sep 14 09:41:44 jak-t14-g3 kernel: BUG: kernel NULL pointer dereference, 
address: 0008
Sep 14 09:41:44 jak-t14-g3 kernel: #PF: supervisor write access in kernel mode
Sep 14 09:41:44 jak-t14-g3 kernel: #PF: error_code(0x0002) - not-present page
Sep 14 09:41:44 jak-t14-g3 kernel: PGD 0 P4D 0 
Sep 14 09:41:44 jak-t14-g3 kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Sep 14 09:41:44 jak-t14-g3 kernel: CPU: 2 PID: 2042 Comm: kworker/u33:2 Not 
tainted 6.5.0-5-generic #5-Ubuntu
Sep 14 09:41:44 jak-t14-g3 kernel: Hardware name: LENOVO 21CF004PGE/21CF004PGE, 
BIOS R23ET70W (1.40 ) 08/08/2023
Sep 14 09:41:44 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth]
Sep 14 09:41:44 jak-t14-g3 kernel: RIP: 0010:skb_dequeue+0x50/0x80
Sep 14 09:41:44 jak-t14-g3 kernel: Code: 74 4b 4d 85 e4 74 46 8b 43 10 83 e8 01 
89 43 10 49 8b 14 24 49 8b 44 24 08 49 c7 04 24 00 00 00 00 49 c7 44 24 08 00 
00 00 00 <48> 89 42 08 48 89 10 4c 89 ef e8 d1 5e 34 00 4c 89 e0 5b 41 5c 41
Sep 14 09:41:44 jak-t14-g3 kernel: RSP: 0018:b8ddc90d7df0 EFLAGS: 00010002
Sep 14 09:41:44 jak-t14-g3 kernel: RAX:  RBX: 9c1291790d98 
RCX: 
Sep 14 09:41:44 jak-t14-g3 kernel: RDX:  RSI: 0246 
RDI: 
Sep 14 09:41:44 jak-t14-g3 kernel: RBP: b8ddc90d7e08 R08:  
R09: 
Sep 14 09:41:44 jak-t14-g3 kernel: R10:  R11:  
R12: 9c1294985c00
Sep 14 09:41:44 jak-t14-g3 kernel: R13: 9c1291790dac R14: 0001 
R15: 9c129179
Sep 14 09:41:44 jak-t14-g3 kernel: FS:  () 
GS:9c197e68() knlGS:
Sep 14 09:41:44 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Sep 14 09:41:44 jak-t14-g3 kernel: CR2: 0008 CR3: 00068e43a000 
CR4: 00750ee0
Sep 14 09:41:44 jak-t14-g3 kernel: PKRU: 5554
Sep 14 09:41:44 jak-t14-g3 kernel: Call Trace:
Sep 14 09:41:44 jak-t14-g3 kernel:  
Sep 14 09:41:44 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
Sep 14 09:41:44 jak-t14-g3 kernel:  ? __die+0x24/0x80
Sep 14 09:41:44 jak-t14-g3 kernel:  ? page_fault_oops+0x99/0x1b0
Sep 14 09:41:44 jak-t14-g3 kernel:  ? do_user_addr_fault+0x316/0x6b0
Sep 14 09:41:44 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Sep 14 09:41:44 jak-t14-g3 kernel:  ? __slab_free+0xf1/0x2e0
Sep 14 09:41:44 jak-t14-g3 kernel:  ? exc_page_fault+0x83/0x1b0
Sep 14 09:41:44 jak-t14-g3 kernel:  ? asm_exc_page_fault+0x27/0x30
Sep 14 09:41:44 jak-t14-g3 kernel:  ? skb_dequeue+0x50/0x80
Sep 14 09:41:44 jak-t14-g3 kernel:  hci_devcd_rx+0x38/0x580 [bluetooth]
Sep 14 09:41:44 jak-t14-g3 kernel:  process_one_work+0x223/0x440
Sep 14 09:41:44 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
Sep 14 09:41:44 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
Sep 14 09:41:44 jak-t14-g3 kernel:  kthread+0xf2/0x120
Sep 14 09:41:44 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
Sep 14 09:41:44 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
Sep 14 09:41:44 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
Sep 14 09:41:44 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
Sep 14 09:41:44 jak-t14-g3 kernel:  
Sep 14 09:41:44 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg overlay bnep binfmt_misc btusb 
btrtl btbcm btintel btmtk bluetooth ecdh_generic ecc qrtr_mhi uvcvideo 
videobuf2_vmalloc cdc_mbim uvc cdc_wdm videobuf2_memops cdc_ncm option 
videobuf2_v4l2 cdc_ether usbnet usb_wwan videodev mii usbserial 
videobuf2_common mc xfs nls_iso8859_1 snd_soc_dmic snd_soc_acp6x_mach 
snd_acp6x_pdm_dma snd_ctl_led snd_sof_amd_rembrandt snd_sof_amd_renoir 
snd_hda_codec_realtek snd_sof_amd_acp snd_hda_codec_generic snd_sof_pci 
snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_hda_intel snd_sof_utils 
joydev snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_common 
snd_soc_core snd_hda_codec qrtr ath11k_pci snd_comp
 ress ac97_bus snd_hda_core ath11k thinkpad_acpi
Sep 14 09:41:44 jak-t14-g3 kernel:  snd_pcm_dmaengine snd_hwdep nvram 
qmi_helpers snd_pci_ps snd_rpl_pci_acp6x snd_seq_midi snd_acp_pci mac80211 
edac_mce_amd snd_seq_midi_event snd_pci_acp6x snd_rawmidi kvm_amd snd_pcm 
snd_seq kvm snd_pci_acp5x snd_seq_device cfg80211 snd_rn_pci_acp3x snd_timer 
irqbypass snd_acp_config libarc4 

[Kernel-packages] [Bug 2035028] Re: 6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

[Julian Andres Klode]

Complete journal from 15:40 to 16:00

** Attachment added: "JournalAt1540To1600.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035028/+attachment/5699730/+files/JournalAt1540To1600.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2035028

Title:
  6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
  between headset and handsfree profiles and I think also ended up
  cycling it on/off, causing a kernel bug in the memory management.

  Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
  Sep 08 15:54:45 jak-t14-g3 kernel: kernel BUG at mm/slub.c:440!
  Sep 08 15:54:45 jak-t14-g3 kernel: invalid opcode:  [#1] PREEMPT SMP NOPTI
  Sep 08 15:54:45 jak-t14-g3 kernel: CPU: 4 PID: 353971 Comm: kworker/u33:3 Not 
tainted 6.5.0-4-generic #4-Ubuntu
  Sep 08 15:54:45 jak-t14-g3 kernel: Hardware name: LENOVO 
21CF004PGE/21CF004PGE, BIOS R23ET65W (1.35 ) 03/21/2023
  Sep 08 15:54:45 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth] 
  Sep 08 15:54:45 jak-t14-g3 kernel: RIP: 0010:__slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel: Code: 8b 06 48 89 0c 24 48 c1 e8 36 48 8b 
84 c3 d8 00 00 00 48 89 c7 48 89 44 24 20 e8 65 6c cc 00 48 8b 0c 24 48 89 44 
24 08 eb 83 <0f> 0b f7 43 08 00 0d 21 00 75 ca eb bf f7 43 08 00 0d 21 00 0f 84
  Sep 08 15:54:45 jak-t14-g3 kernel: RSP: 0018:ae30a77fbc80 EFLAGS: 00010246
  Sep 08 15:54:45 jak-t14-g3 kernel: RAX: 9c11644bac00 RBX: 
9c0dc0042c00 RCX: 801f
  Sep 08 15:54:45 jak-t14-g3 kernel: RDX: 9c11644ba800 RSI: 
9c11644ba800 RDI: ae30a77fbcf0
  Sep 08 15:54:45 jak-t14-g3 kernel: RBP: ae30a77fbd20 R08: 
0001 R09: 8bfd9f77 
  Sep 08 15:54:45 jak-t14-g3 kernel: R10:  R11: 
 R12: 9c11644ba800
  Sep 08 15:54:45 jak-t14-g3 kernel: R13: 9c11644ba800 R14: 
ec1352912e00 R15: 
  Sep 08 15:54:45 jak-t14-g3 kernel: FS:  () 
GS:9c14def0() knlGS:
  Sep 08 15:54:45 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033 
  Sep 08 15:54:45 jak-t14-g3 kernel: CR2: 55ddb6efdcd8 CR3: 
00068703a000 CR4: 00750ee0
  Sep 08 15:54:45 jak-t14-g3 kernel: PKRU: 5554
  Sep 08 15:54:45 jak-t14-g3 kernel: Call Trace:
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? die+0x37/0xa0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_trap+0xd4/0xf0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_error_trap+0x71/0xb0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? exc_invalid_op+0x52/0x80
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? asm_exc_invalid_op+0x1b/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
  Sep 08 15:54:45 jak-t14-g3 kernel:  __kmem_cache_free+0x318/0x360
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree+0x78/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_free_head+0x87/0xd0
  Sep 08 15:54:45 jak-t14-g3 kernel:  skb_release_data+0x159/0x200
  Sep 08 15:54:45 jak-t14-g3 kernel:  kfree_skb_reason+0x55/0x140
  Sep 08 15:54:45 jak-t14-g3 kernel:  hci_devcd_rx+0x99/0x580 [bluetooth]
  Sep 08 15:54:45 jak-t14-g3 kernel:  process_one_work+0x223/0x440
  Sep 08 15:54:45 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? _raw_spin_lock_irqsave+0xe/0x20
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  kthread+0xf2/0x120
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
  Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
  Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
  Sep 08 15:54:45 jak-t14-g3 kernel:  
  Sep 08 15:54:45 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg snd_usb_audio snd_usbmidi_lib 
snd_ump bnep overlay btusb btrtl btbcm btintel btmtk binfmt_misc bluetooth 
ecdh_generic ecc qrtr_mhi uvcvideo videobuf2_vmalloc cdc_mbim uvc cdc_wdm 
videobuf2_memops 

[Kernel-packages] [Bug 2035028] [NEW] 6.5 kernel BUG at mm/slub.c:440 when cycling bluetooth

[Julian Andres Klode]

Public bug reported:

In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
between headset and handsfree profiles and I think also ended up cycling
it on/off, causing a kernel bug in the memory management.

Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
Sep 08 15:54:45 jak-t14-g3 kernel: kernel BUG at mm/slub.c:440!
Sep 08 15:54:45 jak-t14-g3 kernel: invalid opcode:  [#1] PREEMPT SMP NOPTI
Sep 08 15:54:45 jak-t14-g3 kernel: CPU: 4 PID: 353971 Comm: kworker/u33:3 Not 
tainted 6.5.0-4-generic #4-Ubuntu
Sep 08 15:54:45 jak-t14-g3 kernel: Hardware name: LENOVO 21CF004PGE/21CF004PGE, 
BIOS R23ET65W (1.35 ) 03/21/2023
Sep 08 15:54:45 jak-t14-g3 kernel: Workqueue: hci0 hci_devcd_rx [bluetooth] 
Sep 08 15:54:45 jak-t14-g3 kernel: RIP: 0010:__slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel: Code: 8b 06 48 89 0c 24 48 c1 e8 36 48 8b 84 
c3 d8 00 00 00 48 89 c7 48 89 44 24 20 e8 65 6c cc 00 48 8b 0c 24 48 89 44 24 
08 eb 83 <0f> 0b f7 43 08 00 0d 21 00 75 ca eb bf f7 43 08 00 0d 21 00 0f 84
Sep 08 15:54:45 jak-t14-g3 kernel: RSP: 0018:ae30a77fbc80 EFLAGS: 00010246
Sep 08 15:54:45 jak-t14-g3 kernel: RAX: 9c11644bac00 RBX: 9c0dc0042c00 
RCX: 801f
Sep 08 15:54:45 jak-t14-g3 kernel: RDX: 9c11644ba800 RSI: 9c11644ba800 
RDI: ae30a77fbcf0
Sep 08 15:54:45 jak-t14-g3 kernel: RBP: ae30a77fbd20 R08: 0001 
R09: 8bfd9f77 
Sep 08 15:54:45 jak-t14-g3 kernel: R10:  R11:  
R12: 9c11644ba800
Sep 08 15:54:45 jak-t14-g3 kernel: R13: 9c11644ba800 R14: ec1352912e00 
R15: 
Sep 08 15:54:45 jak-t14-g3 kernel: FS:  () 
GS:9c14def0() knlGS:
Sep 08 15:54:45 jak-t14-g3 kernel: CS:  0010 DS:  ES:  CR0: 
80050033 
Sep 08 15:54:45 jak-t14-g3 kernel: CR2: 55ddb6efdcd8 CR3: 00068703a000 
CR4: 00750ee0
Sep 08 15:54:45 jak-t14-g3 kernel: PKRU: 5554
Sep 08 15:54:45 jak-t14-g3 kernel: Call Trace:
Sep 08 15:54:45 jak-t14-g3 kernel:  
Sep 08 15:54:45 jak-t14-g3 kernel:  ? show_regs+0x6d/0x80
Sep 08 15:54:45 jak-t14-g3 kernel:  ? die+0x37/0xa0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_trap+0xd4/0xf0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? do_error_trap+0x71/0xb0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? exc_invalid_op+0x52/0x80
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? asm_exc_invalid_op+0x1b/0x20
Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __slab_free+0x156/0x2e0
Sep 08 15:54:45 jak-t14-g3 kernel:  __kmem_cache_free+0x318/0x360
Sep 08 15:54:45 jak-t14-g3 kernel:  ? skb_free_head+0x87/0xd0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Sep 08 15:54:45 jak-t14-g3 kernel:  kfree+0x78/0x120
Sep 08 15:54:45 jak-t14-g3 kernel:  skb_free_head+0x87/0xd0
Sep 08 15:54:45 jak-t14-g3 kernel:  skb_release_data+0x159/0x200
Sep 08 15:54:45 jak-t14-g3 kernel:  kfree_skb_reason+0x55/0x140
Sep 08 15:54:45 jak-t14-g3 kernel:  hci_devcd_rx+0x99/0x580 [bluetooth]
Sep 08 15:54:45 jak-t14-g3 kernel:  process_one_work+0x223/0x440
Sep 08 15:54:45 jak-t14-g3 kernel:  worker_thread+0x4d/0x3f0
Sep 08 15:54:45 jak-t14-g3 kernel:  ? srso_alias_return_thunk+0x5/0x7f
Sep 08 15:54:45 jak-t14-g3 kernel:  ? _raw_spin_lock_irqsave+0xe/0x20
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_worker_thread+0x10/0x10
Sep 08 15:54:45 jak-t14-g3 kernel:  kthread+0xf2/0x120
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork+0x47/0x70
Sep 08 15:54:45 jak-t14-g3 kernel:  ? __pfx_kthread+0x10/0x10
Sep 08 15:54:45 jak-t14-g3 kernel:  ret_from_fork_asm+0x1b/0x30
Sep 08 15:54:45 jak-t14-g3 kernel:  
Sep 08 15:54:45 jak-t14-g3 kernel: Modules linked in: ccm michael_mic 
vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm 
snd_seq_dummy snd_hrtimer wireguard curve25519_x86_64 libchacha20poly1305 
chacha_x86_64 poly1305_x86_64 libcurve25519_generic libchacha ip6_udp_tunnel 
udp_tunnel cmac algif_hash algif_skcipher af_alg snd_usb_audio snd_usbmidi_lib 
snd_ump bnep overlay btusb btrtl btbcm btintel btmtk binfmt_misc bluetooth 
ecdh_generic ecc qrtr_mhi uvcvideo videobuf2_vmalloc cdc_mbim uvc cdc_wdm 
videobuf2_memops cdc_ncm videobuf2_v4l2 option cdc_ether usb_wwan usbnet 
videodev usbserial mii videobuf2_common mc xfs nls_iso8859_1 snd_soc_dmic 
snd_acp6x_pdm_dma intel_rapl_msr snd_soc_acp6x_mach intel_rapl_common 
snd_sof_amd_rembrandt snd_sof_amd_renoir snd_ctl_led joydev snd_sof_amd_acp 
snd_hda_codec_realtek snd_sof_pci snd_hda_codec_generic snd_sof_xtensa_dsp 
snd_hda_codec_hdmi snd_sof snd_hda_intel snd_sof_utils qrtr snd_intel_dspcfg 
edac_mce_amd snd_soc_core s
 nd_intel_sdw_acpi ath11k_pci snd_hda_codec snd_compress
Sep 08 15:54:45 jak-t14-g3 kernel:  ac97_bus ath11k 

[Kernel-packages] [Bug 1981525] Re: Add support for Raptor Lake CPUs

[Julian Andres Klode]

There doesn't appear to be anything to sponsor here (yet?), so
unsubscribing ubuntu-sponsors. You may resubscribe once there's a
debdiff that needs sponsoring by us.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1981525

Title:
  Add support for Raptor Lake CPUs

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project focal series:
  Fix Committed
Status in thermald package in Ubuntu:
  Invalid
Status in thermald source package in Focal:
  In Progress
Status in thermald source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Support thermald on Raptor Lake CPU.

  [Test Plan]

   * Use a machine with a Raptor Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to add support for Raptor Lake in thermald, which
  won't impact other hardware.

  [Other Info]

   * https://github.com/intel/thermal_daemon/issues/354

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1981525/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader

[Julian Andres Klode]

Right so it seems we forgot to bump the size requirements in ubuntu-
release-upgrader when bumping them in the installer in bug 1959971, you
probably should not have been able to upgrade. Albeit the size it seems
is determined from the initramfs that is in /boot.

We also don't seem to acccount for system.map which is about 10MB per
kernel

Unfortunately there isn't much else we can do here. You can of course
opt to

1) set MODULES=dep in /etc/initramfs-tools/initramfs.conf - this will
mean that you can't replace your mainboard or swap your disk into a
different machine as the initrd will only include modules relevant to
the device the system is running on

2) specify COMPRESS=xz or preferably if available a higher
COMPRESSLEVEL=1 in the same file such that compression is higher.

I don't know why your initramfs are that big, presumably you are using
nvidia gpus? With 3 kernels on my /boot and no out-of-kernel drivers I
use 438MB.

** Tags added: rls-ll-incoming

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2027847

Title:
  Bump minimum /boot size in ubuntu-release-upgrader

Status in apt package in Ubuntu:
  Won't Fix
Status in dpkg package in Ubuntu:
  Invalid
Status in kernel-package package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-kernel-headers package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  System information:
  ubuntu 23.04 x86_64
  6.2.0-24-generic

  Upgrading the system:

  $ sudo dpkg --configure -a
  Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ...
  update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/ubuntu--vg-swap_1)
  I: Set the RESUME variable to override this.
  zstd: error 70 : Write error : cannot write block : No space left on device 
  E: mkinitramfs failure zstd -q -1 -T0 70

  Check space left (none):
  $ df -h /boot
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb2   707M  693M 0 100% /boot

  What is required is to remove older kernels (and purge them most likely). 
List all the installed kernels except the current one:
  $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed 
"s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
  linux-headers-6.2.0-23
  linux-headers-6.2.0-23-generic
  linux-headers-6.2.0-25
  linux-headers-6.2.0-25-generic
  linux-image-6.2.0-23-generic
  linux-libc-dev:amd64
  linux-libc-dev:i386
  linux-modules-6.2.0-23-generic
  linux-modules-6.2.0-25-generic
  linux-modules-extra-6.2.0-23-generic
  linux-modules-extra-6.2.0-25-generic

  Is not possible to uninstall any kernel because fails:
  $ sudo apt purge linux-headers-6.2.0-23
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  Reconfigure fails again so some kernel have to be manually removed to free up 
space:
  $ sudo rm /boot/initrd.img-6.2.0-23-generic
  $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new

  Now you can reconfigure:
  $ 

  Remove kernels:
  $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic 
linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic 
linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic 
linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic 
linux-modules-extra-6.2.0-25-generic

  Reboot:
  $ sudo reboot

  Upgrade as usual:
  $ sudo apt update && sudo apt upgrade

  Before upgrading new kernels I need to check for free space and remove
  older kernels manually. Fix this so there's only one kernel left.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2027847] Re: APT installs 3 kernels at once so /boot runs out of free space left and partition size does not increase alongside with newer ubuntu versions

[Julian Andres Klode]

** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- APT installs 3 kernels at once so /boot runs out of free space left and 
partition size does not increase alongside with newer ubuntu versions
+ Bump minimum /boot size in ubuntu-release-upgrader

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2027847

Title:
  Bump minimum /boot size in ubuntu-release-upgrader

Status in apt package in Ubuntu:
  Won't Fix
Status in dpkg package in Ubuntu:
  Invalid
Status in kernel-package package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-kernel-headers package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  System information:
  ubuntu 23.04 x86_64
  6.2.0-24-generic

  Upgrading the system:

  $ sudo dpkg --configure -a
  Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ...
  update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/ubuntu--vg-swap_1)
  I: Set the RESUME variable to override this.
  zstd: error 70 : Write error : cannot write block : No space left on device 
  E: mkinitramfs failure zstd -q -1 -T0 70

  Check space left (none):
  $ df -h /boot
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb2   707M  693M 0 100% /boot

  What is required is to remove older kernels (and purge them most likely). 
List all the installed kernels except the current one:
  $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed 
"s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
  linux-headers-6.2.0-23
  linux-headers-6.2.0-23-generic
  linux-headers-6.2.0-25
  linux-headers-6.2.0-25-generic
  linux-image-6.2.0-23-generic
  linux-libc-dev:amd64
  linux-libc-dev:i386
  linux-modules-6.2.0-23-generic
  linux-modules-6.2.0-25-generic
  linux-modules-extra-6.2.0-23-generic
  linux-modules-extra-6.2.0-25-generic

  Is not possible to uninstall any kernel because fails:
  $ sudo apt purge linux-headers-6.2.0-23
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  Reconfigure fails again so some kernel have to be manually removed to free up 
space:
  $ sudo rm /boot/initrd.img-6.2.0-23-generic
  $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new

  Now you can reconfigure:
  $ 

  Remove kernels:
  $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic 
linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic 
linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic 
linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic 
linux-modules-extra-6.2.0-25-generic

  Reboot:
  $ sudo reboot

  Upgrade as usual:
  $ sudo apt update && sudo apt upgrade

  Before upgrading new kernels I need to check for free space and remove
  older kernels manually. Fix this so there's only one kernel left.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2027847] Re: Updating kernel does not check for free space left on device beforehand

[Julian Andres Klode]

We generally don't know how much space is going to be needed. APT only
keeps 2 kernel versions around, and the /boot partition is sized
accordingly for 3.

If you override this by marking kernels as manually installed, or
manually installing other versions you need to ensure that there is
enough space for those.

I only see two kernels installed though, so it's not clear to me how you
could be running out of space in /boot in the first place.

Are there additional files in there? The kernels shouldn't fill that up.

** Changed in: apt (Ubuntu)
   Status: New => Won't Fix

** Changed in: dpkg (Ubuntu)
   Status: New => Invalid

** Changed in: kernel-package (Ubuntu)
   Status: New => Won't Fix

** Changed in: kernel-package (Ubuntu)
   Status: Won't Fix => Invalid

** Changed in: linux (Ubuntu)
   Status: New => Invalid

** Changed in: linux-firmware (Ubuntu)
   Status: New => Invalid

** Changed in: linux-kernel-headers (Ubuntu)
   Status: New => Invalid

** Changed in: linux-restricted-modules (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2027847

Title:
  Updating kernel does not check for free space left on device
  beforehand

Status in apt package in Ubuntu:
  Won't Fix
Status in dpkg package in Ubuntu:
  Invalid
Status in kernel-package package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-kernel-headers package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid

Bug description:
  System information:
  ubuntu 23.04 x86_64
  6.2.0-24-generic

  Upgrading the system:

  $ sudo dpkg --configure -a
  Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ...
  update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/ubuntu--vg-swap_1)
  I: Set the RESUME variable to override this.
  zstd: error 70 : Write error : cannot write block : No space left on device 
  E: mkinitramfs failure zstd -q -1 -T0 70

  Check space left (none):
  $ df -h /boot
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb2   707M  693M 0 100% /boot

  What is required is to remove older kernels (and purge them most likely). 
List all the installed kernels except the current one:
  $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed 
"s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
  linux-headers-6.2.0-23
  linux-headers-6.2.0-23-generic
  linux-headers-6.2.0-25
  linux-headers-6.2.0-25-generic
  linux-image-6.2.0-23-generic
  linux-libc-dev:amd64
  linux-libc-dev:i386
  linux-modules-6.2.0-23-generic
  linux-modules-6.2.0-25-generic
  linux-modules-extra-6.2.0-23-generic
  linux-modules-extra-6.2.0-25-generic

  Is not possible to uninstall any kernel because fails:
  $ sudo apt purge linux-headers-6.2.0-23
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  Reconfigure fails again so some kernel have to be manually removed to free up 
space:
  $ sudo rm /boot/initrd.img-6.2.0-23-generic
  $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new

  Now you can reconfigure:
  $ 

  Remove kernels:
  $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic 
linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic 
linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic 
linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic 
linux-modules-extra-6.2.0-25-generic

  Reboot:
  $ sudo reboot

  Upgrade as usual:
  $ sudo apt update && sudo apt upgrade

  Before upgrading new kernels I need to check for free space and remove
  older kernels manually. Fix this so there's only one kernel left.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)

[Julian Andres Klode]

** Changed in: thermald (Ubuntu Jammy)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1995606

Title:
  Upgrade thermald to 2.5.1 for Jammy (22.04)

Status in OEM Priority Project:
  New
Status in thermald package in Ubuntu:
  New
Status in thermald source package in Jammy:
  New

Bug description:
  [Justification]
  The purpose of this bug is that prevent the regression in the future.
  The automatic test scripts are better for the future SRU and is still on the 
planning.

  [Test case]
  For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be 
run on machines in the CI lab:

  1. Run stress-ng, and observe the temperature/frequency/power with s-tui
    - Temperatures should stay just below trip values
    - Power/performance profiles should stay roughly the same between old 
thermald and new thermald (unless specifically expected eg: to fix 
premature/insufficient throttling)
  2. check if thermald could read rules from /dev/acpi_thermal_rel and generate 
the xml file on /etc/thermald/ correctly.
    - this depends on if acpi_thermal_rel exist.
    - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto"
   could be landed in etc/thermald/.
    - if not, the user-defined xml could be created, then jump to (3).
    - run thermald with --loglevel=debug, and compare the log with xml.auto 
file. check if the configuration could be parsed correctly.
  3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded 
correctly.
    - run thermald with --loglevel=debug, and compare the log with xml files.
    - if parsed correctly, the configurations from XML files would appear in 
the log.

  4. Run unit tests, the scripts are under test folder, using emul_temp to 
simulate the High temperatue and check thermald would throttle CPU through the 
related cooling device.
    - rapl.sh
    - intel_pstate.sh
    - powerclamp.sh
    - processor.sh
  5. check if the power/frequency would be throttled once the temperature reach 
the trip-points of thermal zone.
  6. check if system would be throttled even the temperature is under the 
trip-points.

  [ Where problems could occur ]
  since the PL1 min/max is introduced, there may have some cases that don't 
check the minimum of PL1 then make PL1 to smaller and smaller and throttle the 
CPU. 
  this may cause machines run like the old behavior that doesn't have PL1 
min/max.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1995606/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2018275] Re: Fix the in-motion function does not work

[Julian Andres Klode]

The bug description does not match the requirements for an SRU,
particularly "low" is no reasonable answer to "where problems could
occur"

** Changed in: thermald (Ubuntu Jammy)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/2018275

Title:
  Fix the in-motion function does not work

Status in thermald package in Ubuntu:
  New
Status in thermald source package in Jammy:
  Incomplete

Bug description:
  [Summary]
  in-Motion condition doesn't work with adaptive performance policy

  [Fix]
  This patch fix the issue,
  cc0890a59725) Always match motion = 0

  [Test cases]
  1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X
  2. run the thermald applied the fix.
  #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > 
thermald_log.log" and check the log
  3. in-motion condition works

  [Where problems could occur]
  low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic

[Julian Andres Klode]

Unsubscribing ubuntu-sponsors as this seems done except for this
firmware-sof kinetic  tag which is New and I hereby mark Incomplete as
it's not clear if there's anything left to do there to me

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1966841

Title:
  alsa/sdw: Fix the audio issue on a Dell machine without internal mic

Status in HWE Next:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in firmware-sof source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Kinetic:
  Incomplete
Status in linux source package in Kinetic:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  SRU template for linux-firmware
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current asoc driver
  can't work on this machine, the speaker and headset couldn't work.

  [Fix]
  Backport a tplg file which is specific to this mahcine

  [Test]
  Install the patched linux-firmware and boot the latest oem-5.14 kernel
  on the machine, check dmesg, it loads the correct tplg, and
  test speaker and headset, all work well.

  [Where problems could occur]
  This SRU is adding a new tplg file, it has no chance to introduce
  a regression.

  SRU template for linux
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current soc driver
  can't work on this machine, it will load a wrong tplg without this patch,
  and the speaker and headset couldn't work.

  [Fix]
  Backport one patch from upstream.

  [Test]
  Boot the patched kernel on the machine, check dmesg, it loads the
  correct tplg, and test speaker and headset, all work well.

  [Where problems could occur]
  If it could introduce regression, it will be on the sdw codec matching
  for adl machines, then it will make the driver load wrong tplg and make
  output device and input device not work anymore. But this possibility
  is very low, we already tested the patch on some dell adl machines, no
  regression found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966841/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic

[Julian Andres Klode]

Unsubscribing ubuntu-sponsors as this seems done except for this
firmware-sof kinetic  tag which is New and I hereby mark Incomplete as
it's not clear if there's anything left to do there to me

** Changed in: firmware-sof (Ubuntu Kinetic)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1966841

Title:
  alsa/sdw: Fix the audio issue on a Dell machine without internal mic

Status in HWE Next:
  Fix Released
Status in firmware-sof package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in firmware-sof source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in firmware-sof source package in Kinetic:
  Incomplete
Status in linux source package in Kinetic:
  Fix Released
Status in linux-firmware source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  SRU template for linux-firmware
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current asoc driver
  can't work on this machine, the speaker and headset couldn't work.

  [Fix]
  Backport a tplg file which is specific to this mahcine

  [Test]
  Install the patched linux-firmware and boot the latest oem-5.14 kernel
  on the machine, check dmesg, it loads the correct tplg, and
  test speaker and headset, all work well.

  [Where problems could occur]
  This SRU is adding a new tplg file, it has no chance to introduce
  a regression.

  SRU template for linux
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current soc driver
  can't work on this machine, it will load a wrong tplg without this patch,
  and the speaker and headset couldn't work.

  [Fix]
  Backport one patch from upstream.

  [Test]
  Boot the patched kernel on the machine, check dmesg, it loads the
  correct tplg, and test speaker and headset, all work well.

  [Where problems could occur]
  If it could introduce regression, it will be on the sdw codec matching
  for adl machines, then it will make the driver load wrong tplg and make
  output device and input device not work anymore. But this possibility
  is very low, we already tested the patch on some dell adl machines, no
  regression found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1966841/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969434] Re: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI

[Julian Andres Klode]

I don't see anything sponsorable for backport-iwlwifi-dkms/focal and the
other tasks are in various done states, so I am going to mark this task
Incomplete and unsubscribe ubuntu sponsors.

** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1969434

Title:
  build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-hwe-5.15 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms source package in Focal:
  Incomplete
Status in linux source package in Focal:
  Invalid
Status in linux-meta source package in Focal:
  Invalid
Status in linux-meta-hwe-5.15 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in backport-iwlwifi-dkms source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-meta source package in Jammy:
  Fix Released
Status in linux-meta-hwe-5.15 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [SRU Justfication]

  [Impact]

  Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress,
  and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16.
  Not reproducible on every platform with AX211 installed, and the chances
  of such failures vary from one to another.

  [Fix]

  A few solutions were considered. The very first one is to ask Intel to
  fix -64 firmware directly, and the answer is a solid no claimed -64 is
  not the planned production version of AX211.

  It's also possible to backport FW API from v5.16, but while iwlwifi FW
  API is more or less a black box to us and the new FW APIs also depends
  on updates on the wireless stack, this is going to be very risky and
  actually we had regressions before after such backports.

  The last viable solution is to run backport-iwlwifi-dkms >= rev 8580 on
  the effected platforms. This means oem-5.14 and its migration target,
  hwe-5.15 will not be able to drive this piece of hw flawlessly without
  backport-iwlwifi-dkms installed.

  However, while we need secureboot to be enabled on these platforms,
  backport-iwlwifi-dkms must also be signed somehow. There are two
  possible method to achieve this, too. One, to prebuild this dkms as zfs
  and v4l2loopback does. However, while backport-iwlwifi-dkms generates
  kernel modules with exactly the same name as the in-tree ones, when
  prebuilt, they'll be available directly from the linux-modules package
  and therefore overrides the in-tree ones always, turning the in-tree
  driver completely useless and risk the stability of all other generic
  installations.

  The second one is to build backport-iwlwifi-dkms as nvidia graphic
  drivers in the linux-restricted-modules source package. In this way,
  affected platforms may install the corresponding packages when needed
  without interfering others. However, l-r-m is for restricted modules
  that needs special care of redistribution of its binaries, and
  backport-iwlwifi-dkms is GPL licensed.

  Here a similar but simpler process in the main kernel tree is
  re-implemented. Two additional packages,
  linux-modules-MODULE-PKGVER-ABINUM-FLAVOUR and its meta package
  linux-modules-MODULE-FLAVOUR will be created.

  [Test Case]

  Test builds:
  ./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb
  ./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb
  ./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb
  ./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb
  ./oem-5.17/amd64/linux-modules-iwlwifi-5.17.0-1003-oem_5.17.0-1003.3_amd64.deb
  ./oem-5.17/amd64/linux-modules-iwlwifi-oem_5.17.0-1003.3_amd64.deb
  
./oem-5.14/amd64/linux-modules-iwlwifi-5.14.0-1033-oem_5.14.0-1033.36_amd64.deb
  ./oem-5.14/amd64/linux-modules-iwlwifi-oem_5.14.0-1033.36_amd64.deb

  [Where problems could occur]

  The latest (9858-0ubuntu2) backport-iwlwifi-dkms/jammy actually fails
  to build under this proposed process. Debdiff attached to the same
  bug.

  Different from nvidia packages built from l-r-m, the generated package
  names do not carry an additional short version string, e.g. nvidia-410,
  as there is no such necessity to build multiple versions of iwlwifi.
  The modules are installed to /lib/modules//kernel/iwlwifi, not
  iwlwifi-9858/.

  == 

[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )

[Julian Andres Klode]

Unsubscribing Ubuntu Sponsors, as this issue seems to be fairly complex
and the patch seems controversial and incomplete.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1581594

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  Triaged

Bug description:
  Hello, here's my system info

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1581594/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

[Julian Andres Klode]

*** This bug is a duplicate of bug 1936857 ***
https://bugs.launchpad.net/bugs/1936857

** This bug has been marked a duplicate of bug 1936857
   grub-install: error: efibootmgr: not found.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1991676

Title:
  Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
  bionic-proposed fails to install/upgrade (grub-install: error:
  efibootmgr: not found.)

Status in ubuntu-kernel-tests:
  New
Status in grub2-signed package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in grub2-signed source package in Bionic:
  Triaged
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  The ADT tests for arm64 kernels in Bionic are failing during the setup
  phase with the following errors:

  Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
  Installing for arm64-efi platform.
  grub-install: error: efibootmgr: not found.
  dpkg: error processing package grub-efi-arm64-signed (--configure):
   installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 1
  Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
  Errors were encountered while processing:
   grub-efi-arm64-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: 
  badpkg: testbed setup commands failed with status 100
  autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands 
failed with status 100

  ADT test log:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

I'm going to set this to Won't Fix because that seems to be an important
part of the solver logic, and the workarounds - running upgrade first,
or using ubuntu-drivers - are easy to do and the potential for
regression significantly outweighs them.

This will get solved eventually by a nicer solver (a proper optimization
solver) sure, if we make it there. Lots of caveats because I'm not that
clever that I want to write a competitive partial weighted maxsat or
linear programming solver, so end up reusing libraries, and neither z3
nor clasp are exactly optimal (also figuring out how to get them to
explain uninstallability is hard).

On the other hand, I am also exploring preventing the solver (both old
and new) from removing packages due to Conflicts, so removals can only
happen as part of a dist-upgrade or an explicit removal request, to
further reduce issues with people breaking their systems by accidentally
removing half of it (caveats as to the scope with manually vs
automatically installed packages, and whether packages are not needed
anymore are to be).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

** Changed in: apt (Ubuntu)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

I think we debugged this recently but I'm not sure where the end result
of this is that we do not mark packages for removal that have an upgrade
available, hence we end up without a removal request after the first
stage solver, and the Conflicts solver that runs after can't solve that.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

Reproduced issue and dumped test case into https://salsa.debian.org/apt-
team/apt-tests/-/blob/main/edsp/fail-ubuntu-1992513.edsp.log for future
analysis when doing solver work.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

** Tags removed: foundations-todo

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2009620] Re: No Intel sound drivers available for this Mac Mini

[Julian Andres Klode]

Please decide whether you are reporting a missing sound driver or the
grub-install crash, you can't put two bugs into one report.

Regarding the grub crash it's curious but an issue in the firmware
variable handling, not grub.

** Package changed: grub2-signed (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009620

Title:
  No Intel sound drivers available for this Mac Mini

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  No sound ...

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: grub-efi-amd64-signed 1.182~22.04.1+2.06-2ubuntu10
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  AptOrdering:
   grub-efi-amd64-signed:amd64: Install
   grub-efi-amd64-bin:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar  7 16:19:26 2023
  ErrorMessage: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: grub2-signed
  Title: package grub-efi-amd64-signed 1.182~22.04.1+2.06-2ubuntu10 failed to 
install/upgrade: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009620/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed

[Julian Andres Klode]

Actually let me reassign to Linux and mark incomplete.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2007286

Title:
  Ubuntu does not clean out old kernel module files (in /lib/modules)
  when old kernels are removed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  corrado@corrado-x-kinetic:~$ ls /lib/modules
  5.19.0-23-generic  5.19.0-28-generic  5.19.0-29-generic  5.19.0-31-generic
  corrado@corrado-x-kinetic:~$ ls /boot
  config-5.19.0-29-generic  memtest86+.elf
  config-5.19.0-31-generic  memtest86+_multiboot.bin
  efi   System.map-5.19.0-29-generic
  grub  System.map-5.19.0-31-generic
  initrd.imgvmlinuz
  initrd.img-5.19.0-29-generic  vmlinuz-5.19.0-29-generic
  initrd.img-5.19.0-31-generic  vmlinuz-5.19.0-31-generic
  initrd.img.oldvmlinuz.old
  memtest86+.bin
  corrado@corrado-x-kinetic:~$ 
  see also 
https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apt 2.5.3
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 14 16:23:49 2023
  InstallationDate: Installed on 2022-11-28 (77 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 2007286] Re: Ubuntu does not clean out old kernel module files (in /lib/modules) when old kernels are removed

[Julian Andres Klode]

There can be many reasons why files remain. Did you purge the packages
for those Linux versions? Did you do any dkms modules.

This is not a bug in apt, apt is not responsible for those files.

** Changed in: apt (Ubuntu)
   Status: New => Invalid

** Package changed: apt (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Invalid => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2007286

Title:
  Ubuntu does not clean out old kernel module files (in /lib/modules)
  when old kernels are removed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  corrado@corrado-x-kinetic:~$ ls /lib/modules
  5.19.0-23-generic  5.19.0-28-generic  5.19.0-29-generic  5.19.0-31-generic
  corrado@corrado-x-kinetic:~$ ls /boot
  config-5.19.0-29-generic  memtest86+.elf
  config-5.19.0-31-generic  memtest86+_multiboot.bin
  efi   System.map-5.19.0-29-generic
  grub  System.map-5.19.0-31-generic
  initrd.imgvmlinuz
  initrd.img-5.19.0-29-generic  vmlinuz-5.19.0-29-generic
  initrd.img-5.19.0-31-generic  vmlinuz-5.19.0-31-generic
  initrd.img.oldvmlinuz.old
  memtest86+.bin
  corrado@corrado-x-kinetic:~$ 
  see also 
https://discourse.ubuntu.com/t/ubuntu-does-not-clean-out-old-kernel-module-files-in-lib-modules-when-old-kernels-are-removed/33906

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apt 2.5.3
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 14 16:23:49 2023
  InstallationDate: Installed on 2022-11-28 (77 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007286/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

This fix will be included in grub2-unsigned/2.06-2ubuntu14.1 for
kinetic, jammy, focal, bionic. Binaries have been built in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
for kinetic.

Signing request: https://answers.launchpad.net/canonical-signing-
jobs/+question/704589

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: grub2-signed (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: grub2-unsigned (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools (Ubuntu Kinetic)

** No longer affects: initramfs-tools (Ubuntu Jammy)

** No longer affects: initramfs-tools (Ubuntu Focal)

** No longer affects: initramfs-tools (Ubuntu Bionic)

** No longer affects: linux (Ubuntu)

** No longer affects: initramfs-tools (Ubuntu)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu Jammy)

** No longer affects: linux (Ubuntu Kinetic)

** Description changed:

  [Workaround]
  
  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125
  
  [Impact]
  
   * In some cases, if the users’ initramfs grow bigger, then it’ll likely
  not be able to be loaded by grub2.
  
   * Some real cases from OEM projects:
  
  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts
  the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the
  gfxpayload=auto will remain to use 4K resolution since it’s what EFI
  POST passed.
  
  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:
  
  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```
  
  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:
  
  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

The entire upload will be uploaded to all older releases but we do have
a security upload already in the unapproved queues that should go out
first, but that needs approving those first, them passing the SRU
verification, a resigning against the new signing key the new shim
needs, and finally someone to release them. So that the security update
can be released to security pocket.

This won't be ready before Monday the week after next week at the
earliest (7 day testing period in proposed).

People that can approve are still out and only return next week, so I
don't think that's entirely realistic we get the existing uploads into
proposed on Monday.

If we could get them in by Thursday they could go out Monday the 23rd
and we may be able to then upload this fix and release it on like 31st
or so.

We're strictly limited by the point release - it needs to be ready for
that.

** Changed in: grub2-signed (Ubuntu)
Milestone: None => ubuntu-22.04.2

** Changed in: grub2-unsigned (Ubuntu)
Milestone: None => ubuntu-22.04.2

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:

  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 0002 000F
  BS_Data2B633000-2B63CFFF 000A 000F
  Available  2B63D000-2B649FFF 000D 000F
  BS_Data2B64A000-2B64EFFF 0005 000F
  Available  2B64F000-2B666FFF 0018 000F
  BS_Data2B667000-2D8D5FFF 226F 000F
  LoaderCode 2D8D6000-2D8E9FFF 0014 000F
  BS_Data2D8EA000-2D925FFF 003C 000F
  LoaderCode 2D926000-2D932FFF 000D 000F
  

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

The term you're looking for is workaround, not triage or fixes. Triage
is the process of understanding the bug and marking it the correct
things.

Not using the same language as everyone else and writing very long
comments makes it hard to understand.

First I thought you reported an out of memory issue on Pis. Then I
thought you were saying that the fix doesn't help. It took me a long
while to realize it was completely irrelevant for the process of
resolving that bug.

If the initrd grows significantly please open a separate bug against
linux so that is tracked - maybe something went wrong - and leave a
comment here.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

Hi ybdjkfd I don't really understand what you are doing and how it's
relevant. This issue should be fixed in lunar-proposed 2.06-2ubuntu16,
please only add comments if you have meaningful insights regarding the
verification of that update.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

** Changed in: grub2-unsigned (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: grub2-signed (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * 

[Kernel-packages] [Bug 1995041] Re: Fix ath11k deadlock on WCN6855

[Julian Andres Klode]

I see it was marked Fix released for linux (Ubuntu), however it's not
actually fixed in lunar, not even the update from kinetic-proposed has
been copied up to lunar-proposed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1995041

Title:
  Fix ath11k deadlock on WCN6855

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  ath11k is in deadlock when stress reboot or suspend on WCN6855.
  sometimes kernel hang.

  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace:
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: 
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? 
ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k]
  Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211]

  [Fix]
  Fix this by switching from using regulatory_set_wiphy_regd_sync() to
  regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue 
which
  handles the locking on it's own. So the ath11k workqueue can simply exit 
without
  taking any locks, avoiding the deadlock.

  [Test]
  Verified on hardware, stress reboot and suspend 30 times OK.

  [Where problems could occur]
  It may break ath11k wifi driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1995041/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

I have now picked all the rhboot patches in 2.06-2ubuntu16~ppa1 in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
and will boot that before uploading to the archive.

This *should* allow initrds over 4GB but obviously bugs could be there.
The important bit is that we are now close to the rhboot branch again in
that file such that the whole thing is maintainable to some extent at
least.

Once this is uploaded to lunar people can test this easily on secure
boot systems without having to install PPA signing keys in MOK.

I'm gonna see if I can run some tests myself and reproduce this.

Also it turns out it fails to build the i386-efi target due to pointer
size mismatches.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  

[Kernel-packages] [Bug 1991036] Re: ath11k: Freezing kernel when doing s2idle [17cb:1103]

[Julian Andres Klode]

I think kernel team needs patch sent to ML, but I don't do a lot of
kernel stuff. FWIW, here's the log from 6.1-rc5 which includes the fix:

Nov 29 20:03:28 jak-t14-g3 kernel: PM: suspend exit
Nov 29 20:03:28 jak-t14-g3 kernel: ath11k_pci :02:00.0: BAR 0: assigned 
[mem 0x8000-0x801f 64bit]
Nov 29 20:03:28 jak-t14-g3 kernel: ath11k_pci :02:00.0: MSI vectors: 32
Nov 29 20:03:28 jak-t14-g3 kernel: ath11k_pci :02:00.0: wcn6855 hw2.1
Nov 29 20:03:29 jak-t14-g3 kernel: mhi mhi0: Requested to power ON
Nov 29 20:03:29 jak-t14-g3 kernel: mhi mhi0: Power on setup success
Nov 29 20:03:29 jak-t14-g3 kernel: mhi mhi0: Wait for device to enter SBL or 
Mission mode
Nov 29 20:03:29 jak-t14-g3 kernel: ath11k_pci :02:00.0: chip_id 0x12 
chip_family 0xb board_id 0xff soc_id 0x400c1211
Nov 29 20:03:29 jak-t14-g3 kernel: ath11k_pci :02:00.0: fw_version 
0x110c0c35 fw_build_timestamp 2022-06-24 10:50 fw_build_id 
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.16
Nov 29 20:03:29 jak-t14-g3 kernel: Generic FE-GE Realtek PHY r8169-0-100:00: 
attached PHY driver (mii_bus:phy_addr=r8169-0-100:00, irq=MAC)
Nov 29 20:03:30 jak-t14-g3 kernel: ath11k_pci :02:00.0: ignore reset dev 
flags 0x8000
Nov 29 20:03:40 jak-t14-g3 kernel: ath11k_pci :02:00.0: failed to wait wlan 
mode request (mode 0): -110
Nov 29 20:03:40 jak-t14-g3 kernel: ath11k_pci :02:00.0: qmi failed to send 
wlan fw mode: -110
Nov 29 20:03:40 jak-t14-g3 kernel: ath11k_pci :02:00.0: failed to send 
firmware start: -110


(You can see I try the unpublished firmware from the ath11-firmware repo right 
now and it doesn't help either).

(but anything is better than hanging netlink and requiring you to reboot
via sysrq ;))

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991036

Title:
  ath11k: Freezing kernel when doing s2idle [17cb:1103]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On ubuntu 22.04, I installed v6.0-rc3 mainline kernel.
  linux-firmware 20220329.git681281e4-0ubuntu3.4

  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: PM: suspend entry (s2idle)
  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: Filesystems sync: 0.004 seconds
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing user space processes ...
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing of tasks failed after 
20.007 seconds (9 tasks refusing to freeze, wq_busy=0):
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: task:NetworkManager  state:D 
stack:0 pid:  988 ppid: 1 flags:0x4006
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Call Trace:
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __schedule+0x221/0x5c0
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule+0x5f/0x100
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule_timeout+0x111/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  wait_for_completion+0x88/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __flush_work.isra.0+0x1b9/0x340
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
flush_workqueue_prep_pwqs+0x140/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __cancel_work_timer+0x10d/0x190
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
ath11k_mac_config_mon_status_default+0x9c/0x170 [ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  cancel_work_sync+0x10/0x20
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ath11k_mac_op_stop+0x9f/0x1e0 
[ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  drv_stop+0x45/0x120 [mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop_device+0x43/0x50 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_do_stop+0x6b1/0x980 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
cond_synchronize_rcu_expedited+0x40/0x40
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? qdisc_reset+0x27/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop+0x43/0x170 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __dev_close_many+0x9f/0x120

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1991036/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991036] Re: ath11k: Freezing kernel when doing s2idle [17cb:1103]

[Julian Andres Klode]

Dear kernel bot, this bug has enough info, and there's a patch upstream
that's part of 6.1 that fixes the issue.

Though I can say I now hit a failure to restart the device / load
firmware after a 2nd resume.

This is likely another race; if you just suspend by echo mem >
/sys/power/state in a loop, it works multiple times pretty reliable.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991036

Title:
  ath11k: Freezing kernel when doing s2idle [17cb:1103]

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On ubuntu 22.04, I installed v6.0-rc3 mainline kernel.
  linux-firmware 20220329.git681281e4-0ubuntu3.4

  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: PM: suspend entry (s2idle)
  Sep 01 13:25:13 u-ThinkPad-P16-Gen-1 kernel: Filesystems sync: 0.004 seconds
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing user space processes ...
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Freezing of tasks failed after 
20.007 seconds (9 tasks refusing to freeze, wq_busy=0):
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: task:NetworkManager  state:D 
stack:0 pid:  988 ppid: 1 flags:0x4006
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel: Call Trace:
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __schedule+0x221/0x5c0
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule+0x5f/0x100
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  schedule_timeout+0x111/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  wait_for_completion+0x88/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __flush_work.isra.0+0x1b9/0x340
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
flush_workqueue_prep_pwqs+0x140/0x140
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __cancel_work_timer+0x10d/0x190
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
ath11k_mac_config_mon_status_default+0x9c/0x170 [ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  cancel_work_sync+0x10/0x20
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ath11k_mac_op_stop+0x9f/0x1e0 
[ath11k]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  drv_stop+0x45/0x120 [mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop_device+0x43/0x50 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_do_stop+0x6b1/0x980 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? 
cond_synchronize_rcu_expedited+0x40/0x40
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ? qdisc_reset+0x27/0x150
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  ieee80211_stop+0x43/0x170 
[mac80211]
  Sep 01 13:25:33 u-ThinkPad-P16-Gen-1 kernel:  __dev_close_many+0x9f/0x120

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1991036/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

@Craig The limit in Debian is actually much lower than in Ubuntu even,
but fixing it there is even harder as that misses a lot more patches.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  

[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

[Julian Andres Klode]

Well surely not more than the past year, this is not a new bug after
all, the regression was introduced with the initial boothole update when
we did the one grub split.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1991676

Title:
  Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
  bionic-proposed fails to install/upgrade (grub-install: error:
  efibootmgr: not found.)

Status in ubuntu-kernel-tests:
  New
Status in grub2-signed package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in grub2-signed source package in Bionic:
  Triaged
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  The ADT tests for arm64 kernels in Bionic are failing during the setup
  phase with the following errors:

  Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
  Installing for arm64-efi platform.
  grub-install: error: efibootmgr: not found.
  dpkg: error processing package grub-efi-arm64-signed (--configure):
   installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 1
  Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
  Errors were encountered while processing:
   grub-efi-arm64-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: 
  badpkg: testbed setup commands failed with status 100
  autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands 
failed with status 100

  ADT test log:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic

[Julian Andres Klode]

Actions: cherry-pick two patches for kinetic and upload new upstream
release to lunar.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990964

Title:
  FTBFS on kinetic

Status in linux package in Ubuntu:
  Fix Released
Status in strace package in Ubuntu:
  Triaged

Bug description:
  As can be seen in [1], strace FTBFS in kinetic: this is caused by the
  kernel headers (linux-libc-dev) which do not define F_GETLK64 and
  other on 64b builds because the kernel contains a bogus commit
  (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
  fcntl.h"). This commit actually did the opposite of what it was
  supposed to do, namely defining those macros even on 64b builds. There
  is an attempt here to fix this which was not merged yet:
  
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/

  [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
  amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

[Julian Andres Klode]

** Changed in: grub2-signed (Ubuntu Bionic)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: grub2-signed (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1991676

Title:
  Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
  bionic-proposed fails to install/upgrade (grub-install: error:
  efibootmgr: not found.)

Status in ubuntu-kernel-tests:
  New
Status in grub2-signed package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed
Status in grub2-signed source package in Bionic:
  Triaged
Status in linux-hwe-5.4 source package in Bionic:
  Confirmed

Bug description:
  The ADT tests for arm64 kernels in Bionic are failing during the setup
  phase with the following errors:

  Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
  Installing for arm64-efi platform.
  grub-install: error: efibootmgr: not found.
  dpkg: error processing package grub-efi-arm64-signed (--configure):
   installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 1
  Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
  Errors were encountered while processing:
   grub-efi-arm64-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: 
  badpkg: testbed setup commands failed with status 100
  autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands 
failed with status 100

  ADT test log:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

** Changed in: grub2-unsigned (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Changed in: grub2-signed (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

** Tags added: fr-2934

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  `/var/cache/pbuilder/build/276481/build/grub2-2.06/obj/monolithic/grub-
  

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

Really the workaround is to set MODULES=dep in /etc/initramfs-
tools/initramfs.conf, this yields a much smaller initramfs (but you
can't take out the disk and boot it in another machine), disabling
secure boot or sgx should not be doing anything.

** Also affects: grub2-unsigned (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2-unsigned (Ubuntu)
   Status: New => Triaged

** Changed in: grub2-unsigned (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

** Tags removed: foundations-triage-discuss
** Tags added: foundations-todo

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date

[Julian Andres Klode]

It does yeah, and obviously that's a solver bug that's going to need
some more work to root cause.


** Changed in: apt (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: apt (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513

Title:
  apt will not install nvidia-driver-470-server if nvidia-
  driver-450-server is installed and out of date

Status in apt package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  apt/jammy

  apt will refuse to install nvidia-driver-470-server if 
nvidia-driver-450-server is installed *and* out of date. I can reproduce this 
by disabling all but the jammy release pocket, installing the old n-d-450-s 
from there, and then enabling updates and trying to install n-v-470-s (where a 
new
  n-d-450-s is available):

  # libnvidia-gl-450-server has an update available
  root@dannf-apt-jammy:/var/cache# apt install --dry-run 
libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libnvidia-common-450-server : Conflicts: libnvidia-common
   libnvidia-common-470-server : Conflicts: libnvidia-common
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991676] Re: Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from bionic-proposed fails to install/upgrade (grub-install: error: efibootmgr: not found.)

[Julian Andres Klode]

** Changed in: grub2-signed (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1991676

Title:
  Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
  bionic-proposed fails to install/upgrade (grub-install: error:
  efibootmgr: not found.)

Status in ubuntu-kernel-tests:
  New
Status in grub2-signed package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in grub2-signed source package in Bionic:
  Triaged
Status in linux-hwe-5.4 source package in Bionic:
  New

Bug description:
  The ADT tests for arm64 kernels in Bionic are failing during the setup
  phase with the following errors:

  Setting up grub-efi-arm64-signed (1.173.2~18.04.1+2.04-1ubuntu47.4) ...
  Installing for arm64-efi platform.
  grub-install: error: efibootmgr: not found.
  dpkg: error processing package grub-efi-arm64-signed (--configure):
   installed grub-efi-arm64-signed package post-installation script subprocess 
returned error exit status 1
  Setting up libx11-6:arm64 (2:1.6.4-3ubuntu0.5) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Processing triggers for libc-bin (2.27-3ubuntu1.6) ...
  Errors were encountered while processing:
   grub-efi-arm64-signed
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  blame: 
  badpkg: testbed setup commands failed with status 100
  autopkgtest [15:12:03]: ERROR: erroneous package: testbed setup commands 
failed with status 100

  ADT test log:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/l/linux-hwe-5.4/20220930_151219_13ac3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1991676/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Julian Andres Klode]

On my kinetic system, /dev has nosuid, but no noexec.

** Tags added: foundations-triage-discuss

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991975

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in systemd source package in Jammy:
  Confirmed

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

[Julian Andres Klode]

Is there anything left to do here?

** Changed in: klibc (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: klibc (Ubuntu Cosmic)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1760106

Title:
  Enable configuring resume offset via sysfs

Status in OEM Priority Project:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in klibc source package in Bionic:
  Incomplete
Status in linux source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in klibc source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Cannot hibernate & resume from a swapfile

  [Test Case]

   * Create or enlarge swapfile to be big enough for hibernation
   * Attempt to hibernate and resume

  [Regression Potential]

   * Hibernation is not reliable technology in itself, and multiple
  things may cause failure to resume. Thus it is sufficient to validate
  this bug after swapfile is attempted for hibernation and the disk
  offset kernel parameter is modified. Irrespective if actual suspending
  or resume were successful or not.

  [Other Info]
   
   * Original bug report

  In 4.17 a new attribute is introduced to configure the hibernation
  resume offset. Since Ubuntu enables a swapfile by default this
  attribute is important to be able to make hibernation work "out of the
  box".

  The patch in the kernel is here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9

  Systemd support for adopting this change is available here:
  https://github.com/systemd/systemd/pull/8406
  As of 3/30/18 it's not yet been merged however.

  Klibc support for adopting this change is available here:
  https://www.zytor.com/pipermail/klibc/2018-March/003986.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760106/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

OK the patch set here is broken, we gotta do this from scratch properly.
So I'm going to start cherry picking the rhboot patches for memory
management. I have applied so far from bug 1989446 the backport of "Try
to pick better locations for kernel and initrd" and cherry-picked from
rhboot the "x86-efi: Use bounce buffers for reading to addresses > 4GB"
patch and will continue picking up the memory changes from the rhboot
branch and then we can address any gaps remaining.

Now the problem with the patch set is clearly that the rhboot patches
miss half their content and are applied after a custom patch that
changes most of the memory management, which does not help.

0129 I thought was "Try to pick better locations for kernel and initrd"
but it's something custom that's deep into the memory management code
and just looks like it. I thought only increasing the memory limit in
the last patch was the custom bit. I do not want to change general
memory allocation in grub vs our upstreams. Scary.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

Our goal should be to merge the entire patch series into kinetic, worst
case, kinetic will not be installable for some users. This means we will
have decent results from people trying that in the next 4 weeks (by Oct
27 the release has been out 1 week).

In the meantime, next week we should push out the security update again.
Then we can take dannf's patches and the first patch here for that SRU
to unblock the other OEM thing which certainly is less controversial.
And on like Oct 27 if we don't have serious regressions do a final SRU
with all the patches.

I'll see what I can do to get those into kinetic so that we get that bit
moving but I'll be travelling or meeting people most of next week.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ 

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

@jeremyszu (os369510) Did you see #90, it seems your patch would cause
boot failures on older system unable to handle this memory range.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  

[Kernel-packages] [Bug 1699942] Re: network-manager fails to deprecate addresses

[Julian Andres Klode]

We believe the kernel handles RAs itself, adding a task for it.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1699942

Title:
  network-manager fails to deprecate addresses

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  network manager does not properly deprecate autoconfigured temporary IP 
addresses when ValidLifetime for a prefix is 0 in router advertisements. This 
behaviour is non-compliant with RFC 4861 § 6.3.4, which reads:
  If the prefix is already present in the host's Prefix List as
  the result of a previously received advertisement, reset its
  invalidation timer to the Valid Lifetime value in the Prefix
  Information option.  If the new Lifetime value is zero, time-out
  the prefix immediately.

  The hosts instead continued to use temporary addresses configured
  until they reached their timeout, rather than immediately dropping the
  addresses. It further appears that it is generating new temporary
  addresses when the previous ones expire, but I have not been
  monitoring hosts closely enough to tell for sure---I will update on
  this when I have further information.

  This problem was discovered on Ubuntu Studio 16.04.2; it is not
  present on Ubuntu Server (which uses Debian networking scripts).

  Additional Info:

  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.6-0ubuntu0.16.04.1
Candidate: 1.2.6-0ubuntu0.16.04.1
Version table:
   *** 1.2.6-0ubuntu0.16.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.2-0ubuntu0.16.04.4 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699942/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1984203] Re: /var/run/reboot-required not created after installing new kernel

[Julian Andres Klode]

** Package changed: dpkg (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984203

Title:
  /var/run/reboot-required not created after installing new kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just ran `apt-get dist-upgrade -y` on two Jammy systems. On one of
  them, this resulted in /var/run/reboot-required and /var/run/reboot-
  required.pkgs being created:

  jik@jik-x1:~$ ls -l /var/run/reboot-required*
  -rw-r--r-- 1 root root 32 Aug 10 10:09 /var/run/reboot-required
  -rw-r--r-- 1 root root 41 Aug 10 10:09 /var/run/reboot-required.pkgs
  jik@jik-x1:~$ cat /var/run/reboot-required.pkgs
  linux-image-5.15.0-46-generic
  linux-base
  jik@jik-x1:~$ 

  On the other one (the one on which I ran `ubuntu-bug /usr/bin/dpkg` to
  create this issue) the same kernel package was installed during the
  `apt-get dist-upgrade -y` run, but /var/run/reboot-required and
  /var/run/reboot-required.pkgs were NOT created.

  This seems... problematic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dpkg 1.21.1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 10 10:17:55 2022
  InstallationDate: Installed on 2019-01-02 (1315 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: dpkg
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (170 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2022-08-03T12:55:49.044540

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1984203/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Julian Andres Klode]

Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you 

[Kernel-packages] [Bug 1981975] Re: Kinetic live session fails to boot: "error: out of memory.\n\nPress any key to continue..."

[Julian Andres Klode]

*** This bug is a duplicate of bug 1842320 ***
https://bugs.launchpad.net/bugs/1842320

** This bug has been marked a duplicate of bug 1842320
   Out of Memory on boot with 5.2.0 kernel

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981975

Title:
  Kinetic live session fails to boot: "error: out of memory.\n\nPress
  any key to continue..."

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kinetic live session fails to boot on an Intel NUC 9 Extreme:

    error: out of memory.

    Press any key to continue...

  Tried so far:

  FAIL: 20220717
  FAIL: 20220706
  FAIL: 20220626

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1981975/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1981449] Re: 5.19 kernel does not load MOK keys

[Julian Andres Klode]

Here's the 5.15 log, the 5.19 one was attached by apport as
CurrentDmesg.txt already.

** Attachment added: "dmesg-5.15.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981449/+attachment/5602675/+files/dmesg-5.15.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981449

Title:
  5.19 kernel does not load MOK keys

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The 5.19 kernel only reads the db and dbx keys:

  jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity
  Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx


  The 5.15 kernel also loads the mok keys

  jak@jak-t480s:~:master$ journalctl -b -2 -k | grep integrity
  Jun 27 23:10:55 jak-t480s kernel: integrity: Platform Keyring initialized
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Canonical 
Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: ac5ed055ca0a71e3a2343dd42d5afe0cffdd3ef8'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: dc4bc63447738df295a67d455ef7ea0eb3e14945'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ci-train-ppa-service/ubuntu/4093 UEFI: 
bbfd16fec6b3ba059a0f011203a5cd493a4529b7'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jun 27 23:10:55 jak-t480s kernel: 

[Kernel-packages] [Bug 1981449] Re: 5.19 kernel does not load MOK keys

[Julian Andres Klode]

There seems to be an invalid hash presented in MokX, it fails to import
that and then doesn't load MokX (which seems reasonable). I need to
recheck with 5.15 if it still boots, maybe firmware got corrupted or
something (or 5.19 loads the key from the wrong place).

$ mokutil --list-enrolled --mokx
[key 1]
  [SHA-256]
  


$ hd /sys/firmware/efi/efivars/MokListXRT-605dab50-e046-4300-abb6-3dd810dd8b23 
  06 00 00 00 26 16 c4 c1  4c 50 92 40 ac a9 41 f9  |&...LP.@..A.|
0010  36 93 43 28 4c 00 00 00  00 00 00 00 30 00 00 00  |6.C(L...0...|
0020  50 ab 5d 60 46 e0 00 43  ab b6 3d d8 10 dd 8b 23  |P.]`F..C..=#|
0030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ||
*
0050

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981449

Title:
  5.19 kernel does not load MOK keys

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The 5.19 kernel only reads the db and dbx keys:

  jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity
  Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx


  The 5.15 kernel also loads the mok keys

  jak@jak-t480s:~:master$ journalctl -b -2 -k | grep integrity
  Jun 27 23:10:55 jak-t480s kernel: integrity: Platform Keyring initialized
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Canonical 
Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: ac5ed055ca0a71e3a2343dd42d5afe0cffdd3ef8'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: dc4bc63447738df295a67d455ef7ea0eb3e14945'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 

[Kernel-packages] [Bug 1981449] Re: 5.19 kernel does not load MOK keys

[Julian Andres Klode]

In case you wonder: Yes I have the ubuntu UEFI PPA key in db as I needed
to test out shims signed from there :)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981449

Title:
  5.19 kernel does not load MOK keys

Status in linux package in Ubuntu:
  New

Bug description:
  The 5.19 kernel only reads the db and dbx keys:

  jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity
  Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx


  The 5.15 kernel also loads the mok keys

  jak@jak-t480s:~:master$ journalctl -b -2 -k | grep integrity
  Jun 27 23:10:55 jak-t480s kernel: integrity: Platform Keyring initialized
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Canonical 
Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: ac5ed055ca0a71e3a2343dd42d5afe0cffdd3ef8'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: dc4bc63447738df295a67d455ef7ea0eb3e14945'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ci-train-ppa-service/ubuntu/4093 UEFI: 
bbfd16fec6b3ba059a0f011203a5cd493a4529b7'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 
'4845da95ac2b4c1ba5f604ff45a89d83 db: 

[Kernel-packages] [Bug 1981449] Re: 5.19 kernel does not load MOK keys

[Julian Andres Klode]

In the logs I see different values for MOKvar from efi: so maybe it's
calculating something wrongly (or it's just not that stable).

jak@jak-t480s:~:master$ journalctl -k | grep MOK -i
Jul 12 15:14:51 jak-t480s kernel: efi: TPMFinalLog=0xbb592000 SMBIOS=0xba693000 
SMBIOS 3.0=0xba69 ACPI=0xbb5fe000 ACPI 2.0=0xbb5fe014 ESRT=0xba51d000 
MEMATTR=0xb529c018 MOKvar=0xb5194000 RNG=0xba694998 TPMEventLog=0xae7e3018 
jak@jak-t480s:~:master$ journalctl -k -b -2 | grep MOK
Jun 27 23:10:55 jak-t480s kernel: efi: TPMFinalLog=0xbb592000 SMBIOS=0xba693000 
SMBIOS 3.0=0xba69 ACPI=0xbb5fe000 ACPI 2.0=0xbb5fe014 ESRT=0xba51d000 
MEMATTR=0xb529d018 MOKvar=0xb5196000 RNG=0xba694998 TPMEventLog=0xae7e4018

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981449

Title:
  5.19 kernel does not load MOK keys

Status in linux package in Ubuntu:
  New

Bug description:
  The 5.19 kernel only reads the db and dbx keys:

  jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity
  Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx


  The 5.15 kernel also loads the mok keys

  jak@jak-t480s:~:master$ journalctl -b -2 -k | grep integrity
  Jun 27 23:10:55 jak-t480s kernel: integrity: Platform Keyring initialized
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI 
CA 2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:db
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Canonical 
Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: ac5ed055ca0a71e3a2343dd42d5afe0cffdd3ef8'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: dc4bc63447738df295a67d455ef7ea0eb3e14945'
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
  Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI 

[Kernel-packages] [Bug 1981449] [NEW] 5.19 kernel does not load MOK keys

[Julian Andres Klode]

Public bug reported:

The 5.19 kernel only reads the db and dbx keys:

jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity
Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized
Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized
Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI CA 
2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
Jul 09 21:34:14 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jul 09 21:34:14 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
Jul 09 21:34:14 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx


The 5.15 kernel also loads the mok keys

jak@jak-t480s:~:master$ journalctl -b -2 -k | grep integrity
Jun 27 23:10:55 jak-t480s kernel: integrity: Platform Keyring initialized
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo Ltd.: 
ThinkPad Product CA 2012: 838b1f54c1550463f45f98700640f11069265949'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Lenovo UEFI CA 
2014: 4b91a68732eaefdd2c8c6b027ec3449e9c8f'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Microsoft 
Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: UEFI:db
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
Jun 27 23:10:55 jak-t480s kernel: integrity: Revoking X.509 certificate: 
UEFI:dbx
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'Canonical Ltd. 
Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: ac5ed055ca0a71e3a2343dd42d5afe0cffdd3ef8'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'jak-t480s 
Secure Boot Module Signature key: dc4bc63447738df295a67d455ef7ea0eb3e14945'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ci-train-ppa-service/ubuntu/4093 UEFI: 
bbfd16fec6b3ba059a0f011203a5cd493a4529b7'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 'UEFI key for 
~ubuntu-uefi-team/ubuntu/ppa UEFI: 131b868222e85383c2e71ae489372ffac6ce29ed'
Jun 27 23:10:55 jak-t480s kernel: integrity: Loading X.509 certificate: 
UEFI:MokListRT (MOKvar table)
Jun 27 23:10:55 jak-t480s kernel: integrity: Loaded X.509 cert 
'4845da95ac2b4c1ba5f604ff45a89d83 db: 34c5d6debab4133cf0b663f5799e580f31f594c1'

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-9-generic 5.19.0-9.9
ProcVersionSignature: Ubuntu 5.19.0-9.9-generic 5.19.0-rc5
Uname: Linux 5.19.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jak3308 F wireplumber
 /dev/snd/controlC1:  jak

[Kernel-packages] [Bug 1975388] Re: upgrade from 18.04 to 20.04 while on rollbacked kernel 4.15-0-177 - package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: installed grub

[Julian Andres Klode]

You didn't remove all the 177 packages, the headers package or so pulls
in a kernel and then apt switches to the unsigned one.

I'm going to reassign this to Linux, as we should ensure that doesn't
happen by not allowing unsigned to satisfy those dependencies.

** Package changed: grub2-signed (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: Invalid => New

** Summary changed:

- upgrade from 18.04 to 20.04 while on rollbacked kernel 4.15-0-177 - package 
grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to install/upgrade: 
installed grub-efi-amd64-signed package post-installation script subprocess 
returned error exit status 1
+ Removing signed kernel installs unsigned one due to dependencies

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1975388

Title:
  Removing signed kernel installs unsigned one due to dependencies

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dell XPS 15 9570. Dual boot with Windows 10. Linux was on 18.04 when
  attempting to upgrade to 20.04. Had previously installed kernel
  4.15-0-177 which was rolled back to working kernel 4.15-0-175 due to
  issues already reported in Bug #1973482. Due to rollback, there was an
  unsigned image of kernel 4.15-0-177 in the machine, which caused the
  upgrade 20.04 to fail with following error. Ubuntu upgrade attempted
  while logged into kernel 4.15-0-175.

  package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2
  ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
  Uname: Linux 5.4.0-110-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat May 21 12:24:34 2022
  ErrorMessage: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-09-23 (1336 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.8
  SourcePackage: grub2-signed
  Title: package grub-efi-amd64-signed 1.167.2+2.04-1ubuntu44.2 failed to 
install/upgrade: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2022-05-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975388/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1969841] Re: grub-efi-amd64: grub-efi/install_devices depends on the value of LC_COLLATE/LANG

[Julian Andres Klode]

** Package changed: linux-meta (Ubuntu) => grub2 (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1969841

Title:
  grub-efi-amd64: grub-efi/install_devices depends on the value of
  LC_COLLATE/LANG

Status in grub2 package in Ubuntu:
  New

Bug description:
  Hi,
  As discussed with Julian Andres Klode on IRC, there are cases where the value 
of grub-efi/install_devices is affected by the value of LC_COLLATE.

  This is caused by this unique sort: https://git.launchpad.net/~ubuntu-
  core-dev/grub/+git/ubuntu/tree/debian/grub-multi-
  install?h=debian/2.06-2ubuntu7#n220

  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  From what I see, this can only happen on systems with NVMe drives:

  # find -L /dev/disk/by-id/ -samefile /dev/nvme0n1p1
  /dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1
  /dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1

  Let's assume grub-efi/install_devices has the following value:

  # debconf-show grub-efi-amd64 | grep grub-efi/install_devices:
  * grub-efi/install_devices: 
/dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, 
/dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1

  This was obtained with this LANG/LC_COLLATE:
  # echo $LANG
  C.UTF-8
  # dpkg-reconfigure grub-efi-amd64
  │ GRUB EFI system partitions: 
   │
  │ 
   │
  │[*] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 
SDAQNTW-512G-2000  │
  │[*] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 
SDAQNTW-512G-2000   │
  # debconf-show grub-efi-amd64 | grep grub-efi/install_devices:
  * grub-efi/install_devices: 
/dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1, 
/dev/disk/by-id/nvme-WDC_CL_SN720_SDAQNTW-512G-2000_-part1

  We can see that the boxes are properly ticked here.

  However:
  # export LANG=en_US.UTF-8; dpkg-reconfigure grub-efi-amd64
  │ GRUB EFI system partitions: 
│
  │ 
│
  │[ ] /dev/nvme1n1p1 (535 MB; /boot/efi) on 512110 MB WDC CL SN720 
SDAQNTW-512G-2000   │
  │[ ] /dev/nvme0n1p1 (535 MB; ) on 512110 MB WDC CL SN720 
SDAQNTW-512G-2000│

  The boxes are not ticked, if I tick them, I get the following:

  # debconf-show grub-efi-amd64 | grep grub-efi/install_devices:
  * grub-efi/install_devices: 
/dev/disk/by-id/nvme-eui.e8238fa6bf530001001b444-part1, 
/dev/disk/by-id/nvme-eui.e8238fa6bf530001001b4466-part1

  I assume the postinst script for grub-pc exhibits the same bug with
  the value of grub-pc/install_devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1969841/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

[Julian Andres Klode]

** No longer affects: grub2-unsigned (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

[Julian Andres Klode]

Though maybe you also need to unapply efi-implemented-LoadFile2-initrd-
loading-protocol-fo.patch

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

[Julian Andres Klode]

To figure out if it's the new loader code, remove efi-implement-
grub_efi_run_image.patch (or the grub-core/loader/efi/linux.c hunk) or
enable secure boot (if available). The new code path on insecure systems
uses the upstream loader + LoadFile2 support, as is necessary for
RISC-V.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1962471] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

Ping! Releasing with broken WiFi after suspend & resume, with patches
lying around for over a month, feels like a disservice to our users.

** Tags added: rls-jj-incoming

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Status: Confirmed => Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962471

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine,
  but I don't know at which point precisely it broke - with 5.15
  perhaps? Laptop was running 24/7 mostly in the office, not a lot of
  suspend in there.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962471/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1962471] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

Will we see these fixes cherry-picked in a 5.15.0-24 kernel or so soon?
The linux-firmware package has been ready for a while now with the new
firmware

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962471

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine,
  but I don't know at which point precisely it broke - with 5.15
  perhaps? Laptop was running 24/7 mostly in the office, not a lot of
  suspend in there.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962471/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1964626] Re: Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

[Julian Andres Klode]

** Package changed: grub2 (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964626

Title:
  Unable to launch 5.15.0-22-generic kernel (or its recovery mode)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have been running a build of 22.04 Jammy-Daily (amd64 Desktop) for a couple 
of weeks and just updating and upgrading using apt.
  When restarting the VM (VirtualBox), I get the screen in the screenshot 
below. The same thing happens if I select the 5.15.0-22-generic options - 
normal or recovery mode - from the grub list in advanced options.
  I can boot into 5.15.0-18-generic with no issues.

  I have attempted to run upgrade-grub to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: grub2 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 11 18:17:17 2022
  InstallationDate: Installed on 2022-02-26 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964626/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1962471] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

Hi, this works, yes. Thanks!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962471

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine,
  but I don't know at which point precisely it broke - with 5.15
  perhaps? Laptop was running 24/7 mostly in the office, not a lot of
  suspend in there.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962471/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1962472] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

*** This bug is a duplicate of bug 1962471 ***
https://bugs.launchpad.net/bugs/1962471

** This bug has been marked a duplicate of bug 1962471
   iwlwifi fails after suspend (Failed to start RT ucode: -110)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962472

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962472/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1962471] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

** Description changed:

  See attachments.
  
- This is a regression from earlier kernel versions which worked fine.
+ This is a regression from earlier kernel versions which worked fine, but
+ I don't know at which point precisely it broke - with 5.15 perhaps?
+ Laptop was running 24/7 mostly in the office, not a lot of suspend in
+ there.
  
  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  jak7915 F wireplumber
-  /dev/snd/seq:jak7907 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jak7915 F wireplumber
+  /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-22-generic N/A
-  linux-backports-modules-5.15.0-22-generic  N/A
-  linux-firmware 20220217.git6342082c-0ubuntu3
+  linux-restricted-modules-5.15.0-22-generic N/A
+  linux-backports-modules-5.15.0-22-generic  N/A
+  linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962471

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine,
  but I don't know at which point precisely it broke - with 5.15
  perhaps? Laptop was running 24/7 mostly in the office, not a lot of
  suspend in there.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Kernel-packages] [Bug 1962471] [NEW] iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

Public bug reported:

See attachments.

This is a regression from earlier kernel versions which worked fine.

It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
concrete product number)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-22-generic 5.15.0-22.22
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jak7915 F wireplumber
 /dev/snd/seq:jak7907 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Feb 28 13:44:03 2022
HibernationDevice: RESUME=none
InstallationDate: Installed on 2018-03-14 (1446 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-22-generic N/A
 linux-backports-modules-5.15.0-22-generic  N/A
 linux-firmware 20220217.git6342082c-0ubuntu3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2021
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET70W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy package-from-proposed third-party-packages

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962471

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  New

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  

[Kernel-packages] [Bug 1962472] Re: iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

Dmesg with failure

** Attachment added: "LastBoot.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962472/+attachment/5564171/+files/LastBoot.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962472

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  New

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962472/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1962472] [NEW] iwlwifi fails after suspend (Failed to start RT ucode: -110)

[Julian Andres Klode]

Public bug reported:

See attachments.

This is a regression from earlier kernel versions which worked fine.

It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
concrete product number)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-22-generic 5.15.0-22.22
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jak7915 F wireplumber
 /dev/snd/seq:jak7907 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Feb 28 13:44:03 2022
HibernationDevice: RESUME=none
InstallationDate: Installed on 2018-03-14 (1446 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-22-generic N/A
 linux-backports-modules-5.15.0-22-generic  N/A
 linux-firmware 20220217.git6342082c-0ubuntu3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2021
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET70W (1.47 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy package-from-proposed third-party-packages

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962472

Title:
  iwlwifi fails after suspend (Failed to start RT ucode: -110)

Status in linux package in Ubuntu:
  New

Bug description:
  See attachments.

  This is a regression from earlier kernel versions which worked fine.

  It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
  concrete product number)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak7915 F wireplumber
   /dev/snd/seq:jak7907 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Mon Feb 28 13:44:03 2022
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1446 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET70W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET70W(1.47):bd08/11/2021:br1.47:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  

[Kernel-packages] [Bug 1954692] Re: Reconsider compressed kernels on arm64

[Julian Andres Klode]

My side question is what prevents arm64 from having the amd64 approach
where AFAIUI the image is compressed but starts with a small stub that
decompresses it.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954692

Title:
  Reconsider compressed kernels on arm64

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Compressed kernel images were introduced in bug 1384955 to work around
  some limits on old u-boot systems. This in turn broke grub-check-
  signatures, meaning that while cloud images booted in secure boot, you
  could not upgrade grub or install new kernels on secure systems as
  that would trigger a "you have unsigned kernels" message. grub 2.06
  also fails to boot the images, as it verifies before decompressing.

  Work to fix grub to handle such images on arm64 for backward
  compatibility is tracked in bug 1954683. This bug is to reconsider
  whether the change is still necessary or could be removed in 22.04
  such that we can have proper UEFI executables again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954692/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1954692] [NEW] Reconsider compressed kernels on arm64

[Julian Andres Klode]

Public bug reported:

Compressed kernel images were introduced in bug 1384955 to work around
some limits on old u-boot systems. This in turn broke grub-check-
signatures, meaning that while cloud images booted in secure boot, you
could not upgrade grub or install new kernels on secure systems as that
would trigger a "you have unsigned kernels" message. grub 2.06 also
fails to boot the images, as it verifies before decompressing.

Work to fix grub to handle such images on arm64 for backward
compatibility is tracked in bug 1954683. This bug is to reconsider
whether the change is still necessary or could be removed in 22.04 such
that we can have proper UEFI executables again.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Changed in: linux (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954692

Title:
  Reconsider compressed kernels on arm64

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Compressed kernel images were introduced in bug 1384955 to work around
  some limits on old u-boot systems. This in turn broke grub-check-
  signatures, meaning that while cloud images booted in secure boot, you
  could not upgrade grub or install new kernels on secure systems as
  that would trigger a "you have unsigned kernels" message. grub 2.06
  also fails to boot the images, as it verifies before decompressing.

  Work to fix grub to handle such images on arm64 for backward
  compatibility is tracked in bug 1954683. This bug is to reconsider
  whether the change is still necessary or could be removed in 22.04
  such that we can have proper UEFI executables again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954692/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1947460] [NEW] T480s failure to suspend

[Julian Andres Klode]

Public bug reported:

system failed to suspend, see attached logs

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-19-generic 5.13.0-19.19
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jak3615 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 16 19:19:23 2021
HibernationDevice: RESUME=none
InstallationDate: Installed on 2018-03-14 (1311 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-19-generic N/A
 linux-backports-modules-5.13.0-19-generic  N/A
 linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2021
dmi.bios.release: 1.45
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET68W (1.45 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET68W(1.45):bd05/06/2021:br1.45:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug impish third-party-packages

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1947460

Title:
  T480s failure to suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  system failed to suspend, see attached logs

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jak3615 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sat Oct 16 19:19:23 2021
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2018-03-14 (1311 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  MachineType: LENOVO 20L8S02D00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2021
  dmi.bios.release: 1.45
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET68W (1.45 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L8S02D00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET68W(1.45):bd05/06/2021:br1.45:efr1.22:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:skuLENOVO_MT_20L8_BU_Think_FM_ThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L8S02D00
  dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947460/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1943758] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: il sottoprocesso installato pacchetto shim-signed script post-installation ha restituito lo stat

[Julian Andres Klode]

Various dkms weirdness

"Error! The module acpi-call 1.1.0 is not currently installed."

But there are also like 3 services failing to start in the log, so maybe
the system is just misconfigured somewhere that affects all of them.

The bug also indicates that EFI variables are not supported by the
firmware, so I'm not sure fixing the underlying issues would result in a
working system.

** Package changed: shim-signed (Ubuntu) => dkms (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1943758

Title:
  package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: il
  sottoprocesso installato pacchetto shim-signed script post-
  installation ha restituito lo stato di errore 7

Status in dkms package in Ubuntu:
  New

Bug description:
  Whi?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: shim-signed 1.40.7+15.4-0ubuntu9
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 15 21:08:45 2021
  EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI 
variables are not supported on this system.
  ErrorMessage: il sottoprocesso installato pacchetto shim-signed script 
post-installation ha restituito lo stato di errore 7
  InstallationDate: Installed on 2021-09-08 (6 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Missing: /boot/efi/EFI/ubuntu directory is missing
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: shim-signed
  Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: il 
sottoprocesso installato pacchetto shim-signed script post-installation ha 
restituito lo stato di errore 7
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1943758/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1941963] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock

[Julian Andres Klode]

** Package changed: shim-signed (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1941963

Title:
  package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade:
  kernel segfault. Hard lock

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu-Studio 20.04.3 LTS on MacPro 5,1, dual W3520
  From /proc/version: Linux version 5.11.0-27-lowlatency 
(buildd@lcy01-amd64-019) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP PREEMPT Wed Aug 11 17:06:56 
UTC 2021

  # apt-cache policy shim-signed
  shim-signed:
Installed: 1.40.7+15.4-0ubuntu9
Candidate: 1.40.7+15.4-0ubuntu9
Version table:
   *** 1.40.7+15.4-0ubuntu9 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.40.3+15+1533136590.3beb971-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  >What you expected to happen

  Running `apt upgrade` would complete without issue.

  >What happened instead

  System hard lock, becomes completely unresponsive both from the local
  terminal and over established SSH. Eventually memory is exhausted and
  the machine reboots.

  Upon restart, running `apt upgrade` returns the error: "E: dpkg was
  interrupted, you must manually run 'dpkg --configure -a' to correct
  the problem."

  Running `dpkg --configure -a` attempts to complete installation of
  shim-signed, segfaults, requiring a cold boot.

  Only a fraction of the errors generated get written to the logs before
  the crash as the crash prevents a final flush to disk. From a remote
  machine I tailed several logs and triggered the crash again, then
  copied the results from the terminal and attached to report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941963/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1938163] Re: package shim-signed 1.50+15.4-0ubuntu7 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

[Julian Andres Klode]

There are three possible causes

- firmware bug
- kernel bug
- user error (read-only variables), though why does that give I/O rather than 
ENOSPACE

I'm going to reassign this one to linux for a check on the kernel side,
but I suspect it's a firmware issue.

** Package changed: shim-signed (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1938163

Title:
  package shim-signed 1.50+15.4-0ubuntu7 failed to install/upgrade:
  installed shim-signed package post-installation script subprocess
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  idk dude it just popped up at the end of ubuntu's installation

  ProblemType: Package
  DistroRelease: Ubuntu 21.04
  Package: shim-signed 1.50+15.4-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] Нет такого файла или 
каталога: '/proc/sys/kernel/moksbstate_disabled'
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootEFIContents:
   BOOTX64.CSV
   grub.cfg
   grubx64.efi
   mmx64.efi
   shimx64.efi
  CasperMD5CheckResult: pass
  Date: Tue Jul 27 13:11:57 2021
  EFITables:
   июл 27 15:59:33 ilya-Q2542N kernel: efi: EFI v2.31 by American Megatrends
   июл 27 15:59:33 ilya-Q2542N kernel: efi: ACPI 2.0=0xc98a5000 ACPI=0xc98a5000 
SMBIOS=0xca867418 MOKvar=0xc8107000 
   июл 27 15:59:33 ilya-Q2542N kernel: secureboot: Secure boot disabled
   июл 27 15:59:33 ilya-Q2542N kernel: secureboot: Secure boot disabled
  ErrorMessage: installed shim-signed package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-07-27 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu1
   apt  2.2.4ubuntu0.1
  SecureBoot: 22   0   0   0   0
  SourcePackage: shim-signed
  Title: package shim-signed 1.50+15.4-0ubuntu7 failed to install/upgrade: 
installed shim-signed package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938163/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1938699] Re: cpu-checker: riscv64 build missing

[Julian Andres Klode]

cpu-checker (0.7-1.2) experimental; urgency=medium


will be synced shortly with those changes

** Changed in: cpu-checker (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to cpu-checker in Ubuntu.
https://bugs.launchpad.net/bugs/1938699

Title:
  cpu-checker: riscv64 build missing

Status in cpu-checker package in Ubuntu:
  Fix Committed

Bug description:
  cpu-checker builds fine for RISC-V once architecture riscv64 is added to 
debian/control.
  A patch for kvm-ok is needed to add a /dev/kvm check for the RISC-V 
architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1938699/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Julian Andres Klode]

Yes, of course if you don't install the fixed version you still have the
broken one.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Julian Andres Klode]

Marking the packaging tags as invalid, as the bug is fixed in apt 2.0.4
which is in the 20.04.2 images. This bug was tracked as bug 1871268 back
when it was being fixed.

** Changed in: apt (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Julian Andres Klode]

I mean 2.0.4, of course, which is included in the current LTS images
(20.04.2); your image is the previous version (20.04.1)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

[Julian Andres Klode]

It seems you are not using libapt-pkg6.0 in version 2.1.10ubuntu0.2 or
later? This issue was fixed in that version.

** Changed in: apt (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150

Title:
  unexpected error pop-up after 'apt install nvidia-driver-455'

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-455 package in Ubuntu:
  New

Bug description:
  Ubuntu info:

  $ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS (fossa-spark-cml X52)
  Release 20.04

  Full reproduce step

  1. nvidia-driver-455 455.45.01-0ubuntu0.20.04.1 is installed in the first 
place, without all i386 pkg installed.
  2. run update-manager to do upgrade.
  3. it will show error after download deb and didn't upgrade anything.

  Per test with the command to do the upgrade, it will have an extra
  error message, but it will just upgrade and install recommended i386
  debs.

  The error msgs are:

  E: Could not configure 'libc6:i386'.
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  Short way to get the error:
  # apt-get install libgcc-s1:i386 --dry-run
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
apt-clone archdetect-deb dctrl-tools dmraid gir1.2-timezonemap-1.0 
gir1.2-xkl-1.0 kpartx kpartx-boot libdebian-installer4 libdmraid1.0.0.rc16
libtimezonemap-data libtimezonemap1 python3-icu python3-pam rdate
  Use 'apt autoremove' to remove them.
  The following additional packages will be installed:
gcc-10-base:i386 libc6 libc6:i386 libcrypt1:i386 libidn2-0:i386 
libunistring2:i386
  Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
  The following NEW packages will be installed:
gcc-10-base:i386 libc6:i386 libcrypt1:i386 libgcc-s1:i386 libidn2-0:i386 
libunistring2:i386
  The following packages will be upgraded:
libc6
  1 upgraded, 6 newly installed, 0 to remove and 235 not upgraded.
  Inst libc6 [2.31-0ubuntu9.1] (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates 
[amd64])
  Inst libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386]) []
  Conf libc6 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [amd64]) []
  Inst libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Conf gcc-10-base:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386]) []
  Inst libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libgcc-s1:i386 (10.2.0-5ubuntu1~20.04 Ubuntu:20.04/focal-updates, 
Ubuntu:20.04/focal-security [i386])
  Conf libcrypt1:i386 (1:4.4.10-10ubuntu4 Ubuntu:20.04/focal [i386])
  Conf libc6:i386 (2.31-0ubuntu9.2 Ubuntu:20.04/focal-updates [i386])
  Inst libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Inst libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  Conf libunistring2:i386 (0.9.10-2 Ubuntu:20.04/focal [i386])
  Conf libidn2-0:i386 (2.2.0-2 Ubuntu:20.04/focal [i386])
  E: Could not configure 'libc6:i386'. 
  E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  For now, we think the above Error is the root cause of update-manager
  failure.

  ---

  This happens as upgrade package nvidia-driver-455 from
  455.45.01-0ubuntu0.20.04.1 to 460.39-0ubuntu0.20.04.1.

  for more detail, please check the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1923150/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp