[Kernel-packages] [Bug 1964082] Re: MAAS deployment to raspberry pi fails for release 21.10

[Juerg Haefliger]

So you're booting the generic kernel/initrd and the generic arm64 image
on Pis? This is in no way supported and quite frankly I'm surprised that
it even works.

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

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

Title:
  MAAS deployment to raspberry pi fails for release 21.10

Status in MAAS:
  New
Status in linux-raspi package in Ubuntu:
  Invalid

Bug description:
  I have helped develop a reliable procedure for using MAAS to deploy
  ubuntu 20.04 to a Raspberry Pi cluster. Details are here:
  https://discourse.maas.io/t/build-your-own-bare-metal-cloud-using-a-
  raspberry-pi-cluster-with-maas/5845

  However, using the same procedure on the same hardware but selecting
  ubuntu 21.10 always fails. This appears to be caused by curtin being
  unable to see the USB disk device /dev/sda to which we are deploying.

  The same issue occurs with all versions of the kernel available for
  21.10.

  I enclose the log files downloaded from MAAS.

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


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

[Kernel-packages] [Bug 1963914] Re: Require force_probe for i915 driver probing

[You-Sheng Yang]

dfb924e33927 drm/i915/adlp: Remove require_force_probe protection
f5392e5f8ef3 drm/i915/adl_s: Remove require_force_probe protection
have been committed jammy in bug 1960298.

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

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

Title:
  Require force_probe for i915 driver probing

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The kernel require force_probe to support ADL-P graphic.

  Reproduce step:
  1. Boot into Ubuntu Jammy
  2. $ lsmod | grep i915, the used number is 0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1183 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 21:50:41 2022
  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-psyduck+X192
  InstallationDate: Installed on 2022-03-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 5530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=b3c94cea-c8f7-4579-b41d-6360718d00f0 ro i915.force_probe=4626 quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220302.gitee0667aa-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 1.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd02/25/2022:br1.0:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5530
  dmi.product.sku: 0B06
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works).

  Steps to reproduce:

  1. Boot Ubuntu.
  2. Press Ctrl+Alt+F4.

  Expected: VT to be displayed
  Observed: Monitor turns off.

  Notes:
   * This failure only happens in 5.15.0-22-generic. Kernel version 
5.15.0-18-generic works fine.
   * I am currently using the nvidia-470 driver in case that's relevant.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Wed Mar  9 14:33:12 2022
  InstallationDate: Installed on 2021-11-05 (123 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  MachineType: Intel(R) Client Systems NUC9i7QNX
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220302.gitee0667aa-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QXCFL579.0034.2019.1125.1436
  dmi.board.name: NUC9i7QNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K49245-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 24.33
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX:
  dmi.product.family: QN
  dmi.product.name: NUC9i7QNX
  dmi.product.sku: BXNUC9i7QNX
  dmi.product.version: K49244-403
  dmi.sys.vendor: Intel(R) Client Systems

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


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

[Kernel-packages] [Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

[Po-Hsu Lin]

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

** Tags added: 5.13 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/1927076

Title:
  IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash
  P8 node entei (Oops: Exception in kernel mode, sig: 4 [#1])

Status in ubuntu-kernel-tests:
  New
Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  New

Bug description:
  It looks like our P8 node "entei" tend to fail with the IPv6 TCP test
  from reuseport_bpf_cpu in ubuntu_kernel_selftests/net on 5.8 kernels:

   # send cpu 119, receive socket 119
   # send cpu 121, receive socket 121
   # send cpu 123, receive socket 123
   # send cpu 125, receive socket 125
   # send cpu 127, receive socket 127
   #  IPv6 TCP 
  publish-job-status: using request.json

  It failed silently here, this can be 100% reproduced with Groovy 5.8
  and Focal 5.8.

  This will cause the ubuntu_kernel_selftests being interrupted, the
  test result for other tests cannot be processed to our result page.

  Please find attachment for the complete "net" test result on this node
  with Groovy 5.8.0-52.59

  Add the kqa-blocker tag as this might needs to be manually verified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions


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

[Kernel-packages] [Bug 1945927] Re: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310

[Pierre Equoy]

Cheese has a known issue working with some formats (see lp:1882896),
which was fixed, but the fix has not been backported to Ubuntu 20.04.

Could you also check the resolution found by the
https://webcamtests.com/ website?

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

Title:
  Terrible resolution on integrated webcam on Dell XPS 13 Developer
  Edition 9310

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

Bug description:
  This seems to be a known issue, but I couldn't find any launchpad bug
  corresponding to it. Apologies if I missed it, or if there is a better
  place for reporting a bug like this.

  When I try to use the webcam on my newly purchased Dell XPS-13-9310
  Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2
  LTS (fossa-bulbasaur X55), as it came out of the box, I only get a
  very pixelated low quality 640x480 resolution instead of the
  hardware's 1280×720 capability as advertised here:

  https://www.dell.com/en-us/work/shop/dell-laptops-and-
  notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop

  From what I gather, no linux driver exist that can use the full
  resolution of this webcam.

  I hope that it is somehow possible to get a proper driver from Dell /
  Realtek. If not, I hope that Realtek can provide documentation for the
  interface so that a proper driver can be written. I'm tempted to try
  to make that my first contribution of a driver, but in all likelihood
  I won't have the time or motivation to learn all that's needed and
  actually write it.

  Until a driver is available, I would appreciate if Dell would clarify
  on their website that their 9310 Developer Edition can only use the
  full advertised resolution in Windows. (I would not have bought this
  laptop if I had known about this limitation, as I frequently use
  Google Meet / Zoom and the current quality is not acceptable to me).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47
  ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
  Uname: Linux 5.10.0-1045-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  3 15:40:31 2021
  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
  InstallationDate: Installed on 2021-09-22 (11 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1964305] [NEW] Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)

[Daniel van Vugt]

Public bug reported:

Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works).

Steps to reproduce:

1. Boot Ubuntu.
2. Press Ctrl+Alt+F4.

Expected: VT to be displayed
Observed: Monitor turns off.

Notes:
 * This failure only happens in 5.15.0-22-generic. Kernel version 
5.15.0-18-generic works fine.
 * I am currently using the nvidia-470 driver in case that's relevant.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-22-generic 5.15.0-22.22
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Wed Mar  9 14:33:12 2022
InstallationDate: Installed on 2021-11-05 (123 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
MachineType: Intel(R) Client Systems NUC9i7QNX
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-22-generic N/A
 linux-backports-modules-5.15.0-22-generic  N/A
 linux-firmware 20220302.gitee0667aa-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2019
dmi.bios.release: 5.13
dmi.bios.vendor: Intel Corp.
dmi.bios.version: QXCFL579.0034.2019.1125.1436
dmi.board.name: NUC9i7QNB
dmi.board.vendor: Intel Corporation
dmi.board.version: K49245-402
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 24.33
dmi.modalias: 
dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX:
dmi.product.family: QN
dmi.product.name: NUC9i7QNX
dmi.product.sku: BXNUC9i7QNX
dmi.product.version: K49244-403
dmi.sys.vendor: Intel(R) Client Systems

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

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug jammy regression regression-release rls-jj-incoming

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works)

Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  Missing VTs in kernel 5.15.0-22-generic (but 5.15.0-18-generic works).

  Steps to reproduce:

  1. Boot Ubuntu.
  2. Press Ctrl+Alt+F4.

  Expected: VT to be displayed
  Observed: Monitor turns off.

  Notes:
   * This failure only happens in 5.15.0-22-generic. Kernel version 
5.15.0-18-generic works fine.
   * I am currently using the nvidia-470 driver in case that's relevant.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-22-generic 5.15.0-22.22
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Wed Mar  9 14:33:12 2022
  InstallationDate: Installed on 2021-11-05 (123 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
  MachineType: Intel(R) Client Systems NUC9i7QNX
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash 
nvidia-drm.modeset=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-22-generic N/A
   linux-backports-modules-5.15.0-22-generic  N/A
   linux-firmware 20220302.gitee0667aa-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QXCFL579.0034.2019.1125.1436
  dmi.board.name: NUC9i7QNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K49245-402
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  

[Kernel-packages] [Bug 1956496] Re: lost usb devices

[Balint Szigeti]

what kind of information, logs do you need regarding this issue?

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

Title:
  lost usb devices

Status in linux package in Ubuntu:
  Expired

Bug description:
  when I join/start a Google Meets *Video* I got this in dmesg:

  [15092.966530] uvcvideo: Failed to set UVC commit control : -71 (exp. 26).
  [15093.126396] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126474] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126544] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126624] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126703] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126783] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126864] uvcvideo: Failed to set UVC probe control : -71 (exp. 26).
  [15093.156223] usb 1-2.3.4: USB disconnect, device number 9
  [15093.940114] usb 1-2.3.4: new high-speed USB device number 15 using xhci_hcd
  [15094.088563] usb 1-2.3.4: New USB device found, idVendor=1f82, 
idProduct=0001, bcdDevice= 0.00
  [15094.088576] usb 1-2.3.4: New USB device strings: Mfr=0, Product=0, 
SerialNumber=3
  [15094.088582] usb 1-2.3.4: SerialNumber: HDA1AP23D00782
  [15099.132109] usb 1-2.3.4: 1:1: cannot set freq 48000 to ep 0x86
  [15101.164885] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.165798] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.166675] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.167592] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.168455] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.169350] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.170198] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.171027] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  .
  and so on
  .
  [15101.347016] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.347896] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.348092] usb 1-2.3.4: USB disconnect, device number 15
  [15101.348677] usb 1-2.3.4: 1:0: usb_set_interface failed (-19)
  [15102.644067] usb 1-2.3.4: new high-speed USB device number 16 using xhci_hcd
  [15102.793621] usb 1-2.3.4: New USB device found, idVendor=1f82, 
idProduct=0001, bcdDevice= 2.16
  [15102.793627] usb 1-2.3.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15102.793629] usb 1-2.3.4: Product: TANDBERG HD
  [15102.793631] usb 1-2.3.4: Manufacturer: TANDBERG
  [15102.793632] usb 1-2.3.4: SerialNumber: AA1AP23D00782
  [15102.796425] uvcvideo: Found UVC 1.00 device TANDBERG HD (1f82:0001)
  [15102.798164] input: TANDBERG HD: TANDBERG Video as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0/input/input26
  [15109.244101] filter_write: 191 callbacks suppressed

  after that usb ports doens't work at all!

  I think the webcam and kernel doesn't like each other but that webcam works 
correctly with RingCentral or Zoom.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  balint 2464 F pulseaudio
   /dev/snd/controlC2:  balint 2464 F pulseaudio
   /dev/snd/controlC1:  balint 2464 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-21 (534 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20U1000XHV
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-44-generic 
root=UUID=2ea68483-fb39-44f6-86a8-b27735f237e6 ro ipv6.disable=1 quiet splash 
pci=nommconf ipv6.disable=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-44-generic N/A
   linux-backports-modules-5.11.0-44-generic  N/A
   linux-firmware 1.187.24
  Tags:  focal
  Uname: Linux 5.11.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 08/05/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R17ET21W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U1000XHV
  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.4
  dmi.modalias: 

[Kernel-packages] [Bug 1956496] Re: lost usb devices

[Balint Szigeti]

do you need kernel dump?

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

Title:
  lost usb devices

Status in linux package in Ubuntu:
  Expired

Bug description:
  when I join/start a Google Meets *Video* I got this in dmesg:

  [15092.966530] uvcvideo: Failed to set UVC commit control : -71 (exp. 26).
  [15093.126396] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126474] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126544] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126624] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126703] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126783] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126864] uvcvideo: Failed to set UVC probe control : -71 (exp. 26).
  [15093.156223] usb 1-2.3.4: USB disconnect, device number 9
  [15093.940114] usb 1-2.3.4: new high-speed USB device number 15 using xhci_hcd
  [15094.088563] usb 1-2.3.4: New USB device found, idVendor=1f82, 
idProduct=0001, bcdDevice= 0.00
  [15094.088576] usb 1-2.3.4: New USB device strings: Mfr=0, Product=0, 
SerialNumber=3
  [15094.088582] usb 1-2.3.4: SerialNumber: HDA1AP23D00782
  [15099.132109] usb 1-2.3.4: 1:1: cannot set freq 48000 to ep 0x86
  [15101.164885] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.165798] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.166675] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.167592] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.168455] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.169350] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.170198] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.171027] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  .
  and so on
  .
  [15101.347016] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.347896] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.348092] usb 1-2.3.4: USB disconnect, device number 15
  [15101.348677] usb 1-2.3.4: 1:0: usb_set_interface failed (-19)
  [15102.644067] usb 1-2.3.4: new high-speed USB device number 16 using xhci_hcd
  [15102.793621] usb 1-2.3.4: New USB device found, idVendor=1f82, 
idProduct=0001, bcdDevice= 2.16
  [15102.793627] usb 1-2.3.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15102.793629] usb 1-2.3.4: Product: TANDBERG HD
  [15102.793631] usb 1-2.3.4: Manufacturer: TANDBERG
  [15102.793632] usb 1-2.3.4: SerialNumber: AA1AP23D00782
  [15102.796425] uvcvideo: Found UVC 1.00 device TANDBERG HD (1f82:0001)
  [15102.798164] input: TANDBERG HD: TANDBERG Video as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0/input/input26
  [15109.244101] filter_write: 191 callbacks suppressed

  after that usb ports doens't work at all!

  I think the webcam and kernel doesn't like each other but that webcam works 
correctly with RingCentral or Zoom.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  balint 2464 F pulseaudio
   /dev/snd/controlC2:  balint 2464 F pulseaudio
   /dev/snd/controlC1:  balint 2464 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-21 (534 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20U1000XHV
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-44-generic 
root=UUID=2ea68483-fb39-44f6-86a8-b27735f237e6 ro ipv6.disable=1 quiet splash 
pci=nommconf ipv6.disable=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-44-generic N/A
   linux-backports-modules-5.11.0-44-generic  N/A
   linux-firmware 1.187.24
  Tags:  focal
  Uname: Linux 5.11.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 08/05/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R17ET21W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U1000XHV
  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.4
  dmi.modalias: 

[Kernel-packages] [Bug 1963914] Re: Require force_probe for i915 driver probing

[You-Sheng Yang]

This is a follow-up for bug 1940504 for Jammy 5.15+ kernels. oem-5.14 is
to be upgraded to hwe-5.15, so we'll need this for oem-enabled ADL-P
devices.

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

Title:
  Require force_probe for i915 driver probing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel require force_probe to support ADL-P graphic.

  Reproduce step:
  1. Boot into Ubuntu Jammy
  2. $ lsmod | grep i915, the used number is 0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1183 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 21:50:41 2022
  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-psyduck+X192
  InstallationDate: Installed on 2022-03-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 5530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=b3c94cea-c8f7-4579-b41d-6360718d00f0 ro i915.force_probe=4626 quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220302.gitee0667aa-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 1.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd02/25/2022:br1.0:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5530
  dmi.product.sku: 0B06
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1964286] Re: iwlwifi microcode crash after updating to 5.14.0-1027-oem

[Kai-Chuan Hsieh]

Upload sos report.

** Attachment added: "sosreport-MDAT-DVT2-D8-1964286-2022-03-09-xzjjvpz.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1964286/+attachment/5567233/+files/sosreport-MDAT-DVT2-D8-1964286-2022-03-09-xzjjvpz.tar.xz

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

Title:
  iwlwifi microcode crash after updating to 5.14.0-1027-oem

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

Bug description:
  Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot 
sector to mark fs as dirty
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error 
Log Dump:
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 
0x004B, valid: 6
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware 
version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | 
ADVANCED_SYSASSERT  
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | 
trm_hw_status0
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | 
trm_hw_status1
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | 
branchlink2
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink1
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink2
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  9 11:13:53 2022
  InstallationDate: Installed on 2021-10-19 (140 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1964286] Re: iwlwifi microcode crash after updating to 5.14.0-1027-oem

[AceLan Kao]

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

** No longer affects: linux-signed-oem-5.14 (Ubuntu)

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

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

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

Title:
  iwlwifi microcode crash after updating to 5.14.0-1027-oem

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

Bug description:
  Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot 
sector to mark fs as dirty
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error 
Log Dump:
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 
0x004B, valid: 6
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware 
version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | 
ADVANCED_SYSASSERT  
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | 
trm_hw_status0
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | 
trm_hw_status1
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | 
branchlink2
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink1
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink2
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  9 11:13:53 2022
  InstallationDate: Installed on 2021-10-19 (140 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1945927] Re: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310

[Pierre Equoy]

Hello!

Sorry for the very late reply...

First of all, there have been a few Linux kernel updates in Ubuntu 20.04
since you opened this issue. Please upgrade your system and check if you
have the latest available version of the kernel installed; in a
terminal, you can run these commands:

sudo apt update
sudo apt upgrade
uname -r

You should get something like "5.13.0-30-generic".

If the problem still persists, install the Video4Linux utility package
and check what formats and resolutions are available for the webcam;
again, in a terminal:

sudo apt install v4l-utils
v4l2-ctl -D --list-formats-ext

You should get something like:

=
Driver Info:
Driver name  : uvcvideo
Card type: Video Capture 5
Bus info : usb-:00:14.0-3
Driver version   : 5.13.19
Capabilities : 0x84a1
(...)
[1]: 'MJPG' (Motion-JPEG, compressed)
Size: Discrete 640x480
(...)
=

Please attach the output of the v4l2-ctl command to this issue so we can
investigate.

Thanks!

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

Title:
  Terrible resolution on integrated webcam on Dell XPS 13 Developer
  Edition 9310

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

Bug description:
  This seems to be a known issue, but I couldn't find any launchpad bug
  corresponding to it. Apologies if I missed it, or if there is a better
  place for reporting a bug like this.

  When I try to use the webcam on my newly purchased Dell XPS-13-9310
  Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2
  LTS (fossa-bulbasaur X55), as it came out of the box, I only get a
  very pixelated low quality 640x480 resolution instead of the
  hardware's 1280×720 capability as advertised here:

  https://www.dell.com/en-us/work/shop/dell-laptops-and-
  notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop

  From what I gather, no linux driver exist that can use the full
  resolution of this webcam.

  I hope that it is somehow possible to get a proper driver from Dell /
  Realtek. If not, I hope that Realtek can provide documentation for the
  interface so that a proper driver can be written. I'm tempted to try
  to make that my first contribution of a driver, but in all likelihood
  I won't have the time or motivation to learn all that's needed and
  actually write it.

  Until a driver is available, I would appreciate if Dell would clarify
  on their website that their 9310 Developer Edition can only use the
  full advertised resolution in Windows. (I would not have bought this
  laptop if I had known about this limitation, as I frequently use
  Google Meet / Zoom and the current quality is not acceptable to me).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47
  ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
  Uname: Linux 5.10.0-1045-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  3 15:40:31 2021
  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
  InstallationDate: Installed on 2021-09-22 (11 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1956496] Re: lost usb devices

[Launchpad Bug Tracker]

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

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

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

Title:
  lost usb devices

Status in linux package in Ubuntu:
  Expired

Bug description:
  when I join/start a Google Meets *Video* I got this in dmesg:

  [15092.966530] uvcvideo: Failed to set UVC commit control : -71 (exp. 26).
  [15093.126396] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126474] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126544] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126624] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126703] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126783] uvcvideo: Failed to query (GET_CUR) UVC control 11 on unit 5: 
-71 (exp. 1).
  [15093.126864] uvcvideo: Failed to set UVC probe control : -71 (exp. 26).
  [15093.156223] usb 1-2.3.4: USB disconnect, device number 9
  [15093.940114] usb 1-2.3.4: new high-speed USB device number 15 using xhci_hcd
  [15094.088563] usb 1-2.3.4: New USB device found, idVendor=1f82, 
idProduct=0001, bcdDevice= 0.00
  [15094.088576] usb 1-2.3.4: New USB device strings: Mfr=0, Product=0, 
SerialNumber=3
  [15094.088582] usb 1-2.3.4: SerialNumber: HDA1AP23D00782
  [15099.132109] usb 1-2.3.4: 1:1: cannot set freq 48000 to ep 0x86
  [15101.164885] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.165798] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.166675] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.167592] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.168455] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.169350] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.170198] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.171027] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  .
  and so on
  .
  [15101.347016] usb 1-2.3.4: 1:0: usb_set_interface failed (-71)
  [15101.347896] usb 1-2.3.4: 1:1: usb_set_interface failed (-71)
  [15101.348092] usb 1-2.3.4: USB disconnect, device number 15
  [15101.348677] usb 1-2.3.4: 1:0: usb_set_interface failed (-19)
  [15102.644067] usb 1-2.3.4: new high-speed USB device number 16 using xhci_hcd
  [15102.793621] usb 1-2.3.4: New USB device found, idVendor=1f82, 
idProduct=0001, bcdDevice= 2.16
  [15102.793627] usb 1-2.3.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [15102.793629] usb 1-2.3.4: Product: TANDBERG HD
  [15102.793631] usb 1-2.3.4: Manufacturer: TANDBERG
  [15102.793632] usb 1-2.3.4: SerialNumber: AA1AP23D00782
  [15102.796425] uvcvideo: Found UVC 1.00 device TANDBERG HD (1f82:0001)
  [15102.798164] input: TANDBERG HD: TANDBERG Video as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2.3/1-2.3.4/1-2.3.4:1.0/input/input26
  [15109.244101] filter_write: 191 callbacks suppressed

  after that usb ports doens't work at all!

  I think the webcam and kernel doesn't like each other but that webcam works 
correctly with RingCentral or Zoom.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  balint 2464 F pulseaudio
   /dev/snd/controlC2:  balint 2464 F pulseaudio
   /dev/snd/controlC1:  balint 2464 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-21 (534 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20U1000XHV
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-44-generic 
root=UUID=2ea68483-fb39-44f6-86a8-b27735f237e6 ro ipv6.disable=1 quiet splash 
pci=nommconf ipv6.disable=1 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-44-generic N/A
   linux-backports-modules-5.11.0-44-generic  N/A
   linux-firmware 1.187.24
  Tags:  focal
  Uname: Linux 5.11.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 08/05/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R17ET21W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U1000XHV
  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: 

[Kernel-packages] [Bug 1964286] [NEW] iwlwifi microcode crash after updating to 5.14.0-1027-oem

[Kai-Chuan Hsieh]

Public bug reported:

Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot sector 
to mark fs as dirty
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error Log 
Dump:
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 
0x004B, valid: 6
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware 
version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | 
ADVANCED_SYSASSERT  
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | 
trm_hw_status0
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | 
trm_hw_status1
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | 
branchlink2
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink1
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink2
...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30
ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
Uname: Linux 5.14.0-1027-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  9 11:13:53 2022
InstallationDate: Installed on 2021-10-19 (140 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-oem-5.14
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Summary changed:

- iwlwifi micrcode crash after updating to 5.14.0-1027-oem
+ iwlwifi microcode crash after updating to 5.14.0-1027-oem

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

Title:
  iwlwifi microcode crash after updating to 5.14.0-1027-oem

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

Bug description:
  Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot 
sector to mark fs as dirty
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Microcode SW error 
detected. Restarting 0x0.
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Start IWL Error 
Log Dump:
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Transport status: 
0x004B, valid: 6
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: Loaded firmware 
version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x0FAD | 
ADVANCED_SYSASSERT  
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0xA210 | 
trm_hw_status0
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x | 
trm_hw_status1
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004CAD42 | 
branchlink2
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink1
  Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi :00:14.3: 0x004C17C6 | 
interruptlink2
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  9 11:13:53 2022
  InstallationDate: Installed on 2021-10-19 (140 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1963914] Re: Require force_probe for i915 driver probing

[Kai-Chuan Hsieh]

** Tags added: oem-priority

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

Title:
  Require force_probe for i915 driver probing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel require force_probe to support ADL-P graphic.

  Reproduce step:
  1. Boot into Ubuntu Jammy
  2. $ lsmod | grep i915, the used number is 0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-18-generic 5.15.0-18.18
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1183 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar  7 21:50:41 2022
  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-psyduck+X192
  InstallationDate: Installed on 2022-03-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 5530
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic 
root=UUID=b3c94cea-c8f7-4579-b41d-6360718d00f0 ro i915.force_probe=4626 quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220302.gitee0667aa-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-07 (0 days ago)
  dmi.bios.date: 02/25/2022
  dmi.bios.release: 1.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.1:bd02/25/2022:br1.0:svnDellInc.:pnLatitude5530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0B06:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5530
  dmi.product.sku: 0B06
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1964278] [NEW] package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.2

[Rod Barnes]

Public bug reported:

running script "apl-sof-setup-audio" to setup SOF audio on laptop.
During the script, received an error "dpkg-deb: error: paste subprocess
was killed by signal." and the bug report dialog appeared immediately
after.

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: firmware-sof-signed 1.7-1
Uname: Linux 5.10.102-g142ef9297957-dirty x86_64
ApportVersion: 2.20.11-0ubuntu71
AptOrdering:
 firmware-sof-signed:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Mar  8 17:44:45 2022
Dependencies:
 
DpkgTerminalLog:
 Preparing to unpack .../firmware-sof-signed_1.7-1_all.deb ...
 Unpacking firmware-sof-signed (1.7-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack):
  trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in 
package linux-firmware 1.201.4
DuplicateSignature:
 package:firmware-sof-signed:1.7-1
 Unpacking firmware-sof-signed (1.7-1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack):
  trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in 
package linux-firmware 1.201.4
ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which 
is also in package linux-firmware 1.201.4
PackageArchitecture: all
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.9
SourcePackage: firmware-sof
Title: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to 
overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package 
linux-firmware 1.201.4
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package impish need-duplicate-check package-conflict 
uec-images

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

Title:
  package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to
  overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in
  package linux-firmware 1.201.4

Status in firmware-sof package in Ubuntu:
  New

Bug description:
  running script "apl-sof-setup-audio" to setup SOF audio on laptop.
  During the script, received an error "dpkg-deb: error: paste
  subprocess was killed by signal." and the bug report dialog appeared
  immediately after.

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: firmware-sof-signed 1.7-1
  Uname: Linux 5.10.102-g142ef9297957-dirty x86_64
  ApportVersion: 2.20.11-0ubuntu71
  AptOrdering:
   firmware-sof-signed:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar  8 17:44:45 2022
  Dependencies:
   
  DpkgTerminalLog:
   Preparing to unpack .../firmware-sof-signed_1.7-1_all.deb ...
   Unpacking firmware-sof-signed (1.7-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack):
trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in 
package linux-firmware 1.201.4
  DuplicateSignature:
   package:firmware-sof-signed:1.7-1
   Unpacking firmware-sof-signed (1.7-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/firmware-sof-signed_1.7-1_all.deb (--unpack):
trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in 
package linux-firmware 1.201.4
  ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which 
is also in package linux-firmware 1.201.4
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.9
  SourcePackage: firmware-sof
  Title: package firmware-sof-signed 1.7-1 failed to install/upgrade: trying to 
overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package 
linux-firmware 1.201.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Re: [Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Paul Szabo]

Do you know whether the fix that went into 5.15.0-22.22
(or into 5.15.0-17.17) is any different from what went
into impish 5.13.0-28.31? That impish fix did NOT work,
did NOT solve the issue.

Oh well... jammy will be released soon, and I will test.
I wonder whether this bug will remain "alive" until then
so, if needed, whether I will be able to complain about
the fix not working (as it did not for impish).

(How to keep a bug alive: regular "pings"?)

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

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
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:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
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:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1960933] Update Released

[Chris Halse Rogers]

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

Title:
  rtw89_pci constantly drops connection with old firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Impish:
  Fix Released

Bug description:
  [Impact]

  This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10
  (impish)

  The current linux-firmware package (1.201.4+1.201.3) ships with
  realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin)
  version v0.13.8.0.

  My wifi chip wasn't able to keep a connection for more than a minute when 
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried 
disabling the power_save and stuff. But that had little to no effect. I was 
about to open an issue on the upstream project and did a last ditch attempt to 
see if there were any firmware updates... I found linux-firmware.git and it had
  two newer versions!

   - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to 
show up)
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17

   - v0.13.33.0 (was submitted in November 2021 and got merged in December 
2021):
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983

  I've downloaded and installed the latest "v0.13.33.0" on a whim and
  rebooted. And what a pleasant surprise: Instantly, my wifi connection
  lasted until the rest of the day.

  Could you please consider updating this realtek firmware in the next
  release? Thanks!

  [Test Case]

  See above.

  [Fix]

  Cherry pick two commit to match current Jammy:
  4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
  ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")

  [Where Problems Could Occur]

  Limited to wifi using RTL8852A HW.

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


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

[Kernel-packages] [Bug 1960933] Re: rtw89_pci constantly drops connection with old firmware

[Launchpad Bug Tracker]

This bug was fixed in the package linux-firmware - 1.201.5

---
linux-firmware (1.201.5) impish; urgency=medium

  * rtw89_pci constantly drops connection with old firmware (LP: #1960933)
- rtw89: 8852a: update fw to v0.13.30.0
- rtw89: 8852a: update fw to v0.13.33.0

 -- Juerg Haefliger   Fri, 18 Feb 2022 15:22:53
+0100

** Changed in: linux-firmware (Ubuntu Impish)
   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/1960933

Title:
  rtw89_pci constantly drops connection with old firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Impish:
  Fix Released

Bug description:
  [Impact]

  This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10
  (impish)

  The current linux-firmware package (1.201.4+1.201.3) ships with
  realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin)
  version v0.13.8.0.

  My wifi chip wasn't able to keep a connection for more than a minute when 
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried 
disabling the power_save and stuff. But that had little to no effect. I was 
about to open an issue on the upstream project and did a last ditch attempt to 
see if there were any firmware updates... I found linux-firmware.git and it had
  two newer versions!

   - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to 
show up)
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17

   - v0.13.33.0 (was submitted in November 2021 and got merged in December 
2021):
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983

  I've downloaded and installed the latest "v0.13.33.0" on a whim and
  rebooted. And what a pleasant surprise: Instantly, my wifi connection
  lasted until the rest of the day.

  Could you please consider updating this realtek firmware in the next
  release? Thanks!

  [Test Case]

  See above.

  [Fix]

  Cherry pick two commit to match current Jammy:
  4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
  ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")

  [Where Problems Could Occur]

  Limited to wifi using RTL8852A HW.

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


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

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

[Taihsiang Ho]

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

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

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

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Released
Status in kunpeng920 ubuntu-21.10 series:
  Fix Released
Status in kunpeng920 ubuntu-22.04 series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification
  =

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

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

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

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

  == Original Bug Description ==

  [Bug Description]

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

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

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

  [Expected Results]
  no fail
  [Reproducibility]
  100%

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

  [Resolution]
  this following patches will solve this bug.

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

  crypto: hisilicon - add ZIP device using mode parameter

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

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

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

  crypto: hisilicon/hpre - register HPRE device to uacce

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

  crypto: hisilicon/sec - register SEC device to uacce

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


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

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Jörg Hänsel]

yes, this was a typo... of course I meant disabled UDP NFS mounting.
And regarding the 2nd point we have the same understanding.

So since "old" clients are still able to mount the NFS shares via nfs3 over udp 
on jammy servers, I would not flip the kernel config 
CONFIG_NFS_DISABLE_UDP_SUPPORT back to "n" and leave it as it is:
CONFIG_NFS_DISABLE_UDP_SUPPORT=y

thank you very much for clarifying!

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Andreas Hasenack]

>  This disabled NFS3 support seems only to affect the client part of
the kernel-module.

NFSv3 is fine, it's udp that is disabled in the kernel (I think you
understood that, and above is just a typo, but clarifying nonetheless).

Clients running a kernel with CONFIG_NFS_DISABLE_UDP_SUPPORT=y should
not be able to mount NFS exports using udp, that's my understanding. I
believe it can still *export* (aka, server) nfs via udp.

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Jörg Hänsel]

I am currently very confused. I restored the snapshots of my test VMs
from yesterday and now I can mount the NFS-shares on the jammy server on
all clients (Knoppix, Ubuntu 18.04) with nfs3+udp after putting "udp=y"
in /etc/nfs.conf, also with the last kernel version 5.15.0-18.

Yesterday in all my tests the udp=y param was ignored, only the vers=? params 
had an effect after restarting the nfs-kernel-server.
My only explanation for now is a problem with the internal network between my 
VirtualBox Test VMs. Sorry, I know this sounds very strange.

But despite of the kernel config option CONFIG_NFS_DISABLE_UDP_SUPPORT=y
I can mount the NFS-shares on the jammy server with nfs3+udp from every
test client VM. /proc/mounts shows: vers=3 and proto=udp

Only on the server itself I cannot mount with nfs3+udp.

mount -o vers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

leads to
mount.nfs: an incorrect mount option was specified

but
mount -o vers=3,tcp 192.168.0.1:/srv/nfs/testshare /mnt

is working.

So conclusion for me now. The /etc/nfs.conf params are working correctly
and my nfs3+udp problem is solved.

But nfs3+udp should not be possible to be enabled with respect to the kernel 
param.
This disabled NFS3 support seems only to affect the client part of the 
kernel-module.

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1964259] Re: Click and drag not working on MacBook trackpad (bcm5974)

[Raphael]

PPS: The driver in question is bcm5974.

** Summary changed:

- Click and drag not working on MacBook trackpad
+ Click and drag not working on MacBook trackpad (bcm5974)

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

Title:
  Click and drag not working on MacBook trackpad (bcm5974)

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

Bug description:
  Click and drag is not working on a MacBookPro8,1 trackpad. (Oddly
  enough, dragging with two fingers does work.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Mar  8 20:38:23 2022
  InstallationDate: Installed on 2022-03-03 (4 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: Upgraded to focal on 2022-03-08 (0 days ago)

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


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

[Kernel-packages] [Bug 1964259] Re: Click and drag not working on MacBook trackpad

[Raphael]

PS: Unlike what i wrote before, click-dragging with two fingers doesn't
work properly: the cursor gets stuck after a while – sometimes
immediately, sometimes only after a few seconds.

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

Title:
  Click and drag not working on MacBook trackpad

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

Bug description:
  Click and drag is not working on a MacBookPro8,1 trackpad. (Oddly
  enough, dragging with two fingers does work.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Mar  8 20:38:23 2022
  InstallationDate: Installed on 2022-03-03 (4 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: Upgraded to focal on 2022-03-08 (0 days ago)

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


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

[Kernel-packages] [Bug 1964259] [NEW] Click and drag not working on MacBook trackpad

[Raphael]

Public bug reported:

Click and drag is not working on a MacBookPro8,1 trackpad. (Oddly
enough, dragging with two fingers does work.)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Tue Mar  8 20:38:23 2022
InstallationDate: Installed on 2022-03-03 (4 days ago)
InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: Upgraded to focal on 2022-03-08 (0 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  Click and drag not working on MacBook trackpad

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

Bug description:
  Click and drag is not working on a MacBookPro8,1 trackpad. (Oddly
  enough, dragging with two fingers does work.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Mar  8 20:38:23 2022
  InstallationDate: Installed on 2022-03-03 (4 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: Upgraded to focal on 2022-03-08 (0 days ago)

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


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

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Andreas Hasenack]

Are you sure it's using udp? Did you confirm with /proc/mounts or mount
output? I didn't get it to work, not even with a focal server, and the
kernel option disabling UDP sounds very adamant.

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1951055] Re: Reinstate ACPI S5 for reboot

[Launchpad Bug Tracker]

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

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

  * CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- SAUCE: x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- SAUCE: x86/speculation: Add eIBRS + Retpoline options
- SAUCE: Documentation/hw-vuln: Update spectre doc

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

  * focal/linux-oem-5.14: 5.14.0-1025.27 -proposed tracker (LP:
#1961265)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.02.21)
- [Config] Update config to match upstream stable release

  * Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e
currently (LP: #1961971)
- SAUCE: iwlwifi: disable 6-7 GHz channels

  * Fix With 20.04d kernel and WX3200, unit freezes on resume (LP: #1961855)
- SAUCE: drm/amd: Check if ASPM is enabled from PCIe subsystem

  * CVE-2022-25636
- netfilter: nf_tables_offload: incorrect flow offload action array size

  * Focal update: upstream stable patchset 2022-02-22 (LP: #1961793)
- PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
- selftests: mptcp: fix ipv6 routing setup
- net: ipa: use a bitmap for endpoint replenish_enabled
- net: ipa: prevent concurrent replenish
- drm/vc4: hdmi: Make sure the device is powered with CEC
- net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
- net/mlx5: Bridge, take rtnl lock in init error handler
- net/mlx5: Bridge, ensure dev_name is null-terminated
- net/mlx5e: Fix handling of wrong devices during bond netevent
- net/mlx5: Use del_timer_sync in fw reset flow of halting poll
- net/mlx5e: Fix module EEPROM query
- net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
- net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
- net/mlx5: Bridge, Fix devlink deadlock on net namespace deletion
- net/mlx5: E-Switch, Fix uninitialized variable modact
- ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
- i40e: Fix reset bw limit when DCB enabled with 1 TC
- i40e: Fix reset path while removing the driver
- net: amd-xgbe: ensure to reset the tx_timer_active flag
- net: amd-xgbe: Fix skb data length underflow
- fanotify: Fix stale file descriptor in copy_event_to_user()
- net: sched: fix use-after-free in tc_new_tfilter()
- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
- cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
- af_packet: fix data-race in packet_setsockopt / packet_setsockopt
- tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC"
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC" again
- drm/i915: Disable DSB usage for now
- selinux: fix double free of cond_list on error paths
- audit: improve audit queue handling when "audit=1" on cmdline
- ipc/sem: do not sleep with a spin lock held
- spi: stm32-qspi: Update spi registering
- ASoC: hdmi-codec: Fix OOB memory accesses
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Correct quirk for VF0770
- ALSA: hda: Fix UAF of leds class devs at unbinding
- ALSA: hda: realtek: Fix race at concurrent COEF updates
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
  quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
  chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
  reboot from Windows
- btrfs: don't start transaction for scrub if the fs is mounted read-only
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- btrfs: fix use-after-free after failure to create a snapshot
- Revert "fs/9p: search open fids first"
- drm/nouveau: fix off by one in BIOS boundary checking
- drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
- drm/amd/display: watermark latencies is not enough on DCN31
- drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple 
Retina
  panels
- nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
- mm/debug_vm_pgtable: remove pte entry from the page table
- mm/pgtable: define pte_index so that preprocessor could recognize it
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- dma-buf: heaps: Fix potential spectre v1 gadget
- IB/hfi1: Fix AIP early init panic
- Revert 

[Kernel-packages] [Bug 1961119] Re: Lower the volume of expected s0i3 WARN_ON

[Launchpad Bug Tracker]

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

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

  * CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- SAUCE: x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- SAUCE: x86/speculation: Add eIBRS + Retpoline options
- SAUCE: Documentation/hw-vuln: Update spectre doc

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

  * focal/linux-oem-5.14: 5.14.0-1025.27 -proposed tracker (LP:
#1961265)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.02.21)
- [Config] Update config to match upstream stable release

  * Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e
currently (LP: #1961971)
- SAUCE: iwlwifi: disable 6-7 GHz channels

  * Fix With 20.04d kernel and WX3200, unit freezes on resume (LP: #1961855)
- SAUCE: drm/amd: Check if ASPM is enabled from PCIe subsystem

  * CVE-2022-25636
- netfilter: nf_tables_offload: incorrect flow offload action array size

  * Focal update: upstream stable patchset 2022-02-22 (LP: #1961793)
- PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
- selftests: mptcp: fix ipv6 routing setup
- net: ipa: use a bitmap for endpoint replenish_enabled
- net: ipa: prevent concurrent replenish
- drm/vc4: hdmi: Make sure the device is powered with CEC
- net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
- net/mlx5: Bridge, take rtnl lock in init error handler
- net/mlx5: Bridge, ensure dev_name is null-terminated
- net/mlx5e: Fix handling of wrong devices during bond netevent
- net/mlx5: Use del_timer_sync in fw reset flow of halting poll
- net/mlx5e: Fix module EEPROM query
- net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
- net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
- net/mlx5: Bridge, Fix devlink deadlock on net namespace deletion
- net/mlx5: E-Switch, Fix uninitialized variable modact
- ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
- i40e: Fix reset bw limit when DCB enabled with 1 TC
- i40e: Fix reset path while removing the driver
- net: amd-xgbe: ensure to reset the tx_timer_active flag
- net: amd-xgbe: Fix skb data length underflow
- fanotify: Fix stale file descriptor in copy_event_to_user()
- net: sched: fix use-after-free in tc_new_tfilter()
- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
- cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
- af_packet: fix data-race in packet_setsockopt / packet_setsockopt
- tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC"
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC" again
- drm/i915: Disable DSB usage for now
- selinux: fix double free of cond_list on error paths
- audit: improve audit queue handling when "audit=1" on cmdline
- ipc/sem: do not sleep with a spin lock held
- spi: stm32-qspi: Update spi registering
- ASoC: hdmi-codec: Fix OOB memory accesses
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Correct quirk for VF0770
- ALSA: hda: Fix UAF of leds class devs at unbinding
- ALSA: hda: realtek: Fix race at concurrent COEF updates
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
  quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
  chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
  reboot from Windows
- btrfs: don't start transaction for scrub if the fs is mounted read-only
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- btrfs: fix use-after-free after failure to create a snapshot
- Revert "fs/9p: search open fids first"
- drm/nouveau: fix off by one in BIOS boundary checking
- drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
- drm/amd/display: watermark latencies is not enough on DCN31
- drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple 
Retina
  panels
- nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
- mm/debug_vm_pgtable: remove pte entry from the page table
- mm/pgtable: define pte_index so that preprocessor could recognize it
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- dma-buf: heaps: Fix potential spectre v1 gadget
- IB/hfi1: Fix AIP early init panic
- Revert 

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

[Launchpad Bug Tracker]

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

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

  * CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- SAUCE: x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- SAUCE: x86/speculation: Add eIBRS + Retpoline options
- SAUCE: Documentation/hw-vuln: Update spectre doc

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

  * focal/linux-oem-5.14: 5.14.0-1025.27 -proposed tracker (LP:
#1961265)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.02.21)
- [Config] Update config to match upstream stable release

  * Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e
currently (LP: #1961971)
- SAUCE: iwlwifi: disable 6-7 GHz channels

  * Fix With 20.04d kernel and WX3200, unit freezes on resume (LP: #1961855)
- SAUCE: drm/amd: Check if ASPM is enabled from PCIe subsystem

  * CVE-2022-25636
- netfilter: nf_tables_offload: incorrect flow offload action array size

  * Focal update: upstream stable patchset 2022-02-22 (LP: #1961793)
- PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
- selftests: mptcp: fix ipv6 routing setup
- net: ipa: use a bitmap for endpoint replenish_enabled
- net: ipa: prevent concurrent replenish
- drm/vc4: hdmi: Make sure the device is powered with CEC
- net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
- net/mlx5: Bridge, take rtnl lock in init error handler
- net/mlx5: Bridge, ensure dev_name is null-terminated
- net/mlx5e: Fix handling of wrong devices during bond netevent
- net/mlx5: Use del_timer_sync in fw reset flow of halting poll
- net/mlx5e: Fix module EEPROM query
- net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
- net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
- net/mlx5: Bridge, Fix devlink deadlock on net namespace deletion
- net/mlx5: E-Switch, Fix uninitialized variable modact
- ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
- i40e: Fix reset bw limit when DCB enabled with 1 TC
- i40e: Fix reset path while removing the driver
- net: amd-xgbe: ensure to reset the tx_timer_active flag
- net: amd-xgbe: Fix skb data length underflow
- fanotify: Fix stale file descriptor in copy_event_to_user()
- net: sched: fix use-after-free in tc_new_tfilter()
- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
- cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
- af_packet: fix data-race in packet_setsockopt / packet_setsockopt
- tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC"
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC" again
- drm/i915: Disable DSB usage for now
- selinux: fix double free of cond_list on error paths
- audit: improve audit queue handling when "audit=1" on cmdline
- ipc/sem: do not sleep with a spin lock held
- spi: stm32-qspi: Update spi registering
- ASoC: hdmi-codec: Fix OOB memory accesses
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Correct quirk for VF0770
- ALSA: hda: Fix UAF of leds class devs at unbinding
- ALSA: hda: realtek: Fix race at concurrent COEF updates
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
  quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
  chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
  reboot from Windows
- btrfs: don't start transaction for scrub if the fs is mounted read-only
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- btrfs: fix use-after-free after failure to create a snapshot
- Revert "fs/9p: search open fids first"
- drm/nouveau: fix off by one in BIOS boundary checking
- drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
- drm/amd/display: watermark latencies is not enough on DCN31
- drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple 
Retina
  panels
- nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
- mm/debug_vm_pgtable: remove pte entry from the page table
- mm/pgtable: define pte_index so that preprocessor could recognize it
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- dma-buf: heaps: Fix potential spectre v1 gadget
- IB/hfi1: Fix AIP early init panic
- Revert 

[Kernel-packages] [Bug 1961793] Re: Focal update: upstream stable patchset 2022-02-22

[Launchpad Bug Tracker]

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

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

  * CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- SAUCE: x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- SAUCE: x86/speculation: Add eIBRS + Retpoline options
- SAUCE: Documentation/hw-vuln: Update spectre doc

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

  * focal/linux-oem-5.14: 5.14.0-1025.27 -proposed tracker (LP:
#1961265)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.02.21)
- [Config] Update config to match upstream stable release

  * Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e
currently (LP: #1961971)
- SAUCE: iwlwifi: disable 6-7 GHz channels

  * Fix With 20.04d kernel and WX3200, unit freezes on resume (LP: #1961855)
- SAUCE: drm/amd: Check if ASPM is enabled from PCIe subsystem

  * CVE-2022-25636
- netfilter: nf_tables_offload: incorrect flow offload action array size

  * Focal update: upstream stable patchset 2022-02-22 (LP: #1961793)
- PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
- selftests: mptcp: fix ipv6 routing setup
- net: ipa: use a bitmap for endpoint replenish_enabled
- net: ipa: prevent concurrent replenish
- drm/vc4: hdmi: Make sure the device is powered with CEC
- net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
- net/mlx5: Bridge, take rtnl lock in init error handler
- net/mlx5: Bridge, ensure dev_name is null-terminated
- net/mlx5e: Fix handling of wrong devices during bond netevent
- net/mlx5: Use del_timer_sync in fw reset flow of halting poll
- net/mlx5e: Fix module EEPROM query
- net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
- net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
- net/mlx5: Bridge, Fix devlink deadlock on net namespace deletion
- net/mlx5: E-Switch, Fix uninitialized variable modact
- ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
- i40e: Fix reset bw limit when DCB enabled with 1 TC
- i40e: Fix reset path while removing the driver
- net: amd-xgbe: ensure to reset the tx_timer_active flag
- net: amd-xgbe: Fix skb data length underflow
- fanotify: Fix stale file descriptor in copy_event_to_user()
- net: sched: fix use-after-free in tc_new_tfilter()
- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
- cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
- af_packet: fix data-race in packet_setsockopt / packet_setsockopt
- tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC"
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC" again
- drm/i915: Disable DSB usage for now
- selinux: fix double free of cond_list on error paths
- audit: improve audit queue handling when "audit=1" on cmdline
- ipc/sem: do not sleep with a spin lock held
- spi: stm32-qspi: Update spi registering
- ASoC: hdmi-codec: Fix OOB memory accesses
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Correct quirk for VF0770
- ALSA: hda: Fix UAF of leds class devs at unbinding
- ALSA: hda: realtek: Fix race at concurrent COEF updates
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
  quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
  chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
  reboot from Windows
- btrfs: don't start transaction for scrub if the fs is mounted read-only
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- btrfs: fix use-after-free after failure to create a snapshot
- Revert "fs/9p: search open fids first"
- drm/nouveau: fix off by one in BIOS boundary checking
- drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
- drm/amd/display: watermark latencies is not enough on DCN31
- drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple 
Retina
  panels
- nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
- mm/debug_vm_pgtable: remove pte entry from the page table
- mm/pgtable: define pte_index so that preprocessor could recognize it
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- dma-buf: heaps: Fix potential spectre v1 gadget
- IB/hfi1: Fix AIP early init panic
- Revert 

[Kernel-packages] [Bug 1961971] Re: Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e currently

[Launchpad Bug Tracker]

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

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

  * CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- SAUCE: x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- SAUCE: x86/speculation: Add eIBRS + Retpoline options
- SAUCE: Documentation/hw-vuln: Update spectre doc

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

  * focal/linux-oem-5.14: 5.14.0-1025.27 -proposed tracker (LP:
#1961265)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.02.21)
- [Config] Update config to match upstream stable release

  * Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e
currently (LP: #1961971)
- SAUCE: iwlwifi: disable 6-7 GHz channels

  * Fix With 20.04d kernel and WX3200, unit freezes on resume (LP: #1961855)
- SAUCE: drm/amd: Check if ASPM is enabled from PCIe subsystem

  * CVE-2022-25636
- netfilter: nf_tables_offload: incorrect flow offload action array size

  * Focal update: upstream stable patchset 2022-02-22 (LP: #1961793)
- PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
- selftests: mptcp: fix ipv6 routing setup
- net: ipa: use a bitmap for endpoint replenish_enabled
- net: ipa: prevent concurrent replenish
- drm/vc4: hdmi: Make sure the device is powered with CEC
- net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
- net/mlx5: Bridge, take rtnl lock in init error handler
- net/mlx5: Bridge, ensure dev_name is null-terminated
- net/mlx5e: Fix handling of wrong devices during bond netevent
- net/mlx5: Use del_timer_sync in fw reset flow of halting poll
- net/mlx5e: Fix module EEPROM query
- net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
- net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
- net/mlx5: Bridge, Fix devlink deadlock on net namespace deletion
- net/mlx5: E-Switch, Fix uninitialized variable modact
- ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
- i40e: Fix reset bw limit when DCB enabled with 1 TC
- i40e: Fix reset path while removing the driver
- net: amd-xgbe: ensure to reset the tx_timer_active flag
- net: amd-xgbe: Fix skb data length underflow
- fanotify: Fix stale file descriptor in copy_event_to_user()
- net: sched: fix use-after-free in tc_new_tfilter()
- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
- cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
- af_packet: fix data-race in packet_setsockopt / packet_setsockopt
- tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC"
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC" again
- drm/i915: Disable DSB usage for now
- selinux: fix double free of cond_list on error paths
- audit: improve audit queue handling when "audit=1" on cmdline
- ipc/sem: do not sleep with a spin lock held
- spi: stm32-qspi: Update spi registering
- ASoC: hdmi-codec: Fix OOB memory accesses
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Correct quirk for VF0770
- ALSA: hda: Fix UAF of leds class devs at unbinding
- ALSA: hda: realtek: Fix race at concurrent COEF updates
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
  quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
  chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
  reboot from Windows
- btrfs: don't start transaction for scrub if the fs is mounted read-only
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- btrfs: fix use-after-free after failure to create a snapshot
- Revert "fs/9p: search open fids first"
- drm/nouveau: fix off by one in BIOS boundary checking
- drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
- drm/amd/display: watermark latencies is not enough on DCN31
- drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple 
Retina
  panels
- nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
- mm/debug_vm_pgtable: remove pte entry from the page table
- mm/pgtable: define pte_index so that preprocessor could recognize it
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- dma-buf: heaps: Fix potential spectre v1 gadget
- IB/hfi1: Fix AIP early init panic
- Revert 

[Kernel-packages] [Bug 1961855] Re: Fix With 20.04d kernel and WX3200, unit freezes on resume

[Launchpad Bug Tracker]

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

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

  * CVE-2022-0001
- x86,bugs: Unconditionally allow spectre_v2=retpoline,amd
- SAUCE: x86/speculation: Rename RETPOLINE_AMD to RETPOLINE_LFENCE
- SAUCE: x86/speculation: Add eIBRS + Retpoline options
- SAUCE: Documentation/hw-vuln: Update spectre doc

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

  * focal/linux-oem-5.14: 5.14.0-1025.27 -proposed tracker (LP:
#1961265)

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.02.21)
- [Config] Update config to match upstream stable release

  * Disable iwlwifi UHB (ultra high band) channels if we don't support wifi 6e
currently (LP: #1961971)
- SAUCE: iwlwifi: disable 6-7 GHz channels

  * Fix With 20.04d kernel and WX3200, unit freezes on resume (LP: #1961855)
- SAUCE: drm/amd: Check if ASPM is enabled from PCIe subsystem

  * CVE-2022-25636
- netfilter: nf_tables_offload: incorrect flow offload action array size

  * Focal update: upstream stable patchset 2022-02-22 (LP: #1961793)
- PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
- selftests: mptcp: fix ipv6 routing setup
- net: ipa: use a bitmap for endpoint replenish_enabled
- net: ipa: prevent concurrent replenish
- drm/vc4: hdmi: Make sure the device is powered with CEC
- net/mlx5e: IPsec: Fix tunnel mode crypto offload for non TCP/UDP traffic
- net/mlx5: Bridge, take rtnl lock in init error handler
- net/mlx5: Bridge, ensure dev_name is null-terminated
- net/mlx5e: Fix handling of wrong devices during bond netevent
- net/mlx5: Use del_timer_sync in fw reset flow of halting poll
- net/mlx5e: Fix module EEPROM query
- net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
- net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
- net/mlx5: Bridge, Fix devlink deadlock on net namespace deletion
- net/mlx5: E-Switch, Fix uninitialized variable modact
- ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
- i40e: Fix reset bw limit when DCB enabled with 1 TC
- i40e: Fix reset path while removing the driver
- net: amd-xgbe: ensure to reset the tx_timer_active flag
- net: amd-xgbe: Fix skb data length underflow
- fanotify: Fix stale file descriptor in copy_event_to_user()
- net: sched: fix use-after-free in tc_new_tfilter()
- rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
- cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
- af_packet: fix data-race in packet_setsockopt / packet_setsockopt
- tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC"
- Revert "drm/vc4: hdmi: Make sure the device is powered with CEC" again
- drm/i915: Disable DSB usage for now
- selinux: fix double free of cond_list on error paths
- audit: improve audit queue handling when "audit=1" on cmdline
- ipc/sem: do not sleep with a spin lock held
- spi: stm32-qspi: Update spi registering
- ASoC: hdmi-codec: Fix OOB memory accesses
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
- ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
- ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
- ALSA: usb-audio: Correct quirk for VF0770
- ALSA: hda: Fix UAF of leds class devs at unbinding
- ALSA: hda: realtek: Fix race at concurrent COEF updates
- ALSA: hda/realtek: Add quirk for ASUS GU603
- ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220
  quirks
- ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer
  chipset)
- ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after
  reboot from Windows
- btrfs: don't start transaction for scrub if the fs is mounted read-only
- btrfs: fix deadlock between quota disable and qgroup rescan worker
- btrfs: fix use-after-free after failure to create a snapshot
- Revert "fs/9p: search open fids first"
- drm/nouveau: fix off by one in BIOS boundary checking
- drm/amd/pm: correct the MGpuFanBoost support for Beige Goby
- drm/amd/display: watermark latencies is not enough on DCN31
- drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple 
Retina
  panels
- nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
- mm/debug_vm_pgtable: remove pte entry from the page table
- mm/pgtable: define pte_index so that preprocessor could recognize it
- mm/kmemleak: avoid scanning potential huge holes
- block: bio-integrity: Advance seed correctly for larger interval sizes
- dma-buf: heaps: Fix potential spectre v1 gadget
- IB/hfi1: Fix AIP early init panic
- Revert 

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Andreas Hasenack]

I added this to the Jammy 22.04 release notes at
https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

If it's decided to flip this option before release, please remove that
release notes remark.

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Jörg Hänsel]

I just updated linux-image-5.15.0-18-generic to today's new version
linux-image-5.15.0-22-generic.

Now with enabling "udp=y" in /etc/nfs.conf and the new kernel version I can 
mount
the nfs-share on the jammy server from the koppix pxe initdrd (busybox mount) 
with nfs version 3 and udp.

Only mounting jammy server from jammy client is still not possible with
nfs3+udp.

The diff of /boot/config-5.15.0-18-generic and
/boot/config-5.15.0-22-generic shows no hints of NFS related changes in
the kernel config.

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Andreas Hasenack]

This was first disabled on groovy, the first ubuntu release after focal:

root@g1:~# grep NFS /boot/config-5.8.0-59-generic |grep UDP
CONFIG_NFS_DISABLE_UDP_SUPPORT=y

The upstream help text next to that kernel option says:
"""
Choose Y here to disable the use of NFS over UDP. NFS over UDP
on modern networks (1Gb+) can lead to data corruption caused by
fragmentation during high loads.
"""

I'll leave it to the kernel team to comment further.

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1690512] Re: shutdown/restart/suspend freezes laptop on intel graphics

[Paul White]

I'm closing this issue earlier than normal as I'm moving away from
reviewing bug reports that have received little or no attention in
recent times and there have been no comments to suggest that the
reported problem is still an issue when using a currently supported
release of Ubuntu.

Please feel to revert the status of this bug report to a previous status
if this is still an issue while using a currently supported release of
Ubuntu.


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

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

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

Title:
  shutdown/restart/suspend freezes laptop on intel graphics

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I'm not sure where to report this under, so please bear with me.
  Reporting this bug using ubuntu-bug just crashes my system if im using
  intel graphics, I had to switch to nvidia graphics just to file this
  bug report so the automatically attached log files may not be a good
  representation of the problem.

  I've attached the syslog and kern.log files below.

  PROBLEM:

  When using intel graphics:

  Whenever I close the laptop lid or restart / shutdown using GUI or
  terminal commands, it goes into a black screen with a single "_" at
  the top left corner, and hangs. Only long-pressing (hard reset) the
  power button would shut down the computer.

  However, when I use sudo prime-select nvidia to switch over to nvidia,
  everything works fine.log

  I have tried many things, and all do not work. I have attached the
  logs for /var/log/syslog and /var/log/kern.log below.

  Attempts so far:

  1)Tried installing new intel drivers from Updated kernel to 4.8 now
  missing firmware warnings --> Did not work. Issue persists

  2) Tried upgrading kernel from 4.8 to 4.10.15 --> Did not work.
  Problem got worse. Instead of the normal login screen, it gives a
  terminal login screen and hangs.

  3) Tried the fix to nvidia-prime
  https://askubuntu.com/a/884506/547039, but both the poweron.sh and
  poweroff.sh script hangs my laptop instead.

  4) Tried sudo swapoff -a && systemctl poweroff as a workaround, no
  avail.

  5) Tried changing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" Does not work
  either.

  Additional note:
  'sudo lshw -C display' on intel graphics outputs PCI(sysfs) then laptop 
freezes.

  LOG FILES:
  /var/log/syslog
  https://codeshare.io/5XOPwM

  /var/log/kern.log
  https://codeshare.io/aJp6nq

  specs:

  Intel 7700HQ, NVIDIA 1060GTX, kernel 4.8, Ubuntu 16.04

  Would really appreciate your help. Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 13 17:06:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-77-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-49-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-51-generic, x86_64: installed
   nvidia-381, 381.22, 4.8.0-51-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
   NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
  InstallationDate: Installed on 2017-03-30 (43 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 0483:374b STMicroelectronics ST-LINK/V2.1 
(Nucleo-F103RB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root 

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Andreas Hasenack]

Found this in /boot/config-$(uname -r):

CONFIG_NFS_DISABLE_UDP_SUPPORT=y

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1964093] Re: nfsver=3, udp not working anymore

[Andreas Hasenack]

I restored nfs-utils 1.x in the jammy client, and tried to mount again.
It still fails. I don't think this is an nfs-utils problem:

ubuntu@j-nfs-dep8:~$ dpkg -l|grep nfs
ii  libnfsidmap2:amd64   0.25-6build1   amd64   
 NFS idmapping library
ii  nfs-common   1:1.3.4-6ubuntu1   amd64   
 NFS support files common to client and server
ubuntu@j-nfs-dep8:~$ sudo -i
root@j-nfs-dep8:~# mount f1:/storage /mnt -o udp -v
mount.nfs: timeout set for Tue Mar  8 17:54:59 2022
mount.nfs: trying text-based options 
'udp,vers=4.2,addr=192.168.122.197,clientaddr=192.168.122.61'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 
'udp,vers=4.1,addr=192.168.122.197,clientaddr=192.168.122.61'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 
'udp,vers=4.0,addr=192.168.122.197,clientaddr=192.168.122.61'
mount.nfs: mount(2): Invalid argument
mount.nfs: trying text-based options 'udp,addr=192.168.122.197'
mount.nfs: prog 13, trying vers=3, prot=17
mount.nfs: trying 192.168.122.197 prog 13 vers 3 prot UDP port 2049
mount.nfs: prog 15, trying vers=3, prot=17
mount.nfs: trying 192.168.122.197 prog 15 vers 3 prot UDP port 51873
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified


** Package changed: nfs-utils (Ubuntu) => linux (Ubuntu)

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

Title:
  nfsver=3,udp not working anymore

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Package: nfs-kernel-server
  Architecture: amd64
  Version: 1:2.6.1-1~exp1ubuntu1

  nfsversion 3 with proto udp seems not to be supported by the nfs-
  kernel-server anymore.

  In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
  possible. I could mount with either tcp or udp:

  1. tcp
  mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  2. udp
  mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

  mount|grep mnt:

  192.168.0.1:/srv/nfs/testshare on /mnt type nfs
  
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)

  
  Now in Ubuntu 22.04 I get the message:

  mount.nfs: an incorrect mount option was specified

  
  I tried to enable upd in /etc/nfs.conf in section [nfsd]:

  
  [nfsd]
  # debug=0
  # threads=8
  # host=
  # port=0
  # grace-time=90
  # lease-time=90
  # udp=n
  udp=y
  # tcp=y
  # vers2=n
  # vers3=y

  But there was no effect.

  nfs3 with udp is needed by several busybox mount binaries in initrds
  of Knoppix and other live distributions used via PXE boot.

  Best regards
  Jörg

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


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

[Kernel-packages] [Bug 1964093] [NEW] nfsver=3, udp not working anymore

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Package: nfs-kernel-server
Architecture: amd64
Version: 1:2.6.1-1~exp1ubuntu1

nfsversion 3 with proto udp seems not to be supported by the nfs-kernel-
server anymore.

In Ubuntu 18.04 (nfs-kernel-server 1:1.3.4-2.1ubuntu5) it was still
possible. I could mount with either tcp or udp:

1. tcp
mount -o nfsvers=3 192.168.0.1:/srv/nfs/testshare /mnt

mount|grep mnt:

192.168.0.1:/srv/nfs/testshare on /mnt type nfs
(rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)


2. udp
mount -o nfsvers=3,udp 192.168.0.1:/srv/nfs/testshare /mnt

mount|grep mnt:

192.168.0.1:/srv/nfs/testshare on /mnt type nfs
(rw,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=59808,mountproto=udp,local_lock=none,addr=192.168.0.1)


Now in Ubuntu 22.04 I get the message:

mount.nfs: an incorrect mount option was specified


I tried to enable upd in /etc/nfs.conf in section [nfsd]:


[nfsd]
# debug=0
# threads=8
# host=
# port=0
# grace-time=90
# lease-time=90
# udp=n
udp=y
# tcp=y
# vers2=n
# vers3=y

But there was no effect.

nfs3 with udp is needed by several busybox mount binaries in initrds of
Knoppix and other live distributions used via PXE boot.

Best regards
Jörg

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


** Tags: server-todo
-- 
nfsver=3,udp not working anymore
https://bugs.launchpad.net/bugs/1964093
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 1960933] Re: rtw89_pci constantly drops connection with old firmware

[Juerg Haefliger]

** Tags added: verification-done-impish

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

Title:
  rtw89_pci constantly drops connection with old firmware

Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10
  (impish)

  The current linux-firmware package (1.201.4+1.201.3) ships with
  realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin)
  version v0.13.8.0.

  My wifi chip wasn't able to keep a connection for more than a minute when 
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried 
disabling the power_save and stuff. But that had little to no effect. I was 
about to open an issue on the upstream project and did a last ditch attempt to 
see if there were any firmware updates... I found linux-firmware.git and it had
  two newer versions!

   - v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to 
show up)
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17

   - v0.13.33.0 (was submitted in November 2021 and got merged in December 
2021):
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983

  I've downloaded and installed the latest "v0.13.33.0" on a whim and
  rebooted. And what a pleasant surprise: Instantly, my wifi connection
  lasted until the rest of the day.

  Could you please consider updating this realtek firmware in the next
  release? Thanks!

  [Test Case]

  See above.

  [Fix]

  Cherry pick two commit to match current Jammy:
  4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
  ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")

  [Where Problems Could Occur]

  Limited to wifi using RTL8852A HW.

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


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

[Kernel-packages] [Bug 1964144] [NEW] jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y (2022-03-08)

[Juerg Haefliger]

Public bug reported:


Upstream raspberrypi patchset 2022-03-08

  Ported from the following raspberrypi branch:
rpi-5.15.y
  from https://github.com/raspberrypi/linux.git

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

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


** Tags: kern-2651

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

** Also affects: linux-raspi (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

** Tags added: kern-2651

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

Title:
  jammy/linux-raspi: Update to upstream raspberrypi rpi-5.15.y
  (2022-03-08)

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

Bug description:
  
  Upstream raspberrypi patchset 2022-03-08

Ported from the following raspberrypi branch:
  rpi-5.15.y
from https://github.com/raspberrypi/linux.git

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


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

[Kernel-packages] [Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

[Gamithra M]

Same issue here, same machine. I'm dual booting and the issue persists
on Windows, too, even in BIOS settings.

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

Title:
  trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my X1 Yoga Titanium (which has a fancy new "Sensel" trackpad with
  haptic response to clicks), the trackpad stops working after a
  suspend/resume cycle, although the red trackpoint continues to work
  fine for controlling the pointer.  I believe this system is using S0i3
  for suspend, in case that's relevant.

  If I boot from power off, then the trackpad works fine in both the
  pre-boot BIOS and in Ubuntu 22.04 (prerelease), including haptic
  response to clicks.  After a suspend/resume cycle, the trackpad stops
  responding, although a lot of swiping/pressing will occasionally
  produce a button press event.  This state persists even if I reboot
  out of Linux (without a power cycle) - for example the trackpad no
  longer works for the pre-boot BIOS configuration screen, until a full
  power cycle (which fixes the trackpad).

  Possibly relevant, the trackpad seems to be this device to the kernel:

  [2.016917] input: SNSL0001:00 2C2F:0006 Mouse as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input6
  [2.016964] input: SNSL0001:00 2C2F:0006 Touchpad as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-SNSL0001:00/0018:2C2F:0006.0001/input/input7
  [2.017027] hid-generic 0018:2C2F:0006.0001: input,hidraw0: I2C HID v1.00 
Mouse [SNSL0001:00 2C2F:0006] on i2c-SNSL0001:00

  and the last kernel messages before suspend are:

  [  305.216189] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  305.217435] printk: Suspending console(s) (use no_console_suspend to debug)
  [  305.274332] i2c_designware i2c_designware.0: i2c_dw_handle_tx_abort: lost 
arbitration
  [  306.030947] i2c_hid_acpi i2c-SNSL0001:00: failed to set a report to device.
  [  306.616463] ACPI: EC: interrupt blocked
  [  331.551118] ACPI: EC: interrupt unblocked

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bina   1543 F pipewire
bina   1544 F pipewire-media-
bina   1545 F pulseaudio
   /dev/snd/seq:bina   1543 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  1 14:54:14 2022
  InstallationDate: Installed on 2022-02-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  MachineType: LENOVO 20QA000EUS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220124.git0c6a7b3b-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2MET53W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QA000EUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.11
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2MET53W(1.18):bd09/30/2021:br1.18:efr1.11:svnLENOVO:pn20QA000EUS:pvrThinkPadX1TitaniumGen1:rvnLENOVO:rn20QA000EUS:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20QA_BU_Think_FM_ThinkPadX1TitaniumGen1:
  dmi.product.family: ThinkPad X1 Titanium Gen 1
  dmi.product.name: 20QA000EUS
  dmi.product.sku: LENOVO_MT_20QA_BU_Think_FM_ThinkPad X1 Titanium Gen 1
  dmi.product.version: ThinkPad X1 Titanium Gen 1
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x

[Kleber Sacilotto de Souza]

Patch sent upstream: https://marc.info/?l=linux-
netdev=164674758624957=2

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

** Changed in: linux (Ubuntu Impish)
   Status: Confirmed => In Progress

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)

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

Title:
  ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz

  The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x:

  15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh
  15:45:23 DEBUG| [stdout] # PASS: policy routing
  15:45:23 DEBUG| [stdout] # PASS: route get
  15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired
  15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete
  15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy
  15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint
  15:45:29 DEBUG| [stdout] # PASS: gretap
  15:45:29 DEBUG| [stdout] # PASS: ip6gretap
  15:45:29 DEBUG| [stdout] # PASS: erspan
  15:45:29 DEBUG| [stdout] # PASS: ip6erspan
  15:45:30 DEBUG| [stdout] # PASS: bridge setup
  15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel
  15:45:31 DEBUG| [stdout] # PASS: set ifalias 
b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0
  15:45:31 DEBUG| [stdout] # PASS: vrf
  15:45:31 DEBUG| [stdout] # PASS: vxlan
  15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test
  15:45:31 DEBUG| [stdout] # PASS: macsec
  15:45:32 DEBUG| [stdout] # PASS: ipsec
  15:45:33 DEBUG| [stdout] # 3,7c3,7
  15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 
salt=0x64636261 crypt=1
  15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 
33343536
  15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x   
c0a87b03
  15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 
salt=0x64636261 crypt=1
  15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 
33343536
  15:45:33 DEBUG| [stdout] # ---
  15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 
salt=0x61626364 crypt=1
  15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 
36353433
  15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x   
037ba8c0
  15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 
salt=0x61626364 crypt=1
  15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 
36353433
  15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data
  15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload
  15:45:33 DEBUG| [stdout] # PASS: bridge fdb get
  15:45:33 DEBUG| [stdout] # PASS: neigh get
  15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions


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

Re: [Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Paul Szabo]

My laptop is running Ubuntu 21.10 "impish", still.
Can I test this fix somehow, without fully upgrading to "jammy"?

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

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
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:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
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:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1964082] Re: MAAS deployment to raspberry pi fails for release 21.10

[Dimitri John Ledkov]

It could be missing drivers or firmware, it would be nice to see a dmesg
or lsmod from a working system with said USB disk & the non-working
system.

I.e. to identify if 21.10 is somehow missing some kernel modules, or
firmware.

Note that in 21.10 we have split raspi modules into two packages, does
your procedure installs and configures linux-modules-extra-raspi ? such
that more drivers are available.

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

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

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

Title:
  MAAS deployment to raspberry pi fails for release 21.10

Status in MAAS:
  New
Status in linux-raspi package in Ubuntu:
  Incomplete

Bug description:
  I have helped develop a reliable procedure for using MAAS to deploy
  ubuntu 20.04 to a Raspberry Pi cluster. Details are here:
  https://discourse.maas.io/t/build-your-own-bare-metal-cloud-using-a-
  raspberry-pi-cluster-with-maas/5845

  However, using the same procedure on the same hardware but selecting
  ubuntu 21.10 always fails. This appears to be caused by curtin being
  unable to see the USB disk device /dev/sda to which we are deploying.

  The same issue occurs with all versions of the kernel available for
  21.10.

  I enclose the log files downloaded from MAAS.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1964113

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

Title:
  USB camera missing display name

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  integrated laptop cameras and USB cameras have a display name, which makes 
them easy to select the correct camera.

  This display name is replaced by a generic "Video Capture X" as of
  5.13.0-28-generic, including the current 5.13.0-30-generic.

   cat /proc/version_signature 
  Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Video Capture 5 (usb-:00:14.0-1):
/dev/video2
/dev/video3

  Video Capture 3 (usb-:00:14.0-8):
/dev/video0
/dev/video1

   cat /proc/version_signature 
  Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Huddly IQ (usb-:00:14.0-1):
/dev/video0
/dev/video1

  Integrated Camera: Integrated C (usb-:00:14.0-8):
/dev/video2
/dev/video3

  This display name is rendered by eg Cheese and Jitsi to allow camera
  selection by name.

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


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

[Kernel-packages] [Bug 1964114] [NEW] network interface is removed after latest update (pi4)

[fredbcode]

Public bug reported:

Hello,

I have a image disk of ubuntu 20.04 with the previous package version -> 
working well 
When I restore this image at start there is an upgrade and when I reboot eth0 
is gone (configured with netplan) 

I can easily reproduce

Restore image, start, just wait for upgrade, reboot

thanks

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

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

Title:
  network interface is removed after latest update (pi4)

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  Hello,

  I have a image disk of ubuntu 20.04 with the previous package version -> 
working well 
  When I restore this image at start there is an upgrade and when I reboot eth0 
is gone (configured with netplan) 

  I can easily reproduce

  Restore image, start, just wait for upgrade, reboot

  thanks

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


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

[Kernel-packages] [Bug 1964113] Re: USB camera missing display name

[Kacper Wysocki]

** Attachment added: "lspci -vnvn"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964113/+attachment/5566978/+files/lspci-vnvn.log

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

Title:
  USB camera missing display name

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  integrated laptop cameras and USB cameras have a display name, which makes 
them easy to select the correct camera.

  This display name is replaced by a generic "Video Capture X" as of
  5.13.0-28-generic, including the current 5.13.0-30-generic.

   cat /proc/version_signature 
  Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Video Capture 5 (usb-:00:14.0-1):
/dev/video2
/dev/video3

  Video Capture 3 (usb-:00:14.0-8):
/dev/video0
/dev/video1

   cat /proc/version_signature 
  Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Huddly IQ (usb-:00:14.0-1):
/dev/video0
/dev/video1

  Integrated Camera: Integrated C (usb-:00:14.0-8):
/dev/video2
/dev/video3

  This display name is rendered by eg Cheese and Jitsi to allow camera
  selection by name.

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


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

[Kernel-packages] [Bug 1964113] Re: USB camera missing display name

[Kacper Wysocki]

** Attachment added: "lsusb -v"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964113/+attachment/5566977/+files/lsusb-v.log

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

Title:
  USB camera missing display name

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  integrated laptop cameras and USB cameras have a display name, which makes 
them easy to select the correct camera.

  This display name is replaced by a generic "Video Capture X" as of
  5.13.0-28-generic, including the current 5.13.0-30-generic.

   cat /proc/version_signature 
  Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Video Capture 5 (usb-:00:14.0-1):
/dev/video2
/dev/video3

  Video Capture 3 (usb-:00:14.0-8):
/dev/video0
/dev/video1

   cat /proc/version_signature 
  Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Huddly IQ (usb-:00:14.0-1):
/dev/video0
/dev/video1

  Integrated Camera: Integrated C (usb-:00:14.0-8):
/dev/video2
/dev/video3

  This display name is rendered by eg Cheese and Jitsi to allow camera
  selection by name.

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


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

[Kernel-packages] [Bug 1964113] [NEW] USB camera missing display name

[Kacper Wysocki]

Public bug reported:

Hi,
integrated laptop cameras and USB cameras have a display name, which makes them 
easy to select the correct camera.

This display name is replaced by a generic "Video Capture X" as of
5.13.0-28-generic, including the current 5.13.0-30-generic.

 cat /proc/version_signature 
Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19

 v4l-ctl --list-devices
Video Capture 5 (usb-:00:14.0-1):
/dev/video2
/dev/video3

Video Capture 3 (usb-:00:14.0-8):
/dev/video0
/dev/video1

 cat /proc/version_signature 
Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19

 v4l-ctl --list-devices
Huddly IQ (usb-:00:14.0-1):
/dev/video0
/dev/video1

Integrated Camera: Integrated C (usb-:00:14.0-8):
/dev/video2
/dev/video3

This display name is rendered by eg Cheese and Jitsi to allow camera
selection by name.

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

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

Title:
  USB camera missing display name

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,
  integrated laptop cameras and USB cameras have a display name, which makes 
them easy to select the correct camera.

  This display name is replaced by a generic "Video Capture X" as of
  5.13.0-28-generic, including the current 5.13.0-30-generic.

   cat /proc/version_signature 
  Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Video Capture 5 (usb-:00:14.0-1):
/dev/video2
/dev/video3

  Video Capture 3 (usb-:00:14.0-8):
/dev/video0
/dev/video1

   cat /proc/version_signature 
  Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19

   v4l-ctl --list-devices
  Huddly IQ (usb-:00:14.0-1):
/dev/video0
/dev/video1

  Integrated Camera: Integrated C (usb-:00:14.0-8):
/dev/video2
/dev/video3

  This display name is rendered by eg Cheese and Jitsi to allow camera
  selection by name.

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


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

[Kernel-packages] [Bug 1963088] Re: Add support for TPM

[Dimitri John Ledkov]

https://lists.ubuntu.com/archives/kernel-team/2022-March/128510.html

** Changed in: linux-kvm (Ubuntu)
   Status: New => In Progress

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

Title:
  Add support for TPM

Status in linux-kvm package in Ubuntu:
  In Progress

Bug description:
  LXD, libvirt, openstack support launching qemu-kvm instances with TIS
  and CRB tpm's passed through from the host.

  linux-kvm currently is configured without TCG_TPM meaning it doesn't
  allow loading TPM modules, nor does it support exposing measurements,
  and thus allowing to use TPM backed FDE.

  Update config to enable TCG_TPM and compile TIS and CRB tpm's as
  modules. This still keeps linux-kvm fairly minimal in size, and yet
  able to support modern measured boot.

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


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

[Kernel-packages] [Bug 1964110] [NEW] Touchpad not detecting thinkpad

[Aritra Bose]

Public bug reported:

I use Thinkpad T14 Gen 1 with ubuntu 20.04 LTS. My touchpad was working
before. Now I stopped using it for a few weeks and now when I am trying
to switch it on, it is not detected.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  8 11:39:18 2022
InstallationDate: Installed on 2021-10-21 (137 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Touchpad not detecting thinkpad

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

Bug description:
  I use Thinkpad T14 Gen 1 with ubuntu 20.04 LTS. My touchpad was
  working before. Now I stopped using it for a few weeks and now when I
  am trying to switch it on, it is not detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  8 11:39:18 2022
  InstallationDate: Installed on 2021-10-21 (137 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1955689] Re: Add Bluetooth support for Qualcomm WCN6856

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => 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/1955689

Title:
  Add Bluetooth support for Qualcomm WCN6856

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  WCN6856 Bluetooth doesn't work.

  [Fix]
  Backport firmware blobs and driver support to make it work by loading
  correct firmwares.
   
  [Test]
  Bluetooth scanning and pairing work, and continue to do so after several
  suspend/resume cycles.

  [Where problems could occur]
  The upstream version of btusb_generate_qca_nvm_name() adds several
  missing le*_to_cpu() macros, so if this device was ever used on a Big
  Endian system, this is a behavioral change.

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


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

[Kernel-packages] [Bug 1951873] Re: Enable arm64 nitro enclaves

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.15.0-1002.4

---
linux-aws (5.15.0-1002.4) jammy; urgency=medium

  * jammy/linux-aws: 5.15.0-1002.4 -proposed tracker (LP: #1960330)

  * Miscellaneous Ubuntu changes
- [Config] aws: toolchain version update
- [Config] aws: CONFIG_SYSFB_SIMPLEFB=y

  [ Ubuntu: 5.15.0-22.22 ]

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

  [ Ubuntu: 5.15.0-21.21 ]

  * jammy/linux: 5.15.0-21.21 -proposed tracker (LP: #1960211)
  * Miscellaneous Ubuntu changes
- [packaging] unhook lowlatency flavours from the build

  [ Ubuntu: 5.15.0-20.20 ]

  * jammy/linux: 5.15.0-20.20 -proposed tracker (LP: #1959881)
  * Jammy update: v5.15.19 upstream stable release (LP: #1959879)
- can: m_can: m_can_fifo_{read,write}: don't read or write from/to FIFO if
  length is 0
- net: sfp: ignore disabled SFP node
- net: stmmac: configure PTP clock source prior to PTP initialization
- net: stmmac: skip only stmmac_ptp_register when resume from suspend
- ARM: 9179/1: uaccess: avoid alignment faults in
  copy_[from|to]_kernel_nofault
- ARM: 9180/1: Thumb2: align ALT_UP() sections in modules sufficiently
- KVM: arm64: Use shadow SPSR_EL1 when injecting exceptions on !VHE
- s390/hypfs: include z/VM guests with access control group set
- s390/nmi: handle guarded storage validity failures for KVM guests
- s390/nmi: handle vector validity failures for KVM guests
- bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
- powerpc32/bpf: Fix codegen for bpf-to-bpf calls
- powerpc/bpf: Update ldimm64 instructions during extra pass
- scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
  devices
- udf: Restore i_lenAlloc when inode expansion fails
- udf: Fix NULL ptr deref when converting from inline format
- efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
- PM: wakeup: simplify the output logic of pm_show_wakelocks()
- tracing/histogram: Fix a potential memory leak for kstrdup()
- tracing: Don't inc err_log entry count if entry allocation fails
- ceph: properly put ceph_string reference after async create attempt
- ceph: set pool_ns in new inode layout for async creates
- fsnotify: fix fsnotify hooks in pseudo filesystems
- Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
- psi: Fix uaf issue when psi trigger is destroyed while being polled
- powerpc/audit: Fix syscall_get_arch()
- perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
- perf/x86/intel: Add a quirk for the calculation of the number of counters 
on
  Alder Lake
- drm/etnaviv: relax submit size limits
- drm/atomic: Add the crtc to affected crtc only if uapi.enable = true
- drm/amd/display: Fix FP start/end for dcn30_internal_validate_bw.
- KVM: LAPIC: Also cancel preemption timer during SET_LAPIC
- KVM: SVM: Never reject emulation due to SMAP errata for !SEV guests
- KVM: SVM: Don't intercept #GP for SEV guests
- KVM: x86: nSVM: skip eax alignment check for non-SVM instructions
- KVM: x86: Forcibly leave nested virt when SMM state is toggled
- KVM: x86: Keep MSR_IA32_XSS unchanged for INIT
- KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
- KVM: x86: Sync the states size with the XCR0/IA32_XSS at, any time
- KVM: PPC: Book3S HV Nested: Fix nested HFSCR being clobbered with multiple
  vCPUs
- dm: revert partial fix for redundant bio-based IO accounting
- block: add bio_start_io_acct_time() to control start_time
- dm: properly fix redundant bio-based IO accounting
- serial: pl011: Fix incorrect rs485 RTS polarity on set_mctrl
- serial: 8250: of: Fix mapped region size when using reg-offset property
- serial: stm32: fix software flow control transfer
- tty: n_gsm: fix SW flow control encoding/handling
- tty: Partially revert the removal of the Cyclades public API
- tty: Add support for Brainboxes UC cards.
- kbuild: remove include/linux/cyclades.h from header file check
- usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
- usb: xhci-plat: fix crash when suspend if remote wake enable
- usb: common: ulpi: Fix crash in ulpi_match()
- usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
- usb: cdnsp: Fix segmentation fault in cdns_lost_power function
- usb: dwc3: xilinx: Skip resets and USB3 register settings for USB2.0 mode
- usb: dwc3: xilinx: Fix error handling when getting USB3 PHY
- USB: core: Fix hang in usb_kill_urb by adding memory barriers
- usb: typec: tcpci: don't touch CC line if it's Vconn source
- usb: typec: tcpm: Do not disconnect while receiving VBUS off
- usb: typec: tcpm: Do not disconnect when receiving VSAFE0V
- ucsi_ccg: Check DEV_INT bit only when starting CCG4
- mm, kasan: use compare-exchange operation to set 

[Kernel-packages] [Bug 1951111] Re: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for
  Ubuntu 22.04

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The purpose of this bug is to track the incremental patches needed in
  Ubuntu 22.04 for the Broadcom Emulex FC HBA lpfc driver that are
  committed to the 5.16 upstream kernel and not part of the 5.15 kernel
  that 22.04 is rebased to.

  Please integrate the following patches from the 5.16 kernel per James
  Smart the lpfc maintainter.

  James Smart
  Fri, Nov 12, 2:31 PM (4 days ago)
  to me, Dick, Justin, Teresa

  I would argue to take all of the patches in the following list
  (14.0.0.2 & 14.0.0.3 & a mbx cmd failure issue)

  -- james

  
  Applied to 5.16/scsi-queue, thanks!

  [1/8] lpfc: Revert LOG_TRACE_EVENT back to LOG_INIT prior to 
driver_resource_setup
  https://git.kernel.org/mkp/scsi/c/a516074c2026
  [2/8] lpfc: Wait for successful restart of SLI3 adapter during host sg_reset
  https://git.kernel.org/mkp/scsi/c/d305c253af69
  [3/8] lpfc: Correct sysfs reporting of loop support after SFP status change
  https://git.kernel.org/mkp/scsi/c/7a1dda943630
  [4/8] lpfc: Fix use-after-free in lpfc_unreg_rpi() routine
  https://git.kernel.org/mkp/scsi/c/79b20beccea3
  [5/8] lpfc: Allow PLOGI retry if previous PLOGI was aborted
  https://git.kernel.org/mkp/scsi/c/15af02d8a585
  [6/8] lpfc: Fix link down processing to address NULL pointer dereference
  https://git.kernel.org/mkp/scsi/c/1854f53ccd88
  [7/8] lpfc: Allow fabric node recovery if recovery is in progress before 
devloss
  https://git.kernel.org/mkp/scsi/c/af984c87293b
  [8/8] lpfc: Update lpfc version to 14.0.0.3
  https://git.kernel.org/mkp/scsi/c/83c3a7beaef7

  Applied to 5.16/scsi-queue, thanks!

  [1/1] lpfc: Fix mailbox command failure during driver initialization
  https://git.kernel.org/mkp/scsi/c/efe1dc571a5b

  
  Applied to 5.16/scsi-queue, thanks!

  [01/14] lpfc: Fix list_add corruption in lpfc_drain_txq
  https://git.kernel.org/mkp/scsi/c/99154581b05c
  [02/14] lpfc: Don't release final kref on Fport node while ABTS outstanding
  https://git.kernel.org/mkp/scsi/c/982fc3965d13
  [03/14] lpfc: Fix premature rpi release for unsolicited TPLS and LS_RJT
  https://git.kernel.org/mkp/scsi/c/20d2279f90ce
  [04/14] lpfc: Fix hang on unload due to stuck fport node
  https://git.kernel.org/mkp/scsi/c/88f7702984e6
  [05/14] lpfc: Fix rediscovery of tape device after issue lip
  https://git.kernel.org/mkp/scsi/c/3a874488d2e9
  [06/14] lpfc: Don't remove ndlp on PRLI errors in P2P mode
  https://git.kernel.org/mkp/scsi/c/a864ee709bc0
  [07/14] lpfc: Fix NVME I/O failover to non-optimized path
  https://git.kernel.org/mkp/scsi/c/b507357f7917
  [08/14] lpfc: Fix FCP I/O flush functionality for TMF routines
  https://git.kernel.org/mkp/scsi/c/cd8a36a90bab
  [09/14] lpfc: Fix EEH support for NVME I/O
  https://git.kernel.org/mkp/scsi/c/25ac2c970be3
  [10/14] lpfc: Adjust bytes received vales during cmf timer interval
  https://git.kernel.org/mkp/scsi/c/d5ac69b332d8
  [11/14] lpfc: Fix I/O block after enabling managed congestion mode
  https://git.kernel.org/mkp/scsi/c/3ea998cbf9e7
  [12/14] lpfc: Zero CGN stats only during initial driver load and stat reset
  https://git.kernel.org/mkp/scsi/c/afd63fa51149
  [13/14] lpfc: Improve PBDE checks during SGL processing
  https://git.kernel.org/mkp/scsi/c/315b3fd13521
  [14/14] lpfc: Update lpfc version to 14.0.0.2
  https://git.kernel.org/mkp/scsi/c/0d6b26795bd2

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


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

[Kernel-packages] [Bug 1955613] Re: Add basic Wifi support for Qualcomm WCN6856

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => 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/1955613

Title:
  Add basic Wifi support for Qualcomm WCN6856

Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux-firmware source package in Jammy:
  Fix Released
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Qualcomm WCN6856 doens't work.

  [Fix]
  Backport missing bits to make Wifi 5 work. Wifi 6 support is not in the
  scope of this SRU.

  [Test]
  The system can connect to Wifi. Wifi still works after several rounds of
  suspend/resume cycles. 

  [Where problems could occur]
  The change is limited to ath11k, which is also the only user of mhi bus,
  so the scope of risk is limited. Let alone it never worked before, so
  there's not much room to go wrong.

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

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

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-21.10 series:
  Fix Released
Status in kunpeng920 ubuntu-22.04 series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification
  =

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

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

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

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

  == Original Bug Description ==

  [Bug Description]

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

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

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

  [Expected Results]
  no fail
  [Reproducibility]
  100%

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

  [Resolution]
  this following patches will solve this bug.

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

  crypto: hisilicon - add ZIP device using mode parameter

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

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

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

  crypto: hisilicon/hpre - register HPRE device to uacce

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

  crypto: hisilicon/sec - register SEC device to uacce

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


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

[Kernel-packages] [Bug 1953008] Re: Support USB4 DP alt mode for AMD Yellow Carp graphics card

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Support USB4 DP alt mode for AMD Yellow Carp graphics card

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

Bug description:
  [SRU Justification]

  [Impact]

  USB4 DP alt mode not available on AMD yellow carp.

  [Fix]

  Several fixing commits from upstream, inclusive of one titled
  "drm/amd/display: Fixup previous PSR policy commit" sauced commit to
  fix backport problems for commit 9470620e99e9 ("drm/amd/display: Enable
  PSR by default on newer DCN").

  This also depends on the firmware updates.

  [Test Case]

  Plug an external monitor with USB Type-C input function to AMD RMB CRB
  (which has yellow carp) usbc0 and usbc1.

  [Where problems could occur]

  The patches revealed multiple dmub firmware versions were skipped. This
  might introduce incompatibilities between driver code and the firmware.

  == linux-firmware SRU ==

  [Impact]

  Need new firmware to enable USB4 DP alt mode for AMD yellow carp.

  [Fix]

  Already-in-upstream commit 581f8a3aae02 ("amdgpu: update yellow carp
  dmcub firmware") to be backported.

  [Test Case]

  Need also kernel driver fixes to verify.

  [Where problems could occur]

  This introduces new features required both kernel driver and firmware
  updates, the firmware part might cause instability or so.

  == original bug report ==

  Required linux-firmware:
  * 581f8a3a amdgpu: update yellow carp dmcub firmware
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1304 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1304 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+X173
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-12-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.

   enp1s0f0  no wireless extensions.
  MachineType: AMD LilacKD-RMB
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1008-oem 
root=UUID=82b889f1-11ce-4ecf-99e7-65c895cdc771 ro automatic-oem-config
  ProcVersionSignature: Ubuntu 5.14.0-1008.8-oem 5.14.17
  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-1008-oem N/A
   linux-backports-modules-5.14.0-1008-oem  N/A
   linux-firmware   1.187.20+staging.35
  RfKill:

  Tags: third-party-packages focal
  Uname: Linux 5.14.0-1008-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: 09/15/2021
  dmi.bios.release: 190.196
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: RRL0080C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: LilacKD-RMB
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrRRL0080C:bd09/15/2021:br190.196:svnAMD:pnLilacKD-RMB:pvr1:rvnAMD:rnLilacKD-RMB:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789:
  dmi.product.family: Rembrandt
  dmi.product.name: LilacKD-RMB
  dmi.product.sku: 123456789
  dmi.product.version: 1
  dmi.sys.vendor: AMD

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1954611] Re: Let VMD follow host bridge PCIe settings

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Let VMD follow host bridge PCIe settings

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
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]
  Some platforms have endless AER message floods kernel log, slows done
  disk I/O.

  [Fix]
  Honor BIOS settings to disable AER for Intel VMD.

  [Test]
  Use dmesg to check kernel log, no more AER message since AER is
  disabled.

  [Where problem could occur]
  The patch copies PCIe settings from host bridge, so some PCIe features
  will be disabled as a result. This may not be desirable for some users.

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


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

[Kernel-packages] [Bug 1951563] Re: alsa/sdw: add sdw audio machine driver for several ADL machines

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

Title:
  alsa/sdw: add sdw audio machine driver for several ADL machines

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

Bug description:
  [Impact]
  In the Dell oem project, we need to enable the sdw audio on several
  ADL machines, without these patches, the audio can't work at all.

  [Fix]
  Backport some patches from upstream, this adds the audio machine
  drivers for those adl platforms.

  [Test]
  Booting the patched kernel, open the gnome-sound-setting, we could
  see the speaker and microphone, plug headset, the headphone and
  headset-mic all work well.

  [Where problems could occur]
  This add some machine drivers for sdw audio, if it could introduce
  regression, it will be on the Dell previous generation machines which
  has sdw audio, it could make the audio on those machines not work. But
  this possibility is very low, we already tested the patches on those
  machines.

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


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

[Kernel-packages] [Bug 1956407] Re: Add missing BT ID for Qualcomm WCN6856

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

Title:
  Add missing BT ID for Qualcomm WCN6856

Status in linux package in Ubuntu:
  Fix Released
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 Jammy:
  Fix Released
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]
  WCN6856 Bluetooth doesn't work.

  [Fix]
  Add one more ID for BT.

  [Test]
  Verified by our engineers and Dell on some Dell platforms with WCN6856 card.

  [Where problems could occur]
  Adding ID doesn't affect old systems.

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


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

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => 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/1927808

Title:
  rtw88_8821ce causes freeze

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
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:
  Won't Fix
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Impish:
  Confirmed
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:
  Fix Released
Status in linux-oem-5.13 source package in Jammy:
  Invalid
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  smartpqi: Update 20.04.4 to latest kernel.org patch level

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

Bug description:
  SRU Justification:

  Impact:
  Update the smartpqi driver with latest kernel.org patches from git repo:
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  These patches will align the Canonical smartpqi driver with kernel.org

  
  Fix:
  This is targeted at 5.13 for 20.04.4 HWE

  Here is a list of patches that need applied to 20.04.4 to bring the
  smartpqi up to date with kernel.org.

  
  605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055
  80982656b78e scsi: smartpqi: Add 3252-8i PCI id
  d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers
  987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild
  28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs
  4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices
  be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation
  6ce1ddf53252 scsi: smartpqi: Update LUN reset handler
  5d1f03e6f49a scsi: smartpqi: Capture controller reason codes
  9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump
  819225b03dc7 scsi: smartpqi: Update device removal management
  5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array 
member

  These patches should all be upstream as of 5.16.

  Testcase:
  kdump tests.
  fio performance testing to demonstrate no performance regressions.

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


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

[Kernel-packages] [Bug 1956454] Re: Enable audio mute LED and mic mute LED on a new HP laptop

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

** Changed in: linux (Ubuntu Jammy)
   Status: Confirmed => 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/1956454

Title:
  Enable audio mute LED and mic mute LED on a new HP laptop

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

Bug description:
  [Impact]
  Audio mute LED and mic mute LED are not working on a new HP laptop.

  [Fix]
  Use another audio quirk to enable the feature.

  [Test] 
  With the patch applied, both LEDs start working.

  [Where problems could occur]
  This fix is limit to one device, so other devices are totally
  unaffected.

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.15.0-1001.2

---
linux-azure (5.15.0-1001.2) jammy; urgency=medium

  * jammy/linux-azure: 5.15.0-1001.2 -proposed tracker (LP: #1960267)

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

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

  * Miscellaneous Ubuntu changes
- [Config] azure: CONFIG_FB_EFI=y for arm64
- [Packaging] azure: Update dependency of pahole / dwarves

  [ Ubuntu: 5.15.0-21.21 ]

  * jammy/linux: 5.15.0-21.21 -proposed tracker (LP: #1960211)
  * Miscellaneous Ubuntu changes
- [packaging] unhook lowlatency flavours from the build

  [ Ubuntu: 5.15.0-20.20 ]

  * jammy/linux: 5.15.0-20.20 -proposed tracker (LP: #1959881)
  * Jammy update: v5.15.19 upstream stable release (LP: #1959879)
- can: m_can: m_can_fifo_{read,write}: don't read or write from/to FIFO if
  length is 0
- net: sfp: ignore disabled SFP node
- net: stmmac: configure PTP clock source prior to PTP initialization
- net: stmmac: skip only stmmac_ptp_register when resume from suspend
- ARM: 9179/1: uaccess: avoid alignment faults in
  copy_[from|to]_kernel_nofault
- ARM: 9180/1: Thumb2: align ALT_UP() sections in modules sufficiently
- KVM: arm64: Use shadow SPSR_EL1 when injecting exceptions on !VHE
- s390/hypfs: include z/VM guests with access control group set
- s390/nmi: handle guarded storage validity failures for KVM guests
- s390/nmi: handle vector validity failures for KVM guests
- bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
- powerpc32/bpf: Fix codegen for bpf-to-bpf calls
- powerpc/bpf: Update ldimm64 instructions during extra pass
- scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
  devices
- udf: Restore i_lenAlloc when inode expansion fails
- udf: Fix NULL ptr deref when converting from inline format
- efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
- PM: wakeup: simplify the output logic of pm_show_wakelocks()
- tracing/histogram: Fix a potential memory leak for kstrdup()
- tracing: Don't inc err_log entry count if entry allocation fails
- ceph: properly put ceph_string reference after async create attempt
- ceph: set pool_ns in new inode layout for async creates
- fsnotify: fix fsnotify hooks in pseudo filesystems
- Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
- psi: Fix uaf issue when psi trigger is destroyed while being polled
- powerpc/audit: Fix syscall_get_arch()
- perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
- perf/x86/intel: Add a quirk for the calculation of the number of counters 
on
  Alder Lake
- drm/etnaviv: relax submit size limits
- drm/atomic: Add the crtc to affected crtc only if uapi.enable = true
- drm/amd/display: Fix FP start/end for dcn30_internal_validate_bw.
- KVM: LAPIC: Also cancel preemption timer during SET_LAPIC
- KVM: SVM: Never reject emulation due to SMAP errata for !SEV guests
- KVM: SVM: Don't intercept #GP for SEV guests
- KVM: x86: nSVM: skip eax alignment check for non-SVM instructions
- KVM: x86: Forcibly leave nested virt when SMM state is toggled
- KVM: x86: Keep MSR_IA32_XSS unchanged for INIT
- KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
- KVM: x86: Sync the states size with the XCR0/IA32_XSS at, any time
- KVM: PPC: Book3S HV Nested: Fix nested HFSCR being clobbered with multiple
  vCPUs
- dm: revert partial fix for redundant bio-based IO accounting
- block: add bio_start_io_acct_time() to control start_time
- dm: properly fix redundant bio-based IO accounting
- serial: pl011: Fix incorrect rs485 RTS polarity on set_mctrl
- serial: 8250: of: Fix mapped region size when using reg-offset property
- serial: stm32: fix software flow control transfer
- tty: n_gsm: fix SW flow control encoding/handling
- tty: Partially revert the removal of the Cyclades public API
- tty: Add support for Brainboxes UC cards.
- kbuild: remove include/linux/cyclades.h from header file check
- usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
- usb: xhci-plat: fix crash when suspend if remote wake enable
- usb: common: ulpi: Fix crash in ulpi_match()
- usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
- usb: cdnsp: Fix segmentation fault in cdns_lost_power function
- usb: dwc3: xilinx: Skip resets and USB3 register settings for USB2.0 mode
- usb: dwc3: xilinx: Fix error handling when getting USB3 PHY
- USB: core: Fix hang in usb_kill_urb by adding memory barriers
- usb: typec: tcpci: don't touch CC line if it's Vconn source
- usb: typec: tcpm: Do not disconnect while receiving VBUS 

[Kernel-packages] [Bug 1956926] Re: Jammy update: v5.15.13 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Jammy update: v5.15.13 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

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

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

Bug description:
  [SRU Justification]

  [Impact]

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

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

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

  [Fix]

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

  [Test Case]

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

  [Where problems could occur]

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

  [Other Info]

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

  == original bug report ==

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

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

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

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

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

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

[Kernel-packages] [Bug 1957790] Re: NVIDIA CVE-2022-{21813|21814}

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.103.01-0ubuntu2

---
nvidia-graphics-drivers-470-server (470.103.01-0ubuntu2) jammy; urgency=medium

  * debian/rules.defs:
- Add support for video ABI 25.

 -- Alberto Milone   Wed, 23 Feb 2022
18:05:57 +0100

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

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

Title:
  NVIDIA CVE-2022-{21813|21814}

Status in fabric-manager-450 package in Ubuntu:
  New
Status in fabric-manager-470 package in Ubuntu:
  New
Status in libnvidia-nscq-450 package in Ubuntu:
  New
Status in libnvidia-nscq-470 package in Ubuntu:
  New
Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  New
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-470 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-470 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Bionic:
  New
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-470 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-470 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Focal:
  New
Status in fabric-manager-450 source package in Impish:
  Fix Released
Status in fabric-manager-470 source package in Impish:
  Fix Released
Status in libnvidia-nscq-450 source package in Impish:
  Fix Released
Status in libnvidia-nscq-470 source package in Impish:
  Fix Released
Status in linux-restricted-modules source package in Impish:
  New
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470 source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Released
Status in nvidia-graphics-drivers-495 source package in Impish:
  New

Bug description:
  As per the subject, the update includes fixes for the following CVEs:

  CVE-2022-21813
  CVE-2022-21814

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/1957790/+subscriptions


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

[Kernel-packages] [Bug 1958418] Re: Jammy update: v5.15.15 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Jammy update: v5.15.15 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.15
  staging: greybus: fix stack size warning with UBSAN
  drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
  staging: wlan-ng: Avoid bitwise vs logical OR warning in 
hfa384x_usb_throttlefn()
  media: Revert "media: uvcvideo: Set unique vdev name based in type"
  platform/x86/intel: hid: add quirk to support Surface Go 3
  random: fix crash on multiple early calls to add_bootloader_randomness()
  random: fix data race on crng init time
  random: fix data race on crng_node_pool
  can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
  can: isotp: convert struct tpcon::{idx,len} to unsigned int
  can: gs_usb: fix use of uninitialized variable, detach device on reception of 
invalid USB data
  mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
  veth: Do not record rx queue hint in veth_xmit
  Bluetooth: btbcm: disable read tx power for MacBook Air 8,1 and 8,2
  Bluetooth: btbcm: disable read tx power for some Macs with the T2 Security 
chip
  Bluetooth: add quirk disabling LE Read Transmit Power
  mmc: sdhci-pci: Add PCI ID for Intel ADL
  ath11k: Fix buffer overflow when scanning with extraie
  USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
  USB: core: Fix bug in resuming hub's handling of wakeup requests
  ARM: dts: exynos: Fix BCM4330 Bluetooth reset polarity in I9100
  Bluetooth: bfusb: fix division by zero in send path
  Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0
  Bluetooth: btintel: Fix broken LED quirk for legacy ROM devices
  Bluetooth: btusb: Add support for Foxconn MT7922A
  Bluetooth: btusb: Add two more Bluetooth parts for WCN6855
  Bluetooth: btusb: Add one more Bluetooth part for WCN6855
  fget: clarify and improve __fget_files() implementation
  Bluetooth: btusb: Add the new support IDs for WCN6855
  Bluetooth: btusb: Add one more Bluetooth part for the Realtek RTL8852AE
  Bluetooth: btusb: enable Mediatek to support AOSP extension
  Bluetooth: btusb: fix memory leak in btusb_mtk_submit_wmt_recv_urb()
  Bbluetooth: btusb: Add another Bluetooth part for Realtek 8852AE
  Bluetooth: btusb: Add support for IMC Networks Mediatek Chip(MT7921)
  Bluetooth: btusb: Add the new support ID for Realtek RTL8852A
  Bluetooth: btusb: Add protocol for MediaTek bluetooth devices(MT7922)
  bpf: Fix out of bounds access from invalid *_or_null type verification
  staging: r8188eu: switch the led off during deinit
  workqueue: Fix unbind_workers() VS wq_worker_running() race
  s390/kexec: handle R_390_PLT32DBL rela in arch_kexec_apply_relocations_add()

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


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

[Kernel-packages] [Bug 1957882] Re: Jammy update: v5.15.14 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Jammy update: v5.15.14 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

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


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

[Kernel-packages] [Bug 1958977] Re: Jammy update: v5.15.16 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Jammy update: v5.15.16 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.16
  mtd: fixup CFI on ixp4xx
  ALSA: hda/realtek: Re-order quirk entries for Lenovo
  ALSA: hda/realtek: Add quirk for Legion Y9000X 2020
  ALSA: hda/tegra: Fix Tegra194 HDA reset failure
  ALSA: hda: ALC287: Add Lenovo IdeaPad Slim 9i 14ITL5 speaker quirk
  ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after 
reboot from Windows
  ALSA: hda/realtek: Use ALC285_FIXUP_HP_GPIO_LED on another HP laptop
  ALSA: hda/realtek: Add speaker fixup for some Yoga 15ITL5 devices
  KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
  perf annotate: Avoid TUI crash when navigating in the annotation of recursive 
functions
  firmware: qemu_fw_cfg: fix kobject leak in probe error path
  firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
  firmware: qemu_fw_cfg: fix sysfs information leak
  rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
  media: uvcvideo: fix division by zero at stream start
  video: vga16fb: Only probe for EGA and VGA 16 color graphic cards
  9p: only copy valid iattrs in 9P2000.L setattr implementation
  remoteproc: qcom: pas: Add missing power-domain "mxc" for CDSP
  KVM: s390: Clarify SIGP orders versus STOP/RESTART
  KVM: x86: don't print when fail to read/write pv eoi memory
  KVM: x86: Register Processor Trace interrupt hook iff PT enabled in guest
  KVM: x86: Register perf callbacks after calling vendor's hardware_setup()
  perf: Protect perf_guest_cbs with RCU
  vfs: fs_context: fix up param length parsing in legacy_parse_param
  remoteproc: qcom: pil_info: Don't memcpy_toio more than is provided
  orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
  drm/amd/display: explicitly set is_dsc_supported to false before use
  devtmpfs regression fix: reconfigure on each mount

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


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

[Kernel-packages] [Bug 1959012] Re: MANA updates

[Launchpad Bug Tracker]

This bug was fixed in the package linux-azure - 5.15.0-1001.2

---
linux-azure (5.15.0-1001.2) jammy; urgency=medium

  * jammy/linux-azure: 5.15.0-1001.2 -proposed tracker (LP: #1960267)

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

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

  * Miscellaneous Ubuntu changes
- [Config] azure: CONFIG_FB_EFI=y for arm64
- [Packaging] azure: Update dependency of pahole / dwarves

  [ Ubuntu: 5.15.0-21.21 ]

  * jammy/linux: 5.15.0-21.21 -proposed tracker (LP: #1960211)
  * Miscellaneous Ubuntu changes
- [packaging] unhook lowlatency flavours from the build

  [ Ubuntu: 5.15.0-20.20 ]

  * jammy/linux: 5.15.0-20.20 -proposed tracker (LP: #1959881)
  * Jammy update: v5.15.19 upstream stable release (LP: #1959879)
- can: m_can: m_can_fifo_{read,write}: don't read or write from/to FIFO if
  length is 0
- net: sfp: ignore disabled SFP node
- net: stmmac: configure PTP clock source prior to PTP initialization
- net: stmmac: skip only stmmac_ptp_register when resume from suspend
- ARM: 9179/1: uaccess: avoid alignment faults in
  copy_[from|to]_kernel_nofault
- ARM: 9180/1: Thumb2: align ALT_UP() sections in modules sufficiently
- KVM: arm64: Use shadow SPSR_EL1 when injecting exceptions on !VHE
- s390/hypfs: include z/VM guests with access control group set
- s390/nmi: handle guarded storage validity failures for KVM guests
- s390/nmi: handle vector validity failures for KVM guests
- bpf: Guard against accessing NULL pt_regs in bpf_get_task_stack()
- powerpc32/bpf: Fix codegen for bpf-to-bpf calls
- powerpc/bpf: Update ldimm64 instructions during extra pass
- scsi: zfcp: Fix failed recovery on gone remote port with non-NPIV FCP
  devices
- udf: Restore i_lenAlloc when inode expansion fails
- udf: Fix NULL ptr deref when converting from inline format
- efi: runtime: avoid EFIv2 runtime services on Apple x86 machines
- PM: wakeup: simplify the output logic of pm_show_wakelocks()
- tracing/histogram: Fix a potential memory leak for kstrdup()
- tracing: Don't inc err_log entry count if entry allocation fails
- ceph: properly put ceph_string reference after async create attempt
- ceph: set pool_ns in new inode layout for async creates
- fsnotify: fix fsnotify hooks in pseudo filesystems
- Revert "KVM: SVM: avoid infinite loop on NPF from bad address"
- psi: Fix uaf issue when psi trigger is destroyed while being polled
- powerpc/audit: Fix syscall_get_arch()
- perf/x86/intel/uncore: Fix CAS_COUNT_WRITE issue for ICX
- perf/x86/intel: Add a quirk for the calculation of the number of counters 
on
  Alder Lake
- drm/etnaviv: relax submit size limits
- drm/atomic: Add the crtc to affected crtc only if uapi.enable = true
- drm/amd/display: Fix FP start/end for dcn30_internal_validate_bw.
- KVM: LAPIC: Also cancel preemption timer during SET_LAPIC
- KVM: SVM: Never reject emulation due to SMAP errata for !SEV guests
- KVM: SVM: Don't intercept #GP for SEV guests
- KVM: x86: nSVM: skip eax alignment check for non-SVM instructions
- KVM: x86: Forcibly leave nested virt when SMM state is toggled
- KVM: x86: Keep MSR_IA32_XSS unchanged for INIT
- KVM: x86: Update vCPU's runtime CPUID on write to MSR_IA32_XSS
- KVM: x86: Sync the states size with the XCR0/IA32_XSS at, any time
- KVM: PPC: Book3S HV Nested: Fix nested HFSCR being clobbered with multiple
  vCPUs
- dm: revert partial fix for redundant bio-based IO accounting
- block: add bio_start_io_acct_time() to control start_time
- dm: properly fix redundant bio-based IO accounting
- serial: pl011: Fix incorrect rs485 RTS polarity on set_mctrl
- serial: 8250: of: Fix mapped region size when using reg-offset property
- serial: stm32: fix software flow control transfer
- tty: n_gsm: fix SW flow control encoding/handling
- tty: Partially revert the removal of the Cyclades public API
- tty: Add support for Brainboxes UC cards.
- kbuild: remove include/linux/cyclades.h from header file check
- usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
- usb: xhci-plat: fix crash when suspend if remote wake enable
- usb: common: ulpi: Fix crash in ulpi_match()
- usb: gadget: f_sourcesink: Fix isoc transfer for USB_SPEED_SUPER_PLUS
- usb: cdnsp: Fix segmentation fault in cdns_lost_power function
- usb: dwc3: xilinx: Skip resets and USB3 register settings for USB2.0 mode
- usb: dwc3: xilinx: Fix error handling when getting USB3 PHY
- USB: core: Fix hang in usb_kill_urb by adding memory barriers
- usb: typec: tcpci: don't touch CC line if it's Vconn source
- usb: typec: tcpm: Do not disconnect while receiving VBUS 

[Kernel-packages] [Bug 1959879] Re: Jammy update: v5.15.19 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Jammy update: v5.15.19 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.19
  mtd: rawnand: mpc5121: Remove unused variable in ads5121_select_chip()
  block: Fix wrong offset in bio_truncate()
  fsnotify: invalidate dcache before IN_DELETE event
  usr/include/Makefile: add linux/nfc.h to the compile-test coverage
  usb: dwc3: xilinx: fix uninitialized return value
  psi: fix "defined but not used" warnings when CONFIG_PROC_FS=n
  psi: fix "no previous prototype" warnings when CONFIG_CGROUPS=n
  perf/core: Fix cgroup event list management
  dt-bindings: can: tcan4x5x: fix mram-cfg RX FIFO config
  irqchip/realtek-rtl: Fix off-by-one in routing
  irqchip/realtek-rtl: Map control data to virq
  Bluetooth: refactor malicious adv data check
  net: bridge: vlan: fix memory leak in __allowed_ingress
  ipv4: remove sparse error in ip_neigh_gw4()
  ipv4: tcp: send zero IPID in SYNACK messages
  ipv4: raw: lock the socket in raw_bind()
  net: bridge: vlan: fix single net device option dumping
  Revert "ipv6: Honor all IPv6 PIO Valid Lifetime values"
  gve: Fix GFP flags when allocing pages
  ceph: put the requests/sessions when it fails to alloc memory
  KVM: selftests: Don't skip L2's VMCALL in SMM test for SVM guest
  Revert "drm/ast: Support 1600x900 with 108MHz PCLK"
  sch_htb: Fail on unsupported parameters when offload is requested
  net: hns3: handle empty unknown interrupt for VF
  net: cpsw: Properly initialise struct page_pool_params
  yam: fix a memory leak in yam_siocdevprivate()
  drm/msm/a6xx: Add missing suspend_count increment
  drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc
  drm/msm/hdmi: Fix missing put_device() call in msm_hdmi_get_phy
  can: tcan4x5x: regmap: fix max register value
  video: hyperv_fb: Fix validation of screen resolution
  net/smc: Transitional solution for clcsock race issue
  ibmvnic: don't spin in tasklet
  ibmvnic: init ->running_cap_crqs early
  ibmvnic: Allow extra failures before disabling
  ipv4: fix ip option filtering for locally generated fragments
  powerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI 
is pending
  hwmon: (adt7470) Prevent divide by zero in adt7470_fan_write()
  hwmon: (lm90) Fix sysfs and udev notifications
  hwmon: (lm90) Mark alert as broken for MAX6654
  hwmon: (lm90) Re-enable interrupts after alert clears
  Drivers: hv: balloon: account for vmbus packet header in max_pkt_size
  io_uring: fix bug in slow unregistering of nodes
  efi/libstub: arm64: Fix image check alignment at entry
  rxrpc: Adjust retransmission backoff
  octeontx2-pf: Forward error codes to VF
  octeontx2-af: cn10k: Do not enable RPM loopback for LPC interfaces
  octeontx2-af: Increase link credit restore polling timeout
  octeontx2-af: verify CQ context updates
  octeontx2-pf: cn10k: Ensure valid pointers are freed to aura
  octeontx2-af: Retry until RVU block reset complete
  octeontx2-af: Fix LBK backpressure id count
  octeontx2-af: Do not fixup all VF action entries
  phylib: fix potential use-after-free
  net: stmmac: dwmac-visconti: Fix clock configuration for RMII mode
  net: stmmac: dwmac-visconti: Fix bit definitions for ETHER_CLK_SEL
  net: phy: broadcom: hook up soft_reset for BCM54616S
  sched/pelt: Relax the sync of util_sum with util_avg
  perf: Fix perf_event_read_local() time
  powerpc/64s: Mask SRR0 before checking against the masked NIP
  netfilter: conntrack: don't increment invalid counter on NF_REPEAT
  powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06
  SUNRPC: Don't dereference xprt->snd_task if it's a cookie
  SUNRPC: Use BIT() macro in rpc_show_xprt_state()
  KVM: arm64: pkvm: Use the mm_ops indirection for cache maintenance
  NFS: Ensure the server has an up to date ctime before renaming
  NFS: Ensure the server has an up to date ctime before hardlinking
  

[Kernel-packages] [Bug 1959878] Re: Jammy update: v5.15.18 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Jammy update: v5.15.18 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.18
  drm/vmwgfx: Fix stale file descriptors on failed usercopy
  arm64/bpf: Remove 128MB limit for BPF JIT programs
  drm/amdgpu: Use correct VIEWPORT_DIMENSION for DCN2
  select: Fix indefinitely sleeping task in poll_schedule_timeout()
  rcu: Tighten rcu_advance_cbs_nowake() checks
  memcg: better bounds on the memcg stats updates
  memcg: unify memcg stat flushing
  memcg: flush stats only if updated
  bnx2x: Invalidate fastpath HSI version for VFs
  bnx2x: Utilize firmware 7.13.21.0
  io_uring: fix not released cached task refs
  drm/amd/display: reset dcn31 SMU mailbox on failures
  drm/i915: Flush TLBs before releasing backing store

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


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

[Kernel-packages] [Bug 1959376] Re: Jammy update: v5.15.17 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.15.0-22.22

---
linux (5.15.0-22.22) jammy; urgency=medium

  * jammy/linux: 5.15.0-22.22 -proposed tracker (LP: #1960290)

 -- Paolo Pisati   Tue, 08 Feb 2022 10:48:49
+0100

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

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

Title:
  Jammy update: v5.15.17 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

  
  Linux 5.15.17
  scripts: sphinx-pre-install: Fix ctex support on Debian
  scripts: sphinx-pre-install: add required ctex dependency
  lib/test_meminit: destroy cache in kmem_cache_alloc_bulk() test
  bonding: Fix extraction of ports from the packet headers
  mm/hmm.c: allow VM_MIXEDMAP to work with hmm_range_fault
  lib82596: Fix IRQ check in sni_82596_probe
  scripts/dtc: dtx_diff: remove broken example from help text
  sch_api: Don't skip qdisc attach on ingress
  dt-bindings: watchdog: Require samsung,syscon-phandle for Exynos7
  dt-bindings: display: meson-vpu: Add missing amlogic,canvas property
  dt-bindings: display: meson-dw-hdmi: add missing sound-name-prefix property
  net: mscc: ocelot: fix using match before it is set
  net: phy: micrel: use kszphy_suspend()/kszphy_resume for irq aware devices
  net: cpsw: avoid alignment faults by taking NET_IP_ALIGN into account
  net: sfp: fix high power modules without diagnostic monitoring
  net: ocelot: Fix the call to switchdev_bridge_port_offload
  net: ethernet: mtk_eth_soc: fix error checking in mtk_mac_config()
  net: wwan: Fix MRU mismatch issue which may lead to data connection lost
  bcmgenet: add WOL IRQ check
  net: mscc: ocelot: don't let phylink re-enable TX PAUSE on the NPI port
  net_sched: restore "mpu xxx" handling
  net: ipa: fix atomic update in ipa_endpoint_replenish()
  net: bonding: fix bond_xmit_broadcast return value error bug
  net: fix sock_timestamping_bind_phc() to release device
  arm64: dts: qcom: msm8996: drop not documented adreno properties
  devlink: Remove misleading internal_flags from health reporter dump
  perf probe: Fix ppc64 'perf probe add events failed' case
  perf tools: Drop requirement for libstdc++.so for libopencsd check
  dmaengine: at_xdmac: Fix at_xdmac_lld struct definition
  dmaengine: at_xdmac: Fix lld view setting
  dmaengine: at_xdmac: Fix concurrency over xfers_list
  dmaengine: at_xdmac: Print debug message after realeasing the lock
  dmaengine: at_xdmac: Start transfer for cyclic channels in issue_pending
  dmaengine: at_xdmac: Don't start transactions at tx_submit level
  perf script: Fix hex dump character output
  libcxgb: Don't accidentally set RTO_ONLINK in cxgb_find_route()
  gre: Don't accidentally set RTO_ONLINK in gre_fill_metadata_dst()
  vdpa/mlx5: Restore cur_num_vqs in case of failure in change_num_qps()
  xfrm: Don't accidentally set RTO_ONLINK in decode_session4()
  iwlwifi: fix Bz NMI behaviour
  netns: add schedule point in ops_exit_list()
  inet: frags: annotate races around fqdir->dead and fqdir->high_thresh
  taskstats: Cleanup the use of task->exit_code
  virtio_ring: mark ring unused on error
  vdpa/mlx5: Fix wrong configuration of virtio_version_1_0
  rtc: pxa: fix null pointer dereference
  HID: vivaldi: fix handling devices not using numbered reports
  um: gitignore: Add kernel/capflags.c
  bitops: protect find_first_{,zero}_bit properly
  net: axienet: increase default TX ring size to 128
  net: axienet: fix for TX busy handling
  net: axienet: fix number of TX ring slots for available check
  net: axienet: Fix TX ring slot available check
  net: axienet: limit minimum TX ring size
  net: axienet: add missing memory barriers
  net: axienet: reset core on initialization prior to MDIO access
  net: axienet: Wait for PhyRstCmplt after core reset
  net: axienet: increase reset timeout
  net/smc: Fix hung_task when removing SMC-R devices
  gpio: idt3243x: Fix IRQ check in idt_gpio_probe
  gpio: mpc8xxx: Fix IRQ check in mpc8xxx_probe
  pinctrl/rockchip: fix gpio device creation
  clk: si5341: Fix clock HW provider cleanup
  clk: Emit a stern warning with writable debugfs enabled
  af_unix: annote lockless accesses to unix_tot_inflight & gc_in_progress
  crypto: octeontx2 - 

[Kernel-packages] [Bug 1961075] Re: Introduce 510-server NVIDIA driver and update the 510 UDA driver series in Bionic, Focal, and Impish

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-510 -
510.54-0ubuntu1

---
nvidia-graphics-drivers-510 (510.54-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1961075):
- Fixed a bug that could cause GPU exceptions when minimizing a
  fullscreen Vulkan application on certain desktops, such as
  Plasma.
  * debian/templates/control.in:
- Set XB-Support to PB (production branch).
  * debian/libnvidia-ifr1-470.{install|links}:
- Drop leftover files.
  * debian/rules.defs:
- Add support for video ABI 25.

 -- Alberto Milone   Wed, 16 Feb 2022
10:49:20 +0100

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Introduce 510-server NVIDIA driver and update the 510 UDA driver
  series in Bionic, Focal, and Impish

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Incomplete
Status in nvidia-graphics-drivers-510 source package in Impish:
  Fix Committed

Bug description:
  Introduce 510-server NVIDIA driver and its fabric-manager and
  libnvidia-nscq packages, and update the 510 UDA driver series in
  Bionic, Focal, and Impish.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 510 UDA ==

  === impish ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  === focal ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/rules.defs:
  - Add support for video ABI 25.

  === bionic ===

  nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1)

    * New upstream release (LP: #1961075):
  - Fixed a bug that could cause GPU exceptions when minimizing a
    fullscreen Vulkan application on certain desktops, such as
    Plasma.
    * debian/templates/control.in:
  - Set XB-Support to PB (production branch).
    * debian/libnvidia-ifr1-470.{install|links}:
  - Drop leftover files.
    * debian/rules.defs:
  - Add support for video ABI 25.

  == 510 -server ==

  === impish/focal/bionic ===
   * Initial release (LP: #1961075).

  == fabric-manager ==

   * Initial release (LP: #1961075).

  == libnvidia-nscq ==

   * Initial release (LP: #1961075).

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


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

[Kernel-packages] [Bug 1961815] Re: ftbfs with linux 5.16 & 5.17

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.172.01-0ubuntu3

---
nvidia-graphics-drivers-450-server (450.172.01-0ubuntu3) jammy; urgency=medium

  * debian/rules.defs:
- Add support for video ABI 25.

 -- Alberto Milone   Thu, 03 Mar 2022
18:10:50 +0100

** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ftbfs with linux 5.16 & 5.17

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * FTBFS from with 5.16 & 5.17 kernels

  [Test Plan]

   * Install linux-generic-wip from ppa:canonical-kernel-team/unstable
  and linux-generic from jammy

   * install nvidia-dkms-390

   * check that module is compiles correctly for both v5.15 and v5.17
  kernels

   * Similar checks can be done using v5.15 & v5.16 kernels on focal
  using linux-hwe-20.04-edge and linux-oem-5.16 kernels.

  [Where problems could occur]

   * Fixes are backports of similar changes already present and in use
  in nvidia-graphics-drivers-470. Note that 390 drivers are in
  maintainance mode, and have stopped receiving upstream updates. Hence
  manual cherrypicks are performed.

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


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

[Kernel-packages] [Bug 1964035] Re: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only

[Daniel van Vugt]

Yes the screen will still light up if you disable the i915 kernel
driver. But you're essentially using BIOS graphics then. You would lose:

  * High resolution
  * Hardware acceleration
  * Multi-GPU support

Basically graphical desktops won't work anymore, so you shouldn't
disable the i915 kernel driver.

Separately, as mentioned in bug 1964090 the old 'intel' Xorg driver is
buggy and should be removed:

  sudo apt remove xserver-xorg-video-intel

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

Title:
  no image on monitor on laptop with two graphics card (onboard
  intel+nvidia rtx3050) if run nvidia only

Status in linux-hwe-5.13 package in Ubuntu:
  Opinion
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Opinion

Bug description:
  i have laptop (Vendor:MSI / Model:Katana GF76 11UC) with two graphics
  card (onboard intel+nvidia rtx3050)

  I didn't like how intel (i915) works (flickering problem has not yet
  been overcome) so I decided to try using nvidia only.

  I spent a long time dealing with the "xorg" settings in order to run "x" on 
nvidia only:
  * disable the i915 driver with kernel settings: `modprobe.blacklist=i915 
i915.modeset=0`
  * rename /usr/share/X11/xorg.conf.d/20-intel.conf to *.bak
  * then modify /usr/share/X11/xorg.conf.d/10-nvidia.conf (set Identifier 
"Card0" )

  after starting startx on the screen, the image freezes when switching to tty2 
and back to tty1, the server does not render anything, and if you open `top` in 
tty2, you can see:
  ```
  MiB Mem :  31808,1 total,  24998,2 free,   5471,6 used,   1338,3 buff/cache
  MiB Swap:954,0 total,954,0 free,  0,0 used.  25914,7 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
 2547 root  20   0 2880328 156160  86076 R 100,3   0,5   6:19.96 
kwin_x11
 3033 hetman20   0 3052116 350728 186196 S   1,0   1,1   0:06.43 firefox
 3314 hetman20   0 2477080 140688  93056 S   1,0   0,4   0:01.23 
Isolated Web Co
  306 root  20   0   0  0  0 I   0,3   0,0   0:00.36 
kworker/6:2-events
  776 message+  20   09044   6032   3828 S   0,3   0,0   0:01.62 
dbus-daemon
  801 root  20   0   16852   7828   6892 S   0,3   0,0   0:00.17 
systemd-logind
 2967 hetman20   0 5771360   4,4g 124548 S   0,3  14,1   2:04.60 
plasmashell
 3000 hetman20   0  340504  63760  50732 S   0,3   0,2   0:00.37 
kwalletd5
 3207 hetman20   0 2427008 110324  89080 S   0,3   0,3   0:00.30 
Privileged Cont
 3607 root  20   0   0  0  0 I   0,3   0,0   0:00.03 
kworker/u24:2-events_power_efficient
  ```
   nvidia-smi 
  ```
  hetman@katana-lin:/mnt/giga/xorg_nvidia$ cat mvidia-smi.log
  Mon Mar  7 23:03:53 2022   
  
+-+
  | NVIDIA-SMI 510.47.03Driver Version: 510.47.03CUDA Version: 11.6 
|
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  |   |  |   MIG M. 
|
  
|===+==+==|
  |   0  NVIDIA GeForce ...  Off  | :01:00.0 Off |  N/A 
|
  | N/A   41CP8N/A /  N/A |132MiB /  4096MiB |  0%  Default 
|
  |   |  |  N/A 
|
  
+---+--+--+

 
  
+-+
  | Processes:  
|
  |  GPU   GI   CIPID   Type   Process name  GPU Memory 
|
  |ID   ID   Usage  
|
  
|=|
  |0   N/A  N/A  2847  G   /usr/lib/xorg/Xorg 12MiB 
|
  |0   N/A  N/A  2967  G   /usr/bin/plasmashell8MiB 
|
  |0   N/A  N/A  3033  G   /usr/lib/firefox/firefox   85MiB 
|
  |0   N/A  N/A  4436  G   ...bexec/kscreenlocker_greet   12MiB 
|
  
+-+
  ```
  Thus, I stated that the X's started up and are working, but the image is not 
displayed. 

  if return
  modprobe i915.modeset=1
  /usr/share/X11/xorg.conf.d/20-intel.conf
  

[Kernel-packages] [Bug 1964035] Re: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only

[hetman]

I do not exclude such a possibility, but I suppose since I definitely
have 2 video cards, then there are problems 2. I opened a separate topic
on i915: # 1964090.

But I would like to make sure that what you say is true. regarding the
dependence of the display on intel.

I may not have enough information, but it seems to me that I can
definitely turn off the 915 driver and at the same time I can continue
to work in the tty`s console.


although there may be information confirming your words. so for example when X 
starts on i915 then in the logs there is 

[   839.172] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
[   839.172] (--) intel(0): Output HDMI1 using initial mode 1920x1080 on pipe 1
..
[   840.294] (II) intel(0): Modeline "1920x1080"x0.0  368.14  1920 1968 2000 
2102  1080 1090 1095 1216 -hsync -vsync (175.1 kHz eP)
[   840.294] (II) intel(0): Modeline "1920x1080"x0.0  153.40  1920 1968 2000 
2102  1080 1090 1095 1216 -hsync -vsync (73.0 kHz e)

but when running without i915, I did not find similar lines for nvidia but have 
a
[  1327.768] (WW) NVIDIA(0): Unable to get display device for DPI computation.
it maybe:
1. I made a mistake with the settings xorg
2. software bug
3. your option is that it won’t work at all without intel 

** Attachment added: "log for nvidia only settings"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1964035/+attachment/5566947/+files/Xorg.0.log

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

Title:
  no image on monitor on laptop with two graphics card (onboard
  intel+nvidia rtx3050) if run nvidia only

Status in linux-hwe-5.13 package in Ubuntu:
  Opinion
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Opinion

Bug description:
  i have laptop (Vendor:MSI / Model:Katana GF76 11UC) with two graphics
  card (onboard intel+nvidia rtx3050)

  I didn't like how intel (i915) works (flickering problem has not yet
  been overcome) so I decided to try using nvidia only.

  I spent a long time dealing with the "xorg" settings in order to run "x" on 
nvidia only:
  * disable the i915 driver with kernel settings: `modprobe.blacklist=i915 
i915.modeset=0`
  * rename /usr/share/X11/xorg.conf.d/20-intel.conf to *.bak
  * then modify /usr/share/X11/xorg.conf.d/10-nvidia.conf (set Identifier 
"Card0" )

  after starting startx on the screen, the image freezes when switching to tty2 
and back to tty1, the server does not render anything, and if you open `top` in 
tty2, you can see:
  ```
  MiB Mem :  31808,1 total,  24998,2 free,   5471,6 used,   1338,3 buff/cache
  MiB Swap:954,0 total,954,0 free,  0,0 used.  25914,7 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
 2547 root  20   0 2880328 156160  86076 R 100,3   0,5   6:19.96 
kwin_x11
 3033 hetman20   0 3052116 350728 186196 S   1,0   1,1   0:06.43 firefox
 3314 hetman20   0 2477080 140688  93056 S   1,0   0,4   0:01.23 
Isolated Web Co
  306 root  20   0   0  0  0 I   0,3   0,0   0:00.36 
kworker/6:2-events
  776 message+  20   09044   6032   3828 S   0,3   0,0   0:01.62 
dbus-daemon
  801 root  20   0   16852   7828   6892 S   0,3   0,0   0:00.17 
systemd-logind
 2967 hetman20   0 5771360   4,4g 124548 S   0,3  14,1   2:04.60 
plasmashell
 3000 hetman20   0  340504  63760  50732 S   0,3   0,2   0:00.37 
kwalletd5
 3207 hetman20   0 2427008 110324  89080 S   0,3   0,3   0:00.30 
Privileged Cont
 3607 root  20   0   0  0  0 I   0,3   0,0   0:00.03 
kworker/u24:2-events_power_efficient
  ```
   nvidia-smi 
  ```
  hetman@katana-lin:/mnt/giga/xorg_nvidia$ cat mvidia-smi.log
  Mon Mar  7 23:03:53 2022   
  
+-+
  | NVIDIA-SMI 510.47.03Driver Version: 510.47.03CUDA Version: 11.6 
|
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  |   |  |   MIG M. 
|
  
|===+==+==|
  |   0  NVIDIA GeForce ...  Off  | :01:00.0 Off |  N/A 
|
  | N/A   41CP8N/A /  N/A |132MiB /  4096MiB |  0%  Default 
|
  |   |  |  N/A 
|
  
+---+--+--+

 
  

[Kernel-packages] [Bug 1963919] Re: fbtft overlay is missing

[Juerg Haefliger]

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

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

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

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

** Also affects: linux-raspi2 (Ubuntu Jammy)
   Importance: Wishlist
   Status: Won't Fix

** Also affects: linux-raspi (Ubuntu Jammy)
   Importance: Wishlist
   Status: New

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

** Changed in: linux-raspi2 (Ubuntu Jammy)
   Status: Won't Fix => Invalid

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

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

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

Title:
  fbtft overlay is missing

Status in linux-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi2 package in Ubuntu:
  Won't Fix
Status in linux-raspi source package in Focal:
  New
Status in linux-raspi2 source package in Focal:
  Invalid
Status in linux-raspi source package in Impish:
  New
Status in linux-raspi2 source package in Impish:
  Invalid
Status in linux-raspi source package in Jammy:
  Fix Released
Status in linux-raspi2 source package in Jammy:
  Invalid

Bug description:
  To attach TFT touchscreens the pi-foundation kernel ships the fbtft
  devicetree overlay along with rpi-display.

  While you can attach a stand-alone TFT display just fine when only
  using rpi-display to provide the drivers with hardcoded GPIO
  assignments, it gets extremely tricky to even enable the touchscreen
  input or to use such a TFT with other sensors attached since rpi-
  display does not allow any re-assignment of the GPIO pins in use.

  The upstream fbtft driver can make use of the already included rpi-display 
drivers by defining "rpi-display" in its params. It also allows to freely 
re-assign the GPIO pins for backlight, D/C and Reset to give you enough 
flexibility to have the display co-exist with any attached sensors and  touch 
input devices that do not have the ability to re-assign GPIO pins and that 
clash with the hardcoded numbering of rpi-display.
  An example with freely assigned GPIOs can be seen in the upstream 
(rpi-foundation) overlay README file at:

  https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L884

  Please include fbtft in the ubuntu kernels to allow a more flexible
  usage of SPI based TFT touchscreens on the Pi.

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


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

[Kernel-packages] [Bug 1964035] Re: no image on monitor on laptop with two graphics card (onboard intel+nvidia rtx3050) if run nvidia only

[Daniel van Vugt]

Thanks for the bug report.

This is probably not a bug at all since most laptops only have the Intel
GPU wired to the laptop screen. So to disable i915 is to mostly disable
the laptop screen.

I suggest instead of pursuing this bug we should fix the i915
"flickering problem". Please re-enable i915 and then while the
flickering problem is happening open a new bug by running:

  ubuntu-bug xorg

Although xorg is almost always the wrong package, it's a good place to
start when reporting graphics bugs.


** No longer affects: xorg (Ubuntu)

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

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Opinion

** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
   Status: New => Opinion

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

Title:
  no image on monitor on laptop with two graphics card (onboard
  intel+nvidia rtx3050) if run nvidia only

Status in linux-hwe-5.13 package in Ubuntu:
  Opinion
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Opinion

Bug description:
  i have laptop (Vendor:MSI / Model:Katana GF76 11UC) with two graphics
  card (onboard intel+nvidia rtx3050)

  I didn't like how intel (i915) works (flickering problem has not yet
  been overcome) so I decided to try using nvidia only.

  I spent a long time dealing with the "xorg" settings in order to run "x" on 
nvidia only:
  * disable the i915 driver with kernel settings: `modprobe.blacklist=i915 
i915.modeset=0`
  * rename /usr/share/X11/xorg.conf.d/20-intel.conf to *.bak
  * then modify /usr/share/X11/xorg.conf.d/10-nvidia.conf (set Identifier 
"Card0" )

  after starting startx on the screen, the image freezes when switching to tty2 
and back to tty1, the server does not render anything, and if you open `top` in 
tty2, you can see:
  ```
  MiB Mem :  31808,1 total,  24998,2 free,   5471,6 used,   1338,3 buff/cache
  MiB Swap:954,0 total,954,0 free,  0,0 used.  25914,7 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
 2547 root  20   0 2880328 156160  86076 R 100,3   0,5   6:19.96 
kwin_x11
 3033 hetman20   0 3052116 350728 186196 S   1,0   1,1   0:06.43 firefox
 3314 hetman20   0 2477080 140688  93056 S   1,0   0,4   0:01.23 
Isolated Web Co
  306 root  20   0   0  0  0 I   0,3   0,0   0:00.36 
kworker/6:2-events
  776 message+  20   09044   6032   3828 S   0,3   0,0   0:01.62 
dbus-daemon
  801 root  20   0   16852   7828   6892 S   0,3   0,0   0:00.17 
systemd-logind
 2967 hetman20   0 5771360   4,4g 124548 S   0,3  14,1   2:04.60 
plasmashell
 3000 hetman20   0  340504  63760  50732 S   0,3   0,2   0:00.37 
kwalletd5
 3207 hetman20   0 2427008 110324  89080 S   0,3   0,3   0:00.30 
Privileged Cont
 3607 root  20   0   0  0  0 I   0,3   0,0   0:00.03 
kworker/u24:2-events_power_efficient
  ```
   nvidia-smi 
  ```
  hetman@katana-lin:/mnt/giga/xorg_nvidia$ cat mvidia-smi.log
  Mon Mar  7 23:03:53 2022   
  
+-+
  | NVIDIA-SMI 510.47.03Driver Version: 510.47.03CUDA Version: 11.6 
|
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  |   |  |   MIG M. 
|
  
|===+==+==|
  |   0  NVIDIA GeForce ...  Off  | :01:00.0 Off |  N/A 
|
  | N/A   41CP8N/A /  N/A |132MiB /  4096MiB |  0%  Default 
|
  |   |  |  N/A 
|
  
+---+--+--+

 
  
+-+
  | Processes:  
|
  |  GPU   GI   CIPID   Type   Process name  GPU Memory 
|
  |ID   ID   Usage  
|
  
|=|
  |0   N/A  N/A  2847  G   /usr/lib/xorg/Xorg 12MiB 
|
  |0   N/A  N/A  2967  G   /usr/bin/plasmashell8MiB 
|
  |0   N/A  N/A  3033  G   /usr/lib/firefox/firefox   85MiB 
|
  |0   N/A  N/A  4436  G   ...bexec/kscreenlocker_greet  

[Kernel-packages] [Bug 1963754] Re: No brightness slider in settings

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1963754

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  No brightness slider in settings

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This page mentions a brightness slider :
  https://help.ubuntu.com/22.04/ubuntu-help/display-brightness.html.en

  When I click on the system settings I see a (sound) volume slider but no 
brightness slider.
  screenshot : https://i.imgur.com/N6EWUra.png

  lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  apt update/upgrade done today 2022-03-05

  Gnome version 42.beta
  Windowing system X11

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


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

[Kernel-packages] [Bug 1963754] Re: No brightness slider in settings

[Daniel van Vugt]

If you are using a desktop then this is not a bug. The brightness slider
is for laptop screens only.

If you are using a laptop then it most likely is a kernel bug.

** Tags added: jammy

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

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

Title:
  No brightness slider in settings

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This page mentions a brightness slider :
  https://help.ubuntu.com/22.04/ubuntu-help/display-brightness.html.en

  When I click on the system settings I see a (sound) volume slider but no 
brightness slider.
  screenshot : https://i.imgur.com/N6EWUra.png

  lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  apt update/upgrade done today 2022-03-05

  Gnome version 42.beta
  Windowing system X11

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


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

[Kernel-packages] [Bug 1690085]

[ankitvarma604]

This is a really nice information. Thanks for sharing it :)

https://www.firstcomputerspatna.com/

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Expired
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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


-- 

[Kernel-packages] [Bug 1963754] [NEW] No brightness slider in settings

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This page mentions a brightness slider :
https://help.ubuntu.com/22.04/ubuntu-help/display-brightness.html.en

When I click on the system settings I see a (sound) volume slider but no 
brightness slider.
screenshot : https://i.imgur.com/N6EWUra.png

lsb_release -rd
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
apt update/upgrade done today 2022-03-05

Gnome version 42.beta
Windowing system X11

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


** Tags: bot-comment jammy
-- 
No brightness slider in settings
https://bugs.launchpad.net/bugs/1963754
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