date:20211027

You can also apply the fix manually be editing
/lib/systemd/system/bluetooth.service and changing:

  #Restart=on-failure

to

  Restart=on-failure

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

Title:
  Bluetooth does not turn on via gnome-control-center after
  bluetooth.service crash

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  I had bluetooth crash (see logs below).  After the crash, I attempted
  to restart bluetooth by pressing the On/Off switch in the top-right of
  the Bluetooth tab of gnome-control-center (it was set to off).  After
  pressing the switch, the switch read "On", but the display of
  Bluetooth devices still appeared as it does when Bluetooth is off (it
  read "Bluetooth Turned Off\nTurn on to connect devices and receive
  file transfers.").

  I was able to remedy the situation by manually executing `sudo
  bluetoothd`.  I did this while the above On/Off switch was "Off" and
  the Bluetooth device list said Bluetooth was off.  After executing,
  the Bluetooth device list listed all my Bluetooth devices as expected.

  This is with bluetoothd 5.48.

  Bluetooth crash logs

  ```
  12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: 
Bluetooth daemon disappeared
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
  12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
  10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH 
HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  Uname: Linux 5.10.0-051000-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 13:00:09 2021
  InstallationDate: Installed on 2021-01-04 (295 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing

2021-10-27 Thread Kai-Heng Feng

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

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

Title:
  rtw89 kernel module for Realtek 8852 wifi is missing

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

Bug description:
  == SRU Justification ==
  [Impact]
  Realtek 8852AE, which is used by many new laptops, doesn't have a
  driver.

  [Fix]
  Add rtw89 driver to support Realtek 8852AE.

  [Test]
  After applying the patch, 8852AE can scan, connect and do TX/RX.

  [Where problems could occur]
  This is a brand new driver, unless the driver hits some subtle PCI or
  IOMMU bugs, there isn't much chance to introduce any regression.

  == Original Bug Report ==
  Hi,

  Resulting: no wifi adapter detected.
  Currently WIP: 
https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=*

  Workaround: use https://github.com/lwfinger/rtw89
  that allows to build a dkms deb package.

  Ubuntu Impish
  kernel 5.13 (or 5.15 from unstable ppa)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fthx   4574 F pulseaudio
   /dev/snd/controlC2:  fthx   4574 F pulseaudio
   /dev/snd/controlC0:  fthx   4574 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-15 (20 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 21AVFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-4-generic N/A
   linux-backports-modules-5.15.0-4-generic  N/A
   linux-firmware1.201
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET39W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AVFR
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21AVFR
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen

2021-10-27 Thread jeremyszu

** Tags removed: originate-from-1943787

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

Title:
  System hangs on purple screen

Status in OEM Priority Project:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  We are facing an issue that GDM starts with Wayland instead of Xorg,
  despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics.

  The issue happens because gdm-disable-wayland is executed after GDM has
  started. The reason why the udev rules takes so long is because the the
  runtime suspended NVIDIA GFX takes more than 1 second to runtime resume,
  hence the driver starts the probing routine rather late.

  The proper solution is to impose a barrier like
  systemd-udev-settle.service before GDM, but limits to the GFX device
  only to avoid waiting for all udev rules are finished.

  Since such mechanism isn't available right now, workaround the issue by
  enabling runtime PM after driver is bound to avoid the runtime resume
  delay, and hope GDM always starts after the probing is done.

  Please backport below patch to supported nvidia-drivers:
  
https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508

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


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

[Kernel-packages] [Bug 1949026] [NEW] System hangs on purple screen

2021-10-27 Thread jeremyszu

Public bug reported:

We are facing an issue that GDM starts with Wayland instead of Xorg,
despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics.

The issue happens because gdm-disable-wayland is executed after GDM has
started. The reason why the udev rules takes so long is because the the
runtime suspended NVIDIA GFX takes more than 1 second to runtime resume,
hence the driver starts the probing routine rather late.

The proper solution is to impose a barrier like
systemd-udev-settle.service before GDM, but limits to the GFX device
only to avoid waiting for all udev rules are finished.

Since such mechanism isn't available right now, workaround the issue by
enabling runtime PM after driver is bound to avoid the runtime resume
delay, and hope GDM always starts after the probing is done.

Please backport below patch to supported nvidia-drivers:
https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508

** Affects: oem-priority
 Importance: Critical
 Assignee: jeremyszu (os369510)
 Status: Triaged

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


** Tags: oem-priority originate-from-1942281 originate-from-1943787 stella

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

** Tags added: originate-from-1943787

** Changed in: oem-priority
 Assignee: (unassigned) => jeremyszu (os369510)

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

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

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

Title:
  System hangs on purple screen

Status in OEM Priority Project:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New

Bug description:
  We are facing an issue that GDM starts with Wayland instead of Xorg,
  despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics.

  The issue happens because gdm-disable-wayland is executed after GDM has
  started. The reason why the udev rules takes so long is because the the
  runtime suspended NVIDIA GFX takes more than 1 second to runtime resume,
  hence the driver starts the probing routine rather late.

  The proper solution is to impose a barrier like
  systemd-udev-settle.service before GDM, but limits to the GFX device
  only to avoid waiting for all udev rules are finished.

  Since such mechanism isn't available right now, workaround the issue by
  enabling runtime PM after driver is bound to avoid the runtime resume
  delay, and hope GDM always starts after the probing is done.

  Please backport below patch to supported nvidia-drivers:
  
https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508

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


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

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-10-27 Thread Mason Loring Bliss

(Or Ubuntu systems post-fix but with pools created while the bug was
active - and is there a fix possible, or is it "make a new pool"? Is
there a diagnostic possible to be sure either way?)

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Confirmed
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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

[Kernel-packages] [Bug 1948990] Re: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash

It appears BlueZ upstream does not restart on failure, but in Ubuntu we
turned on restart-on-failure in version 5.53-0ubuntu3. I suggest the
best way to get that fix right now is to upgrade to Ubuntu 20.04.

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

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

Title:
  Bluetooth does not turn on via gnome-control-center after
  bluetooth.service crash

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  I had bluetooth crash (see logs below).  After the crash, I attempted
  to restart bluetooth by pressing the On/Off switch in the top-right of
  the Bluetooth tab of gnome-control-center (it was set to off).  After
  pressing the switch, the switch read "On", but the display of
  Bluetooth devices still appeared as it does when Bluetooth is off (it
  read "Bluetooth Turned Off\nTurn on to connect devices and receive
  file transfers.").

  I was able to remedy the situation by manually executing `sudo
  bluetoothd`.  I did this while the above On/Off switch was "Off" and
  the Bluetooth device list said Bluetooth was off.  After executing,
  the Bluetooth device list listed all my Bluetooth devices as expected.

  This is with bluetoothd 5.48.

  Bluetooth crash logs

  ```
  12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: 
Bluetooth daemon disappeared
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
  12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
  10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH 
HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  Uname: Linux 5.10.0-051000-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 13:00:09 2021
  InstallationDate: Installed on 2021-01-04 (295 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1948990] Re: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash

I don't think the GUI is meant to start bluetoothd at all. It only
toggles the power state of the Bluetooth hardware. It assumes bluetoothd
is always running. So failure to restart after a crash is a problem with
bluez's systemd scripting.

** Package changed: gnome-control-center (Ubuntu) => bluez (Ubuntu)

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

Title:
  Bluetooth does not turn on via gnome-control-center after
  bluetooth.service crash

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  I had bluetooth crash (see logs below).  After the crash, I attempted
  to restart bluetooth by pressing the On/Off switch in the top-right of
  the Bluetooth tab of gnome-control-center (it was set to off).  After
  pressing the switch, the switch read "On", but the display of
  Bluetooth devices still appeared as it does when Bluetooth is off (it
  read "Bluetooth Turned Off\nTurn on to connect devices and receive
  file transfers.").

  I was able to remedy the situation by manually executing `sudo
  bluetoothd`.  I did this while the above On/Off switch was "Off" and
  the Bluetooth device list said Bluetooth was off.  After executing,
  the Bluetooth device list listed all my Bluetooth devices as expected.

  This is with bluetoothd 5.48.

  Bluetooth crash logs

  ```
  12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: 
Bluetooth daemon disappeared
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
  12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
  10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH 
HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  Uname: Linux 5.10.0-051000-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 13:00:09 2021
  InstallationDate: Installed on 2021-01-04 (295 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1948990] [NEW] Bluetooth does not turn on via gnome-control-center after bluetooth.service crash

You have been subscribed to a public bug:

I had bluetooth crash (see logs below).  After the crash, I attempted to
restart bluetooth by pressing the On/Off switch in the top-right of the
Bluetooth tab of gnome-control-center (it was set to off).  After
pressing the switch, the switch read "On", but the display of Bluetooth
devices still appeared as it does when Bluetooth is off (it read
"Bluetooth Turned Off\nTurn on to connect devices and receive file
transfers.").

I was able to remedy the situation by manually executing `sudo
bluetoothd`.  I did this while the above On/Off switch was "Off" and the
Bluetooth device list said Bluetooth was off.  After executing, the
Bluetooth device list listed all my Bluetooth devices as expected.

This is with bluetoothd 5.48.

Bluetooth crash logs

```
12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: Bluetooth 
daemon disappeared
12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH HID 
v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
```

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
Uname: Linux 5.10.0-051000-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 27 13:00:09 2021
InstallationDate: Installed on 2021-01-04 (295 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages
-- 
Bluetooth does not turn on via gnome-control-center after bluetooth.service 
crash
https://bugs.launchpad.net/bugs/1948990
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez 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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-10-27 Thread Seth Arnold

Stefan, do filesystems affected by this need to be rebuilt in order to
be used by other OpenZFS distributions or releases of Ubuntu that
predate the introduction of the bug?

Thanks

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Confirmed
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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

[Kernel-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work

** Tags added: impish

** Description changed:

  In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped
  working. This includes the "play/pause" button, "play next" (calls after
  long press of volume increase), and "play previous" (long press of
  volume decrease). The volume +/- buttons themselves are working, but
  this seemingly is implemented entirely in the headphones and does not
  require any communication over bluetooth.
  
- In previous ubuntu (20.04) these buttons worked, and I expect them
+ In previous ubuntu (21.04) these buttons worked, and I expect them
  working.
  
  My headset is Qumo Accord 3.
  
  Here is output of "inxi -Eaz" in terminal:
  
- Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 
-serial:  
-Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 
-rev: e2f 
-Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept 
-service-classes: rendering, capturing, object transfer, audio, 
telephony
+ Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001
+    serial: 
+    Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0
+    rev: e2f
+    Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept
+    service-classes: rendering, capturing, object transfer, audio, 
telephony
  
  Some possible workarounds that I found suggest to "modprobe uinput", but
  the uinput module does not get loaded (lsmod does not list it even after
  modprobe'ing).

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (21.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001
     serial: 
     Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0
     rev: e2f
     Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept
     service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

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


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

[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856

2021-10-27 Thread You-Sheng Yang

This causes an AX201 iwlwifi firmware regression filed in
https://bugs.launchpad.net/somerville/+bug/1948949.

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

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

Title:
  Need support of Qualcomm WCN6856

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
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-firmware source package in Focal:
  Incomplete
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Hirsute:
  New
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Incomplete
Status in linux-firmware source package in Impish:
  New
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Qualcomm WCN685x is not supported yet.

  [Fix]

  Qualcomm WCN685x support are mostly available in linux-next and mainline
  with one patch currently in kvalo/ath tree, and 3 additional in review.

  [Test Case]

  Test hardware connectivity, stability with basic checkbox tests:

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

  [Where problems could occur]

  While this introduces a new hardware, it might need further
  polishments.

  [Other Info]

  WCN685x WiFi 6E capability is still under development and is moved to
  next milestone for oem projects. Firmware blobs for both WiFi and
  Bluetooth are also needed and will be SRUed when a formal release is
  made.

  == original bug report ==

  Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01
  BT driver support: USB\VID_0489_E0C9_0001

  Wireless Driver support: PCI\VEN_17CB_1103_01
  BT driver support: USB\VID_0489_E0CC_0001

  
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
  Already landed to mainline kernel v5.14-rc1.

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


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

[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

** Tags added: psr

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

Title:
  [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

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

Bug description:
  In every 6/10 boot my ubuntu failed to start stuck on blank screen.
  Sometime touchpad stop working and unable to change my brightness
  after installation at first all feature are perfectly fine except
  screen glitch.Screen performance is laggy.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 17:13:28 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
 Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
  InstallationDate: Installed on 2021-07-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55722 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Kernel-packages] [Bug 1949018] [NEW] Focal update: 5.10.75 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.75 upstream stable release
   from git://git.kernel.org/


Linux 5.10.75
net: dsa: mv88e6xxx: don't use PHY_DETECT on internal PHY's
ionic: don't remove netdev->dev_addr when syncing uc list
net: mscc: ocelot: warn when a PTP IRQ is raised for an unknown skb
nfp: flow_offload: move flow_indr_dev_register from app init to app start
r8152: select CRC32 and CRYPTO/CRYPTO_HASH/CRYPTO_SHA256
qed: Fix missing error code in qed_slowpath_start()
mqprio: Correct stats in mqprio_dump_class_stats().
platform/x86: intel_scu_ipc: Fix busy loop expiry time
acpi/arm64: fix next_platform_timer() section mismatch error
drm/msm/dsi: fix off by one in dsi_bus_clk_enable error handling
drm/msm/dsi: Fix an error code in msm_dsi_modeset_init()
drm/msm/a6xx: Track current ctx by seqno
drm/msm/mdp5: fix cursor-related warnings
drm/msm: Fix null pointer dereference on pointer edp
drm/edid: In connector_bad_edid() cap num_of_ext by num_blocks read
drm/panel: olimex-lcd-olinuxino: select CRC32
spi: bcm-qspi: clear MSPI spifie interrupt during probe
platform/mellanox: mlxreg-io: Fix read access of n-bytes size attributes
platform/mellanox: mlxreg-io: Fix argument base in kstrtou32() call
mlxsw: thermal: Fix out-of-bounds memory accesses
ata: ahci_platform: fix null-ptr-deref in ahci_platform_enable_regulators()
pata_legacy: fix a couple uninitialized variable bugs
NFC: digital: fix possible memory leak in digital_in_send_sdd_req()
NFC: digital: fix possible memory leak in digital_tg_listen_mdaa()
nfc: fix error handling of nfc_proto_register()
vhost-vdpa: Fix the wrong input in config_cb
ethernet: s2io: fix setting mac address during resume
net: encx24j600: check error in devm_regmap_init_encx24j600
net: dsa: microchip: Added the condition for scheduling ksz_mib_read_work
net: stmmac: fix get_hw_feature() on old hardware
net/mlx5e: Mutually exclude RX-FCS and RX-port-timestamp
net/mlx5e: Fix memory leak in mlx5_core_destroy_cq() error path
net: korina: select CRC32
net: arc: select CRC32
gpio: pca953x: Improve bias setting
sctp: account stream padding length for reconf chunk
nvme-pci: Fix abort command id
ARM: dts: bcm2711-rpi-4-b: Fix pcie0's unit address formatting
ARM: dts: bcm2711-rpi-4-b: fix sd_io_1v8_reg regulator states
ARM: dts: bcm2711: fix MDIO #address- and #size-cells
ARM: dts: bcm2711-rpi-4-b: Fix usb's unit address
tee: optee: Fix missing devices unregister during optee_remove
iio: dac: ti-dac5571: fix an error code in probe()
iio: ssp_sensors: fix error code in ssp_print_mcu_debug()
iio: ssp_sensors: add more range checking in ssp_parse_dataframe()
iio: adc: max1027: Fix the number of max1X31 channels
iio: light: opt3001: Fixed timeout error when 0 lux
iio: mtk-auxadc: fix case IIO_CHAN_INFO_PROCESSED
iio: adc: max1027: Fix wrong shift with 12-bit devices
iio: adc128s052: Fix the error handling path of 'adc128_probe()'
iio: adc: ad7793: Fix IRQ flag
iio: adc: ad7780: Fix IRQ flag
iio: adc: ad7192: Add IRQ flag
driver core: Reject pointless SYNC_STATE_ONLY device links
drivers: bus: simple-pm-bus: Add support for probing simple bus only devices
iio: adc: aspeed: set driver data when adc probe.
powerpc/xive: Discard disabled interrupts in get_irqchip_state()
x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically
nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells
EDAC/armada-xp: Fix output of uncorrectable error counter
virtio: write back F_VERSION_1 before validate
misc: fastrpc: Add missing lock before accessing find_vma()
USB: serial: option: add prod. id for Quectel EG91
USB: serial: option: add Telit LE910Cx composition 0x1204
USB: serial: option: add Quectel EC200S-CN module support
USB: serial: qcserial: add EM9191 QDL support
Input: xpad - add support for another USB ID of Nacon GC-100
usb: musb: dsps: Fix the probe error path
efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock()
efi/cper: use stack buffer for error record decoding
cb710: avoid NULL pointer subtraction
xhci: Enable trust tx length quirk for Fresco FL11 USB controller
xhci: Fix command ring pointer corruption while aborting a command
xhci: guard accesses to ep_state in xhci_endpoint_reset()
USB: xhci: dbc: fix tty registration race
mei: me: add Ice Lake-N device id.
x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails
btrfs: fix abort logic in btrfs_replace_file_extents
btrfs: update refs for any root except tree log roots
btrfs: check for error when looking up inode during dir entry

[Kernel-packages] [Bug 1949019] [NEW] Focal update: 5.10.76 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.76 upstream stable release
   from git://git.kernel.org/


Linux 5.10.76
pinctrl: stm32: use valid pin identifier in stm32_pinctrl_resume()
ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
selftests: bpf: fix backported ASSERT_FALSE
e1000e: Separate TGP board type from SPT
tracing: Have all levels of checks prevent recursion
net: mdiobus: Fix memory leak in __mdiobus_register
bpf, test, cgroup: Use sk_{alloc,free} for test cases
s390/pci: fix zpci_zdev_put() on reserve
can: isotp: isotp_sendmsg(): fix TX buffer concurrent access in isotp_sendmsg()
scsi: core: Fix shost->cmd_per_lun calculation in scsi_add_host_with_dma()
net: hns3: fix for miscalculation of rx unused desc
sched/scs: Reset the shadow stack when idle_task_exit
scsi: qla2xxx: Fix a memory leak in an error path of qla2x00_process_els()
scsi: iscsi: Fix set_param() handling
Input: snvs_pwrkey - add clk handling
perf/x86/msr: Add Sapphire Rapids CPU support
libperf tests: Fix test_stat_cpu
ALSA: hda: avoid write to STATESTS if controller is in reset
platform/x86: intel_scu_ipc: Update timeout value in comment
isdn: mISDN: Fix sleeping function called from invalid context
ARM: dts: spear3xx: Fix gmac node
net: stmmac: add support for dwmac 3.40a
btrfs: deal with errors when checking if a dir entry exists during log replay
ALSA: hda: intel: Allow repeatedly probing on codec configuration errors
gcc-plugins/structleak: add makefile var for disabling structleak
net: hns3: fix the max tx size according to user manual
drm: mxsfb: Fix NULL pointer dereference crash on unload
net: bridge: mcast: use multicast_membership_interval for IGMPv3
selftests: netfilter: remove stray bash debug line
netfilter: Kconfig: use 'default y' instead of 'm' for bool config option
isdn: cpai: check ctr->cnr to avoid array index out of bound
nfc: nci: fix the UAF of rf_conn_info object
KVM: nVMX: promptly process interrupts delivered while in guest mode
mm, slub: fix incorrect memcg slab count for bulk free
mm, slub: fix potential memoryleak in kmem_cache_open()
mm, slub: fix mismatch between reconstructed freelist depth and cnt
powerpc/idle: Don't corrupt back chain when going idle
KVM: PPC: Book3S HV: Make idle_kvm_start_guest() return 0 if it went to guest
KVM: PPC: Book3S HV: Fix stack handling in idle_kvm_start_guest()
powerpc64/idle: Fix SP offsets when saving GPRs
net: dsa: mt7530: correct ds->num_ports
audit: fix possible null-pointer dereference in audit_filter_rules
ASoC: DAPM: Fix missing kctl change notifications
ALSA: hda/realtek: Add quirk for Clevo PC50HS
ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset
vfs: check fd has read access in kernel_read_file_from_fd()
elfcore: correct reference to CONFIG_UML
userfaultfd: fix a race between writeprotect and exit_mmap()
ocfs2: mount fails with buffer overflow in strlen
ocfs2: fix data corruption after conversion from inline format
ceph: fix handling of "meta" errors
ceph: skip existing superblocks that are blocklisted or shut down when mounting
can: j1939: j1939_xtp_rx_rts_session_new(): abort TP less than 9 bytes
can: j1939: j1939_xtp_rx_dat_one(): cancel session if receive TP.DT with error 
length
can: j1939: j1939_netdev_start(): fix UAF for rx_kref of j1939_priv
can: j1939: j1939_tp_rxtimer(): fix errant alert in j1939_tp_rxtimer
can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible()
can: isotp: isotp_sendmsg(): fix return error on FC timeout on TX path
can: peak_pci: peak_pci_remove(): fix UAF
can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state 
notification
can: rcar_can: fix suspend/resume
net: enetc: fix ethtool counter name for PM0_TERR
drm/panel: ilitek-ili9881c: Fix sync for Feixin K101-IM2BYL02 panel
ice: Add missing E810 device ids
e1000e: Fix packet loss on Tiger Lake and later
net: stmmac: Fix E2E delay mechanism
net: hns3: disable sriov before unload hclge layer
net: hns3: fix vf reset workqueue cannot exit
net: hns3: schedule the polling again when allocation fails
net: hns3: add limit ets dwrr bandwidth cannot be 0
net: hns3: reset DWRR of unused tc to zero
powerpc/smp: do not decrement idle task preempt count in CPU offline
NIOS2: irqflags: rename a redefined register name
net: dsa: lantiq_gswip: fix register definition
ipv6: When forwarding count rx stats on the orig netdev
tcp: md5: Fix overlap between vrf and non-vrf keys
lan78xx: select CRC32
netfilter: ipvs: make global sysctl readonly in non-init netns
netfilter: ip6t_rt: fix rt0_hdr parsing in rt_mt6

[Kernel-packages] [Bug 1949017] [NEW] Focal update: 5.10.74 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.74 upstream stable release
   from git://git.kernel.org/


Linux 5.10.74
hwmon: (pmbus/ibm-cffps) max_power_out swap changes
sched: Always inline is_percpu_thread()
perf/core: fix userpage->time_enabled of inactive events
scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
scsi: ses: Fix unsigned comparison with less than zero
drm/amdgpu: fix gart.bo pin_count leak
net: sun: SUNVNET_COMMON should depend on INET
vboxfs: fix broken legacy mount signature checking
mac80211: check return value of rhashtable_init
net: prevent user from passing illegal stab size
hwmon: (ltc2947) Properly handle errors when looking for the external clock
m68k: Handle arrivals of multiple signals correctly
mac80211: Drop frames from invalid MAC address in ad-hoc mode
netfilter: nf_nat_masquerade: defer conntrack walk to work queue
netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic
ASoC: SOF: loader: release_firmware() on load failure to avoid batching
HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs
netfilter: ip6_tables: zero-initialize fragment offset
HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic
ext4: correct the error path of ext4_write_inline_data_end()
ext4: check and update i_disksize properly

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Focal update: 5.10.74 upstream stable release

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 source package in Focal:
  New

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:

 5.10.74 upstream stable release
 from git://git.kernel.org/

  
  Linux 5.10.74
  hwmon: (pmbus/ibm-cffps) max_power_out swap changes
  sched: Always inline is_percpu_thread()
  perf/core: fix userpage->time_enabled of inactive events
  scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
  scsi: ses: Fix unsigned comparison with less than zero
  drm/amdgpu: fix gart.bo pin_count leak
  net: sun: SUNVNET_COMMON should depend on INET
  vboxfs: fix broken legacy mount signature checking
  mac80211: check return value of rhashtable_init
  net: prevent user from passing illegal stab size
  hwmon: (ltc2947) Properly handle errors when looking for the external clock
  m68k: Handle arrivals of multiple signals correctly
  mac80211: Drop frames from invalid MAC address in ad-hoc mode
  netfilter: nf_nat_masquerade: defer conntrack walk to work queue
  netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic
  ASoC: SOF: loader: release_firmware() on load failure to avoid batching
  HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs
  netfilter: ip6_tables: zero-initialize fragment offset
  HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
  ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic
  ext4: correct the error path of ext4_write_inline_data_end()
  ext4: check and update i_disksize properly

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


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

[Kernel-packages] [Bug 1949013] [NEW] Focal update: 5.10.71 upstream stable release

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

Public bug reported:


SRU Justification

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

   5.10.71 upstream stable release
   from git://git.kernel.org/


Linux 5.10.71
netfilter: nf_tables: Fix oversized kvmalloc() calls
netfilter: conntrack: serialize hash resizes and cleanups
KVM: x86: Handle SRCU initialization failure during page track init
HID: usbhid: free raw_report buffers in usbhid_stop
mm: don't allow oversized kvmalloc() calls
netfilter: ipset: Fix oversized kvmalloc() calls
HID: betop: fix slab-out-of-bounds Write in betop_probe
crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()
usb: hso: remove the bailout parameter
ASoC: dapm: use component prefix when checking widget names
net: udp: annotate data race around udp_sk(sk)->corkflag
HID: u2fzero: ignore incomplete packets without data
ext4: fix potential infinite loop in ext4_dx_readdir()
ext4: add error checking to ext4_ext_replay_set_iblocks()
ext4: fix reserved space counter leakage
ext4: limit the number of blocks in one ADD_RANGE TLV
ext4: fix loff_t overflow in ext4_max_bitmap_size()
ipack: ipoctal: fix module reference leak
ipack: ipoctal: fix missing allocation-failure check
ipack: ipoctal: fix tty-registration error handling
ipack: ipoctal: fix tty registration race
ipack: ipoctal: fix stack information leak
debugfs: debugfs_create_file_size(): use IS_ERR to check for error
elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings
nvme: add command id quirk for apple controllers
hwmon: (pmbus/mp2975) Add missed POUT attribute for page 1 mp2975 controller
perf/x86/intel: Update event constraints for ICX
af_unix: fix races in sk_peer_pid and sk_peer_cred accesses
net: sched: flower: protect fl_walk() with rcu
net: phy: bcm7xxx: Fixed indirect MMD operations
net: hns3: fix always enable rx vlan filter problem after selftest
net: hns3: reconstruct function hns3_self_test
net: hns3: fix prototype warning
net: hns3: fix show wrong state when add existing uc mac address
net: hns3: fix mixed flag HCLGE_FLAG_MQPRIO_ENABLE and HCLGE_FLAG_DCB_ENABLE
net: hns3: keep MAC pause mode when multiple TCs are enabled
net: hns3: do not allow call hns3_nic_net_open repeatedly
ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup
scsi: csiostor: Add module softdep on cxgb4
Revert "block, bfq: honor already-setup queue merges"
net: ks8851: fix link error
selftests, bpf: test_lwt_ip_encap: Really disable rp_filter
selftests, bpf: Fix makefile dependencies on libbpf
bpf: Exempt CAP_BPF from checks against bpf_jit_limit
RDMA/hns: Fix inaccurate prints
e100: fix buffer overrun in e100_get_regs
e100: fix length calculation in e100_get_regs_len
dsa: mv88e6xxx: Include tagger overhead when setting MTU for DSA and CPU ports
dsa: mv88e6xxx: Fix MTU definition
dsa: mv88e6xxx: 6161: Use chip wide MAX MTU
drm/i915/request: fix early tracepoints
smsc95xx: fix stalled rx after link change
net: ipv4: Fix rtnexthop len when RTA_FLOW is present
net: enetc: fix the incorrect clearing of IF_MODE bits
hwmon: (tmp421) fix rounding for negative values
hwmon: (tmp421) report /PVLD condition as fault
mptcp: don't return sockets in foreign netns
sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb
mac80211-hwsim: fix late beacon hrtimer handling
mac80211: mesh: fix potentially unaligned access
mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap
mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug
hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced 
from sysfs
bpf, mips: Validate conditional branch offsets
RDMA/cma: Fix listener leak in rdma_cma_listen_on_all() failure
IB/cma: Do not send IGMP leaves for sendonly Multicast groups
bpf: Handle return value of BPF_PROG_TYPE_STRUCT_OPS prog
ipvs: check that ip_vs_conn_tab_bits is between 8 and 20
drm/amdgpu: correct initial cp_hqd_quantum for gfx9
drm/amd/display: Pass PCI deviceid into DC
RDMA/cma: Do not change route.addr.src_addr.ss_family
media: ir_toy: prevent device from hanging during transmit
KVM: rseq: Update rseq when processing NOTIFY_RESUME on xfer to KVM guest
KVM: nVMX: Filter out all unsupported controls when eVMCS was activated
KVM: x86: nSVM: don't copy virt_ext from vmcb12
KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect()
x86/kvmclock: Move this_cpu_pvti into kvmclock.h
mac80211: fix use-after-free in CCMP/GCMP RX
scsi: ufs: Fix illegal offset in UPIU event trace
gpio: pca953x: do not ignore i2c errors
hwmon: (w83791d) Fix NULL

[Kernel-packages] [Bug 1949015] [NEW] Focal update: 5.10.72 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.72 upstream stable release
   from git://git.kernel.org/


Linux 5.10.72
libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD.
perf/x86: Reset destroy callback on event init failure
KVM: x86: nSVM: restore int_vector in svm_clear_vintr
kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[]
KVM: do not shrink halt_poll_ns below grow_start
selftests: KVM: Align SMCCC call with the spec in steal_time
tools/vm/page-types: remove dependency on opt_file for idle page tracking
smb3: correct smb3 ACL security descriptor
irqchip/gic: Work around broken Renesas integration
scsi: ses: Retry failed Send/Receive Diagnostic commands
thermal/drivers/tsens: Fix wrong check for tzd in irq handlers
nvme-fc: avoid race between time out and tear down
nvme-fc: update hardware queues before using them
selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn
selftests: be sure to make khdr before other targets
habanalabs/gaudi: fix LBW RR configuration
usb: dwc2: check return value after calling platform_get_resource()
usb: testusb: Fix for showing the connection speed
scsi: sd: Free scsi_disk device via put_device()
ext2: fix sleeping in atomic bugs on error
sparc64: fix pci_iounmap() when CONFIG_PCI is not set
xen-netback: correct success/error reporting for the SKB-with-fraglist case
net: mdio: introduce a shutdown method to mdio device drivers
btrfs: fix mount failure due to past and transient device flush error
btrfs: replace BUG_ON() in btrfs_csum_one_bio() with proper error handling
nfsd: back channel stuck in SEQ4_STATUS_CB_PATH_DOWN
platform/x86: touchscreen_dmi: Update info for the Chuwi Hi10 Plus (CWI527) 
tablet
platform/x86: touchscreen_dmi: Add info for the Chuwi HiBook (CWI514) tablet
spi: rockchip: handle zero length transfers without timing out

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Focal update: 5.10.72 upstream stable release

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 source package in Focal:
  New

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:

 5.10.72 upstream stable release
 from git://git.kernel.org/

  
  Linux 5.10.72
  libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD.
  perf/x86: Reset destroy callback on event init failure
  KVM: x86: nSVM: restore int_vector in svm_clear_vintr
  kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[]
  KVM: do not shrink halt_poll_ns below grow_start
  selftests: KVM: Align SMCCC call with the spec in steal_time
  tools/vm/page-types: remove dependency on opt_file for idle page tracking
  smb3: correct smb3 ACL security descriptor
  irqchip/gic: Work around broken Renesas integration
  scsi: ses: Retry failed Send/Receive Diagnostic commands
  thermal/drivers/tsens: Fix wrong check for tzd in irq handlers
  nvme-fc: avoid race between time out and tear down
  nvme-fc: update hardware queues before using them
  selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn
  selftests: be sure to make khdr before other targets
  habanalabs/gaudi: fix LBW RR configuration
  usb: dwc2: check return value after calling platform_get_resource()
  usb: testusb: Fix for showing the connection speed
  scsi: sd: Free scsi_disk device via put_device()
  ext2: fix sleeping in atomic bugs on error
  sparc64: fix pci_iounmap() when CONFIG_PCI is not set
  xen-netback: correct success/error reporting for the SKB-with-fraglist case
  net: mdio: introduce a shutdown method to mdio device drivers

[Kernel-packages] [Bug 1949016] [NEW] Focal update: 5.10.73 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.73 upstream stable release
   from git://git.kernel.org/


Linux 5.10.73
x86/hpet: Use another crystalball to evaluate HPET usability
x86/entry: Clear X86_FEATURE_SMAP when CONFIG_X86_SMAP=n
x86/entry: Correct reference to intended CONFIG_64_BIT
x86/sev: Return an error on a returned non-zero SW_EXITINFO1[31:0]
x86/Kconfig: Correct reference to MWINCHIP3D
x86/platform/olpc: Correct ifdef symbol to intended CONFIG_OLPC_XO15_SCI
pseries/eeh: Fix the kdump kernel crash during eeh_pseries_init
powerpc/64s: fix program check interrupt emergency stack path
powerpc/bpf: Fix BPF_SUB when imm == 0x8000
RISC-V: Include clone3() on rv32
bpf, s390: Fix potential memory leak about jit_data
riscv/vdso: make arch_setup_additional_pages wait for mmap_sem for write 
killable
i2c: mediatek: Add OFFSET_EXT_CONF setting back
i2c: acpi: fix resource leak in reconfiguration device addition
powerpc/iommu: Report the correct most efficient DMA mask for PCI devices
net: prefer socket bound to interface when not in VRF
i40e: Fix freeing of uninitialized misc IRQ vector
i40e: fix endless loop under rtnl
gve: report 64bit tx_bytes counter from gve_handle_report_stats()
gve: fix gve_get_stats()
rtnetlink: fix if_nlmsg_stats_size() under estimation
gve: Avoid freeing NULL pointer
gve: Correct available tx qpl check
drm/nouveau/debugfs: fix file release memory leak
drm/nouveau/kms/nv50-: fix file release memory leak
drm/nouveau: avoid a use-after-free when BO init fails
video: fbdev: gbefb: Only instantiate device when built for IP32
drm/sun4i: dw-hdmi: Fix HDMI PHY clock setup
bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893
perf jevents: Tidy error handling
netlink: annotate data races around nlk->bound
net: sfp: Fix typo in state machine debug string
net/sched: sch_taprio: properly cancel timer from taprio_destroy()
net: bridge: fix under estimation in br_get_linkxstats_size()
net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size()
ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence
dt-bindings: drm/bridge: ti-sn65dsi86: Fix reg value
arm64: dts: ls1028a: add missing CAN nodes
ptp_pch: Load module automatically if ID matches
powerpc/fsl/dts: Fix phy-connection-type for fm1mac3
net_sched: fix NULL deref in fifo_set_limit()
phy: mdio: fix memory leak
net/mlx5: E-Switch, Fix double allocation of acl flow counter
net/mlx5e: IPSEC RX, enable checksum complete
bpf: Fix integer overflow in prealloc_elems_and_freelist()
soc: ti: omap-prm: Fix external abort for am335x pruss
bpf, arm: Fix register clobbering in div/mod implementation
iwlwifi: pcie: add configuration of a Wi-Fi adapter on Dell XPS 15
xtensa: call irqchip_init only when CONFIG_USE_OF is selected
xtensa: use CONFIG_USE_OF instead of CONFIG_OF
arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding
ath5k: fix building with LEDS=m
PCI: hv: Fix sleep while in non-sleep context when removing child devices from 
the bus
ARM: dts: imx6qdl-pico: Fix Ethernet support
ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo
ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo
soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment
ARM: at91: pm: do not panic if ram controllers are not enabled
ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference
soc: qcom: socinfo: Fixed argument passed to platform_set_data()
bus: ti-sysc: Add break in switch statement in sysc_init_soc()
riscv: Flush current cpu icache before other cpus
ARM: dts: qcom: apq8064: use compatible which contains chipid
ARM: dts: imx6dl-yapp4: Fix lp5562 LED driver probe
ARM: dts: omap3430-sdp: Fix NAND device node
xen/balloon: fix cancelled balloon action
SUNRPC: fix sign error causing rpcsec_gss drops
nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero
nfsd: fix error handling of register_pernet_subsys() in init_nfsd()
ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO
ovl: fix missing negative dentry check in ovl_rename()
mmc: sdhci-of-at91: replace while loop with read_poll_timeout
mmc: sdhci-of-at91: wait for calibration done before proceed
mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk
xen/privcmd: fix error handling in mmap-resource processing
drm/nouveau/kms/tu102-: delay enabling cursor until after assign_windows
usb: typec: tcpm: handle SRC_STARTUP state if cc changes
USB: cdc-acm: fix break reporting
USB: cdc-acm: fix racy tty buffer accesses
usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle

[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.

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

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

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

Title:
  Failed to properly resume from S3 (suspend-to-ram) on kernel version
  5.13.0-16 (installed while updating to impish), amdgpu driver.

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  On 5.11.0 everything is OK.
  The GPU is AMD Carrizo APU.

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


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

[Kernel-packages] [Bug 1949011] [NEW] Focal update: 5.10.71 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.71 upstream stable release
   from git://git.kernel.org/


Linux 5.10.71
netfilter: nf_tables: Fix oversized kvmalloc() calls
netfilter: conntrack: serialize hash resizes and cleanups
KVM: x86: Handle SRCU initialization failure during page track init
HID: usbhid: free raw_report buffers in usbhid_stop
mm: don't allow oversized kvmalloc() calls
netfilter: ipset: Fix oversized kvmalloc() calls
HID: betop: fix slab-out-of-bounds Write in betop_probe
crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()
usb: hso: remove the bailout parameter
ASoC: dapm: use component prefix when checking widget names
net: udp: annotate data race around udp_sk(sk)->corkflag
HID: u2fzero: ignore incomplete packets without data
ext4: fix potential infinite loop in ext4_dx_readdir()
ext4: add error checking to ext4_ext_replay_set_iblocks()
ext4: fix reserved space counter leakage
ext4: limit the number of blocks in one ADD_RANGE TLV
ext4: fix loff_t overflow in ext4_max_bitmap_size()
ipack: ipoctal: fix module reference leak
ipack: ipoctal: fix missing allocation-failure check
ipack: ipoctal: fix tty-registration error handling
ipack: ipoctal: fix tty registration race
ipack: ipoctal: fix stack information leak
debugfs: debugfs_create_file_size(): use IS_ERR to check for error
elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings
nvme: add command id quirk for apple controllers
hwmon: (pmbus/mp2975) Add missed POUT attribute for page 1 mp2975 controller
perf/x86/intel: Update event constraints for ICX
af_unix: fix races in sk_peer_pid and sk_peer_cred accesses
net: sched: flower: protect fl_walk() with rcu
net: phy: bcm7xxx: Fixed indirect MMD operations
net: hns3: fix always enable rx vlan filter problem after selftest
net: hns3: reconstruct function hns3_self_test
net: hns3: fix prototype warning
net: hns3: fix show wrong state when add existing uc mac address
net: hns3: fix mixed flag HCLGE_FLAG_MQPRIO_ENABLE and HCLGE_FLAG_DCB_ENABLE
net: hns3: keep MAC pause mode when multiple TCs are enabled
net: hns3: do not allow call hns3_nic_net_open repeatedly
ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup
scsi: csiostor: Add module softdep on cxgb4
Revert "block, bfq: honor already-setup queue merges"
net: ks8851: fix link error
selftests, bpf: test_lwt_ip_encap: Really disable rp_filter
selftests, bpf: Fix makefile dependencies on libbpf
bpf: Exempt CAP_BPF from checks against bpf_jit_limit
RDMA/hns: Fix inaccurate prints
e100: fix buffer overrun in e100_get_regs
e100: fix length calculation in e100_get_regs_len
dsa: mv88e6xxx: Include tagger overhead when setting MTU for DSA and CPU ports
dsa: mv88e6xxx: Fix MTU definition
dsa: mv88e6xxx: 6161: Use chip wide MAX MTU
drm/i915/request: fix early tracepoints
smsc95xx: fix stalled rx after link change
net: ipv4: Fix rtnexthop len when RTA_FLOW is present
net: enetc: fix the incorrect clearing of IF_MODE bits
hwmon: (tmp421) fix rounding for negative values
hwmon: (tmp421) report /PVLD condition as fault
mptcp: don't return sockets in foreign netns
sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb
mac80211-hwsim: fix late beacon hrtimer handling
mac80211: mesh: fix potentially unaligned access
mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap
mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug
hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced 
from sysfs
bpf, mips: Validate conditional branch offsets
RDMA/cma: Fix listener leak in rdma_cma_listen_on_all() failure
IB/cma: Do not send IGMP leaves for sendonly Multicast groups
bpf: Handle return value of BPF_PROG_TYPE_STRUCT_OPS prog
ipvs: check that ip_vs_conn_tab_bits is between 8 and 20
drm/amdgpu: correct initial cp_hqd_quantum for gfx9
drm/amd/display: Pass PCI deviceid into DC
RDMA/cma: Do not change route.addr.src_addr.ss_family
media: ir_toy: prevent device from hanging during transmit
KVM: rseq: Update rseq when processing NOTIFY_RESUME on xfer to KVM guest
KVM: nVMX: Filter out all unsupported controls when eVMCS was activated
KVM: x86: nSVM: don't copy virt_ext from vmcb12
KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect()
x86/kvmclock: Move this_cpu_pvti into kvmclock.h
mac80211: fix use-after-free in CCMP/GCMP RX
scsi: ufs: Fix illegal offset in UPIU event trace
gpio: pca953x: do not ignore i2c errors
hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure 
field
hwmon: (w83792d) Fix NULL pointer

[Kernel-packages] [Bug 1949009] [NEW] Focal update: 5.10.71 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.71 upstream stable release
   from git://git.kernel.org/


Linux 5.10.71
netfilter: nf_tables: Fix oversized kvmalloc() calls
netfilter: conntrack: serialize hash resizes and cleanups
KVM: x86: Handle SRCU initialization failure during page track init
HID: usbhid: free raw_report buffers in usbhid_stop
mm: don't allow oversized kvmalloc() calls
netfilter: ipset: Fix oversized kvmalloc() calls
HID: betop: fix slab-out-of-bounds Write in betop_probe
crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()
usb: hso: remove the bailout parameter
ASoC: dapm: use component prefix when checking widget names
net: udp: annotate data race around udp_sk(sk)->corkflag
HID: u2fzero: ignore incomplete packets without data
ext4: fix potential infinite loop in ext4_dx_readdir()
ext4: add error checking to ext4_ext_replay_set_iblocks()
ext4: fix reserved space counter leakage
ext4: limit the number of blocks in one ADD_RANGE TLV
ext4: fix loff_t overflow in ext4_max_bitmap_size()
ipack: ipoctal: fix module reference leak
ipack: ipoctal: fix missing allocation-failure check
ipack: ipoctal: fix tty-registration error handling
ipack: ipoctal: fix tty registration race
ipack: ipoctal: fix stack information leak
debugfs: debugfs_create_file_size(): use IS_ERR to check for error
elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings
nvme: add command id quirk for apple controllers
hwmon: (pmbus/mp2975) Add missed POUT attribute for page 1 mp2975 controller
perf/x86/intel: Update event constraints for ICX
af_unix: fix races in sk_peer_pid and sk_peer_cred accesses
net: sched: flower: protect fl_walk() with rcu
net: phy: bcm7xxx: Fixed indirect MMD operations
net: hns3: fix always enable rx vlan filter problem after selftest
net: hns3: reconstruct function hns3_self_test
net: hns3: fix prototype warning
net: hns3: fix show wrong state when add existing uc mac address
net: hns3: fix mixed flag HCLGE_FLAG_MQPRIO_ENABLE and HCLGE_FLAG_DCB_ENABLE
net: hns3: keep MAC pause mode when multiple TCs are enabled
net: hns3: do not allow call hns3_nic_net_open repeatedly
ixgbe: Fix NULL pointer dereference in ixgbe_xdp_setup
scsi: csiostor: Add module softdep on cxgb4
Revert "block, bfq: honor already-setup queue merges"
net: ks8851: fix link error
selftests, bpf: test_lwt_ip_encap: Really disable rp_filter
selftests, bpf: Fix makefile dependencies on libbpf
bpf: Exempt CAP_BPF from checks against bpf_jit_limit
RDMA/hns: Fix inaccurate prints
e100: fix buffer overrun in e100_get_regs
e100: fix length calculation in e100_get_regs_len
dsa: mv88e6xxx: Include tagger overhead when setting MTU for DSA and CPU ports
dsa: mv88e6xxx: Fix MTU definition
dsa: mv88e6xxx: 6161: Use chip wide MAX MTU
drm/i915/request: fix early tracepoints
smsc95xx: fix stalled rx after link change
net: ipv4: Fix rtnexthop len when RTA_FLOW is present
net: enetc: fix the incorrect clearing of IF_MODE bits
hwmon: (tmp421) fix rounding for negative values
hwmon: (tmp421) report /PVLD condition as fault
mptcp: don't return sockets in foreign netns
sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb
mac80211-hwsim: fix late beacon hrtimer handling
mac80211: mesh: fix potentially unaligned access
mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap
mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug
hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced 
from sysfs
bpf, mips: Validate conditional branch offsets
RDMA/cma: Fix listener leak in rdma_cma_listen_on_all() failure
IB/cma: Do not send IGMP leaves for sendonly Multicast groups
bpf: Handle return value of BPF_PROG_TYPE_STRUCT_OPS prog
ipvs: check that ip_vs_conn_tab_bits is between 8 and 20
drm/amdgpu: correct initial cp_hqd_quantum for gfx9
drm/amd/display: Pass PCI deviceid into DC
RDMA/cma: Do not change route.addr.src_addr.ss_family
media: ir_toy: prevent device from hanging during transmit
KVM: rseq: Update rseq when processing NOTIFY_RESUME on xfer to KVM guest
KVM: nVMX: Filter out all unsupported controls when eVMCS was activated
KVM: x86: nSVM: don't copy virt_ext from vmcb12
KVM: x86: Fix stack-out-of-bounds memory access from ioapic_write_indirect()
x86/kvmclock: Move this_cpu_pvti into kvmclock.h
mac80211: fix use-after-free in CCMP/GCMP RX
scsi: ufs: Fix illegal offset in UPIU event trace
gpio: pca953x: do not ignore i2c errors
hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure 
field
hwmon: (w83792d) Fix NULL pointer

[Kernel-packages] [Bug 1949008] [NEW] Focal update: 5.10.70 upstream stable release

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

Public bug reported:


SRU Justification

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

   5.10.70 upstream stable release
   from git://git.kernel.org/


Linux 5.10.70
qnx4: work around gcc false positive warning bug
xen/balloon: fix balloon kthread freezing
USB: serial: cp210x: fix dropped characters with CP2102
thermal/drivers/int340x: Do not set a wrong tcc offset on resume
EDAC/dmc520: Assign the proper type to dimm->edac_mode
EDAC/synopsys: Fix wrong value type assignment for edac_mode
spi: Fix tegra20 build with CONFIG_PM=n
net: 6pack: Fix tx timeout and slot time
alpha: Declare virt_to_phys and virt_to_bus parameter as pointer to volatile
arm64: Mark __stack_chk_guard as __ro_after_init
parisc: Use absolute_pointer() to define PAGE0
qnx4: avoid stringop-overread errors
sparc: avoid stringop-overread errors
net: i825xx: Use absolute_pointer for memcpy from fixed memory location
compiler.h: Introduce absolute_pointer macro
blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd
block: flush the integrity workqueue in blk_integrity_unregister
block: check if a profile is actually registered in blk_integrity_unregister
amd/display: downgrade validation failure log level
sparc32: page align size in arch_dma_alloc
nvme-rdma: destroy cm id before destroy qp to avoid use after free
nvme-multipath: fix ANA state updates when a namespace is not present
xen/balloon: use a kernel thread instead a workqueue
bpf: Add oversize check before call kvcalloc()
cpufreq: intel_pstate: Override parameters if HWP forced by BIOS
ipv6: delay fib6_sernum increase in fib6_add
m68k: Double cast io functions to unsigned long
blk-mq: avoid to iterate over stale request
net: stmmac: allow CSR clock of 300MHz
net: macb: fix use after free on rmmod
net: phylink: Update SFP selected interface on advertising changes
blktrace: Fix uaf in blk_trace access after removing by sysfs
io_uring: put provided buffer meta data under memcg accounting
x86/asm: Fix SETZ size enqcmds() build failure
x86/asm: Add a missing __iomem annotation in enqcmds()
md: fix a lock order reversal in md_alloc
irqchip/gic-v3-its: Fix potential VPE leak on error
irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build
scsi: lpfc: Use correct scnprintf() limit
scsi: qla2xxx: Restore initiator in dual mode
cifs: fix a sign extension bug
thermal/core: Potential buffer overflow in thermal_build_list_of_policies()
nvme: keep ctrl->namespaces ordered
treewide: Change list_sort to use const pointers
nvme-tcp: fix incorrect h2cdata pdu offset accounting
fpga: machxo2-spi: Fix missing error code in machxo2_write_complete()
fpga: machxo2-spi: Return an error on failure
tty: synclink_gt: rename a conflicting function name
tty: synclink_gt, drop unneeded forward declarations
scsi: target: Fix the pgr/alua_support_store functions
scsi: iscsi: Adjust iface sysfs attr detection
atlantic: Fix issue in the pm resume flow.
net/mlx4_en: Don't allow aRFS for encapsulated packets
qed: rdma - don't wait for resources under hw error recovery flow
gpio: uniphier: Fix void functions to remove return value
s390/qeth: fix NULL deref in qeth_clear_working_pool_list()
kselftest/arm64: signal: Skip tests if required features are missing
kselftest/arm64: signal: Add SVE to the set of features we can check for
net: dsa: realtek: register the MDIO bus under devres
net: dsa: don't allocate the slave_mii_bus using devres
net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work
net/smc: add missing error check in smc_clc_prfx_set()
net: hns3: check queue id range before using
net: hns3: fix change RSS 'hfunc' ineffective issue
bnxt_en: Fix TX timeout when TX ring size is set to the smallest
enetc: Fix uninitialized struct dim_sample field usage
enetc: Fix illegal access when reading affinity_hint
platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR()
afs: Fix updating of i_blocks on file/dir extension
afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation
comedi: Fix memory leak in compat_insnlist()
net: hso: fix muxed tty registration
drm/amd/pm: Update intermediate power state for SI
scsi: sd_zbc: Ensure buffer size is aligned to SECTOR_SIZE
serial: mvebu-uart: fix driver's tx_empty callback
serial: 8250: 8250_omap: Fix RX_LVL register offset
xhci: Set HCD flag to defer primary roothub registration
btrfs: prevent __btrfs_dump_space_info() to underflow its free space
erofs: fix up erofs_lookup tracepoint
mcb: fix error handling in mcb_alloc_bus()
USB: serial: option: add

[Kernel-packages] [Bug 1949006] [NEW] Focal update: 5.10.69 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.69 upstream stable release
   from git://git.kernel.org/


Linux 5.10.69
drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
sched/idle: Make the idle timer expire in hard interrupt context
rtc: rx8010: select REGMAP_I2C
blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues
blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
pwm: stm32-lp: Don't modify HW state in .remove() callback
pwm: rockchip: Don't modify HW state in .remove() callback
pwm: img: Don't modify HW state in .remove() callback
habanalabs: add validity check for event ID received from F/W
nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
nilfs2: fix NULL pointer in nilfs_##name##_attr_release
nilfs2: fix memory leak in nilfs_sysfs_create_device_group
btrfs: fix lockdep warning while mounting sprout fs
btrfs: update the bdev time directly when closing
ceph: lockdep annotations for try_nonblocking_invalidate
ceph: remove the capsnaps when removing caps
ceph: request Fw caps before updating the mtime in ceph_write_iter
dmaengine: xilinx_dma: Set DMA mask for coherent APIs
dmaengine: ioat: depends on !UML
dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
dmaengine: idxd: depends on !UML
iommu/amd: Relocate GAMSup check to early_enable_iommus
parisc: Move pci_dev_is_behind_card_dino to where it is used
dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
thermal/core: Fix thermal_cooling_device_register() prototype
tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh
Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
ceph: cancel delayed work instead of flushing on mdsc teardown
ceph: allow ceph_put_mds_session to take NULL or ERR_PTR
platform/chrome: cros_ec_trace: Fix format warnings
platform/chrome: sensorhub: Add trace events for sample
dmaengine: idxd: fix wq slot allocation index check
pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered
pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
PM: sleep: core: Avoid setting power.must_resume to false
profiling: fix shift-out-of-bounds bugs
nilfs2: use refcount_dec_and_lock() to fix potential UAF
prctl: allow to setup brk for et_dyn executables
9p/trans_virtio: Remove sysfs file on probe failure
thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
perf tools: Allow build-id with trailing zeros
tools lib: Adopt memchr_inv() from kernel
perf test: Fix bpf test sample mismatch reporting
dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
um: virtio_uml: fix memory leak on init failures
coredump: fix memleak in dump_vma_snapshot()
staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
sctp: validate chunk size in __rcv_asconf_lookup
Revert "net/mlx5: Register to devlink ingress VLAN filter trap"
ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
ARM: 9079/1: ftrace: Add MODULE_PLTS support
ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
ARM: 9077/1: PLT: Move struct plt_entries definition to header
ARM: Qualify enabling of swiotlb_init()
s390/pci_mmio: fully validate the VMA before calling follow_pte()
console: consume APC, DM, DCS
PCI: aardvark: Fix reporting CRS value
PCI: pci-bridge-emul: Add PCIe Root Capabilities Register

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

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


** Tags: kernel-stable-tracking-bug

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

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

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

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

Title:
  Focal update: 5.10.69 upstream stable release

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 source package in Focal:
  New

Bug description:
  
  SRU Justification

[Kernel-packages] [Bug 1949007] [NEW] Focal update: 5.10.70 upstream stable release

Public bug reported:


SRU Justification

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

   5.10.70 upstream stable release
   from git://git.kernel.org/


Linux 5.10.70
qnx4: work around gcc false positive warning bug
xen/balloon: fix balloon kthread freezing
USB: serial: cp210x: fix dropped characters with CP2102
thermal/drivers/int340x: Do not set a wrong tcc offset on resume
EDAC/dmc520: Assign the proper type to dimm->edac_mode
EDAC/synopsys: Fix wrong value type assignment for edac_mode
spi: Fix tegra20 build with CONFIG_PM=n
net: 6pack: Fix tx timeout and slot time
alpha: Declare virt_to_phys and virt_to_bus parameter as pointer to volatile
arm64: Mark __stack_chk_guard as __ro_after_init
parisc: Use absolute_pointer() to define PAGE0
qnx4: avoid stringop-overread errors
sparc: avoid stringop-overread errors
net: i825xx: Use absolute_pointer for memcpy from fixed memory location
compiler.h: Introduce absolute_pointer macro
blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd
block: flush the integrity workqueue in blk_integrity_unregister
block: check if a profile is actually registered in blk_integrity_unregister
amd/display: downgrade validation failure log level
sparc32: page align size in arch_dma_alloc
nvme-rdma: destroy cm id before destroy qp to avoid use after free
nvme-multipath: fix ANA state updates when a namespace is not present
xen/balloon: use a kernel thread instead a workqueue
bpf: Add oversize check before call kvcalloc()
cpufreq: intel_pstate: Override parameters if HWP forced by BIOS
ipv6: delay fib6_sernum increase in fib6_add
m68k: Double cast io functions to unsigned long
blk-mq: avoid to iterate over stale request
net: stmmac: allow CSR clock of 300MHz
net: macb: fix use after free on rmmod
net: phylink: Update SFP selected interface on advertising changes
blktrace: Fix uaf in blk_trace access after removing by sysfs
io_uring: put provided buffer meta data under memcg accounting
x86/asm: Fix SETZ size enqcmds() build failure
x86/asm: Add a missing __iomem annotation in enqcmds()
md: fix a lock order reversal in md_alloc
irqchip/gic-v3-its: Fix potential VPE leak on error
irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build
scsi: lpfc: Use correct scnprintf() limit
scsi: qla2xxx: Restore initiator in dual mode
cifs: fix a sign extension bug
thermal/core: Potential buffer overflow in thermal_build_list_of_policies()
nvme: keep ctrl->namespaces ordered
treewide: Change list_sort to use const pointers
nvme-tcp: fix incorrect h2cdata pdu offset accounting
fpga: machxo2-spi: Fix missing error code in machxo2_write_complete()
fpga: machxo2-spi: Return an error on failure
tty: synclink_gt: rename a conflicting function name
tty: synclink_gt, drop unneeded forward declarations
scsi: target: Fix the pgr/alua_support_store functions
scsi: iscsi: Adjust iface sysfs attr detection
atlantic: Fix issue in the pm resume flow.
net/mlx4_en: Don't allow aRFS for encapsulated packets
qed: rdma - don't wait for resources under hw error recovery flow
gpio: uniphier: Fix void functions to remove return value
s390/qeth: fix NULL deref in qeth_clear_working_pool_list()
kselftest/arm64: signal: Skip tests if required features are missing
kselftest/arm64: signal: Add SVE to the set of features we can check for
net: dsa: realtek: register the MDIO bus under devres
net: dsa: don't allocate the slave_mii_bus using devres
net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work
net/smc: add missing error check in smc_clc_prfx_set()
net: hns3: check queue id range before using
net: hns3: fix change RSS 'hfunc' ineffective issue
bnxt_en: Fix TX timeout when TX ring size is set to the smallest
enetc: Fix uninitialized struct dim_sample field usage
enetc: Fix illegal access when reading affinity_hint
platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR()
afs: Fix updating of i_blocks on file/dir extension
afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation
comedi: Fix memory leak in compat_insnlist()
net: hso: fix muxed tty registration
drm/amd/pm: Update intermediate power state for SI
scsi: sd_zbc: Ensure buffer size is aligned to SECTOR_SIZE
serial: mvebu-uart: fix driver's tx_empty callback
serial: 8250: 8250_omap: Fix RX_LVL register offset
xhci: Set HCD flag to defer primary roothub registration
btrfs: prevent __btrfs_dump_space_info() to underflow its free space
erofs: fix up erofs_lookup tracepoint
mcb: fix error handling in mcb_alloc_bus()
USB: serial: option: add device id for Foxconn T99W265
USB: serial: option: remove duplicate USB device ID
USB:

[Kernel-packages] [Bug 1941893] Re: Improve performance and idle power consumption

2021-10-27 Thread Alex Hung

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

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

Title:
  Improve performance and idle power consumption

Status in amd:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

This can improve AMD performance for all Zen or newer CPU which support C3 
shares cache.

  [Fix]

Its not necessary to flush the caches in software before entering
  C3.

Empirical measurements show:
 40-45% improvement in speedometer score.
 ~15% improvement in idle power.

The patch is in linux-next (tag next-20211007) and can be found @
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  
next.git/commit/arch/x86/kernel/acpi/cstate.c?id=a8fb40966f19ff81520d9ccf8f7e2b95201368b8

  [Test]

This is requested by AMD.

  [Where problems could occur]

Low risk. This only works on AMD Zen CPUs that supports this
  features. AMD tested it and provided estimated measurement results.

   Original descriptions 

  A patch queued for 5.15 to change the C3 entry will improve AMD performance.
  https://lore.kernel.org/patchwork/patch/1478776/

  Empirical measurements show:
   40-45% improvement in speedometer score.
   ~15% improvement in idle power.

  Can you please include in 5.13-oem and 5.14-oem kernels?

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


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

[Kernel-packages] [Bug 1945361] Re: [Yellow Carp] USB4 interdomain communication problems

2021-10-27 Thread Alex Hung

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

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

Title:
  [Yellow Carp] USB4 interdomain communication problems

Status in amd:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

Yellow carp w/ SW CM bi-directional interdomain communication may
  have some problems that the response packets are lost sometimes within
  the stipulated time.

  [Fix]

Enable the retry by increasing retry count from 1 to 4.

The patch is in linux-next (tag next-20211007) and can be found @ 
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3
   
  [Test]

This is requested and tested by AMD.

  [Where problems could occur]

Low risk. This only affects small number of AMD systems that would
  excess the time. Systems without problems won't be affected.

  = Original Description 

  AMD internal team has found that for Yellow carp w/ SW CM bi-
  directional interdomain communication may have some problems.  It's
  been aligned upstream to increase number of retries to account for
  these issues.

  
https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3

  Can Canonical team please include this in future 5.14-OEM?

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


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

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-10-27 Thread Colin Ian King

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => (unassigned)

** Changed in: zfs-linux (Ubuntu Impish)
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Confirmed
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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

[Kernel-packages] [Bug 1947885] Re: Focal update: v5.4.149 upstream stable release

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

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

Title:
  Focal update: v5.4.149 upstream stable release

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

Bug description:
  SRU Justification

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

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

  PCI: pci-bridge-emul: Fix big-endian support
  PCI: aardvark: Indicate error in 'val' when config read fails
  PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
  PCI: aardvark: Fix reporting CRS value
  PCI/ACPI: Add Ampere Altra SOC MCFG quirk
  KVM: remember position in kvm->vcpus array
  console: consume APC, DM, DCS
  s390/pci_mmio: fully validate the VMA before calling follow_pte()
  ARM: Qualify enabling of swiotlb_init()
  apparmor: remove duplicate macro list_entry_is_head()
  ARM: 9077/1: PLT: Move struct plt_entries definition to header
  ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
  ARM: 9079/1: ftrace: Add MODULE_PLTS support
  ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
  sctp: validate chunk size in __rcv_asconf_lookup
  sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
  staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
  um: virtio_uml: fix memory leak on init failures
  dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
  thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
  9p/trans_virtio: Remove sysfs file on probe failure
  prctl: allow to setup brk for et_dyn executables
  nilfs2: use refcount_dec_and_lock() to fix potential UAF
  profiling: fix shift-out-of-bounds bugs
  pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
  phy: avoid unnecessary link-up delay in polling mode
  net: stmmac: reset Tx desc base address before restarting Tx
  Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
  thermal/core: Fix thermal_cooling_device_register() prototype
  drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
  parisc: Move pci_dev_is_behind_card_dino to where it is used
  dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
  dmaengine: ioat: depends on !UML
  dmaengine: xilinx_dma: Set DMA mask for coherent APIs
  ceph: request Fw caps before updating the mtime in ceph_write_iter
  ceph: lockdep annotations for try_nonblocking_invalidate
  btrfs: fix lockdep warning while mounting sprout fs
  nilfs2: fix memory leak in nilfs_sysfs_create_device_group
  nilfs2: fix NULL pointer in nilfs_##name##_attr_release
  nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
  pwm: img: Don't modify HW state in .remove() callback
  pwm: rockchip: Don't modify HW state in .remove() callback
  pwm: stm32-lp: Don't modify HW state in .remove() callback
  blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
  rtc: rx8010: select REGMAP_I2C
  drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
  Linux 5.4.149
  UBUNTU: upstream stable to v5.4.149

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


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

[Kernel-packages] [Bug 1947886] Re: Focal update: v5.4.150 upstream stable release

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

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

Title:
  Focal update: v5.4.150 upstream stable release

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

Bug description:
  SRU Justification

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

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

  ocfs2: drop acl cache for directories too
  usb: gadget: r8a66597: fix a loop in set_feature()
  usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave
  usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA
  usb: musb: tusb6010: uninitialized data in tusb_fifo_write_unaligned()
  cifs: fix incorrect check for null pointer in header_assemble
  xen/x86: fix PV trap handling on secondary processors
  usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c
  USB: serial: cp210x: add ID for GW Instek GDM-834x Digital Multimeter
  USB: cdc-acm: fix minor-number release
  binder: make sure fd closes complete
  staging: greybus: uart: fix tty use after free
  Re-enable UAS for LaCie Rugged USB3-FW with fk quirk
  USB: serial: mos7840: remove duplicated 0xac24 device ID
  USB: serial: option: add Telit LN920 compositions
  USB: serial: option: remove duplicate USB device ID
  USB: serial: option: add device id for Foxconn T99W265
  mcb: fix error handling in mcb_alloc_bus()
  erofs: fix up erofs_lookup tracepoint
  btrfs: prevent __btrfs_dump_space_info() to underflow its free space
  serial: mvebu-uart: fix driver's tx_empty callback
  net: hso: fix muxed tty registration
  afs: Fix incorrect triggering of sillyrename on 3rd-party invalidation
  platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR()
  enetc: Fix illegal access when reading affinity_hint
  bnxt_en: Fix TX timeout when TX ring size is set to the smallest
  net/smc: add missing error check in smc_clc_prfx_set()
  gpio: uniphier: Fix void functions to remove return value
  qed: rdma - don't wait for resources under hw error recovery flow
  net/mlx4_en: Don't allow aRFS for encapsulated packets
  scsi: iscsi: Adjust iface sysfs attr detection
  tty: synclink_gt, drop unneeded forward declarations
  tty: synclink_gt: rename a conflicting function name
  fpga: machxo2-spi: Return an error on failure
  fpga: machxo2-spi: Fix missing error code in machxo2_write_complete()
  thermal/core: Potential buffer overflow in thermal_build_list_of_policies()
  cifs: fix a sign extension bug
  scsi: qla2xxx: Restore initiator in dual mode
  scsi: lpfc: Use correct scnprintf() limit
  irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build
  irqchip/gic-v3-its: Fix potential VPE leak on error
  md: fix a lock order reversal in md_alloc
  blktrace: Fix uaf in blk_trace access after removing by sysfs
  net: macb: fix use after free on rmmod
  net: stmmac: allow CSR clock of 300MHz
  m68k: Double cast io functions to unsigned long
  ipv6: delay fib6_sernum increase in fib6_add
  bpf: Add oversize check before call kvcalloc()
  xen/balloon: use a kernel thread instead a workqueue
  nvme-multipath: fix ANA state updates when a namespace is not present
  sparc32: page align size in arch_dma_alloc
  blk-cgroup: fix UAF by grabbing blkcg lock before destroying blkg pd
  compiler.h: Introduce absolute_pointer macro
  net: i825xx: Use absolute_pointer for memcpy from fixed memory location
  sparc: avoid stringop-overread errors
  qnx4: avoid stringop-overread errors
  parisc: Use absolute_pointer() to define PAGE0
  arm64: Mark __stack_chk_guard as __ro_after_init
  alpha: Declare virt_to_phys and virt_to_bus parameter as pointer to volatile
  net: 6pack: Fix tx timeout and slot time
  spi: Fix tegra20 build with CONFIG_PM=n
  EDAC/synopsys: Fix wrong value type assignment for edac_mode
  thermal/drivers/int340x: Do not set a wrong tcc offset on resume
  arm64: dts: marvell: armada-37xx: Extend PCIe MEM space
  xen/balloon: fix balloon kthread freezing
  qnx4: work around gcc false positive warning bug
  Linux 5.4.150
  UBUNTU: upstream stable to v5.4.150

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


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

[Kernel-packages] [Bug 1947888] Re: Focal update: v5.4.151 upstream stable release

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

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

Title:
  Focal update: v5.4.151 upstream stable release

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

Bug description:
  SRU Justification

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

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

  tty: Fix out-of-bound vmalloc access in imageblit
  cpufreq: schedutil: Use kobject release() method to free sugov_tunables
  cpufreq: schedutil: Destroy mutex before kobject_put() frees the memory
  usb: cdns3: fix race condition before setting doorbell
  fs-verity: fix signed integer overflow with i_size near S64_MAX
  hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary 
structure field
  hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary 
structure field
  hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary 
structure field
  scsi: ufs: Fix illegal offset in UPIU event trace
  mac80211: fix use-after-free in CCMP/GCMP RX
  x86/kvmclock: Move this_cpu_pvti into kvmclock.h
  drm/amd/display: Pass PCI deviceid into DC
  ipvs: check that ip_vs_conn_tab_bits is between 8 and 20
  hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced 
from sysfs
  mac80211: Fix ieee80211_amsdu_aggregate frag_tail bug
  mac80211: limit injected vht mcs/nss in ieee80211_parse_tx_radiotap
  mac80211: mesh: fix potentially unaligned access
  mac80211-hwsim: fix late beacon hrtimer handling
  sctp: break out if skb_header_pointer returns NULL in sctp_rcv_ootb
  hwmon: (tmp421) report /PVLD condition as fault
  hwmon: (tmp421) fix rounding for negative values
  net: ipv4: Fix rtnexthop len when RTA_FLOW is present
  e100: fix length calculation in e100_get_regs_len
  e100: fix buffer overrun in e100_get_regs
  selftests, bpf: test_lwt_ip_encap: Really disable rp_filter
  scsi: csiostor: Add module softdep on cxgb4
  net: hns3: do not allow call hns3_nic_net_open repeatedly
  net: sched: flower: protect fl_walk() with rcu
  af_unix: fix races in sk_peer_pid and sk_peer_cred accesses
  perf/x86/intel: Update event constraints for ICX
  elf: don't use MAP_FIXED_NOREPLACE for elf interpreter mappings
  debugfs: debugfs_create_file_size(): use IS_ERR to check for error
  ipack: ipoctal: fix stack information leak
  ipack: ipoctal: fix tty registration race
  ipack: ipoctal: fix tty-registration error handling
  ipack: ipoctal: fix missing allocation-failure check
  ipack: ipoctal: fix module reference leak
  ext4: fix loff_t overflow in ext4_max_bitmap_size()
  ext4: fix reserved space counter leakage
  ext4: fix potential infinite loop in ext4_dx_readdir()
  HID: u2fzero: ignore incomplete packets without data
  net: udp: annotate data race around udp_sk(sk)->corkflag
  net: stmmac: don't attach interface until resume finishes
  PCI: Fix pci_host_bridge struct device release/free handling
  libnvdimm/pmem: Fix crash triggered when I/O in-flight during unbind
  hso: fix bailout in error case of probe
  usb: hso: fix error handling code of hso_create_net_device
  usb: hso: remove the bailout parameter
  crypto: ccp - fix resource leaks in ccp_run_aes_gcm_cmd()
  HID: betop: fix slab-out-of-bounds Write in betop_probe
  netfilter: ipset: Fix oversized kvmalloc() calls
  HID: usbhid: free raw_report buffers in usbhid_stop
  Linux 5.4.151
  UBUNTU: upstream stable to v5.4.151

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


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

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

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

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

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


** Tags added: verification-needed-focal

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Confirmed
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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

[Kernel-packages] [Bug 1947781] Re: Hirsute update: upstream stable patchset 2021-10-19

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

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

Title:
  Hirsute update: upstream stable patchset 2021-10-19

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-10-19

  Ported from the following upstream stable releases:
  v5.10.67, v5.13.19

     from git://git.kernel.org/

  rtc: tps65910: Correct driver module alias
  io_uring: place fixed tables under memcg limits
  io_uring: add ->splice_fd_in checks
  io_uring: fail links of cancelled timeouts
  io-wq: fix wakeup race when adding new work
  btrfs: wake up async_delalloc_pages waiters after submit
  btrfs: reset replace target device to allocation state on close
  blk-zoned: allow zone management send operations without CAP_SYS_ADMIN
  blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
  PCI/MSI: Skip masking MSI-X on Xen PV
  powerpc/perf/hv-gpci: Fix counter value parsing
  xen: fix setting of max_pfn in shared_info
  9p/xen: Fix end of loop tests for list_for_each_entry
  ceph: fix dereference of null pointer cf
  selftests/ftrace: Fix requirement check of README file
  tools/thermal/tmon: Add cross compiling support
  clk: socfpga: agilex: fix the parents of the psi_ref_clk
  clk: socfpga: agilex: fix up s2f_user0_clk representation
  clk: socfpga: agilex: add the bypass register for s2f_usr0 clock
  pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast
  pinctrl: ingenic: Fix incorrect pull up/down info
  soc: qcom: aoss: Fix the out of bound usage of cooling_devs
  soc: aspeed: lpc-ctrl: Fix boundary check for mmap
  soc: aspeed: p2a-ctrl: Fix boundary check for mmap
  arm64: mm: Fix TLBI vs ASID rollover
  arm64: head: avoid over-mapping in map_memory
  iio: ltc2983: fix device probe
  wcn36xx: Ensure finish scan is not requested before start scan
  crypto: public_key: fix overflow during implicit conversion
  block: bfq: fix bfq_set_next_ioprio_data()
  power: supply: max17042: handle fails of reading status register
  dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
  crypto: ccp - shutdown SEV firmware on kexec
  VMCI: fix NULL pointer dereference when unmapping queue pair
  media: uvc: don't do DMA on stack
  media: rc-loopback: return number of emitters rather than error
  s390/qdio: fix roll-back after timeout on ESTABLISH ccw
  s390/qdio: cancel the ESTABLISH ccw after timeout
  Revert "dmaengine: imx-sdma: refine to load context only once"
  dmaengine: imx-sdma: remove duplicated sdma_load_context
  libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs
  ARM: 9105/1: atags_to_fdt: don't warn about stack size
  f2fs: fix to do sanity check for sb/cp fields correctly
  PCI/portdrv: Enable Bandwidth Notification only if port supports it
  PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported
  PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure
  PCI: xilinx-nwl: Enable the clock through CCF
  PCI: aardvark: Configure PCIe resources from 'ranges' DT property
  PCI: Export pci_pio_to_address() for module use
  PCI: aardvark: Fix checking for PIO status
  PCI: aardvark: Fix masking and unmasking legacy INTx interrupts
  HID: input: do not report stylus battery state as "full"
  f2fs: quota: fix potential deadlock
  pinctrl: remove empty lines in pinctrl subsystem
  pinctrl: armada-37xx: Correct PWM pins definitions
  scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND
  clk: rockchip: drop GRF dependency for rk3328/rk3036 pll types
  IB/hfi1: Adjust pkey entry in index 0
  RDMA/iwcm: Release resources if iw_cm module initialization fails
  docs: Fix infiniband uverbs minor number
  scsi: BusLogic: Use %X for u32 sized integer rather than %lX
  pinctrl: samsung: Fix pinctrl bank pin count
  vfio: Use config not menuconfig for VFIO_NOIOMMU
  scsi: ufs: Fix memory corruption by ufshcd_read_desc_param()
  cpuidle: pseries: Fixup CEDE0 latency only for POWER10 onwards
  powerpc/stacktrace: Include linux/delay.h
  RDMA/efa: Remove double QP type assignment
  RDMA/mlx5: Delete not-available udata check
  cpuidle: pseries: Mark pseries_idle_proble() as __init
  f2fs: reduce the scope of setting fsck tag when de->name_len is zero
  openrisc: don't printk() unconditionally
  dma-debug: fix

[Kernel-packages] [Bug 1947092] Re: Headphone microphone not working on particular Dell laptops

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Headphone microphone not working on particular Dell laptops

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  The Dell Latitude 5430 series with Realtek audio codec ALC3254 fail to detect 
the headphone microphone and thus unable to do recording.

  [Fix]
  The realtek audio quirk ALC269_FIXUP_DELL4_MIC_NO_PRESENCE is required since 
the NID used for headphone microphone should be 0x1b instead of 0x1a, which is 
used for former ALC225/295 variants.

  [Test Case]
  1. Plug in the headphone microphone on the particular Dell Latitude 5430 
laptop
  2. Make sure it's detected in Audio Settings. (pulseaudio)
  3. Record the sound via the headphone microphone and check the recorded 
content.

  [Where problems could occur]
  No. Since the audio quirk only affect the machine with particular subsystem 
ID.

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


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

[Kernel-packages] [Bug 1948873] Re: Hirsute update: upstream stable patchset 2021-10-26

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

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

Title:
  Hirsute update: upstream stable patchset 2021-10-26

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-10-26

  Ported from the following upstream stable releases:
  v5.10.68, v5.14.7

     from git://git.kernel.org/

  drm/bridge: lt9611: Fix handling of 4k panels
  xen: reset legacy rtc flag for PV domU
  arm64/sve: Use correct size when reinitialising SVE state
  PM: base: power: don't try to use non-existing RTC for storing data
  PCI: Add AMD GPU multi-function power dependencies
  drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10
  drm/etnaviv: return context from etnaviv_iommu_context_get
  drm/etnaviv: put submit prev MMU context when it exists
  drm/etnaviv: stop abusing mmu_context as FE running marker
  drm/etnaviv: keep MMU context across runtime suspend/resume
  drm/etnaviv: exec and MMU state is lost when resetting the GPU
  drm/etnaviv: fix MMU context leak on GPU reset
  drm/etnaviv: reference MMU context when setting up hardware state
  drm/etnaviv: add missing MMU context put when reaping MMU mapping
  s390/sclp: fix Secure-IPL facility detection
  x86/pat: Pass valid address to sanitize_phys()
  x86/mm: Fix kern_addr_valid() to cope with existing but not present entries
  tipc: fix an use-after-free issue in tipc_recvmsg
  ethtool: Fix rxnfc copy to user buffer overflow
  net/{mlx5|nfp|bnxt}: Remove unnecessary RTNL lock assert
  net-caif: avoid user-triggerable WARN_ON(1)
  ptp: dp83640: don't define PAGE0
  net/l2tp: Fix reference count leak in l2tp_udp_recv_core
  r6040: Restore MDIO clock frequency after MAC reset
  tipc: increase timeout in tipc_sk_enqueue()
  drm/rockchip: cdn-dp-core: Make cdn_dp_core_resume __maybe_unused
  perf machine: Initialize srcline string member in add_location struct
  net/mlx5: FWTrace, cancel work on alloc pd error flow
  net/mlx5: Fix potential sleeping in atomic context
  nvme-tcp: fix io_work priority inversion
  events: Reuse value read using READ_ONCE instead of re-reading it
  net: ipa: initialize all filter table slots
  gen_compile_commands: fix missing 'sys' package
  vhost_net: fix OoB on sendmsg() failure.
  net/af_unix: fix a data-race in unix_dgram_poll
  net: dsa: destroy the phylink instance on any error in dsa_slave_phy_setup
  x86/uaccess: Fix 32-bit __get_user_asm_u64() when CC_HAS_ASM_GOTO_OUTPUT=y
  tcp: fix tp->undo_retrans accounting in tcp_sacktag_one()
  selftest: net: fix typo in altname test
  qed: Handle management FW error
  udp_tunnel: Fix udp_tunnel_nic work-queue type
  dt-bindings: arm: Fix Toradex compatible typo
  ibmvnic: check failover_pending in login response
  KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing 
registers
  bnxt_en: make bnxt_free_skbs() safe to call after bnxt_free_mem()
  net: hns3: pad the short tunnel frame before sending to hardware
  net: hns3: change affinity_mask to numa node range
  net: hns3: disable mac in flr process
  net: hns3: fix the timing issue of VF clearing interrupt sources
  dt-bindings: mtd: gpmc: Fix the ECC bytes vs. OOB bytes equation
  mfd: db8500-prcmu: Adjust map to reality
  PCI: Add ACS quirks for NXP LX2xx0 and LX2xx2 platforms
  fuse: fix use after free in fuse_read_interrupt()
  PCI: tegra194: Fix handling BME_CHGED event
  PCI: tegra194: Fix MSI-X programming
  PCI: tegra: Fix OF node reference leak
  mfd: Don't use irq_create_mapping() to resolve a mapping
  PCI: rcar: Fix runtime PM imbalance in rcar_pcie_ep_probe()
  tracing/probes: Reject events which have the same name of existing one
  PCI: cadence: Use bitfield for *quirk_retrain_flag* instead of bool
  PCI: cadence: Add quirk flag to set minimum delay in LTSSM Detect.Quiet state
  PCI: j721e: Add PCIe support for J7200
  PCI: j721e: Add PCIe support for AM64
  PCI: Add ACS quirks for Cavium multi-function devices
  watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate
  octeontx2-af: Add additional register check to rvu_poll_reg()
  Set fc_nlinfo in nh_create_ipv4, nh_create_ipv6
  net: usb: cdc_mbim: avoid altsetting toggling for Telit LN920
  PCI: ibmphp: Fix double unmap of io_mem
  ethtool: Fix an

[Kernel-packages] [Bug 1947191] Re: Impish update: v5.13.19 upstream stable release

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

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

Title:
  Impish update: v5.13.19 upstream stable release

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Impish:
  Fix Committed

Bug description:
  SRU Justification

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

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

  rtc: tps65910: Correct driver module alias
  btrfs: wake up async_delalloc_pages waiters after submit
  btrfs: wait on async extents when flushing delalloc
  btrfs: reduce the preemptive flushing threshold to 90%
  btrfs: zoned: fix block group alloc_offset calculation
  btrfs: zoned: suppress reclaim error message on EAGAIN
  btrfs: fix upper limit for max_inline for page size 64K
  btrfs: reset replace target device to allocation state on close
  btrfs: zoned: fix double counting of split ordered extent
  blk-zoned: allow zone management send operations without CAP_SYS_ADMIN
  blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
  PCI/MSI: Skip masking MSI-X on Xen PV
  powerpc/perf/hv-gpci: Fix counter value parsing
  xen: fix setting of max_pfn in shared_info
  9p/xen: Fix end of loop tests for list_for_each_entry
  ceph: fix dereference of null pointer cf
  Input: elan_i2c - reduce the resume time for controller in Whitebox
  selftests/ftrace: Fix requirement check of README file
  tools/thermal/tmon: Add cross compiling support
  clk: socfpga: agilex: fix the parents of the psi_ref_clk
  clk: socfpga: agilex: fix up s2f_user0_clk representation
  clk: socfpga: agilex: add the bypass register for s2f_usr0 clock
  pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast
  pinctrl: ingenic: Fix incorrect pull up/down info
  pinctrl: ingenic: Fix bias config for X2000(E)
  soc: mediatek: mmsys: Fix missing UFOE component in mt8173 table routing
  soc: qcom: aoss: Fix the out of bound usage of cooling_devs
  soc: aspeed: lpc-ctrl: Fix boundary check for mmap
  soc: aspeed: p2a-ctrl: Fix boundary check for mmap
  arm64: Move .hyp.rodata outside of the _sdata.._edata range
  arm64: mm: Fix TLBI vs ASID rollover
  arm64: head: avoid over-mapping in map_memory
  arm64: Do not trap PMSNEVFR_EL1
  iio: ltc2983: fix device probe
  wcn36xx: Ensure finish scan is not requested before start scan
  crypto: public_key: fix overflow during implicit conversion
  block: bfq: fix bfq_set_next_ioprio_data()
  power: supply: max17042: handle fails of reading status register
  dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
  crypto: ccp - shutdown SEV firmware on kexec
  spi: fsi: Reduce max transfer size to 8 bytes
  VMCI: fix NULL pointer dereference when unmapping queue pair
  media: uvc: don't do DMA on stack
  media: rc-loopback: return number of emitters rather than error
  nvmem: core: fix error handling while validating keepout regions
  s390/qdio: fix roll-back after timeout on ESTABLISH ccw
  s390/qdio: cancel the ESTABLISH ccw after timeout
  Revert "dmaengine: imx-sdma: refine to load context only once"
  dmaengine: imx-sdma: remove duplicated sdma_load_context
  io_uring: place fixed tables under memcg limits
  io_uring: add ->splice_fd_in checks
  io_uring: fix io_try_cancel_userdata race for iowq
  io-wq: fix wakeup race when adding new work
  io-wq: fix race between adding work and activating a free worker
  io_uring: fail links of cancelled timeouts
  libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs
  ARM: 9105/1: atags_to_fdt: don't warn about stack size
  f2fs: fix to do sanity check for sb/cp fields correctly
  PCI/portdrv: Enable Bandwidth Notification only if port supports it
  PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported
  PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure
  PCI: xilinx-nwl: Enable the clock through CCF
  PCI: aardvark: Configure PCIe resources from 'ranges' DT property
  PCI: aardvark: Fix checking for PIO status
  PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response
  PCI: aardvark: Fix masking and unmasking legacy INTx interrupts
  f2fs: compress: fix to set zstd compress level correctly
  HID: input: do not report stylus battery state as "full"
  f2fs: quota: fix potential deadlock
  pinctrl: armada-37xx: Correct PWM pins definitions
  scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND
  clk: rockchip: drop GRF dependency for

[Kernel-packages] [Bug 1948485] Re: Impish update: upstream stable patchset 2021-10-22

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

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

Title:
  Impish update: upstream stable patchset 2021-10-22

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-10-22

  Ported from the following upstream stable releases:
  v5.10.68, v5.14.7

     from git://git.kernel.org/

  xen: reset legacy rtc flag for PV domU
  arm64/sve: Use correct size when reinitialising SVE state
  PM: base: power: don't try to use non-existing RTC for storing data
  PCI: Add AMD GPU multi-function power dependencies
  drm/amd/amdgpu: Increase HWIP_MAX_INSTANCE to 10
  drm/etnaviv: return context from etnaviv_iommu_context_get
  drm/etnaviv: put submit prev MMU context when it exists
  drm/etnaviv: stop abusing mmu_context as FE running marker
  drm/etnaviv: keep MMU context across runtime suspend/resume
  drm/etnaviv: exec and MMU state is lost when resetting the GPU
  drm/etnaviv: fix MMU context leak on GPU reset
  drm/etnaviv: reference MMU context when setting up hardware state
  drm/etnaviv: add missing MMU context put when reaping MMU mapping
  s390/sclp: fix Secure-IPL facility detection
  x86/pat: Pass valid address to sanitize_phys()
  x86/mm: Fix kern_addr_valid() to cope with existing but not present entries
  tipc: fix an use-after-free issue in tipc_recvmsg
  ethtool: Fix rxnfc copy to user buffer overflow
  net/{mlx5|nfp|bnxt}: Remove unnecessary RTNL lock assert
  net-caif: avoid user-triggerable WARN_ON(1)
  ptp: dp83640: don't define PAGE0
  net/l2tp: Fix reference count leak in l2tp_udp_recv_core
  r6040: Restore MDIO clock frequency after MAC reset
  tipc: increase timeout in tipc_sk_enqueue()
  drm/rockchip: cdn-dp-core: Make cdn_dp_core_resume __maybe_unused
  perf machine: Initialize srcline string member in add_location struct
  net/mlx5: FWTrace, cancel work on alloc pd error flow
  net/mlx5: Fix potential sleeping in atomic context
  nvme-tcp: fix io_work priority inversion
  events: Reuse value read using READ_ONCE instead of re-reading it
  net: ipa: initialize all filter table slots
  gen_compile_commands: fix missing 'sys' package
  vhost_net: fix OoB on sendmsg() failure.
  net/af_unix: fix a data-race in unix_dgram_poll
  net: dsa: destroy the phylink instance on any error in dsa_slave_phy_setup
  x86/uaccess: Fix 32-bit __get_user_asm_u64() when CC_HAS_ASM_GOTO_OUTPUT=y
  tcp: fix tp->undo_retrans accounting in tcp_sacktag_one()
  selftest: net: fix typo in altname test
  qed: Handle management FW error
  udp_tunnel: Fix udp_tunnel_nic work-queue type
  dt-bindings: arm: Fix Toradex compatible typo
  ibmvnic: check failover_pending in login response
  KVM: PPC: Book3S HV: Tolerate treclaim. in fake-suspend mode changing 
registers
  bnxt_en: make bnxt_free_skbs() safe to call after bnxt_free_mem()
  net: hns3: pad the short tunnel frame before sending to hardware
  net: hns3: change affinity_mask to numa node range
  net: hns3: disable mac in flr process
  net: hns3: fix the timing issue of VF clearing interrupt sources
  dt-bindings: mtd: gpmc: Fix the ECC bytes vs. OOB bytes equation
  mfd: db8500-prcmu: Adjust map to reality
  PCI: Add ACS quirks for NXP LX2xx0 and LX2xx2 platforms
  fuse: fix use after free in fuse_read_interrupt()
  PCI: tegra194: Fix handling BME_CHGED event
  PCI: tegra194: Fix MSI-X programming
  PCI: tegra: Fix OF node reference leak
  mfd: Don't use irq_create_mapping() to resolve a mapping
  PCI: rcar: Fix runtime PM imbalance in rcar_pcie_ep_probe()
  tracing/probes: Reject events which have the same name of existing one
  PCI: cadence: Use bitfield for *quirk_retrain_flag* instead of bool
  PCI: cadence: Add quirk flag to set minimum delay in LTSSM Detect.Quiet state
  PCI: j721e: Add PCIe support for J7200
  PCI: j721e: Add PCIe support for AM64
  PCI: Add ACS quirks for Cavium multi-function devices
  watchdog: Start watchdog in watchdog_set_last_hw_keepalive only if appropriate
  octeontx2-af: Add additional register check to rvu_poll_reg()
  Set fc_nlinfo in nh_create_ipv4, nh_create_ipv6
  net: usb: cdc_mbim: avoid altsetting toggling for Telit LN920
  PCI: ibmphp: Fix double unmap of io_mem
  ethtool: Fix an error code in cxgb2.c
  NTB: Fix an error code in

[Kernel-packages] [Bug 1948977] Re: Impish update: upstream stable patchset 2021-10-27

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

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

Title:
  Impish update: upstream stable patchset 2021-10-27

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-10-27

  Ported from the following upstream stable releases:
  v5.10.69, v5.14.8

     from git://git.kernel.org/

  PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
  PCI: aardvark: Fix reporting CRS value
  console: consume APC, DM, DCS
  ARM: 9077/1: PLT: Move struct plt_entries definition to header
  ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
  ARM: 9079/1: ftrace: Add MODULE_PLTS support
  ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
  sctp: validate chunk size in __rcv_asconf_lookup
  sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
  staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
  coredump: fix memleak in dump_vma_snapshot()
  um: virtio_uml: fix memory leak on init failures
  dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
  perf test: Fix bpf test sample mismatch reporting
  perf tools: Allow build-id with trailing zeros
  thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
  9p/trans_virtio: Remove sysfs file on probe failure
  prctl: allow to setup brk for et_dyn executables
  nilfs2: use refcount_dec_and_lock() to fix potential UAF
  profiling: fix shift-out-of-bounds bugs
  PM: sleep: core: Avoid setting power.must_resume to false
  pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
  pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered
  dmaengine: idxd: fix wq slot allocation index check
  platform/chrome: sensorhub: Add trace events for sample
  platform/chrome: cros_ec_trace: Fix format warnings
  ceph: allow ceph_put_mds_session to take NULL or ERR_PTR
  ceph: cancel delayed work instead of flushing on mdsc teardown
  Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
  tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh
  thermal/core: Fix thermal_cooling_device_register() prototype
  drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
  drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
  dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
  parisc: Move pci_dev_is_behind_card_dino to where it is used
  iommu/amd: Relocate GAMSup check to early_enable_iommus
  dmaengine: idxd: depends on !UML
  dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
  dmaengine: ioat: depends on !UML
  dmaengine: xilinx_dma: Set DMA mask for coherent APIs
  ceph: request Fw caps before updating the mtime in ceph_write_iter
  ceph: remove the capsnaps when removing caps
  ceph: lockdep annotations for try_nonblocking_invalidate
  btrfs: update the bdev time directly when closing
  btrfs: fix lockdep warning while mounting sprout fs
  nilfs2: fix memory leak in nilfs_sysfs_create_device_group
  nilfs2: fix NULL pointer in nilfs_##name##_attr_release
  nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
  nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
  nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
  habanalabs: add validity check for event ID received from F/W
  pwm: img: Don't modify HW state in .remove() callback
  pwm: rockchip: Don't modify HW state in .remove() callback
  pwm: stm32-lp: Don't modify HW state in .remove() callback
  blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
  blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues
  rtc: rx8010: select REGMAP_I2C
  sched/idle: Make the idle timer expire in hard interrupt context
  drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
  um: fix stub location calculation
  RDMA/mlx5: Fix xlt_chunk_align calculation
  perf symbol: Look for ImageBase in PE file to compute .text offset
  staging: rtl8723bs: fix wpa_set_auth_algs() function
  n64cart: fix return value check in n64cart_probe()
  pwm: ab8500: Fix register offset calculation to not depend on probe order
  thermal/drivers/qcom/spmi-adc-tm5: Don't abort probing if a sensor

[Kernel-packages] [Bug 1945011] Re: kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with NTFS partitions

2021-10-27 Thread Etienne URBAH

1) I do NOT know how to retrieve the ntfsresize options.

2) In order to retrieve file system metadata in the attached 'ntfsinfo.log' 
file, I used following command :
   $ for dev in $(sudo blkid -o device -t TYPE=ntfs); do sudo ntfsinfo -fm 
"$dev"; echo; done


** Attachment added: "File system metadata for my NTFS partitions"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945011/+attachment/5536539/+files/ntfsinfo.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/1945011

Title:
  kernel BUG at fs/inode.c:1676! during Live CD ubiquity partman with
  NTFS partitions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On this computer with ext4, FAT and NTFS partitions :

  I successfully booted from the Live CD of Ubuntu Desktop 21.10 (Impish
  Indri) beta with full graphics.

  I started the ubiquity graphical interface and successfully completed
  the first screens.

  But on the 'Updates and other software screen', after clicking on
  Continue, ubiquity does NOT show the next screen (which on previous
  versions was Partitioning).

  ubiquity seems to be blocked inside partman.
  I attach the partman log file.

  syslog contains following message :
  kernel BUG at fs/inode.c:1676!

  Notably, this kernel bug message is preceeded by 2 warnings :
  WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1610 blkdev_put+0x130/0x140
  WARNING: CPU: 7 PID: 18634 at fs/block_dev.c:1576 __blkdev_put+0x1dc/0x1f0

  Thanks in advance for investigating and correcting this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 6322 F pulseaudio
   /dev/snd/controlC1:  ubuntu 6322 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 24 21:25:08 2021
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.200
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuSKU:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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


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

[Kernel-packages] [Bug 1915146] Re: Backport commits required for confidential VMs

This bug is awaiting verification that the linux-azure-
cvm/5.4.0-1063.66+cvm2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal' to 'verification-
done-focal'. If the problem still exists, change the tag 'verification-
needed-focal' to 'verification-failed-focal'.

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

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


** Tags added: verification-needed-focal

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

Title:
  Backport commits required for confidential VMs

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Below are two sets of commits required for CVM:

  1. Core enablement of Linux to run as a Hyper-V guest with the SNP-enabled 
HCL.
  2. VMbus hardening.

  Patches related to core enablement of Linux to run as a Hyper-V guest
  with the SNP-enabled HCL are below:

  HV/Storvsc: Add bounce buffer support for Storvsc -
  
https://github.com/lantianyu/linux/commit/c46341863ba7cfaa11ed6c95d454769dcde57b84

  HV/Netvsc: Add SNP support for netvsc driver -
  
https://github.com/lantianyu/linux/commit/0026626dbc42bfcbe26d993bec104383f9d60e35

  x86/Hyper-V: Copy data from/to bounce buffer during IO operation -
  
https://github.com/lantianyu/linux/commit/5f948e69f2be44891af03d60b918a3bc0845f954

  x86/Hyper-V: Add new parameter for
  vmbus_sendpacket_pagebuffer()/mpb_desc() -
  
https://github.com/lantianyu/linux/commit/b484eebaf79340e29012a2dadb4518fa7d5d1284

  x86/Hyper-V: Initialize bounce buffer page cache and list -
  
https://github.com/lantianyu/linux/commit/8a437af5e4af945b28ba0071302dfa28a48df408

  hv/vmbus: Initialize VMbus ring buffer for Isolated VM -
  
https://github.com/lantianyu/linux/commit/45de7cff82cd6e99aedbd4cf2c44fa30298c0dea

  HV/Vmbus: Add SNP support for VMbus channel initiate message -
  
https://github.com/lantianyu/linux/commit/4bca8b9748dd17fb860a4528781932ade1825dd5

  HV: Add ghcb hvcall support for SNP VM -
  
https://github.com/lantianyu/linux/commit/bfb44533b884b08b639258f7150aa71dc148e221

  HV: Add Write/Read MSR registers via ghcb -
  
https://github.com/lantianyu/linux/commit/8cf6a0dea3189a654c41e16ad859c9ceb5bb940c

  HV: Get Hyper-V Isolated VM capability -
  
https://github.com/lantianyu/linux/commit/9290189014a1b231f70b5620338d61508da673df

  x86/Hyper-V: Add new hvcall guest address host visibility support -
  
https://github.com/lantianyu/linux/commit/deb6dc9bdbff7a6b16910ebe9aff266de9690cb2

  x86/Hyper-V: Add visibility parameter for vmbus_establish_gpadl() -
  
https://github.com/lantianyu/linux/commit/e697bc57e853f058eef9b2268b865aa8e574e233

  The following commit is also required by CVM support. It has been upstreamed. 
If ubuntu kernel doesn't contain the patch, it's necessary to backport the 
patch.
  x86/hyperv: Initialize clockevents earlier in CPU onlining - 
https://github.com/lantianyu/linux/commit/8815c2eec402080a4c5f2536668f6d5b7946ef8b

  VMbus hardening patches:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0a76566595bfb242a7f4bedc77233e9194831ba3
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=44144185951a0ff9b50bf21c0cd1f79ff688e5ca
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e8b7db38449ac5b950a3f00519171c4be3e226ff
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=453de21c2b8281228173a7b689120b92929743d6
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4d18fcc95f50950a99bd940d4e61a983f91d267a

  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=ab548fd21e1cbe601ce5f775254a6d042c6495f2
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=244808e0302953de11dba1f8a580cdd1df35843d
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?id=91b1b640b834b2d6f330baf04c0cc049eca9d689

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=206ad34d52a2f1205c84d08c12fc116aad0eb407

  
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=4424a8d1acc0a30542d4399e83c2a6cfcdd1eb71
  
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=6809ea1c570b40c9b2f139684784d6318d958011

  
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=46011a70c1c21a5dba02b38edeac16e667544361
  
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?id=5c0c26e7dca8f892cc342213e737494d8fd3384f

[Kernel-packages] [Bug 1948057] Re: linux-azure-cvm: Create a 5.4 based kernel

This bug is awaiting verification that the linux-azure-
cvm/5.4.0-1063.66+cvm2 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal' to 'verification-
done-focal'. If the problem still exists, change the tag 'verification-
needed-focal' to 'verification-failed-focal'.

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

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


** Tags added: verification-needed-focal

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

Title:
  linux-azure-cvm: Create a 5.4 based kernel

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  linux-azure-cvm: Create a 5.4 based kernel

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-27 Thread elguavas

@randomdave, in case you didn't, i think you have to disable the
trackpoint as well as the trackpad.

some people have reported that just disabling the trackpoint but leaving
the trackpad enabled works, but you lose the trackpad buttons and have
to configure tap-to-click.

for others it only works if you disable both.

hope that helps.

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work

2021-10-27 Thread Roman

Exact package causing the issue is not obvious, but I add bluez.

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

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (20.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 
 serial:  
 Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 
 rev: e2f 
 Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept 
 service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

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


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

[Kernel-packages] [Bug 1948877] [NEW] Bluetooth headphones media buttons no longer work

You have been subscribed to a public bug:

In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped
working. This includes the "play/pause" button, "play next" (calls after
long press of volume increase), and "play previous" (long press of
volume decrease). The volume +/- buttons themselves are working, but
this seemingly is implemented entirely in the headphones and does not
require any communication over bluetooth.

In previous ubuntu (20.04) these buttons worked, and I expect them
working.

My headset is Qumo Accord 3.

Here is output of "inxi -Eaz" in terminal:

Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 
   serial:  
   Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 
   rev: e2f 
   Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff 
park link-mode: slave accept 
   service-classes: rendering, capturing, object transfer, audio, 
telephony

Some possible workarounds that I found suggest to "modprobe uinput", but
the uinput module does not get loaded (lsmod does not list it even after
modprobe'ing).

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


** Tags: bot-comment
-- 
Bluetooth headphones media buttons no longer work
https://bugs.launchpad.net/bugs/1948877
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to bluez 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 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7

---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)

  * [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert CET patches

linux-intel-5.13 (5.13.0-1006.6) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1006.6 -proposed tracker (LP:
#1945669)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

  * MEI (Intel Management Engine Interface) for sprint 2 (LP: #1945464)
- Revert "mei: dal: add test module"
- mei: backport fix from 5.12
- Revert "UBUNTU: [Config] Disable INTEL_MEI_DAL and INTEL_MEI_VIRTIO"
- [Config] Enable CONFIG_INTEL_MEI_DAL and CONFIG_INTEL_MEI_VIRTIO

  * [EHL] Intel ishtp VNIC driver (LP: #1943524)
- net: Add support for Intel vnic driver
- [Config] CONFIG_INTEL_ISHTP_VNIC=m

  * [EHL] Quadrature Encoder Peripheral support for sprint 2 (LP: #1945494)
- counter: Add support for Intel Quadrature Encoder Peripheral
- counter: intel-qep: Mark PM callbacks with __maybe_unused
- counter: intel-qep: Use to_pci_dev() helper
- [Config] CONFIG_INTEL_QEP=m

  * I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
(LP: #1945548)
- igc: Remove _I_PHY_ID checking
- igc: Remove phy->type checking

  * [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
(LP: #1929903)
- tcc: update RTCT table parser to support two versions
- Enable support to read a few whitelisted registers.
- Remove Clock_Cycles_VT from MHL entry.
- Add new IOCTL to read error log buffer.
- Display errlog buffer raw data in kernel log as requested once this driver
  is loaded.
- Fix issue found in acrn uos when convert cacheid to apicid.

  * Integrated TSN controller for sprint 2 (LP: #1945461)
- net: pcs: Introducing support for DWC xpcs Energy Efficient Ethernet
- net: stmmac: Add callbacks for DWC xpcs Energy Efficient Ethernet
- net: stmmac: enable platform specific safety features
- net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
- net: stmmac: Fix mixed enum type warning
- net: stmmac: Fix unused values warnings
- stmmac: intel: move definitions to dwmac-intel header file
- stmmac: intel: fix wrong kernel-doc
- stmmac: align RX buffers
- net: stmmac: Fix mixed enum type
- net: pcs: xpcs: delete shim definition for mdio_xpcs_get_ops()
- net: pcs: xpcs: there is only one PHY ID
- net: pcs: xpcs: make the checks related to the PHY interface mode
- net: pcs: xpcs: export xpcs_validate
- net: pcs: xpcs: export xpcs_config_eee
- net: pcs: xpcs: export xpcs_probe
- net: pcs: xpcs: use mdiobus_c45_addr in xpcs_{read,write}
- net: pcs: xpcs: convert to mdio_device
- net: pcs: xpcs: convert to phylink_pcs_ops
- net: stmmac: split xPCS setup from mdio register
- net: pcs: add 2500BASEX support for Intel mGbE controller
- net: stmmac: enable Intel mGbE 2.5Gbps link speed
- net: stmmac: fix NPD with phylink_set_pcs if there is no MDIO bus
- net: stmmac: explicitly deassert GMAC_AHB_RESET
- net: stmmac: Fix missing { } around two statements in an if statement
- net: pcs: xpcs: rename mdio_xpcs_args to dw_xpcs
- net: stmmac: reduce indentation when calling stmmac_xpcs_setup
- net: pcs: xpcs: move register bit descriptions to a header file
- net: pcs: xpcs: add support for sgmii with no inband AN
- net: pcs: xpcs: also ignore phy id if it's all ones
- net: pcs: xpcs: export xpcs_do_config and xpcs_link_up
- net: stmmac: remove redundant continue statement
- net: stmmac: option to enable PHY WOL with PMT enabled
- stmmac: intel: Enable PHY WOL option in EHL
- stmmac: intel: set PCI_D3hot in suspend
- net: stmmac: separate the tas basetime calculation function
- net: stmmac: ptp: update tas basetime after ptp adjust
- net: pcs: xpcs: fix error handling on failed to allocate memory
- net: pcs: xpcs: Add Pause Mode support for SGMII and 2500BaseX
- net: phy: marvell: Add WAKE_PHY support to WOL event
- net: stmmac: fix INTR TBU status affecting irq count statistic
- net: stmmac: add ethtool per-queue statistic framework
- net: stmmac: add ethtool per-queue irq statistic support
- net: phy: add API to read 802.3-c45 IDs
- igc: Move igc_xdp_is_enabled()
- igc: Refactor __igc_xdp_run_prog()
- igc: Refactor igc_clean_rx_ring()
- igc: Refactor XDP rxq info registration
- igc: Introduce TX/RX stats helpers
- igc: Introduce igc_unmap_tx_buffer() helper
- igc: Replace IGC_TX_FLAGS_XDP flag by an enum
- igc: Enable RX via AF_XDP zero-copy
- igc: Enable TX via AF_XDP zero-copy
- igc: Revert back xdp_rxq_info_reg() registration call
- igc: Fix fail to set fragment size via ethtool
- igc: Enable

[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization

2021-10-27 Thread Boris Gjenero

No, "pcie_aspm=off" does not help.

I also tried uninstalling broadcom-sta-dkms. It blacklists the b44
module via /etc/modprobe.d/broadcom-sta-dkms.conf and also
https://wiki.debian.org/wl says that b44 is incompatible with wl. This
did not help either.

My laptop seems fine with just having the b44 module loaded. Lockups
only happen when I plug in the Ethernet cable and start using it. The
lockup seems total, with even Magic SysRq from the laptop's own keyboard
doing absolutely nothing.

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

Title:
  b44 Ethernet driver null pointer during initialization

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This problem started after upgrading to Ubuntu 19.04. It was not
  present with 4.18.0-16-generic kernel and is present in the
  4.18.0-15-generic kernel. Ever time during boot there is a null
  pointer dereference in the b44 driver for the on-board Ethernet on
  this Dell Inspiron 6400. After that I can log in but networking
  related commands hang and the computer eventually locks up.
  Blacklisting the b44 module so it doesn't load works as a workaround,
  though of course the on board Ethernet can't be used that way. The b43
  WiFi still works then. The following is pasted from the log of one
  crash:

  6.483003] BUG: unable to handle kernel NULL pointer dereference at 

  6.483052] #PF error: [normal kernel read fault]
  6.483093] PGD 0 P4D 0 
  6.483133] Oops:  [#1] SMP PTI
  6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 
5.0.0-7-generic #8-Ubuntu
  6.483217] Hardware name: Dell Inc. MM061   /0XD720, 
BIOS A17 06/13/2007
  6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310
  6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 
44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 
0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f
  6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016
  6.483416] RAX: 0001 RBX:  RCX: 
  6.483467] RDX:  RSI: 001f RDI: 0001
  6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001
  6.483572] R10:  R11:  R12: 
  6.483621] R13:  R14: 0001 R15: 0020
  6.483670] FS:  7f2cb49ccbc0() GS:9d8a4c40() 
knlGS:
  6.483726] CS:  0010 DS:  ES:  CR0: 80050033
  6.483773] CR2:  CR3: c72ce000 CR4: 06f0
  6.483820] Call Trace:
  6.483869]  swiotlb_map+0x6c/0x1c0
  6.483915]  dma_direct_map_page+0xc5/0x160
  6.483965]  b44_alloc_rx_skb+0x18e/0x3f0 [b44]
  6.484013]  b44_init_rings+0xbe/0x1b0 [b44]
  6.484060]  b44_open+0xfc/0x3f0 [b44]
  6.484107]  __dev_open+0xd4/0x170
  6.484153]  __dev_change_flags+0x18f/0x200
  6.484199]  dev_change_flags+0x27/0x60
  6.484246]  do_setlink+0x31c/0xe30
  6.484292]  ? __nla_parse+0xf1/0x120
  6.484340]  ? cpumask_next+0x1b/0x20
  6.484388]  ? __snmp6_fill_stats64.isra.57+0xf6/0x120
  6.484439]  ? __nla_parse+0x38/0x120
  6.484488]  __rtnl_newlink+0x531/0x910
  6.484535]  ? __nla_put+0x20/0x30
  6.484586]  ? __kmalloc_node_track_caller+0x1e6/0x2b0
  6.484636]  ? pskb_expand_head+0x70/0x2e0
  6.484693]  ? __kmalloc_reserve.isra.53+0x31/0x90
  6.484751]  ? apparmor_inet_conn_request+0x40/0x40
  6.484822]  ? security_sock_rcv_skb+0x2f/0x50
  6.484879]  ? skb_queue_tail+0x43/0x50
  6.484934]  ? __netlink_sendskb+0x53/0x70
  6.484992]  ? syscall_return_via_sysret+0xf/0x7f
  6.485043]  ? __switch_to_asm+0x40/0x70
  6.485097]  ? syscall_return_via_sysret+0xf/0x7f
  6.485153]  ? _cond_resched+0x19/0x30
  6.485204]  ? kmem_cache_alloc_trace+0x153/0x1d0
  6.485253]  rtnl_newlink+0x48/0x70
  6.485301]  rtnetlink_rcv_msg+0x213/0x300
  6.485348]  ? __d_lookup+0x126/0x140
  6.485393]  ? rtnl_calcit.isra.31+0x100/0x100
  6.485440]  netlink_rcv_skb+0x4f/0x120
  6.485485]  rtnetlink_rcv+0x15/0x20
  6.485518]  netlink_unicast+0x1a1/0x260
  6.485518]  netlink_sendmsg+0x20d/0x3c0
  6.485518]  sock_sendmsg+0x3e/0x50
  6.485518]  ___sys_sendmsg+0x295/0x2f0
  6.485518]  ? rtnl_unlock+0xe/0x10
  6.485518]  ? addrconf_sysctl_forward+0x114/0x280
  6.485518]  ? dev_forward_change+0x140/0x140
  6.485518]  ? __fget_light+0x54/0x60
  6.485518]  __sys_sendmsg+0x5c/0xa0
  6.485518]  __x64_sys_sendmsg+0x1f/0x30
  6.485518]  do_syscall_64+0x5a/0x110
  6.485518]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  6.485518] RIP: 0033:0x7f2cb6153cb7
  6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 
3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 
ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48
  6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293

[Kernel-packages] [Bug 1945461] Re: Integrated TSN controller for sprint 2

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7

---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)

  * [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert CET patches

linux-intel-5.13 (5.13.0-1006.6) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1006.6 -proposed tracker (LP:
#1945669)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

  * MEI (Intel Management Engine Interface) for sprint 2 (LP: #1945464)
- Revert "mei: dal: add test module"
- mei: backport fix from 5.12
- Revert "UBUNTU: [Config] Disable INTEL_MEI_DAL and INTEL_MEI_VIRTIO"
- [Config] Enable CONFIG_INTEL_MEI_DAL and CONFIG_INTEL_MEI_VIRTIO

  * [EHL] Intel ishtp VNIC driver (LP: #1943524)
- net: Add support for Intel vnic driver
- [Config] CONFIG_INTEL_ISHTP_VNIC=m

  * [EHL] Quadrature Encoder Peripheral support for sprint 2 (LP: #1945494)
- counter: Add support for Intel Quadrature Encoder Peripheral
- counter: intel-qep: Mark PM callbacks with __maybe_unused
- counter: intel-qep: Use to_pci_dev() helper
- [Config] CONFIG_INTEL_QEP=m

  * I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
(LP: #1945548)
- igc: Remove _I_PHY_ID checking
- igc: Remove phy->type checking

  * [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
(LP: #1929903)
- tcc: update RTCT table parser to support two versions
- Enable support to read a few whitelisted registers.
- Remove Clock_Cycles_VT from MHL entry.
- Add new IOCTL to read error log buffer.
- Display errlog buffer raw data in kernel log as requested once this driver
  is loaded.
- Fix issue found in acrn uos when convert cacheid to apicid.

  * Integrated TSN controller for sprint 2 (LP: #1945461)
- net: pcs: Introducing support for DWC xpcs Energy Efficient Ethernet
- net: stmmac: Add callbacks for DWC xpcs Energy Efficient Ethernet
- net: stmmac: enable platform specific safety features
- net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
- net: stmmac: Fix mixed enum type warning
- net: stmmac: Fix unused values warnings
- stmmac: intel: move definitions to dwmac-intel header file
- stmmac: intel: fix wrong kernel-doc
- stmmac: align RX buffers
- net: stmmac: Fix mixed enum type
- net: pcs: xpcs: delete shim definition for mdio_xpcs_get_ops()
- net: pcs: xpcs: there is only one PHY ID
- net: pcs: xpcs: make the checks related to the PHY interface mode
- net: pcs: xpcs: export xpcs_validate
- net: pcs: xpcs: export xpcs_config_eee
- net: pcs: xpcs: export xpcs_probe
- net: pcs: xpcs: use mdiobus_c45_addr in xpcs_{read,write}
- net: pcs: xpcs: convert to mdio_device
- net: pcs: xpcs: convert to phylink_pcs_ops
- net: stmmac: split xPCS setup from mdio register
- net: pcs: add 2500BASEX support for Intel mGbE controller
- net: stmmac: enable Intel mGbE 2.5Gbps link speed
- net: stmmac: fix NPD with phylink_set_pcs if there is no MDIO bus
- net: stmmac: explicitly deassert GMAC_AHB_RESET
- net: stmmac: Fix missing { } around two statements in an if statement
- net: pcs: xpcs: rename mdio_xpcs_args to dw_xpcs
- net: stmmac: reduce indentation when calling stmmac_xpcs_setup
- net: pcs: xpcs: move register bit descriptions to a header file
- net: pcs: xpcs: add support for sgmii with no inband AN
- net: pcs: xpcs: also ignore phy id if it's all ones
- net: pcs: xpcs: export xpcs_do_config and xpcs_link_up
- net: stmmac: remove redundant continue statement
- net: stmmac: option to enable PHY WOL with PMT enabled
- stmmac: intel: Enable PHY WOL option in EHL
- stmmac: intel: set PCI_D3hot in suspend
- net: stmmac: separate the tas basetime calculation function
- net: stmmac: ptp: update tas basetime after ptp adjust
- net: pcs: xpcs: fix error handling on failed to allocate memory
- net: pcs: xpcs: Add Pause Mode support for SGMII and 2500BaseX
- net: phy: marvell: Add WAKE_PHY support to WOL event
- net: stmmac: fix INTR TBU status affecting irq count statistic
- net: stmmac: add ethtool per-queue statistic framework
- net: stmmac: add ethtool per-queue irq statistic support
- net: phy: add API to read 802.3-c45 IDs
- igc: Move igc_xdp_is_enabled()
- igc: Refactor __igc_xdp_run_prog()
- igc: Refactor igc_clean_rx_ring()
- igc: Refactor XDP rxq info registration
- igc: Introduce TX/RX stats helpers
- igc: Introduce igc_unmap_tx_buffer() helper
- igc: Replace IGC_TX_FLAGS_XDP flag by an enum
- igc: Enable RX via AF_XDP zero-copy
- igc: Enable TX via AF_XDP zero-copy
- igc: Revert back xdp_rxq_info_reg() registration call
- igc: Fix fail to set fragment size via ethtool
- igc: Enable

[Kernel-packages] [Bug 1945462] Re: EHL graphics support for sprint 2

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7

---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)

  * [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert CET patches

linux-intel-5.13 (5.13.0-1006.6) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1006.6 -proposed tracker (LP:
#1945669)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

  * MEI (Intel Management Engine Interface) for sprint 2 (LP: #1945464)
- Revert "mei: dal: add test module"
- mei: backport fix from 5.12
- Revert "UBUNTU: [Config] Disable INTEL_MEI_DAL and INTEL_MEI_VIRTIO"
- [Config] Enable CONFIG_INTEL_MEI_DAL and CONFIG_INTEL_MEI_VIRTIO

  * [EHL] Intel ishtp VNIC driver (LP: #1943524)
- net: Add support for Intel vnic driver
- [Config] CONFIG_INTEL_ISHTP_VNIC=m

  * [EHL] Quadrature Encoder Peripheral support for sprint 2 (LP: #1945494)
- counter: Add support for Intel Quadrature Encoder Peripheral
- counter: intel-qep: Mark PM callbacks with __maybe_unused
- counter: intel-qep: Use to_pci_dev() helper
- [Config] CONFIG_INTEL_QEP=m

  * I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
(LP: #1945548)
- igc: Remove _I_PHY_ID checking
- igc: Remove phy->type checking

  * [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
(LP: #1929903)
- tcc: update RTCT table parser to support two versions
- Enable support to read a few whitelisted registers.
- Remove Clock_Cycles_VT from MHL entry.
- Add new IOCTL to read error log buffer.
- Display errlog buffer raw data in kernel log as requested once this driver
  is loaded.
- Fix issue found in acrn uos when convert cacheid to apicid.

  * Integrated TSN controller for sprint 2 (LP: #1945461)
- net: pcs: Introducing support for DWC xpcs Energy Efficient Ethernet
- net: stmmac: Add callbacks for DWC xpcs Energy Efficient Ethernet
- net: stmmac: enable platform specific safety features
- net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
- net: stmmac: Fix mixed enum type warning
- net: stmmac: Fix unused values warnings
- stmmac: intel: move definitions to dwmac-intel header file
- stmmac: intel: fix wrong kernel-doc
- stmmac: align RX buffers
- net: stmmac: Fix mixed enum type
- net: pcs: xpcs: delete shim definition for mdio_xpcs_get_ops()
- net: pcs: xpcs: there is only one PHY ID
- net: pcs: xpcs: make the checks related to the PHY interface mode
- net: pcs: xpcs: export xpcs_validate
- net: pcs: xpcs: export xpcs_config_eee
- net: pcs: xpcs: export xpcs_probe
- net: pcs: xpcs: use mdiobus_c45_addr in xpcs_{read,write}
- net: pcs: xpcs: convert to mdio_device
- net: pcs: xpcs: convert to phylink_pcs_ops
- net: stmmac: split xPCS setup from mdio register
- net: pcs: add 2500BASEX support for Intel mGbE controller
- net: stmmac: enable Intel mGbE 2.5Gbps link speed
- net: stmmac: fix NPD with phylink_set_pcs if there is no MDIO bus
- net: stmmac: explicitly deassert GMAC_AHB_RESET
- net: stmmac: Fix missing { } around two statements in an if statement
- net: pcs: xpcs: rename mdio_xpcs_args to dw_xpcs
- net: stmmac: reduce indentation when calling stmmac_xpcs_setup
- net: pcs: xpcs: move register bit descriptions to a header file
- net: pcs: xpcs: add support for sgmii with no inband AN
- net: pcs: xpcs: also ignore phy id if it's all ones
- net: pcs: xpcs: export xpcs_do_config and xpcs_link_up
- net: stmmac: remove redundant continue statement
- net: stmmac: option to enable PHY WOL with PMT enabled
- stmmac: intel: Enable PHY WOL option in EHL
- stmmac: intel: set PCI_D3hot in suspend
- net: stmmac: separate the tas basetime calculation function
- net: stmmac: ptp: update tas basetime after ptp adjust
- net: pcs: xpcs: fix error handling on failed to allocate memory
- net: pcs: xpcs: Add Pause Mode support for SGMII and 2500BaseX
- net: phy: marvell: Add WAKE_PHY support to WOL event
- net: stmmac: fix INTR TBU status affecting irq count statistic
- net: stmmac: add ethtool per-queue statistic framework
- net: stmmac: add ethtool per-queue irq statistic support
- net: phy: add API to read 802.3-c45 IDs
- igc: Move igc_xdp_is_enabled()
- igc: Refactor __igc_xdp_run_prog()
- igc: Refactor igc_clean_rx_ring()
- igc: Refactor XDP rxq info registration
- igc: Introduce TX/RX stats helpers
- igc: Introduce igc_unmap_tx_buffer() helper
- igc: Replace IGC_TX_FLAGS_XDP flag by an enum
- igc: Enable RX via AF_XDP zero-copy
- igc: Enable TX via AF_XDP zero-copy
- igc: Revert back xdp_rxq_info_reg() registration call
- igc: Fix fail to set fragment size via ethtool
- igc: Enable

[Kernel-packages] [Bug 1945464] Re: MEI (Intel Management Engine Interface) for sprint 2

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7

---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)

  * [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert CET patches

linux-intel-5.13 (5.13.0-1006.6) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1006.6 -proposed tracker (LP:
#1945669)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

  * MEI (Intel Management Engine Interface) for sprint 2 (LP: #1945464)
- Revert "mei: dal: add test module"
- mei: backport fix from 5.12
- Revert "UBUNTU: [Config] Disable INTEL_MEI_DAL and INTEL_MEI_VIRTIO"
- [Config] Enable CONFIG_INTEL_MEI_DAL and CONFIG_INTEL_MEI_VIRTIO

  * [EHL] Intel ishtp VNIC driver (LP: #1943524)
- net: Add support for Intel vnic driver
- [Config] CONFIG_INTEL_ISHTP_VNIC=m

  * [EHL] Quadrature Encoder Peripheral support for sprint 2 (LP: #1945494)
- counter: Add support for Intel Quadrature Encoder Peripheral
- counter: intel-qep: Mark PM callbacks with __maybe_unused
- counter: intel-qep: Use to_pci_dev() helper
- [Config] CONFIG_INTEL_QEP=m

  * I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
(LP: #1945548)
- igc: Remove _I_PHY_ID checking
- igc: Remove phy->type checking

  * [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
(LP: #1929903)
- tcc: update RTCT table parser to support two versions
- Enable support to read a few whitelisted registers.
- Remove Clock_Cycles_VT from MHL entry.
- Add new IOCTL to read error log buffer.
- Display errlog buffer raw data in kernel log as requested once this driver
  is loaded.
- Fix issue found in acrn uos when convert cacheid to apicid.

  * Integrated TSN controller for sprint 2 (LP: #1945461)
- net: pcs: Introducing support for DWC xpcs Energy Efficient Ethernet
- net: stmmac: Add callbacks for DWC xpcs Energy Efficient Ethernet
- net: stmmac: enable platform specific safety features
- net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
- net: stmmac: Fix mixed enum type warning
- net: stmmac: Fix unused values warnings
- stmmac: intel: move definitions to dwmac-intel header file
- stmmac: intel: fix wrong kernel-doc
- stmmac: align RX buffers
- net: stmmac: Fix mixed enum type
- net: pcs: xpcs: delete shim definition for mdio_xpcs_get_ops()
- net: pcs: xpcs: there is only one PHY ID
- net: pcs: xpcs: make the checks related to the PHY interface mode
- net: pcs: xpcs: export xpcs_validate
- net: pcs: xpcs: export xpcs_config_eee
- net: pcs: xpcs: export xpcs_probe
- net: pcs: xpcs: use mdiobus_c45_addr in xpcs_{read,write}
- net: pcs: xpcs: convert to mdio_device
- net: pcs: xpcs: convert to phylink_pcs_ops
- net: stmmac: split xPCS setup from mdio register
- net: pcs: add 2500BASEX support for Intel mGbE controller
- net: stmmac: enable Intel mGbE 2.5Gbps link speed
- net: stmmac: fix NPD with phylink_set_pcs if there is no MDIO bus
- net: stmmac: explicitly deassert GMAC_AHB_RESET
- net: stmmac: Fix missing { } around two statements in an if statement
- net: pcs: xpcs: rename mdio_xpcs_args to dw_xpcs
- net: stmmac: reduce indentation when calling stmmac_xpcs_setup
- net: pcs: xpcs: move register bit descriptions to a header file
- net: pcs: xpcs: add support for sgmii with no inband AN
- net: pcs: xpcs: also ignore phy id if it's all ones
- net: pcs: xpcs: export xpcs_do_config and xpcs_link_up
- net: stmmac: remove redundant continue statement
- net: stmmac: option to enable PHY WOL with PMT enabled
- stmmac: intel: Enable PHY WOL option in EHL
- stmmac: intel: set PCI_D3hot in suspend
- net: stmmac: separate the tas basetime calculation function
- net: stmmac: ptp: update tas basetime after ptp adjust
- net: pcs: xpcs: fix error handling on failed to allocate memory
- net: pcs: xpcs: Add Pause Mode support for SGMII and 2500BaseX
- net: phy: marvell: Add WAKE_PHY support to WOL event
- net: stmmac: fix INTR TBU status affecting irq count statistic
- net: stmmac: add ethtool per-queue statistic framework
- net: stmmac: add ethtool per-queue irq statistic support
- net: phy: add API to read 802.3-c45 IDs
- igc: Move igc_xdp_is_enabled()
- igc: Refactor __igc_xdp_run_prog()
- igc: Refactor igc_clean_rx_ring()
- igc: Refactor XDP rxq info registration
- igc: Introduce TX/RX stats helpers
- igc: Introduce igc_unmap_tx_buffer() helper
- igc: Replace IGC_TX_FLAGS_XDP flag by an enum
- igc: Enable RX via AF_XDP zero-copy
- igc: Enable TX via AF_XDP zero-copy
- igc: Revert back xdp_rxq_info_reg() registration call
- igc: Fix fail to set fragment size via ethtool
- igc: Enable

[Kernel-packages] [Bug 1945494] Re: [EHL] Quadrature Encoder Peripheral support for sprint 2

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7

---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)

  * [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert CET patches

linux-intel-5.13 (5.13.0-1006.6) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1006.6 -proposed tracker (LP:
#1945669)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

  * MEI (Intel Management Engine Interface) for sprint 2 (LP: #1945464)
- Revert "mei: dal: add test module"
- mei: backport fix from 5.12
- Revert "UBUNTU: [Config] Disable INTEL_MEI_DAL and INTEL_MEI_VIRTIO"
- [Config] Enable CONFIG_INTEL_MEI_DAL and CONFIG_INTEL_MEI_VIRTIO

  * [EHL] Intel ishtp VNIC driver (LP: #1943524)
- net: Add support for Intel vnic driver
- [Config] CONFIG_INTEL_ISHTP_VNIC=m

  * [EHL] Quadrature Encoder Peripheral support for sprint 2 (LP: #1945494)
- counter: Add support for Intel Quadrature Encoder Peripheral
- counter: intel-qep: Mark PM callbacks with __maybe_unused
- counter: intel-qep: Use to_pci_dev() helper
- [Config] CONFIG_INTEL_QEP=m

  * I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
(LP: #1945548)
- igc: Remove _I_PHY_ID checking
- igc: Remove phy->type checking

  * [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
(LP: #1929903)
- tcc: update RTCT table parser to support two versions
- Enable support to read a few whitelisted registers.
- Remove Clock_Cycles_VT from MHL entry.
- Add new IOCTL to read error log buffer.
- Display errlog buffer raw data in kernel log as requested once this driver
  is loaded.
- Fix issue found in acrn uos when convert cacheid to apicid.

  * Integrated TSN controller for sprint 2 (LP: #1945461)
- net: pcs: Introducing support for DWC xpcs Energy Efficient Ethernet
- net: stmmac: Add callbacks for DWC xpcs Energy Efficient Ethernet
- net: stmmac: enable platform specific safety features
- net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
- net: stmmac: Fix mixed enum type warning
- net: stmmac: Fix unused values warnings
- stmmac: intel: move definitions to dwmac-intel header file
- stmmac: intel: fix wrong kernel-doc
- stmmac: align RX buffers
- net: stmmac: Fix mixed enum type
- net: pcs: xpcs: delete shim definition for mdio_xpcs_get_ops()
- net: pcs: xpcs: there is only one PHY ID
- net: pcs: xpcs: make the checks related to the PHY interface mode
- net: pcs: xpcs: export xpcs_validate
- net: pcs: xpcs: export xpcs_config_eee
- net: pcs: xpcs: export xpcs_probe
- net: pcs: xpcs: use mdiobus_c45_addr in xpcs_{read,write}
- net: pcs: xpcs: convert to mdio_device
- net: pcs: xpcs: convert to phylink_pcs_ops
- net: stmmac: split xPCS setup from mdio register
- net: pcs: add 2500BASEX support for Intel mGbE controller
- net: stmmac: enable Intel mGbE 2.5Gbps link speed
- net: stmmac: fix NPD with phylink_set_pcs if there is no MDIO bus
- net: stmmac: explicitly deassert GMAC_AHB_RESET
- net: stmmac: Fix missing { } around two statements in an if statement
- net: pcs: xpcs: rename mdio_xpcs_args to dw_xpcs
- net: stmmac: reduce indentation when calling stmmac_xpcs_setup
- net: pcs: xpcs: move register bit descriptions to a header file
- net: pcs: xpcs: add support for sgmii with no inband AN
- net: pcs: xpcs: also ignore phy id if it's all ones
- net: pcs: xpcs: export xpcs_do_config and xpcs_link_up
- net: stmmac: remove redundant continue statement
- net: stmmac: option to enable PHY WOL with PMT enabled
- stmmac: intel: Enable PHY WOL option in EHL
- stmmac: intel: set PCI_D3hot in suspend
- net: stmmac: separate the tas basetime calculation function
- net: stmmac: ptp: update tas basetime after ptp adjust
- net: pcs: xpcs: fix error handling on failed to allocate memory
- net: pcs: xpcs: Add Pause Mode support for SGMII and 2500BaseX
- net: phy: marvell: Add WAKE_PHY support to WOL event
- net: stmmac: fix INTR TBU status affecting irq count statistic
- net: stmmac: add ethtool per-queue statistic framework
- net: stmmac: add ethtool per-queue irq statistic support
- net: phy: add API to read 802.3-c45 IDs
- igc: Move igc_xdp_is_enabled()
- igc: Refactor __igc_xdp_run_prog()
- igc: Refactor igc_clean_rx_ring()
- igc: Refactor XDP rxq info registration
- igc: Introduce TX/RX stats helpers
- igc: Introduce igc_unmap_tx_buffer() helper
- igc: Replace IGC_TX_FLAGS_XDP flag by an enum
- igc: Enable RX via AF_XDP zero-copy
- igc: Enable TX via AF_XDP zero-copy
- igc: Revert back xdp_rxq_info_reg() registration call
- igc: Fix fail to set fragment size via ethtool
- igc: Enable

[Kernel-packages] [Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot

This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7

---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)

  * [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert CET patches

linux-intel-5.13 (5.13.0-1006.6) focal; urgency=medium

  * focal/linux-intel-5.13: 5.13.0-1006.6 -proposed tracker (LP:
#1945669)

  * Packaging resync (LP: #1786013)
- [Packaging] update variants

  * MEI (Intel Management Engine Interface) for sprint 2 (LP: #1945464)
- Revert "mei: dal: add test module"
- mei: backport fix from 5.12
- Revert "UBUNTU: [Config] Disable INTEL_MEI_DAL and INTEL_MEI_VIRTIO"
- [Config] Enable CONFIG_INTEL_MEI_DAL and CONFIG_INTEL_MEI_VIRTIO

  * [EHL] Intel ishtp VNIC driver (LP: #1943524)
- net: Add support for Intel vnic driver
- [Config] CONFIG_INTEL_ISHTP_VNIC=m

  * [EHL] Quadrature Encoder Peripheral support for sprint 2 (LP: #1945494)
- counter: Add support for Intel Quadrature Encoder Peripheral
- counter: intel-qep: Mark PM callbacks with __maybe_unused
- counter: intel-qep: Use to_pci_dev() helper
- [Config] CONFIG_INTEL_QEP=m

  * I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
(LP: #1945548)
- igc: Remove _I_PHY_ID checking
- igc: Remove phy->type checking

  * [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
(LP: #1929903)
- tcc: update RTCT table parser to support two versions
- Enable support to read a few whitelisted registers.
- Remove Clock_Cycles_VT from MHL entry.
- Add new IOCTL to read error log buffer.
- Display errlog buffer raw data in kernel log as requested once this driver
  is loaded.
- Fix issue found in acrn uos when convert cacheid to apicid.

  * Integrated TSN controller for sprint 2 (LP: #1945461)
- net: pcs: Introducing support for DWC xpcs Energy Efficient Ethernet
- net: stmmac: Add callbacks for DWC xpcs Energy Efficient Ethernet
- net: stmmac: enable platform specific safety features
- net: phy: probe for C45 PHYs that return PHY ID of zero in C22 space
- net: stmmac: Fix mixed enum type warning
- net: stmmac: Fix unused values warnings
- stmmac: intel: move definitions to dwmac-intel header file
- stmmac: intel: fix wrong kernel-doc
- stmmac: align RX buffers
- net: stmmac: Fix mixed enum type
- net: pcs: xpcs: delete shim definition for mdio_xpcs_get_ops()
- net: pcs: xpcs: there is only one PHY ID
- net: pcs: xpcs: make the checks related to the PHY interface mode
- net: pcs: xpcs: export xpcs_validate
- net: pcs: xpcs: export xpcs_config_eee
- net: pcs: xpcs: export xpcs_probe
- net: pcs: xpcs: use mdiobus_c45_addr in xpcs_{read,write}
- net: pcs: xpcs: convert to mdio_device
- net: pcs: xpcs: convert to phylink_pcs_ops
- net: stmmac: split xPCS setup from mdio register
- net: pcs: add 2500BASEX support for Intel mGbE controller
- net: stmmac: enable Intel mGbE 2.5Gbps link speed
- net: stmmac: fix NPD with phylink_set_pcs if there is no MDIO bus
- net: stmmac: explicitly deassert GMAC_AHB_RESET
- net: stmmac: Fix missing { } around two statements in an if statement
- net: pcs: xpcs: rename mdio_xpcs_args to dw_xpcs
- net: stmmac: reduce indentation when calling stmmac_xpcs_setup
- net: pcs: xpcs: move register bit descriptions to a header file
- net: pcs: xpcs: add support for sgmii with no inband AN
- net: pcs: xpcs: also ignore phy id if it's all ones
- net: pcs: xpcs: export xpcs_do_config and xpcs_link_up
- net: stmmac: remove redundant continue statement
- net: stmmac: option to enable PHY WOL with PMT enabled
- stmmac: intel: Enable PHY WOL option in EHL
- stmmac: intel: set PCI_D3hot in suspend
- net: stmmac: separate the tas basetime calculation function
- net: stmmac: ptp: update tas basetime after ptp adjust
- net: pcs: xpcs: fix error handling on failed to allocate memory
- net: pcs: xpcs: Add Pause Mode support for SGMII and 2500BaseX
- net: phy: marvell: Add WAKE_PHY support to WOL event
- net: stmmac: fix INTR TBU status affecting irq count statistic
- net: stmmac: add ethtool per-queue statistic framework
- net: stmmac: add ethtool per-queue irq statistic support
- net: phy: add API to read 802.3-c45 IDs
- igc: Move igc_xdp_is_enabled()
- igc: Refactor __igc_xdp_run_prog()
- igc: Refactor igc_clean_rx_ring()
- igc: Refactor XDP rxq info registration
- igc: Introduce TX/RX stats helpers
- igc: Introduce igc_unmap_tx_buffer() helper
- igc: Replace IGC_TX_FLAGS_XDP flag by an enum
- igc: Enable RX via AF_XDP zero-copy
- igc: Enable TX via AF_XDP zero-copy
- igc: Revert back xdp_rxq_info_reg() registration call
- igc: Fix fail to set fragment size via ethtool
- igc: Enable

[Kernel-packages] [Bug 1946828] Re: ntfsresize hang and call traces in syslog

2021-10-27 Thread Dan Bungert

@Etienne - agree, probably a dupe

@Jeremy - I ran "ntfsresize -f -i /dev/sda4" manually before the
installer ran and ntfsresize had no issue.  Later during this same run,
I saw the hang when ntfsresize was run by Ubiquity.

@Jean-Pierre - I suspect this is a kernel bug more than I suspect a
ntfsresize one.

Here's a sample process tree:
   5991 S   sh -c ubiquity gtk_ui
   5992 S   /bin/sh /usr/lib/udisks2/udisks2-inhibit /usr/lib/ubiquit
   6002 Sl  /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui
   6411 Ss+ /bin/busybox tail -f /var/log/installer/debug -f /var/log
   8639 S   /usr/bin/perl -w /usr/bin/debconf-communicate -fnonintera
   9107 S   /usr/share/ubiquity/activate-dmraid && /bin/partman
   9108 S   /usr/share/ubiquity/activate-dmraid && /bin/partman
   9114 S   /bin/sh /bin/partman
  10014 S   /bin/sh /lib/partman/display.d/10initial_auto
  10060 S   /bin/sh /lib/partman/display.d/10initial_auto
  10062 S   /bin/sh /lib/partman/automatically_partition/10resize_use
  10131 D   [ntfsresize]

ntfsresize has been invoked as "ntfsresize -f -i /dev/sda4", where this
sda4 is a partition created by Windows 10, is NTFS, and is 508MiB.
Also, if I kill parent process of ntfsresize (pid 10062 in this case),
the install is able to continue.

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

Title:
  ntfsresize hang and call traces in syslog

Status in linux package in Ubuntu:
  Confirmed
Status in ntfs-3g package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot the impish final iso on my kvm VM setup with a
  windows 10 install on the virtual disk.  The install process hangs at
  the "updates and other software" screen, apparently on a ntfsresize
  call.  Mind you, this is before I have chosen disks to partition - I'm
  at the step where I can choose a Normal or Minimal installation.

  While this is not a 100% reproduction rate issue, the rate seems high
  - above 50% I would guess.  If I try to quickly click thru the
  installer on boot it might be a little more likely.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-19-generic 5.13.0-19.19
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4609 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 13 02:40:56 2021
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-19-generic N/A
   linux-backports-modules-5.13.0-19-generic  N/A
   linux-firmware 1.201
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-5.2
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.2:sku:cvnQEMU:ct1:cvrpc-q35-5.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-5.2
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs

For future reference, this bug has been reported in Ubuntu KVM hosts
outside of the specific kdump test scenario (i.e. when running actual
VMs in production-like setups). The "kdump with multiple CPUs" case was
discovered as an alternative that hits the same MMU context bug, without
needing complex hypervisor setups or fancy configuration.

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

Title:
  KVM emulation failure when booting into  VM crash kernel with multiple
  CPUs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]
  When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM 
emulation failure. This will cause the VM to go into the "paused" state, and 
prevents it from being restored without a full VM restart.

  This happens only when there are multiple enabled CPUs in the crash
  kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is
  being used. Due to the vCPU MMU state not being cleaned up correctly,
  the secondary CPUs try to access virtual addresses with a faulty MMU
  context that will result in the emulation failure. This shows up with
  a similar spew as below:

  $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log
  KVM internal error. Suberror: 1
  emulation failure
  EAX=de8f EBX= ECX=008f EDX=0600
  ESI= EDI= EBP= ESP=f90c
  EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000 000f  9b00
  SS =de00 000de000  9300
  DS =de00 000de000  9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3=290b8001 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70  71 66 
0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a

  [Test Plan]
  1. Boot an Ubuntu guest VM with e.g. multipass:
  $ multipass launch daily:focal -c8 -m16g -n focal-vm

  2. Configure guest crash kernel command-line with `nr_cpus=8`:
  ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line
  KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service 
nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0"

  3. Crash guest VM and watch for the KVM emulation failure:
  ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger

  [Where problems could occur]
  As we're resetting MMU context on vCPUs, potential regressions would show up 
in workloads relying on KVM guests. We should properly test the scenario 
mentioned in the bug to make sure secondary CPUs are being cleaned up properly, 
and that no other regressions have been introduced when rebooting or kexec'ing 
into different kernels.
  Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression 
potential should be fairly low and contained to starting/resetting vCPUs (i.e. 
VM start and reboot).

  [Other info]
  This has been fixed by upstream commit:
0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT

  The commit above has been picked up by stable trees up until 5.11, so it's 
only needed in Bionic and Focal (4.15 and 5.4 kernels). There are also two 
follow up commits, which revert the vendor-specific resets:
5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()

  These follow ups have not been picked up in stable trees due to the risk of
  regressions. According to the original fix, they have been introduced 
primarily to aid bisection in case there are workflows relying on the vendor 
resets. As these are not required for the fix and don't conflict with the 
backport, we should leave them out to prevent potential regressions in the 
older kernels.

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


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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2021-10-27 Thread Mariano López

Our serves are affected by this bug too in focal and it triggered today
in one of our servers.

Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal

We have seen this in:
- Ubuntu 5.4.0-89.100-generic
- Ubuntu 5.4.0-88.99-generic

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-27 Thread randomdave

I have the same hardware as rudolfharney. Kernel panic still happening
in linux-image-5.13.0-20-generic even after rudulf's suggestion "start
BIOS, exit with SAVE=YES". Also, disabling the trackpad doesn't prevent
the panic.

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels

2021-10-27 Thread fossfreedom

I have no idea why the status has changed ... the fix hasn't entered the
archive yet.

** Changed in: linux-raspi (Ubuntu Impish)
   Status: Fix Released => Fix Committed

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

Title:
  HDMI output freezes under current/proposed impish kernels

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  The UI of Impish desktop for raspi occasionally freezes which can be
  triggered by playing videos and moving windows around. Seems to happen
  more frequently when using higher resolutions and/or higher refresh
  rates (higher than 1920x1080@60Hz).

  Kernel errors are along the lines of:
  [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] co
  mmit wait timed out
  [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] flip_
  done timed out

  [Test Case]

  Install current Impish desktop for raspi on a Pi 4. Use a high-
  refresh/resolution monitor. Play videos, move windows around.

  [Fix]

  The Pi foundation identified a couple of upstream vc4 commits that
  seem to interfere with their downstream patches. Revert those to match
  the Pi foundations currently released 5.10 kernel.

  [Where Problems Could Occur]

  The changes are confined to the vc4 driver, so problems would only
  show up if that driver is in use. Which is only the case for the
  Ubuntu raspi desktop image, so server images should not be impacted at
  all.

  [Original Description]

  Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
  for the Ubuntu Pi pre-installed desktop impish release, the HDMI
  output occasionally freezes. A known workaround at this time is to
  change the following line in /boot/firmware/config.txt:

  dtoverlay=vc4-kms-v3d

  To the following:

  dtoverlay=vc4-fkms-v3d

  In other words, to use the "fake" KMS overlay (fkms) instead of the
  "full" KMS overlay (kms).

  I've been unable to determine a reliable method of guaranteeing a
  freeze, but it appears to occur much more readily when video playback
  is occurring, and when other interactions (especially moving windows
  around, minimizing, restoring) occurs simultaneously.  Display suspend
  also periodically causes the same hang, which made me suspect this
  might be related to #1944397 but it appears that had a separate cause
  (now resolved).

  The following dmesg outputs have been observed immediately after the
  display hang; this one from 1007.8:

  [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] co
  mmit wait timed out
  [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] flip_
  done timed out
  [  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [PLANE:205:plane-25
  ] commit wait timed out
  [  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
  [  534.250685] [ cut here ]
  [  534.250701] refcount_t: underflow; use-after-free.
  [  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 
refcount_dec_not_one+0xa0/0xbc
  [  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher 
af_alg hci_uart btqca btrtl btbcm
   btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth 
snd_compress snd_bcm2835(C)
   snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi 
snd_seq_midi_event bcm2835_codec(C) bcm
  2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem 
bcm2835_mmal_vchiq(C) videobuf2_dma_contig
  videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq 
videobuf2_common videodev snd_seq_devi
  ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem 
uio_pdrv_genirq uio sch_fq_
  codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon 
zstd_compress hid_generic usbhid raid
  6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core 
gpu_sched crct10dif_ce i2c_
  brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci 
xhci_pci_renesas sysfillrect sysimgbl
  t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64
  [  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: GWC
5.13.0-1007-raspi #8-Ubuntu
  [  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
  [  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
  [  534.251239]

[Kernel-packages] [Bug 1946368] Re: HDMI output freezes under current/proposed impish kernels

2021-10-27 Thread Ganesh Chandar Devulapalli

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

Title:
  HDMI output freezes under current/proposed impish kernels

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Impish:
  Fix Released

Bug description:
  [Impact]

  The UI of Impish desktop for raspi occasionally freezes which can be
  triggered by playing videos and moving windows around. Seems to happen
  more frequently when using higher resolutions and/or higher refresh
  rates (higher than 1920x1080@60Hz).

  Kernel errors are along the lines of:
  [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] co
  mmit wait timed out
  [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] flip_
  done timed out

  [Test Case]

  Install current Impish desktop for raspi on a Pi 4. Use a high-
  refresh/resolution monitor. Play videos, move windows around.

  [Fix]

  The Pi foundation identified a couple of upstream vc4 commits that
  seem to interfere with their downstream patches. Revert those to match
  the Pi foundations currently released 5.10 kernel.

  [Where Problems Could Occur]

  The changes are confined to the vc4 driver, so problems would only
  show up if that driver is in use. Which is only the case for the
  Ubuntu raspi desktop image, so server images should not be impacted at
  all.

  [Original Description]

  Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
  for the Ubuntu Pi pre-installed desktop impish release, the HDMI
  output occasionally freezes. A known workaround at this time is to
  change the following line in /boot/firmware/config.txt:

  dtoverlay=vc4-kms-v3d

  To the following:

  dtoverlay=vc4-fkms-v3d

  In other words, to use the "fake" KMS overlay (fkms) instead of the
  "full" KMS overlay (kms).

  I've been unable to determine a reliable method of guaranteeing a
  freeze, but it appears to occur much more readily when video playback
  is occurring, and when other interactions (especially moving windows
  around, minimizing, restoring) occurs simultaneously.  Display suspend
  also periodically causes the same hang, which made me suspect this
  might be related to #1944397 but it appears that had a separate cause
  (now resolved).

  The following dmesg outputs have been observed immediately after the
  display hang; this one from 1007.8:

  [  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] co
  mmit wait timed out
  [  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] flip_
  done timed out
  [  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [PLANE:205:plane-25
  ] commit wait timed out
  [  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
  [  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
  [  534.250685] [ cut here ]
  [  534.250701] refcount_t: underflow; use-after-free.
  [  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 
refcount_dec_not_one+0xa0/0xbc
  [  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher 
af_alg hci_uart btqca btrtl btbcm
   btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth 
snd_compress snd_bcm2835(C)
   snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi 
snd_seq_midi_event bcm2835_codec(C) bcm
  2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem 
bcm2835_mmal_vchiq(C) videobuf2_dma_contig
  videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq 
videobuf2_common videodev snd_seq_devi
  ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem 
uio_pdrv_genirq uio sch_fq_
  codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon 
zstd_compress hid_generic usbhid raid
  6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core 
gpu_sched crct10dif_ce i2c_
  brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci 
xhci_pci_renesas sysfillrect sysimgbl
  t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64
  [  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: GWC
5.13.0-1007-raspi #8-Ubuntu
  [  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
  [  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
  [  534.251239] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--)
  [  534.251248] pc :

[Kernel-packages] [Bug 1948977] [NEW] Impish update: upstream stable patchset 2021-10-27

2021-10-27 Thread Kamal Mostafa

Public bug reported:

SRU Justification

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

   upstream stable patchset 2021-10-27

Ported from the following upstream stable releases:
v5.10.69, v5.14.8

   from git://git.kernel.org/

PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
PCI: aardvark: Fix reporting CRS value
console: consume APC, DM, DCS
ARM: 9077/1: PLT: Move struct plt_entries definition to header
ARM: 9078/1: Add warn suppress parameter to arm_gen_branch_link()
ARM: 9079/1: ftrace: Add MODULE_PLTS support
ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without DYNAMIC_FTRACE
sctp: validate chunk size in __rcv_asconf_lookup
sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
coredump: fix memleak in dump_vma_snapshot()
um: virtio_uml: fix memory leak on init failures
dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
perf test: Fix bpf test sample mismatch reporting
perf tools: Allow build-id with trailing zeros
thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
9p/trans_virtio: Remove sysfs file on probe failure
prctl: allow to setup brk for et_dyn executables
nilfs2: use refcount_dec_and_lock() to fix potential UAF
profiling: fix shift-out-of-bounds bugs
PM: sleep: core: Avoid setting power.must_resume to false
pwm: lpc32xx: Don't modify HW state in .probe() after the PWM chip was 
registered
pwm: mxs: Don't modify HW state in .probe() after the PWM chip was registered
dmaengine: idxd: fix wq slot allocation index check
platform/chrome: sensorhub: Add trace events for sample
platform/chrome: cros_ec_trace: Fix format warnings
ceph: allow ceph_put_mds_session to take NULL or ERR_PTR
ceph: cancel delayed work instead of flushing on mdsc teardown
Kconfig.debug: drop selecting non-existing HARDLOCKUP_DETECTOR_ARCH
tools/bootconfig: Fix tracing_on option checking in ftrace2bconf.sh
thermal/core: Fix thermal_cooling_device_register() prototype
drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
drivers: base: cacheinfo: Get rid of DEFINE_SMP_CALL_CACHE_FUNCTION()
dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
parisc: Move pci_dev_is_behind_card_dino to where it is used
iommu/amd: Relocate GAMSup check to early_enable_iommus
dmaengine: idxd: depends on !UML
dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
dmaengine: ioat: depends on !UML
dmaengine: xilinx_dma: Set DMA mask for coherent APIs
ceph: request Fw caps before updating the mtime in ceph_write_iter
ceph: remove the capsnaps when removing caps
ceph: lockdep annotations for try_nonblocking_invalidate
btrfs: update the bdev time directly when closing
btrfs: fix lockdep warning while mounting sprout fs
nilfs2: fix memory leak in nilfs_sysfs_create_device_group
nilfs2: fix NULL pointer in nilfs_##name##_attr_release
nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
habanalabs: add validity check for event ID received from F/W
pwm: img: Don't modify HW state in .remove() callback
pwm: rockchip: Don't modify HW state in .remove() callback
pwm: stm32-lp: Don't modify HW state in .remove() callback
blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for multiple_queues
rtc: rx8010: select REGMAP_I2C
sched/idle: Make the idle timer expire in hard interrupt context
drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
um: fix stub location calculation
RDMA/mlx5: Fix xlt_chunk_align calculation
perf symbol: Look for ImageBase in PE file to compute .text offset
staging: rtl8723bs: fix wpa_set_auth_algs() function
n64cart: fix return value check in n64cart_probe()
pwm: ab8500: Fix register offset calculation to not depend on probe order
thermal/drivers/qcom/spmi-adc-tm5: Don't abort probing if a sensor is not used
dmanegine: idxd: cleanup all device related bits after disabling device
dmaengine: idxd: have command status always set
dmaengine: idxd: fix abort status check
dmaengine: idxd: clear block on fault flag when clear wq
SUNRPC: don't pause on incomplete allocation
init: move usermodehelper_enable() to populate_rootfs()
dma-buf: DMABUF_DEBUG should depend on DMA_SHARED_BUFFER
arm64: mm: limit linear region to 51 bits for KVM in nVHE mode
drm/ttm: Fix a deadlock if the target BO is not idle during swap
of: property: Disable fw_devlink DT support for X86

[Kernel-packages] [Bug 1945289] Re: Failed to properly resume from S3 (suspend-to-ram) on kernel version 5.13.0-16 (installed while updating to impish), amdgpu driver.

2021-10-27 Thread Colin Brown

Experiencing the same problem after upgrade to Impish. I have determined
that the desktop does actually start after a resume from suspend, but
the screen remains blank, with the backlight on. (To determine this, I
used a keyboard shortcut to launch a terminal window and typed a reboot
command successfully.)

Everything in the kernel log seemed normal for the interval around the
suspend/restore (although there's so much stuff there, it's hard to be
sure.)

The screen does come on OK after a full reboot.

As with the OP, suspend/restore is OK if I back off to using the 5.11
kernel. Also as for the OP, my system is using the amdgpu driver.

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

Title:
  Failed to properly resume from S3 (suspend-to-ram) on kernel version
  5.13.0-16 (installed while updating to impish), amdgpu driver.

Status in linux-meta package in Ubuntu:
  New

Bug description:
  On 5.11.0 everything is OK.
  The GPU is AMD Carrizo APU.

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


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

[Kernel-packages] [Bug 1830585] Re: cpuset_memory_spread from controllers test suite in LTP failed (hog the memory on the unexpected node)

hirsute linux-aws 5.11.0-1021.22 i3.metal,i3en.24xlarge,r5.metal

** Tags added: sru-20211018

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

Title:
  cpuset_memory_spread from controllers test suite in LTP failed (hog
  the memory on the unexpected node)

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-azure source package in Bionic:
  New
Status in linux source package in Disco:
  Won't Fix
Status in linux-azure source package in Disco:
  Won't Fix
Status in linux source package in Focal:
  New
Status in linux-azure source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux-azure source package in Hirsute:
  New

Bug description:
  Test failed with:
  cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected 
node(FilePages_For_Nodes(KB): _0: 2276
  _1: 102428, Expect Nodes: 1).

  <<>>
  tag=cpuset_memory_spread stime=1558937747
  cmdline="   cpuset_memory_spread_testset.sh"
  contacts=""
  analysis=exit
  <<>>
  100+0 records in
  100+0 records out
  104857600 bytes (105 MB, 100 MiB) copied, 0.0993112 s, 1.1 GB/s
  cpuset_memory_spread 1 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 3 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 5 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 7 TFAIL: hog the memory on the unexpected 
node(FilePages_For_Nodes(KB): _0: 2276
  _1: 102428, Expect Nodes: 1).
  cpuset_memory_spread 9 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 11 TPASS: Cpuset memory spread page test succeeded.
  cpuset_memory_spread 13 TPASS: Cpuset memory spread page test succeeded.
  <<>>
  initiation_status="ok"
  duration=10 termination_type=exited termination_id=1 corefile=no
  cutime=364 cstime=383
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 27 05:39 seq
   crw-rw 1 root audio 116, 33 May 27 05:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon May 27 06:16:49 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:

  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.product.sku: 780020-S01
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1948610] Re: Home directory not recognized

2021-10-27 Thread mark maurer

Problem fixed with release of linux-oem-5.14.0-1006

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

Title:
  Home directory not recognized

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

Bug description:
  Used synaptic package manager to install linux-oem-20.04d kernel.  After 
reboot login worked fine, but then desktop reverted to default background and 
scale factor of 1 instead of 2.  (the new installation dialog appeared on 
desktop after login).
  Nautilus was very sluggish to open.  Normal /home was not shown. 

  Rebooted and removed Linus-oem-20.04d and everything is fine.

  I use a ZFS zpool mirror for my /home (since 16.04 actually).  I had
  great luck using the linux-oem-5.10 kernel in the past, but this time
  the oem kernel is behaving differently.

  I am happy to stay on standard Ubuntu kernel, but just wanted to
  report this behavior.

  
***

  lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS

  linux-oem-20.04d

  expected to upgrade kernel while leaving desktop and preferences
  intact

  instead my /home was not recognized and desktop reverted to that of a
  new installation

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-oem-20.04d (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 24 19:30:41 2021
  InstallationDate: Installed on 2020-11-15 (343 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-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-meta-oem-5.14/+bug/1948610/+subscriptions


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

[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs

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

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

Title:
  KVM emulation failure when booting into  VM crash kernel with multiple
  CPUs

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed

Bug description:
  [Impact]
  When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM 
emulation failure. This will cause the VM to go into the "paused" state, and 
prevents it from being restored without a full VM restart.

  This happens only when there are multiple enabled CPUs in the crash
  kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is
  being used. Due to the vCPU MMU state not being cleaned up correctly,
  the secondary CPUs try to access virtual addresses with a faulty MMU
  context that will result in the emulation failure. This shows up with
  a similar spew as below:

  $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log
  KVM internal error. Suberror: 1
  emulation failure
  EAX=de8f EBX= ECX=008f EDX=0600
  ESI= EDI= EBP= ESP=f90c
  EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000 000f  9b00
  SS =de00 000de000  9300
  DS =de00 000de000  9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3=290b8001 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70  71 66 
0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a

  [Test Plan]
  1. Boot an Ubuntu guest VM with e.g. multipass:
  $ multipass launch daily:focal -c8 -m16g -n focal-vm

  2. Configure guest crash kernel command-line with `nr_cpus=8`:
  ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line
  KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service 
nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0"

  3. Crash guest VM and watch for the KVM emulation failure:
  ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger

  [Where problems could occur]
  As we're resetting MMU context on vCPUs, potential regressions would show up 
in workloads relying on KVM guests. We should properly test the scenario 
mentioned in the bug to make sure secondary CPUs are being cleaned up properly, 
and that no other regressions have been introduced when rebooting or kexec'ing 
into different kernels.
  Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression 
potential should be fairly low and contained to starting/resetting vCPUs (i.e. 
VM start and reboot).

  [Other info]
  This has been fixed by upstream commit:
0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT

  The commit above has been picked up by stable trees up until 5.11, so it's 
only needed in Bionic and Focal (4.15 and 5.4 kernels). There are also two 
follow up commits, which revert the vendor-specific resets:
5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()

  These follow ups have not been picked up in stable trees due to the risk of
  regressions. According to the original fix, they have been introduced 
primarily to aid bisection in case there are workflows relying on the vendor 
resets. As these are not required for the fix and don't conflict with the 
backport, we should leave them out to prevent potential regressions in the 
older kernels.

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


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

[Kernel-packages] [Bug 1929247] Re: kernel/selftests: seccomp_benchmark fails with timeout in H/KVM

Seen with aws 5.11.0-1021.22 on m5a.large and r5.metal

** Tags added: aws sru-20211018

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

Title:
  kernel/selftests: seccomp_benchmark fails with timeout in H/KVM

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Hirsute:
  New

Bug description:
  Found that on cycle sru-20210510, on H/KVM 5.11.0-1008.8 :

  02:36:23 DEBUG| [stdout] # selftests: seccomp: seccomp_benchmark
  02:36:23 DEBUG| [stdout] # sysctl: cannot stat 
/proc/sys/net/core/bpf_jit_enable: No such file or directory
  02:36:23 DEBUG| [stdout] # sysctl: cannot stat 
/proc/sys/net/core/bpf_jit_harden: No such file or directory
  02:38:23 DEBUG| [stdout] # 
  02:38:23 DEBUG| [stdout] not ok 2 selftests: seccomp: seccomp_benchmark # 
TIMEOUT 120 seconds

  In the previous cycle this test worked, but this one failed due to
  timeout - I've manually executed in my Hirsute VM and it succeeded in
  ~100 seconds.

  Maybe we need to just bump the timeout.

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


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

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

2021-10-27 Thread Jamie Nguyen

Public bug reported:

The nvidia-driver-XXX-server meta-package "Recommends" nvidia-settings.
I think it would be better to demote nvidia-settings to a "Suggests" for
these packages because of all the following:

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

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

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

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

** Project changed: kernel-sru-workflow => nvidia-graphics-
drivers-470-server (Ubuntu)

** Package changed: nvidia-graphics-drivers-470-server (Ubuntu) =>
nvidia-graphics-drivers-450-server (Ubuntu)

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

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

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

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

Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New

Bug description:
  The nvidia-driver-XXX-server meta-package "Recommends" nvidia-
  settings.  I think it would be better to demote nvidia-settings to a
  "Suggests" for these packages because of all the following:

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

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


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

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

You have been subscribed to a public bug:

The nvidia-driver-XXX-server meta-package "Recommends" nvidia-settings.
I think it would be better to demote nvidia-settings to a "Suggests" for
these packages because of all the following:

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

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

-- 
nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"
https://bugs.launchpad.net/bugs/1948960
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to nvidia-graphics-drivers-470-server 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 1948958] Re: No Wi-fi device found

2021-10-27 Thread Rishi Sharda

To confirm running kernel 5.11.0.27

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

Title:
  No Wi-fi device found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  P14s Gen 2 running 20.04.3 doesn't find Wi-Fi and only ethernet works.
  Tested fine on 21.4 and 21.10 however devices need to be on LTS.

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


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

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

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 1948958

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

Title:
  No Wi-fi device found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  P14s Gen 2 running 20.04.3 doesn't find Wi-Fi and only ethernet works.
  Tested fine on 21.4 and 21.10 however devices need to be on LTS.

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


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

[Kernel-packages] [Bug 1948958] [NEW] No Wi-fi device found

2021-10-27 Thread Rishi Sharda

Public bug reported:

P14s Gen 2 running 20.04.3 doesn't find Wi-Fi and only ethernet works.
Tested fine on 21.4 and 21.10 however devices need to be on LTS.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1948958

Title:
  No Wi-fi device found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  P14s Gen 2 running 20.04.3 doesn't find Wi-Fi and only ethernet works.
  Tested fine on 21.4 and 21.10 however devices need to be on LTS.

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


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

[Kernel-packages] [Bug 1933609] Re: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in

2021-10-27 Thread Tony Beaumont

I am seeing a similar issue with a second monitor plugged in.  I am
using nouveau and it crashes the X server and logs me out.  I have
attached a log of what happened.  This is NOT connected with a screen
lock, it happens randomly.

Display is:
  *-display 
   description: VGA compatible controller
   product: GK107GLM [Quadro K1100M]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
   configuration: driver=nouveau latency=0
   resources: irq:37 memory:d100-d1ff memory:7000-7fff 
memory:8000-81ff ioport:5000(size=128) memory:c-d


** Attachment added: "The text file shows the nouveau error and the X server 
crashing."
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933609/+attachment/5536495/+files/CrashLog.txt

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

Title:
  Locking screen crashes X/Wayland with nouveau when multiple monitors
  are plugged in

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

Bug description:
  Trying to run Ubuntu 20.04 on some Dell workstations with Nvidia
  Quadro P2200 cards. Getting some odd crashes. If a single monitor is
  plugged and the workstation is power on you can then log in and plug a
  second monitor in and locking the screen DOES not crash
  X/Wayland/nouveau. If you boot the system with both monitors plugged
  in then logging in and locking the computer will cause
  X/Wayland/Nouveau to crash and only a reboot will fix it. You can
  still ssh into the box though. The monitors are connected via
  DisplayPort.

  There were no kernel backtraces in the journal when running this bug
  report. But in other cases there has been nouveau backtraces.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun 25 16:02:35 2021
  InstallationDate: Installed on 2021-06-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  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.8/+bug/1933609/+subscriptions


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

[Kernel-packages] [Bug 1933609] Re: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in

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

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Locking screen crashes X/Wayland with nouveau when multiple monitors
  are plugged in

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

Bug description:
  Trying to run Ubuntu 20.04 on some Dell workstations with Nvidia
  Quadro P2200 cards. Getting some odd crashes. If a single monitor is
  plugged and the workstation is power on you can then log in and plug a
  second monitor in and locking the screen DOES not crash
  X/Wayland/nouveau. If you boot the system with both monitors plugged
  in then logging in and locking the computer will cause
  X/Wayland/Nouveau to crash and only a reboot will fix it. You can
  still ssh into the box though. The monitors are connected via
  DisplayPort.

  There were no kernel backtraces in the journal when running this bug
  report. But in other cases there has been nouveau backtraces.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun 25 16:02:35 2021
  InstallationDate: Installed on 2021-06-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.8
  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.8/+bug/1933609/+subscriptions


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

[Kernel-packages] [Bug 1661987] Re: Wrong colours on some monitors via USB-C to HDMI

2021-10-27 Thread Andrey Shpak

This still exist. Maybe we can help somehow to resolve it?

Linux insspb-kubuntu 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24
14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

root@insspb-kubuntu:/home/insspb# xrandr


  
Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767
HDMI-0 disconnected (normal left inverted right x axis y axis)
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 194mm
   1920x1080 60.02*+  60.0159.9759.9659.9348.03  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  59.9959.9459.9559.82  
   1280x1024 60.02  
   1440x900  59.89  
   1400x900  59.9659.88  
   1280x960  60.00  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1360x768  59.8059.96  
   1280x800  59.9959.9759.8159.91  
   1152x864  60.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
DP-1-1 connected 3840x2160+1920+0 (normal left inverted right x axis y axis) 
597mm x 336mm
   3840x2160 60.00*+  60.0050.0059.9430.0025.0024.00
29.9723.9829.98  
   1920x2160 59.99  
   2560x1440 59.95  
   1920x1080 60.0050.0059.94  
   1680x1050 59.88  
   1280x1024 75.0260.02  
   1440x900  59.90  
   1280x960  60.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   720x576   50.00  
   720x480   60.0059.94  
   640x480   75.0072.8166.6760.0059.94  
   720x400   70.08  
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
DP-1-3 disconnected (normal left inverted right x axis y axis)
HDMI-1-3 disconnected (normal left inverted right x axis y axis)

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

Title:
  Wrong colours on some monitors via USB-C to HDMI

Status in Linux:
  New
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 16.04.1 on my Dell XPS 13 9360 and I'm experiencing
  some issues with external displays.

  I bought two adapters from Aukey: USB-C to VGA and USB-C to HDMI
  (USB-C is the only port that I can use for video output on my
  computer).

  USB-C to VGA work flawlessly with all display I tested.

  USB-C to HDMI has issues with some displays. Sound works great but
  with some displays (such as on 2 24" Samsung TV monitors) colors are
  rendered wrong, like if a 16-bit palette is used (this picture posted
  by another user gives an idea of the problem:
  https://i.stack.imgur.com/KY44f.jpg).

  If I connect the display BEFORE turning it on and then turn it on it works 
correctly (until any video setting option is changed... then I get weird 
colours again).
  When I get weird colours if I turn the monitor off and on I get correct 
colours (until a change in video mode options).

  However on some other displays it works correctly all the time, such
  as on a 40" Toshiba TV.

  Other users are reporting the same issues with other usb-c to hdmi
  adapters / monitors combinations.

  The same adapter/monitor combination works flawlessly with Windows 10,
  and previously I used the same monitor with Ubuntu on my old computer
  (that had HDMI output) with no problems.

  I tested some other distros with the same result, so I think it is a

[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-10-27 Thread Alex Deucher

The reverts are in the latest firmware tree:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d7b50e61669dc137924337d03d09b8986eb752a3
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d843e520a4b0d92b986645548d11ade3b9b239a4
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=99d72504bff7ab40c261b8509c0b9d8abf98b296

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

2021-10-27 Thread Rudolf Harney

Same issue with Lenovo ThinkPad E15 Gen 2, AMD Ryzen 7 4700u with radeon 
graphics × 8 (AMD Renoir graphic).
stable workaround: start BIOS, exit with SAVE=YES (don't need to change 
anything).
A (better) solution would be highly appreciated. Thank you!

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1937072] Re: [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

2021-10-27 Thread kyuhyong

I had exact same issue on ubuntu 20.04 with same system "lenovo yoga slim7 
14IIL05"
Putting "i915.enable_psr=0" to GRUB_CMDLINE_LINUX_DEFAULT fixed issues such as 
rendering, screen tearing, delaying.

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

Title:
  [Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws

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

Bug description:
  In every 6/10 boot my ubuntu failed to start stuck on blank screen.
  Sometime touchpad stop working and unable to change my brightness
  after installation at first all feature are perfectly fine except
  screen glitch.Screen performance is laggy.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 21 17:13:28 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34]
 Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34]
  InstallationDate: Installed on 2021-07-21 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82A1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DHCN31WW
  dmi.board.asset.tag: ���
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55722 WIN
  dmi.chassis.asset.tag: ���
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Slim 7 14IIL05
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05:
  dmi.product.family: Yoga Slim 7 14IIL05
  dmi.product.name: 82A1
  dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05
  dmi.product.version: Yoga Slim 7 14IIL05
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021

2021-10-27 Thread Alberto Milone

** Description changed:

  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, 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]
+ 
+ == 470 ==
+   * New upstream release (LP: #1948025):
+ - Fixed a bug that can cause a kernel crash in SLI Mosaic
+   configurations.
+ - Added support for the EGL_NV_robustness_video_memory_purge.
+ 
+ == 495 ==
+   * Initial release (LP: #1948025).

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

Title:
  Update the NVIDIA drivers October 2021

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, 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]

  == 470 ==
* New upstream release (LP: #1948025):
  - Fixed a bug that can cause a kernel crash in SLI Mosaic
configurations.
  - Added support for the EGL_NV_robustness_video_memory_purge.

  == 495 ==
* Initial release (LP: #1948025).

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


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

[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs

** Description changed:

  [Impact]
  When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM 
emulation failure. This will cause the VM to go into the "paused" state, and 
prevents it from being restored without a full VM restart.
  
  This happens only when there are multiple enabled CPUs in the crash
  kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is
  being used. Due to the vCPU MMU state not being cleaned up correctly,
  the secondary CPUs try to access virtual addresses with a faulty MMU
  context that will result in the emulation failure. This shows up with a
  similar spew as below:
  
  $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log
  KVM internal error. Suberror: 1
  emulation failure
  EAX=de8f EBX= ECX=008f EDX=0600
  ESI= EDI= EBP= ESP=f90c
  EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000 000f  9b00
  SS =de00 000de000  9300
  DS =de00 000de000  9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3=290b8001 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70  71 66 
0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a
  
  [Test Plan]
  1. Boot an Ubuntu guest VM with e.g. multipass:
  $ multipass launch daily:focal -c8 -m16g -n focal-vm
  
  2. Configure guest crash kernel command-line with `nr_cpus=8`:
  ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line
  KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service 
nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0"
  
  3. Crash guest VM and watch for the KVM emulation failure:
  ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger
  
  [Where problems could occur]
  As we're resetting MMU context on vCPUs, potential regressions would show up 
in workloads relying on KVM guests. We should properly test the scenario 
mentioned in the bug to make sure secondary CPUs are being cleaned up properly, 
and that no other regressions have been introduced when rebooting or kexec'ing 
into different kernels.
  Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression 
potential should be fairly low and contained to starting/resetting vCPUs (i.e. 
VM start and reboot).
  
  [Other info]
  This has been fixed by upstream commit:
-   0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT
+   0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT
  
- And the two follow up commits, which revert the vendor-specific resets:
-   5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
-   61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()
+ The commit above has been picked up by stable trees up until 5.11, so it's 
only needed in Bionic and Focal (4.15 and 5.4 kernels). There are also two 
follow up commits, which revert the vendor-specific resets:
+   5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
+   61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()
  
- These commits have been introduced during the upstream 5.14 and 5.15 release 
candidates. They have been picked up by upstream stable up until 5.11, so 
backports are only needed for Bionic and Focal (4.15 and 5.4 kernels).
- $ git describe --contains 0aa1837533e5 5d2d7e41e3b8 61152cd907d5
- v5.14-rc1~166^2~58
- v5.15-rc1~65^2~119
- v5.15-rc1~65^2~120
+ These follow ups have not been picked up in stable trees due to the risk of
+ regressions. According to the original fix, they have been introduced 
primarily to aid bisection in case there are workflows relying on the vendor 
resets. As these are not required for the fix and don't conflict with the 
backport, we should leave them out to prevent potential regressions in the 
older kernels.

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

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Heitor Alves de Siqueira (halves)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed

[Kernel-packages] [Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

2021-10-27 Thread Ioanna Alifieraki

VERIFICATION FOCAL

Installed makedumpfile from proposed.
Testing on a Focal machine running 5.11 kernel.

# uname -rv
5.11.0-40-generic #44~20.04.1-Ubuntu SMP Wed Oct 20 19:04:34 UTC 2021

Trigger crash:
# echo 1 > /proc/sys/kernel/sysrq 
# echo c > /proc/sysrq-trigger

After reboot contents of /var/crash :
/var/crash/202110271414# ls
dmesg.202110271414  dump.202110271414

dmesg file has been successfully created.

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

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

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Committed
Status in makedumpfile source package in Hirsute:
  Fix Released
Status in makedumpfile package in Debian:
  Fix Released

Bug description:
  [IMPACT]
  makedumpfile does not create the dmesg. in /var/crash.
  This happens only on 5.10+ kernel because 5.10 kernel introduces a new
  lockless ringbuffer.

  This issue has been addressed upstream with commits :
  [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  After reboot make sure that dmesg. file is created in 
/var/crash/

  [WHERE PROBLEMS COULD OCCUR]

  Any problems would involve the dmesg file not created.

  [Other]

  [1] 
https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd
  [2] 
https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184

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


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

[Kernel-packages] [Bug 1942784] Re: makedumpfile falls back to cp on focal with 5.11 kernel

2021-10-27 Thread Ioanna Alifieraki

VERIFICATION ON FOCAL

Installed makedumpfile from proposed.
Testing on a Focal machine running 5.11 kernel.

# uname -rv
5.11.0-40-generic #44~20.04.1-Ubuntu SMP Wed Oct 20 19:04:34 UTC 2021

Trigger crash:
# echo 1 > /proc/sys/kernel/sysrq 
# echo c > /proc/sysrq-trigger

>From console output :

[   57.418037] kdump-tools[548]: Starting kdump-tools:
[   57.419099] kdump-tools[554]:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/202110271414/dump-incomplete
Copying data  : [100.0 %] /   eta: 
0s
[   61.481957] kdump-tools[572]: The kernel version is not supported.
[   61.494134] kdump-tools[572]: The makedumpfile operation may be incomplete.
[   61.501242] kdump-tools[572]: The dumpfile is saved to 
/var/crash/202110271414/dump-incomplete.
[   61.502711] kdump-tools[572]: makedumpfile Completed.
[   61.503885] kdump-tools[554]:  * kdump-tools: saved vmcore in 
/var/crash/202110271414
[   61.851266] kdump-tools[554]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202110271414/dmesg.202110271414
[   61.867626] kdump-tools[576]: The kernel version is not supported.
[   61.871305] kdump-tools[576]: The makedumpfile operation may be incomplete.
[   61.877902] kdump-tools[576]: The dmesg log is saved to 
/var/crash/202110271414/dmesg.202110271414.
[   61.881797] kdump-tools[576]: makedumpfile Completed.
[   61.885645] kdump-tools[554]:  * kdump-tools: saved dmesg content in 
/var/crash/202110271414
[   61.989595] kdump-tools[579]: Wed, 27 Oct 2021 14:14:21 +
[   62.123243] kdump-tools[580]: Rebooting.
[   62.561341] reboot: Restarting system

Makedumpfile compress the dump and does not fall back to cp.

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

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

Title:
  makedumpfile falls back to cp on focal with 5.11 kernel

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Focal:
  Fix Committed

Bug description:
  [IMPACT]

  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.

  [FIX]

  This can be resolved with upstream commit f1197543d1c4 ([PATCH] Retrieve 
MAX_PHYSMEM_BITS from vmcoreinfo).
  The reason for falling back to cp is that without this patch makedumpfile 
calculates wrongly the memory layout.

  This happens after the kernel commit 1d50e5d0c505 ("crash_core, vmcoreinfo: 
Append 'MAX_PHYSMEM_BITS'to vmcoreinfo").
  With this commit applied, reading MAX_PHYSMEM_BITS from vmcoreinfo instead of 
inferring lead to correctly detecting the memory layout and creating the dump 
file properly.

  [TEST CASE]

  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  On the console we can see that makedumpfile fails and `falls back to cp`.
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.

  [WHERE PROBLEMS COULD OCCUR]

  Any regression potential would involve the crash dump not being
  created after a crash in case kdump is configured.

  [OTHER]

  Only Focal with 5.11 kernel is affected.

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


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

[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs

** Description changed:

  [Impact]
  When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM 
emulation failure. This will cause the VM to go into the "paused" state, and 
prevents it from being restored without a full VM restart.
  
  This happens only when there are multiple enabled CPUs in the crash
  kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is
  being used. Due to the vCPU MMU state not being cleaned up correctly,
  the secondary CPUs try to access virtual addresses with a faulty MMU
  context that will result in the emulation failure. This shows up with a
  similar spew as below:
  
  $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log
  KVM internal error. Suberror: 1
  emulation failure
  EAX=de8f EBX= ECX=008f EDX=0600
  ESI= EDI= EBP= ESP=f90c
  EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000 000f  9b00
  SS =de00 000de000  9300
  DS =de00 000de000  9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3=290b8001 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70  71 66 
0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a
  
  [Test Plan]
  1. Boot an Ubuntu guest VM with e.g. multipass:
  $ multipass launch daily:focal -c8 -m16g -n focal-vm
  
  2. Configure guest crash kernel command-line with `nr_cpus=8`:
  ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line
  KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service 
nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0"
  
  3. Crash guest VM and watch for the KVM emulation failure:
  ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger
  
  [Where problems could occur]
  As we're resetting MMU context on vCPUs, potential regressions would show up 
in workloads relying on KVM guests. We should properly test the scenario 
mentioned in the bug to make sure secondary CPUs are being cleaned up properly, 
and that no other regressions have been introduced when rebooting or kexec'ing 
into different kernels.
  Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression 
potential should be fairly low and contained to starting/resetting vCPUs (i.e. 
VM start and reboot).
  
  [Other info]
  This has been fixed by upstream commit:
    0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT
  
  And the two follow up commits, which revert the vendor-specific resets:
    5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
    61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()
  
- These commits have been introduced during the upstream 5.14 and 5.15 release 
candidates, and as such should be backported to previous supported kernels.
+ These commits have been introduced during the upstream 5.14 and 5.15 release 
candidates. They have been picked up by upstream stable up until 5.11, so 
backports are only needed for Bionic and Focal (4.15 and 5.4 kernels).
  $ git describe --contains 0aa1837533e5 5d2d7e41e3b8 61152cd907d5
  v5.14-rc1~166^2~58
  v5.15-rc1~65^2~119
  v5.15-rc1~65^2~120

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

Title:
  KVM emulation failure when booting into  VM crash kernel with multiple
  CPUs

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM 
emulation failure. This will cause the VM to go into the "paused" state, and 
prevents it from being restored without a full VM restart.

  This happens only when there are multiple enabled CPUs in the crash
  kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is
  being used. Due to the vCPU MMU state not being cleaned up correctly,
  the secondary CPUs try to access virtual addresses with a faulty MMU
  context that will result in the emulation failure. This shows up with
  a similar spew as below:

  $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log
  KVM internal error. Suberror: 1
  emulation failure
  EAX=de8f EBX= ECX=008f EDX=0600
  ESI= EDI= EBP= ESP=f90c
  EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000 000f  9b00
  SS =de00 000de000  9300
  DS =de00 000de000

[Kernel-packages] [Bug 1928890] Re: vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

** Tags added: sru-20211018

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

Title:
  vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT
  test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too
  big)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Hirsute:
  New
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  
  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  
  00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh
  00:09:30 DEBUG| [stdout] # 
  00:09:30 DEBUG| [stdout] # 
###
  00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup 
ping
  00:09:30 DEBUG| [stdout] # 
###
  00:09:30 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded  
 [ OK ]
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup 
traceroute
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error 
route lookup ping
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # 
  00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed   
 [ OK ]
  00:09:34 DEBUG| [stdout] # 
  00:09:34 DEBUG| [stdout] # 
###
  00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup 
ping
  00:09:34 DEBUG| [stdout] # 
###
  00:09:34 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded  
 [ OK ]
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup 
traceroute
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP ttl error route lookup 
ping
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # 
  00:09:40 DEBUG| [stdout] # TEST: Basic IPv6 connectivity  
 [FAIL]
  00:09:40 DEBUG| [stdout] # TEST: Ping received ICMP Hop limit 
 [ OK ]
  00:09:40 DEBUG| [stdout] # 
  00:09:40 DEBUG| [stdout] # 
###
  00:09:40 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP error route lookup 
traceroute
  00:09:40 DEBUG| [stdout] # 
###

[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

** Tags added: aws sru-20211018

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

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with H (Check VM connectivity through VXLAN (underlay in the default
  VRF) [FAIL])

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

Bug description:
  Issue found with GCP 5.3.0-1017.18~18.04.1

   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1

  
  The failure is different from bug 1837348

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


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

[Kernel-packages] [Bug 1948025] Re: Update the NVIDIA drivers October 2021

2021-10-27 Thread Alberto Milone

** Information type changed from Private to Public

** Description changed:

- Update the NVIDIA drivers October 2021
+ Update the NVIDIA series in Bionic, Focal, Hirsute.
+ 
+ [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]

** Description changed:

- Update the NVIDIA series in Bionic, Focal, Hirsute.
+ Update the NVIDIA series and introduce the new 495 series in Bionic,
+ Focal, Hirsute, 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]

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

Title:
  Update the NVIDIA drivers October 2021

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  In Progress

Bug description:
  Update the NVIDIA series and introduce the new 495 series in Bionic,
  Focal, Hirsute, 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]

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


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

[Kernel-packages] [Bug 1948862] Re: KVM emulation failure when booting into VM crash kernel with multiple CPUs

** Description changed:

  [Impact]
- When kexec'ing into a crash kernel with `ncpus` > 1, VMs can raise a KVM
- emulation failure. This will cause the VM to go into the "paused" state, and
- prevents it from being restored without a full VM restart.
+ When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM 
emulation failure. This will cause the VM to go into the "paused" state, and 
prevents it from being restored without a full VM restart.
  
- This happens only when there are multiple enabled CPUs in the crash kernel
- command-line, regardless of whether `nr_cpus` or `maxcpus` is being used. Due 
to
- the vCPU MMU state not being cleaned up correctly, the secondary CPUs try to
- access virtual addresses with a faulty MMU context that will result in the
- emulation failure. This shows up with a similar spew as below:
+ This happens only when there are multiple enabled CPUs in the crash
+ kernel command-line, regardless of whether `nr_cpus` or `maxcpus` is
+ being used. Due to the vCPU MMU state not being cleaned up correctly,
+ the secondary CPUs try to access virtual addresses with a faulty MMU
+ context that will result in the emulation failure. This shows up with a
+ similar spew as below:
  
  $ sudo tail -n20 /var/log/libvirt/qemu/focal-vm.log
  KVM internal error. Suberror: 1
  emulation failure
  EAX=de8f EBX= ECX=008f EDX=0600
  ESI= EDI= EBP= ESP=f90c
  EIP=cdb1 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =   9300
  CS =f000 000f  9b00
  SS =de00 000de000  9300
  DS =de00 000de000  9300
  FS =   9300
  GS =   9300
  LDT=   8200
  TR =   8b00
  GDT=  
  IDT=  
  CR0=6010 CR2= CR3=290b8001 CR4=
  DR0= DR1= DR2= 
DR3=
  DR6=0ff0 DR7=0400
  EFER=
  Code=66 83 c4 28 66 5b 66 c3 66 56 66 53 66 52 b1 8f 88 c8 e6 70  71 66 
0f b6 f0 66 89 f2 67 88 54 24 03 88 c8 e6 70 66 31 db 88 d8 e6 71 66 56 66 68 1a
  
  [Test Plan]
  1. Boot an Ubuntu guest VM with e.g. multipass:
  $ multipass launch daily:focal -c8 -m16g -n focal-vm
  
  2. Configure guest crash kernel command-line with `nr_cpus=8`:
  ubuntu@focal-vm:~$ grep CMDLINE_APPEND /etc/default/kdump-tools
  # KDUMP_CMDLINE_APPEND - Additional arguments to append to the command line
  KDUMP_CMDLINE_APPEND="reset_devices systemd.unit=kdump-tools-dump.service 
nr_cpus=8 irqpoll nousb ata_piix.prefer_ms_hyperv=0"
  
  3. Crash guest VM and watch for the KVM emulation failure:
  ubuntu@focal-vm:~$ echo c | sudo tee /proc/sysrq-trigger
  
  [Where problems could occur]
- As we're resetting MMU context on vCPUs, potential regressions would show up 
in
- workloads relying on KVM guests. We should properly test the scenario 
mentioned
- in the bug to make sure secondary CPUs are being cleaned up properly, and that
- no other regressions have been introduced when rebooting or kexec'ing into
- different kernels.
- Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression
- potential should be fairly low and contained to starting/resetting vCPUs
- (i.e. VM start and reboot).
+ As we're resetting MMU context on vCPUs, potential regressions would show up 
in workloads relying on KVM guests. We should properly test the scenario 
mentioned in the bug to make sure secondary CPUs are being cleaned up properly, 
and that no other regressions have been introduced when rebooting or kexec'ing 
into different kernels.
+ Since we're adding an MMU reset at kvm_vcpu_reset(), the overall regression 
potential should be fairly low and contained to starting/resetting vCPUs (i.e. 
VM start and reboot).
  
  [Other info]
  This has been fixed by upstream commit:
-   0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT
+   0aa1837533e5 KVM: x86: Properly reset MMU context at vCPU RESET/INIT
  
  And the two follow up commits, which revert the vendor-specific resets:
-   5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
-   61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()
+   5d2d7e41e3b8 KVM: SVM: Drop explicit MMU reset at RESET/INIT
+   61152cd907d5 KVM: VMX: Remove explicit MMU reset in enter_rmode()
  
- These commits have been introduced during the upstream 5.14 and 5.15 release
- candidates, and as such should be backported to previous supported kernels.
+ These commits have been introduced during the upstream 5.14 and 5.15 release 
candidates, and as such should be backported to previous supported kernels.
  $ git describe --contains 0aa1837533e5 5d2d7e41e3b8 61152cd907d5
  v5.14-rc1~166^2~58
  v5.15-rc1~65^2~119
  v5.15-rc1~65^2~120

-- 
You received this bug notification because you are a member of Kernel
Packages,

[Kernel-packages] [Bug 1942972] Re: Update fix for LP: #1936708

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

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

Title:
  Update fix for LP: #1936708

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:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  There's a new fix for LP: #1936708, and it's more reliable than the
  old approach. So replace it.

  [Fix]
  Use eDP as predicate to enable max params.

  [Test]
  Users confirmed the fix can resolve their issue.

  [Where problems could occur]
  This patch reverts to the old behavior, which is to use max parameters,
  for older panels. If there's any new panel reports with older eDP
  version, this might change the behavior on it.

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


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

[Kernel-packages] [Bug 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Title:
  PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  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:
  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 Hirsute:
  Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Released
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not
  covered by previous LTR reset fix in bug 1896598.

  [Fix]

  Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is
  requierd:
  * ADL-M: [8086:464d]
  * ADL-P: [8086:51b0]
  * ADL-S: [8086:7ab4]

  [Test Case]

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  ...
  1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode])
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express])
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+

  [Where problems could occur]

  This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT
  values to a fixed 3145728ns that is used on Windows. Devices might want
  to set itself to a smaller value, but while this is not yet correctly
  supported by VMD controller driver, so the device power consumption
  might be little worse than ideal.

  [Other Info]

  VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions
  newer than 5.6 should have already the supporting function. This patch
  targets Alder Lake cpus that are supported since 5.10-oem and on.

  == original bug report ==

  * ADL-M:

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05)
  Kernel driver in use: pcieport
  1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device 
[8086:f1aa] (rev 03)
  Subsystem: Intel Corporation Device [8086:390f]
  Kernel driver in use: nvme
  Kernel modules: nvme

  * ADL-P:

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  * ADL-S:

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, 
https://bugs.launchpad.net/bugs/1896598.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1100 F pulseaudio
  CasperMD5CheckResult: skip
  Dependencies:

  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-04-06 (146 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0032 Intel Corp.
   Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.16+staging.11 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem 
root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1
  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.13.0-9010-oem N/A

[Kernel-packages] [Bug 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

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

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

Title:
  [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver

Status in intel:
  Fix Committed
Status in intel lookout-canyon series:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel source package in Focal:
  New
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Description
  Time Coordinated Compute (TCC)
  Pseudo SRAM interface support on top of Cache Allocation Technology

  Hardware: Tiger Lake & Elkhart Lake & Alder Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

  ---

  [Update, 2021-08-26]
  Please find the Getting Started Guide for Intel TCC Tools here, has steps to 
download, install and verify:

  https://software.intel.com/content/www/us/en/develop/documentation/get-
  started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html

  You can find the BIOS settings to enable TCC here:

  https://software.intel.com/content/www/us/en/develop/documentation/get-
  started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure-
  intel-tcc-tools-in-bios.html

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


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

[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic

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

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

Title:
  Wobbly graphics on built-in display since linux-
  image-5.11.0-22-generic

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

Bug description:
  == SRU Justification ==

  [Impact]
  Wobbly graphics after a kernel update. 

  [Fix]
  Older panels may require more bandwidth then advertised, so we need to
  use max params for them.

  [Test]
  Multiple users tested with positive result.

  [Where problems could occur]
  This patch reverts to the old behavior, which is to use max parameters,
  for older panels. If there's any new panel reports with older DP
  version, this might change the behavior on it.

  == Original Bug Report ==

  Lenovo laptop with Intel + Nvidia graphics.

  Since booting from  linux-image-5.11.0-22-generic, the built-in display is 
unusable, with wobbling horizontal stripes from the disk decryption prompt 
onwards:
  https://www.youtube.com/watch?v=LyRTuPzCe2I
  HDMI output works fine.

  If I boot from linux-image-5.11.0-18-generic instead, all is well.
  If I use Recovery mode with linux-image-5.11.0-22-generic and continue 
bootup, it's usable but there's no HDMI output.

  I think others may be having this issue too:
  
https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base#

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-22-generic 5.11.0-22.23
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   1598 F pulseaudio
   /dev/snd/controlC0:  alex   1598 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul 17 09:50:31 2021
  InstallationDate: Installed on 2021-01-03 (194 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 80DU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-22-generic N/A
   linux-backports-modules-5.11.0-22-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN31WW(V1.14)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80DU
  dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945494] Re: [EHL] Quadrature Encoder Peripheral support for sprint 2

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

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

Title:
  [EHL] Quadrature Encoder Peripheral support for sprint 2

Status in HWE Next:
  New
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Tracking bug, please don't triage.

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


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

[Kernel-packages] [Bug 1942043] Re: Noise will pop up during WB or stay in Ubuntu OS when external speaker attached

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Title:
  Noise will pop up during WB or stay in Ubuntu OS when external speaker
  attached

Status in HWE Next:
  Fix Released
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 Impish:
  Fix Released
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  HD-audio codec shutdown is not quite right when powering off the
  controller side. This causes pop noises on some platforms.

  [Fix]

  While previously in bug 1939541, a local fix for Cirrus CS8409 only is
  proposed the upstream as in
  
https://lore.kernel.org/lkml/20210812183433.6330-2-vita...@opensource.cirrus.com/
  . This initiated a discuss to create a generic solution as in
  https://lore.kernel.org/all/20210813081230.4268-1-ti...@suse.de/ .

  [Test Case]

  Shutdown Ubuntu that is running a patched kernel and see if a pop sound
  is still made.

  [Where problems could occur]

  While this tries to suspend the codec devices at shutting down, out of
  tree drivers without (runtime-)suspend support may fail to react
  correctly. And since this removes .reboot_notify callback from struct
  hda_codec_ops, it may break such oot drivers, too.

  [Other Info]

  This depends on patches for https://bugs.launchpad.net/bugs/1939541 .

  == original bug report ==

  [Reproduce Steps]
  1. Attach external speaker to SUT
  2. Try to reboot SUT or stay in OS.

  [Results]
   Expected Result
   No noise.
   Actual Result
   Noise will pop up during WB or stay in Ubuntu OS when external speaker 
attached.

  [Others]
  [Scenario 1] Login to the Ubuntu OS.
  (Occurs only in Cirrus, within 5 seconds after logging in to OS)
  Can 100% reproduce on Cirrus MB with Ubuntu. Noise can be heard (咚咚 Sounds) 
after login the Ubuntu within 5 secs.

  [Scenario 2] Reboot Ubuntu OS
  (Both Curris and Realtek happen. WB/CB/shutdown OS)
  Can 100% reproduce on Cirrus MB with Ubuntu. Noise can be heard While both 
exiting OS and entering OS.

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


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

[Kernel-packages] [Bug 1945461] Re: Integrated TSN controller for sprint 2

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

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

Title:
  Integrated TSN controller for sprint 2

Status in HWE Next:
  New
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Tracking bug, please don't triage.

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


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

[Kernel-packages] [Bug 1943935] Re: CirrusLogic/CS8409: No headset mic device when plugged earphone jack when HDMI/DP is used on Dolphin platform

** Changed in: hwe-next
   Status: New => Fix Released

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

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

Title:
  CirrusLogic/CS8409: No headset mic device when plugged earphone jack
  when HDMI/DP is used on Dolphin platform

Status in HWE Next:
  Fix Released
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 Impish:
  Fix Released
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When output device is set to HDMI/DP and headset plugged in, there is no
  Headset device available in sound settings.

  [Fix]

  Proposed fix in
  
https://patchwork.kernel.org/project/alsa-devel/patch/20210916095646.7631-1-vita...@opensource.cirrus.com/
  , already accepted as
  
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=94d508fa3186d0cbc63765aa94d5cf3bd847694c
  . This also depends on two commits which already in mainline kernel that
  refactor device init.

  [Test Case]

  1. Set output device to HDMI/DP
  2. Plug headset
  3. Check Sound settings for a new headset device

  [Where problems could occur]

  The last patch simply makes the onboard audio jack to use phantom jack.
  No much potential risk introduced. The two prerequisites simplifies
  init procedures and may need to receive some more stress tests
  especially those for suspend/resume, plug/unplug.

  [Other Info]

  This is for the new oem Dolphin platform that is only available in
  oem-5.13/oem-5.14 and impish. See bug 1939541.

  == original bug report ==

  [Steps to reproduce]
  1. Check output device is HDMI/DP audio and it works
  2. Plug headset
  3. Check Sound settings for Input & Output

  [Expected result]
  Sound settings should have headset when plugging

  [Actual result]
  Sound settings has no headset

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


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

[Kernel-packages] [Bug 1945464] Re: MEI (Intel Management Engine Interface) for sprint 2

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

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

Title:
  MEI (Intel Management Engine Interface) for sprint 2

Status in HWE Next:
  New
Status in linux-intel-5.13 package in Ubuntu:
  Invalid
Status in linux-intel-5.13 source package in Focal:
  Fix Committed

Bug description:
  Tracking bug, please don't triage.

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


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

[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Need support of Qualcomm WCN6856

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  New
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-firmware source package in Focal:
  Incomplete
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Hirsute:
  New
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Incomplete
Status in linux-firmware source package in Impish:
  New
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Qualcomm WCN685x is not supported yet.

  [Fix]

  Qualcomm WCN685x support are mostly available in linux-next and mainline
  with one patch currently in kvalo/ath tree, and 3 additional in review.

  [Test Case]

  Test hardware connectivity, stability with basic checkbox tests:

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

  [Where problems could occur]

  While this introduces a new hardware, it might need further
  polishments.

  [Other Info]

  WCN685x WiFi 6E capability is still under development and is moved to
  next milestone for oem projects. Firmware blobs for both WiFi and
  Bluetooth are also needed and will be SRUed when a formal release is
  made.

  == original bug report ==

  Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01
  BT driver support: USB\VID_0489_E0C9_0001

  Wireless Driver support: PCI\VEN_17CB_1103_01
  BT driver support: USB\VID_0489_E0CC_0001

  
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
  Already landed to mainline kernel v5.14-rc1.

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


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

[Kernel-packages] [Bug 1941893] Re: Improve performance and idle power consumption

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Improve performance and idle power consumption

Status in amd:
  New
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

This can improve AMD performance for all Zen or newer CPU which support C3 
shares cache.

  [Fix]

Its not necessary to flush the caches in software before entering
  C3.

Empirical measurements show:
 40-45% improvement in speedometer score.
 ~15% improvement in idle power.

The patch is in linux-next (tag next-20211007) and can be found @
  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  
next.git/commit/arch/x86/kernel/acpi/cstate.c?id=a8fb40966f19ff81520d9ccf8f7e2b95201368b8

  [Test]

This is requested by AMD.

  [Where problems could occur]

Low risk. This only works on AMD Zen CPUs that supports this
  features. AMD tested it and provided estimated measurement results.

   Original descriptions 

  A patch queued for 5.15 to change the C3 entry will improve AMD performance.
  https://lore.kernel.org/patchwork/patch/1478776/

  Empirical measurements show:
   40-45% improvement in speedometer score.
   ~15% improvement in idle power.

  Can you please include in 5.13-oem and 5.14-oem kernels?

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


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

[Kernel-packages] [Bug 1945361] Re: [Yellow Carp] USB4 interdomain communication problems

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

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

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

** Tags added: verification-needed-focal

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

Title:
[Yellow Carp] USB4 interdomain communication problems

Status in amd:
New
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Fix Committed

Bug description:
[Impact]

Yellow carp w/ SW CM bi-directional interdomain communication may
have some problems that the response packets are lost sometimes within
the stipulated time.

[Fix]

Enable the retry by increasing retry count from 1 to 4.

The patch is in linux-next (tag next-20211007) and can be found @
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thunderbolt/ctl.c?id=641cdbea7635be3a177dbdf81356ccb16f3769e3

[Test]

This is requested and tested by AMD.

[Where problems could occur]

Low risk. This only affects small number of AMD systems that would
excess the time. Systems without problems won't be affected.

= Original Description

AMD internal team has found that for Yellow carp w/ SW CM bi-
directional interdomain communication may have some problems. It's
been aligned upstream to increase number of retries to account for
these issues.

https://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git/commit/?h=next=641cdbea7635be3a177dbdf81356ccb16f3769e3

Can Canonical team please include this in future 5.14-OEM?

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

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

[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing

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

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

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


** Tags added: verification-needed-focal

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

Title:
  rtw89 kernel module for Realtek 8852 wifi is missing

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

Bug description:
  == SRU Justification ==
  [Impact]
  Realtek 8852AE, which is used by many new laptops, doesn't have a
  driver.

  [Fix]
  Add rtw89 driver to support Realtek 8852AE.

  [Test]
  After applying the patch, 8852AE can scan, connect and do TX/RX.

  [Where problems could occur]
  This is a brand new driver, unless the driver hits some subtle PCI or
  IOMMU bugs, there isn't much chance to introduce any regression.

  == Original Bug Report ==
  Hi,

  Resulting: no wifi adapter detected.
  Currently WIP: 
https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=*

  Workaround: use https://github.com/lwfinger/rtw89
  that allows to build a dkms deb package.

  Ubuntu Impish
  kernel 5.13 (or 5.15 from unstable ppa)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fthx   4574 F pulseaudio
   /dev/snd/controlC2:  fthx   4574 F pulseaudio
   /dev/snd/controlC0:  fthx   4574 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-15 (20 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 21AVFR
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-4-generic N/A
   linux-backports-modules-5.15.0-4-generic  N/A
   linux-firmware1.201
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-4-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET39W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AVFR
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21AVFR
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Can only reach PC3 when ethernet is plugged r8169

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  System only can reach PC3, and it affects power consumption alot.

  [Fix]
  Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state 
issue, but also fixes network speed issue.
  
https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/

  [Test]
  Verified on 2 different systems which has PC state issue and has network 
speed issue, these patches fix both issues.

  [Where problems could occur]
  It toggles ASPM on and off depends on the network traffic during runtime, I 
don't think it'll lead to any regressions. Some potential issues have been 
addressed during the patch submitting. It's v6 now and accepted by upstream.

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


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

[Kernel-packages] [Bug 1947859] Re: linux-azure: Updata MANA to 5.15-rc6

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

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

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


** Tags added: verification-needed-impish

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

Title:
  linux-azure: Updata MANA to 5.15-rc6

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

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested the addition of MANA EQ-sharing patch set
  which is essentially everything up through v5.15-rc6.

  3 more patches from Haiyang regarding EQ-sharing for Microsoft Azure
  Network Adapter (MANA). This saves MSI-X interrupts and allows the
  host to offer more virtual ports (network interfaces) to the VM. With
  the patches, the MANA driver supports up to 256 virtual ports per VF
  (it was 16/VF), and support up to 64 queues per vPort (it was 16).

  [Test Case]

  Microsoft to test and verify.

  [Where things might go wrong]

  More virtual ports may cause issues in older kernels.

  [Other Info]

  SF: #00321275

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


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

[Kernel-packages] [Bug 1942319] Re: When booting with UEFI, mokvar table and %:.platform keyring must be available

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

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

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


** Tags added: verification-needed-impish

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

Title:
  When booting with UEFI, mokvar table and %:.platform keyring must be
  available

Status in linux-kvm package in Ubuntu:
  Fix Committed
Status in linux-kvm source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * When booting with UEFI, mokvar table and %:.platform keyring must
  be available. These are required for builtin revocation certificates
  to be present, shim builtin certificates to be present and thus
  support to signed & verified kexec present. It also allows revocation
  of signed lrm and livepatch drivers which are trusted by this kernel.

   * The kvm annotations are very minimal, v3 format, and the parent
  kernel's annotations are not enforced.

  [Test Plan]

   * Check that /sys/firmware/efi/mok-variables/ is available

   * Check that %:.blacklist keyring is populated

 $ sudo keyctl list %:.blacklist

  
   * Check that %:.platform keyring is populated

 $ sudo keyctl list %:.platform

  [Where problems could occur]

   * Given how small the kvm config is, it is not clear if all of
  lockdown features are correctly enabled. Specifically measuring and
  appraising things with integrity framework. It is possible further
  config changes will be required to make kvm flavour as hardened as
  generic one.

  [Other Info]
   
   * This issue was discovered whilst working on 
https://bugs.launchpad.net/bugs/1928679 and 
https://bugs.launchpad.net/bugs/1932029

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


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

[Kernel-packages] [Bug 1937252] Re: e1000e: add handshake with the Intel CSME to support S0ix