[Kernel-packages] [Bug 2023246] Re: package linux-image-5.15.0-73-generic (not installed) failed to install/upgrade: unable to open '/boot/vmlinuz-5.15.0-73-generic.dpkg-new': Operation not permitted

[Apport retracing service]

** Package changed: ubuntu => linux-signed-hwe-5.15 (Ubuntu)

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.15.0-73-generic (not installed) failed to
  install/upgrade: unable to open '/boot/vmlinuz-5.15.0-73-generic.dpkg-
  new': Operation not permitted

Status in linux-signed-hwe-5.15 package in Ubuntu:
  New

Bug description:
  Sometimes getting stuck but mouse responding

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-73-generic (not installed)
  ProcVersionSignature: Ubuntu 5.14.0-1059.67-oem 5.14.21
  Uname: Linux 5.14.0-1059-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  2 07:45:14 2023
  DuplicateSignature:
   package:linux-image-5.15.0-73-generic:(not installed)
   Unpacking linux-image-5.15.0-73-generic (5.15.0-73.80~20.04.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-LQQcaM/1-linux-image-5.15.0-73-generic_5.15.0-73.80~20.04.1_amd64.deb
 (--unpack):
unable to open '/boot/vmlinuz-5.15.0-73-generic.dpkg-new': Operation not 
permitted
  ErrorMessage: unable to open '/boot/vmlinuz-5.15.0-73-generic.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2023-03-15 (84 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: linux-signed-hwe-5.15
  Title: package linux-image-5.15.0-73-generic (not installed) failed to 
install/upgrade: unable to open '/boot/vmlinuz-5.15.0-73-generic.dpkg-new': 
Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2023246/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules

[Dirk Su]

Tested with fresh installed focal on machine with Nvidia GPU. Enabled
-proposed channel and install ubuntu-drivers-common 1:0.9.0~0.20.04.8.
Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and
related packages will be installed. Executed command "sudo ubuntu-
drivers install nvidia:515-open" and Nvidia open driver 515 and related
packages will be installed.

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1786013] Autopkgtest regression report (linux-meta-oracle-5.15/5.15.0.1037.43~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-oracle-5.15 
(5.15.0.1037.43~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

linux-oracle-5.15/5.15.0-1037.43~20.04.1 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-meta-oracle-5.15

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2022981] Re: Frequent hard reboots on RaptorLake

[Daniel van Vugt]

That log is too large and cluttered to find the "hard reboots". Can you
try identifying the exact date and time of such a reboot? Maybe with a
new log?

Also I notice your gnome-shell crashed a couple of times so please be
sure to report that in a separate bug:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  Frequent hard reboots on RaptorLake

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

Bug description:
  I can repro in multiple ways:

  1. Unplug my HDMI monitor. This is pretty much a guaranteed reboot.
  2. Using hardware accelerated Chromium, switching between google profiles 
seems to trigger a crash and full reboot pretty often.

  These could be two separate bugs. I'm not sure I'd be unlucky enough
  to have two full reboot bugs at the same time though. Happy to help
  with more debugging

  Release: Jammy
  Chromium version: 115.0.5762.4-hwacc
  snap refresh --channel=latest/edge/hwacc chromium

  What you expected to happen
  1. HDMI monitor disconnects, and no reboots happen.
  2. I can switch Chromium profiles without a reboot

  What happened instead
  Both actions cause a reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  6 16:09:12 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-41-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-43-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   tp_smapi/0.43, 5.19.0-41-generic, x86_64: installed
   tp_smapi/0.43, 5.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5630]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:]
  InstallationDate: Installed on 2023-04-20 (46 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: System76 Gazelle
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_90m3zy@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_90m3zy ro drm.debug=0xe quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2023
  dmi.bios.release: 4.19
  dmi.bios.vendor: coreboot
  dmi.bios.version: 2023-03-22_799ed79
  dmi.board.name: Gazelle
  dmi.board.vendor: System76
  dmi.board.version: gaze18
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr2023-03-22_799ed79:bd03/22/2023:br4.19:efr0.0:svnSystem76:pnGazelle:pvrgaze18:rvnSystem76:rnGazelle:rvrgaze18:cvnSystem76:ct9:cvr:sku:
  dmi.product.name: Gazelle
  dmi.product.version: gaze18
  dmi.sys.vendor: System76
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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 N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2022981/+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 2022981] Re: Frequent hard reboots on RaptorLake

[Daniel van Vugt]

Compressing large text files before attaching them usually solves that.

** Package changed: linux (Ubuntu) => linux-hwe-5.19 (Ubuntu)

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

Title:
  Frequent hard reboots on RaptorLake

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

Bug description:
  I can repro in multiple ways:

  1. Unplug my HDMI monitor. This is pretty much a guaranteed reboot.
  2. Using hardware accelerated Chromium, switching between google profiles 
seems to trigger a crash and full reboot pretty often.

  These could be two separate bugs. I'm not sure I'd be unlucky enough
  to have two full reboot bugs at the same time though. Happy to help
  with more debugging

  Release: Jammy
  Chromium version: 115.0.5762.4-hwacc
  snap refresh --channel=latest/edge/hwacc chromium

  What you expected to happen
  1. HDMI monitor disconnects, and no reboots happen.
  2. I can switch Chromium profiles without a reboot

  What happened instead
  Both actions cause a reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  6 16:09:12 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-41-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-43-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   tp_smapi/0.43, 5.19.0-41-generic, x86_64: installed
   tp_smapi/0.43, 5.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5630]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:]
  InstallationDate: Installed on 2023-04-20 (46 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: System76 Gazelle
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_90m3zy@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_90m3zy ro drm.debug=0xe quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2023
  dmi.bios.release: 4.19
  dmi.bios.vendor: coreboot
  dmi.bios.version: 2023-03-22_799ed79
  dmi.board.name: Gazelle
  dmi.board.vendor: System76
  dmi.board.version: gaze18
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr2023-03-22_799ed79:bd03/22/2023:br4.19:efr0.0:svnSystem76:pnGazelle:pvrgaze18:rvnSystem76:rnGazelle:rvrgaze18:cvnSystem76:ct9:cvr:sku:
  dmi.product.name: Gazelle
  dmi.product.version: gaze18
  dmi.sys.vendor: System76
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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 N/A

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/2023244/+attachment/5678531/+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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2023244/+attachment/5678528/+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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2023244/+attachment/5678524/+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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2023244/+attachment/5678523/+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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/2023244/+attachment/5678520/+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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

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

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/2023244/+attachment/5678518/+files/CRDA.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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2023244/+attachment/5678519/+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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

[Jeffery To]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2023244/+attachment/5678517/+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/2023244

Title:
  Cannot mount ext4 fs with orphan_file as read-only

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes
  a snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.

  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my
  files. (I booted into SystemRescue 10.01 from a USB drive to do this.)

  Now my backup script fails because it cannot mount the snapshot as
  read-only. When I try to mount the snapshot manually I get this error
  message:

  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.

  Checking dmesg, I see this:

  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed

  I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jeff   3019 F wireplumber
   /dev/snd/seq:jeff   3009 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
  InstallationDate: Installed on 2010-10-17 (4616 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: LENOVO 3626PL2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/11/2012
  dmi.bios.release: 1.64
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET70WW (1.40 )
  dmi.board.name: 3626PL2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad X201
  dmi.product.name: 3626PL2
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023244/+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 2023244] [NEW] Cannot mount ext4 fs with orphan_file as read-only

[Jeffery To]

Public bug reported:

I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes a
snapshot of the file system, mounts the snapshot as read-only, then
backs up from the mounted snapshot.

I recently upgraded my hard disk and created a new ext4 file system on
the new disk with the orphan_file feature before transferring my files.
(I booted into SystemRescue 10.01 from a USB drive to do this.)

Now my backup script fails because it cannot mount the snapshot as read-
only. When I try to mount the snapshot manually I get this error
message:

mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
   dmesg(1) may have more information after failed mount system call.

Checking dmesg, I see this:

[  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan cleanup
[  149.810463] EXT4-fs (dm-6): recovery complete
[  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
[  149.811785] EXT4-fs (dm-6): mount failed

I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
--- 
ProblemType: Bug
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jeff   3019 F wireplumber
 /dev/snd/seq:jeff   3009 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.04
HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
InstallationDate: Installed on 2010-10-17 (4616 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: LENOVO 3626PL2
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_osi=! "acpi_osi=Windows 
2009" intel_iommu=off zswap.enabled=1 vt.handoff=7
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-20-generic N/A
 linux-backports-modules-6.2.0-20-generic  N/A
 linux-firmware20230323.gitbcdcfbcf-0ubuntu1.1
Tags:  lunar
Uname: Linux 6.2.0-20-generic x86_64
UpgradeStatus: Upgraded to lunar on 2023-05-02 (36 days ago)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 10/11/2012
dmi.bios.release: 1.64
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET70WW (1.40 )
dmi.board.name: 3626PL2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.21
dmi.modalias: 
dmi:bvnLENOVO:bvr6QET70WW(1.40):bd10/11/2012:br1.64:efr1.21:svnLENOVO:pn3626PL2:pvrThinkPadX201:rvnLENOVO:rn3626PL2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
dmi.product.family: ThinkPad X201
dmi.product.name: 3626PL2
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO

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


** Tags: apport-collected lunar

** Tags added: apport-collected lunar

** Description changed:

  I'm using Ubuntu 23.04 with lvm. I have a backup script where it takes a
  snapshot of the file system, mounts the snapshot as read-only, then
  backs up from the mounted snapshot.
  
  I recently upgraded my hard disk and created a new ext4 file system on
  the new disk with the orphan_file feature before transferring my files.
  (I booted into SystemRescue 10.01 from a USB drive to do this.)
  
  Now my backup script fails because it cannot mount the snapshot as read-
  only. When I try to mount the snapshot manually I get this error
  message:
  
  mount: /media/backup: mount(2) system call failed: Structure needs cleaning.
 dmesg(1) may have more information after failed mount system call.
  
  Checking dmesg, I see this:
  
  [  149.810442] EXT4-fs (dm-6): write access unavailable, skipping orphan 
cleanup
  [  149.810463] EXT4-fs (dm-6): recovery complete
  [  149.810472] EXT4-fs error (device dm-6): ext4_mark_recovery_complete:6134: 
comm mount: Orphan file not empty on read-only fs.
  [  149.811785] EXT4-fs (dm-6): mount failed
  
- I have booted into SystemRescue to run e2fsck on my file system but the
- error persists.
+ I have booted into SystemRescue to run e2fsck on my file system but the error 
persists.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jeff   3019 F wireplumber
+  /dev/snd/seq:jeff   3009 F pipewire
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.04
+ HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap
+ InstallationDate: Installed on 2010-10-17 (4616 days ago)
+ InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
+ MachineType: LENOVO 3626PL2
+ Package: linux (not installed)
+ ProcFB: 0 

[Kernel-packages] [Bug 1928028] Re: io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 (timeouted / SIGKILL)

[Po-Hsu Lin]

OEM-5.6 EOL. Closing this bug.

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Won't Fix

** Changed in: linux-oem-5.6 (Ubuntu Focal)
   Status: In Progress => Won't Fix

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

Title:
  io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 (timeouted /
  SIGKILL)

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 source package in Focal:
  Won't Fix

Bug description:
  [Impact]
  When using async io_uring OP_SENDMSG, a copy to kernel address 0 might be 
attempted, leading to a kernel WARN/BUG and an uninterruptible process.

  [Fix]
  Partial backport of dd821e0c95a64b5923a0c57f07d3f7563553e756 ("io_uring: fix 
missing msg_name assignment"). The recvmsg side does not seed to set msg_name, 
as it copies from a local/stack kernel address (at sys_recvmsg) to a uaddr 
parameter, which is given when doing the copy_msghdr operation.

  [Test case]
  LTP io_uring02 was run, and an equivalent recvmsg test was done too. A 
successfull sendmsg test (without the chroot at io_uring02 test) was also 
tested.

  [Potential regressions]
  io_uring sendmsg/recvmsg paths could fail, potentially leading to a system 
crash or even a security vulnerability.

  
  ---

  
  io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 5.6.0-1056.60 on host 
spitfire

  This test isn't found to be ran on previous versions on F/oem-5.6, so
  would not consider this to be a regression.

  26934.05/07 14:42:48 DEBUG| utils:0153| [stdout] tag=io_uring01 
stime=1620398217 dur=0 exit=exited stat=0 core=no cu=0 cs=0
  26935.05/07 14:42:48 DEBUG| utils:0153| [stdout] startup='Fri May 7 
14:36:57 2021'
  26936.05/07 14:42:48 DEBUG| utils:0153| [stdout] tst_test.c:1311: 
TINFO: Timeout per run is 0h 05m 00s
  26937.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26938.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26939.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26940.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26941.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26942.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26943.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26944.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26945.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26946.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26947.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted, 
sending SIGKILL!
  26948.05/07 14:42:48 DEBUG| utils:0153| [stdout] Cannot kill test 
processes!
  26949.05/07 14:42:48 DEBUG| utils:0153| [stdout] Congratulation, 
likely test hit a kernel bug.
  26950.05/07 14:42:48 DEBUG| utils:0153| [stdout] Exitting uncleanly...
  26951.05/07 14:42:48 DEBUG| utils:0153| [stdout] tag=io_uring02 
stime=1620398217 dur=350 exit=exited stat=1 core=no cu=0 cs=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928028/+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 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules

[Dirk Su]

Tested with fresh installed jammy on machine with Nvidia GPU. Enabled
-proposed channel and install ubuntu-drivers-common 0.9.6.2~0.22.04.3.
Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and
related packages will be installed. Executed command "sudo ubuntu-
drivers install nvidia:515-open" and Nvidia open driver 515 and related
packages will be installed.

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 2023193] Re: Add firmware files for HP G10 series laptops

[Chris Chiu]

** Tags added: originate-from-2016076

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

Title:
  Add firmware files for HP G10 series laptops

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Kinetic:
  New
Status in linux-firmware source package in Lunar:
  New

Bug description:
  [ Impact ]
  HP G10 laptops need more Cirrus firmware files to enable all amplifiers to 
output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The firmware files are released by Cirrus codec for particular HP series 
laptops.
   * The risk of regression should only impact particular models

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023193/+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 2013325] Re: net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels (TXTIME rel returned '', expected 'OK')

[Po-Hsu Lin]

** Merge proposal unlinked:
   https://code.launchpad.net/~diewald/+git/rt-hints/+merge/444282

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

Title:
  net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels
  (TXTIME rel returned '', expected 'OK')

Status in ubuntu-kernel-tests:
  New
Status in linux-allwinner package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux-starfive package in Ubuntu:
  New
Status in linux-allwinner source package in Kinetic:
  New
Status in linux-riscv source package in Kinetic:
  New
Status in linux-starfive source package in Kinetic:
  New

Bug description:
  Issue found on Kinetic 5.19 RISCV kernels:

  * kinetic/linux-allwinner/5.19.0-1009.9
  # selftests: net: cmsg_time.sh
  #   Case UDPv4  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv4  - TXTIME rel returned '', expected 'OK'
  #   Case UDPv6  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv6  - TXTIME rel returned '', expected 'OK'
  #   Case RAWv6  - TXTIME rel returned '', expected 'OK'
  # FAIL - 5/36 cases failed
  not ok 1 selftests: net: cmsg_time.sh # exit=1

  * kinetic/linux-riscv/5.19.0-1015.16
  # selftests: net: cmsg_time.sh
  #   Case ICMPv4  - TXTIME rel returned '', expected 'OK'
  #   Case UDPv6  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv6  - TXTIME rel returned '', expected 'OK'
  #   Case RAWv6  - TXTIME rel returned '', expected 'OK'
  # FAIL - 4/36 cases failed
  not ok 1 selftests: net: cmsg_time.sh # exit=1

  * kinetic/linux-starfive/5.19.0-1014.16
  # selftests: net: cmsg_time.sh
  #   Case UDPv4  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv4  - TXTIME rel returned '', expected 'OK'
  #   Case UDPv6  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv6  - TXTIME rel returned '', expected 'OK'
  #   Case RAWv6  - TXTIME rel returned '', expected 'OK'
  # FAIL - 5/36 cases failed
  not ok 1 selftests: net: cmsg_time.sh # exit=1

  This is only affecting RISCV64 kernels, it does not affect kinetic
  generic kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2013325/+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 1950627] Re: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused

[Po-Hsu Lin]

** Merge proposal unlinked:
   https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/443928

** Merge proposal unlinked:
   https://code.launchpad.net/~diewald/+git/rt-hints/+merge/444282

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

Title:
  ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg:
  Connection refused

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  This is from ADT testing (amd64) but I believe I occasionally saw this
  before. It feels like sometimes the receiver does not get ready before
  the transmission starts. IIRC this goes away when re-trying.

  02:52:31 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh
  02:52:31 DEBUG| [stdout] # IPv4
  02:52:31 DEBUG| [stdout] # No GRO   ok
  02:52:32 DEBUG| [stdout] # GRO frag listok
  02:52:32 DEBUG| [stdout] # GRO fwd  ok
  02:52:33 DEBUG| [stdout] # UDP fwd perfudp rx:
333 MB/s   271894 calls/s
  02:52:33 DEBUG| [stdout] # udp tx:378 MB/s 6422 calls/s   6422 msg/s
  02:52:34 DEBUG| [stdout] # udp rx:383 MB/s   312480 calls/s
  02:52:34 DEBUG| [stdout] # udp tx:383 MB/s 6506 calls/s   6506 msg/s
  02:52:35 DEBUG| [stdout] # udp rx:381 MB/s   310202 calls/s
  02:52:35 DEBUG| [stdout] # udp tx:380 MB/s 6458 calls/s   6458 msg/s
  02:52:36 DEBUG| [stdout] # UDP GRO fwd perfudp rx:
344 MB/s   280814 calls/s
  02:52:36 DEBUG| [stdout] # udp tx:389 MB/s 6612 calls/s   6612 msg/s
  02:52:37 DEBUG| [stdout] # udp rx:364 MB/s   297088 calls/s
  02:52:37 DEBUG| [stdout] # udp tx:383 MB/s 6512 calls/s   6512 msg/s
  02:52:38 DEBUG| [stdout] # udp rx:448 MB/s   365435 calls/s
  02:52:38 DEBUG| [stdout] # udp tx:453 MB/s 7686 calls/s   7686 msg/s
  02:52:39 DEBUG| [stdout] # GRO frag list over UDP tunnelok
  02:52:39 DEBUG| [stdout] # GRO fwd over UDP tunnel  ok
  02:52:39 DEBUG| [stdout] # UDP tunnel fwd perf 
./udpgso_bench_tx: sendmsg: Connection refused
  02:52:39 DEBUG| [stdout] #  fail client exit code 1, server 0
  02:52:40 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx:
236 MB/s   192389 calls/s
  02:52:41 DEBUG| [stdout] # udp tx:284 MB/s 4826 calls/s   4826 msg/s
  02:52:41 DEBUG| [stdout] # udp rx:295 MB/s   240586 calls/s
  02:52:42 DEBUG| [stdout] # udp tx:306 MB/s 5206 calls/s   5206 msg/s
  02:52:42 DEBUG| [stdout] # udp rx:306 MB/s   249784 calls/s
  02:52:43 DEBUG| [stdout] # udp tx:310 MB/s 5263 calls/s   5263 msg/s
  02:52:43 DEBUG| [stdout] # IPv6
  02:52:43 DEBUG| [stdout] # No GRO   ok
  02:52:43 DEBUG| [stdout] # GRO frag listok
  02:52:43 DEBUG| [stdout] # GRO fwd  ok
  02:52:44 DEBUG| [stdout] # UDP fwd perfudp rx:
 82 MB/s66844 calls/s
  02:52:45 DEBUG| [stdout] # udp tx:334 MB/s 5668 calls/s   5668 msg/s
  02:52:45 DEBUG| [stdout] # udp rx:374 MB/s   305206 calls/s
  02:52:46 DEBUG| [stdout] # udp tx:375 MB/s 6377 calls/s   6377 msg/s
  02:52:46 DEBUG| [stdout] # udp rx:373 MB/s   303948 calls/s
  02:52:47 DEBUG| [stdout] # udp tx:371 MB/s 6299 calls/s   6299 msg/s
  02:52:48 DEBUG| [stdout] # UDP GRO fwd perfudp rx:
340 MB/s   277046 calls/s
  02:52:48 DEBUG| [stdout] # udp tx:389 MB/s 6601 calls/s   6601 msg/s
  02:52:49 DEBUG| [stdout] # udp rx:390 MB/s   318311 calls/s
  02:52:49 DEBUG| [stdout] # udp tx:391 MB/s 6639 calls/s   6639 msg/s
  02:52:50 DEBUG| [stdout] # udp rx:396 MB/s   322528 calls/s
  02:52:50 DEBUG| [stdout] # udp tx:406 MB/s 6891 calls/s   6891 msg/s
  02:52:50 DEBUG| [stdout] # GRO frag list over UDP tunnelok
  02:52:50 DEBUG| [stdout] # GRO fwd over UDP tunnel  ok
  02:52:52 DEBUG| [stdout] # UDP tunnel fwd perf udp rx:
 93 MB/s76354 calls/s
  02:52:52 DEBUG| [stdout] # udp tx:257 MB/s 4360 calls/s   4360 msg/s
  02:52:53 DEBUG| [stdout] # udp rx:297 MB/s   241883 calls/s
  02:52:53 DEBUG| [stdout] # udp tx:315 MB/s 5352 calls/s   5352 msg/s
  02:52:54 DEBUG| [stdout] # udp rx:286 MB/s   233207 calls/s
  02:52:54 DEBUG| [stdout] # udp tx:304 MB/s 5172 calls/s   5172 msg/s
  02:52:55 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx:
267 MB/s   217607 calls/s
  02:52:55 DEBUG| [stdout] # udp tx:297 MB/s 5039 calls/s   5039 msg/s
  02:52:56 DEBUG| [stdout] 

[Kernel-packages] [Bug 2000228] Re: Add initial support for Mediatek mt8195 demo platform

[ethan.hsieh]

Okay. Thanks~

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

Title:
  Add initial support for Mediatek mt8195 demo platform

Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [Impact]
  Add initial support for Mediatek mt8195 demo platform
  
https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9
  
https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9

  [Where problems could occur]
  Audio function doesn't work on Mediatek mt8195 demo platform.
  Play audio by aplay and gnome sound test:
  1. HDMI audio: Pass
  2. Headset: Pass

  [Test Case]
  Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform.

  [Regression Potential]
  Add initial support for Mediatek mt8195 demo platform. There should be no 
risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+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 2008774] Re: Ubuntu 22.04 not waking up after second suspend

[mtrsky]

I have this problem on Lenovo Thinkpad X1 Gen10, Intel i5 and Intel
Irisxe graphics.  Came preinstalled with Ubuntu 20.04, but I immediately
installed 22.04. BIOS version is N3AET72W (1.37), 2023-03-02. The laptop
does not wake from suspend, even after changing BIOS to Linux S3 suspend
option.

What worked was running Xorg instead of Wayland. On startup when typing in 
password, I selected the Xorg option from bottom right settings, as suggested 
in this link. I haven't had the problem since. 
https://itsfoss.com/switch-xorg-wayland/

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

Title:
  Ubuntu 22.04 not waking up after second suspend

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

Bug description:
  After the first suspend it wakes up just fine - it's the second
  suspend after which the screen stays blank and keyboard doesn't react
  (although the power LED starts glowing). It happens if I close the
  laptop's lid or do a manual suspend via the system menu. It happens
  only recently (I think after some kernel update, but I'm not sure
  about this) - before it worked fine for month (since I installed
  Ubuntu).

  I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the
  only OS (if that's important).

  What I tried:

  * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896)
  * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896)
  * I looked through the logs in /var/log but couldn't find anything obvious to 
me (but I'm not a Linux guru).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 28 11:02:36 2023
  InstallationDate: Installed on 2022-06-14 (258 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+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 2023233] [NEW] Jammy update: v5.15.106 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.106 upstream stable release
   from git://git.kernel.org/

fsverity: don't drop pagecache at end of FS_IOC_ENABLE_VERITY
usb: dwc3: gadget: move cmd_endtransfer to extra function
usb: dwc3: gadget: Add 1ms delay after end transfer command without IOC
kernel: kcsan: kcsan_test: build without structleak plugin
kcsan: avoid passing -g for test
ksmbd: don't terminate inactive sessions after a few seconds
bus: imx-weim: fix branch condition evaluates to a garbage value
xfrm: Zero padding when dumping algos and encap
ASoC: codecs: tx-macro: Fix for KASAN: slab-out-of-bounds
md: avoid signed overflow in slot_store()
x86/PVH: obtain VGA console info in Dom0
net: hsr: Don't log netdev_err message on unknown prp dst node
ALSA: asihpi: check pao in control_message()
ALSA: hda/ca0132: fixup buffer overrun at tuning_ctl_set()
fbdev: tgafb: Fix potential divide by zero
sched_getaffinity: don't assume 'cpumask_size()' is fully initialized
fbdev: nvidia: Fix potential divide by zero
fbdev: intelfb: Fix potential divide by zero
fbdev: lxfb: Fix potential divide by zero
fbdev: au1200fb: Fix potential divide by zero
tools/power turbostat: Fix /dev/cpu_dma_latency warnings
tools/power turbostat: fix decoding of HWP_STATUS
tracing: Fix wrong return in kprobe_event_gen_test.c
ca8210: Fix unsigned mac_len comparison with zero in ca8210_skb_tx()
mips: bmips: BCM6358: disable RAC flush for TP1
ALSA: usb-audio: Fix recursive locking at XRUN during syncing
platform/x86: think-lmi: add missing type attribute
platform/x86: think-lmi: use correct possible_values delimiters
platform/x86: think-lmi: only display possible_values if available
platform/x86: think-lmi: Add possible_values for ThinkStation
mtd: rawnand: meson: invalidate cache on polling ECC bit
SUNRPC: fix shutdown of NFS TCP client socket
sfc: ef10: don't overwrite offload features at NIC reset
scsi: megaraid_sas: Fix crash after a double completion
scsi: mpt3sas: Don't print sense pool info twice
ptp_qoriq: fix memory leak in probe()
net: dsa: microchip: ksz8863_smi: fix bulk access
r8169: fix RTL8168H and RTL8107E rx crc error
regulator: Handle deferred clk
net/net_failover: fix txq exceeding warning
net: stmmac: don't reject VLANs when IFF_PROMISC is set
drm/i915/tc: Fix the ICL PHY ownership check in TC-cold state
platform/x86/intel/pmc: Alder Lake PCH slp_s0_residency fix
can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write
s390/vfio-ap: fix memory leak in vfio_ap device driver
loop: suppress uevents while reconfiguring the device
loop: LOOP_CONFIGURE: send uevents for partitions
net: mvpp2: classifier flow fix fragmentation flags
net: mvpp2: parser fix QinQ
net: mvpp2: parser fix PPPoE
smsc911x: avoid PHY being resumed when interface is not up
ice: add profile conflict check for AVF FDIR
ice: fix invalid check for empty list in ice_sched_assoc_vsi_to_agg()
ALSA: ymfpci: Create card with device-managed snd_devm_card_new()
ALSA: ymfpci: Fix BUG_ON in probe function
net: ipa: compute DMA pool size properly
i40e: fix registers dump after run ethtool adapter self test
bnxt_en: Fix reporting of test result in ethtool selftest
bnxt_en: Fix typo in PCI id to device description string mapping
bnxt_en: Add missing 200G link speed reporting
net: dsa: mv88e6xxx: Enable IGMP snooping on user ports only
net: ethernet: mtk_eth_soc: fix flow block refcounting logic
pinctrl: ocelot: Fix alt mode for ocelot
iommu/vt-d: Allow zero SAGAW if second-stage not supported
Input: alps - fix compatibility with -funsigned-char
Input: focaltech - use explicitly signed char type
cifs: prevent infinite recursion in CIFSGetDFSRefer()
cifs: fix DFS traversal oops without CONFIG_CIFS_DFS_UPCALL
Input: goodix - add Lenovo Yoga Book X90F to nine_bytes_report DMI table
btrfs: fix race between quota disable and quota assign ioctls
btrfs: scan device in non-exclusive mode
zonefs: Always invalidate last cached page on append write
can: j1939: prevent deadlock by moving j1939_sk_errqueue()
xen/netback: don't do grant copy across page boundary
net: phy: dp83869: fix default value for tx-/rx-internal-delay
pinctrl: amd: Disable and mask interrupts on resume
pinctrl: at91-pio4: fix domain name assignment
powerpc: Don't try to copy PPR for task with NULL pt_regs
NFSv4: Fix hangs when recovering open state after a server reboot
ALSA: hda/conexant: Partial revert of a quirk for Lenovo
ALSA: usb-audio: Fix regression on detection of Roland VS-100
ALSA: hda/realtek: Add quirks for some Clevo laptops
ALSA: hda/realtek: Add quirk 

[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

[Matthew Ruffell]

Hi Paul,

Yes, if we look at https://kernel.ubuntu.com/sru/dashboards/web/kernel-
stable-board.html under 2023.05.15 SRU cycle, under Jammy it has linux-
hwe-5.19 5.19.0-44.45~22.04.1 sitting in -proposed, so yes, this fix
will be made available to kinetic and jammy-hwe.

Saying that, the dashboard also lists 5.19.0-45 for both, but still in
the preparation stage and not pushed to -proposed yet. I looked up the
code, and 5.19.0-45 only has one patch ontop of 5.19.0-44, which is a
fix to https://bugs.launchpad.net/bugs/2020599, fixing a regression in
WPA offload.

commit 3358af2b077f8e90461a9a8941e8292b995db63b
Author: Hector Martin 
Date:   Sat Mar 11 23:19:14 2023 +0900
wifi: cfg80211: Partial revert "wifi: cfg80211: Fix use after free for wext"
BugLink: https://bugs.launchpad.net/bugs/2020599

I think the kernel team will probably get 5.19.0-45 into -proposed as
soon as they can, and this will likely be the kernel that will be
released next week.

You won't need to re-verify, since its the same as 5.19.0-44 with a
single patch ontop.

Thanks,
Matthew

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2023230] [NEW] Jammy update: v5.15.105 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.105 upstream stable release
   from git://git.kernel.org/

interconnect: qcom: osm-l3: fix icc_onecell_data allocation
perf/core: Fix perf_output_begin parameter is incorrectly invoked in 
perf_event_bpf_output
perf: fix perf_event_context->time
tracing/hwlat: Replace sched_setaffinity with set_cpus_allowed_ptr
serial: fsl_lpuart: Fix comment typo
tty: serial: fsl_lpuart: switch to new dmaengine_terminate_* API
tty: serial: fsl_lpuart: fix race on RX DMA shutdown
serial: 8250: SERIAL_8250_ASPEED_VUART should depend on ARCH_ASPEED
serial: 8250: ASPEED_VUART: select REGMAP instead of depending on it
kthread: add the helper function kthread_run_on_cpu()
trace/hwlat: make use of the helper function kthread_run_on_cpu()
trace/hwlat: Do not start per-cpu thread if it is already running
net: tls: fix possible race condition between do_tls_getsockopt_conf() and 
do_tls_setsockopt_conf()
power: supply: bq24190_charger: using pm_runtime_resume_and_get instead of 
pm_runtime_get_sync
power: supply: bq24190: Fix use after free bug in bq24190_remove due to race 
condition
power: supply: da9150: Fix use after free bug in da9150_charger_remove due to 
race condition
ARM: dts: imx6sll: e60k02: fix usbotg1 pinctrl
ARM: dts: imx6sl: tolino-shine2hd: fix usbotg1 pinctrl
arm64: dts: imx8mn: specify #sound-dai-cells for SAI nodes
xsk: Add missing overflow check in xdp_umem_reg
iavf: fix inverted Rx hash condition leading to disabled hash
iavf: fix non-tunneled IPv6 UDP packet type and hashing
intel/igbvf: free irq on the error path in igbvf_request_msix()
igbvf: Regard vf reset nack as success
igc: fix the validation logic for taprio's gate list
i2c: imx-lpi2c: check only for enabled interrupt flags
i2c: hisi: Only use the completion interrupt to finish the transfer
scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate()
net: dsa: b53: mmap: fix device tree support
net: usb: smsc95xx: Limit packet length to skb->len
qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info
net: phy: Ensure state transitions are processed from phy_stop()
net: mdio: fix owner field for mdio buses registered using device-tree
net: mdio: fix owner field for mdio buses registered using ACPI
drm/i915/gt: perform uc late init after probe error injection
net: qcom/emac: Fix use after free bug in emac_remove due to race condition
net/ps3_gelic_net: Fix RX sk_buff length
net/ps3_gelic_net: Use dma_mapping_error
octeontx2-vf: Add missing free for alloc_percpu
bootconfig: Fix testcase to increase max node
keys: Do not cache key in task struct if key is requested from kernel thread
iavf: fix hang on reboot with ice
i40e: fix flow director packet filter programming
bpf: Adjust insufficient default bpf_jit_limit
net/mlx5e: Set uplink rep as NETNS_LOCAL
net/mlx5: Fix steering rules cleanup
net/mlx5: Read the TC mapping of all priorities on ETS query
net/mlx5: E-Switch, Fix an Oops in error handling code
net: dsa: tag_brcm: legacy: fix daisy-chained switches
atm: idt77252: fix kmemleak when rmmod idt77252
erspan: do not use skb_mac_header() in ndo_start_xmit()
net/sonic: use dma_mapping_error() for error check
nvme-tcp: fix nvme_tcp_term_pdu to match spec
hvc/xen: prevent concurrent accesses to the shared ring
ksmbd: add low bound validation to FSCTL_SET_ZERO_DATA
ksmbd: add low bound validation to FSCTL_QUERY_ALLOCATED_RANGES
ksmbd: fix possible refcount leak in smb2_open()
gve: Cache link_speed value from device
net: dsa: mt7530: move enabling disabling core clock to mt7530_pll_setup()
net: dsa: mt7530: move lowering TRGMII driving to mt7530_setup()
net: dsa: mt7530: move setting ssc_delta to PHY_INTERFACE_MODE_TRGMII case
net: mdio: thunder: Add missing fwnode_handle_put()
Bluetooth: btqcomsmd: Fix command timeout after setting BD address
Bluetooth: L2CAP: Fix responding with wrong PDU type
platform/chrome: cros_ec_chardev: fix kernel data leak from ioctl
thread_info: Add helpers to snapshot thread flags
entry: Snapshot thread flags
entry/rcu: Check TIF_RESCHED _after_ delayed RCU wake-up
hwmon: fix potential sensor registration fail if of_node is missing
hwmon (it87): Fix voltage scaling for chips with 10.9mV ADCs
scsi: qla2xxx: Synchronize the IOCB count to be in order
scsi: qla2xxx: Perform lockless command completion in abort path
uas: Add US_FL_NO_REPORT_OPCODES for JMicron JMS583Gen 2
thunderbolt: Use scale field when allocating USB3 bandwidth
thunderbolt: Call tb_check_quirks() after initializing adapters
thunderbolt: Disable interrupt auto clear for rings

[Kernel-packages] [Bug 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

[Paul Rockwell]

Thanks Matthew. I was erring on the side of caution as it was easy for
me to at least give that variant a whirl on my trusty Jammy VM. I'll
definitely take your lead on the need for future testing.

Looking forward to release next week. I'll update you on my experiences
- but I suspect that it'll be a non-event.

Should I assume that the -proposed kernel will be made available to both
Kinetic and Jammy HWE? I maintain a tips/techniques document for VMWare
Fusion users on Apple Silicon. This issue is highlighted along with  a
few work-arounds. If this is fixed in both releases I can test both and
remove a lot of work-around discussions.

Thanks,

Paul

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

[Matthew Ruffell]

Hi Paul,

Thanks for verifying that linux-nvidia kernel, but for the future, you
don't need to worry about verifying each and every kernel series. These
days, the kernel team maintains over 100 kernel variants, and it is
simply impossible to check them all.

We just check the primary ones, e.g. 5.19 in kinetic, and then when they
are made into their specific derivative kernels, e.g. 5.19 linux-nvidia,
they contain all the patches from the primary kernel, plus some specific
patches to enable whatever hardware the derivative kernel is for.

So, don't worry if there are any more from other odd kernel
combinations, I will let you know if we need to do any more testing.

In other news, looking at https://kernel.ubuntu.com/, we should be on
track for a release to -updates early next week, so look forward to that
and getting this bug fixed for everyone.

Thanks,
Matthew

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

[Roemer Claasen]

No luck running with the patch and without "amdgpu.dcdebugmask=0x10",
sadly.

There is still occasional screen flickering, and sometimes (once every
15 mimutes or so) a blank screen.

Then after a few hours of use, the display froze completely, and I could
only reclaim control through 1) suspend and 2) TTY1. See kern.log below.

$ cat /var/log/kern.log:

Jun  7 23:32:11 rct14s kernel: [ 8513.360433] amdgpu :33:00.0: [drm] 
*ERROR* [CRTC:72:crtc-0] flip_done timed out
Jun  7 23:32:56 rct14s kernel: [ 8558.928374] amdgpu :33:00.0: [drm] 
*ERROR* flip_done timed out
Jun  7 23:32:56 rct14s kernel: [ 8558.928380] amdgpu :33:00.0: [drm] 
*ERROR* [CRTC:72:crtc-0] commit wait timed out
Jun  7 23:33:07 rct14s kernel: [ 8569.168721] amdgpu :33:00.0: [drm] 
*ERROR* flip_done timed out
Jun  7 23:33:07 rct14s kernel: [ 8569.168728] amdgpu :33:00.0: [drm] 
*ERROR* [PLANE:55:plane-3] commit wait timed out
Jun  7 23:33:07 rct14s kernel: [ 8569.168816] [ cut here 
]
Jun  7 23:33:07 rct14s kernel: [ 8569.168817] WARNING: CPU: 4 PID: 1109 at 
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8145 
amdgpu_dm_atomic_commit_tail+0x3b30/0x41f0 [amdgpu]
Jun  7 23:33:07 rct14s kernel: [ 8569.169357] Modules linked in: tls ccm 
michael_mic xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables libcrc32c nfnetlink rfcomm snd_seq_dummy snd_hrtimer nvme_fabrics 
cmac algif_hash algif_skcipher af_alg bnep qrtr_mhi amdgpu qrtr ath11k_pci 
snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_sof_amd_rembrandt 
snd_sof_amd_renoir joydev ath11k snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp 
snd_sof intel_rapl_msr intel_rapl_common btusb btrtl edac_mce_amd snd_ctl_led 
btbcm iommu_v2 snd_hda_codec_realtek qmi_helpers btintel drm_buddy gpu_sched 
btmtk kvm_amd snd_hda_codec_generic snd_sof_utils mac80211 snd_hda_codec_hdmi 
drm_suballoc_helper bluetooth uvcvideo drm_ttm_helper kvm snd_hda_intel 
snd_soc_core ttm binfmt_misc snd_intel_dspcfg videobuf2_vmalloc 
snd_intel_sdw_acpi uvc snd_hda_codec videobuf2_memops drm_display_helper 
videobuf2_v4l2 snd_compress videod
 ev snd_hda_core ac97_bus irqbypass cec crct10dif_pclmul
Jun  7 23:33:07 rct14s kernel: [ 8569.169428]  snd_pcm_dmaengine 
polyval_clmulni snd_hwdep snd_pci_ps rc_core polyval_generic 
ghash_clmulni_intel snd_rpl_pci_acp6x sha512_ssse3 snd_seq_midi thinkpad_acpi 
snd_acp_pci aesni_intel snd_seq_midi_event crypto_simd drm_kms_helper 
snd_rawmidi videobuf2_common nvram ecdh_generic snd_pci_acp6x input_leds cryptd 
cfg80211 snd_pcm ecc think_lmi i2c_algo_bit ledtrig_audio nls_iso8859_1 rapl mc 
serio_raw snd_seq hid_multitouch firmware_attributes_class platform_profile 
wmi_bmof snd_pci_acp5x syscopyarea ucsi_acpi snd_seq_device snd_rn_pci_acp3x 
sysfillrect typec_ucsi ccp k10temp snd_timer snd_acp_config libarc4 sysimgblt 
snd_soc_acpi mhi typec snd snd_pci_acp3x sch_fq_codel soundcore mac_hid amd_pmc 
acpi_tad overlay iptable_filter ip6table_filter ip6_tables br_netfilter bridge 
stp llc arp_tables drm msr parport_pc ppdev lp parport ramoops pstore_blk 
reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 nvme hid_generic 
thunderbolt psmouse 
 crc32_pclmul nvme_core xhci_pci i2c_hid_acpi i2c_piix4
Jun  7 23:33:07 rct14s kernel: [ 8569.169508]  xhci_pci_renesas i2c_hid 
nvme_common video hid wmi
Jun  7 23:33:07 rct14s kernel: [ 8569.169515] CPU: 4 PID: 1109 Comm: 
systemd-logind Tainted: GW  6.4.0-rc5patch_541535-dirty #1
Jun  7 23:33:07 rct14s kernel: [ 8569.169520] Hardware name: LENOVO 
21CQCTO1WW/21CQCTO1WW, BIOS R22ET60W (1.30 ) 02/09/2023
Jun  7 23:33:07 rct14s kernel: [ 8569.169522] RIP: 
0010:amdgpu_dm_atomic_commit_tail+0x3b30/0x41f0 [amdgpu]
Jun  7 23:33:07 rct14s kernel: [ 8569.169988] Code: ff 41 b9 01 00 00 00 31 f6 
4c 89 9d 88 fc ff ff ba 01 00 00 00 4c 89 95 a8 fc ff ff 50 51 48 c7 c1 b0 44 
72 c2 e9 e7 f9 ff ff <0f> 0b e9 a3 f3 ff ff 0f 0b 0f 0b e9 43 f3 ff ff 0f 0b e9 
b2 f3 ff
Jun  7 23:33:07 rct14s kernel: [ 8569.169991] RSP: 0018:a13f82d874f8 
EFLAGS: 00010002
Jun  7 23:33:07 rct14s kernel: [ 8569.169993] RAX: 0246 RBX: 
4e93 RCX: 
Jun  7 23:33:07 rct14s kernel: [ 8569.169995] RDX:  RSI: 
 RDI: 
Jun  7 23:33:07 rct14s kernel: [ 8569.169996] RBP: a13f82d87888 R08: 
 R09: 0002
Jun  7 23:33:07 rct14s kernel: [ 8569.169998] R10:  R11: 
 R12: 0246
Jun  7 23:33:07 rct14s kernel: [ 8569.16] R13: 9499aafb4118 R14: 
9499d0473980 R15: 9499aafb4000
Jun  7 23:33:07 rct14s kernel: [ 8569.17] FS:  7ff2bd8c7980() 
GS:94a07db0() knlGS:
Jun  7 23:33:07 rct14s kernel: [ 8569.170002] CS:  0010 DS:  ES:  CR0: 
80050033
Jun  7 23:33:07 rct14s kernel: [ 8569.170004] CR2: 

[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu Lunar)
   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/2016908

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

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

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

  MAAS Version: 3.3.2

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

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

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

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

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

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

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

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apparmor (Ubuntu Lunar)
   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/2016908

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

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

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

  MAAS Version: 3.3.2

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

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

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

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

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

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

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

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apparmor (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/2016908

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

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

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

  MAAS Version: 3.3.2

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

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

  
  Kernel Bug / Apparmor
  reproducer

  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
  $ wget 
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
  $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd 
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'

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

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

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

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

  
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
  util.c#L1252

  if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
  if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ? 
SIGINT : SIGTERM) < 0) {
  log_full_errno(prio, errno, "Failed to set death 
signal: %m");
  _exit(EXIT_FAILURE);
  }

  
  workaround set kernel commandline to `apparmor=1`
  

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+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 2023225] [NEW] Jammy update: v5.15.104 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.104 upstream stable release
   from git://git.kernel.org/

xfrm: Allow transport-mode states with AF_UNSPEC selector
drm/panfrost: Don't sync rpm suspension after mmu flushing
cifs: Move the in_send statistic to __smb_send_rqst()
drm/meson: fix 1px pink line on GXM when scaling video overlay
clk: HI655X: select REGMAP instead of depending on it
docs: Correct missing "d_" prefix for dentry_operations member d_weak_revalidate
scsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add()
ALSA: hda: Match only Intel devices with CONTROLLER_IN_GPU()
netfilter: nft_nat: correct length for loading protocol registers
netfilter: nft_masq: correct length for loading protocol registers
netfilter: nft_redir: correct length for loading protocol registers
netfilter: nft_redir: correct value of inet type `.maxattrs`
scsi: core: Fix a procfs host directory removal regression
tcp: tcp_make_synack() can be called from process context
nfc: pn533: initialize struct pn533_out_arg properly
ipvlan: Make skb->skb_iif track skb->dev for l3s mode
i40e: Fix kernel crash during reboot when adapter is in recovery mode
vdpa_sim: not reset state in vdpasim_queue_ready
vdpa_sim: set last_used_idx as last_avail_idx in vdpasim_queue_ready
PCI: s390: Fix use-after-free of PCI resources with per-function hotplug
drm/i915/display: Workaround cursor left overs with PSR2 selective fetch enabled
drm/i915/display/psr: Use drm damage helpers to calculate plane damaged area
drm/i915/display: clean up comments
drm/i915/psr: Use calculated io and fast wake lines
net/smc: fix NULL sndbuf_desc in smc_cdc_tx_handler()
qed/qed_dev: guard against a possible division by zero
net: dsa: mt7530: remove now incorrect comment regarding port 5
net: dsa: mt7530: set PLL frequency and trgmii only when trgmii is used
loop: Fix use-after-free issues
net: tunnels: annotate lockless accesses to dev->needed_headroom
net: phy: smsc: bail out in lan87xx_read_status if genphy_read_status fails
nfc: st-nci: Fix use after free bug in ndlc_remove due to race condition
net/smc: fix deadlock triggered by cancel_delayed_work_syn()
net: usb: smsc75xx: Limit packet length to skb->len
drm/bridge: Fix returned array size name for atomic_get_input_bus_fmts kdoc
block: null_blk: Fix handling of fake timeout request
nvme: fix handling single range discard request
nvmet: avoid potential UAF in nvmet_req_complete()
block: sunvdc: add check for mdesc_grab() returning NULL
ice: xsk: disable txq irq before flushing hw
net: dsa: mv88e6xxx: fix max_mtu of 1492 on 6165, 6191, 6220, 6250, 6290
ravb: avoid PHY being resumed when interface is not up
sh_eth: avoid PHY being resumed when interface is not up
ipv4: Fix incorrect table ID in IOCTL path
net: usb: smsc75xx: Move packet length check to prevent kernel panic in skb_pull
net/iucv: Fix size of interrupt data
qed/qed_mng_tlv: correctly zero out ->min instead of ->hour
ethernet: sun: add check for the mdesc_grab()
bonding: restore IFF_MASTER/SLAVE flags on bond enslave ether type change
bonding: restore bond's IFF_SLAVE flag if a non-eth dev enslave fails
hwmon: (adt7475) Display smoothing attributes in correct order
hwmon: (adt7475) Fix masking of hysteresis registers
hwmon: (xgene) Fix use after free bug in xgene_hwmon_remove due to race 
condition
hwmon: (ina3221) return prober error code
hwmon: (ucd90320) Add minimum delay between bus accesses
hwmon: tmp512: drop of_match_ptr for ID table
kconfig: Update config changed flag before calling callback
hwmon: (adm1266) Set `can_sleep` flag for GPIO chip
hwmon: (ltc2992) Set `can_sleep` flag for GPIO chip
media: m5mols: fix off-by-one loop termination error
mmc: atmel-mci: fix race between stop command and start of next command
jffs2: correct logic when creating a hole in jffs2_write_begin
ext4: fail ext4_iget if special inode unallocated
ext4: update s_journal_inum if it changes after journal replay
ext4: fix task hung in ext4_xattr_delete_inode
drm/amdkfd: Fix an illegal memory access
net/9p: fix bug in client create for .L
sh: intc: Avoid spurious sizeof-pointer-div warning
drm/amd/display: fix shift-out-of-bounds in CalculateVMAndRowBytes
ext4: fix possible double unlock when moving a directory
tty: serial: fsl_lpuart: skip waiting for transmission complete when 
UARTCTRL_SBK is asserted
serial: 8250_em: Fix UART port type
serial: 8250_fsl: fix handle_irq locking
firmware: xilinx: don't make a sleepable memory allocation from an atomic 
context
s390/ipl: add missing intersection check to ipl_report 

[Kernel-packages] [Bug 2023224] [NEW] Jammy update: v5.15.103 upstream stable release

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   v5.15.103 upstream stable release
   from git://git.kernel.org/

fs: prevent out-of-bounds array speculation when closing a file descriptor
btrfs: fix percent calculation for bg reclaim message
perf inject: Fix --buildid-all not to eat up MMAP2
fork: allow CLONE_NEWTIME in clone3 flags
x86/CPU/AMD: Disable XSAVES on AMD family 0x17
drm/amdgpu: fix error checking in amdgpu_read_mm_registers for soc15
drm/connector: print max_requested_bpc in state debugfs
staging: rtl8723bs: Pass correct parameters to cfg80211_get_bss()
ext4: fix cgroup writeback accounting with fs-layer encryption
ext4: fix RENAME_WHITEOUT handling for inline directories
ext4: fix another off-by-one fsmap error on 1k block filesystems
ext4: move where set the MAY_INLINE_DATA flag is set
ext4: fix WARNING in ext4_update_inline_data
ext4: zero i_disksize when initializing the bootloader inode
nfc: change order inside nfc_se_io error path
KVM: Optimize kvm_make_vcpus_request_mask() a bit
KVM: Pre-allocate cpumasks for kvm_make_all_cpus_request_except()
KVM: Register /dev/kvm as the _very_ last thing during initialization
KVM: SVM: Don't rewrite guest ICR on AVIC IPI virtualization failure
KVM: SVM: Process ICR on AVIC IPI delivery failure due to invalid target
fs: dlm: fix log of lowcomms vs midcomms
fs: dlm: add midcomms init/start functions
fs: dlm: start midcomms before scand
udf: Fix off-by-one error when discarding preallocation
f2fs: avoid down_write on nat_tree_lock during checkpoint
f2fs: do not bother checkpoint by f2fs_get_node_info
f2fs: retry to update the inode page given data corruption
ipmi:ssif: Increase the message retry time
ipmi:ssif: Add a timer between request retries
irqdomain: Refactor __irq_domain_alloc_irqs()
iommu/vt-d: Fix PASID directory pointer coherency
block/brd: add error handling support for add_disk()
brd: mark as nowait compatible
arm64: efi: Make efi_rt_lock a raw_spinlock
RISC-V: Avoid dereferening NULL regs in die()
riscv: Avoid enabling interrupts in die()
riscv: Add header include guards to insn.h
scsi: core: Remove the /proc/scsi/${proc_name} directory earlier
regulator: Flag uncontrollable regulators as always_on
regulator: core: Fix off-on-delay-us for always-on/boot-on regulators
regulator: core: Use ktime_get_boottime() to determine how long a regulator was 
off
ext4: Fix possible corruption when moving a directory
drm/nouveau/kms/nv50-: remove unused functions
drm/nouveau/kms/nv50: fix nv50_wndw_new_ prototype
drm/msm: Fix potential invalid ptr free
drm/msm/a5xx: fix setting of the CP_PREEMPT_ENABLE_LOCAL register
drm/msm/a5xx: fix highest bank bit for a530
drm/msm/a5xx: fix the emptyness check in the preempt code
drm/msm/a5xx: fix context faults during ring switch
bgmac: fix *initial* chip reset to support BCM5358
nfc: fdp: add null check of devm_kmalloc_array in 
fdp_nci_i2c_read_device_properties
powerpc: dts: t1040rdb: fix compatible string for Rev A boards
ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping()
selftests: nft_nat: ensuring the listening side is up before starting the client
perf stat: Fix counting when initial delay configured
net: lan78xx: fix accessing the LAN7800's internal phy specific registers from 
the MAC driver
net: caif: Fix use-after-free in cfusbl_device_notify()
ice: copy last block omitted in ice_get_module_eeprom()
bpf, sockmap: Fix an infinite loop error when len is 0 in 
tcp_bpf_recvmsg_parser()
drm/msm/dpu: fix len of sc7180 ctl blocks
net: stmmac: add to set device wake up flag when stmmac init phy
net: phylib: get rid of unnecessary locking
bnxt_en: Avoid order-5 memory allocation for TPA data
netfilter: tproxy: fix deadlock due to missing BH disable
btf: fix resolving BTF_KIND_VAR after ARRAY, STRUCT, UNION, PTR
net: phy: smsc: Cache interrupt mask
net: phy: smsc: fix link up detection in forced irq mode
net: ethernet: mtk_eth_soc: fix RX data corruption issue
scsi: megaraid_sas: Update max supported LD IDs to 240
platform: x86: MLX_PLATFORM: select REGMAP instead of depending on it
net/smc: fix fallback failed while sendmsg with fastopen
octeontx2-af: Unlock contexts in the queue context cache in case of fault 
detection
SUNRPC: Fix a server shutdown leak
net: dsa: mt7530: permit port 5 to work without port 6 on MT7621 SoC
af_unix: Remove unnecessary brackets around CONFIG_AF_UNIX_OOB.
af_unix: fix struct pid leaks in OOB support
riscv: Use READ_ONCE_NOCHECK in imprecise unwinding stack mode
s390/ftrace: remove dead code
RISC-V: Don't check text_mutex during 

[Kernel-packages] [Bug 2018125] Re: do-release-upgrade fails due to full zfs partition

[Chelmite]

Yes, Brian. I'm still not up to 100% after the failed upgrade to 23.04.
I don't have printing, a clipboard manager, and several other things
that used to work, plus all the external ppas.

I did get rid of zfs, because being able to work is more important than
being able to have a redundant file system.

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

Title:
  do-release-upgrade fails due to full zfs partition

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I used do-release-upgrade to upgrade from 22.10 x86-64 to 23.10.
  Towards the end of the upgrade, it rebooted, but stuck me in the recovery 
console.
  I enabled networking and opened a root shell.
  1. Networking was not working. I fiddled with this for days, and could not 
get networking working. I tried starting NetworkManager, playing with rfkill, 
and a few other things, but, ultimately, could not get networking working.
  2. The problem that seemed to kill the upgrade was the zfs boot partition 
being too full for the new image, even though the new image was present. After 
a few days I found a way to remove old snapshots and created lots of free space 
on /boot. Linux still doesn't boot.

  Ultimately, if FOSS is supposed to be a good thing, and attract non-
  sysadmins, it should be easy to install/upgrade.

  1. do-release-upgrade should be able to deal with full filesystems,
  whether they're zfs or ext4 or the other front-running file systems,
  giving the user the tools to remove snapshots and/or files to make the
  new upgrade/release work as flawlessly as it can. I should be able to
  convert a zfs partition to ext4, (or vice versa) and get on with my
  real work.

  2. When the user is dumped into the recovery console, give him more
  tools to work with. There should be, at the very least, a way to get
  the network working when you press "enable networking" (not by having
  to download and figure out how to use network-tools, ifconfig, rfkill,
  dhclient, etc.), and deal with and fix ZFS issues.

  I know this isn't going to be fixed by the weekend, so I'm considering
  3 "nuclear" options, in decreasing order of desirability: (1) reformat
  the zfs boot partition as ext4, then copy the (saved) contents of
  /boot into the pristine partition. (2) Reinstall 23.04 from the thumb
  drive. I learned, decades ago, to keep my user partition on a separate
  drive, so it should be safe. What I'll lose is my network and wifi
  settings and printer setups. There are, undoubtedly other things that
  will have to be recovered, but those are the most important. (3) Pay
  through the nose for an Apple. I'd have to learn a new UI and transfer
  my files somehow, and bow down to my kids who have been pushing for me
  to get off this old Linux thing. "You'll have to pry my cold dead
  fingers off my Linux computers..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018125/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

[Roemer Claasen]

Hi Mario,

I've recompiled kernel 6.4-rc5 with the patch applied, and get the same
error (see below). No screen tearing/ flicker - yet. I'll report back
after a day of work to see if the patch had any effect.

Thanks again for your support, best,

Roemer


$ cat /proc/cmdline:

BOOT_IMAGE=/boot/vmlinuz-6.4.0-rc5patch_541535-dirty
root=UUID=41d8f993-282a-48a5-b355-6f537a3a17ab ro quiet splash
vt.handoff=7

$ cat /var/log/kern.log:

Jun  7 21:30:28 rct14s kernel: [ 1211.044086] WARNING: CPU: 3 PID: 7362 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:226 
dmub_psr_enable+0x10b/0x120 [amdgpu]
Jun  7 21:30:28 rct14s kernel: [ 1211.044741] Modules linked in: tls ccm 
michael_mic xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables libcrc32c nfnetlink rfcomm snd_seq_dummy snd_hrtimer nvme_fabrics 
cmac algif_hash algif_skcipher af_alg bnep qrtr_mhi amdgpu qrtr ath11k_pci 
snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_sof_amd_rembrandt 
snd_sof_amd_renoir joydev ath11k snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp 
snd_sof intel_rapl_msr intel_rapl_common btusb btrtl edac_mce_amd snd_ctl_led 
btbcm iommu_v2 snd_hda_codec_realtek qmi_helpers btintel drm_buddy gpu_sched 
btmtk kvm_amd snd_hda_codec_generic snd_sof_utils mac80211 snd_hda_codec_hdmi 
drm_suballoc_helper bluetooth uvcvideo drm_ttm_helper kvm snd_hda_intel 
snd_soc_core ttm binfmt_misc snd_intel_dspcfg videobuf2_vmalloc 
snd_intel_sdw_acpi uvc snd_hda_codec videobuf2_memops drm_display_helper 
videobuf2_v4l2 snd_compress videod
 ev snd_hda_core ac97_bus irqbypass cec crct10dif_pclmul
Jun  7 21:30:28 rct14s kernel: [ 1211.044873]  snd_pcm_dmaengine 
polyval_clmulni snd_hwdep snd_pci_ps rc_core polyval_generic 
ghash_clmulni_intel snd_rpl_pci_acp6x sha512_ssse3 snd_seq_midi thinkpad_acpi 
snd_acp_pci aesni_intel snd_seq_midi_event crypto_simd drm_kms_helper 
snd_rawmidi videobuf2_common nvram ecdh_generic snd_pci_acp6x input_leds cryptd 
cfg80211 snd_pcm ecc think_lmi i2c_algo_bit ledtrig_audio nls_iso8859_1 rapl mc 
serio_raw snd_seq hid_multitouch firmware_attributes_class platform_profile 
wmi_bmof snd_pci_acp5x syscopyarea ucsi_acpi snd_seq_device snd_rn_pci_acp3x 
sysfillrect typec_ucsi ccp k10temp snd_timer snd_acp_config libarc4 sysimgblt 
snd_soc_acpi mhi typec snd snd_pci_acp3x sch_fq_codel soundcore mac_hid amd_pmc 
acpi_tad overlay iptable_filter ip6table_filter ip6_tables br_netfilter bridge 
stp llc arp_tables drm msr parport_pc ppdev lp parport ramoops pstore_blk 
reed_solomon pstore_zone efi_pstore ip_tables x_tables autofs4 nvme hid_generic 
thunderbolt psmouse 
 crc32_pclmul nvme_core xhci_pci i2c_hid_acpi i2c_piix4
Jun  7 21:30:28 rct14s kernel: [ 1211.045018]  xhci_pci_renesas i2c_hid 
nvme_common video hid wmi
Jun  7 21:30:28 rct14s kernel: [ 1211.045030] CPU: 3 PID: 7362 Comm: 
kworker/3:2H Not tainted 6.4.0-rc5patch_541535-dirty #1
Jun  7 21:30:28 rct14s kernel: [ 1211.045035] Hardware name: LENOVO 
21CQCTO1WW/21CQCTO1WW, BIOS R22ET60W (1.30 ) 02/09/2023
Jun  7 21:30:28 rct14s kernel: [ 1211.045039] Workqueue: events_highpri 
dm_irq_work_func [amdgpu]
Jun  7 21:30:28 rct14s kernel: [ 1211.045632] RIP: 
0010:dmub_psr_enable+0x10b/0x120 [amdgpu]
Jun  7 21:30:28 rct14s kernel: [ 1211.046182] Code: 48 2b 04 25 28 00 00 00 75 
24 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d 31 c0 89 c2 89 c1 89 c6 89 c7 41 
89 c0 c3 cc cc cc cc <0f> 0b eb cd e8 5c cb 89 d7 66 66 2e 0f 1f 84 00 00 00 00 
00 90 90
Jun  7 21:30:28 rct14s kernel: [ 1211.046186] RSP: 0018:a13f8b907c80 
EFLAGS: 00010246
Jun  7 21:30:28 rct14s kernel: [ 1211.046191] RAX:  RBX: 
03e9 RCX: 
Jun  7 21:30:28 rct14s kernel: [ 1211.046193] RDX:  RSI: 
 RDI: 
Jun  7 21:30:28 rct14s kernel: [ 1211.046195] RBP: a13f8b907cf8 R08: 
 R09: 
Jun  7 21:30:28 rct14s kernel: [ 1211.046197] R10:  R11: 
 R12: 
Jun  7 21:30:28 rct14s kernel: [ 1211.046198] R13: 9499a513f4c0 R14: 
 R15: 9499a52b8c00
Jun  7 21:30:28 rct14s kernel: [ 1211.046200] FS:  () 
GS:94a07dac() knlGS:
Jun  7 21:30:28 rct14s kernel: [ 1211.046203] CS:  0010 DS:  ES:  CR0: 
80050033
Jun  7 21:30:28 rct14s kernel: [ 1211.046205] CR2: 55ffdb0e9040 CR3: 
00011bf0c000 CR4: 00750ee0
Jun  7 21:30:28 rct14s kernel: [ 1211.046208] PKRU: 5554
Jun  7 21:30:28 rct14s kernel: [ 1211.046209] Call Trace:
Jun  7 21:30:28 rct14s kernel: [ 1211.046213]  
Jun  7 21:30:28 rct14s kernel: [ 1211.046218]  ? show_regs+0x72/0x90
Jun  7 21:30:28 rct14s kernel: [ 1211.046229]  ? dmub_psr_enable+0x10b/0x120 
[amdgpu]
Jun  7 21:30:28 rct14s kernel: [ 1211.04]  ? __warn+0x8d/0x160
Jun  7 21:30:28 rct14s kernel: [ 1211.046672]  ? dmub_psr_enable+0x10b/0x120 

[Kernel-packages] [Bug 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Thadeu Lima de Souza Cascardo]

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

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

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

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

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

** Changed in: linux-oem-6.1 (Ubuntu Mantic)
   Status: New => 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/2023220

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  New
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Thadeu Lima de Souza Cascardo]

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

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

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

** Changed in: linux-oem-6.1 (Ubuntu Trusty)
   Status: New => 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/2023220

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Trusty:
  Incomplete
Status in linux-oem-6.1 source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Incomplete
Status in linux-oem-6.1 source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux-oem-6.1 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-6.1 source package in Focal:
  New
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-6.1 source package in Jammy:
  New
Status in linux source package in Kinetic:
  In Progress
Status in linux-oem-6.1 source package in Kinetic:
  New
Status in linux source package in Lunar:
  In Progress
Status in linux-oem-6.1 source package in Lunar:
  New
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  New

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux (Ubuntu Lunar)
   Status: Incomplete => In Progress

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

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Kinetic:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

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

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 Bionic)
   Status: New => Incomplete

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
   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/2023220

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Kinetic:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2023220] [NEW] Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled

[Thadeu Lima de Souza Cascardo]

*** This bug is a security vulnerability ***

Public security bug reported:

[Impact]
When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the 
global TLB entries. This can lead to info leak or undefined behavior.

[Mitigation]
Boot with nopcid on affected systems.

[Test case]
There is no particular test case.

[Potential regressions]
This affects performance on the affected systems. TLB behavior could also be 
affected.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Fix Released

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

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

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

** Affects: linux (Ubuntu Focal)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Incomplete

** Affects: linux (Ubuntu Jammy)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Incomplete

** Affects: linux (Ubuntu Kinetic)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Lunar)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Mantic)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: Fix Released

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Mantic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Lunar)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Kinetic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

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

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

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

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

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

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

Title:
  Some INVLPG implementations can leave Global translations unflushed
  when PCIDs are enabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Jammy:
  Incomplete
Status in linux source package in Kinetic:
  In Progress
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]
  When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush 
the global TLB entries. This can lead to info leak or undefined behavior.

  [Mitigation]
  Boot with nopcid on affected systems.

  [Test case]
  There is no particular test case.

  [Potential regressions]
  This affects performance on the affected systems. TLB behavior could also be 
affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2022981] Re: Frequent hard reboots on RaptorLake

[Shane McKee]

Unfortunately, it looks like removing drm.debug=0xe helps with
consistent reproduction of this bug. So it sounds like we're dealing
with some sort of timing issue.

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

Title:
  Frequent hard reboots on RaptorLake

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can repro in multiple ways:

  1. Unplug my HDMI monitor. This is pretty much a guaranteed reboot.
  2. Using hardware accelerated Chromium, switching between google profiles 
seems to trigger a crash and full reboot pretty often.

  These could be two separate bugs. I'm not sure I'd be unlucky enough
  to have two full reboot bugs at the same time though. Happy to help
  with more debugging

  Release: Jammy
  Chromium version: 115.0.5762.4-hwacc
  snap refresh --channel=latest/edge/hwacc chromium

  What you expected to happen
  1. HDMI monitor disconnects, and no reboots happen.
  2. I can switch Chromium profiles without a reboot

  What happened instead
  Both actions cause a reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  6 16:09:12 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-41-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-43-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   tp_smapi/0.43, 5.19.0-41-generic, x86_64: installed
   tp_smapi/0.43, 5.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5630]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:]
  InstallationDate: Installed on 2023-04-20 (46 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: System76 Gazelle
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_90m3zy@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_90m3zy ro drm.debug=0xe quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2023
  dmi.bios.release: 4.19
  dmi.bios.vendor: coreboot
  dmi.bios.version: 2023-03-22_799ed79
  dmi.board.name: Gazelle
  dmi.board.vendor: System76
  dmi.board.version: gaze18
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr2023-03-22_799ed79:bd03/22/2023:br4.19:efr0.0:svnSystem76:pnGazelle:pvrgaze18:rvnSystem76:rnGazelle:rvrgaze18:cvnSystem76:ct9:cvr:sku:
  dmi.product.name: Gazelle
  dmi.product.version: gaze18
  dmi.sys.vendor: System76
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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 N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022981/+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 1950627] Re: ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg: Connection refused

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~diewald/+git/rt-hints/+merge/444282

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

Title:
  ubuntu_kernel_selftests:net:udpgro_fwd.sh: udpgso_bench_tx: sendmsg:
  Connection refused

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Confirmed

Bug description:
  This is from ADT testing (amd64) but I believe I occasionally saw this
  before. It feels like sometimes the receiver does not get ready before
  the transmission starts. IIRC this goes away when re-trying.

  02:52:31 DEBUG| [stdout] # selftests: net: udpgro_fwd.sh
  02:52:31 DEBUG| [stdout] # IPv4
  02:52:31 DEBUG| [stdout] # No GRO   ok
  02:52:32 DEBUG| [stdout] # GRO frag listok
  02:52:32 DEBUG| [stdout] # GRO fwd  ok
  02:52:33 DEBUG| [stdout] # UDP fwd perfudp rx:
333 MB/s   271894 calls/s
  02:52:33 DEBUG| [stdout] # udp tx:378 MB/s 6422 calls/s   6422 msg/s
  02:52:34 DEBUG| [stdout] # udp rx:383 MB/s   312480 calls/s
  02:52:34 DEBUG| [stdout] # udp tx:383 MB/s 6506 calls/s   6506 msg/s
  02:52:35 DEBUG| [stdout] # udp rx:381 MB/s   310202 calls/s
  02:52:35 DEBUG| [stdout] # udp tx:380 MB/s 6458 calls/s   6458 msg/s
  02:52:36 DEBUG| [stdout] # UDP GRO fwd perfudp rx:
344 MB/s   280814 calls/s
  02:52:36 DEBUG| [stdout] # udp tx:389 MB/s 6612 calls/s   6612 msg/s
  02:52:37 DEBUG| [stdout] # udp rx:364 MB/s   297088 calls/s
  02:52:37 DEBUG| [stdout] # udp tx:383 MB/s 6512 calls/s   6512 msg/s
  02:52:38 DEBUG| [stdout] # udp rx:448 MB/s   365435 calls/s
  02:52:38 DEBUG| [stdout] # udp tx:453 MB/s 7686 calls/s   7686 msg/s
  02:52:39 DEBUG| [stdout] # GRO frag list over UDP tunnelok
  02:52:39 DEBUG| [stdout] # GRO fwd over UDP tunnel  ok
  02:52:39 DEBUG| [stdout] # UDP tunnel fwd perf 
./udpgso_bench_tx: sendmsg: Connection refused
  02:52:39 DEBUG| [stdout] #  fail client exit code 1, server 0
  02:52:40 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx:
236 MB/s   192389 calls/s
  02:52:41 DEBUG| [stdout] # udp tx:284 MB/s 4826 calls/s   4826 msg/s
  02:52:41 DEBUG| [stdout] # udp rx:295 MB/s   240586 calls/s
  02:52:42 DEBUG| [stdout] # udp tx:306 MB/s 5206 calls/s   5206 msg/s
  02:52:42 DEBUG| [stdout] # udp rx:306 MB/s   249784 calls/s
  02:52:43 DEBUG| [stdout] # udp tx:310 MB/s 5263 calls/s   5263 msg/s
  02:52:43 DEBUG| [stdout] # IPv6
  02:52:43 DEBUG| [stdout] # No GRO   ok
  02:52:43 DEBUG| [stdout] # GRO frag listok
  02:52:43 DEBUG| [stdout] # GRO fwd  ok
  02:52:44 DEBUG| [stdout] # UDP fwd perfudp rx:
 82 MB/s66844 calls/s
  02:52:45 DEBUG| [stdout] # udp tx:334 MB/s 5668 calls/s   5668 msg/s
  02:52:45 DEBUG| [stdout] # udp rx:374 MB/s   305206 calls/s
  02:52:46 DEBUG| [stdout] # udp tx:375 MB/s 6377 calls/s   6377 msg/s
  02:52:46 DEBUG| [stdout] # udp rx:373 MB/s   303948 calls/s
  02:52:47 DEBUG| [stdout] # udp tx:371 MB/s 6299 calls/s   6299 msg/s
  02:52:48 DEBUG| [stdout] # UDP GRO fwd perfudp rx:
340 MB/s   277046 calls/s
  02:52:48 DEBUG| [stdout] # udp tx:389 MB/s 6601 calls/s   6601 msg/s
  02:52:49 DEBUG| [stdout] # udp rx:390 MB/s   318311 calls/s
  02:52:49 DEBUG| [stdout] # udp tx:391 MB/s 6639 calls/s   6639 msg/s
  02:52:50 DEBUG| [stdout] # udp rx:396 MB/s   322528 calls/s
  02:52:50 DEBUG| [stdout] # udp tx:406 MB/s 6891 calls/s   6891 msg/s
  02:52:50 DEBUG| [stdout] # GRO frag list over UDP tunnelok
  02:52:50 DEBUG| [stdout] # GRO fwd over UDP tunnel  ok
  02:52:52 DEBUG| [stdout] # UDP tunnel fwd perf udp rx:
 93 MB/s76354 calls/s
  02:52:52 DEBUG| [stdout] # udp tx:257 MB/s 4360 calls/s   4360 msg/s
  02:52:53 DEBUG| [stdout] # udp rx:297 MB/s   241883 calls/s
  02:52:53 DEBUG| [stdout] # udp tx:315 MB/s 5352 calls/s   5352 msg/s
  02:52:54 DEBUG| [stdout] # udp rx:286 MB/s   233207 calls/s
  02:52:54 DEBUG| [stdout] # udp tx:304 MB/s 5172 calls/s   5172 msg/s
  02:52:55 DEBUG| [stdout] # UDP tunnel GRO fwd perf udp rx:
267 MB/s   217607 calls/s
  02:52:55 DEBUG| [stdout] # udp tx:297 MB/s 5039 calls/s   5039 msg/s
  02:52:56 DEBUG| [stdout] # udp rx:300 MB/s   244255 calls/s
  02:52:56 DEBUG| [stdout] # udp tx:304 MB/s 5164 calls/s   5164 

[Kernel-packages] [Bug 2013325] Re: net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels (TXTIME rel returned '', expected 'OK')

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~diewald/+git/rt-hints/+merge/444282

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

Title:
  net:cmsg_time.sh in ubuntu_kernel_selftests failed on RISCV64 kernels
  (TXTIME rel returned '', expected 'OK')

Status in ubuntu-kernel-tests:
  New
Status in linux-allwinner package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux-starfive package in Ubuntu:
  New
Status in linux-allwinner source package in Kinetic:
  New
Status in linux-riscv source package in Kinetic:
  New
Status in linux-starfive source package in Kinetic:
  New

Bug description:
  Issue found on Kinetic 5.19 RISCV kernels:

  * kinetic/linux-allwinner/5.19.0-1009.9
  # selftests: net: cmsg_time.sh
  #   Case UDPv4  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv4  - TXTIME rel returned '', expected 'OK'
  #   Case UDPv6  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv6  - TXTIME rel returned '', expected 'OK'
  #   Case RAWv6  - TXTIME rel returned '', expected 'OK'
  # FAIL - 5/36 cases failed
  not ok 1 selftests: net: cmsg_time.sh # exit=1

  * kinetic/linux-riscv/5.19.0-1015.16
  # selftests: net: cmsg_time.sh
  #   Case ICMPv4  - TXTIME rel returned '', expected 'OK'
  #   Case UDPv6  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv6  - TXTIME rel returned '', expected 'OK'
  #   Case RAWv6  - TXTIME rel returned '', expected 'OK'
  # FAIL - 4/36 cases failed
  not ok 1 selftests: net: cmsg_time.sh # exit=1

  * kinetic/linux-starfive/5.19.0-1014.16
  # selftests: net: cmsg_time.sh
  #   Case UDPv4  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv4  - TXTIME rel returned '', expected 'OK'
  #   Case UDPv6  - TXTIME rel returned '', expected 'OK'
  #   Case ICMPv6  - TXTIME rel returned '', expected 'OK'
  #   Case RAWv6  - TXTIME rel returned '', expected 'OK'
  # FAIL - 5/36 cases failed
  not ok 1 selftests: net: cmsg_time.sh # exit=1

  This is only affecting RISCV64 kernels, it does not affect kinetic
  generic kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2013325/+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 2019736] Re: Fix hangs when connected to Freesync displays

[Bug Watch Updater]

** Changed in: linux
   Status: New => Fix Released

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

Title:
  Fix hangs when connected to Freesync displays

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Kinetic:
  New
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  New
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  New
Status in linux-oem-6.1 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

   * Selecting certain resolutions causes hangs when an AMD GPU is
  connected to a display that supports FreeSync

  [ Test Plan ]

   * Verify display with freesync doesn't hang anymore

  [ Where problems could occur ]

   * AMD GPU could stop displaying

  [ Other Info ]

   * This issue was reported upstream to AMD here:  
https://gitlab.freedesktop.org/drm/amd/-/issues/2162
   * It has been fixed in kernel 6.4-rc1:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=da5e14909776edea4462672fb4a3007802d262e7

   * AMD will CC it to stable to fix any remaining affected open stable
  releases, but as 5.19 is EOL upstream, want to ensure that Canonical
  picks up this patch in the 5.19 series as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2019736/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms

[Chris Chiu]

** Tags added: oem-priority originate-from-2019873 somerville

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

Title:
  Add support of Smart Amplifier IC ALC1319D  on Intel platforms

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

Bug description:
  [Impact]
  Speaker is not functional on some Dell machines of Intel RPL platforms

  [Fix]
  Here's the patch submitted by Intel.
  
https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy Output` shown on the Audio output option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

[Paul Rockwell]

Apologies for the typo - I meant the linux-nvidia-5.19/5.19.0-1014.14
kernel in -proposed.

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than booting a previous kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+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 2007001] Re: vmwgfx fails to reserve graphics buffer on aarch64 leading to blank display

[Paul Rockwell]

I can verify that the 5.10.0-1014 kernel in -proposed does boot on a
VMware Fusion VM running Jammy aarch64, and that the console appears as
expected. I'm hesitant to change the tag to verification-done-jammy
since I don't have anything nVidia on arm64. I can do that if my testing
meets what you're looking for.

I've verified that the vmwgfx driver has claimed the fb memory:

dmesg shows:

[0.867225] vmwgfx :00:0f.0: [drm] Register MMIO at 0x0x3d00 
size is 4096 kiB
[0.867229] vmwgfx :00:0f.0: [drm] VRAM at 0x7000 size is 
131072 kiB
[0.867234] vmwgfx :00:0f.0: [drm] Running on SVGA version 3.
[0.867237] vmwgfx :00:0f.0: [drm] Capabilities: cursor, cursor bypass, 
alpha cursor, pitchlock, irq mask, traces, comma
nd buffers, command buffers 2, gbobject, dx, hp cmd queue, no bb restriction, 
cap2 register, 
[0.867241] vmwgfx :00:0f.0: [drm] Capabilities2: grow otable, intra 
surface copy, dx2, gb memsize 2, screendma reg, ota
ble ptdepth2, non ms to ms stretchblt, cursor mob, mshint, cb max size 4mb, 
dx3, frame type, trace full fb, extra regs, lo stag
ing, 
[0.867243] vmwgfx :00:0f.0: [drm] DMA map mode: Caching DMA mappings.
[0.867279] vmwgfx :00:0f.0: [drm] Legacy memory limits: VRAM = 4096 kB, 
FIFO = 256 kB, surface = 524288 kB
[0.867281] vmwgfx :00:0f.0: [drm] MOB limits: max mob size = 262144 kB, 
max mob pages = 196608
[0.867283] vmwgfx :00:0f.0: [drm] Maximum display memory size is 262144 
kiB

and cat /proc/iomem shows:

5000-7fff : PCI Bus :00
  7000-77ff : :00:0f.0
7000-77ff : vmwgfx probe

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

Title:
  vmwgfx fails to reserve graphics buffer on aarch64 leading to blank
  display

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Kinetic:
  Fix Committed

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

  [Impact]

  Numerous VMWare users have reported that vmwgfx cannot reserve the
  memory region for the graphics framebuffer, leading their VMs to have
  blank screens.

  They see the following in dmesg:

  [ 11.135360] vmwgfx :00:0f.0: BAR 2: can't reserve [mem 
0x7000-0x77ff 64bit pref]
  [ 11.135366] vmwgfx: probe of :00:0f.0 failed with error -16

  And a cat /proc/iomem shows this:

  5000-7fff : PCI Bus :00
7000-77ff : :00:0f.0
  7000-702f : BOOTFB

  The kernel has failed to release this memory region for vmwgfx to
  occupy.

  Most affected users are on aarch64, with the host being Apple silicon
  systems.

  [Fix]

  The regression was introduced by the below commit in
  5.19.0-30-generic:

  commit 5e01376124309b4dbd30d413f43c0d9c2f60edea
  Author: Thomas Zimmermann 
  Date: Mon Jul 18 09:23:18 2022 +0200
  Subject: video/aperture: Disable and unregister sysfb devices via aperture 
helpers
  Link: 
https://github.com/torvalds/linux/commit/5e01376124309b4dbd30d413f43c0d9c2f60edea

  This commit was part of a larger refactoring of the video subsystem,
  and requires the entire series to function correctly. You can review
  the whole series below:

  https://patchwork.freedesktop.org/series/106040/

  The patch series also requires quite a few additional fixups to fix
  bugs introduced by the series, making the size about 15 commits in
  total. The contents of the series don't really fix any bugs, and their
  purpose is to refactor the code for future changes to the fbdev
  subsystem, and really aren't appropriate to be backported to a stable
  kernel series.

  "video/aperture: Disable and unregister sysfb devices via aperture
  helpers" seems to have been selected for -stable by mistake by its
  fixes: tag, and was pulled into upstream stable by a robot with little
  human review.

  The best course of action is to revert. No action needed for Lunar, as
  the entire series is present in that release.

  [Testcase]

  This bug affects users running Ubuntu in VMWare VMs, notably on
  aarch64 devices, like modern Apple computers.

  Start a Kinetic or Jammy-HWE Server or Desktop VM in VMWare Fusion on
  Apple silicon, and see if the display comes up or not.

  Affected users will see a blank screen.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2007001-test

  If you install the test kernel and reboot, you will be able to see the
  screen on your VM like normal.

  [Where problems could occur]

  This commit changes when the sysfb is disabled and memory region for
  the graphics framebuffer is released to the proper device driver.

  If a regression were to occur, then graphics drivers may fail to
  reserve the framebuffer memory, and fail to start, leaving users with
  a blank screen.

  There are no workarounds, other than 

[Kernel-packages] [Bug 2016881] Re: Building for Focal fails on riscv64

[Sebastien Bacher]

Unsubscribing ubuntu-sponsors, please subscribe them back once the
requested changes are made. Also if you want that uploaded to focal the
bug description needs to be compliant with what is described on
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

Title:
  Building for Focal fails on riscv64

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Bionic:
  Invalid
Status in zfs-linux source package in Focal:
  Incomplete

Bug description:
  Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a
  single patch missing:
  https://github.com/openzfs/zfs/commit/4254e407294b211f3399da2ee131b45fe9f4ac80

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2016881/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

[Mario Limonciello]

OK let's look for results with that patch when you have time.

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

Title:
  [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

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

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+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 2022826] Re: Ethernet hangs

[John Rose]

As I said before the Wired line has disappeared again. So I can't try to
connect by Ethernet. dmesg output is attached.

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+attachment/5678461/+files/dmesg.txt

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

Title:
  Ethernet hangs

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I'm now getting my wired (i.e. Ethernet) connection hanging on trying
  to connect. I've tried switching ports (on the router) and using a
  different cable, but still the same.

  ifconfig shows for Ethernet:
  enp2s0: flags=4163 mtu 1500
  ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet)
  RX packets 2779 bytes 250524 (250.5 KB)
  RX errors 0 dropped 1 overruns 0 frame 0
  TX packets 355 bytes 72171 (72.1 KB)
  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  sudo lshw -C enp2s0 shows nothing

  lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]:
  Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
  (rev 05)

  I found a web page: https://tutorialforlinux.com/2021/05...based-systems/
  I followed the instructions and installed realtek-r8125-dkms package OK. On 
rebooting, I followed the instructed procedure (shown when installing the 
package) of creating a password and then entering it when requested on the 
reboot. But still same problem. Any ideas what to do?
  PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is 
a little flaky due to walls) in order to post this question.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.13
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  3 07:29:15 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  InstallationDate: Installed on 2022-08-21 (285 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-43-generic N/A
   linux-backports-modules-5.19.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago)
  dmi.bios.date: 03/18/2021
  dmi.bios.release: 4.5
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: 0405
  dmi.board.asset.tag: Default string
  dmi.board.name: PN50-E1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku:
  dmi.product.family: Vivo PC
  dmi.product.name: MINIPC PN50-E1
  dmi.product.version: 0405
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+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 2023201] 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 2023201

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 in Ubuntu.
https://bugs.launchpad.net/bugs/2023201

Title:
  Add support of Smart Amplifier IC ALC1319D  on Intel platforms

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  [Impact]
  Speaker is not functional on some Dell machines of Intel RPL platforms

  [Fix]
  Here's the patch submitted by Intel.
  
https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy Output` shown on the Audio output option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023201/+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 2023201] [NEW] Add support of Smart Amplifier IC ALC1319D on Intel platforms

[Chris Chiu]

Public bug reported:

[Impact]
Speaker is not functional on some Dell machines of Intel RPL platforms

[Fix]
Here's the patch submitted by Intel.
https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/

[Test Case]
1. Power on the machine and open the audio settings
2. Verify it's not `Dummy Output` shown on the Audio output option

[Where problems could occur]
Only affect specific Intel RPL platforms. The risk of regression is low.

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

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

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

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

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

** Also affects: linux-oem-6.1 (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/2023201

Title:
  Add support of Smart Amplifier IC ALC1319D  on Intel platforms

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-6.1 package in Ubuntu:
  New
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-6.1 source package in Jammy:
  New

Bug description:
  [Impact]
  Speaker is not functional on some Dell machines of Intel RPL platforms

  [Fix]
  Here's the patch submitted by Intel.
  
https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/

  [Test Case]
  1. Power on the machine and open the audio settings
  2. Verify it's not `Dummy Output` shown on the Audio output option

  [Where problems could occur]
  Only affect specific Intel RPL platforms. The risk of regression is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023201/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

[Roemer Claasen]

Hi Mario,

I have to apologize, I was a little bit too fast sending that update.
Immediately afterwards I had the screen flickering again, with some
blackouts as well. I was able to make a video, see
https://www.youtube.com/watch?v=yjL9OuXhdeg. No errors in the log
though.

I will have to see if I can compile with the patch, not sure yet if I
can find the time.

Thank you for your support!

Roemer

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

Title:
  [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

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

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009952/+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 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools

[Sebastien Bacher]

Unsubscribing sponsors there doesn't seem to be something left to review
there

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

Title:
  linux-tools-common: bpftool wrapper causes build failure for xdp-tools

Status in launchpad-buildd:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xdp-tools package in Ubuntu:
  Fix Released

Bug description:
  The linux-tools-common package appears to provide a shell script with
  a wrapper that will execute the actual bpftool binary located in a
  location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool

  This causes problems for Lunar builds of xdp-tools on Launchpad [0]
  because there we appear to be running the build in a lunar container
  on host with a 5.4.0 kernel.

  Even if we were to install the linux-tools-6.1.0-14 package directly
  to get the real bpftool binary, the provided wrapper would be
  unhelpful.

  0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2

  For completeness/process I collected artifacts below from a Lunar LXD 
container running on a Focal host with a 5.4.0 kernel.
  ---
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux-tools-common 6.1.0-14.14
  PackageArchitecture: all
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic 
root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-139-generic N/A
   linux-backports-modules-5.4.0-139-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  lunar uec-images package-from-proposed
  Uname: Linux 5.4.0-139-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago)
  UserGroups: N/A
  WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 
'add' to '/sys/module/kernel/uevent': Permission denied
  _MarkForUpload: True
  acpidump:

  dmi.bios.date: 02/06/2015
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-7.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-7.1
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-7.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/2007308/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

[Mario Limonciello]

That's good news.  Just today there was a new patch posted that might
help the remaining PSR issue.  Can you please apply this on top of
6.4-rc5?

https://patchwork.freedesktop.org/patch/541535/

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

Title:
  [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

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

Bug description:
  After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there
  is occasional screen flicker/ tear. It happens around every minute; it
  seems connected to window/ pointer movement, but I have no clear way
  of reproducing. Disruption is minor,  but annoying.

  I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The
  system is fully functional. No crashes, nothing breaks.

  Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks
  suspend/ resume on my laptop, see
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718.

  In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic
  (previous 22.04.1 LTS kernel) works well, with working suspend/
  resume, and without screen flicker. But that's an 'old' kernel now,
  missing some nice improvements for the newer Ryzen APUs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-oem-22.04c 6.1.0.1007.7
  ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6
  Uname: Linux 6.1.0-1007-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 10 13:09:20 2023
  InstallationDate: Installed on 2023-02-06 (31 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: linux-meta-oem-6.1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2023197

Title:
  Fix speaker volume too low on HP G10 laptops

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

Bug description:
  [ Impact ]
  HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to 
enable all amplifiers to output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The quirk is for Cirrus codec on particular HP series laptops.
   * The risk of regression should only impact particular models

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023197/+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 2023197] [NEW] Fix speaker volume too low on HP G10 laptops

[Chris Chiu]

Public bug reported:

[ Impact ]
HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to enable 
all amplifiers to output audio with expected level.

[ Test Plan ]
 * Power up the HP G10 series laptops and adjust the output volume to MAX
 * Verify speaker output volume by ears.

[ Where problems could occur ]
 * The quirk is for Cirrus codec on particular HP series laptops.
 * The risk of regression should only impact particular models

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

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

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

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

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


** Tags: oem-priority originate-from-2019213 stella

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

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

** Tags added: oem-priority originate-from-2019213 stella

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

Title:
  Fix speaker volume too low on HP G10 laptops

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

Bug description:
  [ Impact ]
  HP G10 laptops need the quirk ALC245_FIXUP_CS35L41_SPI_4_HP_GPIO_LED to 
enable all amplifiers to output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The quirk is for Cirrus codec on particular HP series laptops.
   * The risk of regression should only impact particular models

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

Re: [Kernel-packages] [Bug 2022826] Re: Ethernet hangs

[koba]

Would you please provide the dmesg when ethernet/wifi is hang

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

Title:
  Ethernet hangs

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I'm now getting my wired (i.e. Ethernet) connection hanging on trying
  to connect. I've tried switching ports (on the router) and using a
  different cable, but still the same.

  ifconfig shows for Ethernet:
  enp2s0: flags=4163 mtu 1500
  ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet)
  RX packets 2779 bytes 250524 (250.5 KB)
  RX errors 0 dropped 1 overruns 0 frame 0
  TX packets 355 bytes 72171 (72.1 KB)
  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  sudo lshw -C enp2s0 shows nothing

  lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]:
  Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
  (rev 05)

  I found a web page: https://tutorialforlinux.com/2021/05...based-systems/
  I followed the instructions and installed realtek-r8125-dkms package OK. On 
rebooting, I followed the instructed procedure (shown when installing the 
package) of creating a password and then entering it when requested on the 
reboot. But still same problem. Any ideas what to do?
  PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is 
a little flaky due to walls) in order to post this question.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.13
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  3 07:29:15 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  InstallationDate: Installed on 2022-08-21 (285 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-43-generic N/A
   linux-backports-modules-5.19.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago)
  dmi.bios.date: 03/18/2021
  dmi.bios.release: 4.5
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: 0405
  dmi.board.asset.tag: Default string
  dmi.board.name: PN50-E1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku:
  dmi.product.family: Vivo PC
  dmi.product.name: MINIPC PN50-E1
  dmi.product.version: 0405
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+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 2023193] [NEW] Add firmware files for HP G10 series laptops

[Chris Chiu]

Public bug reported:

[ Impact ]
HP G10 laptops need more Cirrus firmware files to enable all amplifiers to 
output audio with expected level.

[ Test Plan ]
 * Power up the HP G10 series laptops and adjust the output volume to MAX
 * Verify speaker output volume by ears.

[ Where problems could occur ]
 * The firmware files are released by Cirrus codec for particular HP series 
laptops.
 * The risk of regression should only impact particular models

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

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

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

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

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


** Tags: oem-priority originate-from-2019213 stella

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

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

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

** Tags added: oem-priority originate-from-2019213 stella

** Description changed:

  [ Impact ]
  HP G10 laptops need more Cirrus firmware files to enable all amplifiers to 
output audio with expected level.
  
  [ Test Plan ]
-  * Power up the HP G10 series laptops and adjust the output volume to MAX
-  * Verify speaker output volume
+  * Power up the HP G10 series laptops and adjust the output volume to MAX
+  * Verify speaker output volume by ears.
  
  [ Where problems could occur ]
-  * The firmware files are released by Cirrus codec for particular HP series 
laptops.
-  * The risk of regression should only impact particular models
+  * The firmware files are released by Cirrus codec for particular HP series 
laptops.
+  * The risk of regression should only impact particular models

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

Title:
  Add firmware files for HP G10 series laptops

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Kinetic:
  New
Status in linux-firmware source package in Lunar:
  New

Bug description:
  [ Impact ]
  HP G10 laptops need more Cirrus firmware files to enable all amplifiers to 
output audio with expected level.

  [ Test Plan ]
   * Power up the HP G10 series laptops and adjust the output volume to MAX
   * Verify speaker output volume by ears.

  [ Where problems could occur ]
   * The firmware files are released by Cirrus codec for particular HP series 
laptops.
   * The risk of regression should only impact particular models

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2023193/+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 2022826] Re: Ethernet hangs

[John Rose]

Have you seen this web page?
https://github.com/unrloay2/ubuntu-network-driver-r8169

Any ideas how to download the specified files?

I have sent an email requesting help from unrloay2 (i.e. the author of
this web page).

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

Title:
  Ethernet hangs

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I'm now getting my wired (i.e. Ethernet) connection hanging on trying
  to connect. I've tried switching ports (on the router) and using a
  different cable, but still the same.

  ifconfig shows for Ethernet:
  enp2s0: flags=4163 mtu 1500
  ether 50:eb:f6:ef:a4:e6 txqueuelen 1000 (Ethernet)
  RX packets 2779 bytes 250524 (250.5 KB)
  RX errors 0 dropped 1 overruns 0 frame 0
  TX packets 355 bytes 72171 (72.1 KB)
  TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  sudo lshw -C enp2s0 shows nothing

  lspci -nn shows for Ethernet: 02:00.0 Ethernet controller [0200]:
  Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125]
  (rev 05)

  I found a web page: https://tutorialforlinux.com/2021/05...based-systems/
  I followed the instructions and installed realtek-r8125-dkms package OK. On 
rebooting, I followed the instructed procedure (shown when installing the 
package) of creating a password and then entering it when requested on the 
reboot. But still same problem. Any ideas what to do?
  PS I've switched Wi-Fi on (though I'd prefer to use Ethernet, as my Wi-Fi is 
a little flaky due to walls) in order to post this question.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.13
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  3 07:29:15 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  InstallationDate: Installed on 2022-08-21 (285 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: ASUSTeK COMPUTER INC. MINIPC PN50-E1
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=1d99d177-09b2-43e7-b6c1-451d081353f8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-43-generic N/A
   linux-backports-modules-5.19.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.13
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to jammy on 2022-10-06 (239 days ago)
  dmi.bios.date: 03/18/2021
  dmi.bios.release: 4.5
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: 0405
  dmi.board.asset.tag: Default string
  dmi.board.name: PN50-E1
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvr0405:bd03/18/2021:br4.5:svnASUSTeKCOMPUTERINC.:pnMINIPCPN50-E1:pvr0405:rvnASUSTeKCOMPUTERINC.:rnPN50-E1:rvrTobefilledbyO.E.M.:cvnDefaultstring:ct35:cvrDefaultstring:sku:
  dmi.product.family: Vivo PC
  dmi.product.name: MINIPC PN50-E1
  dmi.product.version: 0405
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2022826/+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 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1/6.2/6.3 kernel

[Roemer Claasen]

UPDATE 2 after testing 6.4rc5.

Still a PSR-related problem when running without
"amdgpu.dcdebugmask=0x10" (see kern.log below), apart from that very
happy with 6.4-rc5. The flicker/ tearing issue seems to be solved
(yeah!).

Without the kernel parameter I do get the following error though,
apparently related to PSR:

Jun  7 14:46:12 rct14s kernel: [ 1057.362873] WARNING: CPU: 3 PID: 226 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:226 
dmub_psr_enable+0x115/0x120 [amdgpu]
Jun  7 14:46:12 rct14s kernel: [ 1057.363546] Modules linked in: ccm 
michael_mic xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack 
nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat 
nf_tables libcrc32c nfnetlink rfcomm snd_seq_dummy snd_hrtimer nvme_fabrics 
cmac algif_hash algif_skcipher af_alg bnep qrtr_mhi amdgpu snd_soc_dmic 
snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_sof_amd_rembrandt snd_sof_amd_renoir 
snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp joydev snd_sof intel_rapl_msr 
intel_rapl_common snd_sof_utils edac_mce_amd snd_soc_core iommu_v2 drm_buddy 
snd_compress ac97_bus snd_ctl_led gpu_sched snd_pcm_dmaengine qrtr kvm_amd 
drm_suballoc_helper snd_hda_codec_realtek drm_ttm_helper snd_pci_ps ath11k_pci 
snd_hda_codec_generic binfmt_misc snd_hda_codec_hdmi ttm snd_rpl_pci_acp6x 
thinkpad_acpi snd_acp_pci kvm ath11k uvcvideo drm_display_helper nvram 
snd_hda_intel irqbypass videobuf2_vmalloc ledtrig_audio cec qmi_helpers 
snd_intel_dspcfg platform_profi
 le crct10dif_pclmul uvc snd_pci_acp6x polyval_clmulni
Jun  7 14:46:12 rct14s kernel: [ 1057.363616]  snd_intel_sdw_acpi rc_core 
videobuf2_memops polyval_generic snd_hda_codec snd_pci_acp5x snd_seq_midi 
ghash_clmulni_intel input_leds videobuf2_v4l2 drm_kms_helper sha512_ssse3 
snd_seq_midi_event mac80211 snd_rn_pci_acp3x aesni_intel i2c_algo_bit 
snd_hda_core videodev crypto_simd snd_rawmidi snd_acp_config syscopyarea 
snd_hwdep cryptd sysfillrect videobuf2_common snd_soc_acpi snd_pcm sysimgblt 
nls_iso8859_1 ccp snd_pci_acp3x rapl mc serio_raw snd_seq hid_multitouch 
cfg80211 btusb snd_seq_device think_lmi firmware_attributes_class wmi_bmof 
btrtl snd_timer btbcm libarc4 btintel snd ucsi_acpi btmtk mhi typec_ucsi 
k10temp typec soundcore mac_hid amd_pmc acpi_tad bluetooth ecdh_generic ecc 
sch_fq_codel overlay iptable_filter ip6table_filter ip6_tables br_netfilter 
bridge stp llc arp_tables msr parport_pc ppdev lp parport drm ramoops 
reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 nvme 
nvme_core video hid_generic crc32_
 pclmul psmouse thunderbolt xhci_pci i2c_piix4 xhci_pci_renesas
Jun  7 14:46:12 rct14s kernel: [ 1057.363702]  nvme_common i2c_hid_acpi i2c_hid 
wmi hid
Jun  7 14:46:12 rct14s kernel: [ 1057.363708] CPU: 3 PID: 226 Comm: 
kworker/3:1H Not tainted 6.4.0-060400rc5-generic #202306041930
Jun  7 14:46:12 rct14s kernel: [ 1057.363712] Hardware name: LENOVO 
21CQCTO1WW/21CQCTO1WW, BIOS R22ET60W (1.30 ) 02/09/2023
Jun  7 14:46:12 rct14s kernel: [ 1057.363714] Workqueue: events_highpri 
dm_irq_work_func [amdgpu]
Jun  7 14:46:12 rct14s kernel: [ 1057.364201] RIP: 
0010:dmub_psr_enable+0x115/0x120 [amdgpu]
Jun  7 14:46:12 rct14s kernel: [ 1057.364777] Code: 45 d0 65 48 2b 04 25 28 00 
00 00 75 21 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d 31 c0 31 d2 31 c9 31 f6 
31 ff c3 cc cc cc cc <0f> 0b eb d0 e8 e2 71 b1 ee 66 90 90 90 90 90 90 90 90 90 
90 90 90
Jun  7 14:46:12 rct14s kernel: [ 1057.364780] RSP: 0018:b3f6c08f3ca8 
EFLAGS: 00010246
Jun  7 14:46:12 rct14s kernel: [ 1057.364783] RAX:  RBX: 
03e9 RCX: 
Jun  7 14:46:12 rct14s kernel: [ 1057.364785] RDX:  RSI: 
 RDI: 
Jun  7 14:46:12 rct14s kernel: [ 1057.364786] RBP: b3f6c08f3d20 R08: 
 R09: 
Jun  7 14:46:12 rct14s kernel: [ 1057.364788] R10:  R11: 
 R12: 
Jun  7 14:46:12 rct14s kernel: [ 1057.364789] R13: 96828546aa30 R14: 
 R15: 9682aa84a9c0
Jun  7 14:46:12 rct14s kernel: [ 1057.364791] FS:  () 
GS:96899eec() knlGS:
Jun  7 14:46:12 rct14s kernel: [ 1057.364792] CS:  0010 DS:  ES:  CR0: 
80050033
Jun  7 14:46:12 rct14s kernel: [ 1057.364794] CR2: 7fb6c403760c CR3: 
000483c3a000 CR4: 00750ee0
Jun  7 14:46:12 rct14s kernel: [ 1057.364796] PKRU: 5554
Jun  7 14:46:12 rct14s kernel: [ 1057.364798] Call Trace:
Jun  7 14:46:12 rct14s kernel: [ 1057.364800]  
Jun  7 14:46:12 rct14s kernel: [ 1057.364803]  ? show_regs+0x6d/0x80
Jun  7 14:46:12 rct14s kernel: [ 1057.364808]  ? __warn+0x89/0x160
Jun  7 14:46:12 rct14s kernel: [ 1057.364813]  ? dmub_psr_enable+0x115/0x120 
[amdgpu]
Jun  7 14:46:12 rct14s kernel: [ 1057.365007]  ? report_bug+0x17e/0x1b0
Jun  7 14:46:12 rct14s kernel: [ 1057.365011]  ? handle_bug+0x46/0x90
Jun  7 14:46:12 rct14s kernel: [ 1057.365014]  ? 

[Kernel-packages] [Bug 2019979] Re: nvidia-dkms-* FTBS with linux 6.3

[Paolo Pisati]

** Patch added: "nvidia-graphics-drivers-515_515.105.01-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+attachment/5678457/+files/nvidia-graphics-drivers-515_515.105.01-0ubuntu3.debdiff

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

Title:
  nvidia-dkms-* FTBS with linux 6.3

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-510 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Mantic:
  Fix Released
Status in nvidia-graphics-drivers-515-server source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c: In function 
‘nvidia_mmap_helper’:
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:474:23: error: assignment 
of read-only member ‘vm_flags’
474 | vma->vm_flags |= VM_IO;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:536:23: error: assignment 
of read-only member ‘vm_flags’
536 | vma->vm_flags |= (VM_IO | VM_LOCKED | VM_RESERVED);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:537:23: error: assignment 
of read-only member ‘vm_flags’
537 | vma->vm_flags |= (VM_DONTEXPAND | VM_DONTDUMP);
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:543:23: error: assignment 
of read-only member ‘vm_flags’
543 | vma->vm_flags &= ~VM_WRITE;
|   ^~
  /var/lib/dkms/nvidia/390.157/build/nvidia/nv-mmap.c:544:23: error: assignment 
of read-only member ‘vm_flags’
544 | vma->vm_flags &= ~VM_MAYWRITE;
|   ^~

  [Fix]

  Apply the attached patch.

  [How to test]

  Build the dkms package and install it.

  [Regression potential]

  This patch doesn't come from NVIDIA itself, so there's a regression
  potential, though i can't state how severe that could be.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019979/+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 2000228] Re: Add initial support for Mediatek mt8195 demo platform

[Sebastien Bacher]

Ethan, I'm unsubscribing the sponsors since you said to wait for updated
patches included the extra fix for g350, please subscribe the team back
once the changes are ready for review

** Changed in: alsa-ucm-conf (Ubuntu)
 Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)

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

Title:
  Add initial support for Mediatek mt8195 demo platform

Status in alsa-ucm-conf package in Ubuntu:
  New

Bug description:
  [Impact]
  Add initial support for Mediatek mt8195 demo platform
  
https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9
  
https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9

  [Where problems could occur]
  Audio function doesn't work on Mediatek mt8195 demo platform.
  Play audio by aplay and gnome sound test:
  1. HDMI audio: Pass
  2. Headset: Pass

  [Test Case]
  Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform.

  [Regression Potential]
  Add initial support for Mediatek mt8195 demo platform. There should be no 
risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+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 2023185] [NEW] iostat -x doesn't give any Device utilization values for Kioxia CM7 drive while running IO

[Kumar Harshith Gowda K S]

Private bug reported:

Steps to Repro : 
1. Configure a Poweredge system with Kioxia CM7 U.2 drive connected
2. Boot to Ubuntu 22.04.2 and verify the drives are discovered successfully.
3. Run IO to the CM7 U.2 drives.
4. Verify the device utilization using "iostat -x 1 -m /dev/nvme0n1" command

Expected Result:
IOSTAT should give non-zero values for Device utilization on CM7 U.2 drives.

Actual Result:
IOSTAT does not give any values for Device utilization on CM7 U.2 drives

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

** Attachment added: "sosreport"
   
https://bugs.launchpad.net/bugs/2023185/+attachment/5678452/+files/sosreport-linux-ubuntuIOstat-2023-06-07-xflntiy.tar.xz

** Information type changed from Public to Private

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

Title:
  iostat -x doesn't give any Device utilization values for Kioxia CM7
  drive while running IO

Status in linux package in Ubuntu:
  New

Bug description:
  Steps to Repro : 
  1. Configure a Poweredge system with Kioxia CM7 U.2 drive connected
  2. Boot to Ubuntu 22.04.2 and verify the drives are discovered successfully.
  3. Run IO to the CM7 U.2 drives.
  4. Verify the device utilization using "iostat -x 1 -m /dev/nvme0n1" command

  Expected Result:
  IOSTAT should give non-zero values for Device utilization on CM7 U.2 drives.

  Actual Result:
  IOSTAT does not give any values for Device utilization on CM7 U.2 drives

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

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 Kinetic)
   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/2023181

Title:
  backport-iwlwifi-dkms fails building for s390x

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  Autopkgtest is been failing for a while now.

  Building backport-include/backport/autoconf.h ... done.
  warning: the compiler differs from the one used to build the kernel
The kernel was built by: s390x-linux-gnu-gcc-12 (Ubuntu 12.2.0-3ubuntu1) 
12.2.0
You are using:   gcc-12 (Ubuntu 12.2.0-3ubuntu1) 12.2.0
CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/main.o
CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/lib-crypto-arc4.o
LD [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/iwlwifi-compat.o
CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.o
  In file included from 
/var/lib/dkms/backport-iwlwifi/9904/build/backport-include/net/cfg80211.h:15,
   from 
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:26:
  /var/lib/dkms/backport-iwlwifi/9904/build/include/net/cfg80211.h: In function 
‘cfg80211_unregister_netdevice’:
  /var/lib/dkms/backport-iwlwifi/9904/build/include/net/cfg80211.h:8128:37: 
error: ‘struct net_device’ has no member named ‘ieee80211_ptr’
   8128 | cfg80211_unregister_wdev(dev->ieee80211_ptr);
| ^~
  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c: In function 
‘cfg80211_register_netdevice’:
  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:1354:40: error: 
‘struct net_device’ has no member named ‘ieee80211_ptr’
   1354 | struct wireless_dev *wdev = dev->ieee80211_ptr;
|^~
  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c: In function 
‘cfg80211_netdev_notifier_call’:
  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:1388:40: error: 
‘struct net_device’ has no member named ‘ieee80211_ptr’
   1388 | struct wireless_dev *wdev = dev->ieee80211_ptr;
|^~
  make[6]: *** [scripts/Makefile.build:257: 
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.o] Error 1
  make[5]: *** [scripts/Makefile.build:474: 
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless] Error 2
  make[4]: *** [Makefile:1857: /var/lib/dkms/backport-iwlwifi/9904/build] Error 
2
  make[3]: *** [Makefile.build:13: modules] Error 2
  make[2]: *** [Makefile.real:100: modules] Error 2
  make[1]: *** [Makefile:43: modules] Error 2
  make: *** [Makefile:30: default] Error 2
  
  ./backport-iwlwifi/9904/build/make.log
  I: Summary:
  I: FAIL 5.19.0-44-generic
  autopkgtest [22:07:53]: test dkms-autopkgtest: ---]
  autopkgtest [22:07:53]: test dkms-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -
  dkms-autopkgtest FAIL non-zero exit status 1

  I think it's because CONFIG_CFG80211 is not enabled for s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023181/+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 2023181] [NEW] backport-iwlwifi-dkms fails building for s390x

[Roxana Nicolescu]

Public bug reported:

Autopkgtest is been failing for a while now.

Building backport-include/backport/autoconf.h ... done.
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: s390x-linux-gnu-gcc-12 (Ubuntu 12.2.0-3ubuntu1) 
12.2.0
  You are using:   gcc-12 (Ubuntu 12.2.0-3ubuntu1) 12.2.0
  CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/main.o
  CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/lib-crypto-arc4.o
  LD [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/iwlwifi-compat.o
  CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.o
In file included from 
/var/lib/dkms/backport-iwlwifi/9904/build/backport-include/net/cfg80211.h:15,
 from 
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:26:
/var/lib/dkms/backport-iwlwifi/9904/build/include/net/cfg80211.h: In function 
‘cfg80211_unregister_netdevice’:
/var/lib/dkms/backport-iwlwifi/9904/build/include/net/cfg80211.h:8128:37: 
error: ‘struct net_device’ has no member named ‘ieee80211_ptr’
 8128 | cfg80211_unregister_wdev(dev->ieee80211_ptr);
  | ^~
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c: In function 
‘cfg80211_register_netdevice’:
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:1354:40: error: 
‘struct net_device’ has no member named ‘ieee80211_ptr’
 1354 | struct wireless_dev *wdev = dev->ieee80211_ptr;
  |^~
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c: In function 
‘cfg80211_netdev_notifier_call’:
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:1388:40: error: 
‘struct net_device’ has no member named ‘ieee80211_ptr’
 1388 | struct wireless_dev *wdev = dev->ieee80211_ptr;
  |^~
make[6]: *** [scripts/Makefile.build:257: 
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.o] Error 1
make[5]: *** [scripts/Makefile.build:474: 
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless] Error 2
make[4]: *** [Makefile:1857: /var/lib/dkms/backport-iwlwifi/9904/build] Error 2
make[3]: *** [Makefile.build:13: modules] Error 2
make[2]: *** [Makefile.real:100: modules] Error 2
make[1]: *** [Makefile:43: modules] Error 2
make: *** [Makefile:30: default] Error 2

./backport-iwlwifi/9904/build/make.log
I: Summary:
I: FAIL 5.19.0-44-generic
autopkgtest [22:07:53]: test dkms-autopkgtest: ---]
autopkgtest [22:07:53]: test dkms-autopkgtest:  - - - - - - - - - - results - - 
- - - - - - - -
dkms-autopkgtest FAIL non-zero exit status 1

I think it's because CONFIG_CFG80211 is not enabled for s390x

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

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


** Tags: sru-20230515

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

** Tags added: sru-20230515

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

Title:
  backport-iwlwifi-dkms fails building for s390x

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  Autopkgtest is been failing for a while now.

  Building backport-include/backport/autoconf.h ... done.
  warning: the compiler differs from the one used to build the kernel
The kernel was built by: s390x-linux-gnu-gcc-12 (Ubuntu 12.2.0-3ubuntu1) 
12.2.0
You are using:   gcc-12 (Ubuntu 12.2.0-3ubuntu1) 12.2.0
CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/main.o
CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/lib-crypto-arc4.o
LD [M]  /var/lib/dkms/backport-iwlwifi/9904/build/compat/iwlwifi-compat.o
CC [M]  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.o
  In file included from 
/var/lib/dkms/backport-iwlwifi/9904/build/backport-include/net/cfg80211.h:15,
   from 
/var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:26:
  /var/lib/dkms/backport-iwlwifi/9904/build/include/net/cfg80211.h: In function 
‘cfg80211_unregister_netdevice’:
  /var/lib/dkms/backport-iwlwifi/9904/build/include/net/cfg80211.h:8128:37: 
error: ‘struct net_device’ has no member named ‘ieee80211_ptr’
   8128 | cfg80211_unregister_wdev(dev->ieee80211_ptr);
| ^~
  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c: In function 
‘cfg80211_register_netdevice’:
  /var/lib/dkms/backport-iwlwifi/9904/build/net/wireless/core.c:1354:40: error: 
‘struct net_device’ has no member named ‘ieee80211_ptr’
   1354 | struct wireless_dev *wdev = dev->ieee80211_ptr;
|^~
  

[Kernel-packages] [Bug 2023176] Re: system hang after running stress-ng softlockup stressor while iwlwifi is connected to the station

[Jian Hui Lee]

** Tags added: lookout-canyon oem-priority originate-from-2008994

** No longer affects: hwe-next

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

Title:
  system hang after running stress-ng softlockup stressor while iwlwifi
  is connected to the station

Status in linux-intel-iotg package in Ubuntu:
  Invalid
Status in linux-intel-iotg source package in Focal:
  New
Status in linux-intel-iotg source package in Jammy:
  New

Bug description:
  [ Impact ]

   * system got hang after running stress-ng softlockup test while
  iwlwifi is connected to the station

  [ Test Plan ]

   * connect wifi (iwlwifi) to any station. (must do this)

   * execute the following command:
  $ sudo stress-ng --softlockup NUM_CPU_CORES --timeout 30

   * make sure the system still responses after testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2023176/+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 2023176] [NEW] system hang after running stress-ng softlockup stressor while iwlwifi is connected to the station

[Jian Hui Lee]

Public bug reported:

[ Impact ]

 * system got hang after running stress-ng softlockup test while iwlwifi
is connected to the station

[ Test Plan ]

 * connect wifi (iwlwifi) to any station. (must do this)

 * execute the following command:
$ sudo stress-ng --softlockup NUM_CPU_CORES --timeout 30

 * make sure the system still responses after testing

** Affects: linux-intel-iotg (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-intel-iotg (Ubuntu Focal)
 Importance: Undecided
 Status: New

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


** Tags: lookout-canyon oem-priority originate-from-2008994

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

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

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

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

Title:
  system hang after running stress-ng softlockup stressor while iwlwifi
  is connected to the station

Status in linux-intel-iotg package in Ubuntu:
  Invalid
Status in linux-intel-iotg source package in Focal:
  New
Status in linux-intel-iotg source package in Jammy:
  New

Bug description:
  [ Impact ]

   * system got hang after running stress-ng softlockup test while
  iwlwifi is connected to the station

  [ Test Plan ]

   * connect wifi (iwlwifi) to any station. (must do this)

   * execute the following command:
  $ sudo stress-ng --softlockup NUM_CPU_CORES --timeout 30

   * make sure the system still responses after testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2023176/+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 2012661] Re: kernel BUG at lib/assoc_array.c:652!

[mjw99]

Still seeing this with 5.15.0-72-generic

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

Title:
  kernel BUG at lib/assoc_array.c:652!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am seeing this in Ubuntu 22.04 with kernel 5.15.0-67.74:

  Mar 23 12:38:32 box kernel: [13399.080589] [ cut here 
]
  Mar 23 12:38:32 box kernel: [13399.080596] kernel BUG at 
lib/assoc_array.c:652!
  Mar 23 12:38:32 box kernel: [13399.082833] invalid opcode:  [#1] SMP PTI
  Mar 23 12:38:32 box kernel: [13399.084912] CPU: 27 PID: 3746279 Comm: 
kworker/27:3 Tainted: G   OE 5.15.0-67-generic #74-Ubuntu
  Mar 23 12:38:32 box kernel: [13399.087091] Hardware name: HP ProLiant DL380 
Gen9/ProLiant DL380 Gen9, BIOS P89 07/18/2022
  Mar 23 12:38:32 box kernel: [13399.089195] Workqueue: cifsiod 
cifs_resolve_server [cifs]
  Mar 23 12:38:32 box kernel: [13399.091379] RIP: 
0010:assoc_array_insert_into_terminal_node.isra.0+0x806/0xc20
  Mar 23 12:38:32 box kernel: [13399.093480] Code: 4c 63 e2 44 8d 6a 01 49 83 
fc 10 0f 87 d7 01 00 00 4c 8b 4d b8 44 89 ea 4b 8d 4c e1 10 e9 a7 fc ff ff 0f 
0b 0f 0b 0f 0b 0f 0b <0f> 0b 0f 0b 48 c7 c7 e0 cf 4b 9c e8 ba 37 03 00 e9 53 f8 
ff ff 0f
  Mar 23 12:38:32 box kernel: [13399.097735] RSP: 0018:c08e7a66fa20 EFLAGS: 
00010286
  Mar 23 12:38:32 box kernel: [13399.099790] RAX: 0002 RBX: 
 RCX: 0001
  Mar 23 12:38:32 box kernel: [13399.101871] RDX: 9d2275968000 RSI: 
000f RDI: 0001
  Mar 23 12:38:32 box kernel: [13399.103963] RBP: c08e7a66faa0 R08: 
9d31e7cbda00 R09: 9d2275969b00
  Mar 23 12:38:32 box kernel: [13399.106111] R10: 9cb6cfc93800 R11: 
000c R12: 0001
  Mar 23 12:38:32 box kernel: [13399.108209] R13: 000f R14: 
 R15: 9d2275969b00
  Mar 23 12:38:32 box kernel: [13399.110292] FS:  () 
GS:9d14bfc4() knlGS:
  Mar 23 12:38:32 box kernel: [13399.112355] CS:  0010 DS:  ES:  CR0: 
80050033
  Mar 23 12:38:32 box kernel: [13399.114411] CR2: 7f3a9b9e4a58 CR3: 
0012c8810005 CR4: 001706e0
  Mar 23 12:38:32 box kernel: [13399.116461] Call Trace:
  Mar 23 12:38:32 box kernel: [13399.118452]  
  Mar 23 12:38:32 box kernel: [13399.120455]  assoc_array_insert+0x153/0x170
  Mar 23 12:38:32 box kernel: [13399.122422]  ? _raw_spin_lock+0x22/0x30
  Mar 23 12:38:32 box kernel: [13399.124357]  ? key_alloc+0x2e6/0x550
  Mar 23 12:38:32 box kernel: [13399.126273]  __key_link_begin+0x4c/0xb0
  Mar 23 12:38:32 box kernel: [13399.128153]  construct_alloc_key+0xdb/0x270
  Mar 23 12:38:32 box kernel: [13399.130032]  request_key_and_link+0x22c/0x320
  Mar 23 12:38:32 box kernel: [13399.131867]  ? dns_resolver_read+0x30/0x30
  Mar 23 12:38:32 box kernel: [13399.133689]  ? key_default_cmp+0x30/0x30
  Mar 23 12:38:32 box kernel: [13399.135469]  request_key_tag+0x49/0x90
  Mar 23 12:38:32 box kernel: [13399.137241]  dns_query+0x13d/0x250
  Mar 23 12:38:32 box kernel: [13399.138989]  
dns_resolve_server_name_to_ip+0xb7/0x310 [cifs]
  Mar 23 12:38:32 box kernel: [13399.141130]  ? scnprintf+0x4d/0x90
  Mar 23 12:38:32 box kernel: [13399.142866]  
reconn_set_ipaddr_from_hostname+0x86/0x2b0 [cifs]
  Mar 23 12:38:32 box kernel: [13399.144654]  ? 
finish_task_switch.isra.0+0x7e/0x280
  Mar 23 12:38:32 box kernel: [13399.146412]  cifs_resolve_server+0x2c/0x90 
[cifs]
  Mar 23 12:38:32 box kernel: [13399.148176]  process_one_work+0x22b/0x3d0
  Mar 23 12:38:32 box kernel: [13399.149845]  worker_thread+0x53/0x420
  Mar 23 12:38:32 box kernel: [13399.151459]  ? process_one_work+0x3d0/0x3d0
  Mar 23 12:38:32 box kernel: [13399.153061]  kthread+0x12a/0x150
  Mar 23 12:38:32 box kernel: [13399.154631]  ? set_kthread_struct+0x50/0x50
  Mar 23 12:38:32 box kernel: [13399.156181]  ret_from_fork+0x22/0x30
  Mar 23 12:38:32 box kernel: [13399.157716]  
  Mar 23 12:38:32 box kernel: [13399.159565] Modules linked in: xt_REDIRECT 
xt_state ip_vs_rr xt_ipvs ip_vs vxlan ip6_udp_tunnel udp_tunnel xt_policy 
xt_mark xt_u32 veth xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE 
nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
xfrm_user xfrm_algo nft_counter xt_addrtype nft_compat nf_tables nfnetlink 
br_netfilter bridge stp llc cmac nls_utf8 cifs cifs_arc4 cifs_md4 binfmt_misc 
nfsv3 rpcsec_gss_krb5 nfsv4 nfs fscache netfs cpuid eset_rtp(OE-) overlay hpwdt 
nls_iso8859_1 intel_rapl_msr intel_rapl_common sb_edac ipmi_ssif 
x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm crct10dif_pclmul 
ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate mgag200 
drm_kms_helper cec rc_core i2c_algo_bit fb_sys_fops syscopyarea sysfillrect 
ioatdma input_leds joydev hpilo sysimgblt dca acpi_ipmi ipmi_si ipmi_devintf 

[Kernel-packages] [Bug 2022981] Re: Frequent hard reboots on RaptorLake

[Daniel van Vugt]

Please also remove the kernel parameter 'drm.debug=0xe' because it seems
to be causing more noise than help right now.

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

Title:
  Frequent hard reboots on RaptorLake

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can repro in multiple ways:

  1. Unplug my HDMI monitor. This is pretty much a guaranteed reboot.
  2. Using hardware accelerated Chromium, switching between google profiles 
seems to trigger a crash and full reboot pretty often.

  These could be two separate bugs. I'm not sure I'd be unlucky enough
  to have two full reboot bugs at the same time though. Happy to help
  with more debugging

  Release: Jammy
  Chromium version: 115.0.5762.4-hwacc
  snap refresh --channel=latest/edge/hwacc chromium

  What you expected to happen
  1. HDMI monitor disconnects, and no reboots happen.
  2. I can switch Chromium profiles without a reboot

  What happened instead
  Both actions cause a reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  6 16:09:12 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-41-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   fwts-efi-runtime-dkms/23.01.00, 5.19.0-43-generic, x86_64: installed 
(WARNING! Diff between built and installed module!)
   tp_smapi/0.43, 5.19.0-41-generic, x86_64: installed
   tp_smapi/0.43, 5.19.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5630]
   NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:25a2] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: NVIDIA Corporation GA107M [GeForce RTX 3050 Mobile] [10de:]
  InstallationDate: Installed on 2023-04-20 (46 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: System76 Gazelle
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_90m3zy@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_90m3zy ro drm.debug=0xe quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2023
  dmi.bios.release: 4.19
  dmi.bios.vendor: coreboot
  dmi.bios.version: 2023-03-22_799ed79
  dmi.board.name: Gazelle
  dmi.board.vendor: System76
  dmi.board.version: gaze18
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr2023-03-22_799ed79:bd03/22/2023:br4.19:efr0.0:svnSystem76:pnGazelle:pvrgaze18:rvnSystem76:rnGazelle:rvrgaze18:cvnSystem76:ct9:cvr:sku:
  dmi.product.name: Gazelle
  dmi.product.version: gaze18
  dmi.sys.vendor: System76
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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 N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022981/+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 2022824] Re: [amdgpu] random blue/pink frames in the desktop

[Daniel van Vugt]

** Summary changed:

- random blue/pink frames in the desktop 
+ [amdgpu] random blue/pink frames in the desktop

** Package changed: xorg (Ubuntu) => linux-hwe-5.19 (Ubuntu)

** Tags added: amdgpu

** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [amdgpu] random blue/pink frames in the desktop

Status in linux-hwe-5.19 package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop.
  every 1-2 minutes, there will be a random blue/pink frame(i'm not sure
  of the color because it only appears for a short time). I don't get
  this problem in fullscreen games running with dxvk and the random
  frames didn't show when I recorded my desktop with obs studio. I also
  got this problem in gnome(on wayland). When I have a dxvk game running
  or when I have 2 monitors connected, I don't get this issue. One thing
  to note is that when I have 2 monitors connected, my gpu will boost
  its vram clock to 2000mhz.

  what I tried:
  -rebooting
  -updating
  -disabling blur in kde settings
  -lowering my refresh rate from 144hz to 120hz

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jun  3 00:45:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 
6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] 
[1043:05d7]
  InstallationDate: Installed on 2023-06-01 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=ca576fb0-08b4-45d8-aadd-83e9df696ff2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: B450M Pro4-F
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2022824/+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 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part

[Frank Heimes]

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

** Also affects: linux (Ubuntu Mantic)
   Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Fix Released

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

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

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

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

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

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

Title:
  [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x -
  kernel part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux source package in Kinetic:
  Won't Fix
Status in linux source package in Lunar:
  Fix Released
Status in linux source package in Mantic:
  Fix Released

Bug description:
  The PCI Passthrough implementation is based on intercepting PCI I/O 
instructions which leads to a reduced I/O performance compared to execution of 
PCI instructions in LPAR. 
  For improved performance the interpretive execution of the PCI store and PCI 
load instructions get enabled. 
  Further improvement is achieved by enabling the Adapter-Event-Notification

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853306/+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 2019024] Re: Migrate oem-5.17 to hwe-6.2

[Timo Aaltonen]

** Summary changed:

- Migrate oem-5.17 to hwe-5.19
+ Migrate oem-5.17 to hwe-6.2

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

Title:
  Migrate oem-5.17 to hwe-6.2

Status in linux-meta-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux-restricted-modules-hwe-5.19 package in Ubuntu:
  Invalid
Status in linux-meta-hwe-5.19 source package in Jammy:
  New
Status in linux-restricted-modules-hwe-5.19 source package in Jammy:
  New

Bug description:
  [Impact]
  Migrate oem-5.17 to hwe-5.19 now that there should be no functional 
regressions left anymore.

  [Test case]
  Update a machine with oem-5.17 metapackages to the proposed ones, and verify 
that all packages (including nvidia etc) migrate properly.

  [Where things could go wrong]
  In theory we might miss a package to transition, but at this point this is 
unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.19/+bug/2019024/+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 2015956] Re: selftest: fib_tests: Always cleanup before exit

[Po-Hsu Lin]

Verified with:
linux-aws/5.19.0-1027.28
linux-aws/5.15.0-1038.43 
linux-azure/5.15.0-1040.47
linux-azure/5.19.0-1028.31
linux-oem-5.17/5.17.0-1033.34 


For 
linux-aws/5.4.0-1104.112
linux-azure/5.4.0-1110.116
The fib_test.sh script is still missing, I cannot verify it at this point.

** Tags removed: verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done-jammy verification-done-kinetic

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

Title:
   selftest: fib_tests: Always cleanup before exit

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux-oem-6.0 source package in Focal:
  Invalid
Status in linux-oem-6.1 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in linux-oem-6.0 source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released
Status in linux-oem-5.17 source package in Kinetic:
  Invalid
Status in linux-oem-6.0 source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Fix Released
Status in linux-oem-5.17 source package in Lunar:
  Invalid
Status in linux-oem-6.0 source package in Lunar:
  Invalid
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Impact]
  Copied from the commit message:
  Usage of `set -e` before executing a command causes immediate exit
  on failure, without cleanup up the resources allocated at setup.
  This can affect the next tests that use the same resources,
  leading to a chain of failures.

  A simple fix is to always call cleanup function when the script exists.
  This approach is already used by other existing tests.

  [Fix]
  * b60417a9f2 selftest: fib_tests: Always cleanup before exit

  This patch can be cherry-picked into affected kernels.

  [Test]
  Run the patched fib_tests.sh on KVM kernels, which is expected to fail 
  due to bug 2007458.
  Check with `ip netns`, the ns1 added during setup() should be removed.

  [Where problems could occur]
  Test robustness improvement, this should not break things.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2015956/+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 1786013] Autopkgtest regression report (linux-meta-oracle/5.15.0.1037.32)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-oracle (5.15.0.1037.32) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.9 (amd64, arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-oracle

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packaging resyncs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2022826] Re: Ethernet hangs

[John Rose]

@koba

ifconfig shows that ethernet has nothing. wg0 is for WireGuard. wlps0 is
for my phone's hotspot as only way I can connect to internet either
wired or wirelessly. Wired connection normally showing by clicking on
top right hand corner of screen has again disappeared! I disconnected
phone's hotspot in between 1st & 2nd ifcnofig:

john@Desktop:~$ ifconfig
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 2459061  bytes 185774876 (185.7 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2459061  bytes 185774876 (185.7 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wg0: flags=209  mtu 1420
inet 10.0.0.1  netmask 255.255.255.0  destination 10.0.0.1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000 
 (UNSPEC)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 15  dropped 0 overruns 0  carrier 0  collisions 0

wlp3s0: flags=4163  mtu 1500
inet 192.168.203.1  netmask 255.255.255.0  broadcast 192.168.203.255
inet6 fe80::c01f:1a40:87b9:30b5  prefixlen 64  scopeid 0x20
ether bc:f1:71:6d:25:4f  txqueuelen 1000  (Ethernet)
RX packets 943830  bytes 1085877280 (1.0 GB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 486094  bytes 69901150 (69.9 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

john@Desktop:~$ ifconfig
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 2462191  bytes 186047466 (186.0 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2462191  bytes 186047466 (186.0 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wg0: flags=209  mtu 1420
inet 10.0.0.1  netmask 255.255.255.0  destination 10.0.0.1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000 
 (UNSPEC)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 15  dropped 0 overruns 0  carrier 0  collisions 0

john@Desktop:~$ sudo lshw -C network
[sudo] password for john: 
  *-network UNCLAIMED   
   description: Ethernet controller
   product: RTL8125 2.5GbE Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   version: 05
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list
   configuration: latency=0
   resources: ioport:f000(size=256) memory:fe90-fe90 
memory:fe91-fe913fff
  *-network DISABLED
   description: Wireless interface
   product: Wi-Fi 6 AX200
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:03:00.0
   logical name: wlp3s0
   version: 1a
   serial: bc:f1:71:6d:25:4f
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=5.19.0-43-generic firmware=72.daa05125.0 cc-a0-72.ucode latency=0 
link=no multicast=yes wireless=IEEE 802.11
   resources: irq:67 memory:fe80-fe803fff
john@Desktop:~$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
john@Desktop:~$ rfkill unblock all
john@Desktop:~$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
john@Desktop:~$ ifconfig
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 2462473  bytes 186069134 (186.0 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2462473  bytes 186069134 (186.0 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wg0: flags=209  mtu 1420
inet 10.0.0.1  netmask 255.255.255.0  destination 10.0.0.1
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000 
 (UNSPEC)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 15  dropped 0 overruns 0  carrier 0  collisions 0

john@Desktop:~$ sudo lshw -C network
  *-network UNCLAIMED   
   description: Ethernet controller
   product: RTL8125 2.5GbE Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:02:00.0
   version: 05
   width: 64 bits

[Kernel-packages] [Bug 2023143] Re: Memory leak on large server

[Ariel E]

** 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/2023143

Title:
  Memory leak on large server

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  We are trying to diagnose a kernel memory look on a production Ubuntu 22.04.2 
LTS.
  We have tried several official Ubuntu kernels, 5.15aws, 5.19aws and now even 
6.2.0-1004-aws (all Ubuntu signed):
  ```
  # cat /proc/version_signature
  Ubuntu 6.2.0-1004.4-aws 6.2.6
  ```

  This is a production server so we'll appreciate any and all help diagnosing 
and solving this issue!
   
  The server is an u-112 instance with 12TB RAM, and is losing 1TB+ of memory a 
day to a kernel leak.
  For example, currently with an uptime of 3.5 days, we have 1.8Ti available, 
however RSS+slabs is only 4.1TB.

  all active process together take about 4TB of RAM (`ps -eo rss | awk
  'BEGIN {x=0} {x = x + $1} END {print x}'` gives 4088636708).

  From slabtop we see about 100GB are consumed by slab (`slabtop -o -s t | 
head`: )
  ```
   Active / Total Objects (% used): 303580174 / 332642344 (91.3%)
   Active / Total Slabs (% used)  : 6697552 / 6697552 (100.0%)
   Active / Total Caches (% used) : 158 / 215 (73.5%)
   Active / Total Size (% used)   : 112801663.93K / 121442845.45K (92.9%)
   Minimum / Average / Maximum Object : 0.01K / 0.36K / 16.00K

OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME
  67537280 59696907  88%0.03K 527635  128   2110540K kmalloc-32
  65247564 65241398  99%0.31K 1279364   51  20469824K arc_buf_hdr_t_full
  58270446 58040685  99%0.10K 747057   78   5976456K abd_t
  16697268 13731405  82%0.38K 397554   42   6360864K dmu_buf_impl_t
  15982912 10366686  64%0.50K 249733   64   7991456K kmalloc-512
  14975616 11605380  77%0.06K 233994   64935976K kmalloc-64
  ```

  In /proc/meminfo:
  ```
  MemTotal:   12656421408 kB
  MemFree:1975976204 kB
  MemAvailable:   1968415088 kB
  Buffers: 1087956 kB
  Cached: 101168004 kB
  SwapCached: 17912340 kB
  Active: 101022084 kB
  Inactive:   4129984264 kB
  Active(anon):   94623216 kB
  Inactive(anon): 4104673512 kB
  Active(file):6398868 kB
  Inactive(file): 25310752 kB
  Unevictable:  338908 kB
  Mlocked:  332132 kB
  SwapTotal:  4294967292 kB
  SwapFree:   3500705532 kB
  Zswap: 0 kB
  Zswapped:  0 kB
  Dirty:  2908 kB
  Writeback: 0 kB
  AnonPages:  4123489132 kB
  Mapped:  3761620 kB
  Shmem:  70756156 kB
  KReclaimable:   10319220 kB
  Slab:   122355620 kB
  SReclaimable:   10319220 kB
  SUnreclaim: 112036400 kB
  KernelStack: 1793296 kB
  PageTables: 21748556 kB
  SecPageTables: 0 kB
  NFS_Unstable:  0 kB
  Bounce:0 kB
  WritebackTmp:  0 kB
  CommitLimit:10623177996 kB
  Committed_AS:   6775476544 kB
  VmallocTotal:   34359738367 kB
  VmallocUsed:296984480 kB
  VmallocChunk:  0 kB
  Percpu:  1326080 kB
  HardwareCorrupted: 0 kB
  AnonHugePages:  1630980096 kB
  ShmemHugePages:0 kB
  ShmemPmdMapped:0 kB
  FileHugePages: 0 kB
  FilePmdMapped: 0 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  Hugetlb:   0 kB
  DirectMap4k: 2056036 kB
  DirectMap2M:40935424 kB
  DirectMap1G:12814647296 kB
  ```

  Its not a tmpfs/shm fs issue either:
  ```
  df -h | grep -E 'tmpfs|shm'
  tmpfs   256G   70G  187G  27% 
/dev/shm
  tmpfs   256G  3.4M  256G   1% /run
  tmpfs   5.0M 0  5.0M   0% 
/run/lock
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10102
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/1002
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10030
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10194
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10200
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10136
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10198
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10143
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10188
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10124
  tmpfs   

[Kernel-packages] [Bug 2021449] Re: ALSA: hda/realtek: Enable headset onLenovo M70/M90

[Bin Li]

** Description changed:

  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.
  
  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f
  
  [Test]
- After applying the patch, the os works fine with the headset mic.
+ After applying the patch, the os works fine with the headset mic on 6.1.0-oem.
  
  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

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

Title:
  ALSA: hda/realtek: Enable headset onLenovo M70/M90

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

Bug description:
  [Impact]
  The headset couldn't work on M70/M90 Gen4 on 6.1.0-oem kernel and 5.19 
generic kernel.
  Lenovo M70/M90 Gen4 are equipped with ALC897, and they need
  ALC897_FIXUP_HEADSET_MIC_PIN quirk to make its headset mic work.
  The previous quirk for M70/M90 is for Gen3.

  [Fix]
  cherry picked from commit 4ca110cab46561cd74a2acd9b447435acb4bec5f

  [Test]
  After applying the patch, the os works fine with the headset mic on 6.1.0-oem.

  [Where problems could occur]
  It's just a quirk for sound/pci/hda/patch_realtek.c, the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2021449/+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 2023143] 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 2023143

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

Title:
  Memory leak on large server

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  We are trying to diagnose a kernel memory look on a production Ubuntu 22.04.2 
LTS.
  We have tried several official Ubuntu kernels, 5.15aws, 5.19aws and now even 
6.2.0-1004-aws (all Ubuntu signed):
  ```
  # cat /proc/version_signature
  Ubuntu 6.2.0-1004.4-aws 6.2.6
  ```

  This is a production server so we'll appreciate any and all help diagnosing 
and solving this issue!
   
  The server is an u-112 instance with 12TB RAM, and is losing 1TB+ of memory a 
day to a kernel leak.
  For example, currently with an uptime of 3.5 days, we have 1.8Ti available, 
however RSS+slabs is only 4.1TB.

  all active process together take about 4TB of RAM (`ps -eo rss | awk
  'BEGIN {x=0} {x = x + $1} END {print x}'` gives 4088636708).

  From slabtop we see about 100GB are consumed by slab (`slabtop -o -s t | 
head`: )
  ```
   Active / Total Objects (% used): 303580174 / 332642344 (91.3%)
   Active / Total Slabs (% used)  : 6697552 / 6697552 (100.0%)
   Active / Total Caches (% used) : 158 / 215 (73.5%)
   Active / Total Size (% used)   : 112801663.93K / 121442845.45K (92.9%)
   Minimum / Average / Maximum Object : 0.01K / 0.36K / 16.00K

OBJS ACTIVE  USE OBJ SIZE  SLABS OBJ/SLAB CACHE SIZE NAME
  67537280 59696907  88%0.03K 527635  128   2110540K kmalloc-32
  65247564 65241398  99%0.31K 1279364   51  20469824K arc_buf_hdr_t_full
  58270446 58040685  99%0.10K 747057   78   5976456K abd_t
  16697268 13731405  82%0.38K 397554   42   6360864K dmu_buf_impl_t
  15982912 10366686  64%0.50K 249733   64   7991456K kmalloc-512
  14975616 11605380  77%0.06K 233994   64935976K kmalloc-64
  ```

  In /proc/meminfo:
  ```
  MemTotal:   12656421408 kB
  MemFree:1975976204 kB
  MemAvailable:   1968415088 kB
  Buffers: 1087956 kB
  Cached: 101168004 kB
  SwapCached: 17912340 kB
  Active: 101022084 kB
  Inactive:   4129984264 kB
  Active(anon):   94623216 kB
  Inactive(anon): 4104673512 kB
  Active(file):6398868 kB
  Inactive(file): 25310752 kB
  Unevictable:  338908 kB
  Mlocked:  332132 kB
  SwapTotal:  4294967292 kB
  SwapFree:   3500705532 kB
  Zswap: 0 kB
  Zswapped:  0 kB
  Dirty:  2908 kB
  Writeback: 0 kB
  AnonPages:  4123489132 kB
  Mapped:  3761620 kB
  Shmem:  70756156 kB
  KReclaimable:   10319220 kB
  Slab:   122355620 kB
  SReclaimable:   10319220 kB
  SUnreclaim: 112036400 kB
  KernelStack: 1793296 kB
  PageTables: 21748556 kB
  SecPageTables: 0 kB
  NFS_Unstable:  0 kB
  Bounce:0 kB
  WritebackTmp:  0 kB
  CommitLimit:10623177996 kB
  Committed_AS:   6775476544 kB
  VmallocTotal:   34359738367 kB
  VmallocUsed:296984480 kB
  VmallocChunk:  0 kB
  Percpu:  1326080 kB
  HardwareCorrupted: 0 kB
  AnonHugePages:  1630980096 kB
  ShmemHugePages:0 kB
  ShmemPmdMapped:0 kB
  FileHugePages: 0 kB
  FilePmdMapped: 0 kB
  HugePages_Total:   0
  HugePages_Free:0
  HugePages_Rsvd:0
  HugePages_Surp:0
  Hugepagesize:   2048 kB
  Hugetlb:   0 kB
  DirectMap4k: 2056036 kB
  DirectMap2M:40935424 kB
  DirectMap1G:12814647296 kB
  ```

  Its not a tmpfs/shm fs issue either:
  ```
  df -h | grep -E 'tmpfs|shm'
  tmpfs   256G   70G  187G  27% 
/dev/shm
  tmpfs   256G  3.4M  256G   1% /run
  tmpfs   5.0M 0  5.0M   0% 
/run/lock
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10102
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/1002
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10030
  tmpfs   8.0G   24K  8.0G   1% 
/run/user/10194
  tmpfs   8.0G   24K