date:20220801

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  laptop keyboard not working for about 30 seconds after resume from
  suspend

Status in linux package in Ubuntu:
  Expired

Bug description:
  Fresh install of Ubuntu 22.04, fully updated, no changes or configuration at 
all.
  Newish HP laptop (so recent hardware)

  Problem: After resuming from suspend, the laptop's keyboard is not
  working for about 30 seconds (the laptop's touchpad is working at
  once).

  Looking at dmesg, it looks the keyboard only starts working after:

  [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as
  /devices/platform/i8042/serio0/input/input106

  ... which happens about 35 seconds after the resume sequence
  completes.

  
  From dmesg:

  suspend:

  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:50 2022] Lockdown: systemd-logind: hibernation is 
restricted; see man kernel_lockdown.7
  [di mei 31 19:06:51 2022] usb 1-1: USB disconnect, device number 2
  [di mei 31 19:06:51 2022] PM: suspend entry (s2idle)
  [di mei 31 19:06:51 2022] Filesystems sync: 0.007 seconds
  [di mei 31 19:06:51 2022] Freezing user space processes ... (elapsed 0.001 
seconds) done.
  [di mei 31 19:06:51 2022] OOM killer disabled.
  [di mei 31 19:06:51 2022] Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
  [di mei 31 19:06:51 2022] printk: Suspending console(s) (use 
no_console_suspend to debug)
  [di mei 31 19:06:52 2022] ACPI: EC: interrupt blocked

  
  After 3 minutes: open laptop lid, and it wakes up:

  [di mei 31 19:09:45 2022] ACPI: EC: interrupt unblocked
  [di mei 31 19:09:46 2022] usb 1-10: reset full-speed USB device number 4 
using xhci_hcd
  [di mei 31 19:09:46 2022] OOM killer enabled.
  [di mei 31 19:09:46 2022] Restarting tasks ...
  [di mei 31 19:09:46 2022] mei_hdcp 
:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops 
i915_hdcp_component_ops [i915])
  [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: examining hci_ver=08 
hci_rev=000c lmp_ver=08 lmp_subver=8821
  [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: rom_version status=0 version=1
  [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
  [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8821c_config.bin
  [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: cfg_sz 10, total sz 31990
  [di mei 31 19:09:46 2022] done.
  [di mei 31 19:09:46 2022] PM: suspend exit
  [di mei 31 19:09:46 2022] Bluetooth: hci0: RTL: fw version 0x829a7644

  ... and then after 35 seconds

  [di mei 31 19:10:21 2022] input: AT Translated Set 2 keyboard as
  /devices/platform/i8042/serio0/input/input106

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sander 1329 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 31 19:24:02 2022
  InstallationDate: Installed on 2022-05-31 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD 
Camera
   Bus 001 Device 005: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 14s-dq2xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=6b217a97-66c0-4829-bbef-01ac3d8034c9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-33-generic N/A
   linux-backports-modules-5.15.0-33-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off)

Looking at the code though, I notice that igfx=off actually filters all
GFX.  Maybe it's just badly named:

#define IS_GFX_DEVICE(pdev) ((pdev->class >> 16) ==
PCI_BASE_CLASS_DISPLAY)

So yeah; have a try with "intel_iommu=igfx_off" on kernel command line.

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

Title:
  [radeon] Pictures including wallpaper not showing in kernel 5.14.21
  and later (fixed with intel_iommu=off)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  I can't see pictures in emails or on some pictures on websites.
  Sometimes it just shows the bottom 20mm of pictures. The wallpaper is
  just a blank white screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  2 13:12:31 2022
  DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 
M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149]
  InstallationDate: Installed on 2021-04-26 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / 
Trackpad
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago)
  dmi.bios.date: 06/11/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 199.0.0.0.0
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/+bug/1971146/+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 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off)

> intel_iommu=igfx_off should be enough to resolve issues with GPUs.

Maybe this design dGPU should have IOMMU off.

> @Mario, would you please have some comment in this? thanks

Maybe a new parameter is needed for Intel IOMMU driver to allow
filtering dGPU from IOMMU too?

But this type of error seems to happen on a few kinds of other devices too 
though.
1) TBT controller: https://bugzilla.kernel.org/show_bug.cgi?id=209321
2) eSATA: https://bugzilla.kernel.org/show_bug.cgi?id=98451
3) audio: https://bugzilla.kernel.org/show_bug.cgi?id=215919

** Bug watch added: Linux Kernel Bug Tracker #209321
   https://bugzilla.kernel.org/show_bug.cgi?id=209321

** Bug watch added: Linux Kernel Bug Tracker #98451
   https://bugzilla.kernel.org/show_bug.cgi?id=98451

** Bug watch added: Linux Kernel Bug Tracker #215919
   https://bugzilla.kernel.org/show_bug.cgi?id=215919

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

Title:
  [radeon] Pictures including wallpaper not showing in kernel 5.14.21
  and later (fixed with intel_iommu=off)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  I can't see pictures in emails or on some pictures on websites.
  Sometimes it just shows the bottom 20mm of pictures. The wallpaper is
  just a blank white screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  2 13:12:31 2022
  DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 
M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149]
  InstallationDate: Installed on 2021-04-26 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / 
Trackpad
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago)
  dmi.bios.date: 06/11/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 199.0.0.0.0
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/+bug/1971146/+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 1950195] Re: [amdgpu] Wayland session unresponsive on resume from suspend

2022-08-01 Thread Daniel van Vugt

Jordan, wrong bug - you are experiencing bug 1968040.

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

Title:
  [amdgpu] Wayland session unresponsive on resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop, HP model 17-y028cy, does not resume after the display has
  been shut off for inactivity. The computer starts back up and the
  display does turn on, but nothing is displayed on my screen. It
  doesn't appear to respond to any key presses so I have to force it to
  power down and back up by holding the power button until it shuts off.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  8 11:10:58 2021
  DistUpgraded: 2021-10-22 09:44:17,286 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon R5 Graphics [103c:8221]
  InstallationDate: Installed on 2021-08-18 (82 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=19963d75-e403-4c58-aa01-13462ff038ab ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-22 (17 days ago)
  dmi.bios.date: 01/16/2017
  dmi.bios.release: 15.37
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8221
  dmi.board.vendor: HP
  dmi.board.version: 85.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 85.39
  dmi.modalias: 
dmi:bvnInsyde:bvrF.37:bd01/16/2017:br15.37:efr85.39:svnHP:pnHPNotebook:pvrType1ProductConfigId:sku1MF63UAR#ABA:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: 1MF63UAR#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950195/+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 1983297] Re: Additional fix for TGL + AUO panel flickering

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

** Tags added: originate-from-1981548

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

Title:
  Additional fix for TGL + AUO panel flickering

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Confirmed

Bug description:
  [Impact] 
  "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel"
  alone used to fix the issue on the AUO panel. But the panel starts to
  flicker like crazy on top of the new stable commits. 

  [Fix]
  Backport full fix for PSR2 selective fetch, but only enable it on TGL +
  specific AUO panel. The last three patches which enable PSR2 on ADL-P
  are dropped.

  [Test]
  Originally the backport regressed ADL + BOE panel, so this time we
  put extra effort to ensure those system are unaffected, while TGL + AUO
  panel is still fixed.
   
  [Where problems could occur]
  Most code changes only have functional impact when PSR2 selective fetch
  is enabled. Some of changes are under more general call path for
  hardware cursor rendering.

  Notes are added to describe the functional impact for each patch, so if
  regression really occurrs it's easier to spot the offending commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1983297/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy

2022-08-01 Thread Jay Lepore

Until such time the fix makes it into mainstream, this hack gets things
going again for me.

I took a look at the contents of the directory /var/lib/mysql/#innodb_redo# 
There was only a single file there which of course matched the filename 
identified in the /var/log/mysql/error.log and this was:

-rw-r- 1 mysql mysql 0 Aug  1 19:10 '#ib_redo0'

I deleted it.

Mysql immediately restarted.

In addition, upon restarting generated these files within that same
directory /var/lib/mysql/#innodb_redo#

-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo0'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo10_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo11_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo12_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo13_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo14_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo15_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo16_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo17_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo18_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo19_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo1_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo20_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo21_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo22_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo23_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo24_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo25_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo26_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo27_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo28_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo29_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo2_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo30_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo31_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo3_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo4_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo5_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo6_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo7_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo8_tmp'
-rw-r- 1 mysql mysql 3276800 Aug  1 19:10 '#ib_redo9_tmp'

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

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
  Jammy

Status in Native ZFS for Linux:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Summary]

  When running Jammy on zfs or LXD with a zfs pool on a Jammy host,
  fallocate creates a zero-sized file.

  The issue was originally found when installing mysql on LXD, where
  fallocate would create a zero-sized ib_logfile1 file. The original
  information in this bug is based on that.

  [Steps to Reproduce]

  touch foo.img
  fallocate -z -l 10M foo.img
  ls -la foo.img

  On a non-zfs Jammy system this will show something like:
  -rw-r--r-- 1 root root 10M ...

  while on zfs it will show:
  -rw-rw-r-- 1 root root 0 ...

  [Original Description]
  I came across this error when testing various mysql setups in an LXD 
container and managed to reproduce it consistently. I'm unable to reproduce on 
Ubuntu desktop or server though since the prerequisites are probably handled 
properly there.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 15 21:31:09 2022
  Dmesg:

  ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  KernLog:

  Logs.var.log.daemon.log:

  MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
  MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
   [mysqldump]
   quick
   quote-names
   max_allowed_packet   = 16M
  MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic 
links: '/etc/mysql/my.cnf'
  MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 
'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 
'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 
'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 
'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 
'public_key.pem', 'ca.pem', 'server-key.pem']
  ProcCmdline:

[Kernel-packages] [Bug 1983297] [NEW] Additional fix for TGL + AUO panel flickering

Public bug reported:

[Impact] 
"UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel"
alone used to fix the issue on the AUO panel. But the panel starts to
flicker like crazy on top of the new stable commits. 

[Fix]
Backport full fix for PSR2 selective fetch, but only enable it on TGL +
specific AUO panel. The last three patches which enable PSR2 on ADL-P
are dropped.

[Test]
Originally the backport regressed ADL + BOE panel, so this time we
put extra effort to ensure those system are unaffected, while TGL + AUO
panel is still fixed.
 
[Where problems could occur]
Most code changes only have functional impact when PSR2 selective fetch
is enabled. Some of changes are under more general call path for
hardware cursor rendering.

Notes are added to describe the functional impact for each patch, so if
regression really occurrs it's easier to spot the offending commit.

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

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Status: Confirmed

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

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

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

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

** Summary changed:

- Additional fix for TGL + AUO panel flicker
+ Additional fix for TGL + AUO panel flickering

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

Title:
  Additional fix for TGL + AUO panel flickering

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Confirmed

Bug description:
  [Impact] 
  "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel"
  alone used to fix the issue on the AUO panel. But the panel starts to
  flicker like crazy on top of the new stable commits. 

  [Fix]
  Backport full fix for PSR2 selective fetch, but only enable it on TGL +
  specific AUO panel. The last three patches which enable PSR2 on ADL-P
  are dropped.

  [Test]
  Originally the backport regressed ADL + BOE panel, so this time we
  put extra effort to ensure those system are unaffected, while TGL + AUO
  panel is still fixed.
   
  [Where problems could occur]
  Most code changes only have functional impact when PSR2 selective fetch
  is enabled. Some of changes are under more general call path for
  hardware cursor rendering.

  Notes are added to describe the functional impact for each patch, so if
  regression really occurrs it's easier to spot the offending commit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983297/+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 1971146] Re: [radeon] Pictures including wallpaper not showing in kernel 5.14.21 and later (fixed with intel_iommu=off)

@Mario, would you please have some comment in this? thanks

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

Title:
  [radeon] Pictures including wallpaper not showing in kernel 5.14.21
  and later (fixed with intel_iommu=off)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  I can't see pictures in emails or on some pictures on websites.
  Sometimes it just shows the bottom 20mm of pictures. The wallpaper is
  just a blank white screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  2 13:12:31 2022
  DistUpgraded: 2022-04-24 19:05:38,365 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 
M270X/M370X] [1002:6821] (rev 83) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Radeon R9 M370X Mac Edition [106b:0149]
  InstallationDate: Installed on 2021-04-26 (371 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 003: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller
   Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Apple Internal Keyboard / 
Trackpad
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro11,5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=2234e6d3-3ebc-44e6-b0a5-bef132fd1f72 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (7 days ago)
  dmi.bios.date: 06/11/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 199.0.0.0.0
  dmi.board.name: Mac-06F11F11946D27C5
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,5
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-06F11F11946D27C5
  dmi.modalias: 
dmi:bvnAppleInc.:bvr199.0.0.0.0:bd06/11/2020:br0.1:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5:sku:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro11,5
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  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/+bug/1971146/+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 1982627] Re: MT7612u wireless chipset not working on Raspberry Pi 400

2022-08-01 Thread fauxsys

Hi Juerg, can you explain why this is now invalid?

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

Title:
  MT7612u wireless chipset not working on Raspberry Pi 400

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  I purchased the Alfa AWUS036ACM wireless adapter to use with my
  Raspberry Pi 400. The adapter works when using Raspberry Pi OS, but
  not when using "Ubuntu for Raspberry Pi" release 22.04. I have tested
  64-bit variants for Ubuntu Desktop and Ubuntu Server, and the results
  are the same. I followed the Kernel Firmware Debugging steps, and
  included its output below. The LinuxWireless Debugging steps seem to
  only be appropriate if the wireless adapter is working to some
  capacity so the below output does not include those steps. I also
  attempted to follow the Kernel USB Debugging steps, but the commands
  do not seem appropriate for the Raspberry Pi 400. For example,
  `/proc/bus/usb` and `/sys/kernel/debug/usb/usbmon/` do not exist on
  the filesystem.

  As part of troubleshooting, I updated the bootloader for the Raspberry
  Pi 400 to version 507b2360 which was built on 2022-04-26. I also ran
  `sudo apt update` and `sudo apt full-upgrade`. Neither of these
  troubleshooting steps resolved the problem.

  On a separate note, I have another Ubuntu Server release 22.04 that is
  installed on dedicated hardware (not the "Ubuntu for Raspberry Pi"
  variant), and the wireless adapter does work on this machine.

   Raspberry Pi 400 Output 

  $ sudo modprobe usbmon
  modprobe: FATAL: Module usbmon not found in directory 
/lib/modules/5.15.0-1012-raspi

  
  $ lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  
  $ apt-cache policy linux-firmware
  linux-firmware:
Installed: 20220329.git681281e4-0ubuntu3.2
Candidate: 20220329.git681281e4-0ubuntu3.2
Version table:
   *** 20220329.git681281e4-0ubuntu3.2 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   20220329.git681281e4-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  
  $ sudo udevadm control --log-priority debug

  
  $ tail -f /var/log/syslog
  Jul 22 20:56:03 ubuntu kernel: [  533.687623] usb 2-1: new SuperSpeed USB 
device number 3 using xhci_hcd
  Jul 22 20:56:03 ubuntu kernel: [  533.709177] usb 2-1: New USB device found, 
idVendor=0e8d, idProduct=7612, bcdDevice= 1.00
  Jul 22 20:56:03 ubuntu kernel: [  533.709203] usb 2-1: New USB device 
strings: Mfr=2, Product=3, SerialNumber=4
  Jul 22 20:56:03 ubuntu kernel: [  533.709214] usb 2-1: Product: Wireless
  Jul 22 20:56:03 ubuntu kernel: [  533.709222] usb 2-1: Manufacturer: MediaTek 
Inc.
  Jul 22 20:56:03 ubuntu kernel: [  533.709230] usb 2-1: SerialNumber: 0
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued 
(SEQNUM=4179, ACTION=add)
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: Validate module index
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: Check if link configuration needs 
reloading.
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device ready for processing 
(SEQNUM=4179, ACTION=add)
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: Successfully forked off 'n/a' as 
PID 1330.
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Worker [1330] is forked for 
processing SEQNUM=4179.
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Processing device 
(SEQNUM=4179, ACTION=add)
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Failed to get watch handle, 
ignoring: No such file or directory
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: 
/usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from 
results of builtin command 'usb_id'
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: Device is queued 
(SEQNUM=4180, ACTION=add)
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: SEQNUM=4180 blocked by 
SEQNUM=4179
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued 
(SEQNUM=4181, ACTION=bind)
  Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: SEQNUM=4181 blocked by 
SEQNUM=4179
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: 
/usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from 
results of builtin command 'hwdb --subsystem=usb'
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: hwdb modalias key: 
"usb:v0E8Dp7612:Wireless "
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: 
/usr/lib/udev/rules.d/50-udev-default.rules:50 MODE 0664
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: 
/usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of 
builtin command 'path_id'
  Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Setting permissions 
/dev/bus/usb/002/003, uid=0, gid=0, mode=0664
  Jul 22 20:56:03 ubuntu

[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch

2022-08-01 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

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

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1983293/+attachment/5606346/+files/acpidump.txt

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

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1983293/+attachment/5606342/+files/PulseList.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/1983293

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1983293/+attachment/5606336/+files/PaInfo.txt

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

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

apport information

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graphite   2307 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-01-04 (209 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20XWCTO1WW
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-43-generic N/A
   linux-backports-modules-5.15.0-43-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.3
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-43-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
  _MarkForUpload: True
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983293/+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 1983293] Re: Speaker sound no longer working after 22.04 upgrade on Lenovo X1 Carbon 9Gen

apport information

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

** Description changed:

  After an upgrade to 22.04 my speakers no longer function properly. With
  the volume at 153% in pavucontrol I can barely hear it (need to put my
  ear almost next to the speaker). I remember I had the same issue after a
  fresh install of 21.04 back in December, but I can no longer recall how
  I fixed it.
  
  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
  
  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)
  
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  
- alsamixer has Speaker and Bass Speaker at 00 and those cannot be
- adjusted, see screenshot. DAC1 and DAC2 control left and right speaker
- respectively (when at 0 can not hear anything even with my ear at the
- speaker).
+ alsamixer has Speaker and Bass Speaker at 00 and those cannot be adjusted, 
see screenshot. DAC1 and DAC2 control left and right speaker respectively (when 
at 0 can not hear anything even with my ear at the speaker).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  graphite   2307 F pulseaudio
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-01-04 (209 days ago)
+ InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
+ MachineType: LENOVO 20XWCTO1WW
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
+ RelatedPackageVersions:
+  linux-restricted-modules-5.15.0-43-generic N/A
+  linux-backports-modules-5.15.0-43-generic  N/A
+  linux-firmware 20220329.git681281e4-0ubuntu3.3
+ Tags:  wayland-session jammy
+ Uname: Linux 5.15.0-43-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-07-27 (5 days ago)
+ UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo tss
+ _MarkForUpload: True
+ dmi.bios.date: 12/02/2021
+ dmi.bios.release: 1.51
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N32ET75W (1.51 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20XWCTO1WW
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.31
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.31:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
+ dmi.product.family: ThinkPad X1 Carbon Gen 9
+ dmi.product.name: 20XWCTO1WW
+ dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
+ dmi.product.version: ThinkPad X1 Carbon Gen 9
+ dmi.sys.vendor: LENOVO

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []

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

2022-08-01 Thread 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 1983293

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be
  adjusted, see screenshot. DAC1 and DAC2 control left and right speaker
  respectively (when at 0 can not hear anything even with my ear at the
  speaker).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983293/+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 1983293] [NEW] Speaker sound no longer working after 22.04 upgrade on Lenovo X1 Carbon 9Gen

Public bug reported:

After an upgrade to 22.04 my speakers no longer function properly. With
the volume at 153% in pavucontrol I can barely hear it (need to put my
ear almost next to the speaker). I remember I had the same issue after a
fresh install of 21.04 back in December, but I can no longer recall how
I fixed it.

uname -a
5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

aplay -l
 List of PLAYBACK Hardware Devices 
card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
  Subdevices: 0/1
  Subdevice #0: subdevice #0

alsamixer has Speaker and Bass Speaker at 00 and those cannot be
adjusted, see screenshot. DAC1 and DAC2 control left and right speaker
respectively (when at 0 can not hear anything even with my ear at the
speaker).

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

** Attachment added: "Screenshot from 2022-08-01 19-57-34.png"
   
https://bugs.launchpad.net/bugs/1983293/+attachment/5606327/+files/Screenshot%20from%202022-08-01%2019-57-34.png

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

Title:
  Speaker sound no longer working after 22.04 upgrade on Lenovo X1
  Carbon 9Gen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade to 22.04 my speakers no longer function properly.
  With the volume at 153% in pavucontrol I can barely hear it (need to
  put my ear almost next to the speaker). I remember I had the same
  issue after a fresh install of 21.04 back in December, but I can no
  longer recall how I fixed it.

  uname -a
  5.15.0-43-generic #46-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

  lspci | grep -i audio
  00:1f.3 Audio device: Intel Corporation Tiger Lake-LP Smart Sound Technology 
Audio Controller (rev 20)

  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []
Subdevices: 0/1
Subdevice #0: subdevice #0

  alsamixer has Speaker and Bass Speaker at 00 and those cannot be
  adjusted, see screenshot. DAC1 and DAC2 control left and right speaker
  respectively (when at 0 can not hear anything even with my ear at the
  speaker).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983293/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

** Tags removed: verification-needed-jammy
** Tags added: verification-failed-jammy

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1983291] [NEW] Update firmware for DCN316/GFX1037

Public bug reported:

[Impact]
Jammy already has firmware for upcoming product with GFX1037 and DCN316.  
However this firmware has some stability problems under stress and it should be 
updated to latest on linux-firmware.git to support systems that will take this 
firmware.

[Fix]
Upgrade following binaries:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122

[Test]
Verify suspend/resume works.
Verify that accelerated graphics works.
Verify video playback works.

[Where problems could occur]
Firmware is only loaded to product with GFX1037/DCN316
This isn't yet on the market and regressions are not possible.

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

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

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


** Tags: originate-from-1971216

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

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

** Changed in: linux-firmware (Ubuntu Kinetic)
   Status: New => Fix Released

** Tags added: originate-from-1971216

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

Title:
  Update firmware for DCN316/GFX1037

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  New
Status in linux-firmware source package in Kinetic:
  Fix Released

Bug description:
  [Impact]
  Jammy already has firmware for upcoming product with GFX1037 and DCN316.  
However this firmware has some stability problems under stress and it should be 
updated to latest on linux-firmware.git to support systems that will take this 
firmware.

  [Fix]
  Upgrade following binaries:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=61eb408159a726decd36350af4017e16b7001d78
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b4994be7d27c7c3f44e80913c547289d2033458f
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=84661a3ba62f07e62795f5999c2e8660aae5d122

  [Test]
  Verify suspend/resume works.
  Verify that accelerated graphics works.
  Verify video playback works.

  [Where problems could occur]
  Firmware is only loaded to product with GFX1037/DCN316
  This isn't yet on the market and regressions are not possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1983291/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

I've changed state because technically, issue still persists on the Ubuntu 
Jammy in default kernel configurations. I've prepared fixes for two kernels:
- master-next
- hwe-5.17

I'm not sure if I need to port these changes to some other branches. I
think I need some advice from ubuntu kernel team guys regarding this.

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1967924

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

fix for Jammy linux kernel 5.15 master-next branch was sent to kernel-
t...@lists.ubuntu.com

** Patch added: 
"0001-UBUNTU-SAUCE-overlayfs-remove-CONFIG_AUFS_FS-depende.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+attachment/5606321/+files/0001-UBUNTU-SAUCE-overlayfs-remove-CONFIG_AUFS_FS-depende.patch

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1980594] Re: /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM

This bug was fixed in the package linux-starfive-5.17 - 5.17.0-1005.6

---
linux-starfive-5.17 (5.17.0-1005.6) jammy; urgency=medium

  * jammy/linux-starfive-5.17: 5.17.0-1005.6 -proposed tracker (LP:
#1983089)

  * Pinctrl driver has a race condition bug (LP: #1983019)
- pinctrl: starfive: Serialize adding groups and functions

  * /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
(LP: #1980594)
- RISC-V: KVM: Fix SRCU deadlock caused by kvm_riscv_check_vcpu_requests()

 -- Emil Renner Berthing   Fri, 29
Jul 2022 15:02:57 +0200

** Changed in: linux-starfive-5.17 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM

Status in linux package in Ubuntu:
  In Progress
Status in linux-allwinner-5.17 package in Ubuntu:
  In Progress
Status in linux-riscv package in Ubuntu:
  Invalid
Status in linux-starfive-5.17 package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux-allwinner-5.17 source package in Jammy:
  Fix Committed
Status in linux-riscv source package in Jammy:
  Invalid
Status in linux-starfive-5.17 source package in Jammy:
  Fix Released

Bug description:
  QEMU 7.0 supports KVM on RISC-V.
  Package u-boot-qemu supplies /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf.

  That binary cannot be used to boot via qemu-system-riscv64 -kvm.

  File u-boot produced by qemu-riscv64_smode_defconfig with

  CONFIG_MTD_NOR_FLASH=n
  CONFIG_CMD_NET=n

  can be used to start U-Boot with qemu-system-riscv64 -kvm. But any
  virtio access leads to a crash leaving QEMU unresponsive.

  Cf. https://lists.denx.de/pipermail/u-boot/2022-July/487893.html
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 10 19:58 seq
   crw-rw 1 root audio 116, 33 Jul 10 19:58 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: riscv64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Red Hat, Inc. QEMU PCIe Host bridge
  +-01.0  Red Hat, Inc. QEMU XHCI Host Controller
  +-02.0  Red Hat, Inc. Virtio block device
  \-03.0  Red Hat, Inc. Virtio block device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   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/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux-starfive-5.17 (not installed)
  PciMultimedia:
   
  ProcCpuinfoMinimal:
   processor: 7
   hart : 7
   isa  : rv64imafdcsuh
   mmu  : sv48
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-starfive 
root=UUID=504657a8-56e8-431b-9c85-65c5737ccf80 ro default_hugepagesz=2M 
hugepagesz=2M hugepages=2048 earlycon efi=debug
  ProcVersionSignature: Ubuntu 5.17.0-1003.4-starfive 5.17.9
  RelatedPackageVersions:
   linux-restricted-modules-5.17.0-1003-starfive N/A
   linux-backports-modules-5.17.0-1003-starfive  N/A
   linux-firmware20220621.git7b71b75b-0ubuntu1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic uec-images
  Uname: Linux 5.17.0-1003-starfive riscv64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  acpidump:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980594/+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 1983019] Re: Pinctrl driver has a race condition bug

This bug was fixed in the package linux-starfive-5.17 - 5.17.0-1005.6

---
linux-starfive-5.17 (5.17.0-1005.6) jammy; urgency=medium

  * jammy/linux-starfive-5.17: 5.17.0-1005.6 -proposed tracker (LP:
#1983089)

  * Pinctrl driver has a race condition bug (LP: #1983019)
- pinctrl: starfive: Serialize adding groups and functions

  * /usr/lib/u-boot/qemu-riscv64_smode/uboot.elf cannot be booted with KVM
(LP: #1980594)
- RISC-V: KVM: Fix SRCU deadlock caused by kvm_riscv_check_vcpu_requests()

 -- Emil Renner Berthing   Fri, 29
Jul 2022 15:02:57 +0200

** Changed in: linux-starfive-5.17 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Pinctrl driver has a race condition bug

Status in linux-starfive-5.17 package in Ubuntu:
  In Progress
Status in linux-starfive-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * The pinctrl-starfive driver has a race when initializing groups and
 functions that may result in other drivers not being able to initialize.

   * If this happens to the mmc driver the board will fail to boot.

   * This is an example of this happening:

  Loading device tree blob...
  [   13.933777] pinctrl-starfive 1191.pinctrl: does not have pin group 
sdio0-0.sdio-pins
  [   13.941940] pinctrl-starfive 1191.pinctrl: invalid group 
sdio0-0.sdio-pins in map table
  [   13.957656] pinctrl-starfive 1191.pinctrl: does not have pin group 
sdio0-0.sdio-pins
  [   13.965801] pinctrl-starfive 1191.pinctrl: could not map group config 
for "sdio0-0.sdio-pins"
  [   13.974746] Unable to handle kernel NULL pointer dereference at virtual 
address 
  [   13.983581] Oops [#1]
  [   13.985853] Modules linked in: phylink dw_mmc_pltfm 
clk_starfive_jh7100_audio reset_starfive_jh7100_audio(+) dw_mc
  [   13.986227] starfive-drm soc:display-subsystem: bound 1200.crtc (ops 
starfive_crtc_component_ops)
  [   13.996286] CPU: 1 PID: 8 Comm: kworker/u4:0 Not tainted 
5.17.0-1004-starfive #5-Ubuntu
  [   13.996297] Hardware name: StarFive VisionFive V1 (DT)
  [   13.996305] Workqueue: events_unbound async_run_entry_fn
  [   14.023868] epc : strcmp+0x12/0x36
  [   14.027274]  ra : pinmux_func_name_to_selector+0x5a/0x76
  [   14.032583] epc : 80521224 ra : 805307d8 sp : 
ffd88006bb00
  [   14.039781]  gp : 81e32e30 tp : ffd87ffd t0 : 
0040
  [   14.046988]  t1 :  t2 : 81004ed4 s0 : 
ffd88006bb10
  [   14.054190]  s1 : 0006 a0 : ffd9ff1d3cb8 a1 : 

  [   14.061392]  a2 :  a3 :  a4 : 
ffd88c45ce00
  [   14.068594]  a5 : 0073 a6 : ffd88c45cdb0 a7 : 
ffd88c45ce08
  [   14.075795]  s2 : ffd897c53000 s3 : 0007 s4 : 
ffd9ff1d3cb8
  [   14.082996]  s5 : 810776f0 s6 :  s7 : 
ffd8801aa5c0
  [   14.090199]  s8 : ffd890fdf780 s9 : fdfb s10: 
81d80008
  [   14.097400]  s11:  t3 : 0002 t4 : 
0402
  [   14.104600]  t5 : ffd897c53040 t6 : ffd897c53048
  [   14.109896] status: 00020120 badaddr:  cause: 
000d
  [   14.117986] ---[ end trace  ]---

  [Test Plan]

   * Unfortunately this is a race that happens rarely so rebooting the board
 several times is the only known way to reproduce.

  [Where problems could occur]

   * The fix could get the locking wrong and lock up the machine at
  boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-starfive-5.17/+bug/1983019/+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 1981173] Re: Clear PCI errors left from BIOS

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1047.54

---
linux-oem-5.14 (5.14.0-1047.54) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1047.54 -proposed tracker (LP:
#1981285)

  * intel_iommu: Fix  enable intel_iommu, Ubuntu 22.04 installation crashes
(LP: #1982104)
- iommu/vt-d: Fix RID2PASID setup/teardown failure

  * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
(LP: #1981950)
- net: atlantic: remove deep parameter on suspend/resume functions
- net: atlantic: remove aq_nic_deinit() when resume

  * Make cm32181 sensor work after system suspend (LP: #1981773)
- iio: light: cm32181: Add PM support

  * Clear PCI errors left from BIOS (LP: #1981173)
- PCI: Clear PCI_STATUS when setting up device

  * Miscellaneous Ubuntu changes
- [Config] Drop CONFIG_PAHOLE_HAS_SPLIT_BTF again

 -- Timo Aaltonen   Tue, 26 Jul 2022
14:10:52 +0300

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Clear PCI errors left from BIOS

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Errors like Master Abort can be flagged before setting up PCI devices.

  [Fix]
  Clear PCI status that BIOS handed over to the OS.

  [Test]
  Using `lspci`, no more errors after boot.

  [Where problems could occur]
  If there's any driver's probe routine depends on PCI status to have 
  different behavior, this can cause some cracks. There doesn't seem to be
  any driver doing such insane thing though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981173/+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 1981773] Re: Make cm32181 sensor work after system suspend

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1047.54

---
linux-oem-5.14 (5.14.0-1047.54) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1047.54 -proposed tracker (LP:
#1981285)

  * intel_iommu: Fix  enable intel_iommu, Ubuntu 22.04 installation crashes
(LP: #1982104)
- iommu/vt-d: Fix RID2PASID setup/teardown failure

  * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
(LP: #1981950)
- net: atlantic: remove deep parameter on suspend/resume functions
- net: atlantic: remove aq_nic_deinit() when resume

  * Make cm32181 sensor work after system suspend (LP: #1981773)
- iio: light: cm32181: Add PM support

  * Clear PCI errors left from BIOS (LP: #1981173)
- PCI: Clear PCI_STATUS when setting up device

  * Miscellaneous Ubuntu changes
- [Config] Drop CONFIG_PAHOLE_HAS_SPLIT_BTF again

 -- Timo Aaltonen   Tue, 26 Jul 2022
14:10:52 +0300

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Make cm32181 sensor work after system suspend

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  cm32181 ambient light sensor stops working after system suspend.

  [Fix]
  Add PM support for cm32181 so it can work after system suspend.

  [Test]
  The sysfs in_illuminance_input continues to change after system suspend.

  [Where problems could occur]
  This changeset is limited to a specific device, and it already lacks PM
  support - so the worst case is that it stops working after resume like
  it always has been.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981773/+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 1982104] Re: intel_iommu: Fix enable intel_iommu, Ubuntu 22.04 installation crashes

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1047.54

---
linux-oem-5.14 (5.14.0-1047.54) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1047.54 -proposed tracker (LP:
#1981285)

  * intel_iommu: Fix  enable intel_iommu, Ubuntu 22.04 installation crashes
(LP: #1982104)
- iommu/vt-d: Fix RID2PASID setup/teardown failure

  * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
(LP: #1981950)
- net: atlantic: remove deep parameter on suspend/resume functions
- net: atlantic: remove aq_nic_deinit() when resume

  * Make cm32181 sensor work after system suspend (LP: #1981773)
- iio: light: cm32181: Add PM support

  * Clear PCI errors left from BIOS (LP: #1981173)
- PCI: Clear PCI_STATUS when setting up device

  * Miscellaneous Ubuntu changes
- [Config] Drop CONFIG_PAHOLE_HAS_SPLIT_BTF again

 -- Timo Aaltonen   Tue, 26 Jul 2022
14:10:52 +0300

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  intel_iommu: Fix  enable intel_iommu, Ubuntu 22.04 installation
  crashes

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Kinetic:
  Invalid
Status in linux-oem-5.17 source package in Kinetic:
  Invalid

Bug description:
  [Impact]
  Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server.
  Attaching the console logs.

  Currently, it looks like disabling VT-D option in BIOS settings helps 
mitigate the issue.
  Console logs indicate something is wrong in iommu/dmar subsystem.

  [Fix]
  The IOMMU driver shares the pasid table for PCI alias devices. When the
  RID2PASID entry of the shared pasid table has been filled by the first
  device, the subsequent device will encounter the "DMAR: Setup RID2PASID
  failed" failure as the pasid entry has already been marked as present.
  As the result, the IOMMU probing process will be aborted.

  On the contrary, when any alias device is hot-removed from the system,
  for example, by writing to /sys/bus/pci/devices/.../remove, the shared
  RID2PASID will be cleared without any notifications to other devices.
  As the result, any DMAs from those rest devices are blocked.

  Sharing pasid table among PCI alias devices could save two memory pages
  for devices underneath the PCIe-to-PCI bridges. Anyway, considering that
  those devices are rare on modern platforms that support VT-d in scalable
  mode and the saved memory is negligible, it's reasonable to remove this
  part of immature code to make the driver feasible and stable.

  [Test Case]
  1. use the target machine(Intel Sapphire Rapids) and install the kernel with 
the fix.
  2. boot the target machine
  3. check dmesg if the error message exists
  [ 8.120527] pci :03:01.0: DMAR: Setup RID2PASID failed

  [Where problems could occur]
  After enable intel_iommu, the errors may be occurred.
  We need to figure out one by one once the related errors are triggered in the 
future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1982104/+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 1981950] Re: Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1047.54

---
linux-oem-5.14 (5.14.0-1047.54) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1047.54 -proposed tracker (LP:
#1981285)

  * intel_iommu: Fix  enable intel_iommu, Ubuntu 22.04 installation crashes
(LP: #1982104)
- iommu/vt-d: Fix RID2PASID setup/teardown failure

  * Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]
(LP: #1981950)
- net: atlantic: remove deep parameter on suspend/resume functions
- net: atlantic: remove aq_nic_deinit() when resume

  * Make cm32181 sensor work after system suspend (LP: #1981773)
- iio: light: cm32181: Add PM support

  * Clear PCI errors left from BIOS (LP: #1981173)
- PCI: Clear PCI_STATUS when setting up device

  * Miscellaneous Ubuntu changes
- [Config] Drop CONFIG_PAHOLE_HAS_SPLIT_BTF again

 -- Timo Aaltonen   Tue, 26 Jul 2022
14:10:52 +0300

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Failed to resume from S3 blocked by atlantic driver[1d6a:94c0]

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The system with atlantic NIC[1d6a:94c0] fails to resume from S3 and hang with 
the following errors

  Jun 7 13:13:54 ubuntu kernel: [ 116.000561] aq_nic_deinit+0xb4/0xd0 [atlantic]
  Jun 7 13:13:54 ubuntu kernel: [ 116.000566] atl_resume_common+0x6d/0x110 
[atlantic]
  Jun 7 13:13:54 ubuntu kernel: [ 116.000571] aq_pm_resume_restore+0x13/0x20 
[atlantic]
  Jun 7 13:13:54 ubuntu kernel: [ 116.000575] pci_pm_resume+0x5c/0x90
  Jun 7 13:13:54 ubuntu kernel: [ 116.000578] ? pci_pm_thaw+0x80/0x80
  Jun 7 13:13:54 ubuntu kernel: [ 116.000580] dpm_run_callback+0x4e/0x120
  Jun 7 13:13:54 ubuntu kernel: [ 116.000582] device_resume+0xad/0x200
  Jun 7 13:13:54 ubuntu kernel: [ 116.000583] async_resume+0x1e/0x40
  Jun 7 13:13:54 ubuntu kernel: [ 116.000585] async_run_entry_fn+0x33/0x120
  Jun 7 13:13:54 ubuntu kernel: [ 116.000586] process_one_work+0x220/0x3c0
  Jun 7 13:13:54 ubuntu kernel: [ 116.000588] worker_thread+0x4d/0x3f0
  Jun 7 13:13:54 ubuntu kernel: [ 116.000589] ? process_one_work+0x3c0/0x3c0
  Jun 7 13:13:54 ubuntu kernel: [ 116.000591] kthread+0x12a/0x150
  Jun 7 13:13:54 ubuntu kernel: [ 116.000592] ? set_kthread_struct+0x40/0x40
  Jun 7 13:13:54 ubuntu kernel: [ 116.000593] ret_from_fork+0x22/0x30
  Jun 7 13:13:54 ubuntu kernel: [ 116.000596] 
  Jun 7 13:13:54 ubuntu kernel: [ 116.000596] ---[ end trace 9d3fcd41d27dae25 
]---

  [Fix]
  aq_nic_deinit() has been called while suspending, so don't need to call it 
again on resuming.
  Applied below 2 commits from v5.19-rc7 fix the issue, and the 2 commits have 
been applied to stable kernel v5.10, v5.15, and v5.18.

  2e15c51fefaf net: atlantic: remove aq_nic_deinit() when resume
  0f3325076038 net: atlantic: remove deep parameter on suspend/resume functions

  [Test]
  Verified on the system with atlantic NIC[1d6a:94c0] and run S3 test for more 
than 200 times.

  [Where problems could occur]
  The 2 commits remove the redundant code, aq_nic_deinit() has been called 
while suspending, so we don't need to call it again while resuming, and this 
fix the issue. I don't think this would introduce any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1981950/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

Fix for Jammy linux master branch (linux kernel 5.15) will be ready
tomorrow.

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

Fix for Jammy hwe-5.17 was sent to kernel-t...@lists.ubuntu.com

** Attachment added: "Jammy hwe-5.17"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+attachment/5606318/+files/jammy-hwe-5.17.tar.gz

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1950195] Re: [amdgpu] Wayland session unresponsive on resume from suspend

2022-08-01 Thread Jordan Christiansen

I have the same issue. In Gnome on Wayland or GDM on Wayland, my system
is unresponsive after resuming from suspend. The screen is black and
switching to other VTs is impossible. This does not happen if I'm logged
in to a Gnome on Xorg session at the time of the suspend.

I have an Intel CPU and GPU.

** Attachment added: "Previous boot log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950195/+attachment/5606317/+files/prevboot.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/1950195

Title:
  [amdgpu] Wayland session unresponsive on resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop, HP model 17-y028cy, does not resume after the display has
  been shut off for inactivity. The computer starts back up and the
  display does turn on, but nothing is displayed on my screen. It
  doesn't appear to respond to any key presses so I have to force it to
  power down and back up by holding the power button until it shuts off.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  8 11:10:58 2021
  DistUpgraded: 2021-10-22 09:44:17,286 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon R5 Graphics [103c:8221]
  InstallationDate: Installed on 2021-08-18 (82 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HP HP Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=19963d75-e403-4c58-aa01-13462ff038ab ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to impish on 2021-10-22 (17 days ago)
  dmi.bios.date: 01/16/2017
  dmi.bios.release: 15.37
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8221
  dmi.board.vendor: HP
  dmi.board.version: 85.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 85.39
  dmi.modalias: 
dmi:bvnInsyde:bvrF.37:bd01/16/2017:br15.37:efr85.39:svnHP:pnHPNotebook:pvrType1ProductConfigId:sku1MF63UAR#ABA:rvnHP:rn8221:rvr85.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: 1MF63UAR#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950195/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy

2022-08-01 Thread Lucas Kanashiro

@mrichtarsky from the logs, mysql was not able to redo the actions
during the upgrade because the size of the ib_redo6 file was not
multiple of innodb_page_size. However, the default of innodb_page_size
is 16kb (https://dev.mysql.com/doc/refman/8.0/en/server-status-
variables.html#statvar_Innodb_page_size), and 1712128/16 = 107008. Did
you change the innodb_page_size global value by any chance? If you can
share your configuration it might be helpful.

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

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
  Jammy

Status in Native ZFS for Linux:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Summary]

  When running Jammy on zfs or LXD with a zfs pool on a Jammy host,
  fallocate creates a zero-sized file.

  The issue was originally found when installing mysql on LXD, where
  fallocate would create a zero-sized ib_logfile1 file. The original
  information in this bug is based on that.

  [Steps to Reproduce]

  touch foo.img
  fallocate -z -l 10M foo.img
  ls -la foo.img

  On a non-zfs Jammy system this will show something like:
  -rw-r--r-- 1 root root 10M ...

  while on zfs it will show:
  -rw-rw-r-- 1 root root 0 ...

  [Original Description]
  I came across this error when testing various mysql setups in an LXD 
container and managed to reproduce it consistently. I'm unable to reproduce on 
Ubuntu desktop or server though since the prerequisites are probably handled 
properly there.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 15 21:31:09 2022
  Dmesg:

  ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  KernLog:

  Logs.var.log.daemon.log:

  MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
  MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
   [mysqldump]
   quick
   quote-names
   max_allowed_packet   = 16M
  MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic 
links: '/etc/mysql/my.cnf'
  MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 
'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 
'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 
'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 
'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 
'public_key.pem', 'ca.pem', 'server-key.pem']
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: mysql-8.0
  Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy

2022-08-01 Thread Lucas Kanashiro

There is no task for this bug targeting Ubuntu Focal (20.04), that's why
it is not fixed there. Apparently, no one reported this issue there,
only in Jammy (22.04). @shadowlmd could you confirm if you are facing
the very same issue described on this bug in Focal? If it is another
issue please file another bug with details.

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

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
  Jammy

Status in Native ZFS for Linux:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released

Bug description:
  [Summary]

  When running Jammy on zfs or LXD with a zfs pool on a Jammy host,
  fallocate creates a zero-sized file.

  The issue was originally found when installing mysql on LXD, where
  fallocate would create a zero-sized ib_logfile1 file. The original
  information in this bug is based on that.

  [Steps to Reproduce]

  touch foo.img
  fallocate -z -l 10M foo.img
  ls -la foo.img

  On a non-zfs Jammy system this will show something like:
  -rw-r--r-- 1 root root 10M ...

  while on zfs it will show:
  -rw-rw-r-- 1 root root 0 ...

  [Original Description]
  I came across this error when testing various mysql setups in an LXD 
container and managed to reproduce it consistently. I'm unable to reproduce on 
Ubuntu desktop or server though since the prerequisites are probably handled 
properly there.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 15 21:31:09 2022
  Dmesg:

  ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  KernLog:

  Logs.var.log.daemon.log:

  MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
  MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
   [mysqldump]
   quick
   quote-names
   max_allowed_packet   = 16M
  MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic 
links: '/etc/mysql/my.cnf'
  MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 
'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 
'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 
'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 
'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 
'public_key.pem', 'ca.pem', 'server-key.pem']
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: mysql-8.0
  Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1969247/+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 1980730] Re: OVS internal port Hardware Offload implementation is missing in Jammy kernel

2022-08-01 Thread Zachary Tahenakos

Hey Itai,

That's great! When you were testing this, did you happen to do any other
generic testing, or would the tests you did here be considered suitable
for testing of the mlx5 driver to ensure there are no potential
regressions?

-Zack

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

Title:
  OVS internal port Hardware Offload implementation is missing in Jammy
  kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Platform: OpenStack Yoga, Ubuntu 22.04 Jammy, Kernel 5.15.0-37-generic

  When deploying Charmed Openstack deployment with HW Offload over Jammy 
series, some of the traffic workloads (mainly those related to Floating IP and 
NAT) will not be properly offloaded.
  In order to solve it, "OVS internal port offload" feature was introduced and 
pushed to upstream kernel.

  These are the main base patches for the feature we call "OVS internal
  port offload":

  b16eb3c81fe27978afdb2c111908d4d627a88d99 net/mlx5: Support internal port as 
decap route device
  5e9942721749fc96b9df4b0545474153316c0571 net/mlx5e: Term table handling of 
internal port rules
  166f431ec6beaf472bc2e116a202a127b64779e4 net/mlx5e: Add indirect tc offload 
of ovs internal port
  100ad4e2d75837c9b42f49b3814b4b42ec9ebe46 net/mlx5e: Offload internal port as 
encap route device
  27484f7170edabbda7b53650cd24d38295cffe60 net/mlx5e: Offload tc rules that 
redirect to ovs internal port
  dbac71f22954276633e525f958994f84a7bd303f net/mlx5e: Accept action skbedit in 
the tc actions list
  4f4edcc2b84fecec66748ecbb90a84b981ecdaae net/mlx5: E-Switch, Add ovs internal 
port mapping to metadata support
  189ce08ebf876df2b51f625877731055475352df net/mlx5e: Use generic name for the 
forwarding dev pointer
  28e7606fa8f106cdc0355e0548396c037443e063 net/mlx5e: Refactor rx handler of 
represetor device

  Please make sure to take as well all patches the came later on top of
  those base patches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980730/+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 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

2022-08-01 Thread Alex A. D.

Suprising, but having the same issue after updating recently to Kubuntu
22.04 (Kernel: 5.15.0-43-generic).

Worked it around by: 
   $ sudo systemctl disable hv-kvp-daemon.service

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

  Impact: The KVP daemon fails to start on first boot due to being
  started before the hv_kvp device appears.

  Fix: Update the hv-kvp-daemon service file to start the daemon after
  device node appears.

  Regression Potential: The changes are only to the hv-kvp-daemon
  service file and adding a udev rule, so the worst case regression
  would be that the service does not start. In testing the service did
  start as expected.

  Test Case: See comment #15.

  ---

  
  Launching a recent daily image of disco on azure results in a VM in which the 
hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
     Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
     Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  ---
  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': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+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 1980884] Re: ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF is used

2022-08-01 Thread Si-Wei Liu

It is verified SEV works for the v5.15 kernel where we wants SEV to be
supported. Closing this one for v5.11 now.

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

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

Title:
  ubuntu guest kernel panics when a sev guest with passthrough mlx5 VF
  is used

Status in linux-oracle-5.11 package in Ubuntu:
  Invalid

Bug description:
  Guest kernel panic can be observed when Ubuntu SEV guest with mlx5 vfio-pci 
is started
  as iperf3 server using "iperf3 -s" and as soon as the client tries to connect
  with it.

  Steps to reproduce:

  HOST INFO
  Host type : OCI (Oracle Cloud) Bare-Metal Server
  Server/Machine: ORACLE SERVER E4-2c
  CPU model : AMD EPYC 7J13 64-Core Processor
  Architecture  : x86_64
  Host OS   : Oracle Linux Server release 7.9
  Host Kernel   : 5.4.17-2136.309.3.el7uek.x86_64 #2 SMP Tue Jun 14 21:58:29 
PDT 2022
  Hypervisor: QEMU emulator version 4.2.1 (qemu-4.2.1-17.1.el7)
  OVMF/AAVMF: OVMF-1.6.2-2.el7.noarch
  libiscsi  : libiscsi-1.19.0-1.el7.x86_64
  Guest Kernel  : 5.11.0-1028-ORACLE

  1) Start Ubuntu 20.04/18.04 SEV guest with vfio-pci:

  /usr/bin/qemu-system-x86_64 -machine q35 -name OL20.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol20.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-20.04-2022.02.15-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.1 -qmp tcp:127.0.0.1:3334,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL20.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0

  2) Start a client guest OL/Ubuntu:

  /usr/bin/qemu-system-x86_64 -machine q35 -name OL18.04-uefi -enable-kvm
  -nodefaults -cpu host,+host-phys-bits -m 8G -smp 8,maxcpus=240 -monitor stdio
  -vnc 0.0.0.0:0,to=999 -vga std -drive
  
file=/usr/share/OVMF/OVMF_CODE.pure-efi.fd,index=0,if=pflash,format=raw,readonly
 -drive file=OVMF_VARS.pure-efi.fd.ol18.04,index=1,if=pflash,format=raw
  -device
  virtio-scsi-pci,id=virtio-scsi-pci0,disable-legacy=on,iommu_platform=true
  -drive
  
file=/systest/atanveer/scripts/Ubuntu-18.04-2022.02.13-0-uefi-x86_64.qcow2,if=none,id=local_disk0,format=qcow2,media=disk
 -device
  ide-hd,drive=local_disk0,id=local_disk1,bootindex=0  -net none -device
  vfio-pci,host=:21:10.2 -qmp tcp:127.0.0.1:,server,nowait -serial
  telnet:127.0.0.1:,server,nowait  -D ./OL18.04-uefi.log -device
  virtio-rng-pci,disable-legacy=on,iommu_platform=true -object
  sev-guest,id=sev0,cbitpos=51,reduced-phys-bits=1 -machine
  memory-encryption=sev0

  3) Flush iptables on both the VMs using "iptables -F"

  4) Start the iperf3 server on the first VM using "iperf3 -s"

  5) Start the iperf3 client on the second VM using "iperf3 -c  -4
  -f M -i 0 -t 70 -O 10 -P 64"

  The kernel panic is seen on the first VM i.e. Ubuntu 20.04 with iperf3 also
  showing "Bad Address" error.

  Console logs:

  root@ubuntu-20-04:~# iperf3 -s
  ---
  Server listening on 5201
  ---
  Accepted connection from 10.196.246.104, port 33732
  [  5] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33734
  [  8] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33736
  [ 10] local 10.196.247.88 port 5201 connected to 10.196.246.104 port 33738
  iperf3: error - unable to read from stream socket: Bad address
  ---
  Server listening on 5201
  ---
  [   91.083856] general protection fault:  [#1] SMP NOPTI
  [   91.084591] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 5.11.0-1028-oracle
  #31~20.04.1-Ubuntu
  [   91.085393] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.6.2
  06/01/2022
  [   91.086205] RIP: 0010:memcpy_erms+0x6/0x10
  [   91.086640] Code: cc cc cc cc eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03
  83 e2 07 f3 48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1  a4
  c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
  [   91.088559] RSP: 0018:a9c1408e4b60 EFLAGS: 00010282
  [   91.089105] RAX: 938cd8e48000 RBX: 1000 RCX:
  1000
  [   91.089843] RDX: 1000 RSI:

[Kernel-packages] [Bug 1933510] Re: Support for SFH changes in Yellow Carp

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

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

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

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

Title:
  Support for SFH changes in Yellow Carp

Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Won't Fix
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  AMD Yellow carp will require some changes for sensor fusion hub in amd_sfh 
driver.
  The following changes are queued for kernel 5.14:
  
https://patchwork.kernel.org/project/linux-input/cover/20210618081838.4156571-1-basavaraj.nati...@amd.com/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933510/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it

2022-08-01 Thread Christophe Combelles

Got it under Debian 11

Short summary without completely disabling btusb autosuspend :

- Run powertop and identify the line in the "Tunables" tab that fix your 
problem when you switch it to "Bad" by hitting the Enter key.
  For instance >> Good  Autosuspend for unknown USB device 1-7 
(a1b2:c3d4) 
- In /etc/tlp.conf, add a line with USB_BLACKLIST="a1b2:c3d4"
- restart tlp (systemctl restart tlp)

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity, but
  btusb.enable_autosuspend=0 fixes it

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+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 1980883] Re: screen randomy goes black then auto recover in 2-5 seconds, with frequency of every few seconds to minutes

2022-08-01 Thread Joan

Upgraded to 19.0, as expected, problem remains the same.

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

Title:
  screen randomy goes black then auto recover in 2-5 seconds, with
  frequency of every few seconds to minutes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  5.15.0-40-generic #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022 x86_64
  x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-40-generic 5.15.0-40.43
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yiqun  1016 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 19:16:23 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 
4000 V1.0
   Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge T30
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic 
root=UUID=61217789-7a38-41ab-b49a-6a3d41ff427c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-40-generic N/A
   linux-backports-modules-5.15.0-40-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 07T4MC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd03/29/2022:br1.9:svnDellInc.:pnPowerEdgeT30:pvr:rvnDellInc.:rn07T4MC:rvrA07:cvnDellInc.:ct6:cvr:sku07C5:
  dmi.product.name: PowerEdge T30
  dmi.product.sku: 07C5
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980883/+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 1974433] Re: [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16

2022-08-01 Thread bugproxy

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004

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

Title:
  [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new
  IBM z16

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

   * This is a hardware enablement SRU

   * and adds support for (new) IBM z16 counters

   * by exporting the extended counter set counters of the IBM z16 via
  sysfs.

  [Fix]

   * c9311de71635 c9311de71635d3eaa158df8516b9b99a92d60a0c
     "s390/cpumf: add new extended counter set for IBM z16"

  [Test Case]

   * Prepare an IBM z16 LPAR with Ubuntu 20.04, 21.10 or 22.04 (incl.
  this patch).

   * At LPARs activation profile, navigate to the Security page
     and within the counter facility options, select each counter set you want 
to use.
     (One may just select all for testing purposes.)

   * Use 'perf list' to determine if the new counters are listed.
     For comparing the new counters see:
     https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git\
     /commit/?id=c9311de71635d3eaa158df8516b9b99a92d60a0c

   * Use 'perf stat -e' to enable and make use of these counters.

  [What can go wrong]

   * Only new code is added by this commit - none is changed nor
  removed.

   * The new code may have syntactical errors,
     which would become visible during a test compile.

   * Initialization of the new struct cpumcf_z16_pmu_event_attr could be
  wrong.

   * The hex code for the counters could be wrong or mixed up,
     or the names might be wrong or mixed up,
     in which case one will get wrong or unexpected results.

   * The expansion of the case statement to determine the correct (z16) hardware
     might be wrong, using wrong case hex numbers.
     Which would lead to potentially counters,
     that may not match to the underlying hardware.

  [ Other info]

   * The commit will be upstream accepted with 5.18.
 (It's was brought upstream 'next-20220517'.)

   * Since the planned target kernel for kinetic is 5.19,
 this will be included.

   * Hence the SRU is for Focal, Impish and Jammy only.

  __

  For IBM z16 machine the extended counter set needs to be exported by the PMU 
device driver CPU MF. The upstream commit from linux-next is
  commit-id: c9311de71635 s390/cpumf: add new extended counter set for IBM z16

  The same patch will be imported into linux repo in the next merge
  window.

  Required patches are attached. They apply cleanly and compile without
  errors on focal (20.04) and jammy (22.04).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1974433/+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 1982930] Re: ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in Focal

2022-08-01 Thread Kleber Sacilotto de Souza

Patch resent: https://lore.kernel.org/linux-
kselftest/20220801124615.256416-1-kleber.so...@canonical.com/

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

Title:
  ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels
  in Focal

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  Testcase ubuntu_kernel_selftests.net:ioam6.sh fails in Focal with the 5.15 
kernels with the following errors:

  17:19:35 DEBUG| [stdout] make: Entering directory 
'/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/cl
  ient/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
  17:19:35 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. 
headers_install
  17:19:35 DEBUG| [stdout] make[1]: Entering directory 
'/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  17:19:35 DEBUG| [stdout]   INSTALL ./usr/include
  17:19:35 DEBUG| [stdout] make[1]: Leaving directory 
'/tmp/autopkgtest.WSxPqj/build.GQs/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  17:19:35 DEBUG| [stdout] TAP version 13
  17:19:35 DEBUG| [stdout] 1..1
  17:19:35 DEBUG| [stdout] # selftests: net: ioam6.sh
  17:19:35 DEBUG| [stdout] # SKIP: iproute2 too old, missing ioam command
  17:19:35 DEBUG| [stdout] not ok 1 selftests: net: ioam6.sh # exit=1

  This is caused by an older version of iproute2 in Focal. The package
  has been updated in Jammy via bug 1951390 and the bug report says it
  should be updated in Focal as well. Even if the package is eventually
  updated, the testcase shouldn't throw a fatal error in this case and
  really return "SKIP" as the log message says.

  [Fix]
  The proper fix would be to make tools/testing/selftests/net/ioam6.sh return 
the Kselftest framework proper skip code instead of failing.

  [Testcase]
  Run the selftest script in Focal with a 5.15 kernel.

  [Where problems could occur]
  If the skip code is added to places where it shouldn't be added it could 
introduce false positives and not fail where it should.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1982930/+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 1956849] Re: Almost all USB ports suddenly stopped working; unbootable

2022-08-01 Thread Jazz

I no longer have the issue with 5.13.0-52-generic, looks like something
was fixed.

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

Title:
  Almost all USB ports suddenly stopped working; unbootable

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This package needs to be pulled NOW.  It disables almost all USB-3.0
  and USB-C ports completely.

  Even though I had automatic software updates turned OFF (or so I
  thought), my Mac Pro suddenly got a new kernel when I rebooted it this
  morning:

  Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14
  15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  and it contains a P0 showstopper bug.  Upon rebooting, I got dropped
  into the initrd prompt because Linux could not see the external USB
  drive that I'm booting from (WDBAGF5000AGY-WESN).

  I wasted an entire day figuring out what was wrong, and even went so
  far as to order a replacement SSD, planning to rebuild everything from
  scratch, because the drive failed to appear in every single USB port I
  tried.

  Then I discovered that a different SSD didn't work, either.  At that
  point, I realized that something else was wrong, and I kept trying
  until I found one other port that worked.  I was then able to boot and
  get dmesg and lsusb output.

  This kernel update broke not only the built-in ports, but also the
  ports on a generic USB-C PCIe card (Amazon B08PF8XR73).

  Mac Pro built-in USB-3.0(A) ports (2x): working
  Mac Pro built-in USB-C ports (4x): dead
  USB-C PCIe card USB-C ports (2x): dead
  USB-C PCIe card USB-3.0(A) ports (5x): dead

  All devices fail to appear in lsusb when attached to the port,
  including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD
  SSD, and a Sandisk SSD.

  I'm going to roll back my kernel to a working kernel, but this package
  needs to be pulled NOW before it affects too many people.  This is too
  catastrophic a bug to wait even a day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+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 1981864] Re: Jammy update: v5.15.46 upstream stable release

Skipped because already applied for CVE-2022-29900 / CVE-2022-29901
* objtool: Fix objtool regression on x32 systems
* objtool: Fix symbol creation

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-29900

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-29901

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

Title:
  Jammy update: v5.15.46 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  In Progress

Bug description:
  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.46 upstream stable release
     from git://git.kernel.org/

  binfmt_flat: do not stop relocating GOT entries prematurely on riscv
  parisc/stifb: Implement fb_is_primary_device()
  parisc/stifb: Keep track of hardware path of graphics card
  RISC-V: Mark IORESOURCE_EXCLUSIVE for reserved mem instead of IORESOURCE_BUSY
  riscv: Initialize thread pointer before calling C functions
  riscv: Fix irq_work when SMP is disabled
  riscv: Wire up memfd_secret in UAPI header
  riscv: Move alternative length validation into subsection
  ALSA: hda/realtek - Add new type for ALC245
  ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop
  ALSA: hda/realtek - Fix microphone noise on ASUS TUF B550M-PLUS
  ALSA: usb-audio: Cancel pending work at closing a MIDI substream
  USB: serial: option: add Quectel BG95 modem
  USB: new quirk for Dell Gen 2 devices
  usb: isp1760: Fix out-of-bounds array access
  usb: dwc3: gadget: Move null pinter check to proper place
  usb: core: hcd: Add support for deferring roothub registration
  fs/ntfs3: Update valid size if -EIOCBQUEUED
  fs/ntfs3: Fix fiemap + fix shrink file size (to remove preallocated space)
  fs/ntfs3: Keep preallocated only if option prealloc enabled
  fs/ntfs3: Check new size for limits
  fs/ntfs3: In function ntfs_set_acl_ex do not change inode->i_mode if called 
from function ntfs_init_acl
  fs/ntfs3: Fix some memory leaks in an error handling path of 'log_replay()'
  fs/ntfs3: Update i_ctime when xattr is added
  fs/ntfs3: Restore ntfs_xattr_get_acl and ntfs_xattr_set_acl functions
  cifs: fix potential double free during failed mount
  cifs: when extending a file with falloc we should make files not-sparse
  xhci: Allow host runtime PM as default for Intel Alder Lake N xHCI
  platform/x86: intel-hid: fix _DSM function index handling
  x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails
  perf/x86/intel: Fix event constraints for ICL
  x86/kexec: fix memory leak of elf header buffer
  x86/sgx: Set active memcg prior to shmem allocation
  ptrace/um: Replace PT_DTRACE with TIF_SINGLESTEP
  ptrace/xtensa: Replace PT_SINGLESTEP with TIF_SINGLESTEP
  ptrace: Reimplement PTRACE_KILL by always sending SIGKILL
  btrfs: add "0x" prefix for unsupported optional features
  btrfs: return correct error number for __extent_writepage_io()
  btrfs: repair super block num_devices automatically
  btrfs: fix the error handling for submit_extent_page() for btrfs_do_readpage()
  iommu/vt-d: Add RPLS to quirk list to skip TE disabling
  drm/vmwgfx: validate the screen formats
  drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes
  selftests/bpf: Fix vfs_link kprobe definition
  selftests/bpf: Fix parsing of prog types in UAPI hdr for bpftool sync
  mwifiex: add mutex lock for call in mwifiex_dfs_chan_sw_work_queue
  b43legacy: Fix assigning negative value to unsigned variable
  b43: Fix assigning negative value to unsigned variable
  ipw2x00: Fix potential NULL dereference in libipw_xmit()
  ipv6: fix locking issues with loops over idev->addr_list
  fbcon: Consistently protect deferred_takeover with console_lock()
  x86/platform/uv: Update TSC sync state for UV5
  ACPICA: Avoid cache flush inside virtual machines
  mac80211: minstrel_ht: fix where rate stats are stored (fixes debugfs output)
  drm/komeda: return early if drm_universal_plane_init() fails.
  drm/amd/display: Disabling Z10 on DCN31
  rcu-tasks: Fix race in schedule and flush work
  rcu: Make TASKS_RUDE_RCU select IRQ_WORK
  sfc: ef10: Fix assigning negative value to unsigned variable
  ALSA: jack: Access input_dev under mutex
  spi: spi-rspi: Remove setting {src,dst}_{addr,addr_width} based on DMA 
direction
  tools/power turbostat: fix ICX DRAM power numbers
  scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg()
  scsi: lpfc: Fix SCSI I/O completion and abort

[Kernel-packages] [Bug 1981809] Re: DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode

2022-08-01 Thread atactic

I fear I do not even get to that point. 
As said: blinking cursor. 
The black screen is a well known issue with NVIDIA drivers on 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/1981809

Title:
  DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode,
  remains on all time. Have switched from legacy NVIDIA drivers to
  Nouveau drivers, from Wayland to xorg but with no change in behaviour.

  $ inxi -F -v 7
  System:
Host: nicolas-XPS-15-7590 Kernel: 5.15.0-41-generic x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME 42.2 tk: GTK 3.24.33 wm: 
gnome-shell
  dm: GDM3 42.0 Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
  Machine:
Type: Laptop System: Dell product: XPS 15 7590 v: N/A
  serial:  Chassis: type: 10 serial: 
Mobo: Dell model: 0T8KGX v: A00 serial:  UEFI: Dell
  v: 1.17.0 date: 04/19/2022
  Battery:
ID-1: BAT0 charge: 36.9 Wh (50.0%) condition: 73.8/97.0 Wh (76.1%)
  volts: 12.4 min: 11.4 model: SMP DELL GPM0365 type: Li-ion serial: 3663
  status: Charging
Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse
  serial: 406b-27-b4-17-46 charge: 100% (should be ignored) rechargeable: 
yes
  status: Discharging
  Memory:
RAM: total: 31 GiB used: 9.11 GiB (29.4%)
RAM Report:
  permissions: Unable to run dmidecode. Root privileges required.
  CPU:
Info: 8-core model: Intel Core i9-9980HK bits: 64 type: MT MCP smt: enabled
  arch: Coffee Lake rev: D cache: L1: 512 KiB L2: 2 MiB L3: 16 MiB
Speed (MHz): avg: 1670 high: 3335 min/max: 800/5000 cores: 1: 2109
  2: 3335 3: 1400 4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 9: 1400 10: 1400
  11: 2107 12: 1853 13: 1700 14: 1630 15: 1400 16: 1400 bogomips: 76800
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
  arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
  clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
  dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
  fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
  ibrs_enhanced ida intel_pt invpcid invpcid_single lahf_lm lm mca mce
  md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe
  pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand
  rdseed rdtscp rep_good sdbg sep sgx sgx_lc smap smep ss ssbd sse sse2
  sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
  tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt
  xsaves xtopology xtpr
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell
  driver: i915 v: kernel ports: active: eDP-1 empty: DP-1,DP-2,DP-3
  bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q]
  vendor: Hewlett-Packard driver: nouveau v: kernel pcie: speed: 8 GT/s
  lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f91 class-ID: 0302
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
  bus-ID: 1-12:6 chip-ID: 0c45:6723 class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.3 compositor: gnome-shell driver: X:
  loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0
  screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5")
  s-diag: 1165mm (45.9")
Monitor-1: eDP-1 model: Samsung res: 3840x2160 hz: 60 dpi: 284
  size: 344x194mm (13.5x7.6") diag: 395mm (15.5") modes: 3840x2160
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 22.0.1 direct render: Yes
  Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Sound Server-1: ALSA v: k5.15.0-41-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Wi-Fi 6 AX200 vendor: Rivet Networks Killer™
  driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 3b:00.0
  chip-ID: 8086:2723 class-ID: 0280
IF: wlp59s0 state: down mac: 90:78:41:22:66:d6
Device-2: Ralink RT2870/RT3070 Wireless Adapter type: USB
  driver: rt2800usb bus-ID: 1-2:3 chip-ID: 148f:3070 class-ID: 
  serial: 1.0
IF: wlx00c0ca5a5edc state: up mac: 00:c0:ca:5a:5e:dc
IP v4: 192.168.1.32/24 type: dynamic noprefixroute scope: global
  broadcast: 192.168.1.255
IP v6: 2a01:cb08:8458:be00:6da9:bb6d:6d13:9a9e/64 type: temporary dynamic
  scope: global
IP v6: 2a01:cb08:8458:be00:82bb:6367:ae9e:5cab/64
  type: dynamic mngtmpaddr noprefixroute scope: global
IP v6:

[Kernel-packages] [Bug 1981862] Re: Jammy update: v5.15.45 upstream stable release

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

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

Title:
  Jammy update: v5.15.45 upstream stable release

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

Bug description:
  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.45 upstream stable release
     from git://git.kernel.org/

  ALSA: usb-audio: Don't get sample rate for MCT Trigger 5 USB-to-HDMI
  pinctrl: sunxi: fix f1c100s uart2 function
  KVM: arm64: Don't hypercall before EL2 init
  percpu_ref_init(): clean ->percpu_count_ref on failure
  net: af_key: check encryption module availability consistency
  nfc: pn533: Fix buggy cleanup order
  net: ftgmac100: Disable hardware checksum on AST2600
  i2c: ismt: Provide a DMA buffer for Interrupt Cause Logging
  drivers: i2c: thunderx: Allow driver to work with ACPI defined TWSI 
controllers
  i2c: ismt: prevent memory corruption in ismt_access()
  assoc_array: Fix BUG_ON during garbage collect
  pipe: make poll_usage boolean and annotate its access
  pipe: Fix missing lock in pipe_resize_ring()
  net: ipa: compute proper aggregation limit
  drm/i915: Fix -Wstringop-overflow warning in call to intel_read_wm_latency()
  exfat: check if cluster num is valid
  lib/crypto: add prompts back to crypto libraries
  crypto: drbg - prepare for more fine-grained tracking of seeding state
  crypto: drbg - track whether DRBG was seeded with !rng_is_initialized()
  crypto: drbg - move dynamic ->reseed_threshold adjustments to __drbg_seed()
  crypto: drbg - make reseeding from get_random_bytes() synchronous
  netfilter: nf_tables: hold mutex on netns pre_exit path
  netfilter: nf_tables: double hook unregistration in netns path
  netfilter: conntrack: re-fetch conntrack after insertion
  KVM: PPC: Book3S HV: fix incorrect NULL check on list iterator
  x86/kvm: Alloc dummy async #PF token outside of raw spinlock
  x86, kvm: use correct GFP flags for preemption disabled
  KVM: x86: avoid calling x86 emulator without a decoded instruction
  KVM: x86: Drop WARNs that assert a triple fault never "escapes" from L2
  KVM: SVM: Use kzalloc for sev ioctl interfaces to prevent kernel data leak
  crypto: caam - fix i.MX6SX entropy delay value
  crypto: ecrdsa - Fix incorrect use of vli_cmp
  zsmalloc: fix races between asynchronous zspage free and page migration
  ALSA: usb-audio: Workaround for clock setup on TEAC devices
  ALSA: usb-audio: Add missing ep_idx in fixed EP quirks
  ALSA: usb-audio: Configure sync endpoints before data
  Bluetooth: hci_qca: Use del_timer_sync() before freeing
  ARM: dts: s5pv210: Correct interrupt name for bluetooth in Aries
  dm integrity: fix error code in dm_integrity_ctr()
  dm crypt: make printing of the key constant-time
  dm stats: add cond_resched when looping over entries
  dm verity: set DM_TARGET_IMMUTABLE feature flag
  raid5: introduce MD_BROKEN
  fs/ntfs3: validate BOOT sectors_per_clusters
  HID: multitouch: Add support for Google Whiskers Touchpad
  HID: multitouch: add quirks to enable Lenovo X12 trackpoint
  x86/sgx: Disconnect backing page references from dirty status
  x86/sgx: Mark PCMD page as dirty when modifying contents
  x86/sgx: Obtain backing storage page with enclave mutex held
  x86/sgx: Fix race between reclaimer and page fault handler
  x86/sgx: Ensure no data in PCMD page after truncate
  media: i2c: imx412: Fix reset GPIO polarity
  media: i2c: imx412: Fix power_off ordering
  tpm: Fix buffer access in tpm2_get_tpm_pt()
  tpm: ibmvtpm: Correct the return value in tpm_ibmvtpm_probe()
  docs: submitting-patches: Fix crossref to 'The canonical patch format'
  NFS: Memory allocation failures are not server fatal errors
  NFSD: Fix possible sleep during nfsd4_release_lockowner()
  bpf: Fix potential array overflow in bpf_trampoline_get_progs()
  bpf: Enlarge offset check value to INT_MAX in bpf_skb_{load,store}_bytes
  bpf: Fix excessive memory allocation in stack_map_alloc()
  bpf: Reject writes for PTR_TO_MAP_KEY in check_helper_mem_access
  bpf: Check PTR_TO_MEM | MEM_RDONLY in check_helper_mem_access
  ALSA: usb-audio: Optimize TEAC clock quirk
  Linux 5.15.45
  UBUNTU: Upstream stable to v5.15.45

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


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

[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)

2022-08-01 Thread AceLan Kao

** Description changed:

+ [Impact]
+ E820 reserved retire memory window, and make other hot-added devices unable 
to get the required memory window.
+ 
+ [Fix]
+ It only can be fixed by a list of quirk to mark those machines out, and 
requires below commits from v5.19-rc1 and v5.19-rc3
+ 
+ a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 
regions"
+ d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
+ fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved 
regions
+ 4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
+ 31bf0f433325 x86: Log resource clipping for E820 regions
+ 93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
+ 
+ [Test]
+ Verified by the bug reporter.
+ 
+ [Where problems could occur]
+ The 6 commits are all clean cherry-picked, and the sixth commit reverts the 
third commit which are the 2 commits that do real functional changes.
+ a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for 
E820 regions\"")
+ 4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
+ The fourth and and fifth commits introduce a new quirk to ignore E820 
reserved regions and the quirk only affects the listed machines.
+ Drivers that operates E820 table may fail if we ignore the E820 regions, but 
it should have no impact on the listed consumer PCs.
+ 
+ ===
+ 
  Touchpad is not working at all on ACER Spin 5 SP513-54N.
  
  According to
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
  I am creating this kernel bug issue.
  
  There are more issues, too, like touchscreen not working and Ubuntu not
  installable - see here if interrested
  https://askubuntu.com/questions/1251719/
  
  I would like to run Ubuntu on this machine and I am willing to help with
  any debug or kernel tweaking... Please let me know.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ubuntu 4195 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 4195 F pulseaudio
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 10:44:58 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-26-generic N/A
-  linux-backports-modules-5.4.0-26-generic  N/A
-  linux-firmware1.187
+  linux-restricted-modules-5.4.0-26-generic N/A
+  linux-backports-modules-5.4.0-26-generic  N/A
+  linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.00
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.00
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.00
  dmi.sys.vendor: Acer

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

Title:
  touchpad and touchscreen doesn't work at all on ACER Spin 5
  (SP513-54N)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Won't Fix
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  E820 reserved retire memory window, and make other hot-added devices unable 
to get the required memory window.

  [Fix]
  It only can be fixed by a list of quirk to mark those machines out, and 
requires below commits from v5.19-rc1 and v5.19-rc3

  a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 
regions"
  d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
  fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore

[Kernel-packages] [Bug 1981468] Re: Jammy update: v5.15.43 upstream stable release

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

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

Title:
  Jammy update: v5.15.43 upstream stable release

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

Bug description:
  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.43 upstream stable release
  (Note: This patchset contains just one upstream patch.)
     from git://git.kernel.org/

  mptcp: Do TCP fallback on early DSS checksum failure
  Linux 5.15.43
  UBUNTU: Upstream stable to v5.15.43

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981468/+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 1981649] Re: Jammy update: v5.15.44 upstream stable release

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

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

Title:
  Jammy update: v5.15.44 upstream stable release

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

Bug description:
  
  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.44 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981649/+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 1981375] Re: Jammy update: v5.15.42 upstream stable release

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

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

Title:
  Jammy update: v5.15.42 upstream stable release

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

Bug description:
  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.42 upstream stable release
     from git://git.kernel.org/

  usb: gadget: fix race when gadget driver register via ioctl
  io_uring: arm poll for non-nowait files
  kernel/resource: Introduce request_mem_region_muxed()
  i2c: piix4: Replace hardcoded memory map size with a #define
  i2c: piix4: Move port I/O region request/release code into functions
  i2c: piix4: Move SMBus controller base address detect into function
  i2c: piix4: Move SMBus port selection into function
  i2c: piix4: Add EFCH MMIO support to region request and release
  i2c: piix4: Add EFCH MMIO support to SMBus base address detect
  i2c: piix4: Add EFCH MMIO support for SMBus port select
  i2c: piix4: Enable EFCH MMIO for Family 17h+
  Watchdog: sp5100_tco: Move timer initialization into function
  Watchdog: sp5100_tco: Refactor MMIO base address initialization
  Watchdog: sp5100_tco: Add initialization using EFCH MMIO
  Watchdog: sp5100_tco: Enable Family 17h+ CPUs
  mm/kfence: reset PG_slab and memcg_data before freeing __kfence_pool
  Revert "drm/i915/opregion: check port number bounds for SWSCI display power 
state"
  rtc: fix use-after-free on device removal
  rtc: pcf2127: fix bug when reading alarm registers
  um: Cleanup syscall_handler_t definition/cast, fix warning
  Input: add bounds checking to input_set_capability()
  Input: stmfts - fix reference leak in stmfts_input_open
  nvme-pci: add quirks for Samsung X5 SSDs
  gfs2: Disable page faults during lockless buffered reads
  rtc: sun6i: Fix time overflow handling
  crypto: stm32 - fix reference leak in stm32_crc_remove
  crypto: x86/chacha20 - Avoid spurious jumps to other functions
  s390/traps: improve panic message for translation-specification exception
  s390/pci: improve zpci_dev reference counting
  vhost_vdpa: don't setup irq offloading when irq_num < 0
  tools/virtio: compile with -pthread
  nvmet: use a private workqueue instead of the system workqueue
  nvme-multipath: fix hang when disk goes live over reconnect
  rtc: mc146818-lib: Fix the AltCentury for AMD platforms
  fs: fix an infinite loop in iomap_fiemap
  MIPS: lantiq: check the return value of kzalloc()
  drbd: remove usage of list iterator variable after loop
  platform/chrome: cros_ec_debugfs: detach log reader wq from devm
  ARM: 9191/1: arm/stacktrace, kasan: Silence KASAN warnings in unwind_frame()
  nilfs2: fix lockdep warnings in page operations for btree nodes
  nilfs2: fix lockdep warnings during disk space reclamation
  ALSA: usb-audio: Restore Rane SL-1 quirk
  ALSA: wavefront: Proper check of get_user() error
  ALSA: hda/realtek: Add quirk for TongFang devices with pop noise
  perf: Fix sys_perf_event_open() race against self
  selinux: fix bad cleanup on error in hashtab_duplicate()
  Fix double fget() in vhost_net_set_backend()
  PCI/PM: Avoid putting Elo i2 PCIe Ports in D3cold
  Revert "can: m_can: pci: use custom bit timings for Elkhart Lake"
  KVM: x86/mmu: Update number of zapped pages even if page list is stable
  arm64: paravirt: Use RCU read locks to guard stolen_time
  arm64: mte: Ensure the cleared tags are visible before setting the PTE
  crypto: qcom-rng - fix infinite loop on requests not multiple of WORD_SZ
  libceph: fix potential use-after-free on linger ping and resends
  drm/i915/dmc: Add MMIO range restrictions
  drm/dp/mst: fix a possible memory leak in fetch_monitor_name()
  dma-buf: fix use of DMA_BUF_SET_NAME_{A,B} in userspace
  dma-buf: ensure unique directory name for dmabuf stats
  ARM: dts: aspeed-g6: remove FWQSPID group in pinctrl dtsi
  pinctrl: pinctrl-aspeed-g6: remove FWQSPID group in pinctrl
  ARM: dts: aspeed-g6: fix SPI1/SPI2 quad pin group
  ARM: dts: aspeed: Add ADC for AST2600 and enable for Rainier and Everest
  ARM: dts: aspeed: Add secure boot controller node
  ARM: dts: aspeed: Add video engine to g6
  pinctrl: mediatek: mt8365: fix IES control pins
  ALSA: hda - fix unused Realtek function when PM is not enabled
  net: ipa: record proper RX transaction count
  net: macb: Increment rx bd head after allocating skb and buffer
  xfrm: rework default policy

[Kernel-packages] [Bug 1967924] Re: re-apply missing overlayfs SAUCE patch

2022-08-01 Thread Dmitry Trofimov

cat /boot/config-$(uname -r) | grep AUFS
# CONFIG_AUFS_FS is not set

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen

2022-08-01 Thread Hadmut Danisch

Oh ... YES. :-)

At least at the relevant parts.

- X11 good with -40 and -43 :-)
- boot time text console good
- but console after X11 (when shutting down) still shows some jumping effect
- even after removing the nosplash option, I still get the text console instead 
of graphical splash at boot time

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

Title:
  [Medion Akoya E3223] Latest kernel breaks LCD screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just installed Lubuntu 22.04 on a brandnew notebook, and everything
  was working well until rebooting after update:

  Both the boot splash and the X11 screens are jumping and appear
  instable afer a few seconds, as out of sync and running through. It
  absolutely looks like a hardware problem like a broken LCD connector
  cable,  but it isn't: booting fresh from the Lubuntu usb stick and
  evernything works. I have a second machine, exactly same model and
  installation procedure, which was working well for some weeks and had
  exactly the same problem after upgrading.

  disabling the boot splash did not help.

  But booting into the older vmlinuz-5.15.0-25-generic , that came with
  the Lubuntu installation iso file, instead of the latest
  vmlinuz-5.15.0-41-generic solved the problem. With the older kernel,
  everything is stable and fine.

  So between the 25 and the 41 revision of the kernel there came
  something in which reliably breaks the screen configuration on both my
  two notebooks of identical hardware.

  Both the X11 login screen and the desktop do work normally for about
  five seconds and then start running through like one of these old days
  analog screens when out of sync or a cable not plugged in correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 1857 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Jul 21 12:28:31 2022
  InstallationDate: Installed on 2022-07-20 (0 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDION E3223
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet 
cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb
 root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GeminiLake_YS13GR_V3.0.2
  dmi.board.asset.tag: Default string
  dmi.board.name: YS13GR
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: GD7387P
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549:
  dmi.product.family: Akoya
  dmi.product.name: E3223
  dmi.product.sku: ML-241006 30032549
  dmi.product.version: ELAN
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen

Does kernel parameter 'intel_iommu=on' help?

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

Title:
  [Medion Akoya E3223] Latest kernel breaks LCD screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just installed Lubuntu 22.04 on a brandnew notebook, and everything
  was working well until rebooting after update:

  Both the boot splash and the X11 screens are jumping and appear
  instable afer a few seconds, as out of sync and running through. It
  absolutely looks like a hardware problem like a broken LCD connector
  cable,  but it isn't: booting fresh from the Lubuntu usb stick and
  evernything works. I have a second machine, exactly same model and
  installation procedure, which was working well for some weeks and had
  exactly the same problem after upgrading.

  disabling the boot splash did not help.

  But booting into the older vmlinuz-5.15.0-25-generic , that came with
  the Lubuntu installation iso file, instead of the latest
  vmlinuz-5.15.0-41-generic solved the problem. With the older kernel,
  everything is stable and fine.

  So between the 25 and the 41 revision of the kernel there came
  something in which reliably breaks the screen configuration on both my
  two notebooks of identical hardware.

  Both the X11 login screen and the desktop do work normally for about
  five seconds and then start running through like one of these old days
  analog screens when out of sync or a cable not plugged in correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 1857 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Jul 21 12:28:31 2022
  InstallationDate: Installed on 2022-07-20 (0 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDION E3223
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet 
cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb
 root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GeminiLake_YS13GR_V3.0.2
  dmi.board.asset.tag: Default string
  dmi.board.name: YS13GR
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: GD7387P
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549:
  dmi.product.family: Akoya
  dmi.product.name: E3223
  dmi.product.sku: ML-241006 30032549
  dmi.product.version: ELAN
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

Ugh, it looks like CONFIG_AUFS_FS is disabled in all branches of jammy
kernel. It means that this fix commit is totally useless. Okay, I'll fix
that too :)

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

Dmitry, couldn't you show:
cat /boot/config-$(uname -r) | grep AUFS
?

5.15 kernel it's master branch, this branch contains corresponding fix:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/tree/fs/overlayfs/file.c?h=master#n493

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen

2022-08-01 Thread Hadmut Danisch

** Attachment added: "dmesg 5.15.0-39"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+attachment/5606282/+files/dmesg_5.15.0-39-generic.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/1982479

Title:
  [Medion Akoya E3223] Latest kernel breaks LCD screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just installed Lubuntu 22.04 on a brandnew notebook, and everything
  was working well until rebooting after update:

  Both the boot splash and the X11 screens are jumping and appear
  instable afer a few seconds, as out of sync and running through. It
  absolutely looks like a hardware problem like a broken LCD connector
  cable,  but it isn't: booting fresh from the Lubuntu usb stick and
  evernything works. I have a second machine, exactly same model and
  installation procedure, which was working well for some weeks and had
  exactly the same problem after upgrading.

  disabling the boot splash did not help.

  But booting into the older vmlinuz-5.15.0-25-generic , that came with
  the Lubuntu installation iso file, instead of the latest
  vmlinuz-5.15.0-41-generic solved the problem. With the older kernel,
  everything is stable and fine.

  So between the 25 and the 41 revision of the kernel there came
  something in which reliably breaks the screen configuration on both my
  two notebooks of identical hardware.

  Both the X11 login screen and the desktop do work normally for about
  five seconds and then start running through like one of these old days
  analog screens when out of sync or a cable not plugged in correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 1857 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Jul 21 12:28:31 2022
  InstallationDate: Installed on 2022-07-20 (0 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDION E3223
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet 
cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb
 root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GeminiLake_YS13GR_V3.0.2
  dmi.board.asset.tag: Default string
  dmi.board.name: YS13GR
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: GD7387P
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549:
  dmi.product.family: Akoya
  dmi.product.name: E3223
  dmi.product.sku: ML-241006 30032549
  dmi.product.version: ELAN
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen

2022-08-01 Thread Hadmut Danisch

** Attachment added: "dmesg 5.15.0-40"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+attachment/5606283/+files/dmesg_5.15.0-40-generic.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/1982479

Title:
  [Medion Akoya E3223] Latest kernel breaks LCD screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just installed Lubuntu 22.04 on a brandnew notebook, and everything
  was working well until rebooting after update:

  Both the boot splash and the X11 screens are jumping and appear
  instable afer a few seconds, as out of sync and running through. It
  absolutely looks like a hardware problem like a broken LCD connector
  cable,  but it isn't: booting fresh from the Lubuntu usb stick and
  evernything works. I have a second machine, exactly same model and
  installation procedure, which was working well for some weeks and had
  exactly the same problem after upgrading.

  disabling the boot splash did not help.

  But booting into the older vmlinuz-5.15.0-25-generic , that came with
  the Lubuntu installation iso file, instead of the latest
  vmlinuz-5.15.0-41-generic solved the problem. With the older kernel,
  everything is stable and fine.

  So between the 25 and the 41 revision of the kernel there came
  something in which reliably breaks the screen configuration on both my
  two notebooks of identical hardware.

  Both the X11 login screen and the desktop do work normally for about
  five seconds and then start running through like one of these old days
  analog screens when out of sync or a cable not plugged in correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-41-generic 5.15.0-41.44
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 1857 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Thu Jul 21 12:28:31 2022
  InstallationDate: Installed on 2022-07-20 (0 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEDION E3223
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet 
cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb
 root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GeminiLake_YS13GR_V3.0.2
  dmi.board.asset.tag: Default string
  dmi.board.name: YS13GR
  dmi.board.vendor: MEDION
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: GD7387P
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549:
  dmi.product.family: Akoya
  dmi.product.name: E3223
  dmi.product.sku: ML-241006 30032549
  dmi.product.version: ELAN
  dmi.sys.vendor: MEDION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1967924] Re: re-apply missing overlayfs SAUCE patch

2022-08-01 Thread Dmitry Trofimov

Using CRIU on Ubuntu 22.04 gives me the error:

Error (criu/files-reg.c:1710): Can't lookup mount=1273 for fd=-3 
path=/opt/python/bin/python3.8
Error (criu/cr-dump.c:1524): Collect mappings (pid: 70655) failed with -1
Error (criu/cr-dump.c:2053): Dumping FAILED.

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS"


uname -a
Linux traff-desktop 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  re-apply missing overlayfs SAUCE patch

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with 5.13 we've incorrectly dropped the following sauce
  patch:

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  This patch seems to be required to use overlayfs on top of shiftfs and
  without this patch we may break containers that rely on shiftfs (using
  zfs/ceph as storage pool w/ shiftfs enabled).

  [Test case]

  No specific test case provided.

  [Fix]

  The original SAUCE patch relies on AUFS in order to use
  vma->vm_prfile, but we're not providing AUFS anymore in jammy,.

  The fix consists of re-apply this patch with a little refactoring to
  be dependent on CONFIG_AUFS_FS.

  [Regression potential]

  This patch is touching overlayfs, so we may see potential regressions
  in overlayfs.

  [Original bug report]

  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
  from map_files

  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967924/+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 1981809] Re: DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode

Maybe `sudo ubuntu-drivers install`?

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

Title:
  DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode,
  remains on all time. Have switched from legacy NVIDIA drivers to
  Nouveau drivers, from Wayland to xorg but with no change in behaviour.

  $ inxi -F -v 7
  System:
Host: nicolas-XPS-15-7590 Kernel: 5.15.0-41-generic x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME 42.2 tk: GTK 3.24.33 wm: 
gnome-shell
  dm: GDM3 42.0 Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
  Machine:
Type: Laptop System: Dell product: XPS 15 7590 v: N/A
  serial:  Chassis: type: 10 serial: 
Mobo: Dell model: 0T8KGX v: A00 serial:  UEFI: Dell
  v: 1.17.0 date: 04/19/2022
  Battery:
ID-1: BAT0 charge: 36.9 Wh (50.0%) condition: 73.8/97.0 Wh (76.1%)
  volts: 12.4 min: 11.4 model: SMP DELL GPM0365 type: Li-ion serial: 3663
  status: Charging
Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse
  serial: 406b-27-b4-17-46 charge: 100% (should be ignored) rechargeable: 
yes
  status: Discharging
  Memory:
RAM: total: 31 GiB used: 9.11 GiB (29.4%)
RAM Report:
  permissions: Unable to run dmidecode. Root privileges required.
  CPU:
Info: 8-core model: Intel Core i9-9980HK bits: 64 type: MT MCP smt: enabled
  arch: Coffee Lake rev: D cache: L1: 512 KiB L2: 2 MiB L3: 16 MiB
Speed (MHz): avg: 1670 high: 3335 min/max: 800/5000 cores: 1: 2109
  2: 3335 3: 1400 4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 9: 1400 10: 1400
  11: 2107 12: 1853 13: 1700 14: 1630 15: 1400 16: 1400 bogomips: 76800
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
  arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
  clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
  dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
  fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
  ibrs_enhanced ida intel_pt invpcid invpcid_single lahf_lm lm mca mce
  md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe
  pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand
  rdseed rdtscp rep_good sdbg sep sgx sgx_lc smap smep ss ssbd sse sse2
  sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
  tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt
  xsaves xtopology xtpr
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell
  driver: i915 v: kernel ports: active: eDP-1 empty: DP-1,DP-2,DP-3
  bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q]
  vendor: Hewlett-Packard driver: nouveau v: kernel pcie: speed: 8 GT/s
  lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f91 class-ID: 0302
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
  bus-ID: 1-12:6 chip-ID: 0c45:6723 class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.3 compositor: gnome-shell driver: X:
  loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0
  screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5")
  s-diag: 1165mm (45.9")
Monitor-1: eDP-1 model: Samsung res: 3840x2160 hz: 60 dpi: 284
  size: 344x194mm (13.5x7.6") diag: 395mm (15.5") modes: 3840x2160
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 22.0.1 direct render: Yes
  Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Sound Server-1: ALSA v: k5.15.0-41-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Wi-Fi 6 AX200 vendor: Rivet Networks Killer™
  driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 3b:00.0
  chip-ID: 8086:2723 class-ID: 0280
IF: wlp59s0 state: down mac: 90:78:41:22:66:d6
Device-2: Ralink RT2870/RT3070 Wireless Adapter type: USB
  driver: rt2800usb bus-ID: 1-2:3 chip-ID: 148f:3070 class-ID: 
  serial: 1.0
IF: wlx00c0ca5a5edc state: up mac: 00:c0:ca:5a:5e:dc
IP v4: 192.168.1.32/24 type: dynamic noprefixroute scope: global
  broadcast: 192.168.1.255
IP v6: 2a01:cb08:8458:be00:6da9:bb6d:6d13:9a9e/64 type: temporary dynamic
  scope: global
IP v6: 2a01:cb08:8458:be00:82bb:6367:ae9e:5cab/64
  type: dynamic mngtmpaddr noprefixroute scope: global
IP v6: fe80::3298:a4bf:8382:15e9/64 type: noprefixroute scope: link
WAN IP: 92.139.67.225
  Bluetooth:
Device-1:

[Kernel-packages] [Bug 1981554] Re: [Ubuntu-22.04] Video mode is not working with the external monitor

2022-08-01 Thread Gnanendra Kolla

Hello Mr.Jeff Lane,

I have collected the logs and attached as Ubuntu Kernel Bot (ubuntu-kernel-bot)
suggested using
command apport-collect 1981554

** Attachment added: "apport.linux.c1ywpzcg.apport"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+attachment/5606281/+files/apport.linux.c1ywpzcg.apport

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

Title:
[Ubuntu-22.04] Video mode is not working with the external monitor

Status in linux package in Ubuntu:
Incomplete

Bug description:
Description:
The SUT Dell EMC Poweredge R440 can not display video mode with external
monitor when Ubuntu 22.04 boots. The video mode working properly under iDRAC
virtual console.

Steps to Reproduce:
1. Connect External monitor to SUT using VGA cable.
2. Mount ubuntu-22.04-live-server-amd64.iso by iDRAC virtual console.
3. Start to install the OS and click "Try or Install Ubuntu server".
4. The SUT can not display video mode with monitor when OS boots.

Expected Results:
Video mode should work properly when OS boots with external monitor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981554/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

2022-08-01 Thread lotuspsychje

@ Daniel #85

just tested linux-image-5.15.0-41-generic and linux-
image-5.15.0-43-generic

wich both still result in flickering indeed,

5.15.0-40 i tested before in #73

back to 5.17.7-051707-generic #202205121146 to fix

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1983259] [NEW] ACPI BIOS error messages at startup

2022-08-01 Thread Dario Menin

Public bug reported:

At startup, the following lines are printed (they were not present with
the previous kernels):

[0.324533] No Local Variables are initialized for Method [_CPC]

[0.324534] No Arguments are initialized for method [_CPC]

[0.324535] ACPI Error: Aborting method \_SB.PR01._CPC due to previous error 
(AE_NOT_FOUND) (20210730/psparse-529)
[0.324582] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

[0.324587] No Local Variables are initialized for Method [_CPC]

[0.324588] No Arguments are initialized for method [_CPC]

[0.324589] ACPI Error: Aborting method \_SB.PR02._CPC due to previous error 
(AE_NOT_FOUND) (20210730/psparse-529)
[0.324713] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

[0.324719] No Local Variables are initialized for Method [_CPC]

[0.324720] No Arguments are initialized for method [_CPC]

[0.324721] ACPI Error: Aborting method \_SB.PR03._CPC due to previous error 
(AE_NOT_FOUND) (20210730/psparse-529)
[0.324804] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

[0.324809] No Local Variables are initialized for Method [_CPC]

[0.324810] No Arguments are initialized for method [_CPC]

[0.324811] ACPI Error: Aborting method \_SB.PR04._CPC due to previous error 
(AE_NOT_FOUND) (20210730/psparse-529)
[0.324905] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

[0.324911] No Local Variables are initialized for Method [_CPC]

[0.324912] No Arguments are initialized for method [_CPC]

[0.324913] ACPI Error: Aborting method \_SB.PR05._CPC due to previous error 
(AE_NOT_FOUND) (20210730/psparse-529)
[0.324992] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

[0.324998] No Local Variables are initialized for Method [_CPC]

[0.324999] No Arguments are initialized for method [_CPC]

[0.325000] ACPI Error: Aborting method \_SB.PR06._CPC due to previous error 
(AE_NOT_FOUND) (20210730/psparse-529)
[0.325099] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

[0.325106] No Local Variables are initialized for Method [_CPC]

[0.325107] No Arguments are initialized for method [_CPC]

[0.325109] ACPI Error: Aborting method \_SB.PR07._CPC due to
previous error (AE_NOT_FOUND) (20210730/psparse-529)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.15.0-41-generic 5.15.0-41.44~20.04.1
ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  1 11:47:35 2022
InstallationDate: Installed on 2021-06-17 (410 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe-5.15
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: acpi amd64 apport-bug bios focal

** Attachment added: "dmesg log"
   https://bugs.launchpad.net/bugs/1983259/+attachment/5606270/+files/dmesg.log

** Tags added: acpi bios

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

Title:
  ACPI BIOS error messages at startup

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

Bug description:
  At startup, the following lines are printed (they were not present
  with the previous kernels):

  [0.324533] No Local Variables are initialized for Method [_CPC]

  [0.324534] No Arguments are initialized for method [_CPC]

  [0.324535] ACPI Error: Aborting method \_SB.PR01._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.324582] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.324587] No Local Variables are initialized for Method [_CPC]

  [0.324588] No Arguments are initialized for method [_CPC]

  [0.324589] ACPI Error: Aborting method \_SB.PR02._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.324713] ACPI BIOS Error (bug): Could not resolve symbol 
[\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)

  [0.324719] No Local Variables are initialized for Method [_CPC]

  [0.324720] No Arguments are initialized for method [_CPC]

  [0.324721] ACPI Error: Aborting method \_SB.PR03._CPC due to previous 
error (AE_NOT_FOUND) (20210730/psparse-529)
  [0.324804] ACPI

[Kernel-packages] [Bug 1983258] [NEW] package linux-modules-nvidia-470-5.15.0-41-generic 5.15.0-41.44~20.04.1+1 failed to install/upgrade: podproces zainstalowany pakiet linux-modules-nvidia-470-5.15.

2022-08-01 Thread Michał Janowski

Public bug reported:

Could not install 'linux-modules-nvidia-470-5.15.0-41-generic'

The upgrade will continue but the 'linux-modules-
nvidia-470-5.15.0-41-generic' package may not be in a working state.
Please consider submitting a bug report about it.

subprocess installed package linux-modules-nvidia-470-5.15.0-41-generic
post-installation script returned error code 1

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: linux-modules-nvidia-470-5.15.0-41-generic 5.15.0-41.44~20.04.1+1
ProcVersionSignature: Ubuntu 5.13.0-52.59-generic 5.13.19
Uname: Linux 5.13.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu71.2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Aug  1 11:43:43 2022
ErrorMessage: podproces zainstalowany pakiet 
linux-modules-nvidia-470-5.15.0-41-generic skrypt post-installation zwrócił kod 
błędu 1
InstallationDate: Installed on 2022-01-03 (209 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2.2
 apt  2.3.9ubuntu0.1
SourcePackage: linux-restricted-modules-hwe-5.15
Title: package linux-modules-nvidia-470-5.15.0-41-generic 
5.15.0-41.44~20.04.1+1 failed to install/upgrade: podproces zainstalowany 
pakiet linux-modules-nvidia-470-5.15.0-41-generic skrypt post-installation 
zwrócił kod błędu 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-restricted-modules-hwe-5.15 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package impish third-party-packages

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

Title:
  package linux-modules-nvidia-470-5.15.0-41-generic
  5.15.0-41.44~20.04.1+1 failed to install/upgrade: podproces
  zainstalowany pakiet linux-modules-nvidia-470-5.15.0-41-generic skrypt
  post-installation zwrócił kod błędu 1

Status in linux-restricted-modules-hwe-5.15 package in Ubuntu:
  New

Bug description:
  Could not install 'linux-modules-nvidia-470-5.15.0-41-generic'

  The upgrade will continue but the 'linux-modules-
  nvidia-470-5.15.0-41-generic' package may not be in a working state.
  Please consider submitting a bug report about it.

  subprocess installed package linux-modules-
  nvidia-470-5.15.0-41-generic post-installation script returned error
  code 1

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: linux-modules-nvidia-470-5.15.0-41-generic 5.15.0-41.44~20.04.1+1
  ProcVersionSignature: Ubuntu 5.13.0-52.59-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Aug  1 11:43:43 2022
  ErrorMessage: podproces zainstalowany pakiet 
linux-modules-nvidia-470-5.15.0-41-generic skrypt post-installation zwrócił kod 
błędu 1
  InstallationDate: Installed on 2022-01-03 (209 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: /usr/bin/python3.9, Python 3.9.7, python-is-python3, 3.9.2-1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2.2
   apt  2.3.9ubuntu0.1
  SourcePackage: linux-restricted-modules-hwe-5.15
  Title: package linux-modules-nvidia-470-5.15.0-41-generic 
5.15.0-41.44~20.04.1+1 failed to install/upgrade: podproces zainstalowany 
pakiet linux-modules-nvidia-470-5.15.0-41-generic skrypt post-installation 
zwrócił kod błędu 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.15/+bug/1983258/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

2022-08-01 Thread Daniel van Vugt

Based on comment #78, I expect the main task at the top of this bug
should close when kernel 5.19 is (soon) released to Ubuntu 22.10.
Assuming there's no regression in 5.19.

I don't know if or when such a fix will ever reach Ubuntu 22.04 because
we really thought it was the same fix at play in both 5.17.7 and
5.15.0-40. Turns out we need two different fixes, unless...

Can you double check that 5.15.0-40 or 5.15.0-41 still has the bug?

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

2022-08-01 Thread lotuspsychje

@ Daniel #83 thank you!

the last kernel version i tested was 5.15.0-40-generic

please let me know wich kernel version to test next that will inclde the
fix

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

Title:
  [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0
  intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @
  18/1/2022

  Booting into desktop gets heavy screen flickering and disforming (unusable)
  both booting on xorg and wayland

  on kernel 5.13 it did not occur so heavy (only little glitches once in
  a while see bug 1948778)

  adding the kernel paramater intel_idle.max_cstate=4 fixed this

  i had these same bugs on this machine before:

  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644

  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   1201 F pipewire-media-
lotuspsychje   1207 F pulseaudio
   /dev/snd/seq:lotuspsychje   1193 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 04:22:00 2022
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N7x0WU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash 
intel_idle.max_cstate=4 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.release: 7.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N7x0WU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.14
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N7x0WU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode

The patches which introduced the problem are both v5.7 and have not been
backported into v5.4.

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

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

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

Title:
  [SRU] bcache deadlock during read IO in writeback mode

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]

  When Random Read I/O is started with a test like -

  fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G
  --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128
  --rw=randread --randrepeat=0

  or

  random read-writes with a test like,

  fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB
  --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128
  --name=iops-test-job --randrepeat=0

  traces are seen in the kernel log,

  [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 
seconds.
  [ 4474.050921]   Not tainted 5.15.50-051550-generic #202206251445
  [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 
flags:0x4000
  [ 4474.731408] Call Trace:
  [ 4474.731411]  
  [ 4474.731413]  __schedule+0x23d/0x5a0
  [ 4474.731433]  schedule+0x4e/0xb0
  [ 4474.731436]  rwsem_down_write_slowpath+0x220/0x3d0
  [ 4474.731441]  down_write+0x43/0x50
  [ 4474.731446]  bch_writeback_thread+0x78/0x320 [bcache]
  [ 4474.731471]  ? read_dirty_submit+0x70/0x70 [bcache]
  [ 4474.731487]  kthread+0x12a/0x150
  [ 4474.731491]  ? set_kthread_struct+0x50/0x50
  [ 4474.731494]  ret_from_fork+0x22/0x30
  [ 4474.731499]  

  The bug exists till kernel 5.15.50-051550-generic

  The reproducer is pasted below:

  # uname -a
  Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
  sdd   8:48   0 279.4G  0 disk
  └─sdd18:49   060G  0 part
    └─bcache0 252:0060G  0 disk /home/ubuntu/bcache_mount
  nvme0n1 259:00 372.6G  0 disk
  └─nvme0n1p1 259:2015G  0 part
    └─bcache0 252:0060G  0 disk /home/ubuntu/bcache_mount

  fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G 
--ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread 
--group_reporting=1
  read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  fio-3.28
  Starting 1 process
  read_iops: Laying out IO file (1 file / 12288MiB)

  The test does not progress beyond a few minutes, and this trace is
  then seen in the kernel log,

  [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 
seconds.
  [ 4474.050921]   Not tainted 5.15.50-051550-generic #202206251445
  [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 
flags:0x4000
  [ 4474.731408] Call Trace:
  [ 4474.731411]  
  [ 4474.731413]  __schedule+0x23d/0x5a0
  [ 4474.731433]  schedule+0x4e/0xb0
  [ 4474.731436]  rwsem_down_write_slowpath+0x220/0x3d0
  [ 4474.731441]  down_write+0x43/0x50
  [ 4474.731446]  bch_writeback_thread+0x78/0x320 [bcache]
  [ 4474.731471]  ? read_dirty_submit+0x70/0x70 [bcache]
  [ 4474.731487]  kthread+0x12a/0x150
  [ 4474.731491]  ? set_kthread_struct+0x50/0x50
  [ 4474.731494]  ret_from_fork+0x22/0x30
  [ 4474.731499]  

  [Fix]
  These 3 fixes are needed for the SRU.

  dea3560e5f31965165bcf34ecf0b47af28bfd155, 
6445ec3df23f24677064a327dce437ef3e02dc6,
  dc60301fb408e06e0b718c0980cdd31d2b238bee

  I have built these fixes into kernel 5.15.0-39-generic (jammy) and
  tested to verify the problem is fixed.

  [Regression Potential]

  Regression potential should be minimal. I have not seen any potential
  drawbacks or harmful effects of this fix in my testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980925/+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 1981809] Re: DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode

2022-08-01 Thread atactic

I switched to Nouveau driver because i had some temperature events where
one of the two indicators drove up to 100°C and remained there for
minutes.

Now I have reverted back to nVidia and after restart I get again the
blinking cursor at startup, no way to come into the login screen.

Any clues how I could solve this without doing a fresh install?*

*on two machines, any time I faced this issue I could only do a new
install.

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

Title:
  DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode,
  remains on all time. Have switched from legacy NVIDIA drivers to
  Nouveau drivers, from Wayland to xorg but with no change in behaviour.

  $ inxi -F -v 7
  System:
Host: nicolas-XPS-15-7590 Kernel: 5.15.0-41-generic x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME 42.2 tk: GTK 3.24.33 wm: 
gnome-shell
  dm: GDM3 42.0 Distro: Ubuntu 22.04 LTS (Jammy Jellyfish)
  Machine:
Type: Laptop System: Dell product: XPS 15 7590 v: N/A
  serial:  Chassis: type: 10 serial: 
Mobo: Dell model: 0T8KGX v: A00 serial:  UEFI: Dell
  v: 1.17.0 date: 04/19/2022
  Battery:
ID-1: BAT0 charge: 36.9 Wh (50.0%) condition: 73.8/97.0 Wh (76.1%)
  volts: 12.4 min: 11.4 model: SMP DELL GPM0365 type: Li-ion serial: 3663
  status: Charging
Device-1: hidpp_battery_0 model: Logitech M585/M590 Multi-Device Mouse
  serial: 406b-27-b4-17-46 charge: 100% (should be ignored) rechargeable: 
yes
  status: Discharging
  Memory:
RAM: total: 31 GiB used: 9.11 GiB (29.4%)
RAM Report:
  permissions: Unable to run dmidecode. Root privileges required.
  CPU:
Info: 8-core model: Intel Core i9-9980HK bits: 64 type: MT MCP smt: enabled
  arch: Coffee Lake rev: D cache: L1: 512 KiB L2: 2 MiB L3: 16 MiB
Speed (MHz): avg: 1670 high: 3335 min/max: 800/5000 cores: 1: 2109
  2: 3335 3: 1400 4: 1400 5: 1400 6: 1400 7: 1400 8: 1400 9: 1400 10: 1400
  11: 2107 12: 1853 13: 1700 14: 1630 15: 1400 16: 1400 bogomips: 76800
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
  arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
  clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
  dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
  fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs
  ibrs_enhanced ida intel_pt invpcid invpcid_single lahf_lm lm mca mce
  md_clear mmx monitor movbe mpx msr mtrr nonstop_tsc nopl nx pae pat pbe
  pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pts rdrand
  rdseed rdtscp rep_good sdbg sep sgx sgx_lc smap smep ss ssbd sse sse2
  sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
  tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave xsavec xsaveopt
  xsaves xtopology xtpr
  Graphics:
Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] vendor: Dell
  driver: i915 v: kernel ports: active: eDP-1 empty: DP-1,DP-2,DP-3
  bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q]
  vendor: Hewlett-Packard driver: nouveau v: kernel pcie: speed: 8 GT/s
  lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1f91 class-ID: 0302
Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
  bus-ID: 1-12:6 chip-ID: 0c45:6723 class-ID: 0e02
Display: x11 server: X.Org v: 1.21.1.3 compositor: gnome-shell driver: X:
  loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0
  screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5")
  s-diag: 1165mm (45.9")
Monitor-1: eDP-1 model: Samsung res: 3840x2160 hz: 60 dpi: 284
  size: 344x194mm (13.5x7.6") diag: 395mm (15.5") modes: 3840x2160
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  v: 4.6 Mesa 22.0.1 direct render: Yes
  Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Dell driver: snd_hda_intel
  v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Sound Server-1: ALSA v: k5.15.0-41-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
  Network:
Device-1: Intel Wi-Fi 6 AX200 vendor: Rivet Networks Killer™
  driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 3b:00.0
  chip-ID: 8086:2723 class-ID: 0280
IF: wlp59s0 state: down mac: 90:78:41:22:66:d6
Device-2: Ralink RT2870/RT3070 Wireless Adapter type: USB
  driver: rt2800usb bus-ID: 1-2:3 chip-ID: 148f:3070 class-ID: 
  serial: 1.0
IF: wlx00c0ca5a5edc state: up mac: 00:c0:ca:5a:5e:dc
IP v4: 192.168.1.32/24 type: dynamic

[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)

2022-08-01 Thread wilk

I can confirm that with your 5.15.0-1043-generic kernel, touchpad and
touchscreen work without the pci=nocrs kernel parameter. Good job and
thank you.

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

Title:
  touchpad and touchscreen doesn't work at all on ACER Spin 5
  (SP513-54N)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Won't Fix
Status in linux source package in Jammy:
  In Progress

Bug description:
  Touchpad is not working at all on ACER Spin 5 SP513-54N.

  According to
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
  I am creating this kernel bug issue.

  There are more issues, too, like touchscreen not working and Ubuntu
  not installable - see here if interrested
  https://askubuntu.com/questions/1251719/

  I would like to run Ubuntu on this machine and I am willing to help
  with any debug or kernel tweaking... Please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4195 F pulseaudio
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 10:44:58 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.00
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.00
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.00
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+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 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode

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

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

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

Title:
  [SRU] bcache deadlock during read IO in writeback mode

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]

  When Random Read I/O is started with a test like -

  fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G
  --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128
  --rw=randread --randrepeat=0

  or

  random read-writes with a test like,

  fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB
  --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128
  --name=iops-test-job --randrepeat=0

  traces are seen in the kernel log,

  [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 
seconds.
  [ 4474.050921]   Not tainted 5.15.50-051550-generic #202206251445
  [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 
flags:0x4000
  [ 4474.731408] Call Trace:
  [ 4474.731411]  
  [ 4474.731413]  __schedule+0x23d/0x5a0
  [ 4474.731433]  schedule+0x4e/0xb0
  [ 4474.731436]  rwsem_down_write_slowpath+0x220/0x3d0
  [ 4474.731441]  down_write+0x43/0x50
  [ 4474.731446]  bch_writeback_thread+0x78/0x320 [bcache]
  [ 4474.731471]  ? read_dirty_submit+0x70/0x70 [bcache]
  [ 4474.731487]  kthread+0x12a/0x150
  [ 4474.731491]  ? set_kthread_struct+0x50/0x50
  [ 4474.731494]  ret_from_fork+0x22/0x30
  [ 4474.731499]  

  The bug exists till kernel 5.15.50-051550-generic

  The reproducer is pasted below:

  # uname -a
  Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  NAMEMAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
  sdd   8:48   0 279.4G  0 disk
  └─sdd18:49   060G  0 part
    └─bcache0 252:0060G  0 disk /home/ubuntu/bcache_mount
  nvme0n1 259:00 372.6G  0 disk
  └─nvme0n1p1 259:2015G  0 part
    └─bcache0 252:0060G  0 disk /home/ubuntu/bcache_mount

  fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G 
--ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread 
--group_reporting=1
  read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 
4096B-4096B, ioengine=libaio, iodepth=128
  fio-3.28
  Starting 1 process
  read_iops: Laying out IO file (1 file / 12288MiB)

  The test does not progress beyond a few minutes, and this trace is
  then seen in the kernel log,

  [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 
seconds.
  [ 4474.050921]   Not tainted 5.15.50-051550-generic #202206251445
  [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 
flags:0x4000
  [ 4474.731408] Call Trace:
  [ 4474.731411]  
  [ 4474.731413]  __schedule+0x23d/0x5a0
  [ 4474.731433]  schedule+0x4e/0xb0
  [ 4474.731436]  rwsem_down_write_slowpath+0x220/0x3d0
  [ 4474.731441]  down_write+0x43/0x50
  [ 4474.731446]  bch_writeback_thread+0x78/0x320 [bcache]
  [ 4474.731471]  ? read_dirty_submit+0x70/0x70 [bcache]
  [ 4474.731487]  kthread+0x12a/0x150
  [ 4474.731491]  ? set_kthread_struct+0x50/0x50
  [ 4474.731494]  ret_from_fork+0x22/0x30
  [ 4474.731499]  

  [Fix]
  These 3 fixes are needed for the SRU.

  dea3560e5f31965165bcf34ecf0b47af28bfd155, 
6445ec3df23f24677064a327dce437ef3e02dc6,
  dc60301fb408e06e0b718c0980cdd31d2b238bee

  I have built these fixes into kernel 5.15.0-39-generic (jammy) and
  tested to verify the problem is fixed.

  [Regression Potential]

  Regression potential should be minimal. I have not seen any potential
  drawbacks or harmful effects of this fix in my testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980925/+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 1983148] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs

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

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

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

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  This is a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1969247
  because the bug is critical and still not fixed in Ubuntu 20.04.

  Problem: fallocate() called with FALLOC_FL_ZERO_RANGE flag must return
  error on ZFS, but in Ubuntu 20.04 it doesn't return error and just
  creates zero-sized files.

  This causes hard to recover data corruption with MySQL server 8.0.30
  (because it started using fallocate() for redo files). More info here:
  https://bugs.mysql.com/bug.php?id=108012

  Also, I cannot set affected package name as "zfsutils-linux" for some
  reason, but the problem is in zfsutils-linux, not zfs-linux (such
  package doesn't even exist in Ubuntu 20.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.14
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/efi.img
  CasperMD5CheckResult: fail
  Date: Fri Jul 29 21:51:34 2022
  InstallationDate: Installed on 2021-01-21 (554 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=C.UTF-8
   TERM=screen.xterm-256color
   PATH=(custom, no user)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1983148/+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 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC

Thanks a lot! I'll send the patch to upstream based on your test result.

Really appreciated!

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

Title:
  [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
  causes Bus Fatal Error when rebooting system with BCM5720 NIC

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

Bug description:
  SRU Justification:

  [IMPACT]

  This is being reported by a hardware partner as it is being noticed a
  lot both in their internal testing teams and also being reported with
  some frequency by customers who are seeing these messages in their
  logs and thus it is generating an unusualy high volume of support
  calls from the field.

  In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
  upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
  Upstream, these errors were discovered and that patch was reverted
  (see Fix Below).  We carry the revert commit in all subsequent Focal
  HWE kernels starting at 5.12, but the fix was never pulled back into
  Focal 5.4.

  according to the hardware partner:

  the following error messages are observed when rebooting a machine
  that uses the BCM5720 chipset, which is a widely used 1GbE controller
  found on LOMs and OCP NICs as well as many PCIe NIC models.

  [  146.429212] shutdown[1]: Rebooting.
  [  146.435151] kvm: exiting hardware virtualization
  [  146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is 
called outbound_intr_mask:0x4009
  [  148.088133] [qede_unload:2236(eno12409)]Link is down
  [  148.183618] qede :31:00.1: Ending qede_remove successfully
  [  148.518541] [qede_unload:2236(eno12399)]Link is down
  [  148.625066] qede :31:00.0: Ending qede_remove successfully
  [  148.762067] ACPI: Preparing to enter system sleep state S5
  [  148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 5
  [  148.803731] {1}[Hardware Error]: event severity: recoverable
  [  148.810191] {1}[Hardware Error]:  Error 0, type: fatal
  [  148.816088] {1}[Hardware Error]:   section_type: PCIe error
  [  148.822391] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [  148.829026] {1}[Hardware Error]:   version: 3.0
  [  148.834266] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [  148.841140] {1}[Hardware Error]:   device_id: :04:00.0
  [  148.847309] {1}[Hardware Error]:   slot: 0
  [  148.852077] {1}[Hardware Error]:   secondary_bus: 0x00
  [  148.857876] {1}[Hardware Error]:   vendor_id: 0x14e4, device_id: 0x165f
  [  148.865145] {1}[Hardware Error]:   class_code: 02
  [  148.870845] {1}[Hardware Error]:   aer_uncor_status: 0x0010, 
aer_uncor_mask: 0x0001
  [  148.879842] {1}[Hardware Error]:   aer_uncor_severity: 0x000ef030
  [  148.886575] {1}[Hardware Error]:   TLP Header: 4001 030f 90028090 

  [  148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask: 
0x0001
  [  148.902795] tg3 :04:00.0: AER:[20] UnsupReq   (First)
  [  148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer, 
aer_agent=Requester ID
  [  148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
  [  148.925558] tg3 :04:00.0: AER:   TLP Header: 4001 030f 
90028090 
  [  148.933984] reboot: Restarting system
  [  148.938319] reboot: machine restart

  The hardware partner did some bisection and observed the following:

  Kernel  version   Fatal Error
  5.4.0-42.46   No
  5.4.0-45.49   No
  5.4.0-47.51   No
  5.4.0-48.52   No
  5.4.0-51.56   No
  5.4.0-52.57   No
  5.4.0-53.59   No
  5.4.0-54.60   No
  5.4.0-58.64   No
  5.4.0-59.65   yes
  5.4.0-60.67   yes

  [FIX]
  The fix is to apply this patch from upstream:

  commit 9d3fcb28f9b9750b474811a2964ce022df56336e
  Author: Josef Bacik 
  Date:   Tue Mar 16 22:17:48 2021 -0400

  Revert "PM: ACPI: reboot: Use S5 for reboot"

  This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.

  This patch causes a panic when rebooting my Dell Poweredge r440.  I do
  not have the full panic log as it's lost at that stage of the reboot and
  I do not have a serial console.  Reverting this patch makes my system
  able to reboot again.

  Example:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471

  The hardware partner has preemptively pulled our 5.4 tree, applied the
  fix and tested it in their labs and determined that this does resolve
  the issue.

  [TEST CASE]
  Install the patched kernel on a machine that uses a BCM5720 LOM and reboot 
the machine and see that the errors no longer appear.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1983235] Re: ADL: Support for new thermal table

upload debdiff for jammy

** Patch added: "thermald_2.4.9-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1983235/+attachment/5606211/+files/thermald_2.4.9-2ubuntu1.debdiff

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

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

** Changed in: thermald (Ubuntu Jammy)
 Assignee: (unassigned) => koba (kobako)

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

** Changed in: thermald (Ubuntu)
 Assignee: koba (kobako) => (unassigned)

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

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

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] Re: ADL: Support for new thermal table

2022-08-01 Thread Dirk Su

** Changed in: oem-priority
 Assignee: (unassigned) => Dirk Su (dirksu)

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] Re: ADL: Support for new thermal table

2022-08-01 Thread Dirk Su

** Also affects: oem-priority
   Importance: Undecided
   Status: New

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] Re: ADL: Support for new thermal table

2022-08-01 Thread Yuan-Chen Cheng

** Tags added: oem-priority

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] Re: ADL: Support for new thermal table

** Patch added: "thermald_2.4.9-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1983235/+attachment/5606210/+files/thermald_2.4.9-2ubuntu1.debdiff

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

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

** Changed in: thermald (Ubuntu)
 Assignee: (unassigned) => koba (kobako)

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] Re: ADL: Support for new thermal table

** Patch added: "thermald_2.4.9-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1983235/+attachment/5606209/+files/thermald_2.4.9-2ubuntu1.debdiff

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] Re: ADL: Support for new thermal table

** Patch added: "thermald_2.4.9-2ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1983235/+attachment/5606208/+files/thermald_2.4.9-2ubuntu1.debdiff

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1983235] [NEW] ADL: Support for new thermal table

Public bug reported:

[Impact]
 * Support the new thermal table on ADL.

[Test Plan]
 * Use a machine with a ADL.
 * systemctl stop thermald.service and run thermald with --adaptive.
 * Check the log of thermald and the adaptive works.

[Where problems could occur]
 * Becuase RPL is still a engineering sample, there's no any thermal rule from 
acpi,
   Need to check with the formal machine in the future.

** Affects: oem-priority
 Importance: Critical
 Assignee: Dirk Su (dirksu)
 Status: New

** Affects: thermald (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: thermald (Ubuntu Jammy)
 Importance: Critical
 Assignee: koba (kobako)
 Status: In Progress


** Tags: oem-priority

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

Title:
  ADL: Support for new thermal table

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

Bug description:
  [Impact]
   * Support the new thermal table on ADL.

  [Test Plan]
   * Use a machine with a ADL.
   * systemctl stop thermald.service and run thermald with --adaptive.
   * Check the log of thermald and the adaptive works.

  [Where problems could occur]
   * Becuase RPL is still a engineering sample, there's no any thermal rule 
from acpi,
 Need to check with the formal machine in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1983235/+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 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC

2022-08-01 Thread Sujith Pandel

>https://people.canonical.com/~khfeng/tg3-poweroff/

This one does not show the 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/1917471

Title:
  [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
  causes Bus Fatal Error when rebooting system with BCM5720 NIC

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

Bug description:
  SRU Justification:

  [IMPACT]

  This is being reported by a hardware partner as it is being noticed a
  lot both in their internal testing teams and also being reported with
  some frequency by customers who are seeing these messages in their
  logs and thus it is generating an unusualy high volume of support
  calls from the field.

  In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
  upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
  Upstream, these errors were discovered and that patch was reverted
  (see Fix Below).  We carry the revert commit in all subsequent Focal
  HWE kernels starting at 5.12, but the fix was never pulled back into
  Focal 5.4.

  according to the hardware partner:

  the following error messages are observed when rebooting a machine
  that uses the BCM5720 chipset, which is a widely used 1GbE controller
  found on LOMs and OCP NICs as well as many PCIe NIC models.

  [  146.429212] shutdown[1]: Rebooting.
  [  146.435151] kvm: exiting hardware virtualization
  [  146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is 
called outbound_intr_mask:0x4009
  [  148.088133] [qede_unload:2236(eno12409)]Link is down
  [  148.183618] qede :31:00.1: Ending qede_remove successfully
  [  148.518541] [qede_unload:2236(eno12399)]Link is down
  [  148.625066] qede :31:00.0: Ending qede_remove successfully
  [  148.762067] ACPI: Preparing to enter system sleep state S5
  [  148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 5
  [  148.803731] {1}[Hardware Error]: event severity: recoverable
  [  148.810191] {1}[Hardware Error]:  Error 0, type: fatal
  [  148.816088] {1}[Hardware Error]:   section_type: PCIe error
  [  148.822391] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [  148.829026] {1}[Hardware Error]:   version: 3.0
  [  148.834266] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [  148.841140] {1}[Hardware Error]:   device_id: :04:00.0
  [  148.847309] {1}[Hardware Error]:   slot: 0
  [  148.852077] {1}[Hardware Error]:   secondary_bus: 0x00
  [  148.857876] {1}[Hardware Error]:   vendor_id: 0x14e4, device_id: 0x165f
  [  148.865145] {1}[Hardware Error]:   class_code: 02
  [  148.870845] {1}[Hardware Error]:   aer_uncor_status: 0x0010, 
aer_uncor_mask: 0x0001
  [  148.879842] {1}[Hardware Error]:   aer_uncor_severity: 0x000ef030
  [  148.886575] {1}[Hardware Error]:   TLP Header: 4001 030f 90028090 

  [  148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask: 
0x0001
  [  148.902795] tg3 :04:00.0: AER:[20] UnsupReq   (First)
  [  148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer, 
aer_agent=Requester ID
  [  148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
  [  148.925558] tg3 :04:00.0: AER:   TLP Header: 4001 030f 
90028090 
  [  148.933984] reboot: Restarting system
  [  148.938319] reboot: machine restart

  The hardware partner did some bisection and observed the following:

  Kernel  version   Fatal Error
  5.4.0-42.46   No
  5.4.0-45.49   No
  5.4.0-47.51   No
  5.4.0-48.52   No
  5.4.0-51.56   No
  5.4.0-52.57   No
  5.4.0-53.59   No
  5.4.0-54.60   No
  5.4.0-58.64   No
  5.4.0-59.65   yes
  5.4.0-60.67   yes

  [FIX]
  The fix is to apply this patch from upstream:

  commit 9d3fcb28f9b9750b474811a2964ce022df56336e
  Author: Josef Bacik 
  Date:   Tue Mar 16 22:17:48 2021 -0400

  Revert "PM: ACPI: reboot: Use S5 for reboot"

  This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.

  This patch causes a panic when rebooting my Dell Poweredge r440.  I do
  not have the full panic log as it's lost at that stage of the reboot and
  I do not have a serial console.  Reverting this patch makes my system
  able to reboot again.

  Example:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471

  The hardware partner has preemptively pulled our 5.4 tree, applied the
  fix and tested it in their labs and determined that this does resolve
  the issue.

  [TEST CASE]
  Install the patched kernel on a machine that uses a BCM5720 LOM and reboot 
the machine and see that the errors no longer appear.

To manage notifications about this bug go to:

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