[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default

[Joao Andre Simioni]

Discussing this internally, it was suggested to use:

fbcon=map:X

With X = 0, I see the same behavior (boot process on the BMC, X on
whatever is set)

And other values for X just blank the boot process on both outputs (BMC
and HDMI).

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

Title:
  Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
  default

Status in linux-nvidia package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
  New

Bug description:
  The DGX Station A10 has various display options. The BMC provides an
  emulated device (Aspeed controller), a physical BMC controller (NVIDIA
  Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
  outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.

  In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
  on the A100 DisplayPort output.

  NVIDIA DGX OS - a derivative of Ubuntu - works around this by
  installing a service that generates an xorg config file dynamically
  based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
  I'll attach samples of those files here. Replacing the default Ubuntu
  xorg.conf file with the sample xorg-nvidia.conf file on a default
  Ubuntu Desktop install is confirmed to enable output.

  [*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
  started-station-a100.html

  (Note: split from bug 2031367)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2033418/+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 2038582] Re: Turning COMPAT_32BIT_TIME off on arm64

[Joao Andre Simioni]

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

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

Title:
  Turning COMPAT_32BIT_TIME off on arm64

Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  New
Status in linux-azure package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-ibm package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New

Bug description:
  This will prevent existing armhf binaries to operate correctly, if
  they are still using 32bit time.

  24.04 LTS is likely to be used for 10 years. And if allowed to overrun
  and remain active in the field in 2038 can lead to catastrophic
  failure in the field due to these syscalls enabled and used.

  I would like to request if we can turn off COMPAT_32BIT_TIME on every
  architecture, thus this will be arch by arch bug report, and arch by
  arch decision.

  This needs to be a per-arch decision, potentially taking into
  consideration bi-arch userspace support.

  config COMPAT_32BIT_TIME
   bool "Provide system calls for 32-bit time_t"
   default !64BIT || COMPAT
   help
 This enables 32 bit time_t support in addition to 64 bit time_t support.
 This is relevant on all 32-bit architectures, and 64-bit architectures
 as part of compat syscall handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038582/+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 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

** Attachment added: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+attachment/5682135/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

Daniel, I have the impression that apport-cli did something wrong here,
so I'm attaching the .crash files. At first it complained that linux-
hwe-5.19 was not installed, so I ran it with the -p gnome-shell option.
Not sure if it picked the already generated file or tried to kill it
again.


** Attachment added: "_usr_lib_xorg_Xorg.0.crash"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+attachment/5682134/+files/_usr_lib_xorg_Xorg.0.crash

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] ProcCpuinfo.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682133/+files/ProcCpuinfo.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] DpkgLog.txt

[Joao Andre Simioni]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682132/+files/DpkgLog.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] Dependencies.txt

[Joao Andre Simioni]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682131/+files/Dependencies.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] BootLog.txt

[Joao Andre Simioni]

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682129/+files/BootLog.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] ProcEnviron.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682127/+files/ProcEnviron.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] ShellJournal.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682128/+files/ShellJournal.txt

** Tags added: ubuntu

** Description changed:

  [Description]
  
  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested with
  5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.
  
  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around 10
  seconds).
  
  [Workaround]
  
  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.4
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ DistUpgraded: Fresh install
+ DistroCodename: jammy
+ DistroRelease: Ubuntu 22.04
+ DistroVariant: ubuntu
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  
+ InstallationDate: Installed on 2023-06-20 (6 days ago)
+ InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
+ Lspci:
+  
+ Lspci-vt: -[:00]-
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: Microsoft Corporation Virtual Machine
+ Package: xorg 1:7.7+23ubuntu2
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
+ Tags:  jammy ubuntu
+ Uname: Linux 5.19.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 11/26/2012
+ dmi.bios.release: 1.0
+ dmi.bios.vendor: Microsoft Corporation
+ dmi.bios.version: Hyper-V UEFI Release v1.0
+ dmi.board.asset.tag: None
+ dmi.board.name: Virtual Machine
+ dmi.board.vendor: Microsoft Corporation
+ dmi.board.version: Hyper-V UEFI Release v1.0
+ dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Microsoft Corporation
+ dmi.chassis.version: Hyper-V UEFI Release v1.0
+ dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
+ dmi.product.family: Virtual Machine
+ dmi.product.name: Virtual Machine
+ dmi.product.sku: None
+ dmi.product.version: Hyper-V UEFI Release v1.0
+ dmi.sys.vendor: Microsoft Corporation
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
+ version.libgl1-mesa-glx: libgl1-mesa-glx N/A
+ version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy 

[Kernel-packages] [Bug 2024598] CurrentDmesg.txt

[Joao Andre Simioni]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682130/+files/CurrentDmesg.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] ProcCpuinfoMinimal.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682126/+files/ProcCpuinfoMinimal.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

apport information

** Tags added: apport-collected

** Description changed:

  [Description]
  
  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested with
  5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.
  
  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around 10
  seconds).
  
  [Workaround]
  
- Switching back to the LTS Kernel (5.15) brings the system back to normal
- operation.
+ Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.4
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ GsettingsChanges:
+  
+ InstallationDate: Installed on 2023-06-20 (6 days ago)
+ InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
+ Package: gnome-shell 42.5-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
+ RelatedPackageVersions: mutter-common 42.5-0ubuntu1
+ Tags:  jammy
+ Uname: Linux 5.19.0-42-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2024598/+attachment/5682125/+files/Dependencies.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  Confirmed

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to normal 
operation.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Package: gnome-shell 42.5-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2023-06-20 (6 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lspci:
   
  Lspci-vt: -[:00]-
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg 1:7.7+23ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-42-generic 
root=UUID=194597a3-7adc-445c-978b-d1db2026d95a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Tags:  jammy ubuntu
  Uname: Linux 5.19.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/26/2012
  dmi.bios.release: 1.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 7287-2454-0075-8144-0704-7909-41
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:br1.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  

[Kernel-packages] [Bug 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

This sos report was generated right after collecting the journal-42.txt
log files.

** Attachment added: 
"sosreport-jasimioni-Virtual-Machine-2023-06-23-xumdlzs.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+attachment/5681666/+files/sosreport-jasimioni-Virtual-Machine-2023-06-23-xumdlzs.tar.xz

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to
  normal operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

** Attachment added: "journal-41.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+attachment/5681664/+files/journal-41.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to
  normal operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

** Attachment added: "journal-42.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+attachment/5681665/+files/journal-42.txt

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to
  normal operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

I was not able to reproduce the error with the 5.19 mainline kernels.
But I tracked the available Jammy kernels, and the problem starts in:

linux-image-5.19.0-42-generic

I don't see the issue with the -41-generic

Does this help? Let me know if I can provide additional info here.

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to
  normal operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2024598] Re: On a successful login the GUI session freezes after a few seconds when using hwe kernel

[Joao Andre Simioni]

Hi Daniel,

There are no crashes, and we don't see the UI crashing, only freezing.
If switching to tty1 and back to tty2, the session continues at the same
point it was before, for around ten seconds, and then it's frozen again.

This is the logs that show up when doing that switching:
https://pastebin.ubuntu.com/p/wdHV3mcbhW/

I'll check which kernel introduces the error and post the outcome.

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

Title:
  On a successful login the GUI session freezes after a few seconds when
  using hwe kernel

Status in linux-hwe-5.19 package in Ubuntu:
  New

Bug description:
  [Description]

  Running a Jammy Desktop inside Hyper-V, with the hwe kernel (tested
  with 5.19 and 6.2), around 10 seconds after a successful login, the UI
  freezes.

  If switching tty to tty1 using CTRL + ALT + F1 and returning to tty2
  using CTRL + ALT + F2 the UI responds again, for a short time (around
  10 seconds).

  [Workaround]

  Switching back to the LTS Kernel (5.15) brings the system back to
  normal operation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2024598/+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 2002427] WifiSyslog.txt

[Joao Andre Simioni]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640540/+files/WifiSyslog.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] acpidump.txt

[Joao Andre Simioni]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640541/+files/acpidump.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] UdevDb.txt

[Joao Andre Simioni]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2002427/+attachment/5640539/+files/UdevDb.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] ProcModules.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640538/+files/ProcModules.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] ProcCpuinfo.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640535/+files/ProcCpuinfo.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] ProcCpuinfoMinimal.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640536/+files/ProcCpuinfoMinimal.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] Lsusb-v.txt

[Joao Andre Simioni]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640534/+files/Lsusb-v.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] ProcInterrupts.txt

[Joao Andre Simioni]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640537/+files/ProcInterrupts.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] Lspci-vt.txt

[Joao Andre Simioni]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2002427/+attachment/5640533/+files/Lspci-vt.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] Lspci.txt

[Joao Andre Simioni]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2002427/+attachment/5640532/+files/Lspci.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/2002427

Title:
  Subiquity segfault in ARM64 with -64k Kernel

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

Bug description:
  [Problem Description]

  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message

  [Additional Info]

  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-
  info works fine. Both python3.8 and wget are statically compiled,
  while ubuntu-distro-info is not.

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable

  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)

  The same VM, using the non -64k kernel works:

  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works

  Tried other kernels (5.17, 5.19) with the same error.

  [Reproducer]

  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole

  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569

  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux

  4. Install subiquity
  sudo snap install subiquity

  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
   crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
  MachineType: QEMU QEMU Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 2002427] Re: Subiquity segfault in ARM64 with -64k Kernel

[Joao Andre Simioni]

apport information

** Tags added: apport-collected jammy uec-images

** Description changed:

  [Problem Description]
  
  Subiquity fails to execute when running on ARM64 with -64k Kernel. It
  exits with the "Segmentation fault" message
  
  [Additional Info]
  
  The problem seems to be with python3.8 binary in the snap. The same
  problem occurs with wget binary in the same snap, but ubuntu-distro-info
  works fine. Both python3.8 and wget are statically compiled, while
  ubuntu-distro-info is not.
  
  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/python3.8
  /snap/subiquity/4236/usr/bin/python3.8: ELF 64-bit LSB executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=bad3f5d001ec1e2ec539f16d8f6729a06cdd68df, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/python3.8
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/python3.8
not a dynamic executable
  
  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/wget
  /snap/subiquity/4236/usr/bin/wget: ELF 64-bit LSB pie executable, ARM 
aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=0f2234825d67c22b6b320139445759f6662aa01e, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/wget
  Segmentation fault
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/wget
not a dynamic executable
  
  root@jammy-arm:~# file /snap/subiquity/4236/usr/bin/ubuntu-distro-info 
  /snap/subiquity/4236/usr/bin/ubuntu-distro-info: ELF 64-bit LSB pie 
executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter 
/snap/core20/current/lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, 
BuildID[sha1]=5d8c4c52d7ce614024eba1ba9069e48ad4192508, stripped
  root@jammy-arm:~# /snap/subiquity/4236/usr/bin/ubuntu-distro-info
  ubuntu-distro-info: You have to select exactly one of --all, --devel, 
--latest, --lts, --stable, --supported, --supported-esm, --series, 
--unsupported.
  root@jammy-arm:~# ldd /snap/subiquity/4236/usr/bin/ubuntu-distro-info
linux-vdso.so.1 (0xfffe7227)
libc.so.6 => /snap/core20/current/lib/aarch64-linux-gnu/libc.so.6 
(0xfffe720b)
/snap/core20/current/lib/ld-linux-aarch64.so.1 => 
/lib/ld-linux-aarch64.so.1 (0xfffe7228)
  
  The same VM, using the non -64k kernel works:
  
  # uname -a
  Linux jammy-arm 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 12:56:31 UTC 2022 
aarch64 aarch64 aarch64 GNU/Linux
  # /snap/subiquity/4236/usr/bin/python3.8 -c "print('Works')"
  Works
  
  Tried other kernels (5.17, 5.19) with the same error.
  
  [Reproducer]
  
  1. Run a VM in ARM64 architecture:
  virt-install --arch aarch64 --boot uefi --osinfo detect=on,require=off --name 
jammy-arm --memory 8096 --vcpus 4 
--disk=jammy-server-cloudimg-arm64.img,bus=virtio 
--disk=jammy-arm-seed.qcow2,bus=virtio --network network=default,model=virtio 
--boot hd --noautoconsole
  
  2. Connect to the VM and install a -64k kernel
  
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/23546569
  
  3. Reboot in the kernel (I disabled secure boot)
  # uname -a
  Linux jammy-arm 5.15.0-27-generic-64k #28-Ubuntu SMP Thu Apr 14 19:01:31 UTC 
2022 aarch64 aarch64 aarch64 GNU/Linux
  
  4. Install subiquity
  sudo snap install subiquity
  
  5. Try to run it
  # /snap/bin/subiquity
  Segmentation fault
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jan 10 18:24 seq
+  crw-rw 1 root audio 116, 33 Jan 10 18:24 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu82.3
+ Architecture: arm64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Lsusb-t:
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
+ MachineType: QEMU QEMU Virtual Machine
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic-64k 
root=UUID=a6c92eea-e1ae-4ec4-9fbc-69e3ab11d0f7 ro console=tty1 console=ttyS0
+ ProcVersionSignature: Ubuntu 5.15.0-27.28-generic-64k 5.15.30
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-27-generic-64k N/A
+  linux-backports-modules-5.15.0-27-generic-64k  N/A
+  linux-firmware

[Kernel-packages] [Bug 1984115] [NEW] nvidia-driver-XXX-server and nvidia-driver-5XX fail to install if nvidia-driver-470 is installed

[Joao Andre Simioni]

Public bug reported:

[Impact]

After installing nvidia-driver-450, apt fails to install any of the following:
  - nvidia-driver-450-server
  - nvidia-driver-470-server
  - nvidia-driver-510-server
  - nvidia-driver-515-server
  - nvidia-driver-510
  - nvidia-driver-515

[Platforms]

  - Bionic (ubuntu 18.04)
  - Focal  (ubuntu 20.04)

[Test case]

# dpkg -l | grep nvidia-driver
ii  nvidia-driver-450460.91.03-0ubuntu0.20.04.1
amd64Transitional package for nvidia-driver-460
ii  nvidia-driver-460470.141.03-0ubuntu0.20.04.1   
amd64Transitional package for nvidia-driver-470
ii  nvidia-driver-470470.141.03-0ubuntu0.20.04.1   
amd64NVIDIA driver metapackage

# apt install nvidia-driver-450-server
Reading package lists... Done
Building dependency tree   
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:
 nvidia-driver-450-server : Depends: libnvidia-gl-450-server (= 
450.203.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-extra-450-server (= 
450.203.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-decode-450-server (= 
450.203.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-encode-450-server (= 
450.203.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: xserver-xorg-video-nvidia-450-server (= 
450.203.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-cfg1-450-server (= 
450.203.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-ifr1-450-server (= 
450.203.03-0ubuntu0.20.04.1) but it is not going to be installed
Recommends: libnvidia-compute-450-server:i386 (= 
450.203.03-0ubuntu0.20.04.1) but it is not installable
Recommends: libnvidia-decode-450-server:i386 (= 
450.203.03-0ubuntu0.20.04.1) but it is not installable
Recommends: libnvidia-encode-450-server:i386 (= 
450.203.03-0ubuntu0.20.04.1) but it is not installable
Recommends: libnvidia-ifr1-450-server:i386 (= 
450.203.03-0ubuntu0.20.04.1) but it is not installable
Recommends: libnvidia-fbc1-450-server:i386 (= 
450.203.03-0ubuntu0.20.04.1) but it is not installable
Recommends: libnvidia-gl-450-server:i386 (= 
450.203.03-0ubuntu0.20.04.1) but it is not installable
E: Unable to correct problems, you have held broken packages.

# apt install nvidia-driver-470-server
Reading package lists... Done
Building dependency tree   
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:
 nvidia-driver-470-server : Depends: libnvidia-gl-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: nvidia-compute-utils-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-decode-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-encode-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: xserver-xorg-video-nvidia-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-cfg1-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-ifr1-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Depends: libnvidia-fbc1-470-server (= 
470.141.03-0ubuntu0.20.04.1) but it is not going to be installed
Recommends: libnvidia-compute-470-server:i386 (= 
470.141.03-0ubuntu0.20.04.1) but it is not installable
Recommends: libnvidia-decode-470-server:i386 (= 
470.141.03-0ubuntu0.20.04.1) but it is not installable
Recommends: libnvidia-encode-470-server:i386 (= 
470.141.03-0ubuntu0.20.04.1) but it is not installable