[Kernel-packages] [Bug 1954911] Re: [i915] [penryn] System freeze when HDMI is plugged in

2022-01-04 Thread Daniel van Vugt
** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1954911

Title:
  [i915] [penryn] System freeze when HDMI is plugged in

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When I try to hookup my laptop to a smart TV using an HDMI it will not
  boot up at all. With my laptop running after booting normally and I
  plugin the HDMI cable it freeze up and the only way to unfreeze it is
  to hold the power down until it shuts off. I've done this at least
  twice maybe three times. Its like there is not an HDMI driver
  installed. I have been a computer tech since 1984 but as you know
  learning a new operating system is very time consuming. I started with
  Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft
  but them out of business then I finally had to go to MS DOS 4.0 and
  its been down hill ever since. I'm 64 and working my way into Linux.
  Any ideas would be great

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 15 05:09:06 2021
  DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [104d:9035]
 Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [104d:9035]
  MachineType: Sony Corporation VGN-FW351J
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago)
  dmi.bios.date: 11/07/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R2050Y0
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-FW351J
  dmi.product.sku: N/A
  dmi.product.version: C60184W1
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/+bug/1954911/+subscriptions


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


[Kernel-packages] [Bug 1954300] Update Released

2022-01-04 Thread Timo Aaltonen
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  mt7921e: Failed to start WM firmware

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  MT7921 might fail at device probe at boot:

  mt7921e :03:00.0: WM Firmware Version: 01, Build Time: 
20211014150922
  IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
  mt7921e :03:00.0: Message 8002 (seq 9) timeout
  mt7921e :03:00.0: Failed to start WM firmware
  mt7921e: probe of :03:00.0 failed with error -110

  [Fix]

  Kernel fixes:
  * 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
  * 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")

  And firmware:
  * 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")

  [Test Case]

  Run checkbox reboot stress tests to try trigger this issue:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  This imports fixes requiring both kernel driver and proprietary firmware
  updates, the firmware part might cause instability or so.

  == original bug report ==

  Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware 
Version: 01, Build Time: 20211014150922
  Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
  Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up - 
1Gbps/Full - flow control rx/tx
  Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: 
link becomes ready
  Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64, 
error -110
  Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002 
(seq 9) timeout
  Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start 
WM firmware
  Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed 
with error -110

  This takes following fixes to resolve completely:
  * kernel patch:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
  * firmware:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a

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


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


[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware - 1.187.24

---
linux-firmware (1.187.24) focal; urgency=medium

  * amdgpu: add UVD firmware for SI asics (LP: #1953249)
  * linux-firmware: update frimware for mediatek bluetooth chip (MT7921) (LP: 
#1954300)

 -- Juerg Haefliger   Thu, 16 Dec 2021 16:01:58
+0100

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

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

Title:
  mt7921e: Failed to start WM firmware

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux-firmware source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Released

Bug description:
  [SRU Justification]

  [Impact]

  MT7921 might fail at device probe at boot:

  mt7921e :03:00.0: WM Firmware Version: 01, Build Time: 
20211014150922
  IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
  mt7921e :03:00.0: Message 8002 (seq 9) timeout
  mt7921e :03:00.0: Failed to start WM firmware
  mt7921e: probe of :03:00.0 failed with error -110

  [Fix]

  Kernel fixes:
  * 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
  * 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")

  And firmware:
  * 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")

  [Test Case]

  Run checkbox reboot stress tests to try trigger this issue:

$ checkbox-cli run com.canonical.certification::stress/reboot

  [Where problems could occur]

  This imports fixes requiring both kernel driver and proprietary firmware
  updates, the firmware part might cause instability or so.

  == original bug report ==

  Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware 
Version: 01, Build Time: 20211014150922
  Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
  Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up - 
1Gbps/Full - flow control rx/tx
  Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: 
link becomes ready
  Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64, 
error -110
  Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002 
(seq 9) timeout
  Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start 
WM firmware
  Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed 
with error -110

  This takes following fixes to resolve completely:
  * kernel patch:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
  * firmware:
    * 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a

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


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


[Kernel-packages] [Bug 1953249] Re: UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-firmware - 1.187.24

---
linux-firmware (1.187.24) focal; urgency=medium

  * amdgpu: add UVD firmware for SI asics (LP: #1953249)
  * linux-firmware: update frimware for mediatek bluetooth chip (MT7921) (LP: 
#1954300)

 -- Juerg Haefliger   Thu, 16 Dec 2021 16:01:58
+0100

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

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

Title:
  UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing

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

Bug description:
  [ Impact ]

  AMD GPU not functional on Focal with HWE kernel.

  [ Test Case ]

  See original description below.

  [ Fix ]

  Cherry-pick relevant commit from upstream linux-firmware.

  [ Where Problems Could Occur ]

  Broken graphics with AMD GPUs.

  [ Original Description ]

  Release: up-to-date Focal LTS (20.04.3)
  Package-version: linux-firmware 1.187.20
  Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M]

  With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly),
  my laptop's discrete graphics stopped working. Looking at the logs, I
  found these messages:

  -- snippet --
  kernel: [1.492908] [drm] amdgpu: dpm initialized
  kernel: [1.492932] [drm] AMDGPU Display Connectors
  kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for 
amdgpu/verde_uvd.bin failed with error -2
  kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load 
firmware "amdgpu/verde_uvd.bin"
  kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init 
of IP block  failed -2
  kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init 
failed
  kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU 
init
  kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device.
  -- snippet --

  In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing.
  Running '$ dpkg -L linux-firmware | sort' gives this:

  -- snippet --
  /lib/firmware/amdgpu/vegam_uvd.bin
  /lib/firmware/amdgpu/vegam_vce.bin
  /lib/firmware/amdgpu/verde_ce.bin
  /lib/firmware/amdgpu/verde_k_smc.bin
  /lib/firmware/amdgpu/verde_mc.bin
  /lib/firmware/amdgpu/verde_me.bin
  /lib/firmware/amdgpu/verde_pfp.bin
  /lib/firmware/amdgpu/verde_rlc.bin
  /lib/firmware/amdgpu/verde_smc.bin
  /lib/firmware/amdgpu/yellow_carp_asd.bin
  /lib/firmware/amdgpu/yellow_carp_ce.bin
  -- snippet --

  Copying the file from upstream
  (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/tree/amdgpu/verde_uvd.bin) didn't work on my system,
  probably because I use UEFI and the module wasn't signed (error
  below):

  -- snippet --
  kernel: [  502.174932] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't 
validate firmware "amdgpu/verde_uvd.bin"
  kernel: [  502.174992] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init 
of IP block  failed -22
  kernel: [  502.175285] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init 
failed
  kernel: [  502.175289] amdgpu :01:00.0: amdgpu: Fatal error during GPU 
init
  kernel: [  502.175293] amdgpu :01:00.0: amdgpu: amdgpu: finishing device.
  -- snippet --

  I can confirm that reverting kernel driver to 'radeonsi' makes the
  device usable again, but at the expense of Vulkan APIs (not supported
  by this driver).

  Could you, please, fix this?

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


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


[Kernel-packages] [Bug 1953249] Update Released

2022-01-04 Thread Timo Aaltonen
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  UVD firmware for AMD Southern Islands (GCN 1) GPUs is missing

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

Bug description:
  [ Impact ]

  AMD GPU not functional on Focal with HWE kernel.

  [ Test Case ]

  See original description below.

  [ Fix ]

  Cherry-pick relevant commit from upstream linux-firmware.

  [ Where Problems Could Occur ]

  Broken graphics with AMD GPUs.

  [ Original Description ]

  Release: up-to-date Focal LTS (20.04.3)
  Package-version: linux-firmware 1.187.20
  Hardware model: [AMD/ATI] Chelsea LP [Radeon HD 7730M]

  With the latest kernel upgrade (5.4 --> 5.11, if I recall correctly),
  my laptop's discrete graphics stopped working. Looking at the logs, I
  found these messages:

  -- snippet --
  kernel: [1.492908] [drm] amdgpu: dpm initialized
  kernel: [1.492932] [drm] AMDGPU Display Connectors
  kernel: [1.492951] amdgpu :01:00.0: Direct firmware load for 
amdgpu/verde_uvd.bin failed with error -2
  kernel: [1.492954] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't load 
firmware "amdgpu/verde_uvd.bin"
  kernel: [1.492957] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init 
of IP block  failed -2
  kernel: [1.493196] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init 
failed
  kernel: [1.493198] amdgpu :01:00.0: amdgpu: Fatal error during GPU 
init
  kernel: [1.493200] amdgpu :01:00.0: amdgpu: amdgpu: finishing device.
  -- snippet --

  In fact, file '/lib/firmware/amdgpu/verde_uvd.bin' was missing.
  Running '$ dpkg -L linux-firmware | sort' gives this:

  -- snippet --
  /lib/firmware/amdgpu/vegam_uvd.bin
  /lib/firmware/amdgpu/vegam_vce.bin
  /lib/firmware/amdgpu/verde_ce.bin
  /lib/firmware/amdgpu/verde_k_smc.bin
  /lib/firmware/amdgpu/verde_mc.bin
  /lib/firmware/amdgpu/verde_me.bin
  /lib/firmware/amdgpu/verde_pfp.bin
  /lib/firmware/amdgpu/verde_rlc.bin
  /lib/firmware/amdgpu/verde_smc.bin
  /lib/firmware/amdgpu/yellow_carp_asd.bin
  /lib/firmware/amdgpu/yellow_carp_ce.bin
  -- snippet --

  Copying the file from upstream
  (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
  firmware.git/tree/amdgpu/verde_uvd.bin) didn't work on my system,
  probably because I use UEFI and the module wasn't signed (error
  below):

  -- snippet --
  kernel: [  502.174932] amdgpu :01:00.0: amdgpu: amdgpu_uvd: Can't 
validate firmware "amdgpu/verde_uvd.bin"
  kernel: [  502.174992] [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* sw_init 
of IP block  failed -22
  kernel: [  502.175285] amdgpu :01:00.0: amdgpu: amdgpu_device_ip_init 
failed
  kernel: [  502.175289] amdgpu :01:00.0: amdgpu: Fatal error during GPU 
init
  kernel: [  502.175293] amdgpu :01:00.0: amdgpu: amdgpu: finishing device.
  -- snippet --

  I can confirm that reverting kernel driver to 'radeonsi' makes the
  device usable again, but at the expense of Vulkan APIs (not supported
  by this driver).

  Could you, please, fix this?

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


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


[Kernel-packages] [Bug 1954956] Re: [amdgpu] System crash

2022-01-04 Thread Daniel van Vugt
Please try:

  * The official Ubuntu kernel

  * https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
(which is much newer than your 5.14)

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

Title:
  [amdgpu] System crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System crashes about 3 times a day; no appearant relation to
  application or process or triggering situation. Happens constantly.
  Random time between incidents normally several hours. This is a
  problem for month now.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Dec 15 23:01:59 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   vhba, 20211023, 5.11.0-42-generic, x86_64: installed
   vhba, 20211023, 5.11.0-44-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
  InstallationDate: Installed on 2020-12-16 (364 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic 
root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "InputClass"
   Identifier "middle button emulation class"
   MatchIsPointer "on"
   Option "Emulate3Buttons" "on"
   EndSection
  dmi.bios.date: 06/18/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.20
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
  xserver.bootTime: Wed Dec 15 15:19:50 2021
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.11-1ubuntu1.2
  xserver.video_driver: amdgpu

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


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


[Kernel-packages] [Bug 1955049] [NEW] amdgpu kernel errors

2022-01-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

System crashes about 3 times a day; no appearant relation to application or 
process or triggering situation. Happens constantly. Random time between 
incidents normally several hours. This is a problem for month now.
Description:Ubuntu 21.04
Release:21.04

GUI crashed: Operation ceses, monitor becomes dark. In this case the monitor 
shows a static picture after some seconds of darkness. 
Remote access via SSH is possible up to some extend.  

Expected: GUI does not crash.

dmesg says:


[ 2284.101478] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for 
fences timed out!
[ 2289.993462] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, 
signaled seq=132409, emitted seq=132410
[ 2289.993826] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: 
process  pid 0 thread  pid 0
[ 2289.994175] amdgpu :0a:00.0: amdgpu: GPU reset begin!
[ 2290.169982] [drm] free PSP TMR buffer
[ 2290.198611] amdgpu :0a:00.0: amdgpu: MODE2 reset
[ 2290.198656] amdgpu :0a:00.0: amdgpu: GPU reset succeeded, trying to 
resume
[ 2290.198943] [drm] PCIE GART of 1024M enabled.
[ 2290.198945] [drm] PTB located at 0x00F40090
[ 2290.199115] [drm] PSP is resuming...
[ 2290.218996] [drm] reserve 0x40 from 0xf45700 for PSP TMR
[ 2290.262318] amdgpu :0a:00.0: amdgpu: RAS: optional ras ta ucode is not 
available
[ 2290.266897] amdgpu :0a:00.0: amdgpu: RAP: optional rap ta ucode is not 
available
[ 2290.266899] amdgpu :0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta 
ucode is not available
[ 2290.468265] [drm] kiq ring mec 2 pipe 1 q 0
[ 2290.602777] [drm] VCN decode and encode initialized successfully(under SPG 
Mode).
[ 2290.602784] amdgpu :0a:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 2290.602787] amdgpu :0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 
on hub 0
[ 2290.602788] amdgpu :0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 
on hub 0
[ 2290.602790] amdgpu :0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 
on hub 0
[ 2290.602791] amdgpu :0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 
on hub 0
[ 2290.602792] amdgpu :0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 
on hub 0
[ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 
on hub 0
[ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 
on hub 0
[ 2290.602795] amdgpu :0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 
on hub 0
[ 2290.602796] amdgpu :0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 
on hub 0
[ 2290.602797] amdgpu :0a:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 
1
[ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on 
hub 1
[ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on 
hub 1
[ 2290.602799] amdgpu :0a:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on 
hub 1
[ 2290.602800] amdgpu :0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on 
hub 1
[ 2290.609397] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow start
[ 2290.609400] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow done
[ 2290.609464] amdgpu :0a:00.0: amdgpu: GPU reset(1) succeeded!
[ 2290.609926] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[ 2290.609979] kfd kfd: amdgpu: error getting iommu info. is the iommu enabled?
[ 2290.609981] kfd kfd: amdgpu: Error initializing iommuv2
[ 2290.610175] kfd kfd: amdgpu: device 1002:15d8 NOT added due to errors
[ 2317.591058] rfkill: input handler enabled
[ 2412.382743] show_signal_msg: 29 callbacks suppressed
[ 2412.382746] apport-gtk[16593]: segfault at 18 ip 7f7f7e90e194 sp 
7fff2ca56790 error 4 in libgtk-3.so.0.2404.21[7f7f7e805000+385000]
[ 2412.382753] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b 
e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 8c 3c 17 00 <48> 8b 40 
18 48 8b 78 10 e8 df 03 09 00 48 83 c4 08 48 89 c7 e9 a3

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Dec 16 14:34:43 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 vhba, 20211023, 5.11.0-42-generic, x86_64: installed
 vhba, 20211023, 5.11.0-44-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 
00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
InstallationDate: Installed on 2020-12-16 (365 days ago)
InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.

[Kernel-packages] [Bug 1955049] Re: amdgpu kernel errors

2022-01-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1954956 ***
https://bugs.launchpad.net/bugs/1954956

You are using an unsupported kernel. Please start by trying an official
Ubuntu kernel or a newer mainline kernel.

** Summary changed:

- Xorg crash
+ amdgpu kernel errors

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

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

** This bug has been marked a duplicate of bug 1954956
   [amdgpu] System crash

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

Title:
  amdgpu kernel errors

Status in linux package in Ubuntu:
  Invalid

Bug description:
  System crashes about 3 times a day; no appearant relation to application or 
process or triggering situation. Happens constantly. Random time between 
incidents normally several hours. This is a problem for month now.
  Description:  Ubuntu 21.04
  Release:  21.04

  GUI crashed: Operation ceses, monitor becomes dark. In this case the monitor 
shows a static picture after some seconds of darkness. 
  Remote access via SSH is possible up to some extend.  

  Expected: GUI does not crash.

  dmesg says:

  
  [ 2284.101478] [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for 
fences timed out!
  [ 2289.993462] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, 
signaled seq=132409, emitted seq=132410
  [ 2289.993826] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process 
information: process  pid 0 thread  pid 0
  [ 2289.994175] amdgpu :0a:00.0: amdgpu: GPU reset begin!
  [ 2290.169982] [drm] free PSP TMR buffer
  [ 2290.198611] amdgpu :0a:00.0: amdgpu: MODE2 reset
  [ 2290.198656] amdgpu :0a:00.0: amdgpu: GPU reset succeeded, trying to 
resume
  [ 2290.198943] [drm] PCIE GART of 1024M enabled.
  [ 2290.198945] [drm] PTB located at 0x00F40090
  [ 2290.199115] [drm] PSP is resuming...
  [ 2290.218996] [drm] reserve 0x40 from 0xf45700 for PSP TMR
  [ 2290.262318] amdgpu :0a:00.0: amdgpu: RAS: optional ras ta ucode is not 
available
  [ 2290.266897] amdgpu :0a:00.0: amdgpu: RAP: optional rap ta ucode is not 
available
  [ 2290.266899] amdgpu :0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta 
ucode is not available
  [ 2290.468265] [drm] kiq ring mec 2 pipe 1 q 0
  [ 2290.602777] [drm] VCN decode and encode initialized successfully(under SPG 
Mode).
  [ 2290.602784] amdgpu :0a:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
  [ 2290.602787] amdgpu :0a:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 
on hub 0
  [ 2290.602788] amdgpu :0a:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 
on hub 0
  [ 2290.602790] amdgpu :0a:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 
on hub 0
  [ 2290.602791] amdgpu :0a:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 
on hub 0
  [ 2290.602792] amdgpu :0a:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 
on hub 0
  [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 
on hub 0
  [ 2290.602793] amdgpu :0a:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 
on hub 0
  [ 2290.602795] amdgpu :0a:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 
10 on hub 0
  [ 2290.602796] amdgpu :0a:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 
on hub 0
  [ 2290.602797] amdgpu :0a:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on 
hub 1
  [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on 
hub 1
  [ 2290.602798] amdgpu :0a:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 
on hub 1
  [ 2290.602799] amdgpu :0a:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 
on hub 1
  [ 2290.602800] amdgpu :0a:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 
on hub 1
  [ 2290.609397] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow start
  [ 2290.609400] amdgpu :0a:00.0: amdgpu: recover vram bo from shadow done
  [ 2290.609464] amdgpu :0a:00.0: amdgpu: GPU reset(1) succeeded!
  [ 2290.609926] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
  [ 2290.609979] kfd kfd: amdgpu: error getting iommu info. is the iommu 
enabled?
  [ 2290.609981] kfd kfd: amdgpu: Error initializing iommuv2
  [ 2290.610175] kfd kfd: amdgpu: device 1002:15d8 NOT added due to errors
  [ 2317.591058] rfkill: input handler enabled
  [ 2412.382743] show_signal_msg: 29 callbacks suppressed
  [ 2412.382746] apport-gtk[16593]: segfault at 18 ip 7f7f7e90e194 sp 
7fff2ca56790 error 4 in libgtk-3.so.0.2404.21[7f7f7e805000+385000]
  [ 2412.382753] Code: c4 08 5b 5d c3 90 f3 0f 1e fa 48 8b 7f 10 48 85 ff 74 0b 
e9 ce c6 ff ff 66 0f 1f 44 00 00 48 83 ec 08 48 89 d7 e8 8c 3c 17 00 <48> 8b 40 
18 48 8b 78 10 e8 df 03 09 00 48 83 c4 08 48 89 c7 e9 a3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
 

[Kernel-packages] [Bug 1955016] Re: devices on thunderbolt dock are not recognized on adl-p platform

2022-01-04 Thread Timo Aaltonen
** Tags added: verification-done-focal

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

Title:
  devices on thunderbolt dock are not recognized on adl-p 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:
  Fix Committed
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  When booting up with the TBT dock is plugged, the devices(USB, Ethernet) on 
the dock can't be recognized. It requires to run lspci command to wake up the 
PCI devices to make the devices on the dock work.

  [Fix]
  The patchset fix this runtime pm issue.
  
https://patchwork.kernel.org/project/linux-usb/cover/20211125073733.74902-1-mika.westerb...@linux.intel.com/

  [Test]
  Verified on Dell ADL-P platform with TBT dock.

  [Where the problems could occur]
  Hard to evaluate, but after some cold boot/warm boot, plug/un-plug the 
devices on the dock, didn't observe any regressions.

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


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


[Kernel-packages] [Bug 1955691] Re: audio mute/ mic mute are not working on a HP machine

2022-01-04 Thread jeremyszu
** Tags added: oem-priority originate-from-1953299 stella

** Tags added: originate-from-1953298

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

Title:
  audio mute/ mic mute are not working on a HP machine

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not working on a HP platform

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955691/+subscriptions


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


[Kernel-packages] [Bug 1956301] [NEW] Jammy update: v5.15.10 upstream stable release

2022-01-04 Thread Andrea Righi
Public bug reported:


SRU Justification

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

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


Linux 5.15.10
perf inject: Fix itrace space allowed for new attributes
fuse: make sure reclaim doesn't write the inode
staging: most: dim2: use device release method
tracing: Fix a kmemleak false positive in tracing_map
drm/amdkfd: process_info lock not needed for svm
drm/amd/display: add connector type check for CRC source set
drm/amdkfd: fix double free mem structure
drm/amd/display: Fix for the no Audio bug with Tiled Displays
drm/amdgpu: check atomic flag to differeniate with legacy path
drm/amdgpu: cancel the correct hrtimer on exit
net: netlink: af_netlink: Prevent empty skb by adding a check on len.
i2c: rk3x: Handle a spurious start completion interrupt flag
parisc/agp: Annotate parisc agp init functions with __init
ALSA: hda/hdmi: fix HDA codec entry table order for ADL-P
ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid
loop: Use pr_warn_once() for loop_control_remove() warning
net/mlx4_en: Update reported link modes for 1/10G
Revert "tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP"
s390/test_unwind: use raw opcode instead of invalid instruction
KVM: arm64: Save PSTATE early on exit
drm/msm/dp: Avoid unpowered AUX xfers that caused crashes
drm/msm/dsi: set default num_data_lanes
drm/msm/a6xx: Fix uinitialized use of gpu_scid
drm/msm: Fix null ptr access msm_ioctl_gem_submit()
i2c: virtio: fix completion handling
vmxnet3: fix minimum vectors alloc issue
ice: fix FDIR init missing when reset VF
RDMA/irdma: Don't arm the CQ more than two times if no CE for this CQ
RDMA/irdma: Report correct WC errors
RDMA/irdma: Fix a potential memory allocation issue in 
'irdma_prm_add_pble_mem()'
RDMA/irdma: Fix a user-after-free in add_pble_prm
netfs: Fix lockdep warning from taking sb_writers whilst holding mmap_lock
perf bpf_skel: Do not use typedef to avoid error on old clang
clk: qcom: sm6125-gcc: Swap ops of ice and apps on sdcc1
dt-bindings: media: nxp,imx7-mipi-csi2: Drop bad if/then schema
inet: use #ifdef CONFIG_SOCK_RX_QUEUE_MAPPING consistently
mtd: rawnand: Fix nand_choose_best_timings() on unsupported interface
mtd: rawnand: Fix nand_erase_op delay
RDMA/mlx5: Fix releasing unallocated memory in dereg MR flow
RDMA: Fix use-after-free in rxe_queue_cleanup
hwmon: (corsair-psu) fix plain integer used as NULL pointer
nfc: fix segfault in nfc_genl_dump_devices_done

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: 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/1956301

Title:
  Jammy update: v5.15.10 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.10
  perf inject: Fix itrace space allowed for new attributes
  fuse: make sure reclaim doesn't write the inode
  staging: most: dim2: use device release method
  tracing: Fix a kmemleak false positive in tracing_map
  drm/amdkfd: process_info lock not needed for svm
  drm/amd/display: add connector type check for CRC source set
  drm/amdkfd: fix double free mem structure
  drm/amd/display: Fix for the no Audio bug with Tiled Displays
  drm/amdgpu: check atomic flag to differeniate with legacy path
  drm/amdgpu: cancel the correct hrtimer on exit
  net: netlink: af_netlink: Prevent empty skb by adding a check on len.
  i2c: rk3x: Handle a spurious start completion interrupt flag
  parisc/agp: Annotate parisc agp init functions with __init
  ALSA: hda/hdmi: fix HDA codec entry table order 

[Kernel-packages] [Bug 1955691] Re: audio mute/ mic mute are not working on a HP machine

2022-01-04 Thread jeremyszu
** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Triaged

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

Title:
  audio mute/ mic mute are not working on a HP machine

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not working on a HP platform

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955691/+subscriptions


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


[Kernel-packages] [Bug 1955138] [NEW] [evdi] External monitor stops showing image for a few seconds

2022-01-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I use Dell Dock Station - D6000S and noticed in the latest two kernels an 
instability on my external monitors. I use two external monitors and they 
randomly stops showing the images for a couple of seconds. It's similar as if 
the usb-C connection to the docker got interrupted and then connected again.  
Notebook display doesn't have this issue. 
Please verify the root cause. 

Thanks,

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-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: GNOME-Flashback:GNOME
Date: Fri Dec 17 11:25:54 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 evdi, 1.9.1, 5.11.0-41-generic, x86_64: installed
 evdi, 1.9.1, 5.11.0-43-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-41-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-43-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics [1028:09a0]
InstallationDate: Installed on 2021-04-07 (253 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Latitude 5410
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2021
dmi.bios.release: 1.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 08NM43
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd03/11/2021:br1.5:svnDellInc.:pnLatitude5410:pvr:sku09A0:rvnDellInc.:rn08NM43:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5410
dmi.product.sku: 09A0
dmi.sys.vendor: Dell Inc.
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

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


** Tags: amd64 apport-bug displaylink evdi focal ubuntu
-- 
[evdi] External monitor stops showing image for a few seconds
https://bugs.launchpad.net/bugs/1955138
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 1956302] [NEW] Jammy update: v5.15.11 upstream stable release

2022-01-04 Thread Andrea Righi
Public bug reported:


SRU Justification

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

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


Linux 5.15.11
xen/netback: don't queue unlimited number of packages
xen/netback: fix rx queue stall detection
xen/console: harden hvc_xen against event channel storms
xen/netfront: harden netfront against event channel storms
xen/blkfront: harden blkfront against event channel storms
Revert "xsk: Do not sleep in poll() when need_wakeup set"
selftests/damon: test debugfs file reads/writes with huge count
bus: ti-sysc: Fix variable set but not used warning for reinit_modules
io-wq: drop wqe lock before creating new worker
rcu: Mark accesses to rcu_state.n_force_qs
io-wq: check for wq exit after adding new worker task_work
io-wq: remove spurious bit clear on task_work addition
scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()
scsi: scsi_debug: Fix type in min_t to avoid stack OOB
scsi: scsi_debug: Don't call kcalloc() if size arg is zero
ovl: fix warning in ovl_create_real()
fuse: annotate lock in fuse_reverse_inval_entry()
media: mxl111sf: change mutex_init() location
USB: core: Make do_proc_control() and do_proc_bulk() killable
bpf: Fix extable address check.
bpf, x64: Factor out emission of REX byte in more cases
mptcp: add missing documented NL params
xsk: Do not sleep in poll() when need_wakeup set
ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
can: m_can: pci: use custom bit timings for Elkhart Lake
can: m_can: make custom bittiming fields const
Revert "can: m_can: remove support for custom bit timing"
drm/amd/pm: fix reading SMU FW version from amdgpu_firmware_info on YC
drm/amdgpu: don't override default ECO_BITs setting
drm/amdgpu: correct register access for RLC_JUMP_TABLE_RESTORE
powerpc/module_64: Fix livepatching for RO modules
libata: if T_LENGTH is zero, dma direction should be DMA_NONE
perf inject: Fix segfault due to perf_data__fd() without open
perf inject: Fix segfault due to close without open
riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
riscv: dts: unleashed: Add gpio card detect to mmc-spi-slot
locking/rtmutex: Fix incorrect condition in rtmutex_spin_on_owner()
cifs: sanitize multiple delimiters in prepath
timekeeping: Really make sure wall_to_monotonic isn't positive
serial: 8250_fintek: Fix garbled text for console
iocost: Fix divide-by-zero on donation from low hweight cgroup
zonefs: add MODULE_ALIAS_FS
btrfs: fix missing blkdev_put() call in btrfs_scan_one_device()
btrfs: check WRITE_ERR when trying to read an extent buffer
btrfs: fix double free of anon_dev after failure to create subvolume
btrfs: fix memory leak in __add_inode_ref()
selinux: fix sleeping function called from invalid context
USB: serial: option: add Telit FN990 compositions
USB: serial: cp210x: fix CP2105 GPIO registration
usb: gadget: u_ether: fix race in setting MAC address in setup phase
usb: typec: tcpm: fix tcpm unregister port but leave a pending timer
usb: cdnsp: Fix lack of spin_lock_irqsave/spin_lock_restore
usb: cdnsp: Fix issue in cdnsp_log_ep trace event
usb: cdnsp: Fix incorrect calling of cdnsp_died function
usb: cdnsp: Fix incorrect status for control request
usb: xhci: Extend support for runtime power management for AMD's Yellow carp.
usb: xhci-mtk: fix list_del warning when enable list debug
PCI/MSI: Mask MSI-X vectors only on success
PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
usb: dwc2: fix STM ID/VBUS detection startup delay in dwc2_driver_probe
USB: NO_LPM quirk Lenovo USB-C to Ethernet Adapher(RTL8153-04)
tty: n_hdlc: make n_hdlc_tty_wakeup() asynchronous
KVM: x86: Drop guest CPUID check for host initiated writes to 
MSR_IA32_PERF_CAPABILITIES
Revert "usb: early: convert to readl_poll_timeout_atomic()"
USB: gadget: bRequestType is a bitfield, not a enum
powerpc/85xx: Fix oops when CONFIG_FSL_PMC=n
bpf, selftests: Fix racing issue in btf_skc_cls_ingress test
bpf: Fix extable fixup offset.
arm64: kexec: Fix missing error code 'ret' warning in load_other_segments()
afs: Fix mmap
sit: do not call ipip6_dev_free() from sit_init_net()
net: systemport: Add global locking for descriptor lifecycle
net/smc: Prevent smc_release() from long blocking
net: Fix double 0x prefix print in SKB dump
dsa: mv88e6xxx: fix debug print for SPEED_UNFORCED
sfc_ef100: potential dereference of null pointer
net: stmmac: dwmac-rk: fix oob read in rk_gmac_setup
net/packet: rx_owner_map depends on pg_vec
netdevsim: Zero-initialize memory for new map's value in function 
nsim_bpf_map_alloc
ixgbe: set X550 MDIO speed b

[Kernel-packages] [Bug 1955138] Re: [evdi] External monitor stops showing image for a few seconds

2022-01-04 Thread Daniel van Vugt
** Summary changed:

- External monitor stops showing image for a few seconds
+ [evdi] External monitor stops showing image for a few seconds

** Tags added: displaylink evdi

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

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

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

Title:
  [evdi] External monitor stops showing image for a few seconds

Status in evdi package in Ubuntu:
  New

Bug description:
  I use Dell Dock Station - D6000S and noticed in the latest two kernels an 
instability on my external monitors. I use two external monitors and they 
randomly stops showing the images for a couple of seconds. It's similar as if 
the usb-C connection to the docker got interrupted and then connected again.  
Notebook display doesn't have this issue. 
  Please verify the root cause. 

  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-41-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: GNOME-Flashback:GNOME
  Date: Fri Dec 17 11:25:54 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.9.1, 5.11.0-41-generic, x86_64: installed
   evdi, 1.9.1, 5.11.0-43-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-41-generic, x86_64: installed
   virtualbox, 6.1.26, 5.11.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09a0]
  InstallationDate: Installed on 2021-04-07 (253 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude 5410
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/11/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 08NM43
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd03/11/2021:br1.5:svnDellInc.:pnLatitude5410:pvr:sku09A0:rvnDellInc.:rn08NM43:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5410
  dmi.product.sku: 09A0
  dmi.sys.vendor: Dell Inc.
  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/evdi/+bug/1955138/+subscriptions


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


[Kernel-packages] [Bug 1956306] [NEW] package nvidia-dkms-440 440.82+really.440.64-0ubuntu6 failed to install/upgrade: installed nvidia-dkms-440 package post-installation script subprocess returned er

2022-01-04 Thread Kirill
Public bug reported:

Dont install ths package.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-440 440.82+really.440.64-0ubuntu6
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jan  4 15:47:31 2022
ErrorMessage: installed nvidia-dkms-440 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2021-12-08 (26 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.1
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-440
Title: package nvidia-dkms-440 440.82+really.440.64-0ubuntu6 failed to 
install/upgrade: installed nvidia-dkms-440 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal third-party-packages

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

Title:
  package nvidia-dkms-440 440.82+really.440.64-0ubuntu6 failed to
  install/upgrade: installed nvidia-dkms-440 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  Dont install ths package.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-440 440.82+really.440.64-0ubuntu6
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  4 15:47:31 2022
  ErrorMessage: installed nvidia-dkms-440 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-12-08 (26 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.1
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-440
  Title: package nvidia-dkms-440 440.82+really.440.64-0ubuntu6 failed to 
install/upgrade: installed nvidia-dkms-440 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1956306/+subscriptions


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


[Kernel-packages] [Bug 1956305] [NEW] Jammy update: v5.15.12 upstream stable release

2022-01-04 Thread Andrea Righi
Public bug reported:


SRU Justification

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

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


Linux 5.15.12
phonet/pep: refuse to enable an unbound pipe
tun: avoid double free in tun_free_netdev
hamradio: improve the incomplete fix to avoid NPD
hamradio: defer ax25 kfree after unregister_netdev
ax25: NPD bug when detaching AX25 device
r8152: sync ocp base
hwmon: (lm90) Do not report 'busy' status bit as alarm
hwmom: (lm90) Fix citical alarm status for MAX6680/MAX6681
pinctrl: mediatek: fix global-out-of-bounds issue
ASoC: rt5682: fix the wrong jack type detected
ASoC: SOF: Intel: pci-tgl: add ADL-N support
ASoC: SOF: Intel: pci-tgl: add new ADL-P variant
ASoC: tas2770: Fix setting of high sample rates
Input: goodix - add id->model mapping for the "9111" model
Input: elants_i2c - do not check Remark ID on eKTH3900/eKTH5312
Input: iqs626a - prohibit inlining of channel parsing functions
kfence: fix memory leak when cat kfence objects
arm64: dts: lx2160a: fix scl-gpios property name
KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
netfs: fix parameter of cleanup()
f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
tee: optee: Fix incorrect page free bug
mm/damon/dbgfs: protect targets destructions with kdamond_lock
mm/hwpoison: clear MF_COUNT_INCREASED before retrying get_any_page()
mm, hwpoison: fix condition in free hugetlb page path
mm: mempolicy: fix THP allocations escaping mempolicy restrictions
mac80211: fix locking in ieee80211_start_ap error path
ksmbd: disable SMB2_GLOBAL_CAP_ENCRYPTION for SMB 3.1.1
ksmbd: fix uninitialized symbol 'pntsd_size'
ksmbd: fix error code in ndr_read_int32()
ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
mmc: mmci: stm32: clear DLYB_CR after sending tuning command
mmc: core: Disable card detect during shutdown
mmc: meson-mx-sdhc: Set MANUAL_STOP for multi-block SDIO commands
mmc: sdhci-tegra: Fix switch to HS400ES mode
gpio: dln2: Fix interrupts when replugging the device
pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
KVM: VMX: Wake vCPU when delivering posted IRQ even if vCPU == this vCPU
KVM: VMX: Always clear vmx->fail on emulation_required
KVM: nVMX: Synthesize TRIPLE_FAULT for L2 if emulation is required
KVM: x86/mmu: Don't advance iterator after restart due to yielding
KVM: x86: Always set kvm_run->if_flag
platform/x86: intel_pmc_core: fix memleak on registration failure
platform/x86: amd-pmc: only use callbacks for suspend
x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
tee: handle lookup of shm with reference count 0
parisc: Fix mask used to select futex spinlock
parisc: Correct completer in lws start
ipmi: fix initialization when workqueue allocation fails
ipmi: ssif: initialize ssif_info->client early
ipmi: bail out if init_srcu_struct fails
Input: atmel_mxt_ts - fix double free in mxt_read_info_block
ASoC: tegra: Restore headphones jack name on Nyan Big
ASoC: tegra: Add DAPM switches for headphones and mic jack
ASoC: meson: aiu: Move AIU_I2S_MISC hold setting to aiu-fifo-i2s
ALSA: hda/realtek: Fix quirk for Clevo NJ51CU
ALSA: hda/realtek: fix mute/micmute LEDs for a HP ProBook
ALSA: hda/realtek: Add new alc285-hp-amp-init model
ALSA: hda/realtek: Amp init fixup for HP ZBook 15 G6
ALSA: hda/hdmi: Disable silent stream on GLK
ALSA: rawmidi - fix the uninitalized user_pversion
ALSA: drivers: opl3: Fix incorrect use of vp->state
ALSA: jack: Check the return value of kstrdup()
x86/boot: Move EFI range reservation after cmdline parsing
Revert "x86/boot: Pull up cmdline preparation and early param parsing"
kernel/crash_core: suppress unknown crashkernel parameter warning
platform/x86/intel: Remove X86_PLATFORM_DRIVERS_INTEL
compiler.h: Fix annotation macro misplacement with Clang
uapi: Fix undefined __always_inline on non-glibc systems
ARM: 9160/1: NOMMU: Reload __secondary_data after PROCINFO_INITFUNC
hwmon: (lm90) Drop critical attribute support for MAX6654
hwmon: (lm90) Add basic support for TI TMP461
hwmon: (lm90) Introduce flag indicating extended temperature support
hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations
hwmon: (lm90) Fix usage of CONFIG2 register in detect function
pinctrl: bcm2835: Change init order for gpio hogs
Input: elantech - fix stack out of bound access in elantech_change_report_id()
net: stmmac: dwmac-visconti: Fix value of ETHER_CLK_SEL_FREQ_SEL_2P5M
r8152: fix the force speed doesn't work for RTL8156
net: bridge: fix ioctl old_deviceless bridge argument
net: bridge: Use array_

[Kernel-packages] [Bug 1955297] Re: Xorg freeze

2022-01-04 Thread Daniel van Vugt
Please open the 'Additional Drivers' app and install the latest Nvidia
driver that it offers you. I expect it will be version 390 for the
Nvidia GeForce GT 525M. Once installed, please reboot and then tell us
if the problem persists.

** Tags added: nouveau

** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu)

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

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

** Changed in: xserver-xorg-video-nouveau (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/1955297

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  Mouse freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
  Uname: Linux 5.4.0-81-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 Dec 18 15:24:35 2021
  DistUpgraded: 2021-08-22 20:45:57,513 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: Continuously
  GpuHangReproducibility: I don't know
  GpuHangStarted: I don't know
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6]
  InstallationDate: Installed on 2021-08-08 (132 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic 
root=UUID=e240f53d-7bb3-4a6d-a0c5-abc23ed371b1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2021-08-22 (117 days ago)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  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.11-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/+bug/1955297/+subscriptions


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


[Kernel-packages] [Bug 1955632] [NEW] Screen flickering or going black

2022-01-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I've been using Ubuntu 20.04 for a long time now and have had no problems. Then 
suddenly the screen started flickering. I tried PCLinuxOS but the screen just 
goes black. I found, on Ubuntu, installing brightness-controller and putting 
the screen brightness down below half way and the setting to Clear Blue Sky 
helps quite a lot but is hard to see. It still flickers once in awhile. And I 
cannot create a file in /sys/class/backlight to make the change permanent on 
boot. The only major change I can think of is setting LivePatch up that could 
have caused the flickering.
Thank you, I hope you find the fix as no Linux distros will work on my 
ThinkCentre desktop PC.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17
Uname: Linux 5.14.0-1011-oem 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: Thu Dec 23 01:52:31 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 rtl8821CU, 5.4.1, 5.11.0-43-generic, x86_64: installed
 rtl8821CU, 5.4.1, 5.14.0-1011-oem, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[17aa:3083]
InstallationDate: Installed on 2021-10-16 (68 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: LENOVO 3227K45
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1011-oem 
root=UUID=e7536889-191e-4640-ba6f-6e940cb65228 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2018
dmi.bios.release: 0.6
dmi.bios.vendor: LENOVO
dmi.bios.version: 9SKT9CAUS
dmi.board.asset.tag: 640688
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9CAUS:bd12/11/2018:br0.6:svnLENOVO:pn3227K45:pvrThinkCentreM92P:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3227:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 3227K45
dmi.product.sku: LENOVO_MT_3227
dmi.product.version: ThinkCentre M92P
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 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-oem-5.14 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu
-- 
Screen flickering or going black
https://bugs.launchpad.net/bugs/1955632
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-oem-5.14 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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2022-01-04 Thread seo suchan
as Gaurav Negi isn't member of any activity on launchpad other then
this, I think it's begus change.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  [Impact]

  On some thinkpads we may get a kernel panic at boot, because the
  elantech driver (trakcpad) can trigger out-of-bounds access in the
  stack.

  [Test case]

  Simply boot the kernel on one of the affected systems (e.g., Thinkpad
  E14 Gen2).

  [Fix]

  Prevent the stack out of bound access by applying the following
  upstream commit (from linux-next):

  1d72d9f960cc ("Input: elantech - fix stack out of bound access in
  elantech_change_report_id()")

  [Regression potential]

  The fix is touching the elantech driver, so we could only see
  regressions with this specific trackpad/mouse driver.

  [Original bug report]

  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  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.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 1955702] [NEW] Grafikkarte Treiber

2022-01-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Grafikkarte Probleme

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 24 10:52:06 2021
DistUpgraded: 2021-12-23 00:23:01,754 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7640G] [144d:c0da]
 Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Radeon HD 7670M [144d:c0da]
InstallationDate: Installed on 2021-12-22 (1 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic 
root=UUID=fc93f578-a24f-400f-95c2-03eaf71b373f ro quiet splash
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2021-12-22 (1 days ago)
dmi.bios.date: 07/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P07ABF
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP355E7C-S09DE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: BOARD REVISION 00
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ABF:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP07ABF.010.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355E7C-S09DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: Eureka
dmi.product.name: 355V4C/356V4C/3445VC/3545VC
dmi.product.sku: P07ABF.010.CP
dmi.product.version: P07ABF.010.CP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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

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


** Tags: amd64 apport-bug focal ubuntu wayland-session
-- 
Grafikkarte Treiber
https://bugs.launchpad.net/bugs/1955702
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 1955632] Re: Screen flickering or going black

2022-01-04 Thread Daniel van Vugt
This appears to be a desktop machine so please don't install any
brightness controlling software as that's likely to cause more problems
than it solves. You should adjust the brightness on the TV itself.

Also please try a different VGA cable if you can. Or at least unplug
both ends and plug them in again firmly.


** Package changed: xorg (Ubuntu) => linux-oem-5.14 (Ubuntu)

** Summary changed:

- Screen flickering or going black
+ [i915] Screen flickering or going black

** Summary changed:

- [i915] Screen flickering or going black
+ [i915] TV connected by VGA is flickering or going black

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

Title:
  [i915] TV connected by VGA is flickering or going black

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

Bug description:
  I've been using Ubuntu 20.04 for a long time now and have had no problems. 
Then suddenly the screen started flickering. I tried PCLinuxOS but the screen 
just goes black. I found, on Ubuntu, installing brightness-controller and 
putting the screen brightness down below half way and the setting to Clear Blue 
Sky helps quite a lot but is hard to see. It still flickers once in awhile. And 
I cannot create a file in /sys/class/backlight to make the change permanent on 
boot. The only major change I can think of is setting LivePatch up that could 
have caused the flickering.
  Thank you, I hope you find the fix as no Linux distros will work on my 
ThinkCentre desktop PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17
  Uname: Linux 5.14.0-1011-oem 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: Thu Dec 23 01:52:31 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821CU, 5.4.1, 5.11.0-43-generic, x86_64: installed
   rtl8821CU, 5.4.1, 5.14.0-1011-oem, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  InstallationDate: Installed on 2021-10-16 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 3227K45
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1011-oem 
root=UUID=e7536889-191e-4640-ba6f-6e940cb65228 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2018
  dmi.bios.release: 0.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9CAUS
  dmi.board.asset.tag: 640688
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9CAUS:bd12/11/2018:br0.6:svnLENOVO:pn3227K45:pvrThinkCentreM92P:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3227:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3227K45
  dmi.product.sku: LENOVO_MT_3227
  dmi.product.version: ThinkCentre M92P
  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 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-oem-5.14/+bug/1955632/+subscriptions


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


[Kernel-packages] [Bug 1955702] Re: Grafikkarte Treiber

2022-01-04 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Grafikkarte Treiber
+ radeon kernel crashes in radeon_ttm_backend_bind

** Tags added: radeon

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

Title:
  radeon kernel crashes in radeon_ttm_backend_bind

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Grafikkarte Probleme

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 24 10:52:06 2021
  DistUpgraded: 2021-12-23 00:23:01,754 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7640G] [144d:c0da]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Radeon HD 7670M [144d:c0da]
  InstallationDate: Installed on 2021-12-22 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic 
root=UUID=fc93f578-a24f-400f-95c2-03eaf71b373f ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-12-22 (1 days ago)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07ABF
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP355E7C-S09DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ABF:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP07ABF.010.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355E7C-S09DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 355V4C/356V4C/3445VC/3545VC
  dmi.product.sku: P07ABF.010.CP
  dmi.product.version: P07ABF.010.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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/+bug/1955702/+subscriptions


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


[Kernel-packages] [Bug 1007901] Re: driver crash radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0

2022-01-04 Thread Daniel van Vugt
This bug is too old to support. It's been almost 10 years.

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

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

Title:
  driver crash radeon_gart.c:187 radeon_gart_bind+0x1b4/0x1c0

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Won't Fix
Status in Fedora:
  Fix Released

Bug description:
  Linux  3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 
x86_64 x86_64 GNU/Linux
  Linux Mint 13 maya
  MATE x64

  
  I have upgraded my Linux Mint system from previous kernel version 3.2.0-23 
and after reboot I get error on screen may be thousands of times:

  Failed to allocate:
  size: 4096000 bytes
  aligment: 0 bytes
  domains:  2

  and in dmesg is this:

  WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/radeon/radeon_gart.c:187 
radeon_gart_bind+0x1b4/0x1c0 [radeon]()
  [   23.157299] Hardware name: AMILO Pa 2510
  [   23.157301] trying to bind memory to uninitialized GART !
  [   23.157303] Modules linked in: rfcomm bnep bluetooth parport_pc ppdev 
binfmt_misc nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc ext2 ip6t_LOG 
xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT ipt_LOG xt_limit 
xt_tcpudp xt_addrtype snd_hda_codec_realtek snd_hda_codec_si3054 xt_state arc4 
snd_hda_intel snd_hda_codec ip6table_filter snd_hwdep ip6_tables snd_pcm 
snd_seq_midi nf_conntrack_netbios_ns nf_conntrack_broadcast snd_rawmidi 
nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 ath5k snd_seq_midi_event 
nf_conntrack_ftp nf_conntrack iptable_filter ip_tables snd_seq x_tables ath 
radeon snd_timer mac80211 snd_seq_device joydev snd psmouse soundcore 
sp5100_tco serio_raw ttm snd_page_alloc cfg80211 video i2c_piix4 k8temp 
drm_kms_helper edac_core edac_mce_amd mac_hid drm i2c_algo_bit shpchp lp 
parport usbhid hid pata_atiixp r8169 usb_storage
  [   23.157372] Pid: 284, comm: plymouthd Tainted: GW
3.2.0-24-generic #39-Ubuntu
  [   23.157375] Call Trace:
  [   23.157388]  [] warn_slowpath_common+0x7f/0xc0
  [   23.157392]  [] warn_slowpath_fmt+0x46/0x50
  [   23.157412]  [] ? ttm_mem_global_alloc_page+0x42/0x50 
[ttm]
  [   23.157433]  [] radeon_gart_bind+0x1b4/0x1c0 [radeon]
  [   23.157453]  [] radeon_ttm_backend_bind+0x35/0xb0 
[radeon]
  [   23.157464]  [] ttm_tt_bind+0x50/0x80 [ttm]
  [   23.157473]  [] ttm_bo_handle_move_mem+0x347/0x3c0 [ttm]
  [   23.157482]  [] ttm_bo_move_buffer+0x13a/0x150 [ttm]
  [   23.157524]  [] ? drm_mm_kmalloc+0x3c/0xe0 [drm]
  [   23.157529]  [] ? alloc_file+0x9c/0xd0
  [   23.157539]  [] ttm_bo_validate+0xe7/0xf0 [ttm]
  [   23.157547]  [] ttm_bo_init+0x1b8/0x260 [ttm]
  [   23.157569]  [] radeon_bo_create+0x176/0x2a0 [radeon]
  [   23.157590]  [] ? 
radeon_create_ttm_backend_entry+0x40/0x40 [radeon]
  [   23.157614]  [] radeon_gem_object_create+0x5a/0x100 
[radeon]
  [   23.157637]  [] radeon_gem_create_ioctl+0x58/0xd0 
[radeon]
  [   23.157643]  [] ? security_capable+0x21/0x30
  [   23.157657]  [] drm_ioctl+0x444/0x510 [drm]
  [   23.157682]  [] ? radeon_gem_pwrite_ioctl+0x30/0x30 
[radeon]
  [   23.157688]  [] ? default_spin_lock_flags+0x9/0x10
  [   23.157693]  [] ? ep_poll+0x1cc/0x380
  [   23.157698]  [] do_vfs_ioctl+0x8a/0x340
  [   23.157702]  [] ? vfs_write+0x110/0x180
  [   23.157706]  [] sys_ioctl+0x91/0xa0
  [   23.157710]  [] ? sys_epoll_wait+0x8e/0xe0
  [   23.157716]  [] system_call_fastpath+0x16/0x1b
  [   23.157719] ---[ end trace 406cb566ecd48e27 ]---
  [   23.157724] [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 1000 
pages at 0x
  [   23.163030] radeon :01:05.0: object_init failed for (4096000, 
0x0002)
  [   23.168037] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096000, 2, 4096, -22)

  So it seems to be a problem with driver for ATI in new kernel.

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


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


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

2022-01-04 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  radeon kernel crashes in radeon_ttm_backend_bind

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Grafikkarte Probleme

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 24 10:52:06 2021
  DistUpgraded: 2021-12-23 00:23:01,754 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Trinity [Radeon HD 7640G] [144d:c0da]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Radeon HD 7670M [144d:c0da]
  InstallationDate: Installed on 2021-12-22 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 355V4C/356V4C/3445VC/3545VC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic 
root=UUID=fc93f578-a24f-400f-95c2-03eaf71b373f ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2021-12-22 (1 days ago)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07ABF
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP355E7C-S09DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07ABF:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn355V4C/356V4C/3445VC/3545VC:pvrP07ABF.010.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP355E7C-S09DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 355V4C/356V4C/3445VC/3545VC
  dmi.product.sku: P07ABF.010.CP
  dmi.product.version: P07ABF.010.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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/+bug/1955702/+subscriptions


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


[Kernel-packages] [Bug 1955906] Re: [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth

2022-01-04 Thread Timo Aaltonen
** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  [SRU][J/OEM-5.14] Add an ID of QCOM WCN6855 bluetooth

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:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  An ID of WCN6855 bluetooth from Foxconn is missing.

  [Fix]
  Add an ID in btusb to load correct driver.
  This patch is based on SRU https://bugs.launchpad.net/bugs/1955689.
  Please apply it first.

  [Test]
  Verified on HW with BT headphones, it works fine.

  [Where problems could occur]
  Limited to specific HW, it may not work well.

  Due to the schedule of project and only ID is added, SRU it as SAUCE 
  patch.

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


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


[Kernel-packages] [Bug 1955691] Re: audio mute/ mic mute are not working on a HP machine

2022-01-04 Thread Timo Aaltonen
** Also affects: linux-oem-5.14 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  audio mute/ mic mute are not working on a HP machine

Status in OEM Priority Project:
  Triaged
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:
  Fix Committed

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not working on a HP platform

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955691/+subscriptions


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


[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

2022-01-04 Thread Stuart
See this AskUbuntu item on this bug
https://askubuntu.com/questions/1229456/ssh-fails-with-connection-timed-out-in-vpn-and-hangs-here-expecting-ssh2-msg

I resolved this with the suggested setting:
> As a temporary workaround, setting the KEX algorithm manually solves this 
> problem for me.
> Add KexAlgorithms ecdh-sha2-nistp521 to the corresponding SSH config, or add 
> -oKexAlgorithms=ecdh-sha2-nistp521 to the command line args for one time use.

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openconnect package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Invalid
Status in openconnect source package in Xenial:
  Confirmed

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: MACs cto

[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)

2022-01-04 Thread Georgi Boiko
Got a newer nvidia driver (470) to work with this kernel over the
holidays.

The issue still applies, regardless of the GPU selected in prime-select.

I started getting new ACPI errors with it, which could be unrelated
(empty lines are in actual output):

[  196.405777] ACPI Error: Thread 25047680 cannot release Mutex [ECMX]
acquired by thread 14745600 (20210604/exmutex-378)

[  196.405804] No Local Variables are initialized for Method [_Q66]

[  196.405809] No Arguments are initialized for method [_Q66]

[  196.405815] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to 
previous error (AE_AML_NOT_OWNER) (20210604/psparse-529)
[  196.426883] input: U as 
/devices/pci:00/:00:1c.0/:02:00.0/:03:04.0/:39:00.0/:3a:04.0/:3c:00.0/:3d:01.0/:3e:00.0/usb5/5-1/5-1.1/5-1.1.4/5-1.1.4:1.0/0003:2A7A:4103.000F/input/input44
[  196.483631] hid-generic 0003:2A7A:4103.000F: input,hidraw4: USB HID v1.10 
Keyboard [U] on usb-:3e:00.0-1.1.4/input0
[  196.489779] input: U Consumer Control as 
/devices/pci:00/:00:1c.0/:02:00.0/:03:04.0/:39:00.0/:3a:04.0/:3c:00.0/:3d:01.0/:3e:00.0/usb5/5-1/5-1.1/5-1.1.4/5-1.1.4:1.1/0003:2A7A:4103.0010/input/input45
[  196.547646] input: U System Control as 
/devices/pci:00/:00:1c.0/:02:00.0/:03:04.0/:39:00.0/:3a:04.0/:3c:00.0/:3d:01.0/:3e:00.0/usb5/5-1/5-1.1/5-1.1.4/5-1.1.4:1.1/0003:2A7A:4103.0010/input/input46
[  196.547809] hid-generic 0003:2A7A:4103.0010: input,hidraw5: USB HID v1.10 
Device [U] on usb-:3e:00.0-1.1.4/input1
[  196.563812] ACPI Error: Thread 24988608 cannot release Mutex [ECMX] acquired 
by thread 14745600 (20210604/exmutex-378)

[  196.563851] No Local Variables are initialized for Method [_Q66]

[  196.563859] No Arguments are initialized for method [_Q66]

[  196.563869] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due
to previous error (AE_AML_NOT_OWNER) (20210604/psparse-529)

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

Title:
  External monitor does not wake up on Titan Ridge laptops when docked
  (9500, TB16)

Status in Dell Sputnik:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-meta-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Won't Fix
Status in linux-oem-5.13 package in Ubuntu:
  Won't Fix
Status in linux-oem-5.14 package in Ubuntu:
  Won't Fix

Bug description:
  I've recently upgraded my workhorse from XPS 9560 (2016) to a newer
  generation XPS 9500 (2020) and ran into several things that feel like
  regressions, but are probably related to hardware changes. This is one
  of them.

  tl;dr:
  When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) 
connected to the dock via USB-C to USB-C (DP alternate mode), most of the time 
the monitor fails to wake up after going blank.

  
  details:
  Simplest way to reproduce is for hit Super+L, wait for the monitor to 
properly go in standby, then type something in or move the mouse to wake it up. 
8 times out of 10 it does not wake up when using XPS 9500. Most of the time 
this can be fixed by power cycling the monitor, however this has a seemingly 
random chance of triggering two other issues:

  1. The system to lose sight of the monitor for a brief period of time, which 
sometimes causes it to hang with a black screen and needs some combination of 
restarting the monitor, the dock, and the laptop, because there is a separate 
USB issue making hot-plugging unusable.
  2. The monitor itself gets stuck in a weird standby state where it stops 
reacting to button presses and I need to hold the power button a bit longer for 
it to sort of hard reset?

  Notably, it wakes up fine every time when using XPS 9560 or Precision
  5520 in the same setup which I have been using for ages.

  This becomes particularly troublesome when screens go into short-lived
  standby during boot: after the Dell logo, after entering the LUKS
  password, after logging in. Each of these points has a chance of
  triggering the bug, because it looks like there is some sort of mode
  change and waking signal submission happening between them that
  triggers it. I had to disable screen timeout as a temporary workaround
  to be able to work on this system at all without having to play
  "monitor wake lottery" every time I go brew a cuppa. The workaround at
  boot time is to either re-roll the lottery, or boot with the dock
  connected and lid open, then close the lid and keep working from
  there.

  The dock, the monitor, all USB peripherals are the same in both cases
  - it's literally just the TB16 cable plugged into a different laptop.

  I have attempted  5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM
  (-20.04b and -20.04-edge) kernels on the 9500 with same results. I
  have attempted disabling USB autosuspe

[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

2022-01-04 Thread Stuart
This is still a current problem

$ dpkg -l | grep -i openvpn
ii  network-manager-openvpn 1.8.14-1
   amd64network management framework (OpenVPN 
plugin core)
ii  network-manager-openvpn-gnome   1.8.14-1
   amd64network management framework (OpenVPN 
plugin GNOME GUI)
ii  openvpn 2.5.1-3ubuntu1  
   amd64virtual private network daemon

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 21.10
Release:21.10
Codename:   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/1874257

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openconnect package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Invalid
Status in openconnect source package in Xenial:
  Confirmed

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes

[Kernel-packages] [Bug 1730924]

2022-01-04 Thread andy.shevchenko
I have reassigned this to Jonas because it seems he knows much better
the state of affairs with this crappy hardware/firmware than vendor
does. Jonas, if you are not comfortable, tell me what to do with this
bug report (and AFAIU the v5.15+ behaves much more stable nowadays,
correct?).

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

Title:
  Wifi does down "crash" in Surface Pro 4

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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


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


[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

2022-01-04 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => 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/1730924

Title:
  Wifi does down "crash" in Surface Pro 4

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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


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


[Kernel-packages] [Bug 1954926] Re: Focal: CIFS stable updates

2022-01-04 Thread Tim Gardner
https://lists.ubuntu.com/archives/kernel-team/2022-January/126897.html

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

Title:
  Focal: CIFS stable updates

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux-azure source package in Focal:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Backport several stable updates to v5.4 Azure

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  Samba connections could fail

  [Other Info]

  SF: #00324495

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


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


[Kernel-packages] [Bug 1951440] Re: Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15

2022-01-04 Thread Andrea Righi
** Changed in: linux (Ubuntu Jammy)
   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/1951440

Title:
  Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
  CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON on jammy 5.15

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

Bug description:
  Starting with the following commit, upstream kernel is enabling Intel
  IOMMU related options by default:

   792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by
  default")

  We should follow upstream direction enabling
  CONFIG_INTEL_IOMMU_DEFAULT_ON and
  CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.

  A downside is that this change may introduce boot regressions on old
  systems (especially those with buggy firmware).

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


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


[Kernel-packages] [Bug 1956232] Re: ipu6: ov01a1s: failed to init camera

2022-01-04 Thread Alex Tu
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  ipu6: ov01a1s: failed to init camera

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With proposed oem-5.14 kernel from bug 1955383 and latest middleware
  installed, cheese no longer gives video streaming.

  Installed middleware are:
  * linux-firmware:   1.187.24+staging.39
  * libipu6:  0~git202112020845.a14b40c-1~ubuntu20.04.1
  * libcamhal-common: 0~git202112130639.4585612~ubuntu20.04.1
  * libcamhal0:   0~git202112130639.4585612~ubuntu20.04.1
  * libgsticamerainterface-1.0-1: 0~git202112230614.eb13eb1~ubuntu20.04.1
  * gstreamer1.0-icamera: 0~git202112230614.eb13eb1~ubuntu20.04.1

  But when switched back to following ones, same oem-5.14 kernel works
  just fine:

  * libipu6:  0~git202104021802.45905c6-1~ubuntu20.04.1
  * libcamhal-common: 0~git202105200731.43dcb4c~ubuntu20.04.1
  * libcamhal0:   0~git202105200731.43dcb4c~ubuntu20.04.1
  * libgsticamerainterface-1.0-1: 0~git202104021904.aeed9b9~ubuntu20.04.1
  * gstreamer1.0-icamera: 0~git202104021904.aeed9b9~ubuntu20.04.1

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2171 F pulseaudio
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-mewtwo+X103
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-17 (17 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 9420
  Package: linux-firmware 1.187.24+staging.39 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-2013-oem 
root=UUID=f010c12a-7bf3-4d44-8e9e-6236b24bdb57 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-2013.13+lp1955383.1-oem 5.14.20
  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.14.0-2013-oem N/A
   linux-backports-modules-5.14.0-2013-oem  N/A
   linux-firmware   1.187.24+staging.39
  Tags: focal third-party-packages
  Uname: Linux 5.14.0-2013-oem x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/25/2021
  dmi.bios.release: 89.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 89.5.23
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr89.5.23:bd01/25/2021:br89.5:svnDellInc.:pnLatitude9420:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0A32:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1956232/+subscriptions


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


[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

2022-01-04 Thread Dan Lenski
@Stuart-ward wrote…

> This is still a current problem
> 
> $ dpkg -l | grep -i openvpn
> ii network-manager-openvpn 1.8.14-1 amd64 network management framework 
> (OpenVPN plugin core)
> ii network-manager-openvpn-gnome 1.8.14-1 amd64 network management framework 
> (OpenVPN plugin GNOME GUI)
> ii openvpn 2.5.1-3ubuntu1 amd64 virtual private network daemon

Once again, OpenConnect and OpenVPN are *not* the same thing. At all.

For your VPN connection, are you using OpenConenct (the original subject
of this bug report), or are you using OpenVPN (completely different and
should have a separate bug files)?

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openconnect package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Invalid
Status in openconnect source package in Xenial:
  Confirmed

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 
chacha20-p

[Kernel-packages] [Bug 1946686] Re: Fix zfs_get_data access to files with wrong generation causing panics

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package zfs-linux - 2.0.2-1ubuntu5.4

---
zfs-linux (2.0.2-1ubuntu5.4) hirsute; urgency=medium

  * Fix zfs_get_data access to files causing panics (LP: #1946686)
   - 
debian/patches/4900-Fix-zfs_get_data-access-to-files-with-wrong-generati.patch
 backport from upstream ZFS commit 296a4a369bc1078a694f88570972330985b3b1b8
 ("Fix zfs_get_data access to files with wrong generation")

 -- Colin Ian King   Tue, 12 Oct 2021 12:34:17
+0100

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

Title:
  Fix zfs_get_data access to files with wrong generation causing panics

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  == SRU Focal/Hirsute ==

  [Impact]

  ZFS: Fix a panic while acquiring a lock.

  If TX_WRITE is create on a file, and the file is later deleted and a new
  directory is created on the same object id, it is possible that when
  zil_commit happens, zfs_get_data will be called on the new directory.
  This may result in panic as it tries to do range lock. 

  Upstream ZFS bug #10593, #11682, upstream fix:

  commit 296a4a369bc1078a694f88570972330985b3b1b8
  Author: Chunwei Chen 
  Date: Fri Mar 19 22:53:31 2021 -0700

  Fix zfs_get_data access to files with wrong generation

  This patch fixes this issue by record the generation number during
  zfs_log_write, so zfs_get_data can check if the object is valid.

  The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a
  relatively simple backport with only minor backporting effort required
  in moving some of the module specific upstream changes into the pre-
  renamed module specific os specific parts of the ZFS module.

  [Test Plan]

  This is difficult to reproduce, see
  https://github.com/openzfs/zfs/issues/10593

  The fix has been tested with the complete ubuntu autotest ZFS
  regression tests that exercise ZFS core functionality (smoke tests),
  file system POSIX compliance (fs tests), extra XFS tests and every
  mount option with stress-ng file I/O stress tests.

  [Where problems could occur]

  This fix could regress the ZIL (ZFS intent log) commit writes since it
  modifies this code to now checks for generation numbers. Testing with
  ZFS autotests with intent logs have not found any regressions, but
  there is a risk that the ZIL functionality is affected. This could
  lead to corruption.

  --

  As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs-
  linux/+question/696659, the following pull request fixes a panic
  acquiring a lock: https://github.com/openzfs/zfs/pull/11682

  This fix does not appear to be a part of the latest Ubuntu 20.04
  release:

  zfsutils-linux:
    Installed: 0.8.3-1ubuntu12.12
    Candidate: 0.8.3-1ubuntu12.12
    Version table:
   *** 0.8.3-1ubuntu12.12 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12.9 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   0.8.3-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Of note is this issue where the bug is reported against the Ubuntu
  0.8.3 packages: https://github.com/openzfs/zfs/issues/10642

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


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


[Kernel-packages] [Bug 1946686] Update Released

2022-01-04 Thread Andy Whitcroft
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Fix zfs_get_data access to files with wrong generation causing panics

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  Fix Released
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  == SRU Focal/Hirsute ==

  [Impact]

  ZFS: Fix a panic while acquiring a lock.

  If TX_WRITE is create on a file, and the file is later deleted and a new
  directory is created on the same object id, it is possible that when
  zil_commit happens, zfs_get_data will be called on the new directory.
  This may result in panic as it tries to do range lock. 

  Upstream ZFS bug #10593, #11682, upstream fix:

  commit 296a4a369bc1078a694f88570972330985b3b1b8
  Author: Chunwei Chen 
  Date: Fri Mar 19 22:53:31 2021 -0700

  Fix zfs_get_data access to files with wrong generation

  This patch fixes this issue by record the generation number during
  zfs_log_write, so zfs_get_data can check if the object is valid.

  The fix is already in Ubuntu ZFS 2.0.6 in Impish. The fix is a
  relatively simple backport with only minor backporting effort required
  in moving some of the module specific upstream changes into the pre-
  renamed module specific os specific parts of the ZFS module.

  [Test Plan]

  This is difficult to reproduce, see
  https://github.com/openzfs/zfs/issues/10593

  The fix has been tested with the complete ubuntu autotest ZFS
  regression tests that exercise ZFS core functionality (smoke tests),
  file system POSIX compliance (fs tests), extra XFS tests and every
  mount option with stress-ng file I/O stress tests.

  [Where problems could occur]

  This fix could regress the ZIL (ZFS intent log) commit writes since it
  modifies this code to now checks for generation numbers. Testing with
  ZFS autotests with intent logs have not found any regressions, but
  there is a risk that the ZIL functionality is affected. This could
  lead to corruption.

  --

  As mentioned at https://answers.launchpad.net/ubuntu/+source/zfs-
  linux/+question/696659, the following pull request fixes a panic
  acquiring a lock: https://github.com/openzfs/zfs/pull/11682

  This fix does not appear to be a part of the latest Ubuntu 20.04
  release:

  zfsutils-linux:
    Installed: 0.8.3-1ubuntu12.12
    Candidate: 0.8.3-1ubuntu12.12
    Version table:
   *** 0.8.3-1ubuntu12.12 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.8.3-1ubuntu12.9 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   0.8.3-1ubuntu12 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Of note is this issue where the bug is reported against the Ubuntu
  0.8.3 packages: https://github.com/openzfs/zfs/issues/10642

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


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


[Kernel-packages] [Bug 1956177] [NEW] battery not detected by ACPI

2022-01-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
[0.528105] ACPI: battery: Slot [BAT1] (battery absent)

But asking lshw for power devices, it says:
*-battery 
   description: Lithium Ion Battery
   product: CP753347-01
   vendor: FUJITSU
   physical id: 1
   serial: 02A-Z201219003557Z
   slot: Internal Battery
   capacity: 45032mWh
   configuration: voltage=10,8V

I've updated the BIOS to latest version 1.12 already, with no better
result. What is the problem here, and how can I fix it?

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


** Tags: bot-comment
-- 
battery not detected by ACPI
https://bugs.launchpad.net/bugs/1956177
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 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-495 -
495.46-0ubuntu0.21.10.1

---
nvidia-graphics-drivers-495 (495.46-0ubuntu0.21.10.1) impish; urgency=medium

  [ Daniel van Vugt ]
  * debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
  which is where Mesa searches for it.

  [ Alberto Milone ]
  * debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
  1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8

  * New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
  nvidia-drm_gbm.so pointing to the file libnvidia-
  allocator.so.VERSION to implement a GBM backend driver usable
  with the GBM loader from the Mesa project version 21.2 and
  above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
  15_nvidia_gbm.json, which implement EGL support for the GBM
  platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
  starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
  deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This
  functionality is now provided by other driver libraries.
- Changed the minimum required Linux kernel version from 2.6.32
  to 3.10.
- Updated nvidia.ko to load even if no supported NVIDIA GPUs are
  present when an NVIDIA NVSwitch device is detected in the
  system. Previously, nvidia.ko would fail to load into the
  kernel if no supported GPUs were present.
- Fixed a bug in the Vulkan driver where unused input attributes
  to a vertex shader would corrupt the interpolation qualifiers
  for the shader.
- Fixed a bug in the Vulkan driver where individual components of
  barycentric inputs could not be read.
- Added support for the VK_KHR_present_id extension.
- Added support for the VK_KHR_present_wait extension.
- Added support for the
  VK_KHR_shader_subgroup_uniform_control_flow extension.
- Fixed a bug where VK_NVX_binary_import was advertised as
  supported on unsupported platforms. This caused calls to
  vkCreateDevice to fail if applications attempted to enable
  VK_NVX_binary_import on such platforms.
- Added a new command line option, "--no-peermem", to nvidia-
  installer. Selecting this option prevents the installation of
  the nvidia-peermem kernel module.
- Fixed a regression which prevented DisplayPort and HDMI 2.1
  variable refresh rate (VRR) G-SYNC Compatible monitors from
  functioning correctly in variable refresh rate mode, resulting
  in issues such as flickering.
- Fixed a bug that can cause a kernel crash in SLI Mosaic
  configurations.
- Added support for the EGL_NV_robustness_video_memory_purge
  extension.

 -- Alberto Milone   Thu, 16 Dec 2021
14:55:33 +0100

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Impish)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
  and 470 in Focal

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
  Fix Released

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

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

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

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

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers t

[Kernel-packages] [Bug 1953522] Re: Ubuntu version macros overflow with high ABI numbers

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-495 -
495.46-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-495 (495.46-0ubuntu0.20.04.1) focal; urgency=medium

  [ Daniel van Vugt ]
  * debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
  which is where Mesa searches for it.

  [ Alberto Milone ]
  * debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
  1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8

  * New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
  nvidia-drm_gbm.so pointing to the file libnvidia-
  allocator.so.VERSION to implement a GBM backend driver usable
  with the GBM loader from the Mesa project version 21.2 and
  above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
  15_nvidia_gbm.json, which implement EGL support for the GBM
  platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
  starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
  deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This
  functionality is now provided by other driver libraries.
- Changed the minimum required Linux kernel version from 2.6.32
  to 3.10.
- Updated nvidia.ko to load even if no supported NVIDIA GPUs are
  present when an NVIDIA NVSwitch device is detected in the
  system. Previously, nvidia.ko would fail to load into the
  kernel if no supported GPUs were present.
- Fixed a bug in the Vulkan driver where unused input attributes
  to a vertex shader would corrupt the interpolation qualifiers
  for the shader.
- Fixed a bug in the Vulkan driver where individual components of
  barycentric inputs could not be read.
- Added support for the VK_KHR_present_id extension.
- Added support for the VK_KHR_present_wait extension.
- Added support for the
  VK_KHR_shader_subgroup_uniform_control_flow extension.
- Fixed a bug where VK_NVX_binary_import was advertised as
  supported on unsupported platforms. This caused calls to
  vkCreateDevice to fail if applications attempted to enable
  VK_NVX_binary_import on such platforms.
- Added a new command line option, "--no-peermem", to nvidia-
  installer. Selecting this option prevents the installation of
  the nvidia-peermem kernel module.
- Fixed a regression which prevented DisplayPort and HDMI 2.1
  variable refresh rate (VRR) G-SYNC Compatible monitors from
  functioning correctly in variable refresh rate mode, resulting
  in issues such as flickering.
- Fixed a bug that can cause a kernel crash in SLI Mosaic
  configurations.
- Added support for the EGL_NV_robustness_video_memory_purge
  extension.

 -- Alberto Milone   Thu, 16 Dec 2021
15:05:55 +0100

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
  and 470 in Focal

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
  Fix Released

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

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

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

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

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

  [Regression Potential]
  In orde

[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-470 -
470.86-0ubuntu0.20.04.2

---
nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal; urgency=medium

  * debian/{nvidia_supported|pm-aliases-gen}:
- Drop the following IDs in favour of the 495 series (LP: #1954818):
  1fbc, 249c, 249d, 24b6, 24b7, 24b8,
  25a0, 25b8.

 -- Alberto Milone   Tue, 14 Dec 2021
17:18:52 +0100

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
  and 470 in Focal

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
  Fix Released

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 470 (focal only) ==

  nvidia-graphics-drivers-470 (470.86-0ubuntu0.20.04.2) focal;
  urgency=medium

    * debian/{nvidia_supported|pm-aliases-gen}:
  - Drop the following IDs in favour of the 495 series (LP: #1954818):
    1fbc, 249c, 249d, 24b6, 24b7, 24b8,
    25a0, 25b8.

  == 495 (bionic, focal, hirsute, impish) ==

  nvidia-graphics-drivers-495 (495.46-0ubuntu*)

[ Daniel van Vugt ]
* debian/templates/libnvidia-extra-flavour.links.in:
  - Move nvidia-drm_gbm.so into the gbm/ library subdirectory
which is where Mesa searches for it.

[ Alberto Milone ]
    * debian/additional_card_ids,
  debian/additional_runtimepm_ids:
  - Add the following IDs:
    1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8

    * New upstream release (LP: #1954818):
  - Added support for the GBM API. This adds the new symlink
    nvidia-drm_gbm.so pointing to the file libnvidia-
    allocator.so.VERSION to implement a GBM backend driver usable
    with the GBM loader from the Mesa project version 21.2 and
    above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
    15_nvidia_gbm.json, which implement EGL support for the GBM
    platform (EGL_KHR_platform_gbm).
  - Add indicator for Resizable BAR support on compatible systems.
  - Fixed a bug that could cause the X server to crash when
    starting a new server generation on PRIME configurations.
  - Removed support for NvIFROpenGL. This functionality was
    deprecated in the 470.xx driver release.
  - Removed libnvidia-cbl.so from the driver package. This
    functionality is now provided by other driver libraries.
  - Changed the minimum required Linux kernel version from 2.6.32
    to 3.10.
  - Updated nvidia.ko to load even if no supported NVIDIA GPUs are
    present when an NVIDIA NVSwitch device is detected in the
    system. Previously, nvidia.ko would fail to load into the
    kernel if no supported GPUs were present.
  - Fixed a bug in the Vulkan driver where unused input attributes
    to a vertex shader would corrupt the interpolation qualifiers
    for the shader.
  - Fixed a bug in the Vulkan driver where individual components of
    barycentric inputs could not be read.
  - Added support for the VK_KHR_present_id extension.
  - Added support for the VK_KHR_present_wait extension.
  - Added support for the
    VK_KHR_shader_subgroup_uniform_control_flow extension.
  - Fixed

[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-495 -
495.46-0ubuntu0.21.04.1

---
nvidia-graphics-drivers-495 (495.46-0ubuntu0.21.04.1) hirsute; urgency=medium

  [ Daniel van Vugt ]
  * debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
  which is where Mesa searches for it.

  [ Alberto Milone ]
  * debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
  1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8

  * New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
  nvidia-drm_gbm.so pointing to the file libnvidia-
  allocator.so.VERSION to implement a GBM backend driver usable
  with the GBM loader from the Mesa project version 21.2 and
  above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
  15_nvidia_gbm.json, which implement EGL support for the GBM
  platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
  starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
  deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This
  functionality is now provided by other driver libraries.
- Changed the minimum required Linux kernel version from 2.6.32
  to 3.10.
- Updated nvidia.ko to load even if no supported NVIDIA GPUs are
  present when an NVIDIA NVSwitch device is detected in the
  system. Previously, nvidia.ko would fail to load into the
  kernel if no supported GPUs were present.
- Fixed a bug in the Vulkan driver where unused input attributes
  to a vertex shader would corrupt the interpolation qualifiers
  for the shader.
- Fixed a bug in the Vulkan driver where individual components of
  barycentric inputs could not be read.
- Added support for the VK_KHR_present_id extension.
- Added support for the VK_KHR_present_wait extension.
- Added support for the
  VK_KHR_shader_subgroup_uniform_control_flow extension.
- Fixed a bug where VK_NVX_binary_import was advertised as
  supported on unsupported platforms. This caused calls to
  vkCreateDevice to fail if applications attempted to enable
  VK_NVX_binary_import on such platforms.
- Added a new command line option, "--no-peermem", to nvidia-
  installer. Selecting this option prevents the installation of
  the nvidia-peermem kernel module.
- Fixed a regression which prevented DisplayPort and HDMI 2.1
  variable refresh rate (VRR) G-SYNC Compatible monitors from
  functioning correctly in variable refresh rate mode, resulting
  in issues such as flickering.
- Fixed a bug that can cause a kernel crash in SLI Mosaic
  configurations.
- Added support for the EGL_NV_robustness_video_memory_purge
  extension.

 -- Alberto Milone   Thu, 16 Dec 2021
15:00:53 +0100

** Changed in: nvidia-graphics-drivers-495 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
  and 470 in Focal

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
  Fix Released

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

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

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

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

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

  [Regression Potential]
  In or

[Kernel-packages] [Bug 1954818] Re: Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish, and 470 in Focal

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-495 -
495.46-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-495 (495.46-0ubuntu0.18.04.1) bionic; urgency=medium

  [ Daniel van Vugt ]
  * debian/templates/libnvidia-extra-flavour.links.in:
- Move nvidia-drm_gbm.so into the gbm/ library subdirectory
  which is where Mesa searches for it.

  [ Alberto Milone ]
  * debian/additional_card_ids,
debian/additional_runtimepm_ids:
- Add the following IDs:
  1FBC 249C 249D 24B6 24B7 24B8 25A0 25B8

  * New upstream release (LP: #1954818):
- Added support for the GBM API. This adds the new symlink
  nvidia-drm_gbm.so pointing to the file libnvidia-
  allocator.so.VERSION to implement a GBM backend driver usable
  with the GBM loader from the Mesa project version 21.2 and
  above, as well as the files libnvidia-egl-gbm.so.1.1.0 and
  15_nvidia_gbm.json, which implement EGL support for the GBM
  platform (EGL_KHR_platform_gbm).
- Add indicator for Resizable BAR support on compatible systems.
- Fixed a bug that could cause the X server to crash when
  starting a new server generation on PRIME configurations.
- Removed support for NvIFROpenGL. This functionality was
  deprecated in the 470.xx driver release.
- Removed libnvidia-cbl.so from the driver package. This
  functionality is now provided by other driver libraries.
- Changed the minimum required Linux kernel version from 2.6.32
  to 3.10.
- Updated nvidia.ko to load even if no supported NVIDIA GPUs are
  present when an NVIDIA NVSwitch device is detected in the
  system. Previously, nvidia.ko would fail to load into the
  kernel if no supported GPUs were present.
- Fixed a bug in the Vulkan driver where unused input attributes
  to a vertex shader would corrupt the interpolation qualifiers
  for the shader.
- Fixed a bug in the Vulkan driver where individual components of
  barycentric inputs could not be read.
- Added support for the VK_KHR_present_id extension.
- Added support for the VK_KHR_present_wait extension.
- Added support for the
  VK_KHR_shader_subgroup_uniform_control_flow extension.
- Fixed a bug where VK_NVX_binary_import was advertised as
  supported on unsupported platforms. This caused calls to
  vkCreateDevice to fail if applications attempted to enable
  VK_NVX_binary_import on such platforms.
- Added a new command line option, "--no-peermem", to nvidia-
  installer. Selecting this option prevents the installation of
  the nvidia-peermem kernel module.
- Fixed a regression which prevented DisplayPort and HDMI 2.1
  variable refresh rate (VRR) G-SYNC Compatible monitors from
  functioning correctly in variable refresh rate mode, resulting
  in issues such as flickering.
- Fixed a bug that can cause a kernel crash in SLI Mosaic
  configurations.
- Added support for the EGL_NV_robustness_video_memory_purge
  extension.

 -- Alberto Milone   Thu, 16 Dec 2021
15:08:58 +0100

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

Title:
  Update the 495 NVIDIA series in Bionic, Focal, Hirsute, and Impish,
  and 470 in Focal

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Invalid
Status in nvidia-graphics-drivers-495 source package in Impish:
  Fix Released

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

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

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

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

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

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are atta

[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1953287] Re: test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and variants

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1951997] Re: Bionic update: upstream stable patchset 2021-11-23

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

[Kernel-packages] [Bug 1950816] Re: Bionic update: upstream stable patchset 2021-11-12

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-166.174

---
linux (4.15.0-166.174) bionic; urgency=medium

  * bionic/linux: 4.15.0-166.174 -proposed tracker (LP: #1953667)

  * Ubuntu version macros overflow with high ABI numbers (LP: #1953522)
- SAUCE: Revert "stable: clamp SUBLEVEL in 4.14"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287)
- SAUCE: Revert "bpf: add also cbpf long jump test cases with heavy 
expansion"

  * test_bpf.sh test in net of ubuntu_kernel_selftests failed on B-4.15 and
variants (LP: #1953287) // CVE-2018-25020
- bpf: fix truncated jump targets on heavy expansions

linux (4.15.0-165.173) bionic; urgency=medium

  * bionic/linux: 4.15.0-165.173 -proposed tracker (LP: #1952780)

  * Support builtin revoked certificates (LP: #1932029)
- certs: Add EFI_CERT_X509_GUID support for dbx entries
- certs: Move load_system_certificate_list to a common function
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
- SAUCE: integrity: add informational messages when revoking certs

  * CVE-2021-4002
- arm64: tlb: Provide forward declaration of tlb_flush() before including
  tlb.h
- mm: mmu_notifier fix for tlb_end_vma
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

linux (4.15.0-164.172) bionic; urgency=medium

  * bionic/linux: 4.15.0-164.172 -proposed tracker (LP: #1952348)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * Bionic update: upstream stable patchset 2021-11-23 (LP: #1951997)
- btrfs: always wait on ordered extents at fsync time
- ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default
- xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF
- xtensa: xtfpga: Try software restart before simulating CPU reset
- NFSD: Keep existing listeners on portlist error
- netfilter: ipvs: make global sysctl readonly in non-init netns
- NIOS2: irqflags: rename a redefined register name
- can: rcar_can: fix suspend/resume
- can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state
  notification
- can: peak_pci: peak_pci_remove(): fix UAF
- ocfs2: fix data corruption after conversion from inline format
- ocfs2: mount fails with buffer overflow in strlen
- elfcore: correct reference to CONFIG_UML
- ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
- ASoC: DAPM: Fix missing kctl change notifications
- nfc: nci: fix the UAF of rf_conn_info object
- isdn: cpai: check ctr->cnr to avoid array index out of bound
- netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
- btrfs: deal with errors when checking if a dir entry exists during log
  replay
- net: stmmac: add support for dwmac 3.40a
- ARM: dts: spear3xx: Fix gmac node
- isdn: mISDN: Fix sleeping function called from invalid context
- platform/x86: intel_scu_ipc: Update timeout value in comment
- ALSA: hda: avoid write to STATESTS if controller is in reset
- tracing: Have all levels of checks prevent recursion
- ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
- dma-debug: fix sg checks in debug_dma_map_sg()
- ASoC: wm8960: Fix clock configuration on slave mode
- lan78xx: select CRC32
- net: hns3: add limit ets dwrr bandwidth cannot be 0
- net: hns3: disable sriov before unload hclge layer
- ALSA: hda/realtek: Add quirk for Clevo PC50HS
- mm, slub: fix mismatch between reconstructed freelist depth and cnt
- gcc-plugins/structleak: add makefile var for disabling structleak

  * creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve
failed with XFS (LP: #1950239)
- xfs: ensure that the inode uid/gid match values match the icdinode ones
- xfs: merge the projid fields in struct xfs_icdinode
- xfs: remove the icdinode di_uid/di_gid members
- xfs: fix up non-directory creation in SGID directories

  * ubuntu_ltp / finit_module02 fails on v4.15 and oth

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

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

apport-collect 1956177

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

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better
  result. What is the problem here, and how can I fix it?

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


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


[Kernel-packages] [Bug 1956177] Re: battery not detected by ACPI

2022-01-04 Thread Paul White
There is no 'kernel-package' package in the impish release. Moving bug
report to 'linux' which is the correct package for the Linux kernel.

** Package changed: kernel-package (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/1956177

Title:
  battery not detected by ACPI

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with 
kernel 5.13.0-22-generic, there is an issue with the internal battery. When 
kernel boots up, ACPI isn't able to detect it correctly, see dmesg line:
  [0.528105] ACPI: battery: Slot [BAT1] (battery absent)

  But asking lshw for power devices, it says:
  *-battery 
 description: Lithium Ion Battery
 product: CP753347-01
 vendor: FUJITSU
 physical id: 1
 serial: 02A-Z201219003557Z
 slot: Internal Battery
 capacity: 45032mWh
 configuration: voltage=10,8V

  I've updated the BIOS to latest version 1.12 already, with no better
  result. What is the problem here, and how can I fix it?

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


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


[Kernel-packages] [Bug 1951883] Re: Focal update: v5.4.157 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1951295] Re: Focal update: v5.4.156 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1951291] Re: Focal update: v5.4.155 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1951288] Re: Focal update: v5.4.154 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

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

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 5.4.0-1061.64

---
linux-aws (5.4.0-1061.64) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1061.64 -proposed tracker (LP: #1952285)

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] aws: Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Support builtin revoked certificates (LP: #1932029)
- [Config] aws: Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

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

  [ Ubuntu: 5.4.0-92.103 ]

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)
  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)
  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare
  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches
  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init
  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys
  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs
  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table
  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked versi

[Kernel-packages] [Bug 1950536] Re: keyboard not working on Medion notebook s17 series

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.226.00-0ubuntu0.21.10.2

---
nvidia-graphics-drivers-418-server (418.226.00-0ubuntu0.21.10.2) impish; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:53:51 +0100

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.106.00-0ubuntu0.21.04.2

---
nvidia-graphics-drivers-460-server (460.106.00-0ubuntu0.21.04.2) hirsute; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:29:04 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1949882] Re: linux-aws: Fix backport of RDMA/efa: Expose maximum TX doorbell batch

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.82.01-0ubuntu0.21.04.2

---
nvidia-graphics-drivers-470-server (470.82.01-0ubuntu0.21.04.2) hirsute; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
12:47:12 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1950462] Re: Focal linux-azure: Vm crash on Dv5/Ev5

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.82.01-0ubuntu0.21.10.2

---
nvidia-graphics-drivers-470-server (470.82.01-0ubuntu0.21.10.2) impish; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Mon, 15 Nov 2021
15:49:26 +0100

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Impish)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1950014] Re: Focal update: v5.4.153 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.106.00-0ubuntu0.21.10.2

---
nvidia-graphics-drivers-460-server (460.106.00-0ubuntu0.21.10.2) impish; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:27:47 +0100

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1950009] Re: Focal update: v5.4.152 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.82.01-0ubuntu0.20.04.2

---
nvidia-graphics-drivers-470-server (470.82.01-0ubuntu0.20.04.2) focal; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
12:54:23 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.156.00-0ubuntu0.21.10.2

---
nvidia-graphics-drivers-450-server (450.156.00-0ubuntu0.21.10.2) impish; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:41:38 +0100

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.106.00-0ubuntu0.20.04.2

---
nvidia-graphics-drivers-460-server (460.106.00-0ubuntu0.20.04.2) focal; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:30:19 +0100

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.226.00-0ubuntu0.21.04.2

---
nvidia-graphics-drivers-418-server (418.226.00-0ubuntu0.21.04.2) hirsute; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
16:00:27 +0100

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.106.00-0ubuntu0.21.04.2

---
nvidia-graphics-drivers-460-server (460.106.00-0ubuntu0.21.04.2) hirsute; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:29:04 +0100

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.226.00-0ubuntu0.20.04.2

---
nvidia-graphics-drivers-418-server (418.226.00-0ubuntu0.20.04.2) focal; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
16:04:58 +0100

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.82.01-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-470-server (470.82.01-0ubuntu0.18.04.2) bionic; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
12:55:23 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.156.00-0ubuntu0.20.04.2

---
nvidia-graphics-drivers-450-server (450.156.00-0ubuntu0.20.04.2) focal; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:43:36 +0100

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.106.00-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-460-server (460.106.00-0ubuntu0.18.04.2) bionic; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:31:23 +0100

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.156.00-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-450-server (450.156.00-0ubuntu0.18.04.2) bionic; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:44:28 +0100

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1945632] Re: Re-enable DEBUG_INFO_BTF where it was disabled

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1932029] Re: Support builtin revoked certificates

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.156.00-0ubuntu0.21.04.2

---
nvidia-graphics-drivers-450-server (450.156.00-0ubuntu0.21.04.2) hirsute; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
15:42:46 +0100

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-418-server -
418.226.00-0ubuntu0.18.04.2

---
nvidia-graphics-drivers-418-server (418.226.00-0ubuntu0.18.04.2) bionic; 
urgency=medium

  [ Jamie Nguyen ]
  * debian/templates/control.in:
- Move nvidia-prime and nvidia-settings to "Suggests"
  (LP: #1948960).

 -- Alberto Milone   Tue, 16 Nov 2021
16:06:58 +0100

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+subscriptions


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


[Kernel-packages] [Bug 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.4.0-92.103

---
linux (5.4.0-92.103) focal; urgency=medium

  * focal/linux: 5.4.0-92.103 -proposed tracker (LP: #1952316)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- tlb: mmu_gather: add tlb_flush_*_range APIs
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * Re-enable DEBUG_INFO_BTF where it was disabled (LP: #1945632)
- [Config] Enable CONFIG_DEBUG_INFO_BTF on all arches

  * Focal linux-azure: Vm crash on Dv5/Ev5 (LP: #1950462)
- KVM: VMX: eVMCS: make evmcs_sanitize_exec_ctrls() work again
- jump_label: Fix usage in module __init

  * Support builtin revoked certificates (LP: #1932029)
- Revert "UBUNTU: SAUCE: (lockdown) Make get_cert_list() not complain about
  cert lists that aren't present."
- integrity: Move import of MokListRT certs to a separate routine
- integrity: Load certs from the EFI MOK config table
- certs: Add ability to preload revocation certs
- integrity: Load mokx variables into the blacklist keyring
- certs: add 'x509_revocation_list' to gitignore
- SAUCE: Dump stack when X.509 certificates cannot be loaded
- [Packaging] build canonical-revoked-certs.pem from branch/arch certs
- [Packaging] Revoke 2012 UEFI signing certificate as built-in
- [Config] Configure CONFIG_SYSTEM_REVOCATION_KEYS with revoked keys

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679)
- efi: Support for MOK variable config table
- efi: mokvar-table: fix some issues in new code
- efi: mokvar: add missing include of asm/early_ioremap.h
- efi/mokvar: Reserve the table only if it is in boot services data
- SAUCE: integrity: add informational messages when revoking certs

  * Support importing mokx keys into revocation list from the mok table
(LP: #1928679) // CVE-2020-26541 when certificates are revoked via
MokListXRT.
- SAUCE: integrity: Load mokx certs from the EFI MOK config table

  * Focal update: v5.4.157 upstream stable release (LP: #1951883)
- ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
- ARM: 9134/1: remove duplicate memcpy() definition
- ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
- ARM: 9141/1: only warn about XIP address when not compile testing
- ipv6: use siphash in rt6_exception_hash()
- ipv4: use siphash instead of Jenkins in fnhe_hashfun()
- usbnet: sanity check for maxpacket
- usbnet: fix error return code in usbnet_probe()
- Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
- ata: sata_mv: Fix the error handling of mv_chip_id()
- nfc: port100: fix using -ERRNO as command type mask
- net/tls: Fix flipped sign in tls_err_abort() calls
- mmc: vub300: fix control-message timeouts
- mmc: cqhci: clear HALT state after CQE enable
- mmc: dw_mmc: exynos: fix the finding clock sample value
- mmc: sdhci: Map more voltage level to SDHCI_POWER_330
- mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning
  circuit
- cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
- net: lan78xx: fix division by zero in send path
- tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
- IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
- IB/hfi1: Fix abba locking issue with sc_disable()
- nvmet-tcp: fix data digest pointer calculation
- nvme-tcp: fix data digest pointer calculation
- RDMA/mlx5: Set user priority for DCT
- arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
- regmap: Fix possible double-free in regcache_rbtree_exit()
- net: batman-adv: fix error handling
- net: Prevent infinite while loop in skb_tx_hash()
- RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
- nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
- net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume
  fails
- net: ethernet: microchip: lan743x: Fix dma allocation failure by using
  dma_set_mask_and_coherent
- net: nxp: lpc_eth.c: avoid hang when bringing interface down
- net/tls: Fix flipped sign in async_wait.err assignment
- phy: phy_ethtool_ksettings_get: Lock the phy for consistency
- phy: phy_start_aneg: Add an unlocked version
- sctp: use init_tag from inithdr for ABORT chunk
- sctp: fix the processing for INIT_ACK chunk
- sctp: fix the processing for COOKIE_ECHO chunk
- sctp: add vtag check in sctp_sf_violation
- sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
- sctp: add vtag check in sctp_sf_ootb
- net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT
- cfg80211: correct bridge/4addr mode check
- KVM: s390: clear kicked_mask before 

[Kernel-packages] [Bug 1955016] Re: devices on thunderbolt dock are not recognized on adl-p platform

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1013.13

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

  * focal/linux-oem-5.14: 5.14.0-1013.13 -proposed tracker (LP:
#1955464)

  * devices on thunderbolt dock are not recognized on adl-p platform
(LP: #1955016)
- SAUCE: thunderbolt: Runtime PM activate both ends of the device link
- SAUCE: thunderbolt: Tear down existing tunnels when resuming from 
hibernate
- SAUCE: thunderbolt: Runtime resume USB4 port when retimers are scanned
- SAUCE: thunderbolt: Do not allow subtracting more NFC credits than
  configured
- SAUCE: thunderbolt: Do not program path HopIDs for USB4 routers
- SAUCE: thunderbolt: Add debug logging of DisplayPort resource allocation

 -- Chia-Lin Kao (AceLan)   Tue, 21 Dec 2021
16:59:25 +0800

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

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

Title:
  devices on thunderbolt dock are not recognized on adl-p 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:
  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]
  When booting up with the TBT dock is plugged, the devices(USB, Ethernet) on 
the dock can't be recognized. It requires to run lspci command to wake up the 
PCI devices to make the devices on the dock work.

  [Fix]
  The patchset fix this runtime pm issue.
  
https://patchwork.kernel.org/project/linux-usb/cover/20211125073733.74902-1-mika.westerb...@linux.intel.com/

  [Test]
  Verified on Dell ADL-P platform with TBT dock.

  [Where the problems could occur]
  Hard to evaluate, but after some cold boot/warm boot, plug/un-plug the 
devices on the dock, didn't observe any regressions.

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


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


[Kernel-packages] [Bug 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1013.13

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

  * focal/linux-oem-5.14: 5.14.0-1013.13 -proposed tracker (LP:
#1955464)

  * devices on thunderbolt dock are not recognized on adl-p platform
(LP: #1955016)
- SAUCE: thunderbolt: Runtime PM activate both ends of the device link
- SAUCE: thunderbolt: Tear down existing tunnels when resuming from 
hibernate
- SAUCE: thunderbolt: Runtime resume USB4 port when retimers are scanned
- SAUCE: thunderbolt: Do not allow subtracting more NFC credits than
  configured
- SAUCE: thunderbolt: Do not program path HopIDs for USB4 routers
- SAUCE: thunderbolt: Add debug logging of DisplayPort resource allocation

 -- Chia-Lin Kao (AceLan)   Tue, 21 Dec 2021
16:59:25 +0800

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

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

Title:
  AMD: Suspend not working when some cores are disabled through cpufreq

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

Bug description:
  [SRU Justification]

  [Impact]

  Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
  some cpu cores offline using cpufreq gadgets or via sysfs may hang the
  system.

  [Fix]

  In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
  dead in C3 state") fixes this issue.

  [Test Case]

  As stated in aforementioned bug url, setup cpufreq extention to take
  down a few cpu cores, and trigger system suspend. There are ~50% chances
  that networking/input/... would hang and the user can only reboot by
  sysrq keys.

  [Where problems could occur]

  According to the patch discussion thread in
  https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
  the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
  not have a practical meaning, but simply C2 was the deepest supported
  then.

  [Other Info]

  While this is currently only available in v5.16-rc1 and affects AMD
  Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.

  == original bug report ==

  https://gitlab.freedesktop.org/drm/amd/-/issues/1708

  Reproduce steps:
  1. Install cpufeq gnome extension 
(https://extensions.gnome.org/extension/1082/cpufreq/)
  2. Click on the cpu freq extention in the top bar
  3. Slide the "cores online" from 16 to 3
  4. close lid of laptop

  Expected result: the laptop goes into suspend
  Actual result: the laptop stay on but screen is now always black and keyboard 
input is ignored

  Fix committed to v5.16-rc1: 
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1188 F pulseaudio
   /dev/snd/controlC2:  ubuntu 1188 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1188 F pulseaudio
  CasperMD5CheckResult: skip
  Dependencies:

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-09-09 (97 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.

   enp1s0f0  no wireless extensions.
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AMD Celadon-CZN
  Package: linux-firmware 1.187.23+staging.38 [origin: 
LP-PPA-canonical-hwe-team-linux-firmware-staging]
  PackageArchitecture: all
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem 
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config 
no_console_suspend
  ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit cod

[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1013.13

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

  * focal/linux-oem-5.14: 5.14.0-1013.13 -proposed tracker (LP:
#1955464)

  * devices on thunderbolt dock are not recognized on adl-p platform
(LP: #1955016)
- SAUCE: thunderbolt: Runtime PM activate both ends of the device link
- SAUCE: thunderbolt: Tear down existing tunnels when resuming from 
hibernate
- SAUCE: thunderbolt: Runtime resume USB4 port when retimers are scanned
- SAUCE: thunderbolt: Do not allow subtracting more NFC credits than
  configured
- SAUCE: thunderbolt: Do not program path HopIDs for USB4 routers
- SAUCE: thunderbolt: Add debug logging of DisplayPort resource allocation

 -- Chia-Lin Kao (AceLan)   Tue, 21 Dec 2021
16:59:25 +0800

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

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

Title:
  [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus  show error 
"severity=Uncorrected (Non-Fatal)",
  and failed to probe.

  [Fix]
  Re-enable PCIe port LTR after reset or hotplug, and probe it properly.

  [Test]
  Verified on HW with TBT4 dock. it works fine.
  Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine.
  Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt.

  [Where problems could occur]
  PCI bus may break.

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


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


[Kernel-packages] [Bug 1951643] Re: Hirsute update: upstream stable patchset 2021-11-19

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.11.0-44.48

---
linux (5.11.0-44.48) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-44.48 -proposed tracker (LP: #1954388)

  * Add F81966 watchdog support (LP: #1949063)
- SAUCE: watchdog: f71808e_wdt: Add F81966 support

linux (5.11.0-42.46) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-42.46 -proposed tracker (LP: #1952278)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * CVE-2021-43267
- tipc: fix size validations for the MSG_CRYPTO type

  * Hirsute update: upstream stable patchset 2021-11-24 (LP: #1952136)
- ext4: check and update i_disksize properly
- ext4: correct the error path of ext4_write_inline_data_end()
- ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic
- HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
- netfilter: ip6_tables: zero-initialize fragment offset
- HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs
- ASoC: SOF: loader: release_firmware() on load failure to avoid batching
- netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic
- netfilter: nf_nat_masquerade: defer conntrack walk to work queue
- mac80211: Drop frames from invalid MAC address in ad-hoc mode
- m68k: Handle arrivals of multiple signals correctly
- hwmon: (ltc2947) Properly handle errors when looking for the external 
clock
- net: prevent user from passing illegal stab size
- mac80211: check return value of rhashtable_init
- vboxfs: fix broken legacy mount signature checking
- net: sun: SUNVNET_COMMON should depend on INET
- drm/amdgpu: fix gart.bo pin_count leak
- scsi: ses: Fix unsigned comparison with less than zero
- scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
- perf/core: fix userpage->time_enabled of inactive events
- sched: Always inline is_percpu_thread()
- hwmon: (pmbus/ibm-cffps) max_power_out swap changes
- ALSA: usb-audio: Unify mixer resume and reset_resume procedure
- pinctrl: qcom: sc7280: Add PM suspend callbacks
- io_uring: kill fasync
- ALSA: usb-audio: Add quirk for VF0770
- ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl
- ALSA: seq: Fix a potential UAF by wrong private_free call order
- ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop
- ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254
- ALSA: hda/realtek: Complete partial device name to avoid ambiguity
- ALSA: hda/realtek: Add quirk for Clevo X170KM-G
- ALSA: hda/realtek - ALC236 headset MIC recording issue
- ALSA: hda/realtek: Add quirk for TongFang PHxTxX1
- ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW
- nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for 
`^'
- s390: fix strrchr() implementation
- clk: socfpga: agilex: fix duplicate s2f_user0_clk
- csky: don't let sigreturn play with priveleged bits of status register
- csky: Fixup regs.sr broken in ptrace
- arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE
- drm/msm: Avoid potential overflow in timeout_to_jiffies()
- btrfs: unlock newly allocated extent buffer after error
- btrfs: deal with errors when replaying dir entry during log replay
- btrfs: deal with errors when adding inode reference during log replay
- btrfs: check for error when looking up inode during dir entry replay
- btrfs: update refs for any root except tree log roots
- btrfs: fix abort logic in btrfs_replace_file_extents
- x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails
- mei: me: add Ice Lake-N device id.
- USB: xhci: dbc: fix tty registration race
- xhci: guard accesses to ep_state in xhci_endpoint_reset()
- xhci: Fix command ring pointer corruption while aborting a command
- xhci: Enable trust tx length quirk for Fresco FL11 USB controller
- cb710: avoid NULL pointer subtraction
- efi/cper: use stack buffer for error record decoding
- efi: Change down_interruptible() in virt_efi_reset_system() to
  down_trylock()
- usb: musb: dsps: Fix the probe error path
- Input: xpad - add support for another USB ID of Nacon GC-100
- USB: serial: qcserial: add EM9191 QDL support
- USB: serial: option: add Quectel EC200S-CN module support
- USB: serial: option: add Telit LE910Cx composition 0x1204
- USB: serial: option: add prod. id for Quectel EG91
- misc: fastrpc: Add missing lock before accessing find_vma()
- EDAC/armada-xp: Fix output of uncorrectable error counter
- nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells
- x86/Kconfig: Do not enable AMD_MEM_ENCR

[Kernel-packages] [Bug 1952136] Re: Hirsute update: upstream stable patchset 2021-11-24

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.11.0-44.48

---
linux (5.11.0-44.48) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-44.48 -proposed tracker (LP: #1954388)

  * Add F81966 watchdog support (LP: #1949063)
- SAUCE: watchdog: f71808e_wdt: Add F81966 support

linux (5.11.0-42.46) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-42.46 -proposed tracker (LP: #1952278)

  * Packaging resync (LP: #1786013)
- [Packaging] resync update-dkms-versions helper
- debian/dkms-versions -- update from kernel-versions (main/2021.11.29)

  * CVE-2021-4002
- hugetlbfs: flush TLBs correctly after huge_pmd_unshare

  * CVE-2021-43267
- tipc: fix size validations for the MSG_CRYPTO type

  * Hirsute update: upstream stable patchset 2021-11-24 (LP: #1952136)
- ext4: check and update i_disksize properly
- ext4: correct the error path of ext4_write_inline_data_end()
- ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic
- HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
- netfilter: ip6_tables: zero-initialize fragment offset
- HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs
- ASoC: SOF: loader: release_firmware() on load failure to avoid batching
- netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic
- netfilter: nf_nat_masquerade: defer conntrack walk to work queue
- mac80211: Drop frames from invalid MAC address in ad-hoc mode
- m68k: Handle arrivals of multiple signals correctly
- hwmon: (ltc2947) Properly handle errors when looking for the external 
clock
- net: prevent user from passing illegal stab size
- mac80211: check return value of rhashtable_init
- vboxfs: fix broken legacy mount signature checking
- net: sun: SUNVNET_COMMON should depend on INET
- drm/amdgpu: fix gart.bo pin_count leak
- scsi: ses: Fix unsigned comparison with less than zero
- scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
- perf/core: fix userpage->time_enabled of inactive events
- sched: Always inline is_percpu_thread()
- hwmon: (pmbus/ibm-cffps) max_power_out swap changes
- ALSA: usb-audio: Unify mixer resume and reset_resume procedure
- pinctrl: qcom: sc7280: Add PM suspend callbacks
- io_uring: kill fasync
- ALSA: usb-audio: Add quirk for VF0770
- ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl
- ALSA: seq: Fix a potential UAF by wrong private_free call order
- ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop
- ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254
- ALSA: hda/realtek: Complete partial device name to avoid ambiguity
- ALSA: hda/realtek: Add quirk for Clevo X170KM-G
- ALSA: hda/realtek - ALC236 headset MIC recording issue
- ALSA: hda/realtek: Add quirk for TongFang PHxTxX1
- ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW
- nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for 
`^'
- s390: fix strrchr() implementation
- clk: socfpga: agilex: fix duplicate s2f_user0_clk
- csky: don't let sigreturn play with priveleged bits of status register
- csky: Fixup regs.sr broken in ptrace
- arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE
- drm/msm: Avoid potential overflow in timeout_to_jiffies()
- btrfs: unlock newly allocated extent buffer after error
- btrfs: deal with errors when replaying dir entry during log replay
- btrfs: deal with errors when adding inode reference during log replay
- btrfs: check for error when looking up inode during dir entry replay
- btrfs: update refs for any root except tree log roots
- btrfs: fix abort logic in btrfs_replace_file_extents
- x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails
- mei: me: add Ice Lake-N device id.
- USB: xhci: dbc: fix tty registration race
- xhci: guard accesses to ep_state in xhci_endpoint_reset()
- xhci: Fix command ring pointer corruption while aborting a command
- xhci: Enable trust tx length quirk for Fresco FL11 USB controller
- cb710: avoid NULL pointer subtraction
- efi/cper: use stack buffer for error record decoding
- efi: Change down_interruptible() in virt_efi_reset_system() to
  down_trylock()
- usb: musb: dsps: Fix the probe error path
- Input: xpad - add support for another USB ID of Nacon GC-100
- USB: serial: qcserial: add EM9191 QDL support
- USB: serial: option: add Quectel EC200S-CN module support
- USB: serial: option: add Telit LE910Cx composition 0x1204
- USB: serial: option: add prod. id for Quectel EG91
- misc: fastrpc: Add missing lock before accessing find_vma()
- EDAC/armada-xp: Fix output of uncorrectable error counter
- nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells
- x86/Kconfig: Do not enable AMD_MEM_ENCR

[Kernel-packages] [Bug 1954773] Re: New fix for jack detection after resume on CS8409 sound driver

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1013.13

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

  * focal/linux-oem-5.14: 5.14.0-1013.13 -proposed tracker (LP:
#1955464)

  * devices on thunderbolt dock are not recognized on adl-p platform
(LP: #1955016)
- SAUCE: thunderbolt: Runtime PM activate both ends of the device link
- SAUCE: thunderbolt: Tear down existing tunnels when resuming from 
hibernate
- SAUCE: thunderbolt: Runtime resume USB4 port when retimers are scanned
- SAUCE: thunderbolt: Do not allow subtracting more NFC credits than
  configured
- SAUCE: thunderbolt: Do not program path HopIDs for USB4 routers
- SAUCE: thunderbolt: Add debug logging of DisplayPort resource allocation

 -- Chia-Lin Kao (AceLan)   Tue, 21 Dec 2021
16:59:25 +0800

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

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

Title:
  New fix for jack detection after resume on CS8409 sound driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Fix Committed
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  On some platforms with Cirrus CS8409 audio codec, the external headset will 
fail to be detected after system resume.

  [Fix]
  Cirrus released a new fix commit 65cc4ad62a9e ('ALSA: hda/cs8409: Set PMSG_ON 
earlier inside cs8409 driver'). It sets the power_state to ON before the 
unsolicited event arrives to make sure the jack detection can be invoked after 
resume.

  [Test]
  Plug-in an external headset in front headset port, suspend/resume the system 
then check whether the headset function works as expected.

  [Where problem could occur]
  Low. It only affect the platforms with Cirrus codec CS8409 which used to have 
problem.

  == Original Bug Description ==

  [Summary] System can't detect external headset after suspend

  [Steps to reproduce]
  1. install manifest and boot into OS
  2. plug-in an external headset in front headset port
  3. un-plug external headset
  4. suspend system
  5. resume system from suspend
  6. plug-in an external headset

  [Expected result]
  System could detect external headset after suspend

  [Actual result]
  System can't detect external headset after suspend

  [Failure rate]
  3/3

  [Additional information]
  CID: 202110-29567
  SKU: DLPV-SFF-DVT-C1
  Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 3710
  bios-version: 0.13.73
  CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
  GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4680] (rev 0c)
  kernel-version: 5.13.0-1019-oem

  [Stage]
  Issue reported and logs collected right after it happened

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


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


[Kernel-packages] [Bug 1954369] Re: Fix runtime power management on USB controller with XHCI_RESET_ON_RESUME flag

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1013.13

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

  * focal/linux-oem-5.14: 5.14.0-1013.13 -proposed tracker (LP:
#1955464)

  * devices on thunderbolt dock are not recognized on adl-p platform
(LP: #1955016)
- SAUCE: thunderbolt: Runtime PM activate both ends of the device link
- SAUCE: thunderbolt: Tear down existing tunnels when resuming from 
hibernate
- SAUCE: thunderbolt: Runtime resume USB4 port when retimers are scanned
- SAUCE: thunderbolt: Do not allow subtracting more NFC credits than
  configured
- SAUCE: thunderbolt: Do not program path HopIDs for USB4 routers
- SAUCE: thunderbolt: Add debug logging of DisplayPort resource allocation

 -- Chia-Lin Kao (AceLan)   Tue, 21 Dec 2021
16:59:25 +0800

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

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

Title:
  Fix runtime power management on USB controller with
  XHCI_RESET_ON_RESUME flag

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

Bug description:
  [Impact]
  xHCI driver's runtime resume routine tries to reset USB controller with
  XHCI_RESET_ON_RESUME flag. That causes USB devices connect to the xHCI
  fail to work.

  [Fix]
  Disable runtime power management regardless of
  CONFIG_USB_DEFAULT_PERSIST option.

  [Test]
  USB devices which connect to the xHCI controller can work normally.

  [Where problems could occur] 
  USB_DEFAULT_PERSIST is a config for system-wide PM to speed up resume
  time, so it shouldn't be applied to runtime PM at first place.

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


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


[Kernel-packages] [Bug 1950540] Re: alsa/sof: All audio jacks can't detect hotplug when only codec is suspended

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1013.13

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

  * focal/linux-oem-5.14: 5.14.0-1013.13 -proposed tracker (LP:
#1955464)

  * devices on thunderbolt dock are not recognized on adl-p platform
(LP: #1955016)
- SAUCE: thunderbolt: Runtime PM activate both ends of the device link
- SAUCE: thunderbolt: Tear down existing tunnels when resuming from 
hibernate
- SAUCE: thunderbolt: Runtime resume USB4 port when retimers are scanned
- SAUCE: thunderbolt: Do not allow subtracting more NFC credits than
  configured
- SAUCE: thunderbolt: Do not program path HopIDs for USB4 routers
- SAUCE: thunderbolt: Add debug logging of DisplayPort resource allocation

 -- Chia-Lin Kao (AceLan)   Tue, 21 Dec 2021
16:59:25 +0800

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

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

Title:
  alsa/sof: All audio jacks can't detect hotplug when only codec is
  suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
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-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  If the codec is in rt_suspend while the controller is in rt_resume,
  all audio jacks can't detect hotplug.

  [Fix]
  Backport a upstream patch, this will enable WAKEEN in the period
  between codec suspend and controller suspend.

  [Test]
  Booting the patched kernel, add snd_sof_pci.sof_pci_debug=0x1 in
  the bootargs, plug the headset to the audio jacks, the system
  could detect the plug in or plug out.

  [Where problems could occur]
  The patch enable the WAKEEN after codec is in rt_suspend, this
  could affect the audio jack hotplug detection, if it introduces
  regression, it will be on the audio jack detection, but this
  possibility is very low, we already verified this patch on
  many machines.

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


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


[Kernel-packages] [Bug 1954555] Re: Focal update: 5.10.81 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1053.55

---
linux-oem-5.10 (5.10.0-1053.55) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1053.55 -proposed tracker (LP:
#1952317)

  * Focal update: 5.10.83 upstream stable release (LP: #1954557)
- bpf: Fix toctou on read-only map's constant scalar tracking
- 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: Update comment about disabling link training
- 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: fix system hang caused by eee_ctrl_timer during 
suspend/resume
- 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
- scsi: core: sysfs: Fix setting device state to SDEV_RUNNING
- scsi: scsi_debug: Zero clear zones at reset write pointer
- erofs: fix deadlock when shrink erofs slab
- net/smc: Ensure the active closing peer first closes clcsock
- mlxsw: Verify the accessed index doesn't exceed the array length
- mlxsw: spectrum: Protect driver from buggy firmware
- net: marvell: mvpp2: increa

[Kernel-packages] [Bug 1954557] Re: Focal update: 5.10.83 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1053.55

---
linux-oem-5.10 (5.10.0-1053.55) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1053.55 -proposed tracker (LP:
#1952317)

  * Focal update: 5.10.83 upstream stable release (LP: #1954557)
- bpf: Fix toctou on read-only map's constant scalar tracking
- 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: Update comment about disabling link training
- 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: fix system hang caused by eee_ctrl_timer during 
suspend/resume
- 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
- scsi: core: sysfs: Fix setting device state to SDEV_RUNNING
- scsi: scsi_debug: Zero clear zones at reset write pointer
- erofs: fix deadlock when shrink erofs slab
- net/smc: Ensure the active closing peer first closes clcsock
- mlxsw: Verify the accessed index doesn't exceed the array length
- mlxsw: spectrum: Protect driver from buggy firmware
- net: marvell: mvpp2: increa

[Kernel-packages] [Bug 1954556] Re: Focal update: 5.10.82 upstream stable release

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1053.55

---
linux-oem-5.10 (5.10.0-1053.55) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1053.55 -proposed tracker (LP:
#1952317)

  * Focal update: 5.10.83 upstream stable release (LP: #1954557)
- bpf: Fix toctou on read-only map's constant scalar tracking
- 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: Update comment about disabling link training
- 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: fix system hang caused by eee_ctrl_timer during 
suspend/resume
- 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
- scsi: core: sysfs: Fix setting device state to SDEV_RUNNING
- scsi: scsi_debug: Zero clear zones at reset write pointer
- erofs: fix deadlock when shrink erofs slab
- net/smc: Ensure the active closing peer first closes clcsock
- mlxsw: Verify the accessed index doesn't exceed the array length
- mlxsw: spectrum: Protect driver from buggy firmware
- net: marvell: mvpp2: increa

[Kernel-packages] [Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel

2022-01-04 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1013.13

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

  * focal/linux-oem-5.14: 5.14.0-1013.13 -proposed tracker (LP:
#1955464)

  * devices on thunderbolt dock are not recognized on adl-p platform
(LP: #1955016)
- SAUCE: thunderbolt: Runtime PM activate both ends of the device link
- SAUCE: thunderbolt: Tear down existing tunnels when resuming from 
hibernate
- SAUCE: thunderbolt: Runtime resume USB4 port when retimers are scanned
- SAUCE: thunderbolt: Do not allow subtracting more NFC credits than
  configured
- SAUCE: thunderbolt: Do not program path HopIDs for USB4 routers
- SAUCE: thunderbolt: Add debug logging of DisplayPort resource allocation

 -- Chia-Lin Kao (AceLan)   Tue, 21 Dec 2021
16:59:25 +0800

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

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

Title:
  Fix  No Screen after login to Desktop on sku with 3840x2400 panel

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
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:
  New

Bug description:
  [Impact]
  Got kernel report CPU pipe A FIFO underrun: soft,transcoder
  kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: 
soft,transcoder,

  [Fix]
  Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: 
Disable underrun recovery).
  Defeature the underrun feature for intel display gen13+.

  [Test Case]
  1. change resolution to 3840x2400
  2. monitor works well and doesn't black out.

  [Where problems could occur]
  low

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


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


  1   2   3   >