[Kernel-packages] [Bug 1961738] Re: UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15

[Daniel van Vugt]

** Tags added: i915

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

Title:
  UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  This seems to happen at boot on all 11th gen Intel systems I've seen.
  But also on a 10th gen Intel system seen in other bug reports.

  [1.778960] 

  [1.778964] UBSAN: shift-out-of-bounds in 
/build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/i915/display/intel_opregion.c:388:15
  [1.778967] shift exponent 37 is too large for 32-bit type 'unsigned int'
  [1.778969] CPU: 5 PID: 374 Comm: systemd-udevd Not tainted 
5.15.0-18-generic #18-Ubuntu
  [1.778970] Hardware name: Microsoft Corporation Surface Laptop 4/Surface 
Laptop 4, BIOS 10.300.141 06/17/2021
  [1.778971] Call Trace:
  [1.778972]  
  [1.778973]  show_stack+0x52/0x58
  [1.778977]  dump_stack_lvl+0x4a/0x5f
  [1.778979]  dump_stack+0x10/0x12
  [1.778980]  ubsan_epilogue+0x9/0x45
  [1.778981]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe9
  [1.778983]  ? icl_ddi_tc_is_clock_enabled+0x4d/0xc0 [i915]
  [1.779060]  intel_opregion_notify_encoder.cold+0x2b/0x45 [i915]
  [1.779129]  intel_sanitize_encoder+0x1e2/0x270 [i915]
  [1.779187]  intel_modeset_setup_hw_state+0x322/0x680 [i915]
  [1.779236]  ? drm_modeset_lock_all_ctx+0x151/0x1c0 [drm]
  [1.779253]  ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0x90 [drm]
  [1.779265]  intel_modeset_init_nogem+0x2a8/0x510 [i915]
  [1.779315]  ? intel_irq_postinstall+0x38b/0x680 [i915]
  [1.779358]  i915_driver_probe+0x1b7/0x470 [i915]
  [1.779395]  ? mutex_lock+0x13/0x40
  [1.779399]  i915_pci_probe+0x58/0x140 [i915]
  [1.779435]  local_pci_probe+0x48/0x90
  [1.779438]  pci_device_probe+0x115/0x1f0
  [1.779439]  really_probe+0x21b/0x420
  [1.779442]  __driver_probe_device+0x115/0x190
  [1.779444]  driver_probe_device+0x23/0xc0
  [1.779445]  __driver_attach+0xbd/0x1d0
  [1.779447]  ? __device_attach_driver+0x110/0x110
  [1.779448]  bus_for_each_dev+0x7c/0xc0
  [1.779450]  driver_attach+0x1e/0x20
  [1.779452]  bus_add_driver+0x135/0x200
  [1.779453]  driver_register+0x95/0xf0
  [1.779454]  __pci_register_driver+0x68/0x70
  [1.779455]  i915_register_pci_driver+0x23/0x30 [i915]
  [1.779488]  i915_init+0x3b/0xfc [i915]
  [1.779534]  ? 0xc1229000
  [1.779535]  do_one_initcall+0x46/0x1d0
  [1.779539]  ? kmem_cache_alloc_trace+0x19e/0x2e0
  [1.779543]  do_init_module+0x62/0x280
  [1.779545]  load_module+0xac9/0xbb0
  [1.779546]  __do_sys_finit_module+0xbf/0x120
  [1.779548]  __x64_sys_finit_module+0x18/0x20
  [1.779549]  do_syscall_64+0x59/0xc0
  [1.779551]  ? do_syscall_64+0x69/0xc0
  [1.779552]  ? do_syscall_64+0x69/0xc0
  [1.779553]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [1.779555] RIP: 0033:0x7f0a61a13a3d
  [1.779557] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c3 53 0f 00 f7 d8 64 89 01 48
  [1.779558] RSP: 002b:7ffcfe9e0748 EFLAGS: 0246 ORIG_RAX: 
0139
  [1.779560] RAX: ffda RBX: 5601776d2090 RCX: 
7f0a61a13a3d
  [1.779561] RDX:  RSI: 7f0a61ba8441 RDI: 
0017
  [1.779561] RBP: 0002 R08:  R09: 
0002
  [1.779562] R10: 0017 R11: 0246 R12: 
7f0a61ba8441
  [1.779562] R13: 5601776cd450 R14: 5601777f7d60 R15: 
5601777f8e30
  [1.779564]  
  [1.779564] 


  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1364 F pipewire-media-
    dan1365 F pulseaudio
   /dev/snd/seq:dan1363 F pipewire
  CasperMD5CheckResult: pass
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error 
executing command as another user: Not authorized

   This incident has been reported.
  Date: Tue Feb 22 15:11:13 2022
  InstallationDate: Installed on 2022-02-14 (8 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220214)
  MachineType: Microsoft Corporation Surface Laptop 4
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=

[Kernel-packages] [Bug 1961121] Re: Not able to enter s2idle state on AMD platforms

[You-Sheng Yang]

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

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

** Changed in: linux-oem-5.14 (Ubuntu Focal)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Alex Hung (alexhung)

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

Title:
  Not able to enter s2idle state on AMD platforms

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

Bug description:
  [Impact]

  AMD Systems don't enter PC6 at runtime and cause failures to enter
  s2idle.

  Currently the fix is from kernel driver rather than MP2 firmware,
  which disable interrupts from kernel driver to fix MP2 firmware
  blocking CPUOFF.

  [Fix]

  The fixes involve 1) cancelling delayed work when entering s0ix and
  re-scheduling it when resuming from s0ix, and 2) clearing interrupts
  during the driver initialization and sensor command operations.

  [Test]

  This is requested by AMD and was tested on AMD CRB.

  [Where problems could occur]

  Risk is low to medium. Some code flow changes are guarded by
  reasonable conditions, but the fixes introduced additional suspend and
  resume operations.

  Having said that, clearing interrupts before driver initialization and
  cancelling work before entering sleeping states are standard
  approaches are usually safe.

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


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

[Kernel-packages] [Bug 1961738] Re: UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15

[Daniel van Vugt]

Fixed upstream it seems:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/i915/display/intel_opregion.c?h=v5.17-rc5&id=ea958422291de248b9e2eaaeea36004e84b64043

** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #4800
   https://gitlab.freedesktop.org/drm/intel/-/issues/4800

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/intel/-/issues/4800
   Importance: Unknown
   Status: Unknown

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

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

** Description changed:

- This seems to happen at boot on all 11th gen Intel systems:
+ This seems to happen at boot on all 11th gen Intel systems I've seen.
+ But also on a 10th gen Intel system seen in other bug reports.
  
  [1.778960] 

  [1.778964] UBSAN: shift-out-of-bounds in 
/build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/i915/display/intel_opregion.c:388:15
  [1.778967] shift exponent 37 is too large for 32-bit type 'unsigned int'
  [1.778969] CPU: 5 PID: 374 Comm: systemd-udevd Not tainted 
5.15.0-18-generic #18-Ubuntu
  [1.778970] Hardware name: Microsoft Corporation Surface Laptop 4/Surface 
Laptop 4, BIOS 10.300.141 06/17/2021
  [1.778971] Call Trace:
  [1.778972]  
  [1.778973]  show_stack+0x52/0x58
  [1.778977]  dump_stack_lvl+0x4a/0x5f
  [1.778979]  dump_stack+0x10/0x12
  [1.778980]  ubsan_epilogue+0x9/0x45
  [1.778981]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe9
  [1.778983]  ? icl_ddi_tc_is_clock_enabled+0x4d/0xc0 [i915]
  [1.779060]  intel_opregion_notify_encoder.cold+0x2b/0x45 [i915]
  [1.779129]  intel_sanitize_encoder+0x1e2/0x270 [i915]
  [1.779187]  intel_modeset_setup_hw_state+0x322/0x680 [i915]
  [1.779236]  ? drm_modeset_lock_all_ctx+0x151/0x1c0 [drm]
  [1.779253]  ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0x90 [drm]
  [1.779265]  intel_modeset_init_nogem+0x2a8/0x510 [i915]
  [1.779315]  ? intel_irq_postinstall+0x38b/0x680 [i915]
  [1.779358]  i915_driver_probe+0x1b7/0x470 [i915]
  [1.779395]  ? mutex_lock+0x13/0x40
  [1.779399]  i915_pci_probe+0x58/0x140 [i915]
  [1.779435]  local_pci_probe+0x48/0x90
  [1.779438]  pci_device_probe+0x115/0x1f0
  [1.779439]  really_probe+0x21b/0x420
  [1.779442]  __driver_probe_device+0x115/0x190
  [1.779444]  driver_probe_device+0x23/0xc0
  [1.779445]  __driver_attach+0xbd/0x1d0
  [1.779447]  ? __device_attach_driver+0x110/0x110
  [1.779448]  bus_for_each_dev+0x7c/0xc0
  [1.779450]  driver_attach+0x1e/0x20
  [1.779452]  bus_add_driver+0x135/0x200
  [1.779453]  driver_register+0x95/0xf0
  [1.779454]  __pci_register_driver+0x68/0x70
  [1.779455]  i915_register_pci_driver+0x23/0x30 [i915]
  [1.779488]  i915_init+0x3b/0xfc [i915]
  [1.779534]  ? 0xc1229000
  [1.779535]  do_one_initcall+0x46/0x1d0
  [1.779539]  ? kmem_cache_alloc_trace+0x19e/0x2e0
  [1.779543]  do_init_module+0x62/0x280
  [1.779545]  load_module+0xac9/0xbb0
  [1.779546]  __do_sys_finit_module+0xbf/0x120
  [1.779548]  __x64_sys_finit_module+0x18/0x20
  [1.779549]  do_syscall_64+0x59/0xc0
  [1.779551]  ? do_syscall_64+0x69/0xc0
  [1.779552]  ? do_syscall_64+0x69/0xc0
  [1.779553]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [1.779555] RIP: 0033:0x7f0a61a13a3d
  [1.779557] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c3 53 0f 00 f7 d8 64 89 01 48
  [1.779558] RSP: 002b:7ffcfe9e0748 EFLAGS: 0246 ORIG_RAX: 
0139
  [1.779560] RAX: ffda RBX: 5601776d2090 RCX: 
7f0a61a13a3d
  [1.779561] RDX:  RSI: 7f0a61ba8441 RDI: 
0017
  [1.779561] RBP: 0002 R08:  R09: 
0002
  [1.779562] R10: 0017 R11: 0246 R12: 
7f0a61ba8441
  [1.779562] R13: 5601776cd450 R14: 5601777f7d60 R15: 
5601777f8e30
  [1.779564]  
  [1.779564] 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  dan1364 F pipewire-media-
-   dan1365 F pulseaudio
-  /dev/snd/seq:dan1363 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  dan1364 F pipewire-media-
+   dan1365 F pulseaud

[Kernel-packages] [Bug 1961738] [NEW] UBSAN: shift-out-of-bounds in .../intel_opregion.c:388:15

[Daniel van Vugt]

Public bug reported:

This seems to happen at boot on all 11th gen Intel systems I've seen.
But also on a 10th gen Intel system seen in other bug reports.

[1.778960] 

[1.778964] UBSAN: shift-out-of-bounds in 
/build/linux-aa0B4d/linux-5.15.0/drivers/gpu/drm/i915/display/intel_opregion.c:388:15
[1.778967] shift exponent 37 is too large for 32-bit type 'unsigned int'
[1.778969] CPU: 5 PID: 374 Comm: systemd-udevd Not tainted 
5.15.0-18-generic #18-Ubuntu
[1.778970] Hardware name: Microsoft Corporation Surface Laptop 4/Surface 
Laptop 4, BIOS 10.300.141 06/17/2021
[1.778971] Call Trace:
[1.778972]  
[1.778973]  show_stack+0x52/0x58
[1.778977]  dump_stack_lvl+0x4a/0x5f
[1.778979]  dump_stack+0x10/0x12
[1.778980]  ubsan_epilogue+0x9/0x45
[1.778981]  __ubsan_handle_shift_out_of_bounds.cold+0x61/0xe9
[1.778983]  ? icl_ddi_tc_is_clock_enabled+0x4d/0xc0 [i915]
[1.779060]  intel_opregion_notify_encoder.cold+0x2b/0x45 [i915]
[1.779129]  intel_sanitize_encoder+0x1e2/0x270 [i915]
[1.779187]  intel_modeset_setup_hw_state+0x322/0x680 [i915]
[1.779236]  ? drm_modeset_lock_all_ctx+0x151/0x1c0 [drm]
[1.779253]  ? drm_warn_on_modeset_not_all_locked.part.0+0x5e/0x90 [drm]
[1.779265]  intel_modeset_init_nogem+0x2a8/0x510 [i915]
[1.779315]  ? intel_irq_postinstall+0x38b/0x680 [i915]
[1.779358]  i915_driver_probe+0x1b7/0x470 [i915]
[1.779395]  ? mutex_lock+0x13/0x40
[1.779399]  i915_pci_probe+0x58/0x140 [i915]
[1.779435]  local_pci_probe+0x48/0x90
[1.779438]  pci_device_probe+0x115/0x1f0
[1.779439]  really_probe+0x21b/0x420
[1.779442]  __driver_probe_device+0x115/0x190
[1.779444]  driver_probe_device+0x23/0xc0
[1.779445]  __driver_attach+0xbd/0x1d0
[1.779447]  ? __device_attach_driver+0x110/0x110
[1.779448]  bus_for_each_dev+0x7c/0xc0
[1.779450]  driver_attach+0x1e/0x20
[1.779452]  bus_add_driver+0x135/0x200
[1.779453]  driver_register+0x95/0xf0
[1.779454]  __pci_register_driver+0x68/0x70
[1.779455]  i915_register_pci_driver+0x23/0x30 [i915]
[1.779488]  i915_init+0x3b/0xfc [i915]
[1.779534]  ? 0xc1229000
[1.779535]  do_one_initcall+0x46/0x1d0
[1.779539]  ? kmem_cache_alloc_trace+0x19e/0x2e0
[1.779543]  do_init_module+0x62/0x280
[1.779545]  load_module+0xac9/0xbb0
[1.779546]  __do_sys_finit_module+0xbf/0x120
[1.779548]  __x64_sys_finit_module+0x18/0x20
[1.779549]  do_syscall_64+0x59/0xc0
[1.779551]  ? do_syscall_64+0x69/0xc0
[1.779552]  ? do_syscall_64+0x69/0xc0
[1.779553]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[1.779555] RIP: 0033:0x7f0a61a13a3d
[1.779557] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d c3 53 0f 00 f7 d8 64 89 01 48
[1.779558] RSP: 002b:7ffcfe9e0748 EFLAGS: 0246 ORIG_RAX: 
0139
[1.779560] RAX: ffda RBX: 5601776d2090 RCX: 7f0a61a13a3d
[1.779561] RDX:  RSI: 7f0a61ba8441 RDI: 0017
[1.779561] RBP: 0002 R08:  R09: 0002
[1.779562] R10: 0017 R11: 0246 R12: 7f0a61ba8441
[1.779562] R13: 5601776cd450 R14: 5601777f7d60 R15: 5601777f8e30
[1.779564]  
[1.779564] 


ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-18-generic 5.15.0-18.18
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu77
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dan1364 F pipewire-media-
  dan1365 F pulseaudio
 /dev/snd/seq:dan1363 F pipewire
CasperMD5CheckResult: pass
CurrentDmesg:
 Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing 
command as another user: Not authorized

 This incident has been reported.
Date: Tue Feb 22 15:11:13 2022
InstallationDate: Installed on 2022-02-14 (8 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220214)
MachineType: Microsoft Corporation Surface Laptop 4
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=6f840793-70c0-4fc9-b509-2f18ca9665ac ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-18-generic N/A
 linux-backports-modules-5.15.0-18-generic  N/A
 linux-firmware 20220217.git6342082c-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2021
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: 10.300.141
dmi.board.

[Kernel-packages] [Bug 1961739] [NEW] PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp platform

[You-Sheng Yang]

Public bug reported:

With bug 1957026, suspend/resume using rtc and power button work as
expected, but PS/2 or USB keyboard still do not work well as an wakeup
source.

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

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Invalid

** Affects: linux-oem-5.14 (Ubuntu Focal)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: linux (Ubuntu Jammy)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

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


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

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

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

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

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

** Changed in: linux-oem-5.14 (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

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

Title:
  PS/2 Keyboard wakeup from s2idle not functioning on AMD Yellow Carp
  platform

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

Bug description:
  With bug 1957026, suspend/resume using rtc and power button work as
  expected, but PS/2 or USB keyboard still do not work well as an wakeup
  source.

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


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

[Kernel-packages] [Bug 1959110] Re: pl2303 serial adapter no longer recognized

[Po-Hsu Lin]

Awesome!
Thanks for checking, I will close this bug with Fix-released.

For those who are still having issue with this device, please feel free
to open a new bug report.

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  pl2303 serial adapter no longer recognized

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  After upgrading the Linux kernel to 5.13.0-27 my pl2303 device stopped
  working.

  Error from dmesg:

  jan 26 07:39:24 semalx0017 kernel: Linux version 5.13.0-27-generic 
(buildd@lgw01-amd64-045) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 
(Ubuntu 5.13.0>
  ...
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: pl2303 converter 
detected
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: unknown device type, 
please report to linux-...@vger.kernel.org

  This works fine in the previous 5.11.0-27-generic kernel.

  Probably this patch needs backporting 
  "USB: serial: pl2303: fix GC type detection"
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5721a9e0c9fb8a4bdfe0c8751377cd537d6174

  lsusb:

  Bus 003 Device 012: ID 067b:23a3 Prolific Technology, Inc. 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x067b Prolific Technology, Inc.
idProduct  0x23a3 
bcdDevice1.05
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Jan 26 15:11:11 2022
  InstallationDate: Installed on 2022-01-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959110/+subscriptions


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

[Kernel-packages] [Bug 1959110] Re: pl2303 serial adapter no longer recognized

[Fredrik Olofsson]

Good morning.
I can confirm my pl2303 devices work in Ubuntu-5.13.0-30.33.
Thanks
/Fredrik

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

Title:
  pl2303 serial adapter no longer recognized

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After upgrading the Linux kernel to 5.13.0-27 my pl2303 device stopped
  working.

  Error from dmesg:

  jan 26 07:39:24 semalx0017 kernel: Linux version 5.13.0-27-generic 
(buildd@lgw01-amd64-045) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 
(Ubuntu 5.13.0>
  ...
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: pl2303 converter 
detected
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: unknown device type, 
please report to linux-...@vger.kernel.org

  This works fine in the previous 5.11.0-27-generic kernel.

  Probably this patch needs backporting 
  "USB: serial: pl2303: fix GC type detection"
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5721a9e0c9fb8a4bdfe0c8751377cd537d6174

  lsusb:

  Bus 003 Device 012: ID 067b:23a3 Prolific Technology, Inc. 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x067b Prolific Technology, Inc.
idProduct  0x23a3 
bcdDevice1.05
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Jan 26 15:11:11 2022
  InstallationDate: Installed on 2022-01-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959110/+subscriptions


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

[Kernel-packages] [Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)

[Po-Hsu Lin]

This test is not failing with "unary operator expected" anymore on
B-ibm-5.4.0-1015.16~18.04.1

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  icmp_redirect from selftests fails on F/kvm (unary operator expected)

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.10 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  If any sub-test in this icmp_redirect.sh is failing but not expected
  to fail. The script will complain:
  ./icmp_redirect.sh: line 72: [: 1: unary operator expected

  This is because when the sub-test is not expected to fail, we won't
  pass any value for the xfail local variable in log_test() and thus
  it's empty. Fix this by passing 0 as the 4th variable to log_test()
  for non-xfail cases.

  This issue can be found on our KVM kernel with SRU tests, they're
  failing because of missing some kernel configs.

  [Fix]
  * 39d8622c72 "selftests: icmp_redirect: pass xfail=0 to log_test()"

  This patch can be cherry-picked into all of the affected kernels.

  [Test Plan]
  Run the patched icmp_redirect.sh script with a KVM kernel (e.g. F/kvm),
  and this "unary operator expected" error message should no longer exist.

  [Where problems could occur]
  Change limited to test script, it won't have any impact to real kernel
  function. And this issue is most likely specific to KVM kernels.

  
  == Original Bug Report ==
  icmp_redirect from selftect is failing on F/kvm 5.4.0-1045.47

   # selftests: net: icmp_redirect.sh
   #
   # ###
   # Legacy routing
   # ###
   #
   # TEST: IPv4: redirect exception  [ OK ]
   # TEST: IPv6: redirect exception  [ OK ]
   # TEST: IPv4: redirect exception plus mtu [ OK ]
   # TEST: IPv6: redirect exception plus mtu [ OK ]
   # TEST: IPv4: routing reset   [ OK ]
   # TEST: IPv6: routing reset   [ OK ]
   # TEST: IPv4: mtu exception   [ OK ]
   # TEST: IPv6: mtu exception   [ OK ]
   # TEST: IPv4: mtu exception plus redirect [ OK ]
   # TEST: IPv6: mtu exception plus redirect [XFAIL]
   #
   # ###
   # Legacy routing with VRF
   # ###
   #
   # Error: Unknown device type.
   # Cannot find device "red"
   # Error: argument "red" is wrong: Invalid VRF
   #
   # Error: argument "red" is wrong: Invalid VRF
   #
   # Cannot find device "red"
   # Cannot find device "red"
   # Error: argument "red" is wrong: Not a valid VRF name
   #
   # Error: argument "red" is wrong: Invalid VRF
   #
   # ./icmp_redirect.sh: line 71: [: 1: unary operator expected
   # TEST: IPv4: redirect exception  [FAIL]
   # Error: argument "red" is wrong: Invalid VRF
   #
   # TEST: IPv6: redirect exception  [XFAIL]
   # Error: argument "red" is wrong: Invalid VRF
   #
   # ./icmp_redirect.sh: line 71: [: 1: unary operator expected
   # TEST: IPv4: redirect exception plus mtu [FAIL]
   # Error: argument "red" is wrong: Invalid VRF
   #
   # TEST: IPv6: redirect exception plus mtu [XFAIL]
   # Error: argument "red" is wrong: Invalid VRF
   #
   # ./icmp_redirect.sh: line 71: [: 1: unary operator expected
   # TEST: IPv4: routing reset   [FAIL]
   # Error: argument "red" is wrong: Invalid VRF
   #
   # TEST: IPv6: routing reset   [XFAIL]
   # Error: argument "red" is wrong: Invalid VRF
   #
   # ./icmp_redirect.sh: line 71: [: 1: unary operator expected
   # TEST: IPv4: mtu exception   [FAIL]
   # Error: argument "red" is wrong: Invalid VRF
   #
   # TEST: IPv6: mtu excep

[Kernel-packages] [Bug 1959110] Re: pl2303 serial adapter no longer recognized

[Po-Hsu Lin]

Hello,
the fix mentioned in comment #3:
dcf097e7d21f ("USB: serial: pl2303: fix GL type detection")

Has already landed in the Ubuntu 5.13 Impish tree:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/commit/?id=77f82bf386d90b9b8e30ca0449177d8fcc3f06b6

With version:
$ git tag --contains 77f82bf386d90b9b8e30ca0449177d8fcc3f06b6
Ubuntu-5.13.0-21.21
Ubuntu-5.13.0-22.22
Ubuntu-5.13.0-23.23
Ubuntu-5.13.0-24.24
Ubuntu-5.13.0-25.26
Ubuntu-5.13.0-26.27
Ubuntu-5.13.0-27.29
Ubuntu-5.13.0-28.31
Ubuntu-5.13.0-29.32
Ubuntu-5.13.0-30.33
Ubuntu-5.13.0-31.34

So apparently this is not the one.

However the fix mentioned in the bug description:
aa5721a9 ("USB: serial: pl2303: fix GC type detection")

Has landed on 5.13 Impish tree as well:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-impish.git/commit/?id=4e1c49e9822a81d05f0518b78968681b8b95c13e

With version:
$ git tag --contain 4e1c49e9822a81d05f0518b78968681b8b95c13e
Ubuntu-5.13.0-29.32
Ubuntu-5.13.0-30.33
Ubuntu-5.13.0-31.34

Please upgrade your kernel to give the latest Ubuntu 5.13 Impish kernel a try 
and check if this can solve your problem.
Thanks!

** Changed in: linux-signed-hwe-5.13 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  pl2303 serial adapter no longer recognized

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After upgrading the Linux kernel to 5.13.0-27 my pl2303 device stopped
  working.

  Error from dmesg:

  jan 26 07:39:24 semalx0017 kernel: Linux version 5.13.0-27-generic 
(buildd@lgw01-amd64-045) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 
(Ubuntu 5.13.0>
  ...
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: pl2303 converter 
detected
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: unknown device type, 
please report to linux-...@vger.kernel.org

  This works fine in the previous 5.11.0-27-generic kernel.

  Probably this patch needs backporting 
  "USB: serial: pl2303: fix GC type detection"
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5721a9e0c9fb8a4bdfe0c8751377cd537d6174

  lsusb:

  Bus 003 Device 012: ID 067b:23a3 Prolific Technology, Inc. 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x067b Prolific Technology, Inc.
idProduct  0x23a3 
bcdDevice1.05
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Jan 26 15:11:11 2022
  InstallationDate: Installed on 2022-01-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959110/+subscriptions


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1961121

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

Title:
  Not able to enter s2idle state on AMD platforms

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

Bug description:
  [Impact]

  AMD Systems don't enter PC6 at runtime and cause failures to enter
  s2idle.

  Currently the fix is from kernel driver rather than MP2 firmware,
  which disable interrupts from kernel driver to fix MP2 firmware
  blocking CPUOFF.

  [Fix]

  The fixes involve 1) cancelling delayed work when entering s0ix and
  re-scheduling it when resuming from s0ix, and 2) clearing interrupts
  during the driver initialization and sensor command operations.

  [Test]

  This is requested by AMD and was tested on AMD CRB.

  [Where problems could occur]

  Risk is low to medium. Some code flow changes are guarded by
  reasonable conditions, but the fixes introduced additional suspend and
  resume operations.

  Having said that, clearing interrupts before driver initialization and
  cancelling work before entering sleeping states are standard
  approaches are usually safe.

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


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

[Kernel-packages] [Bug 1961121] Re: Not able to enter s2idle state on AMD platforms

[You-Sheng Yang]

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

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

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

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

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

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

Title:
  Not able to enter s2idle state on AMD platforms

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

Bug description:
  [Impact]

  AMD Systems don't enter PC6 at runtime and cause failures to enter
  s2idle.

  Currently the fix is from kernel driver rather than MP2 firmware,
  which disable interrupts from kernel driver to fix MP2 firmware
  blocking CPUOFF.

  [Fix]

  The fixes involve 1) cancelling delayed work when entering s0ix and
  re-scheduling it when resuming from s0ix, and 2) clearing interrupts
  during the driver initialization and sensor command operations.

  [Test]

  This is requested by AMD and was tested on AMD CRB.

  [Where problems could occur]

  Risk is low to medium. Some code flow changes are guarded by
  reasonable conditions, but the fixes introduced additional suspend and
  resume operations.

  Having said that, clearing interrupts before driver initialization and
  cancelling work before entering sleeping states are standard
  approaches are usually safe.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1961646

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

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

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

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

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

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

Title:
  On AMD platforms s2idle may not work w/o proper FW

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 source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  It was raised because of a community member using a Lenovo platform
  having very odd s2idle failures.

  It was later debugged that it was caused by them choosing "Linux" mode
  in Lenovo BIOS setup rather than "Windows" mode and then choosing
  "s2idle" in /sys/power/mem_sleep.

  - In "Linux" mode there is both "deep" and "s2idle" offered in 
/sys/power/mem_sleep.
  - In "Windows" mode there is only "s2idle" offered in /sys/power/mem_sleep.

  That is by default no matter if the OEM offers S3 or S2idle
  /sys/power/mem_sleep will contain "s2idle", but on AMD platforms
  "s2idle" only works if the hardware has been configured properly by
  the firmware. The outward indications of this being configured
  properly are the FADT low power idle bit being set and the uPEP ACPI
  device being populated, which is what this patch now checks for.

  So now if a user has the firmware of the machine configured for S3
  then they will only see "deep" on AMD systems.

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


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

[Kernel-packages] [Bug 1961608] Re: [amdgpu] Screen freeze after wake from sleep

[Daniel van Vugt]

This might be related to bug 1958778...

Please:

1. Reproduce the freeze again.

2. Wait 10 seconds.

3. Reboot.

4. Run:

   journalctl -b-1 > prevboot.txt
   lspci -k > lspci.txt

5. Attach the resulting text files here.


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

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

Title:
  [amdgpu] Screen freeze after wake from sleep

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

Bug description:
  Any time the computer sleeps, and I wake it the screen backlight turns on but 
nothing appears.
  This has been occurring since upgrading to Kernel 5.11-44. 

  I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 
without issues.
  I have tried multiple 5.13 releases and none of them handle sleep and wakeup 
successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 21 11:13:07 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  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: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2022-01-02 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2017
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.1.1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1961608] Re: Xorg freeze after wake from sleep

[Daniel van Vugt]

** Tags added: amdgpu

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

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

** Summary changed:

- Xorg freeze after wake from sleep
+ [amdgpu] Screen freeze after wake from sleep

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

Title:
  [amdgpu] Screen freeze after wake from sleep

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

Bug description:
  Any time the computer sleeps, and I wake it the screen backlight turns on but 
nothing appears.
  This has been occurring since upgrading to Kernel 5.11-44. 

  I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 
without issues.
  I have tried multiple 5.13 releases and none of them handle sleep and wakeup 
successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 21 11:13:07 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  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: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2022-01-02 (49 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2017
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.1.1
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.1.1
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1961460] Re: [nouveau] My laptop shuts off randomly after displaying a black screen (nouveau crashes in nvkm_pmu_reset)

[Daniel van Vugt]

** Summary changed:

- My laptop shuts off randomly after displaying a black screen (nouveau crashes 
in nvkm_pmu_reset)
+ [nouveau] My laptop shuts off randomly after displaying a black screen 
(nouveau crashes in nvkm_pmu_reset)

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

Title:
  [nouveau] My laptop shuts off randomly after displaying a black screen
  (nouveau crashes in nvkm_pmu_reset)

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

Bug description:
  Ubuntu 20.04.4 LTS
  N: Unable to locate package pkgname
  My latop screen turns black randomly and it has to do something with graphics 
driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 07:06:41 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) 
[1025:129a]
 Subsystem: Acer Incorporated [ALI] GP108BM [GeForce MX250] [1025:129a]
  InstallationDate: Installed on 2022-02-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Acer Swift SF314-55G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=8e45e071-d3dc-4ff9-9a0b-b18cd73b8609 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.release: 1.7
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Default string
  dmi.board.name: MILLER_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.07:bd12/24/2018:br1.7:efr1.8:svnAcer:pnSwiftSF314-55G:pvrV1.07:rvnWL:rnMILLER_WL:rvrV1.07:cvnAcer:ct10:cvrV1.07:sku:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-55G
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1958523] Re: [amdgpu] Static-noise-like effect

[Daniel van Vugt]

Please also attach a photo of the problem. I am wondering if bug 1961605
is similar.

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

Title:
  [amdgpu] Static-noise-like effect

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

Bug description:
  Hello,

  I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I 
can see the login screen) I see static-noise-like effect. I was able to make a 
screenshot and it depicts my desktop as if the problem didn't exist.
  Switching to stable (non-HWE) kernel solves the issue.

  My desktop environment is GNOME.

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


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

[Kernel-packages] [Bug 1961605] Re: Small window boxes are unstable and keep changing color

[Daniel van Vugt]

** Tags added: amdgpu

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

** Attachment added: "problemic_window.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1961605/+attachment/5562606/+files/problemic_window.png

** Summary changed:

- Small window boxes are unstable and keep changing color
+ amdgpu graphics corruption in kernel 5.13.0-30.33~20.04.1-generic

** Tags added: regression-update

** Summary changed:

- amdgpu graphics corruption in kernel 5.13.0-30.33~20.04.1-generic
+ [amdgpu] graphics corruption in kernel 5.13.0-30.33~20.04.1-generic

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

Title:
  [amdgpu] graphics corruption in kernel 5.13.0-30.33~20.04.1-generic

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

Bug description:
  The small window boxes are unstable, so they keep changing their
  color. I have taken screenshots and uploaded them here:
  https://mega.nz/folder/pctAQaSa#NcHgtpiwKIZs7Alm51f6sA (If you need, I
  can share the video recording of the screen).

  The screenshots are for the app BreakTimer, but the issue also happens
  for other apps, e.g., Zoom. During Zoom meeting, when I share my
  screen, the small window box containing my and other person's video
  suffer from this issue, i.e., this small window keeps changing colors.
  I am then hardly able to see myself or other person in the video and
  have to hide the video to concentrate.

  The problem most probably appeared after a recent update. Here, is the
  relevant information from '/var/log/apt/history.log' file:

  Start-Date: 2022-02-18  08:20:57
  Commandline: aptdaemon role='role-commit-packages' sender=':1.331'
  Install: linux-modules-extra-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-modules-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-headers-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-hwe-5.13-headers-5.13.0-30:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-image-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic)
  Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 
5.13.0.30.33~20.04.17), libdrm-nouveau2:amd64 (2.4.105-3~20.04.2, 
2.4.107-8ubuntu1~20.04.1), libdrm-nouveau2:i386 (2.4.105-3~20.04.2, 
2.4.107-8ubuntu1~20.04.1), linux-libc-dev:amd64 (5.4.0-99.112, 5.4.0-100.113), 
libegl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
libegl-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
signal-desktop:amd64 (5.30.0, 5.32.0), libglapi-mesa:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), snapd:amd64 
(2.51.1+20.04ubuntu2, 2.54.3+20.04.1), ubuntu-advantage-tools:amd64 
(27.5~20.04.1, 27.6~20.04.1), libarchive13:amd64 (3.4.0-2ubuntu1, 
3.4.0-2ubuntu1.1), google-chrome-stable:amd64 (98.0.4758.80-1, 
98.0.4758.102-1), python-apt-common:amd64 (2.0.0ubuntu0.20.04.6, 
2.0.0ubuntu0.20.04.7), libxatracker2:amd64 (21.0.3-0ubuntu0.3~20.04.5, 
21.2.6-0ubuntu0.1~20.04.1), language-pack-en:amd64 (1:20.04+20210802, 
1:20.04+20220211), initramfs-tools-bin:amd64 (0.136ubuntu6.6, 0.136ubuntu6.7), 
linux-image-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 
5.13.0.30.33~20.04.17), libgbm1:amd64 (21.0.3-0ubuntu0.3~20.04.5, 
21.2.6-0ubuntu0.1~20.04.1), linux-generic-hwe-20.04:amd64 
(5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), libxnvctrl0:amd64 
(470.57.01-0ubuntu0.20.04.2, 470.57.01-0ubuntu0.20.04.3), libdrm-amdgpu1:amd64 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-amdgpu1:i386 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), ubuntu-drivers-common:amd64 
(1:0.9.0~0.20.04.4, 1:0.9.0~0.20.04.5), python3-distupgrade:amd64 (1:20.04.36, 
1:20.04.37), ubuntu-release-upgrader-core:amd64 (1:20.04.36, 1:20.04.37), 
libdrm2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm2:i386 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libgl1-mesa-dev:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libgl1-mesa-dri:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
language-pack-en-base:amd64 (1:20.04+20210802, 1:20.04+20220211), 
ubuntu-release-upgrader-gtk:amd64 (1:20.04.36, 1:20.04.37), libdrm-intel1:amd64 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-radeon1:amd64 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-radeon1:i386 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), mesa-vdpau-drivers:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), mesa-vdpau-drivers:i386 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), linux-firmware:amd64 
(1.187.25, 1.187.26), mesa-vulkan-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 
21.2.6-0ubuntu0.1~20.04.1), initramfs-tools-core:amd64 (0.136ubuntu6.6, 
0.136ubuntu6.7), initramfs-tools:amd64 (0.136ubuntu6.6, 0.136ubuntu6.7), 
python3-apt:amd64 (2.0.0ubuntu0.20.04.6, 2.0.0ubuntu0.20.04.7), 
mesa-va-drivers:amd64 (21.0.3-0ubu

[Kernel-packages] [Bug 1961596] Re: Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor

[Daniel van Vugt]

External monitors can't be detected because you have disabled the
graphics driver. You need to remove the 'nomodeset' kernel parameter.

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

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

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

Title:
  Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external
  monitor

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

Bug description:
  Graphics option in About pane shows "llvmpipe (LLVM 12.0.0, 256 bits)"

  $ lspci | grep -E 'VGA|Display'
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05)

  $ glxinfo -B
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Mesa/X.org (0x)
  Device: llvmpipe (LLVM 12.0.0, 256 bits) (0x)
  Version: 21.2.6
  Accelerated: no
  Video memory: 31887MB
  Unified memory: no
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.1
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2
  OpenGL vendor string: Mesa/X.org
  OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.2.6
  OpenGL core profile shading language version string: 4.50
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  OpenGL version string: 3.1 Mesa 21.2.6
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)

  OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.6
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 21 14:42:46 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.9.1, 5.13.0-28-generic, x86_64: installed
   evdi, 1.9.1, 5.13.0-30-generic, x86_64: installed
   virtualbox, 6.1.26, 5.13.0-28-generic, x86_64: installed
   virtualbox, 6.1.26, 5.13.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:8784]
  InstallationDate: Installed on 2021-03-03 (355 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: HP HP ZBook Fury 15 G7 Mobile Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nomodeset vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2021
  dmi.bios.release: 4.1
  dmi.bios.vendor: HP
  dmi.bios.version: S92 Ver. 01.04.01
  dmi.board.name: 8783
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3D.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 22.61
  dmi.modalias: 
dmi:bvnHP:bvrS92Ver.01.04.01:bd01/05/2021:br4.1:efr22.61:svnHP:pnHPZBookFury15G7MobileWorkstation:pvr:sku26F75AV:rvnHP:rn8783:rvrKBCVersion16.3D.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook
  dmi.product.name: HP ZBook Fury 15 G7 Mobile Workstation
  dmi.product.sku: 26F75AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1961646] [NEW] On AMD platforms s2idle may not work w/o proper FW

[You-Sheng Yang]

Public bug reported:

It was raised because of a community member using a Lenovo platform
having very odd s2idle failures.

It was later debugged that it was caused by them choosing "Linux" mode
in Lenovo BIOS setup rather than "Windows" mode and then choosing
"s2idle" in /sys/power/mem_sleep.

- In "Linux" mode there is both "deep" and "s2idle" offered in 
/sys/power/mem_sleep.
- In "Windows" mode there is only "s2idle" offered in /sys/power/mem_sleep.

That is by default no matter if the OEM offers S3 or S2idle
/sys/power/mem_sleep will contain "s2idle", but on AMD platforms
"s2idle" only works if the hardware has been configured properly by the
firmware. The outward indications of this being configured properly are
the FADT low power idle bit being set and the uPEP ACPI device being
populated, which is what this patch now checks for.

So now if a user has the firmware of the machine configured for S3 then
they will only see "deep" on AMD systems.

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

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

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Invalid

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

Title:
  On AMD platforms s2idle may not work w/o proper FW

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  New
Status in linux source package in Impish:
  New
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  New
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  It was raised because of a community member using a Lenovo platform
  having very odd s2idle failures.

  It was later debugged that it was caused by them choosing "Linux" mode
  in Lenovo BIOS setup rather than "Windows" mode and then choosing
  "s2idle" in /sys/power/mem_sleep.

  - In "Linux" mode there is both "deep" and "s2idle" offered in 
/sys/power/mem_sleep.
  - In "Windows" mode there is only "s2idle" offered in /sys/power/mem_sleep.

  That is by default no matter if the OEM offers S3 or S2idle
  /sys/power/mem_sleep will contain "s2idle", but on AMD platforms
  "s2idle" only works if the hardware has been configured properly by
  the firmware. The outward indications of this being configured
  properly are the FADT low power idle bit being set and the uPEP ACPI
  device being populated, which is what this patch now checks for.

  So now if a user has the firmware of the machine configured for S3
  then they will only see "deep" on AMD systems.

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


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

[Kernel-packages] [Bug 1961608] [NEW] Xorg freeze after wake from sleep

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Any time the computer sleeps, and I wake it the screen backlight turns on but 
nothing appears.
This has been occurring since upgrading to Kernel 5.11-44. 

I used 5.11-40 without issues, and when I did a fresh install, I used 5.11-27 
without issues.
I have tried multiple 5.13 releases and none of them handle sleep and wakeup 
successfully.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 21 11:13:07 2022
DistUpgraded: Fresh install
DistroCodename: focal
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: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
   Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
InstallationDate: Installed on 2022-01-02 (49 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Dell Inc. Inspiron 5565
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-30-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2017
dmi.bios.release: 5.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.1
dmi.board.name: 0021CT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.1.1
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:br5.3:svnDellInc.:pnInspiron5565:pvr1.1.1:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.1.1:sku0769:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5565
dmi.product.sku: 0769
dmi.product.version: 1.1.1
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 amdgpu apport-bug false-gpu-hang focal freeze ubuntu
-- 
Xorg freeze after wake from sleep
https://bugs.launchpad.net/bugs/1961608
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-5.11 in Ubuntu.

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

[Kernel-packages] [Bug 1961605] [NEW] Small window boxes are unstable and keep changing color

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The small window boxes are unstable, so they keep changing their color.
I have taken screenshots and uploaded them here:
https://mega.nz/folder/pctAQaSa#NcHgtpiwKIZs7Alm51f6sA (If you need, I
can share the video recording of the screen).

The screenshots are for the app BreakTimer, but the issue also happens
for other apps, e.g., Zoom. During Zoom meeting, when I share my screen,
the small window box containing my and other person's video suffer from
this issue, i.e., this small window keeps changing colors. I am then
hardly able to see myself or other person in the video and have to hide
the video to concentrate.

The problem most probably appeared after a recent update. Here, is the
relevant information from '/var/log/apt/history.log' file:

Start-Date: 2022-02-18  08:20:57
Commandline: aptdaemon role='role-commit-packages' sender=':1.331'
Install: linux-modules-extra-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-modules-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-headers-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-hwe-5.13-headers-5.13.0-30:amd64 (5.13.0-30.33~20.04.1, 
automatic), linux-image-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, 
automatic)
Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 
5.13.0.30.33~20.04.17), libdrm-nouveau2:amd64 (2.4.105-3~20.04.2, 
2.4.107-8ubuntu1~20.04.1), libdrm-nouveau2:i386 (2.4.105-3~20.04.2, 
2.4.107-8ubuntu1~20.04.1), linux-libc-dev:amd64 (5.4.0-99.112, 5.4.0-100.113), 
libegl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
libegl-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
signal-desktop:amd64 (5.30.0, 5.32.0), libglapi-mesa:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), snapd:amd64 
(2.51.1+20.04ubuntu2, 2.54.3+20.04.1), ubuntu-advantage-tools:amd64 
(27.5~20.04.1, 27.6~20.04.1), libarchive13:amd64 (3.4.0-2ubuntu1, 
3.4.0-2ubuntu1.1), google-chrome-stable:amd64 (98.0.4758.80-1, 
98.0.4758.102-1), python-apt-common:amd64 (2.0.0ubuntu0.20.04.6, 
2.0.0ubuntu0.20.04.7), libxatracker2:amd64 (21.0.3-0ubuntu0.3~20.04.5, 
21.2.6-0ubuntu0.1~20.04.1), language-pack-en:amd64 (1:20.04+20210802, 
1:20.04+20220211), initramfs-tools-bin:amd64 (0.136ubuntu6.6, 0.136ubuntu6.7), 
linux-image-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 
5.13.0.30.33~20.04.17), libgbm1:amd64 (21.0.3-0ubuntu0.3~20.04.5, 
21.2.6-0ubuntu0.1~20.04.1), linux-generic-hwe-20.04:amd64 
(5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), libxnvctrl0:amd64 
(470.57.01-0ubuntu0.20.04.2, 470.57.01-0ubuntu0.20.04.3), libdrm-amdgpu1:amd64 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-amdgpu1:i386 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), ubuntu-drivers-common:amd64 
(1:0.9.0~0.20.04.4, 1:0.9.0~0.20.04.5), python3-distupgrade:amd64 (1:20.04.36, 
1:20.04.37), ubuntu-release-upgrader-core:amd64 (1:20.04.36, 1:20.04.37), 
libdrm2:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm2:i386 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libgl1-mesa-dev:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), libgl1-mesa-dri:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
language-pack-en-base:amd64 (1:20.04+20210802, 1:20.04+20220211), 
ubuntu-release-upgrader-gtk:amd64 (1:20.04.36, 1:20.04.37), libdrm-intel1:amd64 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-radeon1:amd64 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), libdrm-radeon1:i386 
(2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1), mesa-vdpau-drivers:amd64 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), mesa-vdpau-drivers:i386 
(21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), linux-firmware:amd64 
(1.187.25, 1.187.26), mesa-vulkan-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 
21.2.6-0ubuntu0.1~20.04.1), initramfs-tools-core:amd64 (0.136ubuntu6.6, 
0.136ubuntu6.7), initramfs-tools:amd64 (0.136ubuntu6.6, 0.136ubuntu6.7), 
python3-apt:amd64 (2.0.0ubuntu0.20.04.6, 2.0.0ubuntu0.20.04.7), 
mesa-va-drivers:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
libglx-mesa0:amd64 (21.0.3-0ubuntu0.3~20.04.5, 21.2.6-0ubuntu0.1~20.04.1), 
libdrm-common:amd64 (2.4.105-3~20.04.2, 2.4.107-8ubuntu1~20.04.1)
End-Date: 2022-02-18  08:24:41

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 21 16:35:12 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 

[Kernel-packages] [Bug 1961596] [NEW] Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Graphics option in About pane shows "llvmpipe (LLVM 12.0.0, 256 bits)"

$ lspci | grep -E 'VGA|Display'
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05)

$ glxinfo -B
name of display: :1
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa/X.org (0x)
Device: llvmpipe (LLVM 12.0.0, 256 bits) (0x)
Version: 21.2.6
Accelerated: no
Video memory: 31887MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Mesa/X.org
OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 21.2.6
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.1 Mesa 21.2.6
OpenGL shading language version string: 1.40
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.2.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 21 14:42:46 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 evdi, 1.9.1, 5.13.0-28-generic, x86_64: installed
 evdi, 1.9.1, 5.13.0-30-generic, x86_64: installed
 virtualbox, 6.1.26, 5.13.0-28-generic, x86_64: installed
 virtualbox, 6.1.26, 5.13.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Device [103c:8784]
InstallationDate: Installed on 2021-03-03 (355 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: HP HP ZBook Fury 15 G7 Mobile Workstation
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-34-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash nomodeset vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2021
dmi.bios.release: 4.1
dmi.bios.vendor: HP
dmi.bios.version: S92 Ver. 01.04.01
dmi.board.name: 8783
dmi.board.vendor: HP
dmi.board.version: KBC Version 16.3D.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 22.61
dmi.modalias: 
dmi:bvnHP:bvrS92Ver.01.04.01:bd01/05/2021:br4.1:efr22.61:svnHP:pnHPZBookFury15G7MobileWorkstation:pvr:sku26F75AV:rvnHP:rn8783:rvrKBCVersion16.3D.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Fury 15 G7 Mobile Workstation
dmi.product.sku: 26F75AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: linux-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug focal ubuntu
-- 
Ubuntu 20.04 with kernel version 5.11.0-34 stopped detecting external monitor
https://bugs.launchpad.net/bugs/1961596
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-hwe-5.11 in Ubuntu.

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

[Kernel-packages] [Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

[Daniel van Vugt]

Mariusz, I have reopened bug 1958523 for you.

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

Title:
  [amdgpu] Random noise 'static' display after internal display turned
  off/on

Status in linux-hwe-5.13 package in Ubuntu:
  Fix Released

Bug description:
  Laptop internal display shows random looking 'static' after it's
  turned off and then on again.   e.g. on suspend/resume, or when
  plugging/unplugging an external monitor.

  This appeared to come after a `dist-upgrade` took the kernel from
  5.11.0-44 to 5.13.0-25 (hwe).

  Others are seeing this with both NVidia and AMD graphics hardware:
  - 
https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/
  - 
https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/

  I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome
  both X and Wayland, and gnome-flashback/metacity.  All showed the same
  problem.

  Also tried an `apt install --reinstall xserver-xorg-video-radeon
  libdrm-radeon1` for luck - no joy.

  Running a 20.04.3 live stick the problem does *not* occur.

  System: Thinkpad X13 Gen1
  Processor: AMD Ryzen 7 PRO 4750U
  System Firmware: 1.35

  $ lsb_release -rd
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

  Happy to assist with investigations.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME
  Date: Thu Jan 20 19:37:09 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:5082]
  InstallationDate: Installed on 2021-06-24 (210 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20UF0014US
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET67W(1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UF0014US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.36
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1:
  dmi.product.family: ThinkPad X13 Gen 1
  dmi.product.name: 20UF0014US
  dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1
  dmi.product.version: ThinkPad X13 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1958523] Re: [amdgpu] Static-noise-like effect

[Daniel van Vugt]

While the problem is happening please run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

** This bug is no longer a duplicate of bug 1958591
   [amdgpu] Random noise 'static' display after internal display turned off/on

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

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

Title:
  [amdgpu] Static-noise-like effect

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

Bug description:
  Hello,

  I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I 
can see the login screen) I see static-noise-like effect. I was able to make a 
screenshot and it depicts my desktop as if the problem didn't exist.
  Switching to stable (non-HWE) kernel solves the issue.

  My desktop environment is GNOME.

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


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

[Kernel-packages] [Bug 1961546] Re: init freezes when >1 display connected on rocket lake PC

[Paul White ]

Changing status to 'Confirmed' as requested in comment #1.

** 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/1961546

Title:
  init freezes when >1 display connected on rocket lake PC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  # apt-cache policy linux-image-5.15.0-18-generic
  linux-image-5.15.0-18-generic:
Installed: 5.15.0-18.18
Candidate: 5.15.0-18.18
Version table:
   *** 5.15.0-18.18 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  # lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  To reproduce: try to boot with more than one connected display on Intel 
Rocket Lake PC (e.g. Asus B560-M with i5-11400)
  Actual results: init stops around the time KMS should engage
  Expected results: boots normally

  Upstream bugs fixed:
  https://gitlab.freedesktop.org/drm/intel/-/issues/4762
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006166 fixed in 5.16.10 & 
5.17rc4
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D17p', '/dev/snd/pcmC0D16p', '/dev/snd/pcmC0D15p', 
'/dev/snd/pcmC0D14p', '/dev/snd/pcmC0D13p', '/dev/snd/pcmC0D12p', 
'/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
   Bus 001 Device 004: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=tm8p17ub2204 noresume 
ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 video=1440x900@60 5
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 12.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1203
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B560M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1203:bd10/27/2021:br12.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB560M-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

Re: [Kernel-packages] [Bug 1938845] Re: Legion 7 16ITHg6 - Touchpad undetected

[Cameron Berkenpas]

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

What distribution and version are you running? Are you running a Legion 
7i 16ITHg6 ? Later Ubuntu kernels have had a fix for this for some time. 
Same for the vanilla Linux source.

Alas, there's still no fix for the sound on the 16ITHg6. You can only 
get the left channel out of both the left and right speakers, and you'll 
lose sound going to sleep. Hibernate is a work around, but Nvidia's 
drivers don't seem to support hibernate reliably so I leave the Nvidia 
GPU disabled for now (games aren't very good with only one audio channel 
after all).

On 2/21/2022 4:37 PM, Darshan Shah wrote:
> *** This bug is a duplicate of bug 1937056 ***
>  https://bugs.launchpad.net/bugs/1937056
>
> Can you tell me how you fixed this issue... I am amateur person
>

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

Title:
  Legion 7 16ITHg6 - Touchpad undetected

Status in linux package in Ubuntu:
  New

Bug description:
  I received my Lenovo Legion 7i 16ITHg6 laptop today. The touchpad
  seems to be entirely undetected.

  I've attached the contents of /proc/bus/input/devices as devices.txt.
  No touchpad device is shown. USB mice work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7344 F pulseaudio
   /dev/snd/controlC0:  hiryu  7344 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Aug  3 20:05:13 2021
  InstallationDate: Installed on 2021-04-23 (103 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=1 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2021
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN26WW:bd05/22/2021:br1.26:efr1.26:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1958229] Re: UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp platform

[You-Sheng Yang]

Has been committed to 5.15.0-19.19 or later. Currently respan in
5.15.0-22.22 in focal-proposed.

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

Title:
  UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp
  platform

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

Bug description:
  [SRU Justification]

  [Impact]

  On HP Lockheed16, following UBSAN warning dumped at boot and the first
  USB4 port is disabled:

UBSAN: array-index-out-of-bounds in 
/drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_resource.c:1295:22
index 6 is out of range for type 'dcn10_stream_enc_registers[5]'

  This is a follow-up for bug 1953008 on Jammy, which only happens when
  patches for USB4 alt mode were applied and tested on a HP platform.

  [Fix]

  Commit d374d3b49321 ("drm/amd/display: Fix out of bounds access on DNC31
  stream encoder regs") from Linus' tree.

  [Test Case]

  Apply and check no more such warning, and USB alt mode should work.

  [Where problems could occur]

  No. This specifies the expected array size to avoid UBSAN warning.

  [Other Info]

  While UBSAN is only turned on by default on 5.15 kernels or newer, and
  we didn't find this issue on oem-5.14, so only Jammy is nominated here.

  == original bug report ==

  UBSAN: array-index-out-of-bounds in
  drivers/gpu/drm/amd/display/dc/dcn31/dcn31_resource.c:1295:22

  This is a follow-up for bug 1953008, which only happens when patches
  for USB4 alt mode were applied.

  This is found on HP Lockheed16 and will disable one of the tbt port.

  Source tree available in
  https://git.launchpad.net/~vicamo/+git/ubuntu-
  
kernel/tree/drivers/gpu/drm/amd/display/dc/dcn31/dcn31_resource.c?h=bug-1953008/amdgpu-
  yellow-carp-support-
  usb4-altmode/jammy&id=243857296edd341e5054cc50732b3af3432eaaf6#n1295

  1263 static struct stream_encoder *dcn31_stream_encoder_create(
  1264 enum engine_id eng_id,
  1265 struct dc_context *ctx)
  1266 {
  ...
  1293 dcn30_dio_stream_encoder_construct(enc1, ctx, ctx->dc_bios,
  1294 eng_id, vpg, afmt,
  1295 &stream_enc_regs[eng_id],
  1296 &se_shift, &se_mask);

  [ 5.557065] [drm] amdgpu kernel modesetting enabled.
  [ 5.562748] amdgpu: Virtual CRAT table created for CPU
  [ 5.562769] amdgpu: Topology: Add CPU node
  [ 5.563048] checking generic (32000 8ca000) vs hw (32000 1000)
  [ 5.563053] fb0: switching to amdgpu from EFI VGA
  [ 5.563274] Console: switching to colour dummy device 80x25
  [ 5.563386] amdgpu :64:00.0: vgaarb: deactivate vga console
  [ 5.563768] [drm] initializing kernel modesetting (YELLOW_CARP 0x1002:0x1681 
0x103C:0x8990 0xD5).
  [ 5.563791] amdgpu :64:00.0: amdgpu: Trusted Memory Zone (TMZ) feature 
disabled as experimental (default)
  [ 5.563968] [drm] register mmio base: 0xA480
  [ 5.563969] [drm] register mmio size: 524288
  [ 5.563976] [drm] PCIE atomic ops is not supported
  [ 5.565481] [drm] add ip block number 0 
  [ 5.565483] [drm] add ip block number 1 
  [ 5.565484] [drm] add ip block number 2 
  [ 5.565485] [drm] add ip block number 3 
  [ 5.565486] [drm] add ip block number 4 
  [ 5.565487] [drm] add ip block number 5 
  [ 5.565488] [drm] add ip block number 6 
  [ 5.565490] [drm] add ip block number 7 
  [ 5.565491] [drm] add ip block number 8 
  [ 5.565492] [drm] add ip block number 9 
  [ 5.565512] amdgpu :64:00.0: amdgpu: Fetched VBIOS from VFCT
  [ 5.565515] amdgpu: ATOM BIOS: 113-REMBRANDT-032
  [ 5.565529] [drm] VCN(0) decode is enabled in VM mode
  [ 5.565530] [drm] VCN(0) encode is enabled in VM mode
  [ 5.565532] [drm] JPEG decode is enabled in VM mode
  [ 5.565570] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, 
fragment size is 9-bit
  [ 5.565576] amdgpu :64:00.0: amdgpu: VRAM: 512M 0x00F4 - 
0x00F41FFF (512M used)
  [ 5.565579] amdgpu :64:00.0: amdgpu: GART: 512M 0x - 
0x1FFF
  [ 5.565580] amdgpu :64:00.0: amdgpu: AGP: 267419648M 0x00F8 - 
0x
  [ 5.565589] [drm] Detected VRAM RAM=512M, BAR=512M
  [ 5.565590] [drm] RAM width 64bits DDR5
  [ 5.565640] [drm] amdgpu: 512M of VRAM memory ready
  [ 5.565642] [drm] amdgpu: 3072M of GTT memory ready.
  [ 5.565658] [drm] GART: num cpu pages 131072, num gpu pages 131072
  [ 5.566076] [drm] PCIE GART of 512M enabled (table at 0x00F4008CA000).
  [ 5.567973] amdgpu :64:00.0: amdgpu: PSP runtime database doesn't exist
  [ 5.573492] [drm] use_doorbell being set to: [true]
  [ 5.574279] [drm] Loading DMUB firmware via PSP: version=0x040D
  [ 5.574727] [drm] Found VCN firmware Version ENC: 1.14 DEC: 2 VEP: 0 
Revision: 3
  [ 5.574733] amdgpu :64:00.0: amdgpu: Will use PSP to load VCN firmware
  [ 5.599344] [drm] reserve 0xa0 from 0xf41f40 for PS

[Kernel-packages] [Bug 1958229] Re: UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp platform

[You-Sheng Yang]

** 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/1958229

Title:
  UBSAN: array-index-out-of-bounds in dcn31_resources on AMD yellow carp
  platform

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

Bug description:
  [SRU Justification]

  [Impact]

  On HP Lockheed16, following UBSAN warning dumped at boot and the first
  USB4 port is disabled:

UBSAN: array-index-out-of-bounds in 
/drivers/gpu/drm/amd/amdgpu/../display/dc/dcn31/dcn31_resource.c:1295:22
index 6 is out of range for type 'dcn10_stream_enc_registers[5]'

  This is a follow-up for bug 1953008 on Jammy, which only happens when
  patches for USB4 alt mode were applied and tested on a HP platform.

  [Fix]

  Commit d374d3b49321 ("drm/amd/display: Fix out of bounds access on DNC31
  stream encoder regs") from Linus' tree.

  [Test Case]

  Apply and check no more such warning, and USB alt mode should work.

  [Where problems could occur]

  No. This specifies the expected array size to avoid UBSAN warning.

  [Other Info]

  While UBSAN is only turned on by default on 5.15 kernels or newer, and
  we didn't find this issue on oem-5.14, so only Jammy is nominated here.

  == original bug report ==

  UBSAN: array-index-out-of-bounds in
  drivers/gpu/drm/amd/display/dc/dcn31/dcn31_resource.c:1295:22

  This is a follow-up for bug 1953008, which only happens when patches
  for USB4 alt mode were applied.

  This is found on HP Lockheed16 and will disable one of the tbt port.

  Source tree available in
  https://git.launchpad.net/~vicamo/+git/ubuntu-
  
kernel/tree/drivers/gpu/drm/amd/display/dc/dcn31/dcn31_resource.c?h=bug-1953008/amdgpu-
  yellow-carp-support-
  usb4-altmode/jammy&id=243857296edd341e5054cc50732b3af3432eaaf6#n1295

  1263 static struct stream_encoder *dcn31_stream_encoder_create(
  1264 enum engine_id eng_id,
  1265 struct dc_context *ctx)
  1266 {
  ...
  1293 dcn30_dio_stream_encoder_construct(enc1, ctx, ctx->dc_bios,
  1294 eng_id, vpg, afmt,
  1295 &stream_enc_regs[eng_id],
  1296 &se_shift, &se_mask);

  [ 5.557065] [drm] amdgpu kernel modesetting enabled.
  [ 5.562748] amdgpu: Virtual CRAT table created for CPU
  [ 5.562769] amdgpu: Topology: Add CPU node
  [ 5.563048] checking generic (32000 8ca000) vs hw (32000 1000)
  [ 5.563053] fb0: switching to amdgpu from EFI VGA
  [ 5.563274] Console: switching to colour dummy device 80x25
  [ 5.563386] amdgpu :64:00.0: vgaarb: deactivate vga console
  [ 5.563768] [drm] initializing kernel modesetting (YELLOW_CARP 0x1002:0x1681 
0x103C:0x8990 0xD5).
  [ 5.563791] amdgpu :64:00.0: amdgpu: Trusted Memory Zone (TMZ) feature 
disabled as experimental (default)
  [ 5.563968] [drm] register mmio base: 0xA480
  [ 5.563969] [drm] register mmio size: 524288
  [ 5.563976] [drm] PCIE atomic ops is not supported
  [ 5.565481] [drm] add ip block number 0 
  [ 5.565483] [drm] add ip block number 1 
  [ 5.565484] [drm] add ip block number 2 
  [ 5.565485] [drm] add ip block number 3 
  [ 5.565486] [drm] add ip block number 4 
  [ 5.565487] [drm] add ip block number 5 
  [ 5.565488] [drm] add ip block number 6 
  [ 5.565490] [drm] add ip block number 7 
  [ 5.565491] [drm] add ip block number 8 
  [ 5.565492] [drm] add ip block number 9 
  [ 5.565512] amdgpu :64:00.0: amdgpu: Fetched VBIOS from VFCT
  [ 5.565515] amdgpu: ATOM BIOS: 113-REMBRANDT-032
  [ 5.565529] [drm] VCN(0) decode is enabled in VM mode
  [ 5.565530] [drm] VCN(0) encode is enabled in VM mode
  [ 5.565532] [drm] JPEG decode is enabled in VM mode
  [ 5.565570] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, 
fragment size is 9-bit
  [ 5.565576] amdgpu :64:00.0: amdgpu: VRAM: 512M 0x00F4 - 
0x00F41FFF (512M used)
  [ 5.565579] amdgpu :64:00.0: amdgpu: GART: 512M 0x - 
0x1FFF
  [ 5.565580] amdgpu :64:00.0: amdgpu: AGP: 267419648M 0x00F8 - 
0x
  [ 5.565589] [drm] Detected VRAM RAM=512M, BAR=512M
  [ 5.565590] [drm] RAM width 64bits DDR5
  [ 5.565640] [drm] amdgpu: 512M of VRAM memory ready
  [ 5.565642] [drm] amdgpu: 3072M of GTT memory ready.
  [ 5.565658] [drm] GART: num cpu pages 131072, num gpu pages 131072
  [ 5.566076] [drm] PCIE GART of 512M enabled (table at 0x00F4008CA000).
  [ 5.567973] amdgpu :64:00.0: amdgpu: PSP runtime database doesn't exist
  [ 5.573492] [drm] use_doorbell being set to: [true]
  [ 5.574279] [drm] Loading DMUB firmware via PSP: version=0x040D
  [ 5.574727] [drm] Found VCN firmware Version ENC: 1.14 DEC: 2 VEP: 0 
Revision: 3
  [ 5.574733] amdgpu :64:00.0: amdgpu: Will use PSP to load VCN firmware
  [ 5.599344] [drm] reserve 0xa0 from 0xf41f40 for PSP TMR
  [ 5.62525

[Kernel-packages] [Bug 1938845] Re: Legion 7 16ITHg6 - Touchpad undetected

[Darshan Shah]

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

Can you tell me how you fixed this issue... I am amateur person

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

Title:
  Legion 7 16ITHg6 - Touchpad undetected

Status in linux package in Ubuntu:
  New

Bug description:
  I received my Lenovo Legion 7i 16ITHg6 laptop today. The touchpad
  seems to be entirely undetected.

  I've attached the contents of /proc/bus/input/devices as devices.txt.
  No touchpad device is shown. USB mice work.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7344 F pulseaudio
   /dev/snd/controlC0:  hiryu  7344 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Aug  3 20:05:13 2021
  InstallationDate: Installed on 2021-04-23 (103 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=1 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2021
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN26WW:bd05/22/2021:br1.26:efr1.26:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1961476] Re: The laptop turns off only through the button and won't wake up from sleep (black screen)

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  The laptop turns off only through the button and won't wake up from
  sleep (black screen)

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

Bug description:
  A complete shutdown of the laptop occurs only with the help of the shutdown 
button. If this is not done, then the keyboard backlight and fans work, and the 
screen itself is turned off. And also the sleep mode does not work (black 
screen and no reaction), you have to turn it off with a button to get out of 
it. The problem has been observed since ubuntu version 20.04 and the BIOS 
update. These problems are not observed in Windows OS. The video card is no 
longer displayed as nvidia in both operating systems, now it is displayed only 
asMesa Intel® UHD Graphics 630 (CFL GT2).
  I didn't reboot myself before, apparently the kernel was fixed. Thanks to the 
developers, that now he at least reboots himself. It remains to solve the issue 
with the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 14:35:10 2022
  InstallationDate: Installed on 2022-02-01 (17 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

  Product Name: G7 7790
  BIOS Information
   Vendor: Dell Inc.
   Version: 1.14.0 10/20/2020
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eve1634 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-01 (17 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. G7 7790
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=72a43957-07b7-4ade-9aa6-30aede661648 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.26
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 0PJ0RG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 6564055862
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd10/20/2020:br1.14:svnDellInc.:pnG77790:pvr:rvnDellInc.:rn0PJ0RG:rvrA00:cvnDellInc.:ct10:cvr:sku08EC:
  dmi.product.family: GSeries
  dmi.product.name: G7 7790
  dmi.product.sku: 08EC
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961476/+subscriptions


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

[Kernel-packages] [Bug 1961632] Re: linux-azure: Case VM fails to initialize CX4 VF due to mem fragmentation

[Tim Gardner]

** Also affects: linux-azure (Ubuntu Jammy)
   Importance: Medium
 Assignee: Tim Gardner (timg-tpi)
   Status: In Progress

** Changed in: linux-azure (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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1961632

Title:
  linux-azure: Case VM fails to initialize CX4 VF due to mem
  fragmentation

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-azure source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification

  [Impact]

  Below are the kernel messages showing the VF being removed at
  12:21:35, and then being re-added starting at 12:22:44. You can see
  the stack traces trying to make an order 7 allocation, and then and
  order 8 allocation, both of which fail.

  [Sun Jan 23 12:21:34 2022] infiniband mlx5_0: 
wait_for_async_commands:745:(pid 15782): done with all pending requests
  [Sun Jan 23 12:21:35 2022] hv_netvsc 000d3a7c-6aa5-000d-3a7c-6aa5000d3a7c 
eth0: Data path switched from VF: eth1
  [Sun Jan 23 12:21:35 2022] hv_netvsc 000d3a7c-6aa5-000d-3a7c-6aa5000d3a7c 
eth0: VF unregistering: eth1
  [Sun Jan 23 12:22:44 2022] hv_pci 61367817-ab6d-44c7-8b57-457fcc1b66c2: PCI 
VMBus probing: Using version 0x10002
  [Sun Jan 23 12:22:44 2022] hv_pci 61367817-ab6d-44c7-8b57-457fcc1b66c2: PCI 
host bridge to bus ab6d:00
  [Sun Jan 23 12:22:44 2022] pci_bus ab6d:00: root bus resource [mem 
0xfe000-0xfe00f window]
  [Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: [15b3:1016] type 00 class 
0x02
  [Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: reg 0x10: [mem 
0xfe000-0xfe00f 64bit pref]
  [Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: 0.000 Gb/s available PCIe 
bandwidth, limited by Unknown speed x0 link at ab6d:00:02.0 (capable of 63.008 
Gb/s with 8 GT/s x8 link)
  [Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: BAR 0: assigned [mem 
0xfe000-0xfe00f 64bit pref]
  [Sun Jan 23 12:22:44 2022] mlx5_core ab6d:00:02.0: firmware version: 
14.30.1210
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 24 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 25 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 26 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 27 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 28 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 29 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 30 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 31 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 32 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 33 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 34 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 35 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 36 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 37 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 38 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 39 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 40 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 41 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 42 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 43 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 44 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 45 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 46 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 47 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 48 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 49 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 50 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 51 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 52 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 53 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 54 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 55 for MSI/MSI-X
  [Sun Jan 23 12:22:45 2022] kworker/18:1: page allocation failure: order:7, 
mode:0x80d0
  [Sun Jan 23 12:22:45 2022] CPU: 18 PID: 11869 Comm: kworker/18:1 Kdump: 
loaded Tainted: G  T 3.10.0-1160.31.1.el7.x86_64 #1
  [Sun Jan 23 12:22:45 2022] Hardware name: Microsoft Corporation Virtual 
Machine/Virtual Machine, BIOS 090008 12/07/2018
  [Sun Jan 23 12:22:45 2022] Workqueue: hv_pri_chan vmbus_add_channel_work 
[hv_vmbus]
  [Sun Jan 23 12:22:45 2022] Call Trace:
  [Sun Jan 23 12:22:45 2022] [] dump_stac

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

[Ubuntu Kernel Bot]

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

apport-collect 1961630

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

Title:
  Thunderbolt display not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Thinkpad X1 Gen4 (20Y5000QUS) using Ubuntu 21.10 is unable to
  connect to Thunderbolt monitor (BENQ PD2272OU).

  It works as expected (monitor signal + USB devices) when I installed
  Windows 10 on the laptop so I have ruled out hardware issues. I have
  also tried with a Carbon Gen9 running Ubuntu 21.10 and it works as
  expected.

  The monitor "BENQ PD2272OU" is detected in the Thunderbolt pane as
  "Authorized" but no signal and no USB devices. I have installed all
  updates and firmware available in the "Software" app. I have checked
  the BIOS and I have "Wake on AC plug" enabled.

  At this point I am unsure what to try.

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


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

[Kernel-packages] [Bug 1961630] Re: Thunderbolt display not working

[Paul White ]

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

** Tags added: impish

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

Title:
  Thunderbolt display not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Thinkpad X1 Gen4 (20Y5000QUS) using Ubuntu 21.10 is unable to
  connect to Thunderbolt monitor (BENQ PD2272OU).

  It works as expected (monitor signal + USB devices) when I installed
  Windows 10 on the laptop so I have ruled out hardware issues. I have
  also tried with a Carbon Gen9 running Ubuntu 21.10 and it works as
  expected.

  The monitor "BENQ PD2272OU" is detected in the Thunderbolt pane as
  "Authorized" but no signal and no USB devices. I have installed all
  updates and firmware available in the "Software" app. I have checked
  the BIOS and I have "Wake on AC plug" enabled.

  At this point I am unsure what to try.

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


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

[Kernel-packages] [Bug 1961630] [NEW] Thunderbolt display not working

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My Thinkpad X1 Gen4 (20Y5000QUS) using Ubuntu 21.10 is unable to connect
to Thunderbolt monitor (BENQ PD2272OU).

It works as expected (monitor signal + USB devices) when I installed
Windows 10 on the laptop so I have ruled out hardware issues. I have
also tried with a Carbon Gen9 running Ubuntu 21.10 and it works as
expected.

The monitor "BENQ PD2272OU" is detected in the Thunderbolt pane as
"Authorized" but no signal and no USB devices. I have installed all
updates and firmware available in the "Software" app. I have checked the
BIOS and I have "Wake on AC plug" enabled.

At this point I am unsure what to try.

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

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

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

[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests

[Launchpad Bug Tracker]

This bug was fixed in the package linux-signed-azure - 5.13.0-1014.16

---
linux-signed-azure (5.13.0-1014.16) impish; urgency=medium

  * Master version: 5.13.0-1014.16

  * Enable arm64 for Hyper-V guests (LP: #1949770)
- [Packaging] azure: Enable arm64

 -- Ian May   Fri, 11 Feb 2022 11:01:26 -0600

** Changed in: linux-signed-azure (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  Enable arm64 for Hyper-V guests

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-meta-azure package in Ubuntu:
  In Progress
Status in linux-signed-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Hirsute:
  Fix Released
Status in linux-meta-azure source package in Hirsute:
  Fix Released
Status in linux-signed-azure source package in Hirsute:
  Fix Released
Status in linux-azure source package in Impish:
  Fix Released
Status in linux-meta-azure source package in Impish:
  Fix Released
Status in linux-signed-azure source package in Impish:
  Fix Released
Status in linux-azure source package in Jammy:
  In Progress
Status in linux-meta-azure source package in Jammy:
  In Progress
Status in linux-signed-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Since linux-azure can also be used for local Hyper-V guests on Windows
  10 Pro running on arm64 platforms, enable arm64 build for this kernel
  as well.

  [Test Case]

  Boot an arm64 VM on a machine running Win10Pro with Hyper-V.

  [Where things could go wrong]

  Some of the patches touch common PCI code. Device detection could be
  impacted.

  [Other info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1947455] Re: sub sub domain names not properly resolved

[Bram Diederik]

I had other network hostname issues. google lead me to a file called
/etc/nsswitch.conf

I replaced a line from a other linux box 
`hosts:  files mdns4_minimal [NOTFOUND=return] dns` 

resolving all my issues.

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

Title:
  sub sub domain names not properly resolved

Status in Ubuntu:
  Invalid
Status in bind9 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I have a local lan with a libvirt server and on that a vpn
  I have a wildcard sub domain at freedns.afraid.org (sub.hostname.com)
  that has a kvm and vpn sub sub domain names. (sub.sub.hostname.com)

  If i ping the sub sub hostname outside my local lan i get my external IP 
address.
  but also if i ping from within my local lan network
  dig and nslookup do a resolve to my local ip.
  But ping and applications like openvpn and libvirt cant connect to the local 
application.

  I worked around it by registering two sub domains at
  freedns.afraid.org those are resolved correctly to the local IP
  address.

  No logs due to privacy.

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


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

[Kernel-packages] [Bug 1961632] [NEW] linux-azure: Case VM fails to initialize CX4 VF due to mem fragmentation

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]

Below are the kernel messages showing the VF being removed at 12:21:35,
and then being re-added starting at 12:22:44. You can see the stack
traces trying to make an order 7 allocation, and then and order 8
allocation, both of which fail.

[Sun Jan 23 12:21:34 2022] infiniband mlx5_0: wait_for_async_commands:745:(pid 
15782): done with all pending requests
[Sun Jan 23 12:21:35 2022] hv_netvsc 000d3a7c-6aa5-000d-3a7c-6aa5000d3a7c eth0: 
Data path switched from VF: eth1
[Sun Jan 23 12:21:35 2022] hv_netvsc 000d3a7c-6aa5-000d-3a7c-6aa5000d3a7c eth0: 
VF unregistering: eth1
[Sun Jan 23 12:22:44 2022] hv_pci 61367817-ab6d-44c7-8b57-457fcc1b66c2: PCI 
VMBus probing: Using version 0x10002
[Sun Jan 23 12:22:44 2022] hv_pci 61367817-ab6d-44c7-8b57-457fcc1b66c2: PCI 
host bridge to bus ab6d:00
[Sun Jan 23 12:22:44 2022] pci_bus ab6d:00: root bus resource [mem 
0xfe000-0xfe00f window]
[Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: [15b3:1016] type 00 class 0x02
[Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: reg 0x10: [mem 
0xfe000-0xfe00f 64bit pref]
[Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: 0.000 Gb/s available PCIe 
bandwidth, limited by Unknown speed x0 link at ab6d:00:02.0 (capable of 63.008 
Gb/s with 8 GT/s x8 link)
[Sun Jan 23 12:22:44 2022] pci ab6d:00:02.0: BAR 0: assigned [mem 
0xfe000-0xfe00f 64bit pref]
[Sun Jan 23 12:22:44 2022] mlx5_core ab6d:00:02.0: firmware version: 14.30.1210
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 24 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 25 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 26 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 27 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 28 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 29 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 30 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 31 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 32 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 33 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 34 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 35 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 36 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 37 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 38 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 39 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 40 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 41 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 42 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 43 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 44 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 45 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 46 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 47 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 48 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 49 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 50 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 51 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 52 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 53 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 54 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] mlx5_core ab6d:00:02.0: irq 55 for MSI/MSI-X
[Sun Jan 23 12:22:45 2022] kworker/18:1: page allocation failure: order:7, 
mode:0x80d0
[Sun Jan 23 12:22:45 2022] CPU: 18 PID: 11869 Comm: kworker/18:1 Kdump: loaded 
Tainted: G  T 3.10.0-1160.31.1.el7.x86_64 #1
[Sun Jan 23 12:22:45 2022] Hardware name: Microsoft Corporation Virtual 
Machine/Virtual Machine, BIOS 090008 12/07/2018
[Sun Jan 23 12:22:45 2022] Workqueue: hv_pri_chan vmbus_add_channel_work 
[hv_vmbus]
[Sun Jan 23 12:22:45 2022] Call Trace:
[Sun Jan 23 12:22:45 2022] [] dump_stack+0x19/0x1b
[Sun Jan 23 12:22:45 2022] [] warn_alloc_failed+0x110/0x180
[Sun Jan 23 12:22:45 2022] [] 
__alloc_pages_nodemask+0x9df/0xbe0
[Sun Jan 23 12:22:45 2022] [] 
dma_generic_alloc_coherent+0x8f/0x140
[Sun Jan 23 12:22:45 2022] [] 
x86_swiotlb_alloc_coherent+0x21/0x50
[Sun Jan 23 12:22:45 2022] [] 
mlx5_dma_zalloc_coherent_node+0xb4/0x110 [mlx5_core]
[Sun Jan 23 12:22:45 2022] [] mlx5_buf_alloc_node+0x89/0x120 
[mlx5_core]
[Sun Jan 23 12:22:45 2022] [] mlx5_buf_alloc+0x14/0x20 
[mlx5_core]
[Sun Jan 23 12:22:45 2022] [] create_map_eq+0xcb/0x3c0 
[mlx5_core]
[Sun Jan 23 12:22:45 2022] [] create_async_eq+0x5a/0x80 
[mlx5_core]
[Sun Jan 23 12:22:45 2022] [] 
mlx5_eq_table_create+0x1a5/0x7e0 [

[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules

[Clement Cherlin]

** Description changed:

  Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
  Distribution: Ubuntu 21.10 (impish)
  
  I run an Ubuntu desktop as a VMWare virtual machine client.
  
  The linux-modules-extra-${VERSION}-generic package contains
  kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to keep
  it installed and updated. The only way to do so conveniently is to
  install linux-image-generic, which also pulls in linux-firmware, which
  is ~760MB installed.
  
  If vmwgfx was moved from linux-modules-extra to linux-modules, I could
  use linux-image-virtual instead of linux-image-generic, remove linux-
  firmware, linux-modules-extra, and the microcode packages, saving
  substantial disk space and bandwidth.
  
  Other virtual graphics drivers in linux-modules-extra that might be
  worth moving are:
  
  kernel/drivers/gpu/drm/bochs/bochs-drm.ko
  kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  
  Thank you for your consideration.
  
  Note: Edited significantly in response to
  https://lists.ubuntu.com/archives/kernel-team/2022-February/128103.html
- to better reflect the underlying problem and solution.
+ and https://lists.ubuntu.com/archives/kernel-
+ team/2022-February/128104.html to better reflect the underlying problem
+ and solution.
  
  P.S. There are three other drivers in linux-modules-extra that seem
  VMWare-related, but they are not in use in my VM and I don't know
  whether they are in common enough use to justify moving them to linux-
  modules. I have listed them here for completeness.
  
  kernel/drivers/net/vsockmon.ko
  kernel/drivers/ptp/ptp_vmw.ko
  kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   1645 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-01-05 (405 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.
  
   ens33 no wireless extensions.
  
   docker0   no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-28-generic N/A
   linux-backports-modules-5.13.0-28-generic  N/A
   linux-firmware 1.201.3
  RfKill:
  
  Tags:  impish
  Uname: Linux 5.13.0-28-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

Title:
  Move virtual graphics drivers from linux-modules-extra to linux-
  modules

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
  Distribution: Ubuntu 21.10 (impish)

  I run an Ubuntu desktop as a VMWare virtual machine client.

  The linux-modules-extra-${VERSION}-generic package contains
  kernel

[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules

[Clement Cherlin]

** Description changed:

  Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
  Distribution: Ubuntu 21.10 (impish)
  
  I run an Ubuntu desktop as a VMWare virtual machine client.
  
- The linux-modules-extra-${VERSION}-generic package contains several
- critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to keep
- it installed and updated.
+ The linux-modules-extra-${VERSION}-generic package contains
+ kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to keep
+ it installed and updated. The only way to do so conveniently is to
+ install linux-image-generic, which also pulls in linux-firmware, which
+ is ~760MB installed.
  
- Since it is a virtual machine, there is no need to install packages such
- as linux-firmware (761MB uncompressed). I would prefer to remove linux-
- firmware to reduce disk space and bandwidth usage, but linux-image-
- generic depends on it.
+ If vmwgfx was moved from linux-modules-extra to linux-modules, I could
+ use linux-image-virtual instead of linux-image-generic, remove linux-
+ firmware, linux-modules-extra, and the microcode packages, saving
+ substantial disk space and bandwidth.
  
- I would remove linux-image-generic and rely on linux-image-virtual, but
- linux-image-virtual does not depend on linux-modules-
- extra-${VERSION}-generic, and there is no linux-modules-extra-generic
- metapackage. I would have to manually install linux-modules-
- extra-${VERSION}-generic every time I update the kernel.
+ Other virtual graphics drivers in linux-modules-extra that might be
+ worth moving are:
  
- There are already linux-modules-extra-aws, linux-modules-extra-gcp and
- linux-modules-extra-gke metapackages which fulfill the same purpose for
- their respective linux-modules-extra-${VERSION}-xxx packages. It would
- be very helpful to me (and, I'm sure, many others) to complete the set
- with a linux-modules-extra-generic metapackage that would depend on the
- latest linux-modules-extra-${VERSION}-generic.
+ kernel/drivers/gpu/drm/bochs/bochs-drm.ko
+ kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
+ kernel/drivers/gpu/drm/xen/drm_xen_front.ko
  
  Thank you for your consideration.
- --- 
+ 
+ Note: Edited significantly in response to
+ https://lists.ubuntu.com/archives/kernel-team/2022-February/128103.html
+ to better reflect the underlying problem and solution.
+ 
+ P.S. There are three other drivers in linux-modules-extra that seem
+ VMWare-related, but they are not in use in my VM and I don't know
+ whether they are in common enough use to justify moving them to linux-
+ modules. I have listed them here for completeness.
+ 
+ kernel/drivers/net/vsockmon.ko
+ kernel/drivers/ptp/ptp_vmw.ko
+ kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ccherlin   1645 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ccherlin   1645 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-01-05 (405 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
-  lono wireless extensions.
-  
-  ens33 no wireless extensions.
-  
-  docker0   no wireless extensions.
+  lono wireless extensions.
+ 
+  ens33 no wireless extensions.
+ 
+  docker0   no wireless extensions.
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
-  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
+  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
-  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
-  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
-  |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
-  TERM=screen-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13

[Kernel-packages] [Bug 1960633] Re: Move virtual graphics drivers from linux-modules-extra to linux-modules

[Clement Cherlin]

** Summary changed:

- Move VMWare drivers from linux-modules-extra to linux-modules
+ Move virtual graphics drivers from linux-modules-extra to linux-modules

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

Title:
  Move virtual graphics drivers from linux-modules-extra to linux-
  modules

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
  Distribution: Ubuntu 21.10 (impish)

  I run an Ubuntu desktop as a VMWare virtual machine client.

  The linux-modules-extra-${VERSION}-generic package contains
  kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko, so at the moment I need to
  keep it installed and updated. The only way to do so conveniently is
  to install linux-image-generic, which also pulls in linux-firmware,
  which is ~760MB installed.

  If vmwgfx was moved from linux-modules-extra to linux-modules, I could
  use linux-image-virtual instead of linux-image-generic, remove linux-
  firmware, linux-modules-extra, and the microcode packages, saving
  substantial disk space and bandwidth.

  Other virtual graphics drivers in linux-modules-extra that might be
  worth moving are:

  kernel/drivers/gpu/drm/bochs/bochs-drm.ko
  kernel/drivers/gpu/drm/virtio/virtio-gpu.ko
  kernel/drivers/gpu/drm/xen/drm_xen_front.ko

  Thank you for your consideration.

  Note: Edited significantly in response to
  https://lists.ubuntu.com/archives/kernel-
  team/2022-February/128103.html to better reflect the underlying
  problem and solution.

  P.S. There are three other drivers in linux-modules-extra that seem
  VMWare-related, but they are not in use in my VM and I don't know
  whether they are in common enough use to justify moving them to linux-
  modules. I have listed them here for completeness.

  kernel/drivers/net/vsockmon.ko
  kernel/drivers/ptp/ptp_vmw.ko
  kernel/drivers/infiniband/hw/vmw_pvrdma/vmw_pvrdma.ko

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   1645 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-01-05 (405 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.

   ens33 no wireless extensions.

   docker0   no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-28-generic N/A
   linux-backports-modules-5.13.0-28-generic  N/A
   linux-firmware 1.201.3
  RfKill:

  Tags:  impish
  Uname: Linux 5.13.0-28-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Kernel-packages] [Bug 1960633] Re: Create linux-modules-extra-generic metapackage

[Clement Cherlin]

Edited significantly in response to
https://lists.ubuntu.com/archives/kernel-team/2022-February/128103.html
to better reflect the underlying problem and solution.

** Summary changed:

- Create linux-modules-extra-generic metapackage
+ Move VMWare drivers from linux-modules-extra to linux-modules

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

Title:
  Move VMWare drivers from linux-modules-extra to linux-modules

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel: Ubuntu 5.13.0-28.31-generic 5.13.19
  Distribution: Ubuntu 21.10 (impish)

  I run an Ubuntu desktop as a VMWare virtual machine client.

  The linux-modules-extra-${VERSION}-generic package contains several
  critical VMWare drivers (vmwgfx, vmw_vmci, vmw_vsock), so I need to
  keep it installed and updated.

  Since it is a virtual machine, there is no need to install packages
  such as linux-firmware (761MB uncompressed). I would prefer to remove
  linux-firmware to reduce disk space and bandwidth usage, but linux-
  image-generic depends on it.

  I would remove linux-image-generic and rely on linux-image-virtual,
  but linux-image-virtual does not depend on linux-modules-
  extra-${VERSION}-generic, and there is no linux-modules-extra-generic
  metapackage. I would have to manually install linux-modules-
  extra-${VERSION}-generic every time I update the kernel.

  There are already linux-modules-extra-aws, linux-modules-extra-gcp and
  linux-modules-extra-gke metapackages which fulfill the same purpose
  for their respective linux-modules-extra-${VERSION}-xxx packages. It
  would be very helpful to me (and, I'm sure, many others) to complete
  the set with a linux-modules-extra-generic metapackage that would
  depend on the latest linux-modules-extra-${VERSION}-generic.

  Thank you for your consideration.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ccherlin   1645 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-01-05 (405 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  IwConfig:
   lono wireless extensions.
   
   ens33 no wireless extensions.
   
   docker0   no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 
zswap.compressor=lz4
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-28-generic N/A
   linux-backports-modules-5.13.0-28-generic  N/A
   linux-firmware 1.201.3
  RfKill:
   
  Tags:  impish
  Uname: Linux 5.13.0-28-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-18 (118 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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


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

[Kernel-packages] [Bug 1959762] Re: HID_ASUS should depend on USB_HID in stable v4.15 backports

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux/4.15.0-170.178 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  HID_ASUS should depend on USB_HID in stable v4.15 backports

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Backported to bionic/linux commit f83baa0cb6cf ("HID: add hid_is_usb() 
function to make it simpler for USB detection") brings to HID_ASUS usage of 
hid_is_usb() which is provided by USB_HID.  If HID_ASUS is built as module but 
USB_HID is not, the kernel build will fail (like linux-azure) did:
    ERROR: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!

  [Fix]

  Because of backport of commit commit f83baa0cb6cf ("HID: add
  hid_is_usb() function to make it simpler for USB detection"), the
  bionic/linux needs also backport of commit c4f0126d487f ("HID: asus:
  Add depends on USB_HID to HID_ASUS Kconfig option").

  [Test Plan]

  Build HID_ASUS as module with or without USB_HID.

  [Where problems could occur]

  It's a new KConfig dependency, so configs using HID_ASUS without
  USB_HID will loose HID_ASUS. This is expected, so no problems should
  occur.

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


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

[Kernel-packages] [Bug 1960083] Re: dirname applet missing from initramfs

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 2.1.2-1ubuntu3

---
zfs-linux (2.1.2-1ubuntu3) jammy; urgency=medium

  * Apply pending stable updates with bug fixes and v5.16, v5.17 compat.
  * Add breaks to ensure that busybox with dirname is required for
zfs-initramfs. LP: #1960083

 -- Dimitri John Ledkov   Mon, 21 Feb 2022
15:12:27 +

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

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

Title:
  dirname applet missing from initramfs

Status in busybox package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  The initramfs is currently being built without the dirname applet.
  This is causing issues with zfs encrypted devices, as cryptsetup is
  attempting to use dirname to determine the location of the system key.
  This results in the following error:

  /init: line 971: dirname: not found

  followed by a prompt that is missing the zpool name. For example

  "Please unlock disk keystore-" rather than "Please unlock disk
  keystore-rpool".

  After entering the password, the user is dropped to an initramfs
  shell.

  It appears that this was caused by a change in cryptsetup to suddenly
  need dirname to function properly.

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


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

[Kernel-packages] [Bug 1959085] Re: Ubuntu 21.10 boot stuck in initramfs

[Alan Baghumian]

I confirmed this is happening. Here are two ways to reproduce:

1) Grabbed jammy-desktop-amd64.iso nightly build (Feb 2). Installing a
system using this ISO, while choosing Encryption + ZFS lands you on this
error.

2) Installed Impish using an ISO from October 12, choosing Encryption +
ZFS. The system installs and boots up w/o any issues. Performed a dist-
upgrade to Jammy, which resulted the system booting into initramfs with
the exact same error.

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

Title:
  Ubuntu 21.10 boot stuck in initramfs

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

Bug description:
  Hi,

  I just installed the latest Ubuntu desktop from iso file
  ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose
  ZFS and native ZFS encryption of the filesystem. The installation went
  fine. Everything worked as expected.

  Then I upgraded the packages to the latest version via the Software
  updater. After reboot I'm stuck in the initramfs prompt. The following
  command fails:

  mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root//

  Permission denied.

  And the system never asks me for the password to unlock the root fs.

  So, I'm guessing that there is something wrong with the new initramfs
  disk: initrd.img-5.13.0-27-generic

  When I reboot and select the previous version in grub:
  initrd.img-5.13.0-27-generic, the system asks for the password and
  boots without a problem.

  Thanks.

  To summarize:

  1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. 
Minimal install.
  2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted 
and failed to boot the new version.

  I didn't customize anything or installed anything extra.

  root@ubud01:/var# lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  root@ubud01:/var# dpkg -l | grep zfs
  ii  libzfs4linux   2.0.6-1ubuntu2 
amd64OpenZFS filesystem library for Linux
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs
  ii  zfs-zed2.0.6-1ubuntu2 
amd64OpenZFS Event Daemon
  ii  zfsutils-linux 2.0.6-1ubuntu2 
amd64command-line tools to manage OpenZFS filesystems

  root@ubud01:/var# dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-6ubuntu3.1
amd64Standalone shell setup for initramfs
  ii  cryptsetup-initramfs   2:2.3.6-0ubuntu1   
all  disk encryption support - initramfs integration
  ii  gnome-initial-setup40.4-1ubuntu1  
amd64Initial GNOME system setup helper
  ii  init   1.60build1 
amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.60build1 
all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu6   
all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu6   
amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu6   
all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.4-1.1ubuntu3.1 
amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.8-6.1ubuntu2   
amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu3  
all  Linux Standard Base init script functionality
  ii  ncurses-base   6.2+20201114-2build1   
all  basic terminal type definitions
  ii  sysvinit-utils 2.96-7ubuntu1  
amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu3 
amd64X server initialisation tool
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs

  root@ubud01:/var# zfs list
  NAME   USED  AVAIL REF

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

[Ubuntu Kernel Bot]

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

apport-collect 1961622

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

Title:
  Wire Network Adapter Stop Working After Kernel Update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  lspci -nnk

  00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Lenovo 8 Series/C220 Series Chipset Family MEI Controller 
[17aa:309f]
Kernel driver in use: mei_me

  SysLog Output:

  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6264] 
device (eno1): Activation: starting connection 'Conexión cableada 1' 
(2758aa8f-5775-4404-8258-83760e13bc80)
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6266] 
audit: op="connection-activate" uuid="2758aa8f-5775-4404-8258-83760e13bc80" 
name="Conexión cableada 1" pid=1854 uid=1000 result="success"
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6270] 
device (eno1): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6279] 
device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 
'managed')
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6392] 
device (eno1): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6395] 
dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6406] 
dhcp4 (eno1): dhclient started with pid 7899
  Feb 21 12:30:47 black-pearl avahi-daemon[852]: Joining mDNS multicast group 
on interface eno1.IPv6 with address fe80::7d12:bae5:fccc:c841.
  Feb 21 12:30:47 black-pearl avahi-daemon[852]: New relevant interface 
eno1.IPv6 for mDNS.
  Feb 21 12:30:47 black-pearl avahi-daemon[852]: Registering new address record 
for fe80::7d12:bae5:fccc:c841 on eno1.*.
  Feb 21 12:30:47 black-pearl dhclient[7899]: DHCPREQUEST of 10.10.144.150 on 
eno1 to 255.255.255.255 port 67 (xid=0x6c31fad1)
  Feb 21 12:30:57 black-pearl dhclient[7899]: message repeated 2 times: [ 
DHCPREQUEST of 10.10.144.150 on eno1 to 255.255.255.255 port 67 
(xid=0x6c31fad1)]
  Feb 21 12:31:07 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 3 (xid=0xb315ff2c)
  Feb 21 12:31:10 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 5 (xid=0xb315ff2c)
  Feb 21 12:31:15 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 11 (xid=0xb315ff2c)
  Feb 21 12:31:26 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 11 (xid=0xb315ff2c)
  Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.2903] 
dhcp4 (eno1): request timed out
  Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.2904] 
dhcp4 (eno1): state changed unknown -> timeout
  Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3226] 
dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 7899
  Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3226] 
dhcp4 (eno1): state changed timeout -> done
  Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3228] 
device (eno1): state change: ip-config -> failed (reason 
'ip-config-unavailable', sys-iface-state: 'managed')
  Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3231] 
device (eno1): Activation: failed for connection 'Conexión cableada 1'
  Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3235] 
device (eno1): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
  Feb 21 12:31:33 black-pearl avahi-daemon[852]: Withdrawing address record for 
fe80::7d12:bae5:fccc:c841 on eno1.
  Feb 21 12:31:33 black-pearl avahi-daemon[852]: Leaving mDNS multicast group 
on interface eno1.IPv6 with address fe80::7d12:bae5:fccc:c841.
  Feb 21 12:31:33 black-pearl avahi-daemon[852]: Interface eno1.IPv6 no longer 
relevant for mDNS.

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


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

[Kernel-packages] [Bug 1961622] [NEW] Wire Network Adapter Stop Working After Kernel Update

[pichel30]

Public bug reported:

lspci -nnk

00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Lenovo 8 Series/C220 Series Chipset Family MEI Controller 
[17aa:309f]
Kernel driver in use: mei_me

SysLog Output:

Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6264] 
device (eno1): Activation: starting connection 'Conexión cableada 1' 
(2758aa8f-5775-4404-8258-83760e13bc80)
Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6266] 
audit: op="connection-activate" uuid="2758aa8f-5775-4404-8258-83760e13bc80" 
name="Conexión cableada 1" pid=1854 uid=1000 result="success"
Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6270] 
device (eno1): state change: disconnected -> prepare (reason 'none', 
sys-iface-state: 'managed')
Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6279] 
device (eno1): state change: prepare -> config (reason 'none', sys-iface-state: 
'managed')
Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6392] 
device (eno1): state change: config -> ip-config (reason 'none', 
sys-iface-state: 'managed')
Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6395] 
dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6406] 
dhcp4 (eno1): dhclient started with pid 7899
Feb 21 12:30:47 black-pearl avahi-daemon[852]: Joining mDNS multicast group on 
interface eno1.IPv6 with address fe80::7d12:bae5:fccc:c841.
Feb 21 12:30:47 black-pearl avahi-daemon[852]: New relevant interface eno1.IPv6 
for mDNS.
Feb 21 12:30:47 black-pearl avahi-daemon[852]: Registering new address record 
for fe80::7d12:bae5:fccc:c841 on eno1.*.
Feb 21 12:30:47 black-pearl dhclient[7899]: DHCPREQUEST of 10.10.144.150 on 
eno1 to 255.255.255.255 port 67 (xid=0x6c31fad1)
Feb 21 12:30:57 black-pearl dhclient[7899]: message repeated 2 times: [ 
DHCPREQUEST of 10.10.144.150 on eno1 to 255.255.255.255 port 67 
(xid=0x6c31fad1)]
Feb 21 12:31:07 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 3 (xid=0xb315ff2c)
Feb 21 12:31:10 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 5 (xid=0xb315ff2c)
Feb 21 12:31:15 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 11 (xid=0xb315ff2c)
Feb 21 12:31:26 black-pearl dhclient[7899]: DHCPDISCOVER on eno1 to 
255.255.255.255 port 67 interval 11 (xid=0xb315ff2c)
Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.2903] 
dhcp4 (eno1): request timed out
Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.2904] 
dhcp4 (eno1): state changed unknown -> timeout
Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3226] 
dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 7899
Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3226] 
dhcp4 (eno1): state changed timeout -> done
Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3228] 
device (eno1): state change: ip-config -> failed (reason 
'ip-config-unavailable', sys-iface-state: 'managed')
Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3231] 
device (eno1): Activation: failed for connection 'Conexión cableada 1'
Feb 21 12:31:33 black-pearl NetworkManager[992]:   [1645468293.3235] 
device (eno1): state change: failed -> disconnected (reason 'none', 
sys-iface-state: 'managed')
Feb 21 12:31:33 black-pearl avahi-daemon[852]: Withdrawing address record for 
fe80::7d12:bae5:fccc:c841 on eno1.
Feb 21 12:31:33 black-pearl avahi-daemon[852]: Leaving mDNS multicast group on 
interface eno1.IPv6 with address fe80::7d12:bae5:fccc:c841.
Feb 21 12:31:33 black-pearl avahi-daemon[852]: Interface eno1.IPv6 no longer 
relevant for mDNS.

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

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

Title:
  Wire Network Adapter Stop Working After Kernel Update

Status in linux package in Ubuntu:
  New

Bug description:
  lspci -nnk

  00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 
Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Lenovo 8 Series/C220 Series Chipset Family MEI Controller 
[17aa:309f]
Kernel driver in use: mei_me

  SysLog Output:

  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6264] 
device (eno1): Activation: starting connection 'Conexión cableada 1' 
(2758aa8f-5775-4404-8258-83760e13bc80)
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6266] 
audit: op="connection-activate" uuid="2758aa8f-5775-4404-8258-83760e13bc80" 
name="Conexión cableada 1" pid=1854 uid=1000 result="success"
  Feb 21 12:30:47 black-pearl NetworkManager[992]:   [1645468247.6270

[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

[Brian Murray]

** Changed in: makedumpfile (Ubuntu Groovy)
   Status: In Progress => Won't Fix

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

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kdump-tools package in Ubuntu:
  Fix Committed
Status in makedumpfile package in Ubuntu:
  Invalid
Status in kdump-tools source package in Focal:
  Invalid
Status in makedumpfile source package in Focal:
  In Progress
Status in kdump-tools source package in Groovy:
  Invalid
Status in makedumpfile source package in Groovy:
  Won't Fix

Bug description:
  Description:
  In case the volume containing the root filesystem is encrypted using LUKS2 
the memory used while unlocking the volume may exceed the size allocated to the 
kdump kernel. This will lead to a failure while processing kdump and the dump 
file will not be stored. Unfortunately, this condition may not be detected by a 
client before a problem occurs.
  The request is to have the kdump package installation script check for LUKS2 
encryption (more precisely for Argon2i PBKDF, which is the root cause of the 
high memory usage). If the condition is met, the installation procedure should 
increase the crashkernel parameter to a higher value (>=512M)or issue a 
warning, if the system memory is insufficient to reserve enough crashkernel 
memory.

  Business Case:
  Pervasive Encryption and Secure Execution require encryption of the 
filesystems in order to keep customer data secure at all times. With the 
increasing usage of these technologies, the number of kdump will rise too, 
typically at inconvenient times, when the kdump is triggered due to a real 
customer issue.
  With the suggested change, the number of customer complaints and effort to 
handle them will be reduced.

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


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

[Kernel-packages] [Bug 1949065] Re: Wireless-AC 9260 iwlwifi unstable and connection drops

[lotuspsychje]

@ Juerg #2

Now 22.04 reached kernel 5.15 my bug still persist the same
getting disconnects just as on 5.13

current kernel version is; 5.15.0-18-generic at 21/02/2022

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

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

Title:
  Wireless-AC 9260 iwlwifi unstable and connection drops

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Jammy:
  New

Bug description:
  Ubuntu 22.04 development branch @ 28/10/2021 with kernel
  5.13.0-19-generic

  My wifi with chipset Wireless-AC 9260 and iwlwifi are unstable and when 
browsing
  around the web a lot, i'm getting connections drops

  iwlwifi :02:00.0: No beacon heard and the time event is over
  already...

  and wlp2s0: Connection to AP 38:35:fb:19:91:da lost in journal logs


  driver=iwlwifi driverversion=5.13.0-19-generic firmware=46.6b541b68.0
  9260-th-b0-jf-b0-

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 1.202
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lotuspsychje   2310 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 28 11:23:52 2021
  Dependencies:
   
  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
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic 
root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.202
  SourcePackage: linux-firmware
  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:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  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-firmware/+bug/1949065/+subscriptions


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

[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Andrew Cloke]

** Changed in: kunpeng920/ubuntu-21.10
   Status: Fix Committed => Fix Released

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

Title:
  [uacc-0623] hisi_sec2  fail to alloc uacce

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-21.10 series:
  Fix Released
Status in kunpeng920 ubuntu-22.04 series:
  Fix Committed
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 Committed

Bug description:
  SRU Justification
  =

  [Impact]
  * Users with HiSilicon Security Engine (SEC) version 2 controller fail to 
allocate Uacce.

  [Fix]
  * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - 
modify the uacce mode check

  [Test Plan]
  * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with 
HiSilicon Security Engine (SEC) version 2 controller
  * Boot the system
  * 'dmesg | grep "fail to alloc uacce"' and you will see complains from 
hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc 
uacce (-22)

  [Where problems could occur]
  * The regression can be considered as low, since it is HiSilicon crypto 
system specific

  == Original Bug Description ==

  [Bug Description]

  ubuntu 20.04.2 boot system and fail to alloc uacce (-22)

  [Steps to Reproduce]
  1) boot ubuntu 20.04.2 system
  2) dmesg | grep fail

  [Actual Results]
  [   27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12
  [   27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID
  [   27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45
  [   27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22)

  [Expected Results]
  no fail
  [Reproducibility]
  100%

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):

  [Resolution]
  this following patches will solve this bug.

  commit f8408d2b79b834f79b6c578817e84f74a85d2190
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:42 2021 +0800

  crypto: hisilicon - add ZIP device using mode parameter

  Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1.
  '0' means ZIP is only registered to kernel crypto, and '1' means it's
  registered to both kernel crypto and UACCE.

  Signed-off-by: Kai Ye 
  Reviewed-by: Zhou Wang 
  Reviewed-by: Zaibo Xu 
  Signed-off-by: Herbert Xu 

  commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:43 2021 +0800

  crypto: hisilicon/hpre - register HPRE device to uacce

  commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:44 2021 +0800

  crypto: hisilicon/sec - register SEC device to uacce

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


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

[Kernel-packages] [Bug 1954938] Re: Include the QCA WCN 6856 v2.1 support

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP:
#1961191)

  * Packaging resync (LP: #1786013)
- [Config] Update config to match upstream stable release
- [Packaging] update variants

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
- ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

  * USB port lost function after unplugging usb drive (LP: #1958850)
- block: add disk sequence number
- mm: hide laptop_mode_wb_timer entirely behind the BDI API
- block: pass a gendisk to blk_queue_update_readahead
- block: add a queue_has_disk helper
- block: move the bdi from the request_queue to the gendisk
- block: remove the bd_bdi in struct block_device
- nvme: use blk_mq_alloc_disk
- st: do not allocate a gendisk
- sg: do not allocate a gendisk
- block: cleanup the lockdep handling in *alloc_disk
- block: remove alloc_disk and alloc_disk_node
- block: remove the minors argument to __alloc_disk_node
- block: pass a request_queue to __blk_alloc_disk
- block: hold a request_queue reference for the lifetime of struct gendisk
- block: add an explicit ->disk backpointer to the request_queue
- writeback: make the laptop_mode prototypes available unconditionally
- sg: pass the device name to blk_trace_setup
- block: factor out a blk_try_enter_queue helper
- block: drain file system I/O on del_gendisk
- block: keep q_usage_counter in atomic mode after del_gendisk
- block: drain queue after disk is removed from sysfs
- nvdimm/pmem: stop using q_usage_count as external pgmap refcount
- nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned

  * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
- iommu/amd: Restore GA log/tail pointer on host resume

 -- Timo Aaltonen   Thu, 17 Feb 2022
13:23:43 +0200

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

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

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

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

Title:
  Include the QCA WCN 6856 v2.1 support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WCN685x hw2.1 takes additional/updated firmware for both WiFi and
  Bluetooth function.

  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95

  [Fix]

  WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except
  for the directory path and a board-2.bin.

  For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from
  mainline are neccessary for Focal. Jammy has all of them already.

  For kernel, many of the prerequisite works have been committed for
  hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G
  will be turned off for the lack of userspace support, the only fix
  necessary is to correct read mask of version info register.

  ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14
  in bug 1939528, so only oem-5.14 has to be reverted.

  [Test Case]

  WiFi and Bluetooth devices should be up and running, pass basic
  operations.

  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

  [Where problems could occur]

  At the time being, WCN685x WiFi 6G support will be turnef off
  deliberately due to the lack

[Kernel-packages] [Bug 1952222] Re: io_uring regression - lost write request

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP:
#1961191)

  * Packaging resync (LP: #1786013)
- [Config] Update config to match upstream stable release
- [Packaging] update variants

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
- ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

  * USB port lost function after unplugging usb drive (LP: #1958850)
- block: add disk sequence number
- mm: hide laptop_mode_wb_timer entirely behind the BDI API
- block: pass a gendisk to blk_queue_update_readahead
- block: add a queue_has_disk helper
- block: move the bdi from the request_queue to the gendisk
- block: remove the bd_bdi in struct block_device
- nvme: use blk_mq_alloc_disk
- st: do not allocate a gendisk
- sg: do not allocate a gendisk
- block: cleanup the lockdep handling in *alloc_disk
- block: remove alloc_disk and alloc_disk_node
- block: remove the minors argument to __alloc_disk_node
- block: pass a request_queue to __blk_alloc_disk
- block: hold a request_queue reference for the lifetime of struct gendisk
- block: add an explicit ->disk backpointer to the request_queue
- writeback: make the laptop_mode prototypes available unconditionally
- sg: pass the device name to blk_trace_setup
- block: factor out a blk_try_enter_queue helper
- block: drain file system I/O on del_gendisk
- block: keep q_usage_counter in atomic mode after del_gendisk
- block: drain queue after disk is removed from sysfs
- nvdimm/pmem: stop using q_usage_count as external pgmap refcount
- nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned

  * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
- iommu/amd: Restore GA log/tail pointer on host resume

 -- Timo Aaltonen   Thu, 17 Feb 2022
13:23:43 +0200

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

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

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

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

Title:
  io_uring regression - lost write request

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

Bug description:
  There's a regression with io_uring reported against 5.11-5.14 kernels,
  see:

  https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_-
  
ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b

  From reading the thread and looking at the history in 
linux-stable/linux-5.15.y,
  I assume that Linux 5.15.3 is the first fully fixed version.
  And 5.10 was not affected.

  Sadly all other versions are EOL for kernel.org.

  But ubuntu provides 5.11, 5.13 and 5.14 based kernels,
  which most likely have the bug.

  I'm reporting it against linux-hwe-5.13 as that's what I test on most systems,
  but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem.

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


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

[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP:
#1961191)

  * Packaging resync (LP: #1786013)
- [Config] Update config to match upstream stable release
- [Packaging] update variants

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
- ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

  * USB port lost function after unplugging usb drive (LP: #1958850)
- block: add disk sequence number
- mm: hide laptop_mode_wb_timer entirely behind the BDI API
- block: pass a gendisk to blk_queue_update_readahead
- block: add a queue_has_disk helper
- block: move the bdi from the request_queue to the gendisk
- block: remove the bd_bdi in struct block_device
- nvme: use blk_mq_alloc_disk
- st: do not allocate a gendisk
- sg: do not allocate a gendisk
- block: cleanup the lockdep handling in *alloc_disk
- block: remove alloc_disk and alloc_disk_node
- block: remove the minors argument to __alloc_disk_node
- block: pass a request_queue to __blk_alloc_disk
- block: hold a request_queue reference for the lifetime of struct gendisk
- block: add an explicit ->disk backpointer to the request_queue
- writeback: make the laptop_mode prototypes available unconditionally
- sg: pass the device name to blk_trace_setup
- block: factor out a blk_try_enter_queue helper
- block: drain file system I/O on del_gendisk
- block: keep q_usage_counter in atomic mode after del_gendisk
- block: drain queue after disk is removed from sysfs
- nvdimm/pmem: stop using q_usage_count as external pgmap refcount
- nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned

  * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
- iommu/amd: Restore GA log/tail pointer on host resume

 -- Timo Aaltonen   Thu, 17 Feb 2022
13:23:43 +0200

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

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

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

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

Title:
  AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

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

Bug description:
  [SRU Justification]

  [Impact]

  On AMD Yellow Carp B0 platforms, S0i3 is still not working.

  [Fix]

  This denpends on a few fixes for kernel driver that are all either in
  v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed
  dmcub firmware.

  [Test Case]

  On AMD RMT CRB board,
  1. apply both kernel and firmware fixes
  2. module blacklist amd_sfh as it's still under development,
  3. trigger system suspend. Use power button to wake up the device.
  4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero

  On without any of above, the board may not cut device power during
  suspend, and/or fail to resume and leaving a blank screen, and/or s0ix
  stats remain all zeros.

  [Where problems could occur]

  On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't
  support S0ix and has to be disabled. For the kernel side, the driver
  fixes addressed a few procedure errors that should be unlikely to
  introduce regressions; for the firmware side, also tested loading new
  firmware on unpatched kernels and there is no difference found yet.

  [Other Info]

  For kernel driver fixes, patches for both oem-5.14 and jammy are
  necessary; for firmware, that has been available in jammy branch but
  not yet released, so only Focal will be nominated.

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


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

[Kernel-packages] [Bug 1958850] Re: USB port lost function after unplugging usb drive

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP:
#1961191)

  * Packaging resync (LP: #1786013)
- [Config] Update config to match upstream stable release
- [Packaging] update variants

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
- ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

  * USB port lost function after unplugging usb drive (LP: #1958850)
- block: add disk sequence number
- mm: hide laptop_mode_wb_timer entirely behind the BDI API
- block: pass a gendisk to blk_queue_update_readahead
- block: add a queue_has_disk helper
- block: move the bdi from the request_queue to the gendisk
- block: remove the bd_bdi in struct block_device
- nvme: use blk_mq_alloc_disk
- st: do not allocate a gendisk
- sg: do not allocate a gendisk
- block: cleanup the lockdep handling in *alloc_disk
- block: remove alloc_disk and alloc_disk_node
- block: remove the minors argument to __alloc_disk_node
- block: pass a request_queue to __blk_alloc_disk
- block: hold a request_queue reference for the lifetime of struct gendisk
- block: add an explicit ->disk backpointer to the request_queue
- writeback: make the laptop_mode prototypes available unconditionally
- sg: pass the device name to blk_trace_setup
- block: factor out a blk_try_enter_queue helper
- block: drain file system I/O on del_gendisk
- block: keep q_usage_counter in atomic mode after del_gendisk
- block: drain queue after disk is removed from sysfs
- nvdimm/pmem: stop using q_usage_count as external pgmap refcount
- nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned

  * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
- iommu/amd: Restore GA log/tail pointer on host resume

 -- Timo Aaltonen   Thu, 17 Feb 2022
13:23:43 +0200

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

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

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

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

Title:
  USB port lost function after unplugging usb drive

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

Bug description:
  [Impact]
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI

  [Fix]
  2a19b28f7929) blk-mq: cancel blk-mq dispatch work... is the first regression 
and it lands mainline since v5.16-rc2.

  After applied https://lore.kernel.org/all/20210816134624.ga24...@lst.de/#r, 
issue is gone.
  the patches has beend landed since v5.15-rc1.

  [Test Case]
  1. plug usb driver on the machine.
  2. unplug usb driver.
  3. check the dmesg if the oops would be shown

  [Where problems could occur]
  Medium
  ~~~
  Test the proposed 5.14 oem kernel, and get a failure symptom.

  Unplug a usb drive from WD19TB docking and a BUG reported in kernel,
  then the other embedded usb port can't detect usb drive anymore after
  a while.

  kernel: usb 5-2.3.3: USB disconnect, device number 5
  kernel: BUG: kernel NULL pointer dereference, address: 0030
  kernel: #PF: supervisor read access in kernel mode
  kernel: #PF: error_code(0x) - not-present page
  kernel: PGD 0 P4D 0
  kernel: Oops:  [#1] SMP NOPTI
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  2205 F pulseaudio
   /dev/snd/controlC0:  u  2205 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-04-29 (270 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsut

[Kernel-packages] [Bug 1959569] Re: Focal update: upstream stable patchset 2022-01-31

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP:
#1961191)

  * Packaging resync (LP: #1786013)
- [Config] Update config to match upstream stable release
- [Packaging] update variants

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
- ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

  * USB port lost function after unplugging usb drive (LP: #1958850)
- block: add disk sequence number
- mm: hide laptop_mode_wb_timer entirely behind the BDI API
- block: pass a gendisk to blk_queue_update_readahead
- block: add a queue_has_disk helper
- block: move the bdi from the request_queue to the gendisk
- block: remove the bd_bdi in struct block_device
- nvme: use blk_mq_alloc_disk
- st: do not allocate a gendisk
- sg: do not allocate a gendisk
- block: cleanup the lockdep handling in *alloc_disk
- block: remove alloc_disk and alloc_disk_node
- block: remove the minors argument to __alloc_disk_node
- block: pass a request_queue to __blk_alloc_disk
- block: hold a request_queue reference for the lifetime of struct gendisk
- block: add an explicit ->disk backpointer to the request_queue
- writeback: make the laptop_mode prototypes available unconditionally
- sg: pass the device name to blk_trace_setup
- block: factor out a blk_try_enter_queue helper
- block: drain file system I/O on del_gendisk
- block: keep q_usage_counter in atomic mode after del_gendisk
- block: drain queue after disk is removed from sysfs
- nvdimm/pmem: stop using q_usage_count as external pgmap refcount
- nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned

  * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
- iommu/amd: Restore GA log/tail pointer on host resume

 -- Timo Aaltonen   Thu, 17 Feb 2022
13:23:43 +0200

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

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

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

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

Title:
  Focal update: upstream stable patchset 2022-01-31

Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

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:

 upstream stable patchset 2022-01-31
 from git://git.kernel.org/

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


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

[Kernel-packages] [Bug 1960771] Re: Use EC GPE for s2idle wakeup on AMD platforms

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP:
#1961191)

  * Packaging resync (LP: #1786013)
- [Config] Update config to match upstream stable release
- [Packaging] update variants

  * CVE-2022-0435
- tipc: improve size validations for received domain records

  * CVE-2022-0492
- cgroup-v1: Require capabilities to set release_agent

  * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
- ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

  * USB port lost function after unplugging usb drive (LP: #1958850)
- block: add disk sequence number
- mm: hide laptop_mode_wb_timer entirely behind the BDI API
- block: pass a gendisk to blk_queue_update_readahead
- block: add a queue_has_disk helper
- block: move the bdi from the request_queue to the gendisk
- block: remove the bd_bdi in struct block_device
- nvme: use blk_mq_alloc_disk
- st: do not allocate a gendisk
- sg: do not allocate a gendisk
- block: cleanup the lockdep handling in *alloc_disk
- block: remove alloc_disk and alloc_disk_node
- block: remove the minors argument to __alloc_disk_node
- block: pass a request_queue to __blk_alloc_disk
- block: hold a request_queue reference for the lifetime of struct gendisk
- block: add an explicit ->disk backpointer to the request_queue
- writeback: make the laptop_mode prototypes available unconditionally
- sg: pass the device name to blk_trace_setup
- block: factor out a blk_try_enter_queue helper
- block: drain file system I/O on del_gendisk
- block: keep q_usage_counter in atomic mode after del_gendisk
- block: drain queue after disk is removed from sysfs
- nvdimm/pmem: stop using q_usage_count as external pgmap refcount
- nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned

  * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
- iommu/amd: Restore GA log/tail pointer on host resume

 -- Timo Aaltonen   Thu, 17 Feb 2022
13:23:43 +0200

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

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

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

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

Title:
  Use EC GPE for s2idle wakeup on AMD platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 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 source package in Jammy:
  Confirmed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Opening lid doesn't wakeup some AMD platforms from s2idle.

  [Fix]
  Use EC GPE for lid events to wakeup the laptops.

  [Test]
  Close and only the lid. The affected laptop now can be woken up by lid.

  [Where problems could occur]
  The original issue was later fixed by "pinctrl: amd: Fix wakeups when
  IRQ is shared with SCI". However, EC GPE is prone to cause spurious
  wakeup, so we still need to keep an eye on the regression reports.

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


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

[Kernel-packages] [Bug 1958252] Re: Support networking XDP

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.13.0-1014.16

---
linux-azure (5.13.0-1014.16) impish; urgency=medium

  * impish/linux-azure: 5.13.0-1014.16 -proposed tracker (LP: #1960044)

  * linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] azure: CONFIG_FB_EFI=y

  * Add sunrpc module parameters for NFSv3 nconnect (LP: #1958990)
- SAUCE: Add sunrpc module parameters for NFSv3 nconnect

  * MANA updates (LP: #1959012)
- net: mana: Add RX fencing
- net: mana: Fix memory leak in mana_hwc_create_wq

  * Enable arm64 for Hyper-V guests (LP: #1949770)
- [Packaging] linux-azure: Add basic packaging support for arm64
- [Config] azure: CONFIG_CMA=n [arm64]
- Drivers: hv: Move Hyper-V extended capability check to arch neutral code
- asm-generic/hyperv: Add missing #include of nmi.h
- Drivers: hv: Make portions of Hyper-V init code be arch neutral
- Drivers: hv: Add arch independent default functions for some Hyper-V
  handlers
- kernel.h: split out panic and oops helpers
- Drivers: hv: Move Hyper-V misc functionality to arch-neutral code
- drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers
- arm64: hyperv: Add Hyper-V hypercall and register access utilities
- arm64: hyperv: Add panic handler
- arm64: hyperv: Initialize hypervisor on boot
- arm64: efi: Export screen_info
- Drivers: hv: Enable Hyper-V code to be built on ARM64
- PCI: hv: Support for create interrupt v3
- PCI: Introduce domain_nr in pci_host_bridge
- PCI: Support populating MSI domains of root buses via bridges
- arm64: PCI: Restructure pcibios_root_bridge_prepare()
- arm64: PCI: Support root bridge preparation for Hyper-V
- PCI: hv: Generify PCI probing
- PCI: hv: Set ->domain_nr of pci_host_bridge at probing time
- PCI: hv: Turn on the host bridge probing on ARM64
- PCI: hv: Set up MSI domain at bridge probing time
- arm64: smccc: Add support for SMCCCv1.2 extended input/output registers
- [Config] azure: Ignore initial arm64 ABI
- PCI: hv: Make the code arch neutral by adding arch specific interfaces
- PCI: hv: Add arm64 Hyper-V vPCI support
- [Config] azure: Update arm64 policy for CONFIG_PCI_HYPERV

  * Support networking XDP (LP: #1958252)
- net: mana: Use kcalloc() instead of kzalloc()
- net: mana: Allow setting the number of queues while the NIC is down
- net: mana: Fix the netdev_err()'s vPort argument in mana_init_port()
- net: mana: Report OS info to the PF driver
- net: mana: Improve the HWC error handling
- net: mana: Support hibernation and kexec
- net: mana: Fix spelling mistake "calledd" -> "called"
- net: mana: Add XDP support

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after la

[Kernel-packages] [Bug 1958990] Re: Add sunrpc module parameters for NFSv3 nconnect

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.13.0-1014.16

---
linux-azure (5.13.0-1014.16) impish; urgency=medium

  * impish/linux-azure: 5.13.0-1014.16 -proposed tracker (LP: #1960044)

  * linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] azure: CONFIG_FB_EFI=y

  * Add sunrpc module parameters for NFSv3 nconnect (LP: #1958990)
- SAUCE: Add sunrpc module parameters for NFSv3 nconnect

  * MANA updates (LP: #1959012)
- net: mana: Add RX fencing
- net: mana: Fix memory leak in mana_hwc_create_wq

  * Enable arm64 for Hyper-V guests (LP: #1949770)
- [Packaging] linux-azure: Add basic packaging support for arm64
- [Config] azure: CONFIG_CMA=n [arm64]
- Drivers: hv: Move Hyper-V extended capability check to arch neutral code
- asm-generic/hyperv: Add missing #include of nmi.h
- Drivers: hv: Make portions of Hyper-V init code be arch neutral
- Drivers: hv: Add arch independent default functions for some Hyper-V
  handlers
- kernel.h: split out panic and oops helpers
- Drivers: hv: Move Hyper-V misc functionality to arch-neutral code
- drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers
- arm64: hyperv: Add Hyper-V hypercall and register access utilities
- arm64: hyperv: Add panic handler
- arm64: hyperv: Initialize hypervisor on boot
- arm64: efi: Export screen_info
- Drivers: hv: Enable Hyper-V code to be built on ARM64
- PCI: hv: Support for create interrupt v3
- PCI: Introduce domain_nr in pci_host_bridge
- PCI: Support populating MSI domains of root buses via bridges
- arm64: PCI: Restructure pcibios_root_bridge_prepare()
- arm64: PCI: Support root bridge preparation for Hyper-V
- PCI: hv: Generify PCI probing
- PCI: hv: Set ->domain_nr of pci_host_bridge at probing time
- PCI: hv: Turn on the host bridge probing on ARM64
- PCI: hv: Set up MSI domain at bridge probing time
- arm64: smccc: Add support for SMCCCv1.2 extended input/output registers
- [Config] azure: Ignore initial arm64 ABI
- PCI: hv: Make the code arch neutral by adding arch specific interfaces
- PCI: hv: Add arm64 Hyper-V vPCI support
- [Config] azure: Update arm64 policy for CONFIG_PCI_HYPERV

  * Support networking XDP (LP: #1958252)
- net: mana: Use kcalloc() instead of kzalloc()
- net: mana: Allow setting the number of queues while the NIC is down
- net: mana: Fix the netdev_err()'s vPort argument in mana_init_port()
- net: mana: Report OS info to the PF driver
- net: mana: Improve the HWC error handling
- net: mana: Support hibernation and kexec
- net: mana: Fix spelling mistake "calledd" -> "called"
- net: mana: Add XDP support

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after la

[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.13.0-1014.16

---
linux-azure (5.13.0-1014.16) impish; urgency=medium

  * impish/linux-azure: 5.13.0-1014.16 -proposed tracker (LP: #1960044)

  * linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] azure: CONFIG_FB_EFI=y

  * Add sunrpc module parameters for NFSv3 nconnect (LP: #1958990)
- SAUCE: Add sunrpc module parameters for NFSv3 nconnect

  * MANA updates (LP: #1959012)
- net: mana: Add RX fencing
- net: mana: Fix memory leak in mana_hwc_create_wq

  * Enable arm64 for Hyper-V guests (LP: #1949770)
- [Packaging] linux-azure: Add basic packaging support for arm64
- [Config] azure: CONFIG_CMA=n [arm64]
- Drivers: hv: Move Hyper-V extended capability check to arch neutral code
- asm-generic/hyperv: Add missing #include of nmi.h
- Drivers: hv: Make portions of Hyper-V init code be arch neutral
- Drivers: hv: Add arch independent default functions for some Hyper-V
  handlers
- kernel.h: split out panic and oops helpers
- Drivers: hv: Move Hyper-V misc functionality to arch-neutral code
- drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers
- arm64: hyperv: Add Hyper-V hypercall and register access utilities
- arm64: hyperv: Add panic handler
- arm64: hyperv: Initialize hypervisor on boot
- arm64: efi: Export screen_info
- Drivers: hv: Enable Hyper-V code to be built on ARM64
- PCI: hv: Support for create interrupt v3
- PCI: Introduce domain_nr in pci_host_bridge
- PCI: Support populating MSI domains of root buses via bridges
- arm64: PCI: Restructure pcibios_root_bridge_prepare()
- arm64: PCI: Support root bridge preparation for Hyper-V
- PCI: hv: Generify PCI probing
- PCI: hv: Set ->domain_nr of pci_host_bridge at probing time
- PCI: hv: Turn on the host bridge probing on ARM64
- PCI: hv: Set up MSI domain at bridge probing time
- arm64: smccc: Add support for SMCCCv1.2 extended input/output registers
- [Config] azure: Ignore initial arm64 ABI
- PCI: hv: Make the code arch neutral by adding arch specific interfaces
- PCI: hv: Add arm64 Hyper-V vPCI support
- [Config] azure: Update arm64 policy for CONFIG_PCI_HYPERV

  * Support networking XDP (LP: #1958252)
- net: mana: Use kcalloc() instead of kzalloc()
- net: mana: Allow setting the number of queues while the NIC is down
- net: mana: Fix the netdev_err()'s vPort argument in mana_init_port()
- net: mana: Report OS info to the PF driver
- net: mana: Improve the HWC error handling
- net: mana: Support hibernation and kexec
- net: mana: Fix spelling mistake "calledd" -> "called"
- net: mana: Add XDP support

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after la

[Kernel-packages] [Bug 1951011] Re: linux-aws: Make a signed kernel

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.13.0-1014.15

---
linux-aws (5.13.0-1014.15) impish; urgency=medium

  * impish/linux-aws: 5.13.0-1014.15 -proposed tracker (LP: #1960525)

  * linux-aws: Make a signed kernel (LP: #1951011)
- [Packaging] aws: Make a signed kernel

linux-aws (5.13.0-1013.14) impish; urgency=medium

  * impish/linux-aws: 5.13.0-1013.14 -proposed tracker (LP: #1960042)

  * tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
- [Packaging] aws: Include tcm_loop.ko

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1953689] Re: smartpqi: Update 20.04.4 to latest kernel.org patch level

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1941829] Re: ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests

[Launchpad Bug Tracker]

This bug was fixed in the package linux-meta-azure - 5.13.0.1014.14

---
linux-meta-azure (5.13.0.1014.14) impish; urgency=medium

  * Bump ABI 5.13.0-1014

  * Packaging resync (LP: #1786013)
- [Packaging] resync debian/dkms-versions from main package

  * Enable arm64 for Hyper-V guests (LP: #1949770)
- [Packaging] azure: Enable arm64

 -- Ian May   Fri, 11 Feb 2022 11:00:59 -0600

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

Title:
  Enable arm64 for Hyper-V guests

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-meta-azure package in Ubuntu:
  In Progress
Status in linux-signed-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Hirsute:
  Fix Released
Status in linux-meta-azure source package in Hirsute:
  Fix Released
Status in linux-signed-azure source package in Hirsute:
  Fix Released
Status in linux-azure source package in Impish:
  Fix Released
Status in linux-meta-azure source package in Impish:
  Fix Released
Status in linux-signed-azure source package in Impish:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress
Status in linux-meta-azure source package in Jammy:
  In Progress
Status in linux-signed-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Since linux-azure can also be used for local Hyper-V guests on Windows
  10 Pro running on arm64 platforms, enable arm64 build for this kernel
  as well.

  [Test Case]

  Boot an arm64 VM on a machine running Win10Pro with Hyper-V.

  [Where things could go wrong]

  Some of the patches touch common PCI code. Device detection could be
  impacted.

  [Other info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1956508] Re: Impish update: upstream stable patchset 2022-01-05

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1958155] Re: Pod traffic not taking advantage of interfaces with multiple tx queues

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1958151] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1959216] Re: linux-azure: CONFIG_FB_EFI=y

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.4.0-1070.73

---
linux-azure (5.4.0-1070.73) focal; urgency=medium

  * focal/linux-azure: 5.4.0-1070.73 -proposed tracker (LP: #1959251)

  * Packaging resync (LP: #1786013)
- [Packaging] azure: config resync

  * Focal update: v5.4.165 upstream stable release (LP: #1957007)
- HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option

  * linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] CONFIG_FB_EFI=y

  * Add sunrpc module parameters for NFSv3 nconnect (LP: #1958990)
- SAUCE: Add sunrpc module parameters for NFSv3 nconnect

  [ Ubuntu: 5.4.0-100.113 ]

  * focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
  * Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
  tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
  stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
  test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- ne

[Kernel-packages] [Bug 1959216] Re: linux-azure: CONFIG_FB_EFI=y

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.13.0-1014.16

---
linux-azure (5.13.0-1014.16) impish; urgency=medium

  * impish/linux-azure: 5.13.0-1014.16 -proposed tracker (LP: #1960044)

  * linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] azure: CONFIG_FB_EFI=y

  * Add sunrpc module parameters for NFSv3 nconnect (LP: #1958990)
- SAUCE: Add sunrpc module parameters for NFSv3 nconnect

  * MANA updates (LP: #1959012)
- net: mana: Add RX fencing
- net: mana: Fix memory leak in mana_hwc_create_wq

  * Enable arm64 for Hyper-V guests (LP: #1949770)
- [Packaging] linux-azure: Add basic packaging support for arm64
- [Config] azure: CONFIG_CMA=n [arm64]
- Drivers: hv: Move Hyper-V extended capability check to arch neutral code
- asm-generic/hyperv: Add missing #include of nmi.h
- Drivers: hv: Make portions of Hyper-V init code be arch neutral
- Drivers: hv: Add arch independent default functions for some Hyper-V
  handlers
- kernel.h: split out panic and oops helpers
- Drivers: hv: Move Hyper-V misc functionality to arch-neutral code
- drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers
- arm64: hyperv: Add Hyper-V hypercall and register access utilities
- arm64: hyperv: Add panic handler
- arm64: hyperv: Initialize hypervisor on boot
- arm64: efi: Export screen_info
- Drivers: hv: Enable Hyper-V code to be built on ARM64
- PCI: hv: Support for create interrupt v3
- PCI: Introduce domain_nr in pci_host_bridge
- PCI: Support populating MSI domains of root buses via bridges
- arm64: PCI: Restructure pcibios_root_bridge_prepare()
- arm64: PCI: Support root bridge preparation for Hyper-V
- PCI: hv: Generify PCI probing
- PCI: hv: Set ->domain_nr of pci_host_bridge at probing time
- PCI: hv: Turn on the host bridge probing on ARM64
- PCI: hv: Set up MSI domain at bridge probing time
- arm64: smccc: Add support for SMCCCv1.2 extended input/output registers
- [Config] azure: Ignore initial arm64 ABI
- PCI: hv: Make the code arch neutral by adding arch specific interfaces
- PCI: hv: Add arm64 Hyper-V vPCI support
- [Config] azure: Update arm64 policy for CONFIG_PCI_HYPERV

  * Support networking XDP (LP: #1958252)
- net: mana: Use kcalloc() instead of kzalloc()
- net: mana: Allow setting the number of queues while the NIC is down
- net: mana: Fix the netdev_err()'s vPort argument in mana_init_port()
- net: mana: Report OS info to the PF driver
- net: mana: Improve the HWC error handling
- net: mana: Support hibernation and kexec
- net: mana: Fix spelling mistake "calledd" -> "called"
- net: mana: Add XDP support

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after la

[Kernel-packages] [Bug 1958990] Re: Add sunrpc module parameters for NFSv3 nconnect

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.4.0-1070.73

---
linux-azure (5.4.0-1070.73) focal; urgency=medium

  * focal/linux-azure: 5.4.0-1070.73 -proposed tracker (LP: #1959251)

  * Packaging resync (LP: #1786013)
- [Packaging] azure: config resync

  * Focal update: v5.4.165 upstream stable release (LP: #1957007)
- HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option

  * linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] CONFIG_FB_EFI=y

  * Add sunrpc module parameters for NFSv3 nconnect (LP: #1958990)
- SAUCE: Add sunrpc module parameters for NFSv3 nconnect

  [ Ubuntu: 5.4.0-100.113 ]

  * focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
  * Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
  tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
  stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
  test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- ne

[Kernel-packages] [Bug 1959012] Re: MANA updates

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.13.0-1014.16

---
linux-azure (5.13.0-1014.16) impish; urgency=medium

  * impish/linux-azure: 5.13.0-1014.16 -proposed tracker (LP: #1960044)

  * linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] azure: CONFIG_FB_EFI=y

  * Add sunrpc module parameters for NFSv3 nconnect (LP: #1958990)
- SAUCE: Add sunrpc module parameters for NFSv3 nconnect

  * MANA updates (LP: #1959012)
- net: mana: Add RX fencing
- net: mana: Fix memory leak in mana_hwc_create_wq

  * Enable arm64 for Hyper-V guests (LP: #1949770)
- [Packaging] linux-azure: Add basic packaging support for arm64
- [Config] azure: CONFIG_CMA=n [arm64]
- Drivers: hv: Move Hyper-V extended capability check to arch neutral code
- asm-generic/hyperv: Add missing #include of nmi.h
- Drivers: hv: Make portions of Hyper-V init code be arch neutral
- Drivers: hv: Add arch independent default functions for some Hyper-V
  handlers
- kernel.h: split out panic and oops helpers
- Drivers: hv: Move Hyper-V misc functionality to arch-neutral code
- drivers: hv: Decouple Hyper-V clock/timer code from VMbus drivers
- arm64: hyperv: Add Hyper-V hypercall and register access utilities
- arm64: hyperv: Add panic handler
- arm64: hyperv: Initialize hypervisor on boot
- arm64: efi: Export screen_info
- Drivers: hv: Enable Hyper-V code to be built on ARM64
- PCI: hv: Support for create interrupt v3
- PCI: Introduce domain_nr in pci_host_bridge
- PCI: Support populating MSI domains of root buses via bridges
- arm64: PCI: Restructure pcibios_root_bridge_prepare()
- arm64: PCI: Support root bridge preparation for Hyper-V
- PCI: hv: Generify PCI probing
- PCI: hv: Set ->domain_nr of pci_host_bridge at probing time
- PCI: hv: Turn on the host bridge probing on ARM64
- PCI: hv: Set up MSI domain at bridge probing time
- arm64: smccc: Add support for SMCCCv1.2 extended input/output registers
- [Config] azure: Ignore initial arm64 ABI
- PCI: hv: Make the code arch neutral by adding arch specific interfaces
- PCI: hv: Add arm64 Hyper-V vPCI support
- [Config] azure: Update arm64 policy for CONFIG_PCI_HYPERV

  * Support networking XDP (LP: #1958252)
- net: mana: Use kcalloc() instead of kzalloc()
- net: mana: Allow setting the number of queues while the NIC is down
- net: mana: Fix the netdev_err()'s vPort argument in mana_init_port()
- net: mana: Report OS info to the PF driver
- net: mana: Improve the HWC error handling
- net: mana: Support hibernation and kexec
- net: mana: Fix spelling mistake "calledd" -> "called"
- net: mana: Add XDP support

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after la

[Kernel-packages] [Bug 1959593] Re: tcm_loop requires '-extras' for EKS optimised AMIs

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.4.0-1066.69

---
linux-aws (5.4.0-1066.69) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1066.69 -proposed tracker (LP: #1959246)

  * tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
- [Packaging] aws: Include tcm_loop.ko

  [ Ubuntu: 5.4.0-100.113 ]

  * focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
  * Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
  tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
  stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
  test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
- net, neigh: clear whole pneigh_entry at alloc time
- net/qla3xxx: fix an error code in ql_adapter_up()
- Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
  rp_filter tests"
- selftests/fib_tests

[Kernel-packages] [Bug 1959593] Re: tcm_loop requires '-extras' for EKS optimised AMIs

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.13.0-1014.15

---
linux-aws (5.13.0-1014.15) impish; urgency=medium

  * impish/linux-aws: 5.13.0-1014.15 -proposed tracker (LP: #1960525)

  * linux-aws: Make a signed kernel (LP: #1951011)
- [Packaging] aws: Make a signed kernel

linux-aws (5.13.0-1013.14) impish; urgency=medium

  * impish/linux-aws: 5.13.0-1013.14 -proposed tracker (LP: #1960042)

  * tcm_loop requires '-extras' for EKS optimised AMIs (LP: #1959593)
- [Packaging] aws: Include tcm_loop.ko

  [ Ubuntu: 5.13.0-30.33 ]

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)
  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

  [ Ubuntu: 5.13.0-29.32 ]

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)
  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)
  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for

[Kernel-packages] [Bug 1960034] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.13.0-30.33

---
linux (5.13.0-30.33) impish; urgency=medium

  * impish/linux: 5.13.0-30.33 -proposed tracker (LP: #1960055)

  * systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
(LP: #1960034)
- Revert "block: avoid to quiesce queue in elevator_init_mq"
- Revert "blk-mq: cancel blk-mq dispatch work in both blk_cleanup_queue and
  disk_release()"

linux (5.13.0-29.32) impish; urgency=medium

  * impish/linux: 5.13.0-29.32 -proposed tracker (LP: #1959238)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.01.31)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store

  * Impish update: upstream stable patchset 2022-01-05 (LP: #1956508)
- ACPI: Get acpi_device's parent from the parent field
- USB: serial: option: add Telit LE910S1 0x9200 composition
- USB: serial: option: add Fibocom FM101-GL variants
- usb: dwc2: gadget: Fix ISOC flow for elapsed frames
- usb: dwc2: hcd_queue: Fix use of floating point literal
- usb: dwc3: gadget: Ignore NoStream after End Transfer
- usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
- usb: dwc3: gadget: Fix null pointer exception
- net: nexthop: fix null pointer dereference when IPv6 is not enabled
- usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in 
probe
- usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
- usb: hub: Fix usb enumeration issue due to address0 race
- usb: hub: Fix locking issues with address0_mutex
- binder: fix test regression due to sender_euid change
- ALSA: ctxfi: Fix out-of-range access
- ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
- ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
- media: cec: copy sequence field for the reply
- Revert "parisc: Fix backtrace to always include init funtion names"
- HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
- staging/fbtft: Fix backlight
- staging: greybus: Add missing rwsem around snd_ctl_remove() calls
- staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
- fuse: release pipe buf after last use
- xen: don't continue xenstore initialization in case of errors
- xen: detect uninitialized xenbus in xenbus_init
- KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
- tracing/uprobe: Fix uprobe_perf_open probes iteration
- tracing: Fix pid filtering when triggers are attached
- mmc: sdhci-esdhc-imx: disable CMDQ support
- mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
- mdio: aspeed: Fix "Link is Down" issue
- powerpc/32: Fix hardlockup on vmap stack overflow
- PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
- PCI: aardvark: Implement re-issuing config requests on CRS response
- PCI: aardvark: Simplify initialization of rootcap on virtual bridge
- PCI: aardvark: Fix link training
- proc/vmcore: fix clearing user buffer by properly using clear_user()
- netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
- netfilter: ctnetlink: do not erase error code with EINVAL
- netfilter: ipvs: Fix reuse connection if RS weight is 0
- netfilter: flowtable: fix IPv6 tunnel addr match
- ARM: dts: BCM5301X: Fix I2C controller interrupt
- ARM: dts: BCM5301X: Add interrupt properties to GPIO node
- ARM: dts: bcm2711: Fix PCIe interrupts
- ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
- ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
- ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
- ASoC: codecs: wcd934x: return error code correctly from hw_params
- net: ieee802154: handle iftypes as u32
- firmware: arm_scmi: pm: Propagate return value to caller
- NFSv42: Don't fail clone() unless the OP_CLONE operation failed
- ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
- drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
- scsi: mpt3sas: Fix kernel panic during drive powercycle test
- drm/vc4: fix error code in vc4_create_object()
- net: marvell: prestera: fix double free issue on err path
- iavf: Prevent changing static ITR values if adaptive moderation is on
- ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
- mptcp: fix delack timer
- firmware: smccc: Fix check for ARCH_SOC_ID not implemented
- ipv6: fix typos in __ip6_finish_output()
- nfp: checking parameter process for rx-usecs/tx-usecs is invalid
- net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
- net: ipv6: add fib6_nh_release_dsts stub
- net: nexthop: release IPv6 per-cpu dsts when replacing a nexthop group
- ice: fix vsi->txq_map sizing
- ice: avoid bpf_prog refcount underflow
 

[Kernel-packages] [Bug 1961476] Re: The laptop turns off only through the button and won't wake up from sleep (black screen)

[Rosso]

** Information type changed from Private Security to Public

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

Title:
  The laptop turns off only through the button and won't wake up from
  sleep (black screen)

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

Bug description:
  A complete shutdown of the laptop occurs only with the help of the shutdown 
button. If this is not done, then the keyboard backlight and fans work, and the 
screen itself is turned off. And also the sleep mode does not work (black 
screen and no reaction), you have to turn it off with a button to get out of 
it. The problem has been observed since ubuntu version 20.04 and the BIOS 
update. These problems are not observed in Windows OS. The video card is no 
longer displayed as nvidia in both operating systems, now it is displayed only 
asMesa Intel® UHD Graphics 630 (CFL GT2).
  I didn't reboot myself before, apparently the kernel was fixed. Thanks to the 
developers, that now he at least reboots himself. It remains to solve the issue 
with the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 19 14:35:10 2022
  InstallationDate: Installed on 2022-02-01 (17 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

  Product Name: G7 7790
  BIOS Information
   Vendor: Dell Inc.
   Version: 1.14.0 10/20/2020
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eve1634 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-01 (17 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. G7 7790
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=72a43957-07b7-4ade-9aa6-30aede661648 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-30-generic N/A
   linux-backports-modules-5.13.0-30-generic  N/A
   linux-firmware 1.187.26
  Tags:  focal
  Uname: Linux 5.13.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.name: 0PJ0RG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 6564055862
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd10/20/2020:br1.14:svnDellInc.:pnG77790:pvr:rvnDellInc.:rn0PJ0RG:rvrA00:cvnDellInc.:ct10:cvr:sku08EC:
  dmi.product.family: GSeries
  dmi.product.name: G7 7790
  dmi.product.sku: 08EC
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961476/+subscriptions


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

[Kernel-packages] [Bug 1956614] Re: Bionic update: upstream stable patchset 2022-01-06

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-169.177

---
linux (4.15.0-169.177) bionic; urgency=medium

  * bionic/linux: 4.15.0-169.177 -proposed tracker (LP: #1959877)

  * ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux
4.15.0-168.176 on s390x (LP: #1959752)
- recordmcount.pl: fix typo in s390 mcount regex

linux (4.15.0-168.176) bionic; urgency=medium

  * bionic/linux: 4.15.0-168.176 -proposed tracker (LP: #1959308)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * Bionic update: upstream stable patchset 2022-01-25 (LP: #1959033)
- IB/qib: Use struct_size() helper
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- net: usb: lan78xx: add Allied Telesis AT29M2-AF
- can: kvaser_usb: get CAN clock frequency from device
- HID: holtek: fix mouse probing
- spi: change clk_disable_unprepare to clk_unprepare
- IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
- netfilter: fix regression in looped (broad|multi)cast's MAC handling
- qlcnic: potential dereference null pointer of rx_queue->page_ring
- net: accept UFOv6 packages in virtio_net_hdr_to_skb
- net: skip virtio_net_hdr_set_proto if protocol already set
- bonding: fix ad_actor_system option setting to default
- fjes: Check for error irq
- drivers: net: smc911x: Check for error irq
- sfc: falcon: Check null pointer of rx_queue->page_ring
- hwmon: (lm90) Fix usage of CONFIG2 register in detect function
- ALSA: jack: Check the return value of kstrdup()
- ALSA: drivers: opl3: Fix incorrect use of vp->state
- Input: atmel_mxt_ts - fix double free in mxt_read_info_block
- x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
- pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
- ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
- f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
- usb: gadget: u_ether: fix race in setting MAC address in setup phase
- KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
- hwmon: (lm90) Do not report 'busy' status bit as alarm
- ax25: NPD bug when detaching AX25 device
- hamradio: defer ax25 kfree after unregister_netdev
- hamradio: improve the incomplete fix to avoid NPD
- phonet/pep: refuse to enable an unbound pipe
- parisc: Correct completer in lws start

  * Bionic update: upstream stable patchset 2022-01-14 (LP: #1957957)
- nfc: fix segfault in nfc_genl_dump_devices_done
- drm/msm/dsi: set default num_data_lanes
- net/mlx4_en: Update reported link modes for 1/10G
- parisc/agp: Annotate parisc agp init functions with __init
- i2c: rk3x: Handle a spurious start completion interrupt flag
- net: netlink: af_netlink: Prevent empty skb by adding a check on len.
- tracing: Fix a kmemleak false positive in tracing_map
- bpf: fix panic due to oob in bpf_prog_test_run_skb
- hwmon: (dell-smm) Fix warning on /proc/i8k creation error
- mac80211: send ADDBA requests using the tid/queue of the aggregation 
session
- recordmcount.pl: look for jgnop instruction as well as bcrl on s390
- dm btree remove: fix use after free in rebalance_children()
- audit: improve robustness of the audit queue handling
- nfsd: fix use-after-free due to delegation race
- x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol
- x86/sme: Explicitly map new EFI memmap table as encrypted
- ARM: socfpga: dts: fix qspi node compatible
- dmaengine: st_fdma: fix MODULE_ALIAS
- soc/tegra: fuse: Fix bitwise vs. logical OR warning
- igbvf: fix double free in `igbvf_probe`
- ixgbe: set X550 MDIO speed before talking to PHY
- net/packet: rx_owner_map depends on pg_vec
- sit: do not call ipip6_dev_free() from sit_init_net()
- USB: gadget: bRequestType is a bitfield, not a enum
- PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
- PCI/MSI: Mask MSI-X vectors only on success
- USB: serial: option: add Telit FN990 compositions
- timekeeping: Really make sure wall_to_monotonic isn't positive
- libata: if T_LENGTH is zero, dma direction should be DMA_NONE
- net: systemport: Add global locking for descriptor lifecycle
- firmware: arm_scpi: Fix string overflow in SCPI genpd driver
- ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
- fuse: annotate lock in fuse_reverse_inval_entry()
- scsi: scsi_debug: Sanity check block descriptor length in 
resp_mode_select()
- net: lan78xx: Avoid unnecessary self assignment
- ARM: 8805/2: remove unneeded naked function usage
- mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO
- ARM: 8800/1: use choice for kernel unwinders
- [Config] updateconfigs for UNWINDER_ARM
- Input: touchscreen - avoid bitwise vs logical OR warning
- xen/blkfront: harden blkfront ag

[Kernel-packages] [Bug 1957113] Re: Bionic update: upstream stable patchset 2022-01-11

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-169.177

---
linux (4.15.0-169.177) bionic; urgency=medium

  * bionic/linux: 4.15.0-169.177 -proposed tracker (LP: #1959877)

  * ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux
4.15.0-168.176 on s390x (LP: #1959752)
- recordmcount.pl: fix typo in s390 mcount regex

linux (4.15.0-168.176) bionic; urgency=medium

  * bionic/linux: 4.15.0-168.176 -proposed tracker (LP: #1959308)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * Bionic update: upstream stable patchset 2022-01-25 (LP: #1959033)
- IB/qib: Use struct_size() helper
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- net: usb: lan78xx: add Allied Telesis AT29M2-AF
- can: kvaser_usb: get CAN clock frequency from device
- HID: holtek: fix mouse probing
- spi: change clk_disable_unprepare to clk_unprepare
- IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
- netfilter: fix regression in looped (broad|multi)cast's MAC handling
- qlcnic: potential dereference null pointer of rx_queue->page_ring
- net: accept UFOv6 packages in virtio_net_hdr_to_skb
- net: skip virtio_net_hdr_set_proto if protocol already set
- bonding: fix ad_actor_system option setting to default
- fjes: Check for error irq
- drivers: net: smc911x: Check for error irq
- sfc: falcon: Check null pointer of rx_queue->page_ring
- hwmon: (lm90) Fix usage of CONFIG2 register in detect function
- ALSA: jack: Check the return value of kstrdup()
- ALSA: drivers: opl3: Fix incorrect use of vp->state
- Input: atmel_mxt_ts - fix double free in mxt_read_info_block
- x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
- pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
- ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
- f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
- usb: gadget: u_ether: fix race in setting MAC address in setup phase
- KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
- hwmon: (lm90) Do not report 'busy' status bit as alarm
- ax25: NPD bug when detaching AX25 device
- hamradio: defer ax25 kfree after unregister_netdev
- hamradio: improve the incomplete fix to avoid NPD
- phonet/pep: refuse to enable an unbound pipe
- parisc: Correct completer in lws start

  * Bionic update: upstream stable patchset 2022-01-14 (LP: #1957957)
- nfc: fix segfault in nfc_genl_dump_devices_done
- drm/msm/dsi: set default num_data_lanes
- net/mlx4_en: Update reported link modes for 1/10G
- parisc/agp: Annotate parisc agp init functions with __init
- i2c: rk3x: Handle a spurious start completion interrupt flag
- net: netlink: af_netlink: Prevent empty skb by adding a check on len.
- tracing: Fix a kmemleak false positive in tracing_map
- bpf: fix panic due to oob in bpf_prog_test_run_skb
- hwmon: (dell-smm) Fix warning on /proc/i8k creation error
- mac80211: send ADDBA requests using the tid/queue of the aggregation 
session
- recordmcount.pl: look for jgnop instruction as well as bcrl on s390
- dm btree remove: fix use after free in rebalance_children()
- audit: improve robustness of the audit queue handling
- nfsd: fix use-after-free due to delegation race
- x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol
- x86/sme: Explicitly map new EFI memmap table as encrypted
- ARM: socfpga: dts: fix qspi node compatible
- dmaengine: st_fdma: fix MODULE_ALIAS
- soc/tegra: fuse: Fix bitwise vs. logical OR warning
- igbvf: fix double free in `igbvf_probe`
- ixgbe: set X550 MDIO speed before talking to PHY
- net/packet: rx_owner_map depends on pg_vec
- sit: do not call ipip6_dev_free() from sit_init_net()
- USB: gadget: bRequestType is a bitfield, not a enum
- PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
- PCI/MSI: Mask MSI-X vectors only on success
- USB: serial: option: add Telit FN990 compositions
- timekeeping: Really make sure wall_to_monotonic isn't positive
- libata: if T_LENGTH is zero, dma direction should be DMA_NONE
- net: systemport: Add global locking for descriptor lifecycle
- firmware: arm_scpi: Fix string overflow in SCPI genpd driver
- ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
- fuse: annotate lock in fuse_reverse_inval_entry()
- scsi: scsi_debug: Sanity check block descriptor length in 
resp_mode_select()
- net: lan78xx: Avoid unnecessary self assignment
- ARM: 8805/2: remove unneeded naked function usage
- mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO
- ARM: 8800/1: use choice for kernel unwinders
- [Config] updateconfigs for UNWINDER_ARM
- Input: touchscreen - avoid bitwise vs logical OR warning
- xen/blkfront: harden blkfront ag

[Kernel-packages] [Bug 1957957] Re: Bionic update: upstream stable patchset 2022-01-14

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-169.177

---
linux (4.15.0-169.177) bionic; urgency=medium

  * bionic/linux: 4.15.0-169.177 -proposed tracker (LP: #1959877)

  * ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux
4.15.0-168.176 on s390x (LP: #1959752)
- recordmcount.pl: fix typo in s390 mcount regex

linux (4.15.0-168.176) bionic; urgency=medium

  * bionic/linux: 4.15.0-168.176 -proposed tracker (LP: #1959308)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * Bionic update: upstream stable patchset 2022-01-25 (LP: #1959033)
- IB/qib: Use struct_size() helper
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- net: usb: lan78xx: add Allied Telesis AT29M2-AF
- can: kvaser_usb: get CAN clock frequency from device
- HID: holtek: fix mouse probing
- spi: change clk_disable_unprepare to clk_unprepare
- IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
- netfilter: fix regression in looped (broad|multi)cast's MAC handling
- qlcnic: potential dereference null pointer of rx_queue->page_ring
- net: accept UFOv6 packages in virtio_net_hdr_to_skb
- net: skip virtio_net_hdr_set_proto if protocol already set
- bonding: fix ad_actor_system option setting to default
- fjes: Check for error irq
- drivers: net: smc911x: Check for error irq
- sfc: falcon: Check null pointer of rx_queue->page_ring
- hwmon: (lm90) Fix usage of CONFIG2 register in detect function
- ALSA: jack: Check the return value of kstrdup()
- ALSA: drivers: opl3: Fix incorrect use of vp->state
- Input: atmel_mxt_ts - fix double free in mxt_read_info_block
- x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
- pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
- ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
- f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
- usb: gadget: u_ether: fix race in setting MAC address in setup phase
- KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
- hwmon: (lm90) Do not report 'busy' status bit as alarm
- ax25: NPD bug when detaching AX25 device
- hamradio: defer ax25 kfree after unregister_netdev
- hamradio: improve the incomplete fix to avoid NPD
- phonet/pep: refuse to enable an unbound pipe
- parisc: Correct completer in lws start

  * Bionic update: upstream stable patchset 2022-01-14 (LP: #1957957)
- nfc: fix segfault in nfc_genl_dump_devices_done
- drm/msm/dsi: set default num_data_lanes
- net/mlx4_en: Update reported link modes for 1/10G
- parisc/agp: Annotate parisc agp init functions with __init
- i2c: rk3x: Handle a spurious start completion interrupt flag
- net: netlink: af_netlink: Prevent empty skb by adding a check on len.
- tracing: Fix a kmemleak false positive in tracing_map
- bpf: fix panic due to oob in bpf_prog_test_run_skb
- hwmon: (dell-smm) Fix warning on /proc/i8k creation error
- mac80211: send ADDBA requests using the tid/queue of the aggregation 
session
- recordmcount.pl: look for jgnop instruction as well as bcrl on s390
- dm btree remove: fix use after free in rebalance_children()
- audit: improve robustness of the audit queue handling
- nfsd: fix use-after-free due to delegation race
- x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol
- x86/sme: Explicitly map new EFI memmap table as encrypted
- ARM: socfpga: dts: fix qspi node compatible
- dmaengine: st_fdma: fix MODULE_ALIAS
- soc/tegra: fuse: Fix bitwise vs. logical OR warning
- igbvf: fix double free in `igbvf_probe`
- ixgbe: set X550 MDIO speed before talking to PHY
- net/packet: rx_owner_map depends on pg_vec
- sit: do not call ipip6_dev_free() from sit_init_net()
- USB: gadget: bRequestType is a bitfield, not a enum
- PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
- PCI/MSI: Mask MSI-X vectors only on success
- USB: serial: option: add Telit FN990 compositions
- timekeeping: Really make sure wall_to_monotonic isn't positive
- libata: if T_LENGTH is zero, dma direction should be DMA_NONE
- net: systemport: Add global locking for descriptor lifecycle
- firmware: arm_scpi: Fix string overflow in SCPI genpd driver
- ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
- fuse: annotate lock in fuse_reverse_inval_entry()
- scsi: scsi_debug: Sanity check block descriptor length in 
resp_mode_select()
- net: lan78xx: Avoid unnecessary self assignment
- ARM: 8805/2: remove unneeded naked function usage
- mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO
- ARM: 8800/1: use choice for kernel unwinders
- [Config] updateconfigs for UNWINDER_ARM
- Input: touchscreen - avoid bitwise vs logical OR warning
- xen/blkfront: harden blkfront ag

[Kernel-packages] [Bug 1959033] Re: Bionic update: upstream stable patchset 2022-01-25

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-169.177

---
linux (4.15.0-169.177) bionic; urgency=medium

  * bionic/linux: 4.15.0-169.177 -proposed tracker (LP: #1959877)

  * ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux
4.15.0-168.176 on s390x (LP: #1959752)
- recordmcount.pl: fix typo in s390 mcount regex

linux (4.15.0-168.176) bionic; urgency=medium

  * bionic/linux: 4.15.0-168.176 -proposed tracker (LP: #1959308)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * Bionic update: upstream stable patchset 2022-01-25 (LP: #1959033)
- IB/qib: Use struct_size() helper
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- net: usb: lan78xx: add Allied Telesis AT29M2-AF
- can: kvaser_usb: get CAN clock frequency from device
- HID: holtek: fix mouse probing
- spi: change clk_disable_unprepare to clk_unprepare
- IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
- netfilter: fix regression in looped (broad|multi)cast's MAC handling
- qlcnic: potential dereference null pointer of rx_queue->page_ring
- net: accept UFOv6 packages in virtio_net_hdr_to_skb
- net: skip virtio_net_hdr_set_proto if protocol already set
- bonding: fix ad_actor_system option setting to default
- fjes: Check for error irq
- drivers: net: smc911x: Check for error irq
- sfc: falcon: Check null pointer of rx_queue->page_ring
- hwmon: (lm90) Fix usage of CONFIG2 register in detect function
- ALSA: jack: Check the return value of kstrdup()
- ALSA: drivers: opl3: Fix incorrect use of vp->state
- Input: atmel_mxt_ts - fix double free in mxt_read_info_block
- x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
- pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
- ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
- f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
- usb: gadget: u_ether: fix race in setting MAC address in setup phase
- KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
- hwmon: (lm90) Do not report 'busy' status bit as alarm
- ax25: NPD bug when detaching AX25 device
- hamradio: defer ax25 kfree after unregister_netdev
- hamradio: improve the incomplete fix to avoid NPD
- phonet/pep: refuse to enable an unbound pipe
- parisc: Correct completer in lws start

  * Bionic update: upstream stable patchset 2022-01-14 (LP: #1957957)
- nfc: fix segfault in nfc_genl_dump_devices_done
- drm/msm/dsi: set default num_data_lanes
- net/mlx4_en: Update reported link modes for 1/10G
- parisc/agp: Annotate parisc agp init functions with __init
- i2c: rk3x: Handle a spurious start completion interrupt flag
- net: netlink: af_netlink: Prevent empty skb by adding a check on len.
- tracing: Fix a kmemleak false positive in tracing_map
- bpf: fix panic due to oob in bpf_prog_test_run_skb
- hwmon: (dell-smm) Fix warning on /proc/i8k creation error
- mac80211: send ADDBA requests using the tid/queue of the aggregation 
session
- recordmcount.pl: look for jgnop instruction as well as bcrl on s390
- dm btree remove: fix use after free in rebalance_children()
- audit: improve robustness of the audit queue handling
- nfsd: fix use-after-free due to delegation race
- x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol
- x86/sme: Explicitly map new EFI memmap table as encrypted
- ARM: socfpga: dts: fix qspi node compatible
- dmaengine: st_fdma: fix MODULE_ALIAS
- soc/tegra: fuse: Fix bitwise vs. logical OR warning
- igbvf: fix double free in `igbvf_probe`
- ixgbe: set X550 MDIO speed before talking to PHY
- net/packet: rx_owner_map depends on pg_vec
- sit: do not call ipip6_dev_free() from sit_init_net()
- USB: gadget: bRequestType is a bitfield, not a enum
- PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
- PCI/MSI: Mask MSI-X vectors only on success
- USB: serial: option: add Telit FN990 compositions
- timekeeping: Really make sure wall_to_monotonic isn't positive
- libata: if T_LENGTH is zero, dma direction should be DMA_NONE
- net: systemport: Add global locking for descriptor lifecycle
- firmware: arm_scpi: Fix string overflow in SCPI genpd driver
- ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
- fuse: annotate lock in fuse_reverse_inval_entry()
- scsi: scsi_debug: Sanity check block descriptor length in 
resp_mode_select()
- net: lan78xx: Avoid unnecessary self assignment
- ARM: 8805/2: remove unneeded naked function usage
- mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO
- ARM: 8800/1: use choice for kernel unwinders
- [Config] updateconfigs for UNWINDER_ARM
- Input: touchscreen - avoid bitwise vs logical OR warning
- xen/blkfront: harden blkfront ag

[Kernel-packages] [Bug 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.15.0-169.177

---
linux (4.15.0-169.177) bionic; urgency=medium

  * bionic/linux: 4.15.0-169.177 -proposed tracker (LP: #1959877)

  * ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux
4.15.0-168.176 on s390x (LP: #1959752)
- recordmcount.pl: fix typo in s390 mcount regex

linux (4.15.0-168.176) bionic; urgency=medium

  * bionic/linux: 4.15.0-168.176 -proposed tracker (LP: #1959308)

  * CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy

  * Bionic update: upstream stable patchset 2022-01-25 (LP: #1959033)
- IB/qib: Use struct_size() helper
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- net: usb: lan78xx: add Allied Telesis AT29M2-AF
- can: kvaser_usb: get CAN clock frequency from device
- HID: holtek: fix mouse probing
- spi: change clk_disable_unprepare to clk_unprepare
- IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
- netfilter: fix regression in looped (broad|multi)cast's MAC handling
- qlcnic: potential dereference null pointer of rx_queue->page_ring
- net: accept UFOv6 packages in virtio_net_hdr_to_skb
- net: skip virtio_net_hdr_set_proto if protocol already set
- bonding: fix ad_actor_system option setting to default
- fjes: Check for error irq
- drivers: net: smc911x: Check for error irq
- sfc: falcon: Check null pointer of rx_queue->page_ring
- hwmon: (lm90) Fix usage of CONFIG2 register in detect function
- ALSA: jack: Check the return value of kstrdup()
- ALSA: drivers: opl3: Fix incorrect use of vp->state
- Input: atmel_mxt_ts - fix double free in mxt_read_info_block
- x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
- pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
- ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
- f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
- usb: gadget: u_ether: fix race in setting MAC address in setup phase
- KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
- hwmon: (lm90) Do not report 'busy' status bit as alarm
- ax25: NPD bug when detaching AX25 device
- hamradio: defer ax25 kfree after unregister_netdev
- hamradio: improve the incomplete fix to avoid NPD
- phonet/pep: refuse to enable an unbound pipe
- parisc: Correct completer in lws start

  * Bionic update: upstream stable patchset 2022-01-14 (LP: #1957957)
- nfc: fix segfault in nfc_genl_dump_devices_done
- drm/msm/dsi: set default num_data_lanes
- net/mlx4_en: Update reported link modes for 1/10G
- parisc/agp: Annotate parisc agp init functions with __init
- i2c: rk3x: Handle a spurious start completion interrupt flag
- net: netlink: af_netlink: Prevent empty skb by adding a check on len.
- tracing: Fix a kmemleak false positive in tracing_map
- bpf: fix panic due to oob in bpf_prog_test_run_skb
- hwmon: (dell-smm) Fix warning on /proc/i8k creation error
- mac80211: send ADDBA requests using the tid/queue of the aggregation 
session
- recordmcount.pl: look for jgnop instruction as well as bcrl on s390
- dm btree remove: fix use after free in rebalance_children()
- audit: improve robustness of the audit queue handling
- nfsd: fix use-after-free due to delegation race
- x86: Make ARCH_USE_MEMREMAP_PROT a generic Kconfig symbol
- x86/sme: Explicitly map new EFI memmap table as encrypted
- ARM: socfpga: dts: fix qspi node compatible
- dmaengine: st_fdma: fix MODULE_ALIAS
- soc/tegra: fuse: Fix bitwise vs. logical OR warning
- igbvf: fix double free in `igbvf_probe`
- ixgbe: set X550 MDIO speed before talking to PHY
- net/packet: rx_owner_map depends on pg_vec
- sit: do not call ipip6_dev_free() from sit_init_net()
- USB: gadget: bRequestType is a bitfield, not a enum
- PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
- PCI/MSI: Mask MSI-X vectors only on success
- USB: serial: option: add Telit FN990 compositions
- timekeeping: Really make sure wall_to_monotonic isn't positive
- libata: if T_LENGTH is zero, dma direction should be DMA_NONE
- net: systemport: Add global locking for descriptor lifecycle
- firmware: arm_scpi: Fix string overflow in SCPI genpd driver
- ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
- fuse: annotate lock in fuse_reverse_inval_entry()
- scsi: scsi_debug: Sanity check block descriptor length in 
resp_mode_select()
- net: lan78xx: Avoid unnecessary self assignment
- ARM: 8805/2: remove unneeded naked function usage
- mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO
- ARM: 8800/1: use choice for kernel unwinders
- [Config] updateconfigs for UNWINDER_ARM
- Input: touchscreen - avoid bitwise vs logical OR warning
- xen/blkfront: harden blkfront ag

[Kernel-packages] [Bug 1960871] Re: linux-modules-extra-* fails to install due to dependency on unsigned package

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.15.0-1121.129

---
linux-aws (4.15.0-1121.129) bionic; urgency=medium

  * bionic/linux-aws: 4.15.0-1121.129 -proposed tracker (LP: #1960932)

  * linux-modules-extra-* fails to install due to dependency on unsigned package
(LP: #1960871)
- [Packaging] aws: Fix dependency for modules-extra

 -- Ian May   Tue, 15 Feb 2022 11:09:33 -0600

** Changed in: linux-aws (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  linux-modules-extra-* fails to install due to dependency on unsigned
  package

Status in linux-aws package in Ubuntu:
  Fix Released

Bug description:
  Several SRU tests are failing the test setup due to failure to install
  the modules-extra package:

  * Command: 
  yes "" | DEBIAN_FRONTEND=noninteractive apt-get install --yes --force-yes
  automake bison build-essential byacc flex git keyutils libacl1-dev libaio-
  dev libcap-dev libmm-dev libnuma-dev libsctp-dev libselinux1-dev libssl-
  dev libtirpc-dev pkg-config quota xfslibs-dev xfsprogs gcc linux-modules-
  extra-4.15.0-1120-aws
  Exit status: 100
  Duration: 0.908210039139

  stdout:
  Reading package lists...
  Building dependency tree...
  Reading state information...
  xfsprogs is already the newest version (4.9.0+nmu1ubuntu2).
  xfsprogs set to manually installed.
  git is already the newest version (1:2.17.1-1ubuntu0.9).
  git set to manually installed.
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-modules-extra-4.15.0-1120-aws : Depends: 
linux-image-unsigned-4.15.0-1120-aws but it is not going to be installed
  stderr:
  W: --force-yes is deprecated, use one of the options starting with --allow 
instead.
  E: Unable to correct problems, you have held broken packages.

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


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

[Kernel-packages] [Bug 1961599] Re: i915 [drm] *ERROR* CPU pipe A FIFO underrun on Dell XPS13 9310

[Bartłomiej Żogała]

Exact kernel package is linux-image-5.10.0-1057-oem. I'm using builtin
16:10 3840x2400 screen and external 3440x1440 one

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

Title:
  i915 [drm] *ERROR* CPU pipe A FIFO underrun on Dell XPS13 9310

Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  My system randomly hangs and I've spotted following i915 bug in dmesg:
  [  154.272665] wlan0: associated
  [  154.287455] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 
d0:57:XX:XX:XX:XX
  [  285.756393] input: MX Anywhere 2S Keyboard as 
/devices/virtual/misc/uhid/0005:046D:B01A.0005/input/input36
  [  285.756516] input: MX Anywhere 2S Mouse as 
/devices/virtual/misc/uhid/0005:046D:B01A.0005/input/input37
  [  285.756615] hid-generic 0005:046D:B01A.0005: input,hidraw3: BLUETOOTH HID 
v0.03 Keyboard [MX Anywhere 2S] on dc:41:XX:XX:XX:XX
  [  368.114749] SGI XFS with ACLs, security attributes, realtime, quota, no 
debug enabled
  [  368.120451] JFS: nTxBlock = 8192, nTxLock = 65536
  [  368.128173] ntfs: driver 2.1.32 [Flags: R/O MODULE].
  [  368.137701] QNX4 filesystem 0.2.3 registered.
  [  570.307743] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

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


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

[Kernel-packages] [Bug 1961599] [NEW] i915 [drm] *ERROR* CPU pipe A FIFO underrun on Dell XPS13 9310

[Bartłomiej Żogała]

Public bug reported:

My system randomly hangs and I've spotted following i915 bug in dmesg:
[  154.272665] wlan0: associated
[  154.287455] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 
d0:57:XX:XX:XX:XX
[  285.756393] input: MX Anywhere 2S Keyboard as 
/devices/virtual/misc/uhid/0005:046D:B01A.0005/input/input36
[  285.756516] input: MX Anywhere 2S Mouse as 
/devices/virtual/misc/uhid/0005:046D:B01A.0005/input/input37
[  285.756615] hid-generic 0005:046D:B01A.0005: input,hidraw3: BLUETOOTH HID 
v0.03 Keyboard [MX Anywhere 2S] on dc:41:XX:XX:XX:XX
[  368.114749] SGI XFS with ACLs, security attributes, realtime, quota, no 
debug enabled
[  368.120451] JFS: nTxBlock = 8192, nTxLock = 65536
[  368.128173] ntfs: driver 2.1.32 [Flags: R/O MODULE].
[  368.137701] QNX4 filesystem 0.2.3 registered.
[  570.307743] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

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

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

Title:
  i915 [drm] *ERROR* CPU pipe A FIFO underrun on Dell XPS13 9310

Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  My system randomly hangs and I've spotted following i915 bug in dmesg:
  [  154.272665] wlan0: associated
  [  154.287455] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by 
d0:57:XX:XX:XX:XX
  [  285.756393] input: MX Anywhere 2S Keyboard as 
/devices/virtual/misc/uhid/0005:046D:B01A.0005/input/input36
  [  285.756516] input: MX Anywhere 2S Mouse as 
/devices/virtual/misc/uhid/0005:046D:B01A.0005/input/input37
  [  285.756615] hid-generic 0005:046D:B01A.0005: input,hidraw3: BLUETOOTH HID 
v0.03 Keyboard [MX Anywhere 2S] on dc:41:XX:XX:XX:XX
  [  368.114749] SGI XFS with ACLs, security attributes, realtime, quota, no 
debug enabled
  [  368.120451] JFS: nTxBlock = 8192, nTxLock = 65536
  [  368.128173] ntfs: driver 2.1.32 [Flags: R/O MODULE].
  [  368.137701] QNX4 filesystem 0.2.3 registered.
  [  570.307743] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

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


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

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

[AdlerHorst]

apport information

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

Title:
  Wrong Energy value for an Asus Stylus

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Stylus: ELAN25B2:00 04F3:25B1
  All hardware: https://linux-hardware.org/?probe=1055dc7082

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  Date: Fri Feb 18 21:58:54 2022
  DisplayManager: gdm3
  GsettingsChanges:

  InstallationDate: Installed on 2021-08-15 (187 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 41.3-1ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-08-15 (189 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags: third-party-packages jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1961444/+subscriptions


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

[Kernel-packages] [Bug 1961444] Re: Wrong Energy value for an Asus Stylus

[AdlerHorst]

apport information

** Tags added: apport-collected

** Description changed:

  Stylus: ELAN25B2:00 04F3:25B1
  All hardware: https://linux-hardware.org/?probe=1055dc7082
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  Date: Fri Feb 18 21:58:54 2022
  DisplayManager: gdm3
  GsettingsChanges:
  
  InstallationDate: Installed on 2021-08-15 (187 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 41.3-1ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu77
+ Architecture: amd64
+ CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
+ CasperMD5CheckResult: fail
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2021-08-15 (189 days ago)
+ InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
+ Package: linux
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANGUAGE=de_CH:de
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_CH.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
+ Tags: third-party-packages jammy
+ Uname: Linux 5.15.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True

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

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

Title:
  Wrong Energy value for an Asus Stylus

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Stylus: ELAN25B2:00 04F3:25B1
  All hardware: https://linux-hardware.org/?probe=1055dc7082

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 41.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  Date: Fri Feb 18 21:58:54 2022
  DisplayManager: gdm3
  GsettingsChanges:

  InstallationDate: Installed on 2021-08-15 (187 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 41.3-1ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb
  CasperMD5CheckResult: fail
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-08-15 (189 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags: third-party-packages jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1961444/+subscriptions


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

[Kernel-packages] [Bug 1953587] Please test proposed package

[Timo Aaltonen]

Hello Juerg, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.21 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Fix sanity checker and cleanup metadata

Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-firmware source package in Hirsute:
  Fix Released
Status in linux-firmware source package in Impish:
  Fix Released

Bug description:
  The repo contains a checker script check_whence.py that checks WHENCE
  data against present firmware files and flags missing files and
  missing WHENCE entries. It currently doesn't parse the downstream
  WHENCE.ubuntu file. Fix that and cleanup any errors flagged by the
  checker.

  [ Impact ]

  None. These are packaging changes that are not visible to the end
  user.

  [ Where Problems Could Occur ]

  None.

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


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

[Kernel-packages] [Bug 1960839] Please test proposed package

[Timo Aaltonen]

Hello Mauricio, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.173.21 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Missing firmware for Intel ICE driver on Bionic,
     which is supported by the HWE kernel from Focal.

  [Fix]

   * commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
     brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)

  [Test Case]

   * Without firmware:

  ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0 
build 0x391f7640
  ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed 
with error -2
  ice :98:00.0: The DDP package file was not found or could not be 
read. Entering Safe Mode
  ice :98:00.0: Package download failed. Advanced features disabled - 
Device now in Safe Mode

   * With firmware:

  ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0 
build 0x391f7640
  ice :98:00.0: The DDP package was successfully loaded: ICE OS Default 
Package version 1.3.4.0
  ice :98:00.0: DCB is enabled in the hardware, max number of TCs 
supported on this port are 8
  ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.

  [Where problems could occur]

   * Systems with devices managed by the ice driver on Bionic HWE kernel
  from Focal.

   * The firmware enables advanced features, increasing driver exposure
  and device activity.

   * This has been available on Focal, which helps with some chance of issues 
being hit and
     reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on 
bugs.lp.net).

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


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

[Kernel-packages] [Bug 1954938] Please test proposed package

[Timo Aaltonen]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.27 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Include the QCA WCN 6856 v2.1 support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Won't Fix
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  WCN685x hw2.1 takes additional/updated firmware for both WiFi and
  Bluetooth function.

  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95

  [Fix]

  WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except
  for the directory path and a board-2.bin.

  For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from
  mainline are neccessary for Focal. Jammy has all of them already.

  For kernel, many of the prerequisite works have been committed for
  hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G
  will be turned off for the lack of userspace support, the only fix
  necessary is to correct read mask of version info register.

  ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14
  in bug 1939528, so only oem-5.14 has to be reverted.

  [Test Case]

  WiFi and Bluetooth devices should be up and running, pass basic
  operations.

  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

  [Where problems could occur]

  At the time being, WCN685x WiFi 6G support will be turnef off
  deliberately due to the lack of full support in the userspace
  management tools.

  [Other Info]

  While this is a new hardware model from OEM program, it's only
  nominated for Focal oem-5.14 kernel and the coming LTS Jammy.

  == original bug report ==

  ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit]
  ath11k_pci :71:00.0: enabling device ( -> 0002)
  ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17
  ath11k_pci: probe of :71:00.0 failed with error -95

  $ lspci -nnk|grep -A3 Network
  :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01)
  Subsystem: Foxconn International, Inc. Device [105b:e0ce]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  $ lsusb
  Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai

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


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

[Kernel-packages] [Bug 1958467] Please test proposed package

[Timo Aaltonen]

Hello Henry, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.27 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  focal linux-firmware package omits amdgpu/navi12 firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Impish:
  Won't Fix
Status in linux-firmware source package in Jammy:
  Invalid

Bug description:
  [Impact]

  The 20.04 LTS linux-firmware package list was cut before the
  amdgpu/navi12* firmware files were upstreamed to the Linux kernel
  repository, which is unfortunate because this hardware is older than
  some other included firmware (navi14*), and the firmware is required
  for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD
  GPUs.

  The files are included in 21.04 and 21.10, but to date they have not
  been included in the LTS hardware-enablement releases for 20.04. It
  would be helpful to include the navi12 firmware files for the next
  LTS+HWE release, since 22.04 isn't due out for a while.

  Without this firmware it is difficult to get AWS EC2 G4ad instances
  working with Ubuntu, as customers need to manually download and
  install the firmware from a reputable source and put it into the
  appropriate directory, which is not the experience they expect on
  hardware that is over a year old with the most recent HWE release.

  [Test Case]

  See above.

  [Fix]

  Backport amdgpu/nav12* from linux-firmware Jammy.

  [Where Problems Could Occur]

  Graphics problems, kernel crashes on machines with AMD GPU.

  [Notes]

  This is required for the HWE kernel so not updating linux-firmware in
  Impish.

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


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

[Kernel-packages] [Bug 1960933] Please test proposed package

[Timo Aaltonen]

Hello Christian, or anyone else affected,

Accepted linux-firmware into impish-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.201.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  rtw89_pci constantly drops connection with old firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10
  (impish)

  The current linux-firmware package (1.201.4+1.201.3) ships with
  realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin)
  version v0.13.8.0.

  My wifi chip wasn't able to keep a connection for more than a minute when 
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried 
disabling the power_save and stuff. But that had little to no effect. I was 
about to open an issue on the upstream project and did a last ditch attempt to 
see if there were any firmware updates... I found linux-firmware.git and it had
  two newer versions!

   - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to 
show up)
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17

   - v0.13.33.0 (was submitted in November 2021 and got merged in December 
2021):
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983

  I've downloaded and installed the latest "v0.13.33.0" on a whim and
  rebooted. And what a pleasant surprise: Instantly, my wifi connection
  lasted until the rest of the day.

  Could you please consider updating this realtek firmware in the next
  release? Thanks!

  [Test Case]

  See above.

  [Fix]

  Cherry pick two commit to match current Jammy:
  4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
  ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")

  [Where Problems Could Occur]

  Limited to wifi using RTL8852A HW.

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


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

[Kernel-packages] [Bug 1957786] Re: Enable CONFIG_NO_HZ_FULL in Jammy realtime kernel

[Krzysztof Kozlowski]

** Tags added: 5.15

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

Title:
  Enable CONFIG_NO_HZ_FULL in Jammy realtime kernel

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  nohz_full should be enabled by default as it improves certain
  workloads. No actual data was given, just strong opinion nohz_full is
  needed. CONFIG_NO_HZ_FULL is also in Intel’s BSP for Yocto RT.

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


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

[Kernel-packages] [Bug 1961588] [NEW] Tweak realtime-related config options in Jammy realtime kernel

[Krzysztof Kozlowski]

Public bug reported:

Config options below are useful for Realtime users:

1. CONFIG_WQ_POWER_EFFICIENT_DEFAULT disabled: energy saving is not that
important for Realtime workload but locality of any workqueues (thus
waking up only local CPU).

2. CONFIG_TIMERLAT_TRACER and CONFIG_OSNOISE_TRACER enabled: for
debugging latency issues.

3. CONFIG_BLK_CGROUP_IOLATENCY enabled: for users wanting to have
guarantees on IO latencies.

4. CONFIG_IRQ_TIME_ACCOUNTING enabled: for fine granularity task IRQ
accounting.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Krzysztof Kozlowski (krzk)
 Status: In Progress


** Tags: 5.15 jammy realtime

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

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

** Tags added: 5.15 jammy realtime

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

Title:
  Tweak realtime-related config options in Jammy realtime kernel

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Config options below are useful for Realtime users:

  1. CONFIG_WQ_POWER_EFFICIENT_DEFAULT disabled: energy saving is not
  that important for Realtime workload but locality of any workqueues
  (thus waking up only local CPU).

  2. CONFIG_TIMERLAT_TRACER and CONFIG_OSNOISE_TRACER enabled: for
  debugging latency issues.

  3. CONFIG_BLK_CGROUP_IOLATENCY enabled: for users wanting to have
  guarantees on IO latencies.

  4. CONFIG_IRQ_TIME_ACCOUNTING enabled: for fine granularity task IRQ
  accounting.

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


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

[Kernel-packages] [Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

[Mariusz]

That didn't fix the bug in my case. Should I create new bug report?

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

Title:
  [amdgpu] Random noise 'static' display after internal display turned
  off/on

Status in linux-hwe-5.13 package in Ubuntu:
  Fix Released

Bug description:
  Laptop internal display shows random looking 'static' after it's
  turned off and then on again.   e.g. on suspend/resume, or when
  plugging/unplugging an external monitor.

  This appeared to come after a `dist-upgrade` took the kernel from
  5.11.0-44 to 5.13.0-25 (hwe).

  Others are seeing this with both NVidia and AMD graphics hardware:
  - 
https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/
  - 
https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/

  I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome
  both X and Wayland, and gnome-flashback/metacity.  All showed the same
  problem.

  Also tried an `apt install --reinstall xserver-xorg-video-radeon
  libdrm-radeon1` for luck - no joy.

  Running a 20.04.3 live stick the problem does *not* occur.

  System: Thinkpad X13 Gen1
  Processor: AMD Ryzen 7 PRO 4750U
  System Firmware: 1.35

  $ lsb_release -rd
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

  Happy to assist with investigations.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME
  Date: Thu Jan 20 19:37:09 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:5082]
  InstallationDate: Installed on 2021-06-24 (210 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20UF0014US
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET67W(1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UF0014US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.36
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1:
  dmi.product.family: ThinkPad X13 Gen 1
  dmi.product.name: 20UF0014US
  dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1
  dmi.product.version: ThinkPad X13 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1961075] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-510 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-510/510.47.03-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961075] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-510 into impish-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-510/510.47.03-0ubuntu0.21.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961075] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted libnvidia-nscq-510 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libnvidia-
nscq-510/510.47.03-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961075] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-510 into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-510/510.47.03-0ubuntu0.20.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961075] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-510 into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-510/510.47.03-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961075] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted fabric-manager-510 into impish-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fabric-
manager-510/510.47.03-0ubuntu0.21.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961581] [NEW] 'Synaptics touchpad' not detected as an input device on 'Fujitsu LIFEBOOK U7411'

[Naman Kumar Bhalla]

Public bug reported:

Touchpad used to work fine initially but I recently realised that it's
not responding at all, since I'm mostly working with an external mouse.
Therefore, I'm not sure when this problem started or what really caused
it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 21 12:13:55 2022
InstallationDate: Installed on 2021-11-02 (111 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "cat /proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1961581/+attachment/5562442/+files/devices

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

Title:
  'Synaptics touchpad' not detected as an input device on 'Fujitsu
  LIFEBOOK U7411'

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

Bug description:
  Touchpad used to work fine initially but I recently realised that it's
  not responding at all, since I'm mostly working with an external
  mouse. Therefore, I'm not sure when this problem started or what
  really caused it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 21 12:13:55 2022
  InstallationDate: Installed on 2021-11-02 (111 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1961581/+subscriptions


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