date:20220211

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

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

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

Title:
  KVM ROP Control-Flow Enforcement Tech (CET)

Status in linux package in Ubuntu:
  Expired
Status in qemu package in Ubuntu:
  Expired

Bug description:
  Control-Flow Enforcement Tech (CET)

  What is Intel CET:
  Control-flow Enforcement Technology (CET) provides protection against
  return/jump-oriented programming (ROP) attacks. It can be implemented
  to protect both the kernel and applications. In the first phase,
  only the user-mode protection is implemented on the 64-bit kernel.
  However, 32-bit applications are supported under the compatibility
  mode.
  CET includes shadow stack (SHSTK) and indirect branch tracking (IBT).
  The SHSTK is a secondary stack allocated from memory. The processor
  automatically pushes/pops a secure copy to the SHSTK every return
  address and, by comparing the secure copy to the program stack copy,
  verifies function returns are as intended. The IBT verifies all
  indirect CALL/JMP targets are intended and marked by the compiler with
  'ENDBR' op codes.

  Why need this technology(CET VMX):
  CET also can provide ROP attack in guest OS with VMX HW support. This will 
enhance platform security in Cloud computing, it's meaningful for Cloud service 
providers.

  Key change in kvm:
  To enable KVM based CET feature for guest OS, we need to :
  1) Expose the features(CET SHSTK/IBT) to guest OS via CPUID report.
  2) Enable xsaves/xrstors support for guest OS.
  3) Fix xsaves/xrstors issue in existing KVM code.
  4) Enabled CET states loading in guest entry/exit.
  5) Add CET VMX related definitions.

  Key change in Qemu-kvm:
  expose CET related CPUID and xsaves/xrstors support to guest.

  Target Linux 5.18

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


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

[Kernel-packages] [Bug 1954463] Re: KVM ROP Control-Flow Enforcement Tech (CET)

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

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

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

Title:
  KVM ROP Control-Flow Enforcement Tech (CET)

Status in linux package in Ubuntu:
  Expired
Status in qemu package in Ubuntu:
  Expired

Bug description:
  Control-Flow Enforcement Tech (CET)

  What is Intel CET:
  Control-flow Enforcement Technology (CET) provides protection against
  return/jump-oriented programming (ROP) attacks. It can be implemented
  to protect both the kernel and applications. In the first phase,
  only the user-mode protection is implemented on the 64-bit kernel.
  However, 32-bit applications are supported under the compatibility
  mode.
  CET includes shadow stack (SHSTK) and indirect branch tracking (IBT).
  The SHSTK is a secondary stack allocated from memory. The processor
  automatically pushes/pops a secure copy to the SHSTK every return
  address and, by comparing the secure copy to the program stack copy,
  verifies function returns are as intended. The IBT verifies all
  indirect CALL/JMP targets are intended and marked by the compiler with
  'ENDBR' op codes.

  Why need this technology(CET VMX):
  CET also can provide ROP attack in guest OS with VMX HW support. This will 
enhance platform security in Cloud computing, it's meaningful for Cloud service 
providers.

  Key change in kvm:
  To enable KVM based CET feature for guest OS, we need to :
  1) Expose the features(CET SHSTK/IBT) to guest OS via CPUID report.
  2) Enable xsaves/xrstors support for guest OS.
  3) Fix xsaves/xrstors issue in existing KVM code.
  4) Enabled CET states loading in guest entry/exit.
  5) Add CET VMX related definitions.

  Key change in Qemu-kvm:
  expose CET related CPUID and xsaves/xrstors support to guest.

  Target Linux 5.18

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


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

[Kernel-packages] [Bug 1954464] Re: kvm SPR support for AMX

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

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

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

Title:
  kvm SPR support for AMX

Status in linux package in Ubuntu:
  Expired

Bug description:
  AMX (including XFD):  AMX (Advance Matrix eXtensions) is a new programming 
paradigm for direct matrix operations. TMUL (TILE Matrix mULtiply unit) is the 
multiply accelerator. XFD (Extended Feature Disable) is an XSAVE extension 
mechanism for those features with large XSAVE storage context, that enables the 
OS not pre-allocate the space initially. AMX is the first one using XFD feature.
  Use cases: Deep learning inference and training (CNN, DNN), other data 
analytics and machine learning apps, HPC SGEMM

  Target Linux 5.17

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


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

[Kernel-packages] [Bug 1954466] Re: KVM Protection Keys for Supervisor Pages (PKS)

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

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

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

Title:
  KVM Protection Keys for Supervisor Pages (PKS)

Status in linux package in Ubuntu:
  Expired

Bug description:
  SKX introduced the Protection Key for User Pages (PKU) feature
  enabling fast, thread-specific manipulation of permission restrictions
  on user pages. SPR introduced Protection Key for Supervisor
  Pages(PKS), a new feature that extends the Protection Key architecture
  to support thread-specific permission restrictions on supervisor
  pages. This important feature enables enhanced access control on
  memory, and brings more valid usage model.

  Generally PKS enables protections on 'domains' of supervisor pages to
  limit supervisor mode access to pages beyond the normal paging
  protections(U/S, R/W, P). PKS works in a similar fashion to user space
  pkeys, PKU. As with PKU, supervisor pkeys are checked in addition to
  normal paging protections and Access or Writes can be disabled via a
  MSR update without TLB flushes when permissions change.

  PKS virtualization enabling should base on existing PKU code. Major
  works:

  CPUID exposure

  New CR4 bit exposure

  New VMCS fields enabling

  IA32_PKRS saving/restoring

  #GP handling


  Target Linux 5.19

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


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

[Kernel-packages] [Bug 1954465] Re: KVM AIA User IPI

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

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

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

Title:
  KVM AIA User IPI

Status in linux package in Ubuntu:
  Expired

Bug description:
  SENDUIPI is a new ring-3 instruction that sending IPI notification
  between ring 3 software. It uses a data structure (table) owned and
  managed by ring 0 OS. Ring 3 software can choose which table entry to
  invoke.

  Target Linux 5.18

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


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

[Kernel-packages] [Bug 1954468] Re: KVM Architectural LBRs

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

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

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

Title:
  KVM Architectural LBRs

Status in linux package in Ubuntu:
  Expired

Bug description:
  Architectural LBRs (Last Branch Records)

  Architectural LBRs (Last Branch Records) enable recording of software
  path history by logging taken branches and other control flow
  transfers within model-specific registers, and is inherited from
  legacy LBR. If CPUID.(EAX=07H, ECX=0):EDX[19] is set to 1, the
  processor supports Architectural LBRs. With VMCS support and XSAVE
  support, the KVM guests could also use ARCH LBR as well.

  Target Linux 5.17

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


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

[Kernel-packages] [Bug 1954473] Re: KVM Shared Virtual Memory (SVM)

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

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

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

Title:
  KVM Shared Virtual Memory (SVM)

Status in linux package in Ubuntu:
  Expired

Bug description:
  SVM is short for shared virtual memory. This task is aiming at
  enabling SVM support for assigned devices on KVM. Example: assign a
  GPU from host to guest, the application program running in guest could
  share its virtual memory address to the assigned device.

  Latest update: extend the vIOMMU in QEMU to support SVM feature.

  1. Description of the Technology.
  SVM is shorted for Shared Virtual Memory, it is a VT-d feature that allows 
sharing application virtual address space with the I/O device. The feature 
works with the PCI sig Process Address Space ID (PASID). SVM has the following 
benefits:
  • Programmer gets a consistent view of memory across host application and 
device
  • Efficient access to data, avoiding pining or copying overheads
  2. Use cases that is important for this technology (aka, why is this 
technology needed).
  Intel has multiple IPs that would support SVM, and the usage in guest is also 
a demand. e.g. QAT, it is usual to assign a QAT to guest and requires SVM to 
benefit from its advantages.
  3. General design description (components modified: kvm, qemu-kvm, driver, 
libvirt (and other userland libraries))
  Modified components would include: qemu-kvm, vfio driver, iommu driver

  Target Linux 5.19

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


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

[Kernel-packages] [Bug 1954472] Re: KVM Scalable I/O Virtualization

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

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

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

Title:
  KVM Scalable I/O Virtualization

Status in linux package in Ubuntu:
  Expired

Bug description:
  Core OS/ VMM device virtualization framework extended to support
  Scalable IOV; OS/ VMM support for Scalable IOV IOMMU extensions; PASID
  translation support; existing device frameworks extended to support
  Scalable IOV; converged SW arch as prescribed by spec

  Improved performance and lower complexity for software utilizing PCIe
  devices in virtualized environments

  Software Benefits: Broad range of usages, e.g. security, comms, server
  graphics

  Target Linux 5.18

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


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

[Kernel-packages] [Bug 1954474] Re: KVM notify VM Exit

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

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

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

Title:
  KVM notify VM Exit

Status in linux package in Ubuntu:
  Expired

Bug description:
  A VMM can enable notification VM exits to occur if no interrupt
  windows occur in VMX non-root operation for a specified amount of time
  (notify window).


  KVM Enabling:

  enable bit 31 of secondary processor-based excution control.
  enable notification VM exit (exit reason 75) handler.
  expose a module param to configure notify window and disable/enable VM notify.

  Target Linux 5.17

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


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

[Kernel-packages] [Bug 1518457]

2022-02-11 Thread d

Reproduced on latest centos kernel 3.10.0-1160.53

It's so strange that this keeps on happening I tried disabling swap and
everything but it doesn't care. There's 100 GB free ram and yet it
happens

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

Title:
  kswapd0 100% CPU usage

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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


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

[Kernel-packages] [Bug 1845214] Re: Keyboard NumLock indicator turns off on connecting another keyboard

2022-02-11 Thread Stuart Longland

I've noticed the same thing… both on Ubuntu, and lately on Gentoo as
well, so I'm thinking maybe something in udev / kernel has changed?

I use FVWM2 as my desktop on both OSes.  My desktop runs Ubuntu 20.04
(AMD64).

On my laptop (Panasonic CF-53, which runs Gentoo) it's particularly
insidious, plugging in the YubiKey (mine's a 5C which I use with a USB-
A-C adaptor) causes NumLock to be turned on, and if your PIN code uses
letters over the right-side of the keyboard, guess what?  You're
unwittingly typing numbers now!  Cue confusion when the YubiKey rejects
the PIN you just entered.

I've locked myself out of the YubiKey once because of that -- had to go
in with the PUK and unlock it.

My desktop doesn't seem to secretly turn NumLock on; the state is
retained, just the LED turns off.

If we can figure out what mechanism is doing it in Ubuntu, I'll chase up
what's doing it Gentoo-side.

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

Title:
  Keyboard NumLock indicator turns off on connecting another keyboard

Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  My USB HID keyboard has NumLock LED. It usually works fine. However,
  when I plug in YubiKey (hardware security token, it is also identified
  as a USB HID keyboard) NumLock LED turns OFF, but the NumLock feature
  is still ON.

  If I press NumLock, NumLock becomes disabled (it is displayed by DE
  and checked by typing). If I press NumLock again, NumLock turns back
  ON with LED.

  I originally thought that issue could be related to the fact that
  YubiKey does not have a NumLock led, so it reports LED as nonexisting
  and stuff happens. However, today I tried attaching another USB
  keyboard: LED on first one still goes off; but LED on second goes ON
  immediately after plugging in. Pressing NumLock once disables NumLock
  and LED on first keyboard, as with YubiKey; pressing again enabled
  NumLock and both LEDs.

  Seems like my user session (on vt2) is running Xorg while login screen
  (on vt1, the one that allows to choose a user and that you see before
  first login) is running Wayland; both are faulty. Because of this, I
  believe the issue is in the kernel.

  However, I am not sure, so you can ask for way more reports to be
  added, I will add those. Reproducing should be pretty easy with any
  cheap USB keyboards, nothing special is used by me.

  Operating system: Ubuntu 18.04 Bionic Beaver.
  Linux kernel: 18.04 HWE, 5.0.0-25. However, I think I saw this blinking 
before upgrading to HWE.
  DE: GNOME.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04 5.0.0.29.86
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 16:52:08 2019
  SourcePackage: linux-meta-hwe
  UpgradeStatus: Upgraded to bionic on 2018-09-03 (386 days ago)

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


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

[Kernel-packages] [Bug 1845214] Re: Keyboard NumLock indicator turns off on connecting another keyboard

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

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

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

Title:
  Keyboard NumLock indicator turns off on connecting another keyboard

Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  My USB HID keyboard has NumLock LED. It usually works fine. However,
  when I plug in YubiKey (hardware security token, it is also identified
  as a USB HID keyboard) NumLock LED turns OFF, but the NumLock feature
  is still ON.

  If I press NumLock, NumLock becomes disabled (it is displayed by DE
  and checked by typing). If I press NumLock again, NumLock turns back
  ON with LED.

  I originally thought that issue could be related to the fact that
  YubiKey does not have a NumLock led, so it reports LED as nonexisting
  and stuff happens. However, today I tried attaching another USB
  keyboard: LED on first one still goes off; but LED on second goes ON
  immediately after plugging in. Pressing NumLock once disables NumLock
  and LED on first keyboard, as with YubiKey; pressing again enabled
  NumLock and both LEDs.

  Seems like my user session (on vt2) is running Xorg while login screen
  (on vt1, the one that allows to choose a user and that you see before
  first login) is running Wayland; both are faulty. Because of this, I
  believe the issue is in the kernel.

  However, I am not sure, so you can ask for way more reports to be
  added, I will add those. Reproducing should be pretty easy with any
  cheap USB keyboards, nothing special is used by me.

  Operating system: Ubuntu 18.04 Bionic Beaver.
  Linux kernel: 18.04 HWE, 5.0.0-25. However, I think I saw this blinking 
before upgrading to HWE.
  DE: GNOME.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic-hwe-18.04 5.0.0.29.86
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 16:52:08 2019
  SourcePackage: linux-meta-hwe
  UpgradeStatus: Upgraded to bionic on 2018-09-03 (386 days ago)

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


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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2022-02-11 Thread Alistair Sutter

Edit: I just noticed that my touchpad actually works on the login screen
and then stops working after I log in. Might actually be a different
bug.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1960403] Re: Kubuntu constantly freezing on ThinkPad T510

I meant that nothing shows up on the terminal.

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

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

Title:
  Kubuntu constantly freezing on ThinkPad T510

Status in kubuntu-meta package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This happens either during SDDM, or on the desktop, but Kubuntu's
  constantly freezing up.

  I tried disabling the compositor, but it doesn't seem to help.  Also,
  I removed the external monitor, but that doesn't seem to help.

  I've installed Lubuntu, and so far it's been fine. However, when I
  tried to change the SDDM theme via KDE's System Settings, the laptop
  locked up.

  I'll keep Kubuntu on it for now, but I'm gonna have to switch this to
  Lubuntu in the meantime.

  Specs:
  * Core i7-640M
  * 8GB RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: kubuntu-desktop 1.416
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 05:58:18 2022
  InstallationDate: Installed on 2021-08-07 (186 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago)

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


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

[Kernel-packages] [Bug 1960403] Re: Kubuntu constantly freezing on ThinkPad T510

Hope this helps for now.

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

Title:
  Kubuntu constantly freezing on ThinkPad T510

Status in kubuntu-meta package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This happens either during SDDM, or on the desktop, but Kubuntu's
  constantly freezing up.

  I tried disabling the compositor, but it doesn't seem to help.  Also,
  I removed the external monitor, but that doesn't seem to help.

  I've installed Lubuntu, and so far it's been fine. However, when I
  tried to change the SDDM theme via KDE's System Settings, the laptop
  locked up.

  I'll keep Kubuntu on it for now, but I'm gonna have to switch this to
  Lubuntu in the meantime.

  Specs:
  * Core i7-640M
  * 8GB RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: kubuntu-desktop 1.416
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 05:58:18 2022
  InstallationDate: Installed on 2021-08-07 (186 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago)

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


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

[Kernel-packages] [Bug 1960403] Re: Kubuntu constantly freezing on ThinkPad T510

the following packages were updated that fixed the issue: libegl-mesa0
libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0 libxatracker2 mesa-
va-drivers mesa-vdpau-drivers mesa-vulkan-drivers xserver-xorg-video-
amdgpu libllvm13

I'll try to run apport-collect some other time, but right now, it's
officially stuck.

$ journalctl -r --grep apport
Feb 11 16:52:09 METEOR-ThinkPad-T510 apport[892]:  * Starting automatic crash 
report generation: apport
Feb 11 16:52:09 METEOR-ThinkPad-T510 systemd[1]: Condition check resulted in 
Unix socket for apport crash forwarding being skipped.

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

Title:
  Kubuntu constantly freezing on ThinkPad T510

Status in kubuntu-meta package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This happens either during SDDM, or on the desktop, but Kubuntu's
  constantly freezing up.

  I tried disabling the compositor, but it doesn't seem to help.  Also,
  I removed the external monitor, but that doesn't seem to help.

  I've installed Lubuntu, and so far it's been fine. However, when I
  tried to change the SDDM theme via KDE's System Settings, the laptop
  locked up.

  I'll keep Kubuntu on it for now, but I'm gonna have to switch this to
  Lubuntu in the meantime.

  Specs:
  * Core i7-640M
  * 8GB RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: kubuntu-desktop 1.416
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 05:58:18 2022
  InstallationDate: Installed on 2021-08-07 (186 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago)

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


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

[Kernel-packages] [Bug 1960403] Re: Kubuntu constantly freezing on ThinkPad T510

Adding this PPA fixed this so far

https://launchpad.net/~ernstp/+archive/ubuntu/mesarc

Also, running apport-collect just makes it stuck.

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

Title:
  Kubuntu constantly freezing on ThinkPad T510

Status in kubuntu-meta package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This happens either during SDDM, or on the desktop, but Kubuntu's
  constantly freezing up.

  I tried disabling the compositor, but it doesn't seem to help.  Also,
  I removed the external monitor, but that doesn't seem to help.

  I've installed Lubuntu, and so far it's been fine. However, when I
  tried to change the SDDM theme via KDE's System Settings, the laptop
  locked up.

  I'll keep Kubuntu on it for now, but I'm gonna have to switch this to
  Lubuntu in the meantime.

  Specs:
  * Core i7-640M
  * 8GB RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: kubuntu-desktop 1.416
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 05:58:18 2022
  InstallationDate: Installed on 2021-08-07 (186 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago)

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


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

[Kernel-packages] [Bug 1960681] Re: Bionic update: upstream stable patchset 2022-02-11

2022-02-11 Thread Kamal Mostafa

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:
  
     upstream stable patchset 2022-02-11
+ 
+ Ported from the following upstream stable releases:
+ v4.14.263, v4.19.226
+ 
     from git://git.kernel.org/
  
  Bluetooth: bfusb: fix division by zero in send path
  USB: core: Fix bug in resuming hub's handling of wakeup requests
  USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
  mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
  can: gs_usb: fix use of uninitialized variable, detach device on reception of 
invalid USB data
  can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
  random: fix data race on crng_node_pool
  random: fix data race on crng init time
  staging: wlan-ng: Avoid bitwise vs logical OR warning in 
hfa384x_usb_throttlefn()
  drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
  orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
  media: uvcvideo: fix division by zero at stream start
  rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
  Bluetooth: schedule SCO timeouts with delayed_work
  Bluetooth: fix init and cleanup of sco_conn.timeout_work
  HID: uhid: Fix worker destroying device without any protection
  HID: wacom: Ignore the confidence flag when a touch is removed
  HID: wacom: Avoid using stale array indicies to read contact count
  nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind()
  rtc: cmos: take rtc_lock while reading from CMOS
  media: flexcop-usb: fix control-message timeouts
  media: mceusb: fix control-message timeouts
  media: em28xx: fix control-message timeouts
  media: cpia2: fix control-message timeouts
  media: s2255: fix control-message timeouts
  media: dib0700: fix undefined behavior in tuner shutdown
  media: redrat3: fix control-message timeouts
  media: pvrusb2: fix control-message timeouts
  media: stk1160: fix control-message timeouts
  can: softing_cs: softingcs_probe(): fix memleak on registration failure
  shmem: fix a race between shmem_unused_huge_shrink and shmem_evict_inode
  PCI: Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller
  Bluetooth: cmtp: fix possible panic when cmtp_init_sockets() fails
  clk: bcm-2835: Pick the closest clock rate
  clk: bcm-2835: Remove rounding up the dividers
  wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND
  media: em28xx: fix memory leak in em28xx_init_dev
  Bluetooth: stop proccessing malicious adv data
  media: dmxdev: fix UAF when dvb_register_device() fails
  crypto: qce - fix uaf on qce_ahash_register_one
  tty: serial: atmel: Check return code of dmaengine_submit()
  tty: serial: atmel: Call dma_async_issue_pending()
  media: mtk-vcodec: call v4l2_m2m_ctx_release first when file is released
  netfilter: bridge: add support for pppoe filtering
  arm64: dts: qcom: msm8916: fix MMC controller aliases
  drm/amdgpu: Fix a NULL pointer dereference in 
amdgpu_connector_lcd_native_mode()
  drm/radeon/radeon_kms: Fix a NULL pointer dereference in 
radeon_driver_open_kms()
  serial: amba-pl011: do not request memory region twice
  floppy: Fix hang in watchdog when disk is ejected
  media: dib8000: Fix a memleak in dib8000_init()
  media: saa7146: mxb: Fix a NULL pointer dereference in mxb_attach()
  media: si2157: Fix "warm" tuner state detection
  sched/rt: Try to restart rt period timer when rt runtime exceeded
  media: dw2102: Fix use after free
  media: msi001: fix possible null-ptr-deref in msi001_probe()
  usb: ftdi-elan: fix memory leak on device disconnect
  x86/mce/inject: Avoid out-of-bounds write when setting flags
  pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in 
__nonstatic_find_io_region()
  pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in 
nonstatic_find_mem_region()
  ppp: ensure minimum packet size in ppp_write()
  fsl/fman: Check for null pointer after calling devm_ioremap
  spi: spi-meson-spifc: Add missing pm_runtime_disable() in meson_spifc_probe
  tpm: add request_locality before write TPM_INT_ENABLE
  can: softing: softing_startstop(): fix set but not used variable warning
  can: xilinx_can: xcan_probe(): check for error irq
  pcmcia: fix setting of kthread task states
  net: mcs7830: handle usb read errors properly
  ext4: avoid trim error on fs with small groups
  ALSA: jack: Add missing rwsem around snd_ctl_remove() calls
  ALSA: PCM: Add missing rwsem around snd_ctl_remove() calls
  ALSA: hda:

[Kernel-packages] [Bug 1960681] [NEW] Bionic update: upstream stable patchset 2022-02-11

2022-02-11 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 2022-02-11

Ported from the following upstream stable releases:
v4.14.263, v4.19.226

   from git://git.kernel.org/

Bluetooth: bfusb: fix division by zero in send path
USB: core: Fix bug in resuming hub's handling of wakeup requests
USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
can: gs_usb: fix use of uninitialized variable, detach device on reception of 
invalid USB data
can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
random: fix data race on crng_node_pool
random: fix data race on crng init time
staging: wlan-ng: Avoid bitwise vs logical OR warning in 
hfa384x_usb_throttlefn()
drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
media: uvcvideo: fix division by zero at stream start
rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
Bluetooth: schedule SCO timeouts with delayed_work
Bluetooth: fix init and cleanup of sco_conn.timeout_work
HID: uhid: Fix worker destroying device without any protection
HID: wacom: Ignore the confidence flag when a touch is removed
HID: wacom: Avoid using stale array indicies to read contact count
nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind()
rtc: cmos: take rtc_lock while reading from CMOS
media: flexcop-usb: fix control-message timeouts
media: mceusb: fix control-message timeouts
media: em28xx: fix control-message timeouts
media: cpia2: fix control-message timeouts
media: s2255: fix control-message timeouts
media: dib0700: fix undefined behavior in tuner shutdown
media: redrat3: fix control-message timeouts
media: pvrusb2: fix control-message timeouts
media: stk1160: fix control-message timeouts
can: softing_cs: softingcs_probe(): fix memleak on registration failure
shmem: fix a race between shmem_unused_huge_shrink and shmem_evict_inode
PCI: Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller
Bluetooth: cmtp: fix possible panic when cmtp_init_sockets() fails
clk: bcm-2835: Pick the closest clock rate
clk: bcm-2835: Remove rounding up the dividers
wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND
media: em28xx: fix memory leak in em28xx_init_dev
Bluetooth: stop proccessing malicious adv data
media: dmxdev: fix UAF when dvb_register_device() fails
crypto: qce - fix uaf on qce_ahash_register_one
tty: serial: atmel: Check return code of dmaengine_submit()
tty: serial: atmel: Call dma_async_issue_pending()
media: mtk-vcodec: call v4l2_m2m_ctx_release first when file is released
netfilter: bridge: add support for pppoe filtering
arm64: dts: qcom: msm8916: fix MMC controller aliases
drm/amdgpu: Fix a NULL pointer dereference in amdgpu_connector_lcd_native_mode()
drm/radeon/radeon_kms: Fix a NULL pointer dereference in 
radeon_driver_open_kms()
serial: amba-pl011: do not request memory region twice
floppy: Fix hang in watchdog when disk is ejected
media: dib8000: Fix a memleak in dib8000_init()
media: saa7146: mxb: Fix a NULL pointer dereference in mxb_attach()
media: si2157: Fix "warm" tuner state detection
sched/rt: Try to restart rt period timer when rt runtime exceeded
media: dw2102: Fix use after free
media: msi001: fix possible null-ptr-deref in msi001_probe()
usb: ftdi-elan: fix memory leak on device disconnect
x86/mce/inject: Avoid out-of-bounds write when setting flags
pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in 
__nonstatic_find_io_region()
pcmcia: rsrc_nonstatic: Fix a NULL pointer dereference in 
nonstatic_find_mem_region()
ppp: ensure minimum packet size in ppp_write()
fsl/fman: Check for null pointer after calling devm_ioremap
spi: spi-meson-spifc: Add missing pm_runtime_disable() in meson_spifc_probe
tpm: add request_locality before write TPM_INT_ENABLE
can: softing: softing_startstop(): fix set but not used variable warning
can: xilinx_can: xcan_probe(): check for error irq
pcmcia: fix setting of kthread task states
net: mcs7830: handle usb read errors properly
ext4: avoid trim error on fs with small groups
ALSA: jack: Add missing rwsem around snd_ctl_remove() calls
ALSA: PCM: Add missing rwsem around snd_ctl_remove() calls
ALSA: hda: Add missing rwsem around snd_ctl_remove() calls
RDMA/hns: Validate the pkey index
powerpc/prom_init: Fix improper check of prom_getprop()
ALSA: oss: fix compile error when OSS_DEBUG

[Kernel-packages] [Bug 1949075] Re: Bluetooth headset not autoconnecting on power-on on 21.10

2022-02-11 Thread Sebastien Bacher

** Tags removed: champagne

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

Title:
  Bluetooth headset not autoconnecting on power-on on 21.10

Status in bluez package in Ubuntu:
  New

Bug description:
  After moving to Impish, my bluetooth headset doesn't automatically
  connect when I power it on (it was working fine on hirsute).

  
  When I go to the bluetooth settings, select it and click connect, the first 
time it disconnects immediately and I see this line in bluetoothd log:

  Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb()
  Unable to get Hands-Free Voice gateway SDP record: Host is down

  After that, clicking the connect button again makes it work.

  I'm not sure where to find info to debug this furhter

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: bluetooth (not installed)
  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-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 28 13:57:34 2021
  InstallationDate: Installed on 2021-10-16 (11 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20F6CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/08/2019
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R02ET71W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F6CTO1WW
  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.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X260
  dmi.product.name: 20F6CTO1WW
  dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260
  dmi.product.version: ThinkPad X260
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:01:19:D5  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:56756 acl:285 sco:0 events:6453 errors:0
TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0

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


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

[Kernel-packages] [Bug 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's

2022-02-11 Thread Mario Limonciello

The patch series was just accepted into the maintainer's i2c-next tree.
It should be in for 5.18.

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

Title:
  Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's

Status in amd:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in Arch Linux:
  New

Bug description:
  OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard
  RGB controller and the DRAM RGB controllers and after updating my
  system to a 5700G from a 2400G I see error messages in dmesg for each
  read and write attempt to the interfaces. If I swap the CPU back on
  the same install I am able to see and control the RGB interfaces.

  Another user on the OpenRGB discord with a 5600G is also seeing the
  same issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1654 F pulseaudio
   /dev/snd/pcmC1D0p:   user   1654 F...m pulseaudio
   /dev/snd/controlC0:  user   1654 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  6 16:36:17 2021
  InstallationDate: Installed on 2021-09-18 (49 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago)
  dmi.bios.date: 08/11/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.60
  dmi.board.name: B450 Gaming-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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

[Kernel-packages] [Bug 1960403] 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 1960403

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

Title:
  Kubuntu constantly freezing on ThinkPad T510

Status in kubuntu-meta package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This happens either during SDDM, or on the desktop, but Kubuntu's
  constantly freezing up.

  I tried disabling the compositor, but it doesn't seem to help.  Also,
  I removed the external monitor, but that doesn't seem to help.

  I've installed Lubuntu, and so far it's been fine. However, when I
  tried to change the SDDM theme via KDE's System Settings, the laptop
  locked up.

  I'll keep Kubuntu on it for now, but I'm gonna have to switch this to
  Lubuntu in the meantime.

  Specs:
  * Core i7-640M
  * 8GB RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: kubuntu-desktop 1.416
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 05:58:18 2022
  InstallationDate: Installed on 2021-08-07 (186 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago)

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


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

[Kernel-packages] [Bug 1960403] Re: Kubuntu constantly freezing on ThinkPad T510

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

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

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Kubuntu constantly freezing on ThinkPad T510

Status in kubuntu-meta package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  This happens either during SDDM, or on the desktop, but Kubuntu's
  constantly freezing up.

  I tried disabling the compositor, but it doesn't seem to help.  Also,
  I removed the external monitor, but that doesn't seem to help.

  I've installed Lubuntu, and so far it's been fine. However, when I
  tried to change the SDDM theme via KDE's System Settings, the laptop
  locked up.

  I'll keep Kubuntu on it for now, but I'm gonna have to switch this to
  Lubuntu in the meantime.

  Specs:
  * Core i7-640M
  * 8GB RAM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: kubuntu-desktop 1.416
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 05:58:18 2022
  InstallationDate: Installed on 2021-08-07 (186 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: kubuntu-meta
  UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago)

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


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

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

2022-02-11 Thread Stefan Metzmacher

5.14.0-1023.25 seems to work fine.

I used the steps similar to
https://lore.kernel.org/io-uring/CABVffEM79CZ+4SW0+yP0+NioMX=shhoobcefbhqs6g6hex2...@mail.gmail.com/

cmake -DPLUGIN_{MROONGA,ROCKSDB,CONNECT,SPIDER,SPHINX,S3,COLUMNSTORE}=NO 
-DWITH_URING=ON ../mariadb-server
make -j8
mysql-test/mtr  --mysqld=--innodb_use_native_aio=1 --nowarnings --parallel=4 
--force encryption.innochecksum{,} --mysqld=--innodb_io_capacity=5 
--mysqld=--innodb_io_capacity_max=9

And it failed twice with 5.14.0-1022.24, while it finished twice on
5.14.0-1023.25

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

Title:
  io_uring regression - lost write request

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

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

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

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

  Sadly all other versions are EOL for kernel.org.

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

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

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


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

[Kernel-packages] [Bug 1960671] Re: jammy/linux-azure: CIFS 5.15 backport

2022-02-11 Thread Tim Gardner

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

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

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

Title:
  jammy/linux-azure: CIFS 5.15 backport

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

Bug description:
  Backport CIFS updates from git://git.samba.org/sfrench/cifs-2.6.git
  5.15-backport

  SF: #00327908

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


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

[Kernel-packages] [Bug 1960671] Re: jammy/linux-azure: CIFS 5.15 backport

2022-02-11 Thread Tim Gardner

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

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

** Changed in: linux-azure (Ubuntu)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Tags added: bot-stop-nagging

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

** Description changed:

  Backport CIFS updates from git://git.samba.org/sfrench/cifs-2.6.git
  5.15-backport
+ 
+ SF: #00327908

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

Title:
  jammy/linux-azure: CIFS 5.15 backport

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  Backport CIFS updates from git://git.samba.org/sfrench/cifs-2.6.git
  5.15-backport

  SF: #00327908

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


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

[Kernel-packages] [Bug 1960671] 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 1960671

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

Title:
  jammy/linux-azure: CIFS 5.15 backport

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  Backport CIFS updates from git://git.samba.org/sfrench/cifs-2.6.git
  5.15-backport

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


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

[Kernel-packages] [Bug 1960671] [NEW] jammy/linux-azure: CIFS 5.15 backport

2022-02-11 Thread Tim Gardner

Public bug reported:

Backport CIFS updates from git://git.samba.org/sfrench/cifs-2.6.git
5.15-backport

** Affects: linux-azure (Ubuntu)
 Importance: Low
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Low
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress


** Tags: bot-stop-nagging

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

Title:
  jammy/linux-azure: CIFS 5.15 backport

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Jammy:
  In Progress

Bug description:
  Backport CIFS updates from git://git.samba.org/sfrench/cifs-2.6.git
  5.15-backport

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


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

[Kernel-packages] [Bug 1960662] [NEW] nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6: nvidia kernel module failed to build

2022-02-11 Thread Andres

Public bug reported:

External monitor not detected on Ubuntu 20.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.11.0-46-generic
Date: Fri Feb 11 12:32:32 2022
Dependencies:
 
DuplicateSignature: 
dkms:nvidia-kernel-source-440:440.82+really.440.64-0ubuntu6:/var/lib/dkms/nvidia/440.64/build/common/inc/nv-mm.h:149:45:
 error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2021-10-06 (128 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageVersion: 440.82+really.440.64-0ubuntu6
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-440
Title: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6: nvidia kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6: nvidia kernel
  module failed to build

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

Bug description:
  External monitor not detected on Ubuntu 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.11.0-46-generic
  Date: Fri Feb 11 12:32:32 2022
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-440:440.82+really.440.64-0ubuntu6:/var/lib/dkms/nvidia/440.64/build/common/inc/nv-mm.h:149:45:
 error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2021-10-06 (128 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageVersion: 440.82+really.440.64-0ubuntu6
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-440
  Title: nvidia-kernel-source-440 440.82+really.440.64-0ubuntu6: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1960660] [NEW] nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to build

2022-02-11 Thread Νικόλαος Τσιρονίκος

Public bug reported:

ubuntu stuck. hard reset

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
Uname: Linux 5.10.0-1057-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.10.0-1057-oem
Date: Thu Feb 10 07:45:46 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
DuplicateSignature: 
dkms:nvidia-dkms-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-mm.h:149:45:
 error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2021-05-13 (273 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
PackageVersion: 440.100-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.2
SourcePackage: nvidia-graphics-drivers-440
Title: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed
  to build

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

Bug description:
  ubuntu stuck. hard reset

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-440 440.100-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
  Uname: Linux 5.10.0-1057-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.10.0-1057-oem
  Date: Thu Feb 10 07:45:46 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DuplicateSignature: 
dkms:nvidia-dkms-440:440.100-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/440.100/build/common/inc/nv-mm.h:149:45:
 error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer 
type [-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2021-05-13 (273 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  PackageVersion: 440.100-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: nvidia-graphics-drivers-440
  Title: nvidia-dkms-440 440.100-0ubuntu0.20.04.1: nvidia kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1957808] Re: Kernel soft lockup after resume

2022-02-11 Thread Michael Kuefner

Hi Thomas,

thank you for the help to gather more information.
I added "initcall_debug" in grub and tested the suspend / cpu-lockup problem 
after a rebooting into the new grub config.

I tried it different times, and can say, that the connected Thunderbolt
dock was not the problem, as the cpu-lockup also happens, when the
laptop was not connected to anything.

It is not happening on each suspend, but after some rounds of
suspend+resume I can see the problem.


In the attachment is the kern.log with two incidents, the last one took quite a 
while (8000s).

If you have any other idea or have things I can test, I am happy to
help!


Best regards,
Michael

** Attachment added: "kernel.log.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957808/+attachment/5560417/+files/kernel.log.tgz

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

Title:
  Kernel soft lockup after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the kernel hangs after resuming from suspend.
  It might be a problem when suspending, while the DELL thunderbolt dock is 
connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-25-generic 5.13.0-25.26
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  minni  5443 F pulseaudio
   /dev/snd/pcmC0D0c:   minni  5443 F...m pulseaudio
   /dev/snd/pcmC0D0p:   minni  5443 F...m pulseaudio
   /dev/snd/timer:  minni  5443 f pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 13 15:53:19 2022
  InstallationDate: Installed on 2020-12-19 (389 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. XPS 15 9500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-25-generic N/A
   linux-backports-modules-5.13.0-25-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-17 (88 days ago)
  dmi.bios.date: 05/26/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 05XYW7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd05/26/2021:br1.8:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9500
  dmi.product.sku: 097D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1960649] 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 1960649

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

Title:
  Support arch restrictions in lrm

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  LRM drivers may only be supported on some architectures, and not
  others.

  package.config already supports specifying which kernel flavours &
  architectures to build modules for.

  Also allow to specify optional arch= keys in dkms-versions.

  Such that a subset of drivers are built on arches for which both the
  driver and kernel-flavour exist.

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


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

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

2022-02-11 Thread Kleber Sacilotto de Souza

This patch was also already applied to Bionic via " Bionic update:
upstream stable patchset 2022-01-27" (bug 1959335).

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

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

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

Bug description:
  [Impact]

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

  [Fix]

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

  [Test Plan]

  Build HID_ASUS as module with or without USB_HID.

  [Where problems could occur]

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

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


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

[Kernel-packages] [Bug 1960649] [NEW] Support arch restrictions in lrm

2022-02-11 Thread Dimitri John Ledkov

Public bug reported:

LRM drivers may only be supported on some architectures, and not others.

package.config already supports specifying which kernel flavours &
architectures to build modules for.

Also allow to specify optional arch= keys in dkms-versions.

Such that a subset of drivers are built on arches for which both the
driver and kernel-flavour exist.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Dimitri John Ledkov (xnox)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  Support arch restrictions in lrm

Status in linux package in Ubuntu:
  New

Bug description:
  LRM drivers may only be supported on some architectures, and not
  others.

  package.config already supports specifying which kernel flavours &
  architectures to build modules for.

  Also allow to specify optional arch= keys in dkms-versions.

  Such that a subset of drivers are built on arches for which both the
  driver and kernel-flavour exist.

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


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

[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

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

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

Title:
  jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >=
  11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in gcc-11 source package in Impish:
  New
Status in linux source package in Impish:
  Fix Committed
Status in gcc-11 source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Installing zfs-dkms seems to trigger a soft lockup issue as soon as
  zfs.ko is loaded. When the soft lockup happens the system isn't
  reachable anymore via ssh and on the console we can see some exlicit
  rcu stall warnings.

  This seems to happen only when zfs is compile with gcc >=
  11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show
  the problem and zfs is working just fine.

  [Test case]

  On s390x install the latest 5.15 Jammy kernel and run:
  apt install zfs-dkms

  [Fix]

  Temporary workaround is to build zfs with gcc-10 on s390x.

  [Regression potential]

  Building a kernel module with a different compiler is never 100% safe,
  we may experience potential crashes / panics if the ABI is not
  compatible. Moreover, if we build zfs with gcc-10 we are going to lose
  some of the performance benefits provided by gcc-11.

  However these regressions are limited to zfs on s390x and without this
  change zfs is broken anyway on this architecture.

  [Further analysis]

  @IBM

  Issue report to zfs upstream at
  https://github.com/openzfs/zfs/issues/12942

  Reverting
  
https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7
  appears to make everything work, the compiled kernel and zfs.ko are
  loadable/unloadable once again.

  Please bring this issue to the attention of  Ilya Leoshkevich

  Potentially this means we may have missbuilt userspace binaries in the
  archive for s390x.

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


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

[Kernel-packages] [Bug 1960565] Re: package linux-image-5.4.0-99-generic 5.4.0-99.112 failed to install/upgrade

2022-02-11 Thread Jeff Hamric

I found 30_os_prober.bak in /etc/grub.d. I compared the two & deleted
30_os_prober & rennaming 30_os_prober.bak. Installation then proceeded.

Mark as solved.

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

Title:
  package linux-image-5.4.0-99-generic 5.4.0-99.112 failed to
  install/upgrade

Status in linux-signed package in Ubuntu:
  New

Bug description:
  Running sudo dpkg --configure -a returns the following

  Setting up linux-image-5.4.0-99-generic (5.4.0-99.112) ...
  Processing triggers for linux-image-5.4.0-99-generic (5.4.0-99.112) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.4.0-99-generic
  /etc/kernel/postinst.d/zz-update-grub:
  Sourcing file `/etc/default/grub'
  Sourcing file `/etc/default/grub.d/init-select.cfg'
  Generating grub configuration file ...
  Found background image: Methane_Rose_B_by_skamradt.jpg
  Found linux image: /boot/vmlinuz-5.13.0-28-generic
  Found initrd image: /boot/initrd.img-5.13.0-28-generic
  Found linux image: /boot/vmlinuz-5.13.0-27-generic
  Found initrd image: /boot/initrd.img-5.13.0-27-generic
  Found linux image: /boot/vmlinuz-5.4.0-99-generic
  Found initrd image: /boot/initrd.img-5.4.0-99-generic
  /etc/grub.d/30_os-prober: 39: Syntax error: "fi" unexpected (expecting "then")
  run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 2
  dpkg: error processing package linux-image-5.4.0-99-generic (--configure):
   installed linux-image-5.4.0-99-generic package post-installation script 
subprocess returned error exit status 1
  Errors were encountered while processing:
   linux-image-5.4.0-99-generic

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-99-generic 5.4.0-99.112
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   linux-generic-hwe-18.04:amd64: Install
   linux-libc-dev:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jeff  12206 F pulseaudio
   /dev/snd/pcmC1D0p:   jeff  12206 F...m pulseaudio
   /dev/snd/controlC0:  jeff  12206 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Feb  7 14:01:26 2022
  DpkgHistoryLog:
   Start-Date: 2022-02-07  14:00:51
   Requested-By: jeff (1000)
   Upgrade: linux-libc-dev:amd64 (5.4.0-97.110, 5.4.0-99.112), 
linux-generic-hwe-18.04:amd64 (5.4.0.97.101, 5.4.0.99.103)
  ErrorMessage: installed linux-image-5.4.0-99-generic package 
post-installation script subprocess returned error exit status 1
  MachineType: Dell Inc. Inspiron 5575
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=b91e31b8-e61f-4428-afa9-5ff99f9abadc ro quiet splash idle=nomwait 
acpi_backlight=vendor
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux-signed
  Title: package linux-image-5.4.0-99-generic 5.4.0-99.112 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2019
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.asset.tag: not specified
  dmi.board.name: 0M0Y6P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.3
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:br5.3:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn0M0Y6P:rvrX01:cvnDellInc.:ct10:cvr1.3.3:sku0812:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5575
  dmi.product.sku: 0812
  dmi.product.version: 1.3.3
  dmi.sys.vendor: Dell Inc.

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


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

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

That came via "Focal update: v5.4.170 upstream stable release" (bug
1958898). I added this report to the bug references.

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

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

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

Bug description:
  [Impact]

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

  [Fix]

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

  [Test Plan]

  Build HID_ASUS as module with or without USB_HID.

  [Where problems could occur]

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

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


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-02-11 Thread Timo Aaltonen

Hello jeremyszu, or anyone else affected,

Accepted nvidia-settings into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/470.57.01-0ubuntu0.20.04.3 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nvidia-settings (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Impish:
  Fix Committed
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * reboot the system
   * prime-select query (and check that on-demand mode is still in use).

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Kernel-packages] [Bug 1957986] Re: Recalled NFSv4 files delegations overwhelm server

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

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

Title:
  Recalled NFSv4 files delegations overwhelm server

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

Bug description:
  [Impact]
  An NFSv4 client that does a lot of opens/closes can overwhelm and NFSv4 
server, causing a significant drop in performance. In my testing, I've seen 
performance drop from ~700MiB/s down to < 10MiB/s. The same workload using 
NFSv3 does not have this problem.

  [Test Case]
  This can be demonstrated using the elbencho benchmark from 
https://github.com/breuner/elbencho:
   $ elbencho -t 40 -r -n 10 -N 5000 -s 128k -b 128k /mnt/nfs/ubuntu

  You'll notice the nfsd threads (I stuck w/ the default of 4) start to
  consume 100% CPU, and the performance of the elbencho benchmark will
  begin to trickle.

  [Fix]
  The following fix solves the problem, but there are a number of patches 
dependencies required before it will apply to focal:

  commit 10717f45639f6c1bc27b56405252c3a027406d92 (refs/bisect/bad)
  Author: Trond Myklebust 
  Date:   Mon Jan 27 09:58:19 2020 -0500

  NFSv4: Limit the total number of cached delegations

  Delegations can be expensive to return, and can cause scalability issues
  for the server. Let's therefore try to limit the number of inactive
  delegations we hold.
  Once the number of delegations is above a certain threshold, start
  to return them on close.

  Signed-off-by: Trond Myklebust 
  Signed-off-by: Anna Schumaker 

  [What could go wrong]
  The fixes are restricted to NFS code, so problems should be limited to NFS 
users. They could include performance issues, crashes, etc. Because these 
changes are mostly related to NFS delegations, I use the `nfstest_delegation` 
test suite from nfstest[*] to try and identify any regressions: 

  ./nfstest_delegation --client 192.168.42.1 --server 192.168.42.2 -e
  /srv/nfstest --trcdelay 4

  Both before and after applying the fixes, I see the same 146 tests
  pass and 23 failures. The 23 failures are expected because I was using
  a Linux-based NFSv4 server which does not support all of the
  delegation modes that the test checks for.

  [*] git://git.linux-nfs.org/projects/mora/nfstest.git

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


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

[Kernel-packages] [Bug 1960643] [NEW] wifi adapter sometimes not working after startup

2022-02-11 Thread Claudio Corvino

Public bug reported:

1)
Description:Ubuntu 20.04.3 LTS
Release:20.04
2)
ii  iw 5.4-1
 amd64tool for configuring Linux wireless devices
3)
wifi adapter working on every boot
4)
Sometimes wifi does not work after booting and I need to restart laptop.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-oem-20.04b 5.10.0.1057.57
ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
Uname: Linux 5.10.0-1057-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 11 16:17:11 2022
InstallationDate: Installed on 2021-02-03 (373 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: linux-meta-oem-5.10
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  wifi adapter sometimes not working after startup

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

Bug description:
  1)
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  2)
  ii  iw 5.4-1  
   amd64tool for configuring Linux wireless devices
  3)
  wifi adapter working on every boot
  4)
  Sometimes wifi does not work after booting and I need to restart laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-oem-20.04b 5.10.0.1057.57
  ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
  Uname: Linux 5.10.0-1057-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 11 16:17:11 2022
  InstallationDate: Installed on 2021-02-03 (373 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-meta-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390

2022-02-11 Thread Timo Aaltonen

Hello jeremyszu, or anyone else affected,

Accepted nvidia-settings into impish-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
settings/470.57.01-0ubuntu3.1~0.21.10.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nvidia-settings (Ubuntu Impish)
   Status: New => Fix Committed

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

Title:
  on-demand mode doesn't work with nvidia-390

Status in OEM Priority Project:
  New
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Impish:
  Fix Committed
Status in ubuntu-drivers-common source package in Impish:
  Fix Committed
Status in nvidia-settings source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * In any Ubuntu series, if user using a old GPU (which supported by
  nvidia-390 only) then issuing glxinfo will get "Error: couldn't find
  RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri
  driver correctly.

  [Test Plan]

   * install nvidia-390 on nvidia-390 supported system.
   * prime-select on-demand
   * reboot
   * glxinfo
   * after applying this patch, it will fall back to "ON" mode after reboot.

   * install nvidia-450 on nvidia-450 supported system.
   * prime-select on-demand
   * reboot the system
   * prime-select query (and check that on-demand mode is still in use).

  [Where problems could occur]
   * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user 
stays in on-demand mode with 390 without problem, the after upgrading u-d-c and 
reboot. The mode will fall back to "ON" mode.
   * From my point of view, it's fine because nvidia-390 doesn't support RTD3. 
Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
  * While there is no way to inform the user about this change, changing to the 
only supported default will avoid breaking GLX.

  ---

  The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-
  drivers-common/+bug/1942789.

  It impacts Jammy and Impish so far.

  [Steps to reproduce]
  1. Find a GPU supports nvidia-390
  2. ubuntu-drivers install nvidia:390
  3. prime-select on-demand
  4. glxinfo

  [Expected result]
  Shows intel or nvidia drives monitor

  [Actual result]
  Error: couldn't find RGB GLX visual or fbconfig

  Since we are all agree "on-demand" mode as default mode.
  Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter 
RTD3).
  We could consider to make it as performance mode and leave a note on 
nvidia-settings.
  I'll prepare some test packages.

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


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

[Kernel-packages] [Bug 1960633] 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 1960633

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

Title:
  Create linux-modules-extra-generic metapackage

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

  Thank you for your consideration.

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


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

[Kernel-packages] [Bug 1959701] Re: Focal update: v5.4.173 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/1959701

Title:
  Focal update: v5.4.173 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.173 upstream stable release
     from git://git.kernel.org/

  kbuild: Add $(KBUILD_HOSTLDFLAGS) to 'has_libelf' test
  devtmpfs regression fix: reconfigure on each mount
  orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
  perf: Protect perf_guest_cbs with RCU
  KVM: s390: Clarify SIGP orders versus STOP/RESTART
  media: uvcvideo: fix division by zero at stream start
  rtlwifi: rtl8192cu: Fix WARNING when calling local_irq_restore() with 
interrupts enabled
  firmware: qemu_fw_cfg: fix sysfs information leak
  firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate entries
  firmware: qemu_fw_cfg: fix kobject leak in probe error path
  KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
  ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Master after 
reboot from Windows
  mtd: fixup CFI on ixp4xx
  ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
  Linux 5.4.173
  UBUNTU: upstream stable to v5.4.173

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


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

[Kernel-packages] [Bug 1960566] Re: Focal update: v5.4.174 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/1960566

Title:
  Focal update: v5.4.174 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.174 upstream stable release
     from git://git.kernel.org/

  HID: uhid: Fix worker destroying device without any protection
  HID: wacom: Reset expected and received contact counts at the same time
  HID: wacom: Ignore the confidence flag when a touch is removed
  HID: wacom: Avoid using stale array indicies to read contact count
  f2fs: fix to do sanity check in is_alive()
  nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind()
  mtd: rawnand: gpmi: Add ERR007117 protection for nfc_apply_timings
  mtd: rawnand: gpmi: Remove explicit default gpmi clock setting for i.MX6
  x86/gpu: Reserve stolen memory for first integrated Intel GPU
  tools/nolibc: x86-64: Fix startup code bug
  tools/nolibc: i386: fix initial stack alignment
  tools/nolibc: fix incorrect truncation of exit code
  rtc: cmos: take rtc_lock while reading from CMOS
  media: v4l2-ioctl.c: readbuffers depends on V4L2_CAP_READWRITE
  media: flexcop-usb: fix control-message timeouts
  media: mceusb: fix control-message timeouts
  media: em28xx: fix control-message timeouts
  media: cpia2: fix control-message timeouts
  media: s2255: fix control-message timeouts
  media: dib0700: fix undefined behavior in tuner shutdown
  media: redrat3: fix control-message timeouts
  media: pvrusb2: fix control-message timeouts
  media: stk1160: fix control-message timeouts
  can: softing_cs: softingcs_probe(): fix memleak on registration failure
  lkdtm: Fix content of section containing lkdtm_rodata_do_nothing()
  iommu/io-pgtable-arm-v7s: Add error handle for page table allocation failure
  dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
  PCI: Add function 1 DMA alias quirk for Marvell 88SE9125 SATA controller
  mm_zone: add function to check if managed dma zone exists
  mm/page_alloc.c: do not warn allocation failure on zone DMA if no managed 
pages
  shmem: fix a race between shmem_unused_huge_shrink and shmem_evict_inode
  drm/rockchip: dsi: Hold pm-runtime across bind/unbind
  drm/rockchip: dsi: Reconfigure hardware on resume()
  drm/panel: kingdisplay-kd097d04: Delete panel on attach() failure
  drm/panel: innolux-p079zca: Delete panel on attach() failure
  drm/rockchip: dsi: Fix unbalanced clock on probe error
  Bluetooth: cmtp: fix possible panic when cmtp_init_sockets() fails
  clk: bcm-2835: Pick the closest clock rate
  clk: bcm-2835: Remove rounding up the dividers
  wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND
  wcn36xx: Release DMA channel descriptor allocations
  media: videobuf2: Fix the size printk format
  media: aspeed: fix mode-detect always time out at 2nd run
  media: em28xx: fix memory leak in em28xx_init_dev
  media: aspeed: Update signal status immediately to ensure sane hw state
  arm64: dts: meson-gxbb-wetek: fix HDMI in early boot
  arm64: dts: meson-gxbb-wetek: fix missing GPIO binding
  Bluetooth: stop proccessing malicious adv data
  tee: fix put order in teedev_close_context()
  media: dmxdev: fix UAF when dvb_register_device() fails
  crypto: qce - fix uaf on qce_ahash_register_one
  arm64: dts: ti: k3-j721e: correct cache-sets info
  tty: serial: atmel: Check return code of dmaengine_submit()
  tty: serial: atmel: Call dma_async_issue_pending()
  media: rcar-csi2: Correct the selection of hsfreqrange
  media: imx-pxp: Initialize the spinlock prior to using it
  media: si470x-i2c: fix possible memory leak in si470x_i2c_probe()
  media: mtk-vcodec: call v4l2_m2m_ctx_release first when file is released
  media: venus: core: Fix a resource leak in the error handling path of 
'venus_probe()'
  netfilter: bridge: add support for pppoe filtering
  arm64: dts: qcom: msm8916: fix MMC controller aliases
  ACPI: EC: Rework flushing of EC work while suspended to idle
  drm/amdgpu: Fix a NULL pointer dereference in 
amdgpu_connector_lcd_native_mode()
  drm/radeon/radeon_kms: Fix a NULL pointer dereference in 
radeon_driver_open_kms()
  arm64: dts: ti: k3-j721e: Fix the L2 cache sets
  tty: serial: uartlite: allow 64 bit address
  serial: amba-pl011: do not request memory region twice

[Kernel-packages] [Bug 1959698] Re: Focal update: v5.4.172 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/1959698

Title:
  Focal update: v5.4.172 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.172 upstream stable release
     from git://git.kernel.org/

  workqueue: Fix unbind_workers() VS wq_worker_running() race
  Bluetooth: btusb: fix memory leak in btusb_mtk_submit_wmt_recv_urb()
  Bluetooth: bfusb: fix division by zero in send path
  USB: core: Fix bug in resuming hub's handling of wakeup requests
  USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
  mmc: sdhci-pci: Add PCI ID for Intel ADL
  veth: Do not record rx queue hint in veth_xmit
  mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
  drivers core: Use sysfs_emit and sysfs_emit_at for show(device *...) functions
  can: gs_usb: fix use of uninitialized variable, detach device on reception of 
invalid USB data
  can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
  random: fix data race on crng_node_pool
  random: fix data race on crng init time
  random: fix crash on multiple early calls to add_bootloader_randomness()
  media: Revert "media: uvcvideo: Set unique vdev name based in type"
  staging: wlan-ng: Avoid bitwise vs logical OR warning in 
hfa384x_usb_throttlefn()
  drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
  staging: greybus: fix stack size warning with UBSAN
  Linux 5.4.172
  UBUNTU: upstream stable to v5.4.172

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


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

[Kernel-packages] [Bug 1959437] Re: Focal update: v5.4.171 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/1959437

Title:
  Focal update: v5.4.171 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.171 upstream stable release
     from git://git.kernel.org/

  f2fs: quota: fix potential deadlock
  Input: touchscreen - Fix backport of a02dcde595f7cbd240ccd64de96034ad91cffc40
  selftests: x86: fix [-Wstringop-overread] warn in test_process_vm_readv()
  tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
  tracing: Tag trace_percpu_buffer as a percpu pointer
  ieee802154: atusb: fix uninit value in atusb_set_extended_addr
  iavf: Fix limit of total number of queues to active queues of VF
  RDMA/core: Don't infoleak GRH fields
  RDMA/uverbs: Check for null return of kmalloc_array
  mac80211: initialize variable have_higher_than_11mbit
  i40e: fix use-after-free in i40e_sync_filters_subtask()
  i40e: Fix for displaying message regarding NVM version
  i40e: Fix incorrect netdev's real number of RX/TX queues
  ipv4: Check attribute length for RTA_GATEWAY in multipath route
  ipv4: Check attribute length for RTA_FLOW in multipath route
  ipv6: Check attribute length for RTA_GATEWAY in multipath route
  ipv6: Check attribute length for RTA_GATEWAY when deleting multipath route
  lwtunnel: Validate RTA_ENCAP_TYPE attribute length
  batman-adv: mcast: don't send link-local multicast to mcast routers
  sch_qfq: prevent shift-out-of-bounds in qfq_init_qdisc
  net: phy: micrel: set soft_reset callback to genphy_soft_reset for KSZ8081
  power: supply: core: Break capacity loop
  power: reset: ltc2952: Fix use of floating point literals
  rndis_host: support Hytera digital radios
  phonet: refcount leak in pep_sock_accep
  ipv6: Continue processing multipath route even if gateway attribute is invalid
  ipv6: Do cleanup if attribute validation fails in multipath route
  usb: mtu3: fix interval value for intr and isoc
  scsi: libiscsi: Fix UAF in iscsi_conn_get_param()/iscsi_conn_teardown()
  ip6_vti: initialize __ip6_tnl_parm struct in vti6_siocdevprivate
  net: udp: fix alignment problem in udp4_seq_show()
  atlantic: Fix buff_ring OOB in aq_ring_rx_clean
  mISDN: change function names to avoid conflicts
  Linux 5.4.171
  UBUNTU: upstream stable to v5.4.171

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


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

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

This bug was fixed in the package busybox - 1:1.30.1-7ubuntu3

---
busybox (1:1.30.1-7ubuntu3) jammy; urgency=medium

  * Add dirname from coreutils to the initramfs (LP: #1960083)

 -- William 'jawn-smith' Wilson   Fri, 04 Feb
2022 16:10:23 -0600

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

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

Title:
  dirname applet missing from initramfs

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

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

  /init: line 971: dirname: not found

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

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

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

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

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


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

[Kernel-packages] [Bug 1958557] Re: Focal update: v5.4.169 upstream stable release

Skipped (already applied):
- HID: holtek: fix mouse probing

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

Title:
  Focal update: v5.4.169 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.169 upstream stable release
     from git://git.kernel.org/

  net: usb: lan78xx: add Allied Telesis AT29M2-AF
  serial: 8250_fintek: Fix garbled text for console
  HID: holtek: fix mouse probing
  arm64: dts: allwinner: orangepi-zero-plus: fix PHY mode
  spi: change clk_disable_unprepare to clk_unprepare
  IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
  netfilter: fix regression in looped (broad|multi)cast's MAC handling
  qlcnic: potential dereference null pointer of rx_queue->page_ring
  net: accept UFOv6 packages in virtio_net_hdr_to_skb
  net: skip virtio_net_hdr_set_proto if protocol already set
  ipmi: Fix UAF when uninstall ipmi_si and ipmi_msghandler module
  bonding: fix ad_actor_system option setting to default
  fjes: Check for error irq
  drivers: net: smc911x: Check for error irq
  sfc: falcon: Check null pointer of rx_queue->page_ring
  Input: elantech - fix stack out of bound access in elantech_change_report_id()
  hwmon: (lm90) Fix usage of CONFIG2 register in detect function
  hwmon: (lm90) Add max6654 support to lm90 driver
  hwmon: (lm90) Add basic support for TI TMP461
  hwmon: (lm90) Introduce flag indicating extended temperature support
  hwmon: (lm90) Drop critical attribute support for MAX6654
  ALSA: jack: Check the return value of kstrdup()
  ALSA: drivers: opl3: Fix incorrect use of vp->state
  ALSA: hda/realtek: Amp init fixup for HP ZBook 15 G6
  Input: atmel_mxt_ts - fix double free in mxt_read_info_block
  ipmi: bail out if init_srcu_struct fails
  ipmi: ssif: initialize ssif_info->client early
  ipmi: fix initialization when workqueue allocation fails
  parisc: Correct completer in lws start
  x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
  pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
  mmc: sdhci-tegra: Fix switch to HS400ES mode
  mmc: core: Disable card detect during shutdown
  ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
  tee: optee: Fix incorrect page free bug
  f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
  usb: gadget: u_ether: fix race in setting MAC address in setup phase
  KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
  mm: mempolicy: fix THP allocations escaping mempolicy restrictions
  pinctrl: mediatek: fix global-out-of-bounds issue
  hwmom: (lm90) Fix citical alarm status for MAX6680/MAX6681
  hwmon: (lm90) Do not report 'busy' status bit as alarm
  ax25: NPD bug when detaching AX25 device
  hamradio: defer ax25 kfree after unregister_netdev
  hamradio: improve the incomplete fix to avoid NPD
  phonet/pep: refuse to enable an unbound pipe
  Linux 5.4.169
  UBUNTU: upstream stable to v5.4.169

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


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

[Kernel-packages] [Bug 1958898] Re: Focal update: v5.4.170 upstream stable release

Skipped (already applied):
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment

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

Title:
  Focal update: v5.4.170 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.170 upstream stable release
     from git://git.kernel.org/

  HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option
  tee: handle lookup of shm with reference count 0
  Input: i8042 - add deferred probe support
  Input: i8042 - enable deferred probe quirk for ASUS UM325UA
  tomoyo: Check exceeded quota early in tomoyo_domain_quota_is_ok().
  platform/x86: apple-gmux: use resource_size() with res
  memblock: fix memblock_phys_alloc() section mismatch error
  recordmcount.pl: fix typo in s390 mcount regex
  selinux: initialize proto variable in selinux_ip_postroute_compat()
  scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write()
  net/mlx5: DR, Fix NULL vs IS_ERR checking in dr_domain_init_resources
  udp: using datalen to cap ipv6 udp max gso segments
  selftests: Calculate udpgso segment count without header adjustment
  sctp: use call_rcu to free endpoint
  net: usb: pegasus: Do not drop long Ethernet frames
  net: lantiq_xrx200: fix statistics of received bytes
  NFC: st21nfca: Fix memory leak in device probe and remove
  ionic: Initialize the 'lif->dbid_inuse' bitmap
  net/mlx5e: Fix wrong features assignment in case of error
  selftests/net: udpgso_bench_tx: fix dst ip argument
  net/ncsi: check for error return from call to nla_put_u32
  fsl/fman: Fix missing put_device() call in fman_port_probe
  i2c: validate user data in compat ioctl
  nfc: uapi: use kernel size_t to fix user-space builds
  uapi: fix linux/nfc.h userspace compilation errors
  xhci: Fresco FL1100 controller should not have BROKEN_MSI quirk set.
  usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.
  usb: mtu3: add memory barrier before set GPD's HWO
  usb: mtu3: fix list_head check warning
  usb: mtu3: set interval of FS intr and isoc endpoint
  binder: fix async_free_space accounting for empty parcels
  scsi: vmw_pvscsi: Set residual data length conditionally
  Input: appletouch - initialize work before device registration
  Input: spaceball - fix parsing of movement data packets
  net: fix use-after-free in tw_timer_handler
  perf script: Fix CPU filtering of a script's switch events
  Linux 5.4.170
  UBUNTU: upstream stable to v5.4.170

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


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

[Kernel-packages] [Bug 1957991] Re: Focal update: v5.4.168 upstream stable release

Skipped (already applied):
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum

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

Title:
  Focal update: v5.4.168 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.168 upstream stable release
     from git://git.kernel.org/

  KVM: selftests: Make sure kvm_create_max_vcpus test won't hit RLIMIT_NOFILE
  mac80211: mark TX-during-stop for TX in in_reconfig
  mac80211: send ADDBA requests using the tid/queue of the aggregation session
  firmware: arm_scpi: Fix string overflow in SCPI genpd driver
  virtio_ring: Fix querying of maximum DMA mapping size for virtio device
  recordmcount.pl: look for jgnop instruction as well as bcrl on s390
  dm btree remove: fix use after free in rebalance_children()
  audit: improve robustness of the audit queue handling
  iio: adc: stm32: fix a current leak by resetting pcsel before disabling vdda
  nfsd: fix use-after-free due to delegation race
  arm64: dts: rockchip: remove mmc-hs400-enhanced-strobe from rk3399-khadas-edge
  arm64: dts: rockchip: fix rk3399-leez-p710 vcc3v3-lan supply
  arm64: dts: rockchip: fix audio-supply for Rock Pi 4
  mac80211: track only QoS data frames for admission control
  ARM: socfpga: dts: fix qspi node compatible
  clk: Don't parent clks until the parent is fully registered
  selftests: net: Correct ping6 expected rc from 2 to 1
  s390/kexec_file: fix error handling when applying relocations
  sch_cake: do not call cake_destroy() from cake_init()
  inet_diag: use jiffies_delta_to_msecs()
  inet_diag: fix kernel-infoleak for UDP sockets
  selftests: Fix raw socket bind tests with VRF
  selftests: Fix IPv6 address bind tests
  dmaengine: st_fdma: fix MODULE_ALIAS
  selftest/net/forwarding: declare NETIFS p9 p10
  mac80211: agg-tx: refactor sending addba
  mac80211: agg-tx: don't schedule_and_wake_txq() under sta->lock
  mac80211: accept aggregation sessions on 6 GHz
  mac80211: fix lookup when adding AddBA extension element
  net: sched: lock action when translating it to flow_action infra
  flow_offload: return EOPNOTSUPP for the unsupported mpls action type
  rds: memory leak in __rds_conn_create()
  soc/tegra: fuse: Fix bitwise vs. logical OR warning
  igb: Fix removal of unicast MAC filters of VFs
  igbvf: fix double free in `igbvf_probe`
  ixgbe: set X550 MDIO speed before talking to PHY
  netdevsim: Zero-initialize memory for new map's value in function 
nsim_bpf_map_alloc
  net/packet: rx_owner_map depends on pg_vec
  net: Fix double 0x prefix print in SKB dump
  net/smc: Prevent smc_release() from long blocking
  net: systemport: Add global locking for descriptor lifecycle
  sit: do not call ipip6_dev_free() from sit_init_net()
  USB: gadget: bRequestType is a bitfield, not a enum
  USB: NO_LPM quirk Lenovo USB-C to Ethernet Adapher(RTL8153-04)
  PCI/MSI: Clear PCI_MSIX_FLAGS_MASKALL on error
  PCI/MSI: Mask MSI-X vectors only on success
  usb: xhci: Extend support for runtime power management for AMD's Yellow carp.
  USB: serial: cp210x: fix CP2105 GPIO registration
  USB: serial: option: add Telit FN990 compositions
  timekeeping: Really make sure wall_to_monotonic isn't positive
  libata: if T_LENGTH is zero, dma direction should be DMA_NONE
  drm/amdgpu: correct register access for RLC_JUMP_TABLE_RESTORE
  mac80211: validate extended element ID is present
  mwifiex: Remove unnecessary braces from HostCmd_SET_SEQ_NO_BSS_INFO
  Input: touchscreen - avoid bitwise vs logical OR warning
  ARM: dts: imx6ull-pinfunc: Fix CSI_DATA07__ESAI_TX0 pad name
  xsk: Do not sleep in poll() when need_wakeup set
  media: mxl111sf: change mutex_init() location
  fuse: annotate lock in fuse_reverse_inval_entry()
  ovl: fix warning in ovl_create_real()
  scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select()
  rcu: Mark accesses to rcu_state.n_force_qs
  mac80211: fix regression in SSN handling of addba tx
  net: sched: Fix suspicious RCU usage while accessing tcf_tunnel_info
  Revert "xsk: Do not sleep in poll() when need_wakeup set"
  xen/blkfront: harden blkfront against event channel storms
  xen/netfront: harden netfront against event channel storms
  xen/console: harden

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

2022-02-11 Thread Clement Cherlin

Public bug reported:

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

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

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

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

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

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

Thank you for your consideration.

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

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

Title:
  Create linux-modules-extra-generic metapackage

Status in linux package in Ubuntu:
  New

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

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

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

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

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

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

  Thank you for your consideration.

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


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

[Kernel-packages] [Bug 1957987] Re: Focal update: v5.4.167 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/1957987

Title:
  Focal update: v5.4.167 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.167 upstream stable release
     from git://git.kernel.org/

  nfc: fix segfault in nfc_genl_dump_devices_done
  drm/msm/dsi: set default num_data_lanes
  net/mlx4_en: Update reported link modes for 1/10G
  parisc/agp: Annotate parisc agp init functions with __init
  i2c: rk3x: Handle a spurious start completion interrupt flag
  net: netlink: af_netlink: Prevent empty skb by adding a check on len.
  drm/amd/display: Fix for the no Audio bug with Tiled Displays
  drm/amd/display: add connector type check for CRC source set
  tracing: Fix a kmemleak false positive in tracing_map
  KVM: x86: Ignore sparse banks size for an "all CPUs", non-sparse IPI req
  selinux: fix race condition when computing ocontext SIDs
  bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc
  hwmon: (dell-smm) Fix warning on /proc/i8k creation error
  memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER
  memblock: align freed memory map on pageblock boundaries with SPARSEMEM
  memblock: ensure there is no overflow in memblock_overlaps_region()
  arm: extend pfn_valid to take into account freed memory map alignment
  arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
  Linux 5.4.167
  UBUNTU: upstream stable to v5.4.167

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


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

[Kernel-packages] [Bug 1959529] Comment bridged from LTC Bugzilla

2022-02-11 Thread bugproxy

--- Comment From wint...@de.ibm.com 2022-02-11 09:02 EDT---
Thanks again to Krzysztof and Thadeu for the careful review of the backport.
I'm embarrassed to admit that my initial tests didn't show the problem; 
possibly a build error on my side. I tried again today and KASAN showed the 
issue.
I also took the opportunity to educate myself more about get_free_page,
alloc_page and GFP flags. Thanks again.

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

Title:
  Hipersocket page allocation failure on Ubuntu 20.04 based SSC
  environments

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  == Comment: #0 - D. Gary Chapman  - 2022-01-26 12:43:25 ==
  ---Problem Description---
  IBM IDAA customer exposes hipersocket page allocation failure on Ubuntu 20.04 
based SSC

  Contact Information = Gary Chapman (ch...@us.ibm.com)

  ---uname output---
  5.4.0-73-generic #82-Ubuntu

  Machine Type = IBM Z in IDAA SSC-mode lpar

  ---Debugger---
  A debugger is not configured

  --

  IBM SSC LEVEL: 4.1.5
  IBM IDAA LEVEL: 7.5.6

  On a client system we are observing this:

  Jan 19 16:25:57 data5 kernel: kworker/u760:28: page allocation failure: 
order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0
  Jan 19 16:25:57 data5 kernel: CPU: 20 PID: 4137988 Comm: kworker/u760:28 
Kdump: loaded Tainted: G   OE 5.4.0-73-generic #82-Ubuntu
  Jan 19 16:25:57 data5 kernel: Hardware name: IBM 8561 T01 727 (LPAR)
  Jan 19 16:25:57 data5 kernel: Workqueue: kcryptd/253:11 kcryptd_crypt 
[dm_crypt]
  Jan 19 16:25:57 data5 kernel: Call Trace:
  Jan 19 16:25:57 data5 kernel: ([<006b6d63e092>] show_stack+0x7a/0xc0)
  Jan 19 16:25:57 data5 kernel:  [<006b6d64588a>] dump_stack+0x8a/0xb8
  Jan 19 16:25:57 data5 kernel:  [<006b6cfd8262>] warn_alloc+0xe2/0x160

  IBM LTC Networking team has identified the upstream commit
  714c9108851743bb718fbc1bfb81290f12a53854 as the root cause.

  This  patch shows up in the Ubuntu kernel source tree:
  
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/commit/?id=714c9108851743bb718fbc1bfb81290f12a53854
  but has not been ported to Ubuntu 20.04 / kernel 5.4

  IDAA on SSC requests backport to focal.

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


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

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

2022-02-11 Thread James Ferguson

Any chance this bug can get assigned and get some attention?  An entire
generation of Ryzen systems seem to be rendered unusable without holding
back the kernel to 5.11.

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

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

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

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

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

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

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

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

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

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

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

  Happy to assist with investigations.

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

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


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

[Kernel-packages] [Bug 1960452] Re: Impish update: upstream stable patchset 2022-02-09

Skipped (already applied):
- bpf: Fix out of bounds access from invalid *_or_null type verification

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

Title:
  Impish update: upstream stable patchset 2022-02-09

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 2022-02-09

  Ported from the following upstream stable releases:
  v5.10.92, v5.15.15

     from git://git.kernel.org/

  workqueue: Fix unbind_workers() VS wq_worker_running() race
  bpf: Fix out of bounds access from invalid *_or_null type verification
  Bluetooth: btusb: fix memory leak in btusb_mtk_submit_wmt_recv_urb()
  Bluetooth: btusb: Add two more Bluetooth parts for WCN6855
  Bluetooth: btusb: Add support for Foxconn QCA 0xe0d0
  Bluetooth: bfusb: fix division by zero in send path
  ARM: dts: exynos: Fix BCM4330 Bluetooth reset polarity in I9100
  USB: core: Fix bug in resuming hub's handling of wakeup requests
  USB: Fix "slab-out-of-bounds Write" bug in usb_hcd_poll_rh_status
  ath11k: Fix buffer overflow when scanning with extraie
  mmc: sdhci-pci: Add PCI ID for Intel ADL
  mfd: intel-lpss: Fix too early PM enablement in the ACPI ->probe()
  can: gs_usb: fix use of uninitialized variable, detach device on reception of 
invalid USB data
  can: isotp: convert struct tpcon::{idx,len} to unsigned int
  can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
  random: fix data race on crng_node_pool
  random: fix data race on crng init time
  random: fix crash on multiple early calls to add_bootloader_randomness()
  media: Revert "media: uvcvideo: Set unique vdev name based in type"
  staging: wlan-ng: Avoid bitwise vs logical OR warning in 
hfa384x_usb_throttlefn()
  drm/i915: Avoid bitwise vs logical OR warning in snb_wm_latency_quirk()
  staging: greybus: fix stack size warning with UBSAN
  s390/kexec: handle R_390_PLT32DBL rela in arch_kexec_apply_relocations_add()
  Bluetooth: btusb: Add the new support ID for Realtek RTL8852A
  Bluetooth: btusb: Add support for IMC Networks Mediatek Chip(MT7921)
  Bbluetooth: btusb: Add another Bluetooth part for Realtek 8852AE
  Bluetooth: btusb: Enable MSFT extension for Mediatek Chip (MT7921)
  Bluetooth: btusb: enable Mediatek to support AOSP extension
  Bluetooth: btusb: Add one more Bluetooth part for the Realtek RTL8852AE
  Bluetooth: btusb: Add the new support IDs for WCN6855
  fget: clarify and improve __fget_files() implementation
  Bluetooth: btusb: Add one more Bluetooth part for WCN6855
  Bluetooth: add quirk disabling LE Read Transmit Power
  Bluetooth: btbcm: disable read tx power for some Macs with the T2 Security 
chip
  Bluetooth: btbcm: disable read tx power for MacBook Air 8,1 and 8,2
  UBUNTU: upstream stable to v5.10.92, v5.15.15

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


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

[Kernel-packages] [Bug 1959627] Re: Impish update: upstream stable patchset 2022-01-31

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

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

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 2022-01-31

  Ported from the following upstream stable releases:
  v5.10.91, v5.15.14

     from git://git.kernel.org/

  selftests: x86: fix [-Wstringop-overread] warn in test_process_vm_readv()
  tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
  tracing: Tag trace_percpu_buffer as a percpu pointer
  ieee802154: atusb: fix uninit value in atusb_set_extended_addr
  i40e: Fix to not show opcode msg on unsuccessful VF MAC change
  iavf: Fix limit of total number of queues to active queues of VF
  RDMA/core: Don't infoleak GRH fields
  netrom: fix copying in user data in nr_setsockopt
  RDMA/uverbs: Check for null return of kmalloc_array
  mac80211: initialize variable have_higher_than_11mbit
  sfc: The RX page_ring is optional
  i40e: fix use-after-free in i40e_sync_filters_subtask()
  i40e: Fix for displaying message regarding NVM version
  i40e: Fix incorrect netdev's real number of RX/TX queues
  ftrace/samples: Add missing prototypes direct functions
  ipv4: Check attribute length for RTA_GATEWAY in multipath route
  ipv4: Check attribute length for RTA_FLOW in multipath route
  ipv6: Check attribute length for RTA_GATEWAY in multipath route
  ipv6: Check attribute length for RTA_GATEWAY when deleting multipath route
  lwtunnel: Validate RTA_ENCAP_TYPE attribute length
  batman-adv: mcast: don't send link-local multicast to mcast routers
  sch_qfq: prevent shift-out-of-bounds in qfq_init_qdisc
  net: ena: Fix undefined state when tx request id is out of bounds
  net: ena: Fix error handling when calculating max IO queues number
  power: supply: core: Break capacity loop
  power: reset: ltc2952: Fix use of floating point literals
  rndis_host: support Hytera digital radios
  phonet: refcount leak in pep_sock_accep
  power: bq25890: Enable continuous conversion for ADC at charging
  ipv6: Continue processing multipath route even if gateway attribute is invalid
  ipv6: Do cleanup if attribute validation fails in multipath route
  usb: mtu3: fix interval value for intr and isoc
  scsi: libiscsi: Fix UAF in iscsi_conn_get_param()/iscsi_conn_teardown()
  ip6_vti: initialize __ip6_tnl_parm struct in vti6_siocdevprivate
  net: udp: fix alignment problem in udp4_seq_show()
  atlantic: Fix buff_ring OOB in aq_ring_rx_clean
  mISDN: change function names to avoid conflicts
  drm/amd/display: Added power down for DCN10
  ipv6: raw: check passed optlen before reading
  ARM: dts: gpio-ranges property is now required
  Input: zinitix - make sure the IRQ is allocated before it gets enabled
  fscache_cookie_enabled: check cookie is valid before accessing it
  Revert "net: usb: r8152: Add MAC passthrough support for more Lenovo Docks"
  mac80211: mesh: embedd mesh_paths and mpp_paths into ieee80211_if_mesh
  selftests: net: udpgro_fwd.sh: explicitly checking the available ping feature
  sctp: hold endpoint before calling cb in sctp_transport_lookup_process
  net: ena: Fix wrong rx request id by resetting device
  md/raid1: fix missing bitmap update w/o WriteMostly devices
  cgroup: Use open-time credentials for process migraton perm checks
  cgroup: Allocate cgroup_file_ctx for kernfs_open_file->priv
  cgroup: Use open-time cgroup namespace for process migration perm checks
  i2c: mpc: Avoid out of bounds memory access
  net ticp:fix a kernel-infoleak in __tipc_sendmsg()
  fbdev: fbmem: add a helper to determine if an aperture is used by a fw fb
  drm/amdgpu: disable runpm if we are the primary adapter
  auxdisplay: charlcd: checking for pointer reference before dereferencing
  drm/amd/pm: Fix xgmi link control on aldebaran
  drm/amd/pm: skip setting gfx cgpg in the s0ix suspend-resume
  drm/amdgpu: always reset the asic in suspend (v2)
  drm/amdgpu: put SMU into proper state on runpm suspending for BOCO capable 
platform
  userfaultfd/selftests: fix hugetlb area allocations
  UBUNTU: upstream stable to v5.10.91, v5.15.14

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

[Kernel-packages] [Bug 1960609] Re: Missing quota on ext4 on Impish/Oracle arm64 (ubuntu_quota_smoke_test)

** Tags added: arm64

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

Title:
  Missing quota on ext4 on Impish/Oracle arm64 (ubuntu_quota_smoke_test)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  2022.01.31/impish/linux-oracle/5.13.0-1018.22
  VM.Standard.A1.Flex-4c.8m
  test: ubuntu_quota_smoke_test
  --
  401   13:27:26 DEBUG| [stdout] Using block device /dev/loop9 for path 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt
  402   13:27:26 DEBUG| [stdout] PASSED (quotacheck -vucmg)
  403   13:27:26 DEBUG| [stdout] 
  404   13:27:26 ERROR| [stderr] quotaon: Your kernel probably supports 
ext4 quota feature but you are using external quota files. Please switch your 
filesystem to use ext4 quota feature as external quota files on ext4 are 
deprecated.
  405   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.group
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  406   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
  407   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.user
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  408   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
   409  13:27:26 DEBUG| [stdout] FAILED (quotaon -v)
  --

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


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

[Kernel-packages] [Bug 1959134] Re: Impish update: upstream stable patchset 2022-01-26

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

Title:
  Impish update: upstream stable patchset 2022-01-26

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 2022-01-26

  Ported from the following upstream stable releases:
  v5.10.90, v5.15.13

     from git://git.kernel.org/

  Input: i8042 - add deferred probe support
  Input: i8042 - enable deferred probe quirk for ASUS UM325UA
  tomoyo: Check exceeded quota early in tomoyo_domain_quota_is_ok().
  tomoyo: use hwight16() in tomoyo_domain_quota_is_ok()
  parisc: Clear stale IIR value on instruction access rights trap
  platform/x86: apple-gmux: use resource_size() with res
  memblock: fix memblock_phys_alloc() section mismatch error
  recordmcount.pl: fix typo in s390 mcount regex
  selinux: initialize proto variable in selinux_ip_postroute_compat()
  scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write()
  net/mlx5: DR, Fix NULL vs IS_ERR checking in dr_domain_init_resources
  net/mlx5e: Wrap the tx reporter dump callback to extract the sq
  net/mlx5e: Fix interoperability between XSK and ICOSQ recovery flow
  net/mlx5e: Fix ICOSQ recovery flow for XSK
  udp: using datalen to cap ipv6 udp max gso segments
  selftests: Calculate udpgso segment count without header adjustment
  sctp: use call_rcu to free endpoint
  net/smc: fix using of uninitialized completions
  net: usb: pegasus: Do not drop long Ethernet frames
  net: ag71xx: Fix a potential double free in error handling paths
  net: lantiq_xrx200: fix statistics of received bytes
  NFC: st21nfca: Fix memory leak in device probe and remove
  net/smc: don't send CDC/LLC message if link not ready
  net/smc: fix kernel panic caused by race of smc_sock
  igc: Fix TX timestamp support for non-MSI-X platforms
  ionic: Initialize the 'lif->dbid_inuse' bitmap
  net/mlx5e: Fix wrong features assignment in case of error
  selftests/net: udpgso_bench_tx: fix dst ip argument
  net/ncsi: check for error return from call to nla_put_u32
  fsl/fman: Fix missing put_device() call in fman_port_probe
  i2c: validate user data in compat ioctl
  nfc: uapi: use kernel size_t to fix user-space builds
  uapi: fix linux/nfc.h userspace compilation errors
  drm/amdgpu: When the VCN(1.0) block is suspended, powergating is explicitly 
enabled
  drm/amdgpu: add support for IP discovery gc_info table v2
  xhci: Fresco FL1100 controller should not have BROKEN_MSI quirk set.
  usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.
  usb: mtu3: add memory barrier before set GPD's HWO
  usb: mtu3: fix list_head check warning
  usb: mtu3: set interval of FS intr and isoc endpoint
  binder: fix async_free_space accounting for empty parcels
  scsi: vmw_pvscsi: Set residual data length conditionally
  Input: appletouch - initialize work before device registration
  Input: spaceball - fix parsing of movement data packets
  net: fix use-after-free in tw_timer_handler
  perf script: Fix CPU filtering of a script's switch events
  net/sched: Extend qdisc control block with tc control block
  platform/mellanox: mlxbf-pmc: Fix an IS_ERR() vs NULL bug in 
mlxbf_pmc_map_counters
  net/mlx5: Fix SF health recovery flow
  net/mlx5: Fix tc max supported prio for nic mode
  selftests: net: Fix a typo in udpgro_fwd.sh
  selftests: net: using ping6 for IPv6 in udpgro_fwd.sh
  fs/mount_setattr: always cleanup mount_kattr
  UBUNTU: upstream stable to v5.10.90, v5.15.13

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


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

[Kernel-packages] [Bug 1958287] Re: Impish update: upstream stable patchset 2022-01-18

Skipped (already applied):
- net/sched: sch_ets: don't remove idle classes from the round-robin list
- net/packet: rx_owner_map depends on pg_vec

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

Title:
  Impish update: upstream stable patchset 2022-01-18

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 2022-01-18

  Ported from the following upstream stable releases:
  v5.10.86, v5.15.9
  v5.10.87, v5.15.10
  v5.10.88, v5.15.11

     from git://git.kernel.org/

  netfilter: selftest: conntrack_vrf.sh: fix file permission
  UBUNTU: upstream stable to v5.10.86, v5.15.9
  nfc: fix segfault in nfc_genl_dump_devices_done
  drm/msm/dsi: set default num_data_lanes
  KVM: arm64: Save PSTATE early on exit
  s390/test_unwind: use raw opcode instead of invalid instruction
  Revert "tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP"
  net/mlx4_en: Update reported link modes for 1/10G
  ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid
  ALSA: hda/hdmi: fix HDA codec entry table order for ADL-P
  parisc/agp: Annotate parisc agp init functions with __init
  i2c: rk3x: Handle a spurious start completion interrupt flag
  net: netlink: af_netlink: Prevent empty skb by adding a check on len.
  drm/amd/display: Fix for the no Audio bug with Tiled Displays
  drm/amd/display: add connector type check for CRC source set
  tracing: Fix a kmemleak false positive in tracing_map
  staging: most: dim2: use device release method
  fuse: make sure reclaim doesn't write the inode
  hwmon: (dell-smm) Fix warning on /proc/i8k creation error
  ethtool: do not perform operations on net devices being unregistered
  perf inject: Fix itrace space allowed for new attributes
  memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER
  memblock: align freed memory map on pageblock boundaries with SPARSEMEM
  memblock: ensure there is no overflow in memblock_overlaps_region()
  arm: extend pfn_valid to take into account freed memory map alignment
  arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
  hwmon: (corsair-psu) fix plain integer used as NULL pointer
  perf bpf_skel: Do not use typedef to avoid error on old clang
  netfs: Fix lockdep warning from taking sb_writers whilst holding mmap_lock
  ice: fix FDIR init missing when reset VF
  drm/msm/dp: Avoid unpowered AUX xfers that caused crashes
  UBUNTU: upstream stable to v5.10.87, v5.15.10
  KVM: selftests: Make sure kvm_create_max_vcpus test won't hit RLIMIT_NOFILE
  KVM: downgrade two BUG_ONs to WARN_ON_ONCE
  mac80211: fix regression in SSN handling of addba tx
  mac80211: mark TX-during-stop for TX in in_reconfig
  mac80211: send ADDBA requests using the tid/queue of the aggregation session
  mac80211: validate extended element ID is present
  firmware: arm_scpi: Fix string overflow in SCPI genpd driver
  bpf: Fix signed bounds propagation after mov32
  bpf: Make 32->64 bounds propagation slightly more robust
  bpf, selftests: Add test case trying to taint map value pointer
  virtio_ring: Fix querying of maximum DMA mapping size for virtio device
  vdpa: check that offsets are within bounds
  recordmcount.pl: look for jgnop instruction as well as bcrl on s390
  dm btree remove: fix use after free in rebalance_children()
  audit: improve robustness of the audit queue handling
  arm64: dts: rockchip: remove mmc-hs400-enhanced-strobe from rk3399-khadas-edge
  arm64: dts: rockchip: fix rk3308-roc-cc vcc-sd supply
  arm64: dts: rockchip: fix rk3399-leez-p710 vcc3v3-lan supply
  arm64: dts: rockchip: fix audio-supply for Rock Pi 4
  mac80211: track only QoS data frames for admission control
  tee: amdtee: fix an IS_ERR() vs NULL bug
  ceph: fix duplicate increment of opened_inodes metric
  ceph: initialize pathlen variable in reconnect_caps_cb
  ARM: socfpga: dts: fix qspi node compatible
  clk: Don't parent clks until the parent is fully registered
  soc: imx: Register SoC device only on i.MX boards
  virtio/vsock: fix the transport to work with VMADDR_CID_ANY
  selftests: net: Correct ping6 expected rc from 2 to 1
  s390/kexec_file: fix error handling when applying relocations
  sch_cake: do not call

[Kernel-packages] [Bug 1958672] Re: Impish update: upstream stable patchset 2022-01-21

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

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

Title:
  Impish update: upstream stable patchset 2022-01-21

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 2022-01-21

  Ported from the following upstream stable releases:
  v5.10.89, v5.15.12

     from git://git.kernel.org/

  arm64: vdso32: require CROSS_COMPILE_COMPAT for gcc+bfd
  net: usb: lan78xx: add Allied Telesis AT29M2-AF
  ext4: prevent partial update of the extent blocks
  ext4: check for out-of-order index extents in ext4_valid_extent_entries()
  ext4: check for inconsistent extents between index and leaf block
  HID: holtek: fix mouse probing
  HID: potential dereference of null pointer
  arm64: dts: allwinner: orangepi-zero-plus: fix PHY mode
  spi: change clk_disable_unprepare to clk_unprepare
  ASoC: meson: aiu: fifo: Add missing dma_coerce_mask_and_coherent()
  IB/qib: Fix memory leak in qib_user_sdma_queue_pkts()
  RDMA/hns: Replace kfree() with kvfree()
  netfilter: fix regression in looped (broad|multi)cast's MAC handling
  ARM: dts: imx6qdl-wandboard: Fix Ethernet support
  net: marvell: prestera: fix incorrect return of port_find
  qlcnic: potential dereference null pointer of rx_queue->page_ring
  net: accept UFOv6 packages in virtio_net_hdr_to_skb
  net: skip virtio_net_hdr_set_proto if protocol already set
  igb: fix deadlock caused by taking RTNL in RPM resume path
  ipmi: Fix UAF when uninstall ipmi_si and ipmi_msghandler module
  bonding: fix ad_actor_system option setting to default
  fjes: Check for error irq
  drivers: net: smc911x: Check for error irq
  net: ks8851: Check for error irq
  sfc: Check null pointer of rx_queue->page_ring
  sfc: falcon: Check null pointer of rx_queue->page_ring
  pinctrl: bcm2835: Change init order for gpio hogs
  hwmon: (lm90) Fix usage of CONFIG2 register in detect function
  hwmon: (lm90) Add basic support for TI TMP461
  hwmon: (lm90) Introduce flag indicating extended temperature support
  hwmon: (lm90) Drop critical attribute support for MAX6654
  ALSA: jack: Check the return value of kstrdup()
  ALSA: drivers: opl3: Fix incorrect use of vp->state
  ALSA: hda/realtek: Amp init fixup for HP ZBook 15 G6
  ALSA: hda/realtek: Add new alc285-hp-amp-init model
  ALSA: hda/realtek: Fix quirk for Clevo NJ51CU
  ASoC: meson: aiu: Move AIU_I2S_MISC hold setting to aiu-fifo-i2s
  Input: atmel_mxt_ts - fix double free in mxt_read_info_block
  ipmi: bail out if init_srcu_struct fails
  ipmi: ssif: initialize ssif_info->client early
  ipmi: fix initialization when workqueue allocation fails
  parisc: Correct completer in lws start
  parisc: Fix mask used to select futex spinlock
  tee: handle lookup of shm with reference count 0
  x86/pkey: Fix undefined behaviour with PKRU_WD_BIT
  platform/x86: intel_pmc_core: fix memleak on registration failure
  KVM: VMX: Wake vCPU when delivering posted IRQ even if vCPU == this vCPU
  pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines
  gpio: dln2: Fix interrupts when replugging the device
  mmc: sdhci-tegra: Fix switch to HS400ES mode
  mmc: meson-mx-sdhc: Set MANUAL_STOP for multi-block SDIO commands
  mmc: core: Disable card detect during shutdown
  mmc: mmci: stm32: clear DLYB_CR after sending tuning command
  ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling
  mac80211: fix locking in ieee80211_start_ap error path
  mm/hwpoison: clear MF_COUNT_INCREASED before retrying get_any_page()
  tee: optee: Fix incorrect page free bug
  f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr()
  usb: gadget: u_ether: fix race in setting MAC address in setup phase
  KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state
  mm: mempolicy: fix THP allocations escaping mempolicy restrictions
  Input: elants_i2c - do not check Remark ID on eKTH3900/eKTH5312
  Input: goodix - add id->model mapping for the "9111" model
  ASoC: tas2770: Fix setting of high sample rates
  ASoC: rt5682: fix the wrong jack type detected
  pinctrl: mediatek: fix global-out-of-bounds issue
  hwmom: (lm90) Fix citical alarm status for MAX6680/MAX6681
  hwmon: (lm90) Do not report

[Kernel-packages] [Bug 1957832] Re: Impish update: upstream stable patchset 2022-01-13

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

Title:
  Impish update: upstream stable patchset 2022-01-13

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 2022-01-13

  Ported from the following upstream stable releases:
  v5.10.85, v5.15.8

     from git://git.kernel.org/

  usb: gadget: uvc: fix multiple opens
  HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
  HID: google: add eel USB id
  HID: add hid_is_usb() function to make it simpler for USB detection
  HID: add USB_HID dependancy to hid-prodikeys
  HID: add USB_HID dependancy to hid-chicony
  HID: add USB_HID dependancy on some USB HID drivers
  HID: bigbenff: prevent null pointer dereference
  HID: wacom: fix problems when device is not a valid USB device
  HID: check for valid USB device for many HID drivers
  nft_set_pipapo: Fix bucket load in AVX2 lookup routine for six 8-bit groups
  IB/hfi1: Insure use of smp_processor_id() is preempt disabled
  IB/hfi1: Fix early init panic
  IB/hfi1: Fix leak of rcvhdrtail_dummy_kvaddr
  can: kvaser_usb: get CAN clock frequency from device
  can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct 
stats->{rx,tx}_errors counter
  can: sja1000: fix use after free in ems_pcmcia_add_card()
  x86/sme: Explicitly map new EFI memmap table as encrypted
  nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
  selftests: netfilter: add a vrf+conntrack testcase
  vrf: don't run conntrack on vrf with !dflt qdisc
  bpf, x86: Fix "no previous prototype" warning
  bpf: Fix the off-by-two error in range markings
  ice: ignore dropped packets during init
  bonding: make tx_rebalance_counter an atomic
  nfp: Fix memory leak in nfp_cpp_area_cache_add()
  seg6: fix the iif in the IPv6 socket control block
  udp: using datalen to cap max gso segments
  netfilter: conntrack: annotate data-races around ct->timeout
  iavf: restore MSI state on reset
  iavf: Fix reporting when setting descriptor count
  IB/hfi1: Correct guard on eager buffer deallocation
  devlink: fix netns refcount leak in devlink_nl_cmd_reload()
  net/sched: fq_pie: prevent dismantle issue
  KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush 
hypercall
  mm: bdi: initialize bdi_min_ratio when bdi is unregistered
  ALSA: ctl: Fix copy of updated id with element read/write
  ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
  ALSA: hda/realtek: Fix quirk for TongFang PHxTxX1
  ALSA: pcm: oss: Fix negative period/buffer sizes
  ALSA: pcm: oss: Limit the period size to 16MB
  ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
  scsi: qla2xxx: Format log strings only if needed
  btrfs: clear extent buffer uptodate when we fail to write it
  btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
  md: fix update super 1.0 on rdev size change
  nfsd: fix use-after-free due to delegation race
  nfsd: Fix nsfd startup race (again)
  tracefs: Have new files inherit the ownership of their parent
  mmc: renesas_sdhi: initialize variable properly when tuning
  clk: qcom: regmap-mux: fix parent clock lookup
  drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
  can: pch_can: pch_can_rx_normal: fix use after free
  can: m_can: Disable and ignore ELO interrupt
  libata: add horkage for ASMedia 1092
  wait: add wake_up_pollfree()
  UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
  binder: use wake_up_pollfree()
  signalfd: use wake_up_pollfree()
  aio: keep poll requests on waitqueue until completed
  aio: fix use-after-free due to missing POLLFREE handling
  net: mvpp2: fix XDP rx queues registering
  tracefs: Set all files to the same group ownership as the mount option
  block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
  scsi: pm80xx: Do not call scsi_remove_host() in pm8001_alloc()
  scsi: scsi_debug: Fix buffer size of REPORT ZONES command
  qede: validate non LSO skb length
  PM: runtime: Fix pm_runtime_active() kerneldoc comment
  ASoC: rt5682: Fix crash due to out of scope stack vars
  ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
  ASoC: codecs: wsa881x: fix return values from kcontrol

[Kernel-packages] [Bug 1960448] Re: Sony WF-XB700 Bluetooth headset not detected

2022-02-11 Thread Ilia Kichev

No, the device is not one of the listed ones. Here are the requested
files. Sorry for the delay.

** Attachment added: "files.zip"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+attachment/5560391/+files/files.zip

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

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)

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


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

[Kernel-packages] [Bug 1956791] Re: Impish update: upstream stable patchset 2022-01-07

Skipped (already applied):
- fget: check that the fd still exists after getting a ref to it
- net/smc: Keep smc_close_final rc during active close

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

Title:
  Impish update: upstream stable patchset 2022-01-07

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 2022-01-07

  Ported from the following upstream stable releases:
  v5.10.84, v5.15.7

     from git://git.kernel.org/

  can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM
  gfs2: release iopen glock early in evict
  gfs2: Fix length of holes reported at end-of-file
  powerpc/pseries/ddw: Revert "Extend upper limit for huge DMA window for 
persistent memory"
  drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY
  mac80211: do not access the IV when it was stripped
  net/smc: Transfer remaining wait queue entries during fallback
  atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait
  net: return correct error code
  platform/x86: thinkpad_acpi: Add support for dual fan control
  platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep
  s390/setup: avoid using memblock_enforce_memory_limit
  btrfs: check-integrity: fix a warning on write caching disabled disk
  thermal: core: Reset previous low and high trip during thermal zone init
  scsi: iscsi: Unblock session then wake up error handler
  drm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
  drm/amd/amdgpu: fix potential memleak
  ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile
  ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in 
hns_dsaf_ge_srst_by_port()
  ipv6: check return value of ipv6_skip_exthdr
  net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of 
bound
  net: ethernet: dec: tulip: de4x5: fix possible array overflows in 
type3_infoblock()
  perf inject: Fix ARM SPE handling
  perf hist: Fix memory leak of a perf_hpp_fmt
  perf report: Fix memory leaks around perf_tip()
  net/smc: Avoid warning of possible recursive locking
  ACPI: Add stubs for wakeup handler functions
  vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit
  kprobes: Limit max data_size of the kretprobe instances
  rt2x00: do not mark device gone on EPROTO errors during start
  cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink()
  s390/pci: move pseudo-MMIO to prevent MIO overlap
  fget: check that the fd still exists after getting a ref to it
  sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl
  sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl
  ipv6: fix memory leak in fib6_rule_suppress
  drm/amd/display: Allow DSC on supported MST branch devices
  KVM: Disallow user memslot with size that exceeds "unsigned long"
  KVM: nVMX: Flush current VPID (L1 vs. L2) for KVM_REQ_TLB_FLUSH_GUEST
  KVM: x86: Use a stable condition around all VT-d PI paths
  KVM: arm64: Avoid setting the upper 32 bits of TCR_EL2 and CPTR_EL2 to 1
  KVM: X86: Use vcpu->arch.walk_mmu for kvm_mmu_invlpg()
  tracing/histograms: String compares should not care about signed values
  wireguard: selftests: increase default dmesg log size
  wireguard: allowedips: add missing __rcu annotation to satisfy sparse
  wireguard: selftests: actually test for routing loops
  wireguard: selftests: rename DEBUG_PI_LIST to DEBUG_PLIST
  wireguard: device: reset peer src endpoint when netns exits
  wireguard: receive: use ring buffer for incoming handshakes
  wireguard: receive: drop handshakes if queue lock is contended
  wireguard: ratelimiter: use kvcalloc() instead of kvzalloc()
  i2c: stm32f7: flush TX FIFO upon transfer errors
  i2c: stm32f7: recover the bus on access timeout
  i2c: stm32f7: stop dma transfer in case of NACK
  i2c: cbus-gpio: set atomic transfer callback
  natsemi: xtensa: fix section mismatch warnings
  tcp: fix page frag corruption on page fault
  net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings()
  net: mpls: Fix notifications when deleting a device
  siphash: use _unaligned version by default
  arm64: ftrace: add missing BTIs
  net/mlx4_en: Fix an use-after-free bug in

[Kernel-packages] [Bug 1960621] [NEW] Nvidia 510 drivers result in failure to start GUI on GeForce GTX 1050 Ti

2022-02-11 Thread Ian

Public bug reported:

I have been using nvidia-graphics-drivers-470 for a while. In January, I
tried the 495 drivers, but this resulted in failing to start the GUI
when booting: the mouse cursor would appear, but then the screen would
clear and the switch to graphics would be attempted again. This would
repeat until restarted, so I used recovery mode to test that a) it still
happened with that (yes) and b) to go back to the 470 drivers via the
root terminal.

For some reason, yesterday xscreensaver had a problem getting the right
GLcontext. I noticed that the 510 drivers were available, so used
Software & Updates's Additional Drivers to install those.

Exactly the same issue as with the 495 drivers: the mouse cursor appears
for a second, then disappears, and reappears, and.. until I reboot and
go back to 470.

I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card.

$ lsb_release -rd
Description:Ubuntu 21.10
Release:21.10

** Affects: nvidia-graphics-drivers-510 (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-510 in Ubuntu.
https://bugs.launchpad.net/bugs/1960621

Title:
Nvidia 510 drivers result in failure to start GUI on GeForce GTX 1050
Ti

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

Bug description:
I have been using nvidia-graphics-drivers-470 for a while. In January,
I tried the 495 drivers, but this resulted in failing to start the GUI
when booting: the mouse cursor would appear, but then the screen would
clear and the switch to graphics would be attempted again. This would
repeat until restarted, so I used recovery mode to test that a) it
still happened with that (yes) and b) to go back to the 470 drivers
via the root terminal.

For some reason, yesterday xscreensaver had a problem getting the
right GLcontext. I noticed that the 510 drivers were available, so
used Software & Updates's Additional Drivers to install those.

Exactly the same issue as with the 495 drivers: the mouse cursor
appears for a second, then disappears, and reappears, and.. until I
reboot and go back to 470.

I am using Ubuntu MATE 21.10 with a GeForce GTX 1050 Ti card.

$ lsb_release -rd
Description: Ubuntu 21.10
Release: 21.10

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

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

[Kernel-packages] [Bug 1959709] Re: Bionic update: upstream stable patchset 2022-02-01

2022-02-11 Thread Kleber Sacilotto de Souza

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

Title:
  Bionic update: upstream stable patchset 2022-02-01

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 2022-02-01

  Ported from the following upstream stable releases:
  v4.14.262, v4.19.225

     from git://git.kernel.org/

  tracing: Fix check for trace_percpu_buffer validity in get_trace_buf()
  tracing: Tag trace_percpu_buffer as a percpu pointer
  virtio_pci: Support surprise removal of virtio pci device
  ieee802154: atusb: fix uninit value in atusb_set_extended_addr
  RDMA/core: Don't infoleak GRH fields
  mac80211: initialize variable have_higher_than_11mbit
  i40e: fix use-after-free in i40e_sync_filters_subtask()
  i40e: Fix incorrect netdev's real number of RX/TX queues
  ipv6: Check attribute length for RTA_GATEWAY in multipath route
  ipv6: Check attribute length for RTA_GATEWAY when deleting multipath route
  sch_qfq: prevent shift-out-of-bounds in qfq_init_qdisc
  power: reset: ltc2952: Fix use of floating point literals
  rndis_host: support Hytera digital radios
  phonet: refcount leak in pep_sock_accep
  ipv6: Continue processing multipath route even if gateway attribute is invalid
  ipv6: Do cleanup if attribute validation fails in multipath route
  scsi: libiscsi: Fix UAF in iscsi_conn_get_param()/iscsi_conn_teardown()
  ip6_vti: initialize __ip6_tnl_parm struct in vti6_siocdevprivate
  net: udp: fix alignment problem in udp4_seq_show()
  mISDN: change function names to avoid conflicts
  usb: mtu3: fix interval value for intr and isoc
  UBUNTU: upstream stable to v4.14.262, v4.19.225

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


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

[Kernel-packages] [Bug 1959335] Re: Bionic update: upstream stable patchset 2022-01-27

2022-02-11 Thread Kleber Sacilotto de Souza

Skipped patch 358926f3c499 "recordmcount.pl: fix typo in s390 mcount
regex"  as it has already been applied for Ubuntu-4.15.0-169.177.

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

Title:
  Bionic update: upstream stable patchset 2022-01-27

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  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 2022-01-27

  Ported from the following upstream stable releases:
  v4.14.261, v4.19.224

     from git://git.kernel.org/

  HID: asus: Add depends on USB_HID to HID_ASUS Kconfig option
  tee: handle lookup of shm with reference count 0
  platform/x86: apple-gmux: use resource_size() with res
  recordmcount.pl: fix typo in s390 mcount regex
  selinux: initialize proto variable in selinux_ip_postroute_compat()
  scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write()
  net: usb: pegasus: Do not drop long Ethernet frames
  NFC: st21nfca: Fix memory leak in device probe and remove
  fsl/fman: Fix missing put_device() call in fman_port_probe
  nfc: uapi: use kernel size_t to fix user-space builds
  uapi: fix linux/nfc.h userspace compilation errors
  xhci: Fresco FL1100 controller should not have BROKEN_MSI quirk set.
  usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.
  binder: fix async_free_space accounting for empty parcels
  scsi: vmw_pvscsi: Set residual data length conditionally
  Input: appletouch - initialize work before device registration
  Input: spaceball - fix parsing of movement data packets
  net: fix use-after-free in tw_timer_handler
  sctp: use call_rcu to free endpoint
  Input: i8042 - add deferred probe support
  Input: i8042 - enable deferred probe quirk for ASUS UM325UA
  i2c: validate user data in compat ioctl
  usb: mtu3: set interval of FS intr and isoc endpoint
  UBUNTU: upstream stable to v4.14.261, v4.19.224

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


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

[Kernel-packages] [Bug 1960579] 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 1960579

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

Title:
  PL2303 Driver Bug in 5.13 Kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Looks like 5.13.0 kernel broke something in the USB-serial PL2303
  driver module.  I have a Sky-Watcher EQ6-R Pro telescope mount with a
  PL23D3 USB-serial chip (I think).  My MSECORE mini PC running Ubuntu
  20.04.3 has been working with this mount for the last couple of years
  with the 5.11 kernel.  Now with the 5.13 kernel, the pl2303 module
  doesn't recognize the USB-serial device.  I revert back to the 5.11
  kernel and it works fine again.  Here's the snippets from dmesg:

  5.13.0-28-generic kernel:
  [ 2.894277] usbcore: registered new interface driver usbserial_generic
  [ 2.894292] usbserial: USB Serial support registered for generic
  [ 2.907539] usbcore: registered new interface driver pl2303
  [ 2.907574] usbserial: USB Serial support registered for pl2303
  [ 2.907596] pl2303 1-6:1.0: pl2303 converter detected
  [ 2.907602] pl2303 1-6:1.0: unknown device type, please report to 
linux-...@vger.kernel.org 

  5.11.0-27-generic kernel
  [ 3.201216] usbcore: registered new interface driver pl2303
  [ 3.201228] usbserial: USB Serial support registered for pl2303
  [ 3.201243] pl2303 1-5:1.0: pl2303 converter detected
  [ 3.201349] usb 1-5: pl2303 converter now attached to ttyUSB1

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


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

[Kernel-packages] [Bug 1960579] Re: PL2303 Driver Bug in 5.13 Kernel

2022-02-11 Thread Paul White 

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

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

Title:
  PL2303 Driver Bug in 5.13 Kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Looks like 5.13.0 kernel broke something in the USB-serial PL2303
  driver module.  I have a Sky-Watcher EQ6-R Pro telescope mount with a
  PL23D3 USB-serial chip (I think).  My MSECORE mini PC running Ubuntu
  20.04.3 has been working with this mount for the last couple of years
  with the 5.11 kernel.  Now with the 5.13 kernel, the pl2303 module
  doesn't recognize the USB-serial device.  I revert back to the 5.11
  kernel and it works fine again.  Here's the snippets from dmesg:

  5.13.0-28-generic kernel:
  [ 2.894277] usbcore: registered new interface driver usbserial_generic
  [ 2.894292] usbserial: USB Serial support registered for generic
  [ 2.907539] usbcore: registered new interface driver pl2303
  [ 2.907574] usbserial: USB Serial support registered for pl2303
  [ 2.907596] pl2303 1-6:1.0: pl2303 converter detected
  [ 2.907602] pl2303 1-6:1.0: unknown device type, please report to 
linux-...@vger.kernel.org 

  5.11.0-27-generic kernel
  [ 3.201216] usbcore: registered new interface driver pl2303
  [ 3.201228] usbserial: USB Serial support registered for pl2303
  [ 3.201243] pl2303 1-5:1.0: pl2303 converter detected
  [ 3.201349] usb 1-5: pl2303 converter now attached to ttyUSB1

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


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

[Kernel-packages] [Bug 1960579] [NEW] PL2303 Driver Bug in 5.13 Kernel

You have been subscribed to a public bug:

Looks like 5.13.0 kernel broke something in the USB-serial PL2303 driver
module.  I have a Sky-Watcher EQ6-R Pro telescope mount with a PL23D3
USB-serial chip (I think).  My MSECORE mini PC running Ubuntu 20.04.3
has been working with this mount for the last couple of years with the
5.11 kernel.  Now with the 5.13 kernel, the pl2303 module doesn't
recognize the USB-serial device.  I revert back to the 5.11 kernel and
it works fine again.  Here's the snippets from dmesg:

5.13.0-28-generic kernel:
[ 2.894277] usbcore: registered new interface driver usbserial_generic
[ 2.894292] usbserial: USB Serial support registered for generic
[ 2.907539] usbcore: registered new interface driver pl2303
[ 2.907574] usbserial: USB Serial support registered for pl2303
[ 2.907596] pl2303 1-6:1.0: pl2303 converter detected
[ 2.907602] pl2303 1-6:1.0: unknown device type, please report to 
linux-...@vger.kernel.org 

5.11.0-27-generic kernel
[ 3.201216] usbcore: registered new interface driver pl2303
[ 3.201228] usbserial: USB Serial support registered for pl2303
[ 3.201243] pl2303 1-5:1.0: pl2303 converter detected
[ 3.201349] usb 1-5: pl2303 converter now attached to ttyUSB1

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


** Tags: 5.13.0 bot-comment eq6-r pl2303 pl23d3
-- 
PL2303 Driver Bug in 5.13 Kernel
https://bugs.launchpad.net/bugs/1960579
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1960609] Re: Missing quota on ext4 on Impish/Oracle arm64 (ubuntu_quota_smoke_test)

Seems ubuntu_ltp_syscalls quotactl06 fails for the same reason:
---
59907   quotactl06.c:165: TINFO: quotactl() with vfsv0 format
59908   quotactl06.c:174: TCONF: Kernel or device does not support FS 
quotas
59909   quotactl06.c:192: TWARN: rmdir(mntpoint/testdir1) failed: 
ENOENT (2)
59910   tst_test.c:1423: TINFO: Timeout per run is 0h 05m 00s
59911   quotactl06.c:165: TINFO: quotactl() with vfsv1 format
59912   quotactl06.c:174: TCONF: Kernel or device does not support FS 
quotas
59913   quotactl06.c:192: TWARN: rmdir(mntpoint/testdir1) failed: 
ENOENT (2)
---

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

Title:
  Missing quota on ext4 on Impish/Oracle arm64 (ubuntu_quota_smoke_test)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  2022.01.31/impish/linux-oracle/5.13.0-1018.22
  VM.Standard.A1.Flex-4c.8m
  test: ubuntu_quota_smoke_test
  --
  401   13:27:26 DEBUG| [stdout] Using block device /dev/loop9 for path 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt
  402   13:27:26 DEBUG| [stdout] PASSED (quotacheck -vucmg)
  403   13:27:26 DEBUG| [stdout] 
  404   13:27:26 ERROR| [stderr] quotaon: Your kernel probably supports 
ext4 quota feature but you are using external quota files. Please switch your 
filesystem to use ext4 quota feature as external quota files on ext4 are 
deprecated.
  405   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.group
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  406   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
  407   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.user
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  408   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
   409  13:27:26 DEBUG| [stdout] FAILED (quotaon -v)
  --

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


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

[Kernel-packages] [Bug 1960609] 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 1960609

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

Title:
  Missing quota on ext4 on Impish/Oracle arm64 (ubuntu_quota_smoke_test)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  2022.01.31/impish/linux-oracle/5.13.0-1018.22
  VM.Standard.A1.Flex-4c.8m
  test: ubuntu_quota_smoke_test
  --
  401   13:27:26 DEBUG| [stdout] Using block device /dev/loop9 for path 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt
  402   13:27:26 DEBUG| [stdout] PASSED (quotacheck -vucmg)
  403   13:27:26 DEBUG| [stdout] 
  404   13:27:26 ERROR| [stderr] quotaon: Your kernel probably supports 
ext4 quota feature but you are using external quota files. Please switch your 
filesystem to use ext4 quota feature as external quota files on ext4 are 
deprecated.
  405   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.group
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  406   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
  407   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.user
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  408   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
   409  13:27:26 DEBUG| [stdout] FAILED (quotaon -v)
  --

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


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

[Kernel-packages] [Bug 1960609] [NEW] Missing quota on ext4 on Impish/Oracle arm64 (ubuntu_quota_smoke_test)

Public bug reported:

2022.01.31/impish/linux-oracle/5.13.0-1018.22
VM.Standard.A1.Flex-4c.8m
test: ubuntu_quota_smoke_test
--
401 13:27:26 DEBUG| [stdout] Using block device /dev/loop9 for path 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt
402 13:27:26 DEBUG| [stdout] PASSED (quotacheck -vucmg)
403 13:27:26 DEBUG| [stdout] 
404 13:27:26 ERROR| [stderr] quotaon: Your kernel probably supports 
ext4 quota feature but you are using external quota files. Please switch your 
filesystem to use ext4 quota feature as external quota files on ext4 are 
deprecated.
405 13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.group
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
406 13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
407 13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.user
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
408 13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
 40913:27:26 DEBUG| [stdout] FAILED (quotaon -v)
--

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: 5.13 impish oracle sru-20220131

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: 5.13 impish oracle sru-20220131

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

Title:
  Missing quota on ext4 on Impish/Oracle arm64 (ubuntu_quota_smoke_test)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  2022.01.31/impish/linux-oracle/5.13.0-1018.22
  VM.Standard.A1.Flex-4c.8m
  test: ubuntu_quota_smoke_test
  --
  401   13:27:26 DEBUG| [stdout] Using block device /dev/loop9 for path 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt
  402   13:27:26 DEBUG| [stdout] PASSED (quotacheck -vucmg)
  403   13:27:26 DEBUG| [stdout] 
  404   13:27:26 ERROR| [stderr] quotaon: Your kernel probably supports 
ext4 quota feature but you are using external quota files. Please switch your 
filesystem to use ext4 quota feature as external quota files on ext4 are 
deprecated.
  405   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.group
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  406   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
  407   13:27:26 ERROR| [stderr] quotaon: using 
/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt/aquota.user
 on /dev/loop9 
[/home/ubuntu/autotest/client/results/default/ubuntu_quota_smoke_test.quota-smoke-test/mnt]:
 No such process
  408   13:27:26 ERROR| [stderr] quotaon: Quota format not supported in 
kernel.
   409  13:27:26 DEBUG| [stdout] FAILED (quotaon -v)
  --

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


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

[Kernel-packages] [Bug 1960575] Re: Pass originating device to drivers offloading ct connection so devices will filter the tuples and offload them more efficiently

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

** Changed in: linux-bluefield (Ubuntu Focal)
   Importance: Undecided => Medium

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

** Changed in: linux-bluefield (Ubuntu Focal)
 Assignee: (unassigned) => Bodong Wang (bodong-wang)

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

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

Title:
  Pass originating device to drivers offloading ct connection so devices
  will filter the tuples and offload them more efficiently

Status in linux-bluefield package in Ubuntu:
  Invalid
Status in linux-bluefield source package in Focal:
  In Progress

Bug description:
  * Explain the feature
   
  Currently, drivers register to a ct zone that can be shared by multiple
  devices. This can be inefficient for the driver to offload, as it
  needs to handle all the cases where the tuple can come from,
  instead of where it's most likely will arive from.

  For example, consider the following tc rules:
  tc filter add dev dev1 ... flower action ct commit zone 5 \
 action mirred egress redirect dev dev2

  tc filter add dev dev2 ... flower action ct zone 5 \
 action goto chain chain 2
  tc filter add dev dev2 ... flower ct_state +trk+est ... \
 action mirred egress redirect dev dev1

  Both dev2 and dev1 register to the zone 5 flow table (created
  by act_ct). A tuple originating on dev1, going to dev2, will
  be offloaded to both devices, and both will need to offload
  both directions, resulting in 4 total rules. The traffic
  will only hit originiating tuple on dev1, and reply tuple
  on dev2.

  By passing the originating device that created the connection
  with the tuple, dev1 can choose to offload only the originating
  tuple, and dev2 only the reply tuple. Resulting in a more
  efficient offload.

  The first patch adds an act_ct nf conntrack extension, to
  temporarily store the originiating device from the skb before
  offloading the connection once the connection is established.
  Once sent to offload, it fills the tuple originating device.

  The second patch get this information from tuples
  which pass in openvswitch.

  The third patch is Mellanox driver ct offload implementation using
  this information to provide a hint to firmware of where this
  offloaded tuple packets will arrive from (LOCAL or UPLINK port),
  and thus increase insertion rate.

   
  * How to test
   
  Create OVS bridge with 2 devices mlx5 rep devices.
  Enable HW offload and configure regular connection tracking OpenFlow rules:

  e.g:
  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"

  With SW steering enabled and the above commits (and up to date ofed) tuple 
insertion rate should be about
  twice as fast. This can be seen via procfs hw offloaded count while running 
high traffic:
  while true; do res=`sudo cat /proc/net/nf_conntrack | grep -i offload` && 
echo "$res" && echo "$res" | wc -l; done

  * What it could break.
   
  NA

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


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

[Kernel-packages] [Bug 1837037] Re: memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp

2022.01.31/bionic/linux-ibm-gt-5.4/5.4.0-1009.11
(as expected since this happens on B/hwe-5.4)
memcg_move_charge_at_immigrate_test 2 TFAIL: cache is 135168, 270336 expected


** Tags added: sru-20220131

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

Title:
  memcg_move_charge_at_immigrate_test from controllers in ubuntu_ltp

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Won't Fix

Bug description:
  Similar to bug 1837035

  This memcg_move_charge_at_immigrate_test test failed on an i386 node
  "pepe" with Disco kernel.

  It failed with:
  memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with
  1 after warm up

  <<>>
  tag=memcg_move_charge_at_immigrate stime=1563448078
  cmdline="memcg_move_charge_at_immigrate_test.sh"
  contacts=""
  analysis=exit
  <<>>
  memcg_move_charge_at_immigrate_test 1 TINFO: Starting test 1
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 1 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 1 TINFO: Running memcg_process 
--mmap-anon -s 135168
  memcg_move_charge_at_immigrate_test 1 TINFO: Warming up pid: 2162
  memcg_move_charge_at_immigrate_test 1 TINFO: Process is still here after warm 
up: 2162
  memcg_move_charge_at_immigrate_test 1 TPASS: rss is 0 as expected
  memcg_move_charge_at_immigrate_test 2 TPASS: cache is 0 as expected
  memcg_move_charge_at_immigrate_test 3 TPASS: rss is 135168 as expected
  memcg_move_charge_at_immigrate_test 4 TPASS: cache is 0 as expected
  memcg_move_charge_at_immigrate_test 5 TINFO: Starting test 2
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 5 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 5 TINFO: Running memcg_process 
--mmap-anon --shm --mmap-file -s 135168
  memcg_move_charge_at_immigrate_test 5 TINFO: Warming up pid: 2192
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 5 TFAIL: Process 2192 exited with 1 after 
warm up
  memcg_move_charge_at_immigrate_test 6 TINFO: Starting test 3
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 6 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 6 TINFO: Running memcg_process 
--mmap-anon --shm --mmap-file -s 135168
  memcg_move_charge_at_immigrate_test 6 TINFO: Warming up pid: 2207
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 6 TFAIL: Process 2207 exited with 1 after 
warm up
  memcg_move_charge_at_immigrate_test 7 TINFO: Starting test 4
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 522: echo: 
echo: I/O error
  memcg_move_charge_at_immigrate_test 7 TINFO: set 
/dev/memcg/memory.use_hierarchy to 0 failed
  memcg_move_charge_at_immigrate_test 7 TINFO: Running memcg_process 
--mmap-anon --shm -s 135168
  memcg_move_charge_at_immigrate_test 7 TINFO: Warming up pid: 
  memcg_process: shmget() failed: Invalid argument
  /opt/ltp/testcases/bin/memcg_move_charge_at_immigrate_test.sh: 168: kill: No 
such process

  memcg_move_charge_at_immigrate_test 7 TFAIL: Process  exited with 1 after 
warm up
  <<>>
  initiation_status="ok"
  duration=4 termination_type=exited termination_id=1 corefile=no
  cutime=9 cstime=2
  <<>>

  Steps to run this test:
    git clone --depth=1 https://github.com/linux-test-project/ltp.git
    cd ltp; make autotools; ./configure; make; sudo make install
    echo "memcg_move_charge_at_immigrate  
memcg_move_charge_at_immigrate_test.sh" > /tmp/jobs
    sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-21-generic 5.0.0-21.22
  ProcVersionSignature: User Name 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 18 10:01 seq
   crw-rw 1 root audio 116, 33 Jul 18 10:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v',

[Kernel-packages] [Bug 1845919] Re: memcg_failcnt in mm from ubuntu_ltp failed on B 4.15

** Tags added: sru-20220131

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

Title:
  memcg_failcnt in mm from ubuntu_ltp failed on B 4.15

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

Bug description:
  Issue found on node amaura, with Bionic 4.15 AMD64:
   tag=memcg_test_3 stime=1569410880 dur=0 exit=exited stat=0 core=no cu=9 cs=17
   startup='Wed Sep 25 11:28:01 2019'
   memcg_failcnt 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 8192
   memcg_failcnt 1 TBROK: timeouted on memory.usage_in_bytes
   tag=memcg_failcnt stime=1569410881 dur=10 exit=exited stat=2 core=no cu=9 
cs=2

  
  Probably a test case issue, it needs to be investigated

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


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

[Kernel-packages] [Bug 1845919] Re: memcg_failcnt in mm from ubuntu_ltp failed on B 4.15

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

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

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

Title:
  memcg_failcnt in mm from ubuntu_ltp failed on B 4.15

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

Bug description:
  Issue found on node amaura, with Bionic 4.15 AMD64:
   tag=memcg_test_3 stime=1569410880 dur=0 exit=exited stat=0 core=no cu=9 cs=17
   startup='Wed Sep 25 11:28:01 2019'
   memcg_failcnt 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_failcnt 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
   memcg_failcnt 1 TINFO: Running memcg_process --mmap-anon -s 8192
   memcg_failcnt 1 TBROK: timeouted on memory.usage_in_bytes
   tag=memcg_failcnt stime=1569410881 dur=10 exit=exited stat=2 core=no cu=9 
cs=2

  
  Probably a test case issue, it needs to be investigated

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


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

[Kernel-packages] [Bug 1845919] Re: memcg_failcnt in mm from ubuntu_ltp failed on B 4.15