[Kernel-packages] [Bug 1992723] Re: Enable DP tunneling functionality on AMD Pink Sardine

[You-Sheng Yang]

SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-October/133992.html (unstable, oem-6.0)

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ DP tunneling on a certain thunderbolt docking doesn't work well.
+ 
+ [Fix]
+ 
+ Add a new IP version in the switch cases that supports DPIA.
+ 
+ [Test Case]
+ 
+ Connect an external monitor via thunderbolt docking station.
+ 
+ [Where problems could occur]
+ 
+ DPIA is supported on AMD DCN314 gpu platforms. With or without it may
+ both introduce compatibility issues as what to be solve here.
+ 
+ [Other Info]
+ 
+ While this applies to AMD Phoenix/Phoenix2 platforms, only oem-6.0 or
+ above are nominated for fix.
+ 
+ == original bug description ==
+ 
  Observed unsuccessfully light-up on some TBT docking with the single
  monitor connected, adding a new IP version to enable DPIA functionality.
  
  
https://gitlab.freedesktop.org/agd5f/linux/-/commit/6fc6c3a991c2a983336ed230938937617a1394ab

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

Title:
  Enable DP tunneling functionality on AMD Pink Sardine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  DP tunneling on a certain thunderbolt docking doesn't work well.

  [Fix]

  Add a new IP version in the switch cases that supports DPIA.

  [Test Case]

  Connect an external monitor via thunderbolt docking station.

  [Where problems could occur]

  DPIA is supported on AMD DCN314 gpu platforms. With or without it may
  both introduce compatibility issues as what to be solve here.

  [Other Info]

  While this applies to AMD Phoenix/Phoenix2 platforms, only oem-6.0 or
  above are nominated for fix.

  == original bug description ==

  Observed unsuccessfully light-up on some TBT docking with the single
  monitor connected, adding a new IP version to enable DPIA
  functionality.

  
https://gitlab.freedesktop.org/agd5f/linux/-/commit/6fc6c3a991c2a983336ed230938937617a1394ab

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992723/+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 1990922] Re: Fix USB4 PCIe hotplug on AMD Pink Sardine

[You-Sheng Yang]

Landed in linux-oem-6.0/jammy version 6.0.0-1005.5.

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

Title:
  Fix USB4 PCIe hotplug on AMD Pink Sardine

Status in HWE Next:
  New
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]

  For some reason that PCIe device hotplug is disabled once another OS
  stack launches prior to Linux CM, which makes some registers not go
  properly, so correct those registers to meet the default value of the
  USB4 spec.

  [Fix]

  Two commits targeting v6.1 to restore the default values.

  [Test Case]

  To be verified from ODM side.

  [Where problems could occur]

  These two commits restores the default values as expected from USB4 spec
  at being initialized, so it should be the right behaviour anyway.

  [Other Info]

  While this is for AMD Pink Sardine platforms, only oem-6.0 and newer
  are nominated for fix.

  == original bug description ==

  For some reason that PCIe device hotplug is disabled once another OS
  stack launches prior to Linux CM, which makes some registers not go
  properly, so correct those registers to meet the default value of the
  USB4 spec.

  
https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=fixes=31f87f705b3c1635345d8e8a493697099b43e508

  
https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=5d2569cb4a65c373896ec0217febdf88739ed295

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1990922/+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 1992723] Re: Enable DP tunneling functionality on AMD Pink Sardine

[You-Sheng Yang]

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

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
   Status: New => Invalid

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

Title:
  Enable DP tunneling functionality on AMD Pink Sardine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid

Bug description:
  Observed unsuccessfully light-up on some TBT docking with the single
  monitor connected, adding a new IP version to enable DPIA
  functionality.

  
https://gitlab.freedesktop.org/agd5f/linux/-/commit/6fc6c3a991c2a983336ed230938937617a1394ab

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992723/+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 1992723] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1992723

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

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

Title:
  Enable DP tunneling functionality on AMD Pink Sardine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-6.0 source package in Jammy:
  New
Status in linux source package in Kinetic:
  Incomplete
Status in linux-oem-6.0 source package in Kinetic:
  New

Bug description:
  Observed unsuccessfully light-up on some TBT docking with the single
  monitor connected, adding a new IP version to enable DPIA
  functionality.

  
https://gitlab.freedesktop.org/agd5f/linux/-/commit/6fc6c3a991c2a983336ed230938937617a1394ab

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992723/+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 1992723] [NEW] Enable DP tunneling functionality on AMD Pink Sardine

[You-Sheng Yang]

Public bug reported:

Observed unsuccessfully light-up on some TBT docking with the single
monitor connected, adding a new IP version to enable DPIA functionality.

https://gitlab.freedesktop.org/agd5f/linux/-/commit/6fc6c3a991c2a983336ed230938937617a1394ab

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.0 (Ubuntu Kinetic)
 Importance: Undecided
 Status: New


** Tags: amd oem-priority originate-from-1992124

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

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

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

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

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

** Tags added: amd oem-priority originate-from-1992124

-- 
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/1992723

Title:
  Enable DP tunneling functionality on AMD Pink Sardine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New
Status in linux source package in Jammy:
  New
Status in linux-oem-6.0 source package in Jammy:
  New
Status in linux source package in Kinetic:
  New
Status in linux-oem-6.0 source package in Kinetic:
  New

Bug description:
  Observed unsuccessfully light-up on some TBT docking with the single
  monitor connected, adding a new IP version to enable DPIA
  functionality.

  
https://gitlab.freedesktop.org/agd5f/linux/-/commit/6fc6c3a991c2a983336ed230938937617a1394ab

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1992723/+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 1992564] Re: [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block device not working

[Frode Nordahl]

For completeness, I can confirm this also happens with the 5.19.0-20
kernel currently in -proposed.

** Summary changed:

- [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working
+ [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with block 
device not working

-- 
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/1992564

Title:
  [kinetic] 5.19.0-19 and 5.19.0-20 kernels, lxd virtual-machine with
  block device not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+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 1992118] Re: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel

[Jian Hui Lee]

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

** Changed in: linux-intel-iotg-5.15 (Ubuntu)
   Status: New => Invalid

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

Title:
  AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15
  intel IoTG kernel

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Invalid

Bug description:
  [Summary]
  AX210 (8086:e024) WLAN init failed ucode -5  after upgrading to 5.15 Intel 
IoTG kernel.

  [Steps to reproduce]
  $ sudo apt update
  $ sudo apt upgrade
  $ reboot

  [Expected result]
  WLAN works with no problem.

  [Actual result]
  Can't detect WLAN.

  [Failure rate]
  100%

  [Other Info]
  [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002)
  [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported 
by driver
  [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
0.63.2.2
  [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode op_mode iwlmvm
  [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
  [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000
  [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 
0x0.
  [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6
  [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 
ty-a0-gf-a0-66.ucode
  [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0
  [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1
  [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2
  [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1
  [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2
  [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1
  [4.812520] iwlwifi :02:00.0: 0x0010 | data2
  [4.812523] iwlwifi :02:00.0: 0x | data3
  [4.812527] iwlwifi :02:00.0: 0x | beacon time
  [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low
  [4.812533] iwlwifi :02:00.0: 0x | tsf hi
  [4.812536] iwlwifi :02:00.0: 0x | time gp1
  [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2
  [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type
  [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major
  [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor
  [4.812553] iwlwifi :02:00.0: 0x0420 | hw version
  [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version
  [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd
  [4.812563] iwlwifi :02:00.0: 0x0002 | isr0
  [4.812566] iwlwifi :02:00.0: 0x6000 | isr1
  [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2
  [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3
  [4.812575] iwlwifi :02:00.0: 0x | isr4
  [4.812578] iwlwifi :02:00.0: 0x | last cmd Id
  [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event
  [4.812584] iwlwifi :02:00.0: 0x | l2p_control
  [4.812588] iwlwifi :02:00.0: 0x | l2p_duration
  [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid
  [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match
  [4.812597] iwlwifi :02:00.0: 0x0009 | lmpm_pmg_sel
  [4.812600] iwlwifi :02:00.0: 0x | timestamp
  [4.812603] iwlwifi :02:00.0: 0x0024 | flow_handler
  [4.812640] iwlwifi :02:00.0: Start IWL Error Log Dump:
  [4.812643] iwlwifi :02:00.0: Transport status: 0x004A, valid: 7
  [4.812647] iwlwifi :02:00.0: 0x2010070D | ADVANCED_SYSASSERT
  [4.812651] iwlwifi :02:00.0: 0x | umac branchlink1
  [4.812654] iwlwifi :02:00.0: 0x8045DFC6 | umac branchlink2
  [4.812658] iwlwifi :02:00.0: 0x010910FE | umac interruptlink1
  [4.812661] iwlwifi :02:00.0: 0x | umac interruptlink2
  [4.812664] iwlwifi :02:00.0: 0x0005 | umac data1
  [4.812667] iwlwifi :02:00.0: 0xDEADBEEF | umac data2
  [4.812670] iwlwifi :02:00.0: 0xDEADBEEF | umac data3
  [4.812673] iwlwifi :02:00.0: 0x0042 | umac major
  [4.812677] iwlwifi :02:00.0: 0xF1C864E0 | umac minor
  [4.812680] iwlwifi :02:00.0: 0x000244D8 | frame pointer
  [4.812683] iwlwifi :02:00.0: 0xC0885E88 | stack pointer
  [4.812686] iwlwifi :02:00.0: 0x00010C00 | last host cmd
  [4.812689] iwlwifi :02:00.0: 0x | isr status reg
  [

[Kernel-packages] [Bug 1992721] [NEW] package nvidia-dkms-515 515.76-0ubuntu0.22.04.1~gpu1 failed to install/upgrade: installed nvidia-dkms-515 package post-installation script subprocess returned err

[Rafael Zasas]

Public bug reported:

unable to sudo apt-get update/upgrade. unable to install nvidia 515 from
additional drivers

dpkg: error processing package nvidia-driver-515 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup erro
r from a previous failure.
  Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for initramfs-tools (0.140ubuntu13) ...
update-initramfs: Generating /boot/initrd.img-6.0.1-060001-generic
Errors were encountered while processing:
 nvidia-dkms-515
 nvidia-driver-515

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: nvidia-dkms-515 515.76-0ubuntu0.22.04.1~gpu1
Uname: Linux 6.0.1-060001-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Oct 12 20:42:21 2022
ErrorMessage: installed nvidia-dkms-515 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2022-08-06 (68 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: nvidia-graphics-drivers-515
Title: package nvidia-dkms-515 515.76-0ubuntu0.22.04.1~gpu1 failed to 
install/upgrade: installed nvidia-dkms-515 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-515 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package nvidia-dkms-515 515.76-0ubuntu0.22.04.1~gpu1 failed to
  install/upgrade: installed nvidia-dkms-515 package post-installation
  script subprocess returned error exit status 10

Status in nvidia-graphics-drivers-515 package in Ubuntu:
  New

Bug description:
  unable to sudo apt-get update/upgrade. unable to install nvidia 515
  from additional drivers

  dpkg: error processing package nvidia-driver-515 (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
erro
  r from a previous failure.
Processing triggers for man-db (2.10.2-1) ...
  Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
  Processing triggers for initramfs-tools (0.140ubuntu13) ...
  update-initramfs: Generating /boot/initrd.img-6.0.1-060001-generic
  Errors were encountered while processing:
   nvidia-dkms-515
   nvidia-driver-515

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: nvidia-dkms-515 515.76-0ubuntu0.22.04.1~gpu1
  Uname: Linux 6.0.1-060001-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 20:42:21 2022
  ErrorMessage: installed nvidia-dkms-515 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2022-08-06 (68 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: nvidia-graphics-drivers-515
  Title: package nvidia-dkms-515 515.76-0ubuntu0.22.04.1~gpu1 failed to 
install/upgrade: installed nvidia-dkms-515 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1992721/+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 1992714] [NEW] SoF for RPL support

[AceLan Kao]

Public bug reported:

[Impact]

[Fix]

[Test]

[Where problems could occur]

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-6.0 (Ubuntu Jammy)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

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

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

Title:
  SoF for RPL support

Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 source package in Jammy:
  In Progress

Bug description:
  [Impact]

  [Fix]

  [Test]

  [Where problems could occur]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992714/+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 1992580] Re: i915 DG1 fails to load

[Alex Murray]

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

** This bug has been marked a duplicate of bug 1991704
   Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

-- 
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/1992580

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+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 1992667] Re: Application windows invisible (on DG2 graphics)

[Daniel van Vugt]

Thanks for the bug report. Yes the screenshot shows texture corruption
which may also relate to missing windows. If DG2 is anything like the
desktop Arc chips then you will need Mesa 22.2 (Ubuntu 22.10) to support
it. As well as kernel 6.0.

Please run:

  lspci -k > lspci.txt

and attach the resulting text file here.

Please also consider testing Ubuntu 22.10:

  https://cdimage.ubuntu.com/daily-live/current/

because that's probably the only Ubuntu release with an adequate Mesa
version.

** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)

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

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

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

Title:
  Application windows invisible (on DG2 graphics)

Status in linux-oem-6.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  When using GNOME Shell with Wayland, all application windows become
  invisible from time to time. This usually happens right after starting
  GNOME Shell for the first time or after having a VRAM intensive
  application open, such as a game.

  I have installed the latest linux-oem-6.0 kernel and manually enabled
  support for DG2 graphics by passing the i915.force_probe parameter
  with the PCIe ID of the graphics card.

  I have attached a screenshot of the described behavior below.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 17:23:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.0/+bug/1992667/+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 1883511] Re: High load from process irq/65-i2c-INT3 - kernel module tps6598x

[gui ambros]

Same here; it seems there was a regression in kernel 5.15.x, and
confirmed on a Intel Frost Canyon NUC 10 with Core i7.

The behavior is the same as before: load > 1.0 due to irq/65-i2c-INT3,
even when not running anything. Using `modprobe -r tps6598x` fixes it
(temporarily).

In my case I'm running Proxmox, which is based on Debian 11 (bullseye),
kernel 5.15.53-1-pve, so this is not Ubuntu-specific.

-- 
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/1883511

Title:
  High load from process irq/65-i2c-INT3  - kernel module tps6598x

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  There seems to be an issue with the kernel module tps6598x which puts
  the CPU on a high load:
  https://forums.intel.com/s/question/0D50P4fWnUeSAK/nuc10i3-irq-
  problem

  As soon as the module is unloaded, cpu load is back to normal.

  According to a post in the link above the issue is the following:
  "My guess is that the IRQ resource is not correct for the PD
  controller causing you to see irq flood.
   
  The problem is that the ACPI device entry (the node) on this platform
  has 4 I2CSerialBus resources and 4 IRQ resources. The idea is that the
  single ACPI device entry can represent up to 4 USB PD controllers. The
  problem is that there is no way to know which IRQ resource belongs to
  which I2CSerialBus resource :-(.
   
  Andy, this is one of those multi-instantiate I2C slave devices with
  HID INT3515.
   
  The only solution I can think of is that we start maintaining DMI
  quirk table in drivers/platform/x86/i2c-multi-instantiate.c where we
  supply the correct i2c to irq resource mapping for every platform
  that has this device(s)."

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  Hardware: Intel NUC10i5FNK

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-37-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperMD5CheckResult: pass
  Date: Mon Jun 15 11:04:57 2020
  InstallationDate: Installed on 2020-04-26 (49 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel(R) Client Systems NUC10i5FNK
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-37-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0041.2020.0518.1045
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i5FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61361-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0041.2020.0518.1045:bd05/18/2020:svnIntel(R)ClientSystems:pnNUC10i5FNK:pvrK61339-302:rvnIntelCorporation:rnNUC10i5FNB:rvrK61361-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i5FNK
  dmi.product.sku: BXNUC10i5FNK
  dmi.product.version: K61339-302
  dmi.sys.vendor: Intel(R) Client Systems

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


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

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

[Daniel van Vugt]

Duplicate bug 1970402 mentions that:

> Workaround: Disable Secure Boot and SGX.

works for multiple people.

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

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

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

Bug description:
  [Impact]

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

   * Some real cases from OEM projects:

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

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

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

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

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

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

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

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

  [Test Plan]

   * detailed instructions how to reproduce the bug:

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

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

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

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

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

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

  And then update-initramfs

   * After applying my patches, the issue is gone.

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

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

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

  All working well.

  [Where problems could occur]

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

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

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

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

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

  [Other Info]

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

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

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

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

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  

[Kernel-packages] [Bug 1991254] Re: No HDMI sound output from alsa in server (no KMS)

[Brian Murray]

Is this sorted out now?

** Changed in: linux-raspi (Ubuntu Kinetic)
Milestone: None => ubuntu-22.10

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

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

Title:
  No HDMI sound output from alsa in server (no KMS)

Status in Release Notes for Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  Fix Committed
Status in linux-raspi source package in Kinetic:
  Fix Committed

Bug description:
  During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi
  image, on a Raspberry Pi 4B and 3B, I noted that the HDMI "sound card"
  no longer appears in /proc/asound/cards; only the Headphones output
  (from the AUX socket on the board) appears.

  I checked with the current linux-raspi in the release pocket
  (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi),
  and both exhibit the same issue.

  On Kinetic:

  $ cat /proc/asound/cards
   0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
    bcm2835 Headphones

  On Jammy:

  $ cat /proc/asound/cards
   0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1
    bcm2835 HDMI 1
   1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones
    bcm2835 Headphones

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991254/+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 1992212] Re: nouveau pmu: firmware unavailable gp107

[Robert Browne]

As you can see in dmesg cannot enable HDA controller.
Causes no sound when using HDMI video stream.
Is there other firmware for gp107m ?

00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graph
ics 630]
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (r
ev a1)

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

Title:
  nouveau pmu: firmware unavailable gp107

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  /lib/firmware/nvidia/gp107
  /lib/firmware/nvidia/gp107/acr
  /lib/firmware/nvidia/gp107/gr
  /lib/firmware/nvidia/gp107/gr/fecs_bl.bin
  /lib/firmware/nvidia/gp107/gr/fecs_data.bin
  /lib/firmware/nvidia/gp107/gr/fecs_inst.bin
  /lib/firmware/nvidia/gp107/gr/fecs_sig.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_data.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin
  /lib/firmware/nvidia/gp107/gr/sw_ctx.bin
  /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin
  /lib/firmware/nvidia/gp107/nvdec
  /lib/firmware/nvidia/gp107/sec2
  /lib/firmware/nvidia/gp107/acr/bl.bin
  /lib/firmware/nvidia/gp107/acr/ucode_load.bin
  /lib/firmware/nvidia/gp107/acr/ucode_unload.bin
  /lib/firmware/nvidia/gp107/acr/unload_bl.bin
  /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin
  /lib/firmware/nvidia/gp107/gr/sw_method_init.bin
  /lib/firmware/nvidia/gp107/nvdec/scrubber.bin
  /lib/firmware/nvidia/gp107/sec2/desc-1.bin
  /lib/firmware/nvidia/gp107/sec2/desc.bin
  /lib/firmware/nvidia/gp107/sec2/image-1.bin
  /lib/firmware/nvidia/gp107/sec2/image.bin
  /lib/firmware/nvidia/gp107/sec2/sig-1.bin
  /lib/firmware/nvidia/gp107/sec2/sig.bin

  Package: linux-firmware
  Status: install ok installed
  Priority: optional
  Section: misc
  Installed-Size: 846721
  Maintainer: Ubuntu Kernel Team 
  Architecture: all
  Multi-Arch: foreign
  Version: 20220329.git681281e4-0ubuntu3.5
  Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), 
linux-res
  tricted-common
  Provides: atmel-firmware
  Recommends: firmware-sof-signed
  Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), 
linux-firmware-snapdrago
  n (<= 1.2-0ubuntu1)
  Conflicts: atmel-firmware
  Description: Firmware for Linux kernel drivers
   This package provides firmware used by Linux kernel drivers.
  Oct  8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS
  Oct  8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: 
\_SB.PCI0.GFX0._DSM: 
  Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20210730/ns
  arguments-61)
  Oct  8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: 
\_SB.PCI0.PEG0.PEGP._
  DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] 
(202107
  30/nsarguments-61)
  Oct  8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus 
capabilit
  ies: enabled, status dynamic power, hda bios codec supported
  Oct  8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus 
DS
  M method \_SB_.PCI0.PEG0.PEGP handle
  Oct  8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling 
devi
  ce (0006 -> 0007)
  Oct  8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 
7e9000) 
  vs hw (a300 100)
  Oct  8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 
7e9000) 
  vs hw (9000 1000)
  Oct  8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 
7e9000) 
  vs hw (a000 200)
  Oct  8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA 
GP107 
  (137000a1)
  Oct  8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 
7e9000) 
  vs hw (a200 100)
  Oct  8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 
7e9000) 
  vs hw (8000 1000)
  Oct  8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: 
version
   86.07.50.00.59
  Oct  8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: 
firmware
   unavailable
  Oct  8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] 
[ENCODER:1
  02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
  Oct  8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 
MiB 
  GDDR5
  Oct  8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 
202011
  03 for :00:02.0 on minor 0
  Oct  8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] 
(m
  ulti-head: yes  rom: no  post: no)
  Oct  8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM: 
40
  96 MiB
  Oct  8 08:49:44 fx504 kernel: [3.139763] nouveau :01:00.0: DRM: GART: 
53
  6870912 MiB
  Oct  8 08:49:44 fx504 kernel: [3.139766] nouveau :01:00.0: DRM: BIT 
tabl
  e 'A' not found
  Oct  8 

[Kernel-packages] [Bug 1992696] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I plug in this usb wifi 802.11ac + Bluetooth 5.0 Realtek adaptor and I
  get no networking from it.  I also have a wireless N adapter  on usb
  as well.

  This was pretty much the same behavior since 20.04.   I haven't been
  able to use this adaptor for wifi for quite a while.   I heard that
  Fedora has no problem with this device.  It may be that the order of
  activation is what needs to be modified.  Like activate the bluetooth
  first, and then make the wifi part active.

  Thanks for all the great work!

  Here is the Dmesg I get the following which shows up using dmesg...

  
  [  107.256812] usb 3-3: new high-speed USB device number 3 using xhci_hcd
  [  107.405398] usb 3-3: New USB device found, idVendor=0bda, idProduct=b82c, 
bcdDevice= 2.10
  [  107.405415] usb 3-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  107.405421] usb 3-3: Product: 802.11ac+Bluetooth 5.0 Adapter
  [  107.405425] usb 3-3: Manufacturer: Realtek
  [  107.405428] usb 3-3: SerialNumber: 123456
  [  107.409742] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b 
lmp_ver=07 lmp_subver=8822
  [  107.410730] Bluetooth: hci0: RTL: rom_version status=0 version=2
  [  107.410740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
  [  107.411027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
  [  107.411173] Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
  [  108.152731] Bluetooth: hci0: RTL: fw version 0xab6b705c

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-19-generic 5.19.0-19.19
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uplifting   4065 F wireplumber
   /dev/snd/seq:uplifting   4058 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 15:00:44 2022
  MachineType: Hewlett-Packard HP ProBook 4540s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_uiqi22@/vmlinuz-5.19.0-19-generic 
root=ZFS=rpool/ROOT/ubuntu_uiqi22 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  dmi.bios.date: 05/20/2013
  dmi.bios.release: 15.65
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.41
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 88.30
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:br15.65:efr88.30:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr:skuC9K70UT#ABA:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 4540s
  dmi.product.sku: C9K70UT#ABA
  dmi.product.version: A1019D1103
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992696/+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 1992696] [NEW] Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function

[Joe Baker]

Public bug reported:

I plug in this usb wifi 802.11ac + Bluetooth 5.0 Realtek adaptor and I
get no networking from it.  I also have a wireless N adapter  on usb as
well.

This was pretty much the same behavior since 20.04.   I haven't been
able to use this adaptor for wifi for quite a while.   I heard that
Fedora has no problem with this device.  It may be that the order of
activation is what needs to be modified.  Like activate the bluetooth
first, and then make the wifi part active.

Thanks for all the great work!

Here is the Dmesg I get the following which shows up using dmesg...


[  107.256812] usb 3-3: new high-speed USB device number 3 using xhci_hcd
[  107.405398] usb 3-3: New USB device found, idVendor=0bda, idProduct=b82c, 
bcdDevice= 2.10
[  107.405415] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  107.405421] usb 3-3: Product: 802.11ac+Bluetooth 5.0 Adapter
[  107.405425] usb 3-3: Manufacturer: Realtek
[  107.405428] usb 3-3: SerialNumber: 123456
[  107.409742] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b 
lmp_ver=07 lmp_subver=8822
[  107.410730] Bluetooth: hci0: RTL: rom_version status=0 version=2
[  107.410740] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
[  107.411027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
[  107.411173] Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
[  108.152731] Bluetooth: hci0: RTL: fw version 0xab6b705c

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: linux-image-5.19.0-19-generic 5.19.0-19.19
ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
Uname: Linux 5.19.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  uplifting   4065 F wireplumber
 /dev/snd/seq:uplifting   4058 F pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 12 15:00:44 2022
MachineType: Hewlett-Packard HP ProBook 4540s
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_uiqi22@/vmlinuz-5.19.0-19-generic 
root=ZFS=rpool/ROOT/ubuntu_uiqi22 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.19.0-19-generic N/A
 linux-backports-modules-5.19.0-19-generic  N/A
 linux-firmware 20220923.gitf09bebf3-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
dmi.bios.date: 05/20/2013
dmi.bios.release: 15.65
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IRR Ver. F.41
dmi.board.name: 17F6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 58.1E
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 88.30
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.41:bd05/20/2013:br15.65:efr88.30:svnHewlett-Packard:pnHPProBook4540s:pvrA1019D1103:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1E:cvnHewlett-Packard:ct10:cvr:skuC9K70UT#ABA:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 4540s
dmi.product.sku: C9K70UT#ABA
dmi.product.version: A1019D1103
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug kinetic

-- 
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/1992696

Title:
  Realtek USB 802.11ac + Bluetooth 5.0 Fails wifi Network function

Status in linux package in Ubuntu:
  New

Bug description:
  I plug in this usb wifi 802.11ac + Bluetooth 5.0 Realtek adaptor and I
  get no networking from it.  I also have a wireless N adapter  on usb
  as well.

  This was pretty much the same behavior since 20.04.   I haven't been
  able to use this adaptor for wifi for quite a while.   I heard that
  Fedora has no problem with this device.  It may be that the order of
  activation is what needs to be modified.  Like activate the bluetooth
  first, and then make the wifi part active.

  Thanks for all the great work!

  Here is the Dmesg I get the following which shows up using dmesg...

  
  [  107.256812] usb 3-3: new high-speed USB device number 3 using xhci_hcd
  [  107.405398] usb 3-3: New USB device found, idVendor=0bda, idProduct=b82c, 
bcdDevice= 2.10
  [  107.405415] usb 3-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  107.405421] usb 3-3: Product: 802.11ac+Bluetooth 5.0 Adapter
  [  107.405425] usb 3-3: Manufacturer: Realtek
  [  107.405428] usb 3-3: SerialNumber: 123456
  [  107.409742] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b 
lmp_ver=07 lmp_subver=8822
  [  107.410730] Bluetooth: hci0: RTL: rom_version status=0 

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Dimitri John Ledkov]

initramfs-tools also mounts /dev with nosuid, without noexec

> mount -t devtmpfs -o nosuid,mode=0755 udev /dev

I believe all of these should be the same, thus kernel can mount /dev
with nosuid, but should not mount it with noexec.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Dave Chiluk]

Alright so that means we either need to push a change to remove noexec
from the kernel init code, or we go ahead with noexec, and give people
on option to remount with exec should they want sgx functionality.  I do
think the nosuid flag does still provide some benefit even if we decide
not to include the noexec flag by default until 5.17+.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1991782] Re: mktme error on boot

[Amnon Yekutieli]

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

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

Title:
  mktme error on boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  While booting the system I get this error message twice: 

  kernel: x86/mktme: No known encryption algorithm is supported: 0x0
  pci :00:07.0: DPC: RP PIO log size 0 is invalid
  pci :00:07.2: DPC: RP PIO log size 0 is invalid

  This seems to be new, after recent upgrade to KUBUNTU 22.04.

  My system:

  Dell XPS 13 9310

  Operating System: Kubuntu 22.04
  KDE Plasma Version: 5.24.6
  KDE Frameworks Version: 5.92.0
  Qt Version: 5.15.3
  Kernel Version: 5.15.0-48-generic (64-bit)
  Graphics Platform: X11
  Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
  Memory: 15.3 GiB of RAM
  Graphics Processor: Mesa Intel® Xe Graphics
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amyekut1134 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-06-15 (479 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9310
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  Tags:  jammy
  Uname: Linux 5.15.0-48-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 08/09/2022
  dmi.bios.release: 3.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.10.0
  dmi.board.name: 0DXP1F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amyekut1134 F pulseaudio
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-06-15 (479 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9310
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IL:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=c0b5dac0-3a80-4a1b-b92e-2238aaccc427 ro quiet splash
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  Tags:  jammy
  Uname: Linux 5.15.0-48-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-09-19 (18 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/09/2022
  dmi.bios.release: 3.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.10.0
  dmi.board.name: 0DXP1F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.10.0:bd08/09/2022:br3.10:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0DXP1F:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991782/+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 1991691] Re: cannot change mount namespace

[Dimitri John Ledkov]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  cannot change mount namespace

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Multiple snaps are either broken or "only" display permission denied
  messages.

  slack snap is not starting at all with:

  > update.go:85: cannot change mount namespace according to change
  mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none
  bind,rw,x-snapd.ignore-missing 0 0): cannot inspect
  "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied

  firefox snap does start, but also logs errors:

  
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot 
inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat 
/var/lib/snapd/hostfs/usr/share/doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat 
/var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": 
lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Oct  4 17:29:01 2022
  InstallationDate: Installed on 2017-09-26 (1834 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1991691/+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 1992679] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Can not login after new kernel installed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed

[vodopad27]

https://youtu.be/5KiSmPbkibg video with bugs (~1 min)

-- 
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/1992679

Title:
  Can not login after new kernel installed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed

[vodopad27]

And look to strange line in button after booting...

** Attachment added: "2022-10-12_20-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+attachment/5623586/+files/2022-10-12_20-11.png

-- 
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/1992679

Title:
  Can not login after new kernel installed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed

[vodopad27]

apt log

** Attachment added: "apt1.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+attachment/5623584/+files/apt1.log

** Description changed:

  Hello. Today i have installed new kernel from. I installed 5.15.0-50 and
  after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and login
  with old kernel  (5.15.0-48).
  
  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)
  
- 
  Updated logs see in attachement.
  
- Logs from journalctl:
+ Logs from journalctl see in attachements.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  vodka  1819 F pulseaudio
-  /dev/snd/controlC1:  vodka  1819 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  vodka  1819 F pulseaudio
+  /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
-  Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
-  Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
+  Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
+  Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.15.0-48-generic N/A
-  linux-backports-modules-5.15.0-48-generic  N/A
-  linux-firmware 20220329.git681281e4-0ubuntu3.5
+  linux-restricted-modules-5.15.0-48-generic N/A
+  linux-backports-modules-5.15.0-48-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

-- 
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/1992679

Title:
  Can not login after new kernel installed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 

[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed

[vodopad27]

journalctl log

** Attachment added: "journal.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+attachment/5623583/+files/journal.log

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

Title:
  Can not login after new kernel installed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed

[vodopad27]

Nvidia driver version: 510.85.02
Videocard: RTX 3060

-- 
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/1992679

Title:
  Can not login after new kernel installed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] [NEW] Can not login after new kernel installed

[vodopad27]

Public bug reported:

Hello. Today i have installed new kernel from. I installed 5.15.0-50 and
after that i can not login to system... I see boot text, but after
booting i see black log screen and can not login. I able boot and login
with old kernel  (5.15.0-48).

I updated these packages:
Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

Updated logs see in attachement.

Logs from journalctl see in attachements.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-50-generic 5.15.0-50.56
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vodka  1819 F pulseaudio
 /dev/snd/controlC1:  vodka  1819 F pulseaudio
CasperMD5CheckResult: unknown
Date: Wed Oct 12 19:56:43 2022
InstallationDate: Installed on 2018-05-02 (1623 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
 Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-48-generic N/A
 linux-backports-modules-5.15.0-48-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
dmi.bios.date: 03/28/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F7a
dmi.board.asset.tag: Default string
dmi.board.name: H610M S2H DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: H610 MB
dmi.product.name: H610M S2H DDR4
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug jammy

-- 
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/1992679

Title:
  Can not login after new kernel installed

Status in linux package in Ubuntu:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 

[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x

[Frank Heimes]

Thx for the update about the PR, Boris!

-- 
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/1639924

Title:
  Kernel livepatch support for for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in kpatch package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in gcc-11 source package in Jammy:
  Fix Released
Status in kpatch source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in gcc-11 source package in Kinetic:
  Fix Released
Status in kpatch source package in Kinetic:
  New
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  Kernel live-patch is afaik fully upstream and available for 'all' platforms 
(incl. s390x).
  But the kpatch-build tool does only support amd64 as of today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+subscriptions


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

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Nick Rosbrook]

FWIW upstream systemd removed the MS_NOEXEC flag from /dev in
https://github.com/systemd/systemd/commit/4eb105fa4aae30566d23382e8c9430eddf1a3dd4.

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1971712] Re: Add support for Intel DG2

[Sebastian Heiden]

Looking forward to linux-oem-6.0 support. Got an A380 and A770 here for
testing purposes.

It seems like the current proposed build of the linux-oem-6.0 kernel
still has some issues in this regard.

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1992671] [NEW] cm4 2021 version failed to boot on 20.04

[soft]

Public bug reported:

The new CM4 (2021), which has UKCA sign on the board, here is its cpuinfo :
Hardware: BCM2835
Revision: b03141
Model   : Raspberry Pi Compute Module 4 Rev 1.1

Once it is connected to internet, the security patch creates in /boot
lrwxrwxrwx  1 root root   43 Oct 12 14:31 dtb-5.4.0-1071-raspi -> 
dtbs/5.4.0-1071-raspi/./bcm2711-rpi-4-b.dtb

At the same time, in /boot/firmware, all .elf files and .dat files are
backed up and replaced. The new files make the next boot crash. If we
connect it to screen, it shows that the cm4 needs new software to boot.

The fix from our side is to mount as usb disk and replace all .elf and .dat 
files by the latest here :
https://github.com/raspberrypi/firmware/tree/master/boot
and then it can boot again.

On CM4 (2020) this security patch doesn't crash on boot.
Revision: b03140
Model   : Raspberry Pi Compute Module 4 Rev 1.0

Here is the product change note :
https://pip.raspberrypi.com/categories/645

This bug seems to be introduced before, the 1070 patch cause the same
boot problem already.

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  cm4 2021 version failed to boot on 20.04

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  The new CM4 (2021), which has UKCA sign on the board, here is its cpuinfo :
  Hardware: BCM2835
  Revision: b03141
  Model   : Raspberry Pi Compute Module 4 Rev 1.1

  Once it is connected to internet, the security patch creates in /boot
  lrwxrwxrwx  1 root root   43 Oct 12 14:31 dtb-5.4.0-1071-raspi -> 
dtbs/5.4.0-1071-raspi/./bcm2711-rpi-4-b.dtb

  At the same time, in /boot/firmware, all .elf files and .dat files are
  backed up and replaced. The new files make the next boot crash. If we
  connect it to screen, it shows that the cm4 needs new software to
  boot.

  The fix from our side is to mount as usb disk and replace all .elf and .dat 
files by the latest here :
  https://github.com/raspberrypi/firmware/tree/master/boot
  and then it can boot again.

  On CM4 (2020) this security patch doesn't crash on boot.
  Revision: b03140
  Model   : Raspberry Pi Compute Module 4 Rev 1.0

  Here is the product change note :
  https://pip.raspberrypi.com/categories/645

  This bug seems to be introduced before, the 1070 patch cause the same
  boot problem already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1992671/+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 1992669] [NEW] Introduce the NVIDIA 520 UDA driver series

[Alberto Milone]

Public bug reported:

[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates

Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.

[Discussion]

[Changelog]

== 520.56.06 (UDA) ==

  * New upstream release:
- Implemented support for over-the-air updates in the Proton and
  Wine NVIDIA NGX build. This feature is disabled by default and
  can be enabled by setting the "PROTON_ENABLE_NGX_UPDATER" 
  environment variable to a value of "1".   
- Updated the Vulkan driver so that the following extensions no
  longer depend on nvidia-uvm.ko being loaded at runtime:
  + VK_KHR_acceleration_structure
  + VK_KHR_deferred_host_operations
  + VK_KHR_ray_query
  + VK_KHR_ray_tracing_pipeline
  + VK_NV_cuda_kernel_launch
  + VK_NV_ray_tracing
  + VK_NV_ray_tracing_motion_blur
  + VK_NVX_binary_import
  + VK_NVX_image_view_handle
- Updated nvidia-installer to allow use of the "--add-this-
  kernel" feature by non-root users.
- Updated nvidia-installer to display a more accurate progress
  bar when building the kernel modules.
- Updated nvidia-installer to display a warning message if a
  Vulkan ICD loader is not detected.
- Reworked nvidia-installer's support for DKMS: the kernel
  modules will now be optionally registered with DKMS after the
  installer has already built and installed them on its own.
  nvidia-installer will now register the kernel modules with DKMS
  by default when the dkms(8) utility is detected on the system.
- Fixed a bug in the Vulkan driver which could lead to corruption
  in geometry and tessellation control shaders.
- Added a new CUDA Debugger implementation for Pascal and newer
  architectures as a part of the driver package:
  libcudadebugger.so (previously released separately as "CUDA GDB
  Developer Preview").
- Fixed a regression in 515.76 that caused blank screens and
  hangs when starting an X server on RTX 30 series GPUs in some
  configurations where the boot display is connected via HDMI.
- Fixed a bug where Marvel's Spider-Man Remastered would
  sometimes crash with Xid 13 errors on Turing and later.

** Affects: nvidia-graphics-drivers-515 (Ubuntu)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: In Progress

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

Title:
  Introduce the NVIDIA 520 UDA driver series

Status in nvidia-graphics-drivers-515 package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 520.56.06 (UDA) ==

* New upstream release:
  - Implemented support for over-the-air updates in the Proton and
Wine NVIDIA NGX build. This feature is disabled by default and
can be enabled by setting the "PROTON_ENABLE_NGX_UPDATER" 
environment variable to a value of "1".   
  - Updated the Vulkan driver so that the following extensions no
longer depend on nvidia-uvm.ko being loaded at runtime:
+ VK_KHR_acceleration_structure
+ VK_KHR_deferred_host_operations
+ VK_KHR_ray_query
+ 

[Kernel-packages] [Bug 1992667] [NEW] Application windows invisible (on DG2 graphics)

[Sebastian Heiden]

Public bug reported:

When using GNOME Shell with Wayland, all application windows become
invisible from time to time. This usually happens right after starting
GNOME Shell for the first time or after having a VRAM intensive
application open, such as a game.

I have installed the latest linux-oem-6.0 kernel and manually enabled
support for DG2 graphics by passing the i915.force_probe parameter with
the PCIe ID of the graphics card.

I have attached a screenshot of the described behavior below.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
Uname: Linux 6.0.0-1005-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Oct 12 17:23:40 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-10-11 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux-oem-6.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Attachment added: "Screenshot of the described bug"
   
https://bugs.launchpad.net/bugs/1992667/+attachment/5623541/+files/gnome_shell_invisible_windows.png

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

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

Title:
  Application windows invisible (on DG2 graphics)

Status in gnome-shell package in Ubuntu:
  New
Status in linux-oem-6.0 package in Ubuntu:
  New

Bug description:
  When using GNOME Shell with Wayland, all application windows become
  invisible from time to time. This usually happens right after starting
  GNOME Shell for the first time or after having a VRAM intensive
  application open, such as a game.

  I have installed the latest linux-oem-6.0 kernel and manually enabled
  support for DG2 graphics by passing the i915.force_probe parameter
  with the PCIe ID of the graphics card.

  I have attached a screenshot of the described behavior below.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1005.5-oem 6.0.0
  Uname: Linux 6.0.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 17:23:40 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-11 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1992667/+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 1992525] Re: Boot failure when not in recovery mode

[Andrea Righi]

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

** This bug has been marked a duplicate of bug 1991704
   Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen

-- 
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/1992525

Title:
  Boot failure when not in recovery mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded the kernel to 5.19.0-19 and can only boot in recovery
  mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-19-generic 5.19.0-19.19
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bdmurray   5525 F pipewire
bdmurray   5528 F wireplumber
   /dev/snd/seq:bdmurray   5525 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 11 15:15:29 2022
  InstallationDate: Installed on 2022-01-07 (277 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20XY0027US
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=UUID=c58ecc55-8765-4214-b495-303b0d3056b4 ro recovery nomodeset 
dis_ucode_ldr
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to kinetic on 2022-09-15 (26 days ago)
  dmi.bios.date: 09/06/2021
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET71W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XY0027US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET71W(1.47):bd09/06/2021:br1.47:efr1.29:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6:
  dmi.product.family: ThinkPad X1 Yoga Gen 6
  dmi.product.name: 20XY0027US
  dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6
  dmi.product.version: ThinkPad X1 Yoga Gen 6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992525/+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 1639924] Re: Kernel livepatch support for for s390x

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-01-18 08:14 EDT---
According to the effort, this can only be on a wishlist, till priority will 
change.
Set target to 18.04 for revalidation.

--- Comment From heinz-werner_se...@de.ibm.com 2018-03-05 05:09 EDT---
This Feature is currently flagged with Low Prio.
Set to Ubuntu 19.04 for revalidation.

--- Comment From heinz-werner_se...@de.ibm.com 2018-12-11 05:26 EDT---
This feature request will not make it into 19.04/19.10. Need to be prioritized 
within the overall plan Therefore change for the time beeing to 20.04.

--- Comment From heinz-werner_se...@de.ibm.com 2019-11-15 04:14 EDT---
This feature will not make it into 20.04 -> need to be postponend, at least to 
20.10

--- Comment From heinz-werner_se...@de.ibm.com 2020-07-09 05:08 EDT---
Feature request moved to 21.04, will not make it into 20.10 timeframe.
The function need to be implemented within the kpatch package for s390x...

--- Comment From heinz-werner_se...@de.ibm.com 2021-03-10 08:40 EDT---
Feature will not make it into 21.10 , moved to 22.04

--- Comment From boris.m...@de.ibm.com 2022-06-08 08:58 EDT---
* The kpatch  pull request that Sumanth had submitted quite a while ago has now 
finally been agreed to by the maintainer (after thorough tests and 
modifications).

This is the relevant pull request:
https://github.com/dynup/kpatch/pull/1203

** Tags added: architecture-s39064 bugnameltc-148869 severity-high
targetmilestone-inin2204

-- 
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/1639924

Title:
  Kernel livepatch support for for s390x

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in kpatch package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in gcc-11 source package in Jammy:
  Fix Released
Status in kpatch source package in Jammy:
  New
Status in linux source package in Jammy:
  New
Status in gcc-11 source package in Kinetic:
  Fix Released
Status in kpatch source package in Kinetic:
  New
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  Kernel live-patch is afaik fully upstream and available for 'all' platforms 
(incl. s390x).
  But the kpatch-build tool does only support amd64 as of today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+subscriptions


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

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

[sudodus]

Another workaround might be to use Ubuntu's own compressed image with a
preinstalled Ubuntu Server (although not officially released) according
to the following link

https://ubuntuforums.org/showthread.php?t=2474692

Scroll down to read also the following posts, that describe how to
install Lubuntu. In the same way you can install Ubuntu Desktop as well
as all the community flavours.

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

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

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

Bug description:
  [Impact]

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

   * Some real cases from OEM projects:

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

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

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

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

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

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

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

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

  [Test Plan]

   * detailed instructions how to reproduce the bug:

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

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

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

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

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

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

  And then update-initramfs

   * After applying my patches, the issue is gone.

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

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

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

  All working well.

  [Where problems could occur]

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

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

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

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

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

  [Other Info]

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

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

   * Test grubx64.efi:
  

[Kernel-packages] [Bug 1992647] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  ~/devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad not recognized

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilherme   1780 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 14:09:35 2022
  InstallationDate: Installed on 2022-10-07 (4 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Spin SP314-54N
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=ce47c382-5d2f-4ad1-966d-cadcfe91cbe7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.name: Lenny_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.12
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.7:svnAcer:pnSpinSP314-54N:pvrV1.12:rvnIL:rnLenny_IL:rvrV1.12:cvnAcer:ct31:cvrV1.12:sku:
  dmi.product.family: Spin 3
  dmi.product.name: Spin SP314-54N
  dmi.product.sku: 
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992647/+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 1971712] Re: Add support for Intel DG2

[Timo Aaltonen]

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

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

** Changed in: linux-oem-6.0 (Ubuntu Jammy)
   Status: New => In Progress

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1992647] [NEW] ~/devices

[Guilherme]

Public bug reported:

Touchpad not recognized

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-50-generic 5.15.0-50.56
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  guilherme   1780 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 12 14:09:35 2022
InstallationDate: Installed on 2022-10-07 (4 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Acer Spin SP314-54N
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=ce47c382-5d2f-4ad1-966d-cadcfe91cbe7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-50-generic N/A
 linux-backports-modules-5.15.0-50-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2021
dmi.bios.release: 1.12
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.12
dmi.board.name: Lenny_IL
dmi.board.vendor: IL
dmi.board.version: V1.12
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.12
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.7:svnAcer:pnSpinSP314-54N:pvrV1.12:rvnIL:rnLenny_IL:rvrV1.12:cvnAcer:ct31:cvrV1.12:sku:
dmi.product.family: Spin 3
dmi.product.name: Spin SP314-54N
dmi.product.sku: 
dmi.product.version: V1.12
dmi.sys.vendor: Acer

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


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

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

Title:
  ~/devices

Status in linux package in Ubuntu:
  New

Bug description:
  Touchpad not recognized

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guilherme   1780 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 14:09:35 2022
  InstallationDate: Installed on 2022-10-07 (4 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Spin SP314-54N
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=ce47c382-5d2f-4ad1-966d-cadcfe91cbe7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.name: Lenny_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.12
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd03/15/2021:br1.12:efr1.7:svnAcer:pnSpinSP314-54N:pvrV1.12:rvnIL:rnLenny_IL:rvrV1.12:cvnAcer:ct31:cvrV1.12:sku:
  dmi.product.family: Spin 3
  dmi.product.name: Spin SP314-54N
  dmi.product.sku: 
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992647/+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 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1

[Jimmy]

Ubuntu 22.10 Beta fixed this defect

** Attachment added: "ubuntu22.10_beta_dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990342/+attachment/5623435/+files/ubuntu22.10_beta_dmesg

-- 
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/1990342

Title:
  Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu
  22.04 and Ubuntu 22.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Configuration:
   
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
   CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
   BMC Version  0.48 (Build ID: ESX303K)
   UEFI Version 0.62 (Build ID: ESE105G)
   SSD:931.51GB 7.2K SATA HDD   S471A08RSH20K04054  00LF039
   SSD*2(SATA 0/1):894.25GB SATA SSD
   HDD*2(SATA 2 alias tsata): 1TB SATA HDD
   Boot mode:UEFI
  Reproduce Steps:
   1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set 
to "RAID",save and reboot.
   2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via 
drive 12,13 HDD to create RAID Volume,save and reboot.
   3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 
22.004.1),the raid group under tSATA is not detected.
   4.In the OS,the RAID of the tSATA group is not detected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990342/+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 1991691] Re: cannot change mount namespace

[Ubuntu Foundations Team Bug Bot]

The attachment "kernel patch to apparmor" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  cannot change mount namespace

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Multiple snaps are either broken or "only" display permission denied
  messages.

  slack snap is not starting at all with:

  > update.go:85: cannot change mount namespace according to change
  mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none
  bind,rw,x-snapd.ignore-missing 0 0): cannot inspect
  "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied

  firefox snap does start, but also logs errors:

  
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot 
inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat 
/var/lib/snapd/hostfs/usr/share/doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat 
/var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": 
lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Oct  4 17:29:01 2022
  InstallationDate: Installed on 2017-09-26 (1834 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1991691/+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 1992641] [NEW] stress ng seal regression

[Dimitri John Ledkov]

Public bug reported:

stress ng seal regression

180021:47:23 DEBUG| [stdout] stress-ng: debug: [43108] invoked with 
'./stress-ng -v -t 5 --seal 4 --seal-ops 3000 --ignite-cpu --syslog --verbose 
--verify --oomable' by user 0 'root'
180121:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] stress-ng 0.14.03 g346518caffe5
180221:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] system: Linux riscv64-kinetic 5.19.0-1003-generic #3-Ubuntu SMP Mon Oct 
10 15:09:23 UTC 2022 riscv64
180321:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] RAM total: 7.8G, RAM free: 7.4G, swap free: 1021.4M
180421:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] 8 processors online, 8 processors configured
180521:47:23 DEBUG| [stdout] stress-ng: info:  
[43108] setting to a 5 second run per stressor
180621:47:23 DEBUG| [stdout] stress-ng: info:  
[43108] dispatching hogs: 4 seal
180721:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] cache allocate: using defaults, cannot determine cache level details
180821:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] cache allocate: shared cache buffer size: 2048K
180921:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] starting stressors
181021:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] 4 stressors started
181121:47:23 DEBUG| [stdout] stress-ng: debug: 
[43109] stress-ng-seal: started [43109] (instance 0)
181221:47:23 DEBUG| [stdout] stress-ng: debug: 
[43110] stress-ng-seal: started [43110] (instance 1)
181321:47:23 DEBUG| [stdout] stress-ng: debug: 
[43111] stress-ng-seal: started [43111] (instance 2)
181421:47:23 DEBUG| [stdout] stress-ng: debug: 
[43112] stress-ng-seal: started [43112] (instance 3)
181521:47:23 DEBUG| [stdout] stress-ng: fail:  
[43110] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
181621:47:23 DEBUG| [stdout] stress-ng: fail:  
[43109] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
181721:47:23 DEBUG| [stdout] stress-ng: fail:  
[43111] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
181821:47:23 DEBUG| [stdout] stress-ng: fail:  
[43112] stress-ng-seal: mmap failed, errno=22 (Invalid argument)
181921:47:23 DEBUG| [stdout] stress-ng: debug: 
[43109] stress-ng-seal: exited [43109] (instance 0)
182021:47:23 DEBUG| [stdout] stress-ng: debug: 
[43110] stress-ng-seal: exited [43110] (instance 1)
182121:47:23 DEBUG| [stdout] stress-ng: debug: 
[43112] stress-ng-seal: exited [43112] (instance 3)
182221:47:23 DEBUG| [stdout] stress-ng: debug: 
[43111] stress-ng-seal: exited [43111] (instance 2)
182321:47:23 DEBUG| [stdout] stress-ng: error: 
[43108] process 43109 (stress-ng-seal) terminated with an error, exit status=2 
(stressor failed)
182421:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] process [43109] terminated
182521:47:23 DEBUG| [stdout] stress-ng: error: 
[43108] process 43110 (stress-ng-seal) terminated with an error, exit status=2 
(stressor failed)
182621:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] process [43110] terminated
182721:47:23 DEBUG| [stdout] stress-ng: error: 
[43108] process 43111 (stress-ng-seal) terminated with an error, exit status=2 
(stressor failed)
182821:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] process [43111] terminated
182921:47:23 DEBUG| [stdout] stress-ng: error: 
[43108] process 43112 (stress-ng-seal) terminated with an error, exit status=2 
(stressor failed)
183021:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] process [43112] terminated
183121:47:23 DEBUG| [stdout] stress-ng: debug: 
[43108] metrics-check: all stressor metrics validated and sane
183221:47:23 DEBUG| [stdout] stress-ng: info:  
[43108] unsuccessful run completed in 0.05s
183321:47:23 DEBUG| [stdout]  

potentially related to the
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992484

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux-riscv (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 5.19 kinetic riscv64 stress-smoke-test

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

-- 
You received this bug 

[Kernel-packages] [Bug 1958692] Re: System crashes and reboots every 15min - 2hr

[Justin Moore]

It had been fine for a little while after I replaced the hardware, but
starting maybe a month ago I started seeing it again. Adding to the list
of problem kernels are:

5.14.0-1044-oem
5.15.0-50-generi

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

Title:
  System crashes and reboots every 15min - 2hr

Status in linux-signed-oem-5.14 package in Ubuntu:
  New

Bug description:
  I have a NUC11NAHi5 system running Ubuntu 20.04.3, and every few
  minutes to hours it will crash:

  justin   :0   :0   Fri Jan 21 19:46 - crash  (00:37)
  justin   :0   :0   Fri Jan 21 19:40 - crash  (00:05)
  justin   :0   :0   Fri Jan 21 17:33 - crash  (02:07)
  justin   :0   :0   Fri Jan 21 17:16 - crash  (00:07)
  justin   :0   :0   Fri Jan 21 17:13 - crash  (00:02)
  justin   :0   :0   Fri Jan 21 16:54 - crash  (00:19)
  justin   :0   :0   Fri Jan 21 16:25 - crash  (00:28)
  justin   :0   :0   Fri Jan 21 16:18 - crash  (00:06)
  justin   :0   :0   Fri Jan 21 16:11 - crash  (00:07)
  justin   :0   :0   Fri Jan 21 15:46 - crash  (00:24)

  When it comes back up I see the following errors in journalctl:

  kernel: BERT: Error records from previous boot:
  kernel: [Hardware Error]: event severity: fatal
  kernel: [Hardware Error]:  Error 0, type: fatal
  kernel: [Hardware Error]:   section_type: Firmware Error Record Reference
  kernel: [Hardware Error]:   Firmware Error Record Type: SOC Firmware Error 
Record Type2
  kernel: [Hardware Error]:   Revision: 2
  kernel: [Hardware Error]:   Record Identifier: 
8f87f311-c998-4d9e-a0c4-6065518c4f6d

  followed by a large hex dump. It could be related to this issue:
  
https://community.intel.com/t5/Processors/Frequent-crashes-on-i5-11500/td-p/1280709

  The BIOS is up-to-date, as is the intel microcode package. It doesn't
  seem to matter which kernel I use. I'm using the OEM one since the
  regular kernels for 20.04.3 (a) also have this problem, and (b) have
  broken IR support (https://askubuntu.com/questions/1380500/kernel-rc-
  rc0-receive-overflow).

  System: NUC11PAHi5
  SKU: RNUC11PAHi5000
  BIOS: PATGL357.0041.2021.0811.1505
  Board: NUC11PABi5
  CPU: i5-1135G7

  I'm not sure if it's a kernel issue, BIOS issue, microcode issue, or
  hardware issue, so I decided to start here. Let me know how else I can
  help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1020-oem 5.14.0-1020.22
  ProcVersionSignature: Ubuntu 5.14.0-1020.22-oem 5.14.20
  Uname: Linux 5.14.0-1020-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jan 21 20:44:43 2022
  InstallationDate: Installed on 2022-01-08 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1958692/+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 1992640] [NEW] memfd test failed

[Dimitri John Ledkov]

Public bug reported:

http://10.246.75.167/d2022.07.18/kinetic/linux-riscv/5.19.0-1002.2/sru-
generic-metal-riscv64-kinetic.riscv64-ubuntu_kernel_selftests-
log.html#memfd:memfd_test-start

178317:39:06 DEBUG| Running 'make run_tests -C 
memfd TEST_PROGS=memfd_test TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
178417:39:07 DEBUG| [stdout] make: Entering 
directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
178517:39:07 DEBUG| [stdout] TAP version 13
178617:39:08 DEBUG| [stdout] 1..1
178717:39:08 DEBUG| [stdout] # selftests: memfd: 
memfd_test
178817:39:09 DEBUG| [stdout] # memfd: CREATE
178917:39:09 DEBUG| [stdout] # memfd: BASIC
179017:39:09 DEBUG| [stdout] # memfd: SEAL-WRITE
179117:39:09 DEBUG| [stdout] # memfd: 
SEAL-FUTURE-WRITE
179217:39:09 DEBUG| [stdout] # memfd: CREATE
179317:39:09 DEBUG| [stdout] # memfd: BASIC
179417:39:09 DEBUG| [stdout] # memfd: SEAL-WRITE
179517:39:09 DEBUG| [stdout] # memfd: 
SEAL-FUTURE-WRITE
179617:39:09 DEBUG| [stdout] # memfd: SEAL-SHRINK
179717:39:09 DEBUG| [stdout] # memfd: SEAL-GROW
179817:39:09 DEBUG| [stdout] # memfd: SEAL-RESIZE
179917:39:09 DEBUG| [stdout] # memfd: SHARE-DUP 
180017:39:09 DEBUG| [stdout] # memfd: SHARE-MMAP 
180117:39:09 DEBUG| [stdout] # memfd: SHARE-OPEN 
180217:39:09 DEBUG| [stdout] # memfd: SHARE-FORK 
180317:39:09 DEBUG| [stdout] # memfd: SHARE-DUP 
(shared file-table)
180417:39:09 DEBUG| [stdout] # memfd: SHARE-MMAP 
(shared file-table)
180517:39:09 DEBUG| [stdout] # memfd: SHARE-OPEN 
(shared file-table)
180617:39:09 DEBUG| [stdout] # memfd: SHARE-FORK 
(shared file-table)
180717:39:09 DEBUG| [stdout] # memfd: DONE
180817:39:09 DEBUG| [stdout] ok 1 selftests: memfd: 
memfd_test

http://10.246.75.167/d2022.09.27/kinetic/linux-riscv/5.19.0-1003.3/sru-
generic-metal-riscv64-kinetic.riscv64-ubuntu_kernel_selftests-
log.html#memfd:memfd_test-start

405417:14:44 DEBUG| Running 'make run_tests -C 
memfd TEST_PROGS=memfd_test TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
405517:14:45 DEBUG| [stdout] make: Entering 
directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
405617:14:45 DEBUG| [stdout] TAP version 13
405717:14:46 DEBUG| [stdout] 1..1
405817:14:46 DEBUG| [stdout] # selftests: memfd: 
memfd_test
405917:14:47 DEBUG| [stdout] # memfd: CREATE
406017:14:47 DEBUG| [stdout] # memfd: BASIC
406117:14:47 DEBUG| [stdout] # memfd: SEAL-WRITE
406217:14:47 DEBUG| [stdout] # memfd: 
SEAL-FUTURE-WRITE
406317:14:50 DEBUG| [stdout] # /usr/bin/timeout: 
the monitored command dumped core
406417:14:50 DEBUG| [stdout] # Aborted
406517:14:50 DEBUG| [stdout] not ok 1 selftests: 
memfd: memfd_test # exit=134

memfd regressed.

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux-riscv (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 5.19 kinetic riscv64 ubuntu-kernel-selftests

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

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

Title:
  memfd test failed

Status in ubuntu-kernel-tests:
  New
Status in linux-riscv package in Ubuntu:
  New

Bug description:
  http://10.246.75.167/d2022.07.18/kinetic/linux-
  riscv/5.19.0-1002.2/sru-generic-metal-
  riscv64-kinetic.riscv64-ubuntu_kernel_selftests-
  log.html#memfd:memfd_test-start

178317:39:06 DEBUG| Running 'make run_tests -C 
memfd TEST_PROGS=memfd_test TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
178417:39:07 DEBUG| [stdout] make: Entering 
directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
178517:39:07 DEBUG| [stdout] TAP version 13
1786

[Kernel-packages] [Bug 1991691] Re: cannot change mount namespace

[John Johansen]

Note: this bug report has two parts to it.

1. Snap issue: mkdir failing covered by bug 1951210 and fixed in
https://github.com/snapcore/snapd/pull/12127

2. apparmor module issue in the kernel, covered by patch in #18


** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => John Johansen (jjohansen)

-- 
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/1991691

Title:
  cannot change mount namespace

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Multiple snaps are either broken or "only" display permission denied
  messages.

  slack snap is not starting at all with:

  > update.go:85: cannot change mount namespace according to change
  mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none
  bind,rw,x-snapd.ignore-missing 0 0): cannot inspect
  "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied

  firefox snap does start, but also logs errors:

  
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot 
inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat 
/var/lib/snapd/hostfs/usr/share/doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat 
/var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": 
lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Oct  4 17:29:01 2022
  InstallationDate: Installed on 2017-09-26 (1834 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1991691/+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 1991691] Re: cannot change mount namespace

[John Johansen]

The following patch fixes the issue for me.

** Patch added: "kernel patch to apparmor"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1991691/+attachment/5623421/+files/0001-UBUNTU-SAUCE-apparmor-Fix-getattr-mediation-causing-.patch

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

Title:
  cannot change mount namespace

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Multiple snaps are either broken or "only" display permission denied
  messages.

  slack snap is not starting at all with:

  > update.go:85: cannot change mount namespace according to change
  mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none
  bind,rw,x-snapd.ignore-missing 0 0): cannot inspect
  "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied

  firefox snap does start, but also logs errors:

  
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot 
inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat 
/var/lib/snapd/hostfs/usr/share/doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat 
/var/lib/snapd/hostfs/usr/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none 
bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat 
/usr/local/share/fonts: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none 
bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission 
denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none 
bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): 
cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat 
/var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none 
bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": 
lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied
  update.go:85: cannot change mount namespace according to change mount 
(/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none 
bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat 
/run/user/1000/doc: permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Oct  4 17:29:01 2022
  InstallationDate: Installed on 2017-09-26 (1834 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago)

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


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

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

[Julian Andres Klode]

It does yeah, and obviously that's a solver bug that's going to need
some more work to root cause.


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

** Changed in: apt (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Bug description:
  apt/jammy

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

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

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

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

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


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

[Kernel-packages] [Bug 1992593] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1992593

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67

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


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

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

[Lukas Märdian]

Does this also happen when you use the more recent version 2.4.8 from
the jammy-updates pocket?

** Also affects: nvidia-graphics-drivers-450-server (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-470-server (Ubuntu)
   Importance: Undecided
   Status: New

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

** Tags added: foundations-triage-discuss

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

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

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

Bug description:
  apt/jammy

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

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

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

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

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


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

[Kernel-packages] [Bug 1992593] [NEW] HDMI port not working after upgrade to 5.15.0-50-generic

[ali]

Public bug reported:

Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
5.15.0-50. After rebooting the second monitor was not getting detected
(connected via HDMI cable). When i booted back from 5.15.0-46, the
monitor worked again.

I am running Ubuntu 20.04.5 LTS

  *-display
   description: VGA compatible controller
   product: Renoir
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:04:00.0
   version: c6
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
   configuration: driver=amdgpu latency=0
   resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67

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

** Description changed:

  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
- (connected va HDMI cable). When i booted back from 5.15.0-46, i monitor
- worked again.
+ (connected via HDMI cable). When i booted back from 5.15.0-46, the
+ monitor worked again.
  
  I am running Ubuntu 20.04.5 LTS
  
- 
-   *-display 
-description: VGA compatible controller
-product: Renoir
-vendor: Advanced Micro Devices, Inc. [AMD/ATI]
-physical id: 0
-bus info: pci@:04:00.0
-version: c6
-width: 64 bits
-clock: 33MHz
-capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
-configuration: driver=amdgpu latency=0
-resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67
+   *-display
+    description: VGA compatible controller
+    product: Renoir
+    vendor: Advanced Micro Devices, Inc. [AMD/ATI]
+    physical id: 0
+    bus info: pci@:04:00.0
+    version: c6
+    width: 64 bits
+    clock: 33MHz
+    capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
+    configuration: driver=amdgpu latency=0
+    resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67

-- 
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/1992593

Title:
  HDMI port not working after upgrade to 5.15.0-50-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Yesterday i upgraded the linux kernel from 5.15.0-46-generic to
  5.15.0-50. After rebooting the second monitor was not getting detected
  (connected via HDMI cable). When i booted back from 5.15.0-46, the
  monitor worked again.

  I am running Ubuntu 20.04.5 LTS

    *-display
     description: VGA compatible controller
     product: Renoir
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:04:00.0
     version: c6
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi msix vga_controller bus_master cap_list
     configuration: driver=amdgpu latency=0
     resources: irq:45 memory:d000-dfff memory:e000-e01f 
ioport:e000(size=256) memory:fe60-fe67

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


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

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Dimitri John Ledkov]

./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev

when booting containers

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

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Dimitri John Ledkov]

./src/nspawn/nspawn-mount.c missing NO_EXEC on /dev
./src/shared/mount-setup.c missing NO_EXEC on /dev

when booting containers

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec

[Lukas Märdian]

Setting the systemd bug task to "Invalid", as this is being handled in
the kernel.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu Focal)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu Jammy)
   Status: Confirmed => Invalid

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

Title:
  dev file system is mounted without nosuid or noexec

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in systemd source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in systemd source package in Jammy:
  Invalid

Bug description:
  [ SRU TEMPLATE ]
  [ Impact ]

   * nosuid, and noexec bits are not set on /dev
   * This has the potential for nefarious actors to use this as an avenue for 
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more 
discussion around this.
   * It is not best security practice.

  [ Test Plan ]

     1.Boot a Canonical Supplied EC2 instance
     2.Check the mount options for /dev.
     3.You will notice the lack of nosuid and noexec on /dev.

  [ Where problems could occur ]

   * As of 2022/10/06, I need to test this, but don't know how to build
  -aws flavored ubuntu kernels. Instructions welcome.  I'm holding off
  on adding SRU tags until I can actually get this tested.

   * If this is applied to non initramfs-less kernels it could potentially 
cause a regression for very old hardware that does nefarious things with 
memory.  For a larger discussion about that see:
  
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/

   * Low risk if a driver depends on /dev allowing suid or exec this
  might prevent boot.  That being said, all kernels that have been
  booting with an initramfs have been getting nosuid, and noexec set so
  hopefully we can consider that risk fairly well tested.

  [ Other Info ]

   * Patch is accepted into 5.17, and will drop out quickly
   * Any server booting with an initramfs already has nosuid, and noexec set, 
so hopefully

  <<< ORIGINAL TEXT 

  This is similar to
  https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.

  I discovered that my ec2 instances based off of Canonical supplied AMI
  ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without
  the nosuid option.

  https://us-east-2.console.aws.amazon.com/ec2/home?region=us-
  east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee

  My usb installed 20.04.4 home machine does not have this problem, but
  it has been installed for quite some time.  My 22.04 laptop machine
  also does not have this issue.

  Reproduce.
  Start an ec2 instance based off of ami-0a23d90349664c6ee.
  $ mount | grep devtmpfs
  nosuid is not found in the options list.

  I've checked the initrd, and /etc/init.d/udev script and all places I
  know of where dev gets mounted set nosuid, so it's non-obvious what
  boot code-path is being taken that results in nosuid missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.18
  ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53
  Uname: Linux 5.15.0-1020-aws x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules
  Date: Thu Oct  6 17:39:42 2022
  Ec2AMI: ami-0a23d90349664c6ee
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-2c
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:

  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Xen HVM domU
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws 
root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 
console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.release: 4.2
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1991220] Re: "dpc: probe of 0000:00:10.0:pcie010 failed with error -524" errors are found in Ubuntu18.04.6

[conie chang]

I re-installed Ubuntu 18.04.6 HWE version, the dpc errros do not exist
in dmesg and /var/log/syslogs.

We can close this bug. Thank you all.

The output as below===
root@ubuntu:/home/conie# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.6 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.6 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
root@ubuntu:/home/conie# uname -mrs
Linux 5.4.0-84-generic x86_64
root@ubuntu:/home/conie# hwe-support-status
Your Hardware Enablement Stack (HWE) is supported until April 2023.
root@ubuntu:/home/conie# grep -i dpc /var/log/syslog
root@ubuntu:/home/conie# dmesg|grep -i dpc
root@ubuntu:/home/conie#


** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1991220

Title:
  "dpc: probe of :00:10.0:pcie010 failed with error -524" errors are
  found in Ubuntu18.04.6

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  1. Power on SUT and install Ubuntu 18.04.6 
(ubuntu-18.04.6-live-server-amd64.iso)
  2. Boot into OS then run dmesg to check if there are unexpected errors or 
warnings. (=> failed, there are dpc errors in dmesg:
  [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524
  [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524
  [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524
  [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524
  [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524
  [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524
  [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524
  [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524
  [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524
  [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 
  )

  Expected behaviors: 
  2. There are no unexpected errors or warnings in dmesg.

  Current behaviors: 
  2. Tthere are dpc errors in dmesg:
  [1.178079] dpc: probe of :00:10.0:pcie010 failed with error -524
  [1.178083] dpc: probe of :00:11.0:pcie010 failed with error -524
  [1.178087] dpc: probe of :00:12.0:pcie010 failed with error -524
  [1.178090] dpc: probe of :00:13.0:pcie010 failed with error -524
  [1.178094] dpc: probe of :00:14.0:pcie010 failed with error -524
  [1.178097] dpc: probe of :15:02.0:pcie010 failed with error -524
  [1.178101] dpc: probe of :8c:02.0:pcie010 failed with error -524
  [1.178104] dpc: probe of :8c:03.0:pcie010 failed with error -524
  [1.178108] dpc: probe of :8c:04.0:pcie010 failed with error -524
  [1.178111] dpc: probe of :8c:05.0:pcie010 failed with error -524 

  
  Hardware information:
  Server MTM: SE350/360 V2 Hakuba (Icelake -D)
  OS installed: ubuntu-18.04.6-live-server-amd64
  BMC Version: 0.90 (Build ID: USX313E)
  UEFI Version: 1.10 (Build ID: IYE101N)
  LXPM Version: 4.00 (Build ID: EAL103Y)
  CPU: Intel(R) Xeon(R) D-2775TE CPU @ 2.00GHz
  DIMM: ThinkSystem 32GB TruDDR4 3200 MHz (2Rx4 1.2V) RDIMM - SAM*1
  IO Config:
  I/O Board: 25Gb/10Gb I/O Board
  RAID: NA
  NIC: uptech usb rj45
  Storage:
  M.2 SSD: ThinkSystem M.2 7450P 960GB Read Intensive NVMe PCIe 4.0 x4 NHS SSD, 
2280*2
  PSU: Mean Well SE-600-48 600W/48V

  
  Debug information:
  1. Double confirm with 20.04.5 and 22.04 and there are no this errors in 
those two Ubuntu OS.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  3 02:10 seq
   crw-rw 1 root audio 116, 33 Oct  3 02:10 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.28
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2022-09-29 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: LENOVO ThinkEdge SE350 V2 CPU Planar
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-193-generic 
root=UUID=dac195ba-5207-49c4-b324-3daaebd2b0f0 ro
  ProcVersionSignature: 

[Kernel-packages] [Bug 1992484] Re: Kernel regresses openjdk on riscv64

[Stefan Bader]

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

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Jammy)
   Status: New => Fix Committed

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

Title:
  Kernel regresses openjdk on riscv64

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  Over at https://lore.kernel.org/linux-
  riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2
  it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses
  userspace (openjdk) on riscv64.

  This commit has already been released in v6.0 kernel upstream, but has
  also been included in the stable patch series all the way back to
  v4.19.y

  There is a proposed fix for this at https://lore.kernel.org/linux-
  riscv/20220915193702.2201018-1-abres...@rivosinc.com/ which has not
  yet been merged upstream or in stable series.

  Please review and merge above proposed fix, or please revert
  2139619bcad7ac44cc8f6f749089120594056613 to stop the regression
  spreading to all the distributions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992484/+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 1983656] Re: iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

[Stefan Bader]

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

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

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

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

Title:
  iavf: SR-IOV VFs error with no traffic flow when MTU greater than 1500

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1983656

  [Impact]

  Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b]
  get no traffic flow and produce error messages in both the host and
  guest during network configuration.

  Environment: Ubuntu OpenStack Focal-Ussuri with OVN
  Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE
  Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy

  Host Error Messages:
  ice :98:00.1: VF 7 failed opcode 6, retval: -5

  Guest Error Messages:
  iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6

  In the context of these errors "6" refers to the value of
  VIRTCHNL_OP_CONFIG_VSI_QUEUES

  It was found in these cases that the VM is able to successfully
  transmit packets but never receives any and the RX packet drop
  counters for the VF in "ip link" on the host increase equal to the RX
  packet count.

  There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d
  claiming to resolve this error in some cases. It is already included
  in 5.15.0-41-generic and did not resolve the issue.

  The following conditions are required to trigger the bug:
  - A port VLAN must be assigned by the host
  - The MTU must be set >1500 by the guest

  There is no workaround, Intel E810 SR-IOV VFs with MTU >1500 cannot be
  used without these patches.

  [Fix]

  iavf currently sets the maximum packet size to IAVF_MAX_RXBUFFER, but
  on the previous ice driver, it was decremented by VLAN_HLEN to make
  some space to fit the VLAN header. This doesn't happen on iavf, and we
  end up trying to use a packet size larger than IAVF_MAX_RXBUFFER,
  causing the IAVF_ERR_PARAM error.

  The fix is to change the maximum packet size from IAVF_MAX_RXBUFFER to
  max_mtu received from the PF via GET_VF_RESOURCES msg.

  Also pick up a necessary commit for i40e to announce the correct
  maximum packet size by GET_VF_RESOURCES msg.

  This has been fixed by the following commits:

  commit 399c98c4dc50b7eb7e9f24da7ffdda6f025676ef
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:35 2022 +0200
  Subject: iavf: Fix set max MTU size with port VLAN and jumbo frames
  Link: 
https://github.com/torvalds/linux/commit/399c98c4dc50b7eb7e9f24da7ffdda6f025676ef

  commit 372539def2824c43b6afe2403045b140f65c5acc
  Author: Michal Jaron 
  Date:   Tue Sep 13 15:38:36 2022 +0200
  Subject: i40e: Fix VF set max MTU size
  Link: 
https://github.com/torvalds/linux/commit/372539def2824c43b6afe2403045b140f65c5acc

  A test kernel is available in the following ppa:

  https://launchpad.net/~arif-ali/+archive/ubuntu/sf00343742

  If you install the test kernel to a compute host and VM, when you
  attach a VF and set the MTU to 9000, it succeeds, and traffic can
  flow.

  [Test Plan]

  Create a Focal VM and assign an Intel E810 (ice) SR-IOV VF with a port
  vlan:

  Openstack works, as does creating a VM directly with uvtool/libvirt.

  $ uvt-kvm create focal-test release=focal

  Using the document to understand SRIOV basics in the link below

  
https://www.intel.com/content/www/us/en/developer/articles/technical/configure-
  sr-iov-network-virtual-functions-in-linux-kvm.html

  The following command show all the bus info for all the network
  devices

  $ lshw -c network -businfo

  Choose one, as shown below

  pci@:17:01.4  ens2f0v4 networkEthernet Adaptive
  Virtual Function

  We can then add the following into the XML definition via “virsh edit
  focal-test”

  
    
  
    
   
  
    
  

  Then we stop and start the VM via "virsh shutdown focal-test" and then
  "virsh start focal-test". We can then login to the VM using the
  command below

  $ uvt-kvm ssh focal-test

  Once you have logged in, run the following ip parameters

  $ sudo ip a a 192.168.1.7/24 dev enp7s0
  $ sudo ip link set up dev enp7s0
  $ sudo ip link set mtu 9000 dev enp7s0

  Now check dmesg, and we will find the error

  [   61.529605] iavf :07:00.0: PF returned error -5
  (IAVF_ERR_PARAM) to our request 6

  Setting the IP and bringing the link up

  [   36.228877] iavf :07:00.0 enp7s0: NIC Link is Up Speed is 25 Gbps Full 
Duplex
  [   36.228887] IPv6: ADDRCONF(NETDEV_CHANGE): enp7s0: link becomes ready
  [   

Re: [Kernel-packages] [Bug 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot

[Michael Amplatz]

I had an update yesterday on Ubuntu 20.04.5. Today I recognized that the 
Touchpad works. SOLVED!!!

After 2,5 years I am lucky.

Michael Amplatz


Am 05.06.22 um 19:18 schrieb Noctis Bennington:
> I tried with pci=nocrs on Linux 5.18 and now it works, just to let you
> know.
>

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

Title:
  MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
  from any given boot

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux-signed-hwe package in Ubuntu:
  In Progress
Status in linux-signed-hwe package in Fedora:
  New

Bug description:
  Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
  at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
  14IIL05 81YH' from first system start on.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tilman 1607 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 21:22:22 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81YH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DSCN23WW(V1.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 5 14IIL05
  dmi.modalias: 
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
  dmi.product.family: IdeaPad 5 14IIL05
  dmi.product.name: 81YH
  dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
  dmi.product.version: IdeaPad 5 14IIL05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1878279/+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 1992584] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: próba nadpisania dzielonego "/etc/OpenCL/vendors/nvidia.icd", który różni się od innych k

[Marcin Szymanski]

Public bug reported:

Nvidia driver installation problem

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnvidia-compute-390 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Oct 12 10:50:11 2022
ErrorMessage: próba nadpisania dzielonego "/etc/OpenCL/vendors/nvidia.icd", 
który różni się od innych kopii pakietu libnvidia-compute-390:amd64
InstallationDate: Installed on 2022-10-10 (1 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.8
SourcePackage: nvidia-graphics-drivers-390
Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 
próba nadpisania dzielonego "/etc/OpenCL/vendors/nvidia.icd", który różni się 
od innych kopii pakietu libnvidia-compute-390:amd64
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: próba nadpisania dzielonego
  "/etc/OpenCL/vendors/nvidia.icd", który różni się od innych kopii
  pakietu libnvidia-compute-390:amd64

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  Nvidia driver installation problem

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libnvidia-compute-390 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 12 10:50:11 2022
  ErrorMessage: próba nadpisania dzielonego "/etc/OpenCL/vendors/nvidia.icd", 
który różni się od innych kopii pakietu libnvidia-compute-390:amd64
  InstallationDate: Installed on 2022-10-10 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: próba nadpisania dzielonego "/etc/OpenCL/vendors/nvidia.icd", 
który różni się od innych kopii pakietu libnvidia-compute-390:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1992584/+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 1992580] ProcCpuinfoMinimal.txt

[Gijs Peskens]

apport information

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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

[Gijs Peskens]

apport information

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

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

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

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

[Gijs Peskens]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1992580/+attachment/5623382/+files/Dependencies.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/1992580

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+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 1992580] Re: i915 DG1 fails to load

[Gijs Peskens]

The card initializes properly on linux-image-
unsigned-6.0.0-06-generic


** Attachment added: "Good boot with kernel 6.0"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992580/+attachment/5623380/+files/i915_good_kernel_6.0

** Tags added: apport-collected kinetic wayland-session

** Description changed:

  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu2
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2020-12-06 (674 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ Package: linux
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
+ Tags:  wayland-session kinetic
+ Uname: Linux 5.19.0-19-generic x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
+ UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
+ _MarkForUpload: True

-- 
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/1992580

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+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 1992572] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Samba crashes in gnutls at logon

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows a lot of:

  [ 8665.587829] traps: smbd[4612] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.617605] traps: smbd[4614] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.649484] traps: smbd[4616] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.676820] traps: smbd[4618] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.701019] traps: smbd[4620] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.726626] traps: smbd[4622] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.747612] traps: smbd[4624] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.768710] traps: smbd[4626] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.790433] traps: smbd[4628] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
  [ 8665.821738] traps: smbd[4630] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]

  entries and logon from an windows 10 workstation failes.

  Mainline Kernel version 5.15.71 works!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Okt 12 09:35 seq
   crw-rw+ 1 root audio 116, 33 Okt 12 09:35 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  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:
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 09:41:59 2022
  HibernationDevice: RESUME=UUID=3d1cb136-8319-4996-b9f7-44a9c63cad8c
  InstallationDate: Installed on 2015-07-06 (2654 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=1494f24d-65e5-435e-84d8-eed5b54561ab ro text
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-50-generic N/A
   linux-backports-modules-5.15.0-50-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-09-28 (13 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/09/2019:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  

[Kernel-packages] [Bug 1992580] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1992580

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2020-12-06 (674 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: linux
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  Tags:  wayland-session kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-09-19 (22 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo 
wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+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 1973098] Re: Intermittent freezing and LSPCON init failed kernel messages

[Daniel van Vugt]

Now also reported in kernel 5.15.0-50.56-generic (bug 1992563)

** Tags added: jammy regression-update

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

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

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

Title:
  Intermittent freezing and LSPCON init failed kernel messages

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-oem-5.14 package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Lenovo ThinkPad model 20ST0055AU

  Boot messages show:
  [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on 
minor 0

  During normal operation there will intermittently be a freeze for a
  second or two and then more of these messages display in the kernel
  logs:

  [  505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D
  [  506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  [  506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  The system will then become operational again.

  The system is still usable, but it is annoying.

  I've switched onto this OEM kernel from the generic kernel (5.13), as
  I had other problems with 5.13 regarding external displays not coming
  back after idle timeouts.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40
  ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21
  Uname: Linux 5.14.0-1036-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 10:29:31 2022
  InstallationDate: Installed on 2021-05-05 (371 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+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 1992580] Re: i915 DG1 fails to load

[Gijs Peskens]

Sigh. It somehow incorrectly selected initramfs-tools. That's totally
unrelated. No idea on how to remove it.

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+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 1992563] Re: Boot freeze

[Daniel van Vugt]

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

Looks like bug 1973098 is the same.

** Tags added: hybrid i915 multigpu nvidia

** Tags added: regression-update

** Summary changed:

- Boot freeze
+ Boot freeze - [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon - 
[drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

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

** This bug has been marked a duplicate of bug 1973098
   Intermittent freezing and LSPCON init failed kernel messages

-- 
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/1992563

Title:
  Boot freeze - [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon
  - [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

Status in linux package in Ubuntu:
  New

Bug description:
  After recent update during boot Ubuntu freezes or I should wait a
  couple of minutes before gui starts.

  Laptop is Ubuntu certified (Thinkpad 17p gen1)

  Dmesg shows the following errors:
   [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
  Uname: Linux 5.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 
14:00:58 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 09:37:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/515.65.01, 5.15.0-48-generic, x86_64: installed
   nvidia/515.65.01, 5.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22bb]
   NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22bb]
  InstallationDate: Installed on 2020-11-20 (690 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20SN002WRT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=464ea21f-3e4f-4d24-97b2-deb2a870e063 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N30ET43W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SN002WRT
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SN002WRT:pvrThinkPadP17Gen1:rvnLENOVO:rn20SN002WRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:
  dmi.product.family: ThinkPad P17 Gen 1
  dmi.product.name: 20SN002WRT
  dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
  dmi.product.version: ThinkPad P17 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  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:

[Kernel-packages] [Bug 1992580] Re: i915 DG1 fails to load

[Gijs Peskens]

** Attachment added: "lspci gpu's"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+attachment/5623378/+files/lspci_gpu

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

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

Title:
  i915 DG1 fails to load

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  On kernel 5.19 in Ubuntu Jammy i915 fails to initialize Intel DG1 GPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992580/+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 1992563] [NEW] Boot freeze - [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon - [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After recent update during boot Ubuntu freezes or I should wait a couple
of minutes before gui starts.

Laptop is Ubuntu certified (Thinkpad 17p gen1)

Dmesg shows the following errors:
 [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  515.65.01  Wed Jul 20 14:00:58 
UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 12 09:37:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/515.65.01, 5.15.0-48-generic, x86_64: installed
 nvidia/515.65.01, 5.15.0-50-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22bb]
 NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22bb]
InstallationDate: Installed on 2020-11-20 (690 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20SN002WRT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=464ea21f-3e4f-4d24-97b2-deb2a870e063 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/08/2021
dmi.bios.release: 1.26
dmi.bios.vendor: LENOVO
dmi.bios.version: N30ET43W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20SN002WRT
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnLENOVO:bvrN30ET43W(1.26):bd11/08/2021:br1.26:efr1.16:svnLENOVO:pn20SN002WRT:pvrThinkPadP17Gen1:rvnLENOVO:rn20SN002WRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20SN_BU_Think_FM_ThinkPadP17Gen1:
dmi.product.family: ThinkPad P17 Gen 1
dmi.product.name: 20SN002WRT
dmi.product.sku: LENOVO_MT_20SN_BU_Think_FM_ThinkPad P17 Gen 1
dmi.product.version: ThinkPad P17 Gen 1
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
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

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


** Tags: amd64 apport-bug freeze hybrid i915 jammy multigpu nvidia 
regression-update ubuntu
-- 
Boot freeze - [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon - 
[drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D
https://bugs.launchpad.net/bugs/1992563
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1992572] [NEW] Samba crashes in gnutls at logon

[Peter Metzler]

Public bug reported:

dmesg shows a lot of:

[ 8665.587829] traps: smbd[4612] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.617605] traps: smbd[4614] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.649484] traps: smbd[4616] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.676820] traps: smbd[4618] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.701019] traps: smbd[4620] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.726626] traps: smbd[4622] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.747612] traps: smbd[4624] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.768710] traps: smbd[4626] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.790433] traps: smbd[4628] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]
[ 8665.821738] traps: smbd[4630] trap invalid opcode ip:7fb0ab12f54a 
sp:7ffc9ba52c80 error:0 in libgnutls.so.30.31.0[7fb0ab008000+129000]

entries and logon from an windows 10 workstation failes.

Mainline Kernel version 5.15.71 works!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-50-generic 5.15.0-50.56
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
Uname: Linux 5.15.0-50-generic x86_64
AlsaDevices:
 total 0
 crw-rw+ 1 root audio 116,  1 Okt 12 09:35 seq
 crw-rw+ 1 root audio 116, 33 Okt 12 09:35 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
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:
CasperMD5CheckResult: unknown
Date: Wed Oct 12 09:41:59 2022
HibernationDevice: RESUME=UUID=3d1cb136-8319-4996-b9f7-44a9c63cad8c
InstallationDate: Installed on 2015-07-06 (2654 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
 
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic 
root=UUID=1494f24d-65e5-435e-84d8-eed5b54561ab ro text
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-50-generic N/A
 linux-backports-modules-5.15.0-50-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-09-28 (13 days ago)
dmi.bios.date: 12/09/2019
dmi.bios.release: 4.6
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/09/2019:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2016-03-11T12:54:54

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


** Tags: amd64 apport-bug jammy

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

[Kernel-packages] [Bug 1992564] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1992564/+attachment/5623328/+files/RfKill.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/1992564

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1992564/+attachment/5623322/+files/PaInfo.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/1992564

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1992564/+attachment/5623325/+files/ProcEnviron.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/1992564

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1992564/+attachment/5623314/+files/AudioDevicesInUse.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/1992564

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1992564/+attachment/5623315/+files/CurrentDmesg.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/1992564

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

[Frode Nordahl]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1992564/+attachment/5623316/+files/IwConfig.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/1992564

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-19-generic N/A
   linux-backports-modules-5.19.0-19-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  Tags:  kinetic
  Uname: Linux 5.19.0-19-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 03/04/2022
  dmi.bios.release: 16.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG ZENITH II EXTREME ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+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 1992564] Re: [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working

[Frode Nordahl]

apport information

** Tags added: apport-collected kinetic

** Description changed:

  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic
  
  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -
  
  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm
  
  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied
  
  Downgrading to 5.19.0-18 makes it work again
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.23.1-0ubuntu2
+ Architecture: amd64
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2021-01-18 (631 days ago)
+ InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
+ MachineType: ASUS System Product Name
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB: 0 amdgpudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-19-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nvidia-drm.modeset=1 
crashkernel=512M-:192M vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-5.19.0-19-generic N/A
+  linux-backports-modules-5.19.0-19-generic  N/A
+  linux-firmware 20220923.gitf09bebf3-0ubuntu1
+ Tags:  kinetic
+ Uname: Linux 5.19.0-19-generic x86_64
+ UpgradeStatus: Upgraded to kinetic on 2022-05-09 (156 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 03/04/2022
+ dmi.bios.release: 16.3
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1603
+ dmi.board.asset.tag: Default string
+ dmi.board.name: ROG ZENITH II EXTREME ALPHA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREMEALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.sku: SKU
+ dmi.product.version: System Version
+ dmi.sys.vendor: ASUS

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1992564/+attachment/5623313/+files/AlsaInfo.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/1992564

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-01-18 (631 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201230)
  MachineType: ASUS System Product Name
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1992564] [NEW] [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not working

[Frode Nordahl]

Public bug reported:

$ uname -a
Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Kinetic Kudu (development branch)
Release:22.10
Codename:   kinetic

$ snap info lxd | grep ^installed
installed:  5.6-794016a  (23680) 142MB -

$ lxc storage show pool
config:
  lvm.thinpool_name: lxd-pool
  lvm.use_thinpool: "true"
  lvm.vg.force_reuse: "true"
  lvm.vg_name: vgubuntu
  source: vgubuntu
  volatile.initial_source: vgubuntu
  volume.lvm.stripes: "3"
description: ""
name: pool
driver: lvm

$ lxc start actual-beagle
Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

Downgrading to 5.19.0-18 makes it work again

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

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

Title:
  [kinetic] 5.19.0-19 kernel, lxd virtual-machine with block device not
  working

Status in linux package in Ubuntu:
  New

Bug description:
  $ uname -a
  Linux frode-threadripper 5.19.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Tue 
Sep 27 16:03:25 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Kinetic Kudu (development branch)
  Release:  22.10
  Codename: kinetic

  $ snap info lxd | grep ^installed
  installed:  5.6-794016a  (23680) 142MB -

  $ lxc storage show pool
  config:
lvm.thinpool_name: lxd-pool
lvm.use_thinpool: "true"
lvm.vg.force_reuse: "true"
lvm.vg_name: vgubuntu
source: vgubuntu
volatile.initial_source: vgubuntu
volume.lvm.stripes: "3"
  description: ""
  name: pool
  driver: lvm

  $ lxc start actual-beagle
  Error: Failed setting up device via monitor: Failed adding block device for 
disk device "root": Failed adding block device: The device is not writable: 
Permission denied

  Downgrading to 5.19.0-18 makes it work again

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992564/+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 1990700] Re: Fibocom WWAN FM350-GL suspend error (notebook not suspend)

[Muralidharan]

Hi Vicamo,

We wanted to request you to take this attached patch in the email and
let us know if this patch helps in this suspend resume issue.

diff -Naur t7xx/t7xx_pci.c t7xx_new/t7xx_pci.c
--- t7xx/t7xx_pci.c 2022-06-27 11:56:21.240049223 +0530
+++ t7xx_new/t7xx_pci.c 2022-06-27 19:20:19.120801177 +0530
@@ -308,13 +308,6 @@
   goto abort_suspend;
  }

- ret = t7xx_send_pm_request(t7xx_dev, H2D_CH_SUSPEND_REQ_AP);
- if (ret) {
- t7xx_send_pm_request(t7xx_dev, H2D_CH_RESUME_REQ);
- dev_err(>dev, "[PM] SAP suspend error: %d\n", ret);
- goto abort_suspend;
- }
-
  list_for_each_entry(entity, _dev->md_pm_entities, entity) {
   if (entity->suspend_late)
entity->suspend_late(t7xx_dev, entity->entity_param);

Thanks and Best Regards,
Murali

-- 
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/1990700

Title:
   Fibocom WWAN FM350-GL suspend error (notebook not suspend)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module 
mtk_t7xx . Power management for this modem is bad. When the notebook goes to 
sleep/suspend, kernel module mtk_t7xx return an error:

  mtk_t7xx :58:00.0: [PM] SAP suspend error: -110 
  mtk_t7xx :58:00.0: PM: pci_pm_suspend(): t7xx_pci_pm_suspend+0x0/0x20 
[mtk_t7xx] returns -110 
  mtk_t7xx :58:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1a0 
returns -110 
  mtk_t7xx :58:00.0: PM: failed to suspend async: error -110 

  So power management failed to suspend:
  PM: Some devices failed to suspend, or early wake event detected 

  And the notebook not suspend and wake up again.
  It must be this module, because if I remove the module first (modprobe -r), 
the laptop goes to sleep and wakes up normally.
  However, after reinserting the module, the modem no longer appears in the 
system.

  Expected state: sleep occurs when the device is put to sleep -
  including the modem. When you wake up, you will wake up, including
  activating the modem and logging into the operator's network.

  Description:Ubuntu 20.04.5 LTS
  Release:20.04

  lspci -v:
  58:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device 4d75 (rev 01)
  Subsystem: Device 1cf8:3500
  Flags: bus master, fast devsel, latency 0, IRQ 17
  Memory at 601e80 (64-bit, prefetchable) [size=32K]
  Memory at 5e80 (64-bit, non-prefetchable) [size=8M]
  Memory at 601e00 (64-bit, prefetchable) [size=8M]
  Capabilities: [80] Express Endpoint, MSI 00
  Capabilities: [d0] MSI-X: Enable+ Count=34 Masked-
  Capabilities: [e0] MSI: Enable- Count=1/32 Maskable+ 64bit+
  Capabilities: [f8] Power Management version 3
  Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 
Len=008 
  Capabilities: [108] Latency Tolerance Reporting
  Capabilities: [110] L1 PM Substates
  Capabilities: [200] Advanced Error Reporting
  Capabilities: [300] Secondary PCI Express
  Kernel driver in use: mtk_t7xx
  Kernel modules: mtk_t7xx

  lshw:
  *-generic
  description: Wireless controller
  product: MEDIATEK Corp.
  vendor: MEDIATEK Corp.
  physical id: 0
  bus info: pci@:58:00.0
  version: 01
  width: 64 bits
  clock: 33MHz
  capabilities: pciexpress msix msi pm bus_master cap_list
  configuration: driver=mtk_t7xx latency=0
  resources: iomemory:600-5ff iomemory:600-5ff irq:17 
memory:601e80-601e807fff memory:5e80-5eff 
memory:601e00-601e7f

  modinfo:
  modinfo mtk_t7xx
  filename:   
/lib/modules/5.19.10-051910-generic/kernel/drivers/net/wwan/t7xx/mtk_t7xx.ko
  license:GPL
  description:MediaTek PCIe 5G WWAN modem T7xx driver
  author: MediaTek Inc
  srcversion: 5FA53465EA0167231B632D4
  alias:  pci:v14C3d4D75sv*sd*bc*sc*i*
  depends:
  retpoline:  Y
  intree: Y
  name:   mtk_t7xx
  vermagic:   5.19.10-051910-generic SMP preempt mod_unload modversions 
  sig_id: PKCS#7
  signer: Build time autogenerated kernel key
  sig_key:7E:38:36:48:BB:F2:74:0E:30:57:1B:6E:64:90:57:55:30:C5:AF:45
  sig_hashalgo:   sha512
  signature:  78:1B:C9:7F:DE:D2:BE:87:EA:17:94:14:C2:51:3E:2C:75:03:76:0F:
  36:96:92:9B:88:48:B0:C8:73:E6:88:E4:A2:61:25:E9:16:E8:87:40:
  45:99:CC:50:FD:21:B0:BB:11:0E:B5:8F:CC:5F:47:7A:5E:00:BF:7D:
  77:50:A1:F5:00:24:DC:EF:E6:3E:A0:3B:0A:D7:2E:84:EC:FC:6B:4D:
  9E:42:CD:A2:07:C3:D9:F8:6E:7B:76:12:7F:B9:9B:70:6A:22:3D:09:
  

[Kernel-packages] [Bug 1992212] Re: nouveau pmu: firmware unavailable gp107

[Juerg Haefliger]

Is it not working or are you just worried about the firmware load
error/warning?

** Tags added: kern-4599

-- 
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/1992212

Title:
  nouveau pmu: firmware unavailable gp107

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  /lib/firmware/nvidia/gp107
  /lib/firmware/nvidia/gp107/acr
  /lib/firmware/nvidia/gp107/gr
  /lib/firmware/nvidia/gp107/gr/fecs_bl.bin
  /lib/firmware/nvidia/gp107/gr/fecs_data.bin
  /lib/firmware/nvidia/gp107/gr/fecs_inst.bin
  /lib/firmware/nvidia/gp107/gr/fecs_sig.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_bl.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_data.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_inst.bin
  /lib/firmware/nvidia/gp107/gr/gpccs_sig.bin
  /lib/firmware/nvidia/gp107/gr/sw_ctx.bin
  /lib/firmware/nvidia/gp107/gr/sw_nonctx.bin
  /lib/firmware/nvidia/gp107/nvdec
  /lib/firmware/nvidia/gp107/sec2
  /lib/firmware/nvidia/gp107/acr/bl.bin
  /lib/firmware/nvidia/gp107/acr/ucode_load.bin
  /lib/firmware/nvidia/gp107/acr/ucode_unload.bin
  /lib/firmware/nvidia/gp107/acr/unload_bl.bin
  /lib/firmware/nvidia/gp107/gr/sw_bundle_init.bin
  /lib/firmware/nvidia/gp107/gr/sw_method_init.bin
  /lib/firmware/nvidia/gp107/nvdec/scrubber.bin
  /lib/firmware/nvidia/gp107/sec2/desc-1.bin
  /lib/firmware/nvidia/gp107/sec2/desc.bin
  /lib/firmware/nvidia/gp107/sec2/image-1.bin
  /lib/firmware/nvidia/gp107/sec2/image.bin
  /lib/firmware/nvidia/gp107/sec2/sig-1.bin
  /lib/firmware/nvidia/gp107/sec2/sig.bin

  Package: linux-firmware
  Status: install ok installed
  Priority: optional
  Section: misc
  Installed-Size: 846721
  Maintainer: Ubuntu Kernel Team 
  Architecture: all
  Multi-Arch: foreign
  Version: 20220329.git681281e4-0ubuntu3.5
  Replaces: atmel-firmware, linux-firmware-snapdragon (<= 1.2-0ubuntu1), 
linux-res
  tricted-common
  Provides: atmel-firmware
  Recommends: firmware-sof-signed
  Breaks: linux-firmware-raspi2 (<= 1.20190819-0ubuntu2), 
linux-firmware-snapdrago
  n (<= 1.2-0ubuntu1)
  Conflicts: atmel-firmware
  Description: Firmware for Linux kernel drivers
   This package provides firmware used by Linux kernel drivers.
  Oct  8 08:49:44 fx504 kernel: [2.659551] MXM: GUID detected in BIOS
  Oct  8 08:49:44 fx504 kernel: [2.660477] ACPI Warning: 
\_SB.PCI0.GFX0._DSM: 
  Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20210730/ns
  arguments-61)
  Oct  8 08:49:44 fx504 kernel: [2.661646] ACPI Warning: 
\_SB.PCI0.PEG0.PEGP._
  DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] 
(202107
  30/nsarguments-61)
  Oct  8 08:49:44 fx504 kernel: [2.663101] pci :01:00.0: optimus 
capabilit
  ies: enabled, status dynamic power, hda bios codec supported
  Oct  8 08:49:44 fx504 kernel: [2.664016] VGA switcheroo: detected Optimus 
DS
  M method \_SB_.PCI0.PEG0.PEGP handle
  Oct  8 08:49:44 fx504 kernel: [2.664940] nouveau :01:00.0: enabling 
devi
  ce (0006 -> 0007)
  Oct  8 08:49:44 fx504 kernel: [2.665979] checking generic (8000 
7e9000) 
  vs hw (a300 100)
  Oct  8 08:49:44 fx504 kernel: [2.665981] checking generic (8000 
7e9000) 
  vs hw (9000 1000)
  Oct  8 08:49:44 fx504 kernel: [2.665982] checking generic (8000 
7e9000) 
  vs hw (a000 200)
  Oct  8 08:49:44 fx504 kernel: [2.666029] nouveau :01:00.0: NVIDIA 
GP107 
  (137000a1)
  Oct  8 08:49:44 fx504 kernel: [2.680631] checking generic (8000 
7e9000) 
  vs hw (a200 100)
  Oct  8 08:49:44 fx504 kernel: [2.680632] checking generic (8000 
7e9000) 
  vs hw (8000 1000)
  Oct  8 08:49:44 fx504 kernel: [2.746655] nouveau :01:00.0: bios: 
version
   86.07.50.00.59
  Oct  8 08:49:44 fx504 kernel: [2.747754] nouveau :01:00.0: pmu: 
firmware
   unavailable
  Oct  8 08:49:44 fx504 kernel: [2.755349] i915 :00:02.0: [drm] 
[ENCODER:1
  02:DDI B/PHY B] is disabled/in DSI mode with an ungated DDI clock, gate it
  Oct  8 08:49:44 fx504 kernel: [2.803611] nouveau :01:00.0: fb: 4096 
MiB 
  GDDR5
  Oct  8 08:49:44 fx504 kernel: [3.132263] [drm] Initialized i915 1.6.0 
202011
  03 for :00:02.0 on minor 0
  Oct  8 08:49:44 fx504 kernel: [3.139712] ACPI: video: Video Device [GFX0] 
(m
  ulti-head: yes  rom: no  post: no)
  Oct  8 08:49:44 fx504 kernel: [3.139759] nouveau :01:00.0: DRM: VRAM: 
40
  96 MiB
  Oct  8 08:49:44 fx504 kernel: [3.139763] nouveau :01:00.0: DRM: GART: 
53
  6870912 MiB
  Oct  8 08:49:44 fx504 kernel: [3.139766] nouveau :01:00.0: DRM: BIT 
tabl
  e 'A' not found
  Oct  8 08:49:44 fx504 kernel: [3.139768] nouveau :01:00.0: DRM: BIT 
tabl
  e 'L' not found
  Oct  8 08:49:44 fx504 kernel: [3.139770] nouveau :01:00.0: DRM: 
Pointer 
  to TMDS table not found
  Oct  8 

[Kernel-packages] [Bug 1992230] Re: APU Packages missing in Kernel too long boot

[Juerg Haefliger]

Note that warnings like
'W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for 
module amdgpu`
are just that, warnings. That doesn't mean that your system actually needs 
these firmware blobs, it simply means that a driver has been included in the 
initramfs that references said blobs.

Can you at least attach the output of 'sudo dmesg'?

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

Title:
  APU Packages missing in Kernel too long boot

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Confirmed

Bug description:
  Error in new 15 Kernel by a brandnew installed Linux without any
  programs installed.

  kemie@kemie-853-opz623:~$ sudo update-initramfs -u

  [sudo] password for kemie: 
  update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic
  W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
  I: The initramfs will attempt to resume from /dev/sdb4
  I: (UUID=579e79cb-4822-44ee-881b-e27ac58e5d0c)
  I: Set the RESUME variable to override this.

  System:
Kernel: 5.15.0-27-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: 
Cinnamon 5.4.12
  tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa 
base: Ubuntu 22.04 jammy
  Machine:
Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING PLUS (MS-7C56) v: 1.0
  serial:  UEFI: American Megatrends LLC. v: 1.A0 date: 
05/21/2022
  CPU:
Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: 
MT MCP arch: Zen 3
  rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 2411 high: 2994 min/max: 1400/4672 boost: disabled cores: 
1: 2770 2: 2394
  3: 2395 4: 2395 5: 2394 6: 2992 7: 2392 8: 1953 9: 1397 10: 1397 11: 2676 
12: 2487 13: 2561
  14: 2993 15: 2994 16: 2394 bogomips: 121368
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nouveau v: kernel 
pcie: speed: 2.5 GT/s
  lanes: 8 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 10:00.0 
chip-ID: 10de:1c82
Device-2: AMD Cezanne driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 
16 ports:
  active: none empty: DP-2,DP-3,HDMI-A-2 bus-ID: 30:00.0 chip-ID: 1002:1638
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: 
amdgpu,ati,modesetting
  unloaded: fbdev,vesa gpu: nouveau display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-1 mapped: HDMI-A-1 model: L236VA res: 1920x1080 dpi: 94 
diag: 598mm (23.5")
OpenGL: renderer: NV137 v: 4.3 Mesa 22.0.5 direct render: Yes
  Audio:
Device-1: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: 
kernel pcie:
  speed: 2.5 GT/s lanes: 8 bus-ID: 10:00.1 chip-ID: 10de:0fb9
Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: 
kernel pcie:
  speed: 8 GT/s lanes: 16 bus-ID: 30:00.1 chip-ID: 1002:1637
Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: 
snd_hda_intel v: kernel pcie:
  speed: 8 GT/s lanes: 16 bus-ID: 30:00.6 chip-ID: 1022:15e3
Sound Server-1: ALSA v: k5.15.0-27-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel 
pcie: speed: 5 GT/s
  lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:2725
IF: wlp33s0 state: down mac: 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
Micro-Star MSI
  driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 
2a:00.0
  chip-ID: 10ec:8168

[Kernel-packages] [Bug 1992230] Re: APU Packages missing in Kernel too long boot

[Juerg Haefliger]

Please:
$ sudo apt install apport
$ sudo apport-collect 1992230


** Tags added: kern-4598

-- 
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/1992230

Title:
  APU Packages missing in Kernel too long boot

Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Confirmed

Bug description:
  Error in new 15 Kernel by a brandnew installed Linux without any
  programs installed.

  kemie@kemie-853-opz623:~$ sudo update-initramfs -u

  [sudo] password for kemie: 
  update-initramfs: Generating /boot/initrd.img-5.15.0-48-generic
  W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin 
for module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu
  I: The initramfs will attempt to resume from /dev/sdb4
  I: (UUID=579e79cb-4822-44ee-881b-e27ac58e5d0c)
  I: Set the RESUME variable to override this.

  System:
Kernel: 5.15.0-27-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: 
Cinnamon 5.4.12
  tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa 
base: Ubuntu 22.04 jammy
  Machine:
Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING PLUS (MS-7C56) v: 1.0
  serial:  UEFI: American Megatrends LLC. v: 1.A0 date: 
05/21/2022
  CPU:
Info: 8-core model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: 
MT MCP arch: Zen 3
  rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
Speed (MHz): avg: 2411 high: 2994 min/max: 1400/4672 boost: disabled cores: 
1: 2770 2: 2394
  3: 2395 4: 2395 5: 2394 6: 2992 7: 2392 8: 1953 9: 1397 10: 1397 11: 2676 
12: 2487 13: 2561
  14: 2993 15: 2994 16: 2394 bogomips: 121368
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nouveau v: kernel 
pcie: speed: 2.5 GT/s
  lanes: 8 ports: active: HDMI-A-1 empty: DP-1,DVI-D-1 bus-ID: 10:00.0 
chip-ID: 10de:1c82
Device-2: AMD Cezanne driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 
16 ports:
  active: none empty: DP-2,DP-3,HDMI-A-2 bus-ID: 30:00.0 chip-ID: 1002:1638
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: 
amdgpu,ati,modesetting
  unloaded: fbdev,vesa gpu: nouveau display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-1 mapped: HDMI-A-1 model: L236VA res: 1920x1080 dpi: 94 
diag: 598mm (23.5")
OpenGL: renderer: NV137 v: 4.3 Mesa 22.0.5 direct render: Yes
  Audio:
Device-1: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel v: 
kernel pcie:
  speed: 2.5 GT/s lanes: 8 bus-ID: 10:00.1 chip-ID: 10de:0fb9
Device-2: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: 
kernel pcie:
  speed: 8 GT/s lanes: 16 bus-ID: 30:00.1 chip-ID: 1002:1637
Device-3: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: 
snd_hda_intel v: kernel pcie:
  speed: 8 GT/s lanes: 16 bus-ID: 30:00.6 chip-ID: 1022:15e3
Sound Server-1: ALSA v: k5.15.0-27-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel 
pcie: speed: 5 GT/s
  lanes: 1 bus-ID: 21:00.0 chip-ID: 8086:2725
IF: wlp33s0 state: down mac: 
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: 
Micro-Star MSI
  driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 
2a:00.0
  chip-ID: 10ec:8168
IF: enp42s0 state: up speed: 100 Mbps duplex: full mac: 
  Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 
1-2.3:4
  chip-ID: 8087:0032
Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: