[Kernel-packages] [Bug 1885862] [NEW] Add in-tree Realtek 8821CE wireless module support

[You-Sheng Yang]

Public bug reported:

TBD.

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

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

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

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

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

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

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

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

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

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


** Tags: oem-priority originate-from-1884513 stella

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

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

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

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

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

** Also affects: linux-firmware (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/1885862

Title:
  Add in-tree Realtek 8821CE wireless module support

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-oem-5.6 source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux-firmware source package in Groovy:
  New
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  TBD.

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

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

[Kernel-packages] [Bug 1867591] Re: [ACC-0316]sync mainline kernel 5.6rc6 ACC patchset into ubuntu HWE kernel branch

[Ike Panhc]

** Tags removed: ikeradar

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

Title:
  [ACC-0316]sync mainline kernel 5.6rc6  ACC patchset into ubuntu HWE
  kernel branch

Status in kunpeng920:
  Incomplete
Status in kunpeng920 ubuntu-18.04-hwe series:
  Incomplete
Status in kunpeng920 ubuntu-20.04 series:
  Incomplete
Status in kunpeng920 upstream-kernel series:
  Incomplete
Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Bug Description]
  roce patchset have merged into mainline 5.6rc2 kernel.

  [Steps to Reproduce]
1)
2)
3)

  [Actual Results]

  [Expected Results]

  [Reproducibility]

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

  [Resolution]
  crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver
  crypto: hisilicon/sec2 - Update IV and MAC operation
  crypto: hisilicon/sec2 - Add iommu status check
  crypto: hisilicon/sec2 - Add workqueue for SEC driver.
  crypto: hisilicon - Use one workqueue per qm instead of per qp
  crypto: hisilicon - qm depends on UACCE
  crypto: hisilicon - remove redundant assignment of pointer ctx
  hisilicon - register zip engine to uacce
  hisilicon - Remove module_param uacce_mode
  uacce: add uacce driver
  uacce: Add documents for uacce
  crypto: hisilicon - Fix duplicate print when qm occur multiple errors
  crypto: hisilicon - Unify error detect process into qm
  crypto: hisilicon - Configure zip RAS error type
  crypto: hisilicon - Unify hardware error init/uninit into QM

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

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

[Kernel-packages] [Bug 1875113] Re: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  The screen presents screen tearing in the browser, on the desktop as
  well and when installing Steam it says that it does not detect Opengl
  or any video card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 20:01:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:100d]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
  InstallationDate: Installed on 2020-04-24 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CM
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CM.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K46CM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/nvidia-graphics-drivers-390/+bug/1875113/+subscriptions

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

[Kernel-packages] [Bug 1875113] Re: OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  OpenGL not detected (Intel Ivy Bridge + Nvidia GeForce GT 635M)

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  The screen presents screen tearing in the browser, on the desktop as
  well and when installing Steam it says that it does not detect Opengl
  or any video card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.132  Fri Nov  1 00:40:14 
PDT 2019
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 20:01:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:100d]
   NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d]
  InstallationDate: Installed on 2020-04-24 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. K46CM
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K46CM.317
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K46CM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K46CM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  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/nvidia-graphics-drivers-390/+bug/1875113/+subscriptions

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

[Kernel-packages] [Bug 1885011] Re: Eoan update: upstream stable patchset 2020-06-24

[Khaled El Mously]

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

Title:
  Eoan update: upstream stable patchset 2020-06-24

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  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 2020-06-24

  Ported from the following upstream stable releases:
  v4.19.128, v5.4.46

     from git://git.kernel.org/

  devinet: fix memleak in inetdev_init()
  l2tp: add sk_family checks to l2tp_validate_socket
  l2tp: do not use inet_hash()/inet_unhash()
  net: usb: qmi_wwan: add Telit LE910C1-EUX composition
  NFC: st21nfca: add missed kfree_skb() in an error path
  vsock: fix timeout in vsock_accept()
  net: check untrusted gso_size at kernel entry
  USB: serial: qcserial: add DW5816e QDL support
  USB: serial: usb_wwan: do not resubmit rx urb on fatal errors
  USB: serial: option: add Telit LE910C1-EUX compositions
  iio: vcnl4000: Fix i2c swapped word reading.
  usb: musb: start session in resume for host port
  usb: musb: Fix runtime PM imbalance on error
  vt: keyboard: avoid signed integer overflow in k_ascii
  tty: hvc_console, fix crashes on parallel open/close
  staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK
  CDC-ACM: heed quirk also in error handling
  nvmem: qfprom: remove incorrect write support
  uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned
  Revert "net/mlx5: Annotate mutex destroy for root ns"
  net/mlx5: Fix crash upon suspend/resume
  net: stmmac: enable timestamp snapshot for required PTP packets in dwmac 
v5.10a
  nfp: flower: fix used time of merge flow statistics
  net: be more gentle about silly gso requests coming from user
  USB: serial: ch341: add basis for quirk detection
  iio:chemical:sps30: Fix timestamp alignment
  iio:chemical:pms7003: Fix timestamp alignment and prevent data leak.
  iio: adc: stm32-adc: fix a wrong error message when probing interrupts
  UBUNTU: upstream stable to v4.19.128, v5.4.46

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

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

[Kernel-packages] [Bug 1885775] Re: Eoan update: upstream stable patchset 2020-06-30

[Khaled El Mously]

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

Title:
  Eoan update: upstream stable patchset 2020-06-30

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  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 2020-06-30

  Ported from the following upstream stable releases:
  v4.19.129, v5.4.47

     from git://git.kernel.org/

  ipv6: fix IPV6_ADDRFORM operation logic
  net_failover: fixed rollback in net_failover_open()
  bridge: Avoid infinite loop when suppressing NS messages with invalid options
  vxlan: Avoid infinite loop when suppressing NS messages with invalid options
  tun: correct header offsets in napi frags mode
  Input: mms114 - fix handling of mms345l
  ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
  sched/fair: Don't NUMA balance for kthreads
  Input: synaptics - add a second working PNP_ID for Lenovo T470s
  drivers/net/ibmvnic: Update VNIC protocol version reporting
  powerpc/xive: Clear the page tables for the ESB IO mapping
  ath9k_htc: Silence undersized packet warnings
  RDMA/uverbs: Make the event_queue fds return POLLERR when disassociated
  x86/cpu/amd: Make erratum #1054 a legacy erratum
  perf probe: Accept the instance number of kretprobe event
  mm: add kvfree_sensitive() for freeing sensitive data objects
  aio: fix async fsync creds
  x86_64: Fix jiffies ODR violation
  x86/PCI: Mark Intel C620 MROMs as having non-compliant BARs
  x86/speculation: Prevent rogue cross-process SSBD shutdown
  x86/reboot/quirks: Add MacBook6,1 reboot quirk
  efi/efivars: Add missing kobject_put() in sysfs entry creation error path
  ALSA: es1688: Add the missed snd_card_free()
  ALSA: hda/realtek - add a pintbl quirk for several Lenovo machines
  ALSA: usb-audio: Fix inconsistent card PM state after resume
  ALSA: usb-audio: Add vendor, product and profile name for HP Thunderbolt Dock
  ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
  ACPI: CPPC: Fix reference count leak in acpi_cppc_processor_probe()
  ACPI: GED: add support for _Exx / _Lxx handler methods
  ACPI: PM: Avoid using power resources if there are none for D0
  nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
  spi: dw: Fix controller unregister order
  spi: bcm2835aux: Fix controller unregister order
  spi: bcm-qspi: when tx/rx buffer is NULL set to 0
  PM: runtime: clk: Fix clk_pm_runtime_get() error path
  crypto: cavium/nitrox - Fix 'nitrox_get_first_device()' when ndevlist is 
fully iterated
  ALSA: pcm: disallow linking stream to itself
  x86/{mce,mm}: Unmap the entire page if the whole page is affected and poisoned
  KVM: x86: Fix APIC page invalidation race
  KVM: x86/mmu: Consolidate "is MMIO SPTE" code
  KVM: x86: only do L1TF workaround on affected processors
  x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS.
  x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
  spi: Fix controller unregister order
  spi: pxa2xx: Fix controller unregister order
  spi: bcm2835: Fix controller unregister order
  spi: pxa2xx: Fix runtime PM ref imbalance on probe error
  crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req()
  crypto: virtio: Fix src/dst scatterlist calculation in 
__virtio_crypto_skcipher_do_req()
  crypto: virtio: Fix dest length calculation in 
__virtio_crypto_skcipher_do_req()
  selftests/net: in rxtimestamp getopt_long needs terminating null entry
  ovl: initialize error in ovl_copy_xattr
  proc: Use new_inode not new_inode_pseudo
  video: fbdev: w100fb: Fix a potential double free.
  KVM: nSVM: fix condition for filtering async PF
  KVM: nSVM: leave ASID aside in copy_vmcb_control_area
  KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
  KVM: MIPS: Define KVM_ENTRYHI_ASID to cpu_asid_mask(_cpu_data)
  KVM: MIPS: Fix VPN2_MASK definition for variable cpu_vmbits
  KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
  scsi: megaraid_sas: TM command refire leads to controller firmware crash
  ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
  ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
  ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
  ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
  Smack: 

[Kernel-packages] [Bug 1884296] Re: Eoan update: upstream stable patchset 2020-06-19

[Khaled El Mously]

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

Title:
  Eoan update: upstream stable patchset 2020-06-19

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  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 2020-06-19

  Ported from the following upstream stable releases:
  v4.19.127, v5.4.45

     from git://git.kernel.org/

  Revert "cgroup: Add memory barriers to plug cgroup_rstat_updated() race 
window"
  mm: Fix mremap not considering huge pmd devmap
  HID: sony: Fix for broken buttons on DS3 USB dongles
  HID: i2c-hid: add Schneider SCL142ALM to descriptor override
  p54usb: add AirVasT USB stick device-id
  kernel/relay.c: handle alloc_percpu returning NULL in relay_open
  mmc: fix compilation of user API
  scsi: ufs: Release clock if DMA map fails
  net: dsa: mt7530: set CPU port to fallback mode
  airo: Fix read overflows sending packets
  powerpc/powernv: Avoid re-registration of imc debugfs directory
  s390/ftrace: save traced function caller
  ARC: Fix ICCM & DCCM runtime size checks
  ARC: [plat-eznps]: Restrict to CONFIG_ISA_ARCOMPACT
  evm: Fix RCU list related warnings
  i2c: altera: Fix race between xfer_msg and isr thread
  x86/mmiotrace: Use cpumask_available() for cpumask_var_t variables
  net: bmac: Fix read of MAC address from ROM
  drm/edid: Add Oculus Rift S to non-desktop list
  s390/mm: fix set_huge_pte_at() for empty ptes
  null_blk: return error for invalid zone size
  net/ethernet/freescale: rework quiesce/activate for ucc_geth
  net: ethernet: stmmac: Enable interface clocks on probe for IPQ806x
  net: smsc911x: Fix runtime PM imbalance on error
  HID: multitouch: add support for the Smart Tech panel
  HID: multitouch: enable multi-input as a quirk for some devices
  mt76: mt76x02u: Add support for newer versions of the XBox One wifi adapter
  media: Revert "staging: imgu: Address a compiler warning on alignment"
  media: staging: ipu3-imgu: Move alignment attribute to field
  ASoC: intel - fix the card names
  RDMA/qedr: Fix qpids xarray api used
  RDMA/qedr: Fix synchronization methods and memory leaks in qedr
  io_uring: initialize ctx->sqo_wait earlier
  selftests: mlxsw: qos_mc_aware: Specify arping timeout as an integer
  UBUNTU: upstream stable to v4.19.127, v5.4.45

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

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

[Kernel-packages] [Bug 1882831] Re: Eoan update: upstream stable patchset 2020-06-09

[Khaled El Mously]

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

Title:
  Eoan update: upstream stable patchset 2020-06-09

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  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 2020-06-09

  Ported from the following upstream stable releases:
  v4.19.126, v5.4.44

     from git://git.kernel.org/

  ax25: fix setsockopt(SO_BINDTODEVICE)
  dpaa_eth: fix usage as DSA master, try 3
  net: dsa: mt7530: fix roaming from DSA user ports
  __netif_receive_skb_core: pass skb by reference
  net: inet_csk: Fix so_reuseport bind-address cache in tb->fast*
  net: ipip: fix wrong address family in init error path
  net/mlx5: Add command entry handling completion
  net: qrtr: Fix passing invalid reference to qrtr_local_enqueue()
  net: revert "net: get rid of an signed integer overflow in 
ip_idents_reserve()"
  net sched: fix reporting the first-time use timestamp
  r8152: support additional Microsoft Surface Ethernet Adapter variant
  sctp: Don't add the shutdown timer if its already been added
  sctp: Start shutdown on association restart if in SHUTDOWN-SENT state and 
socket is closed
  net/mlx5e: Update netdev txq on completions during closure
  net/mlx5: Annotate mutex destroy for root ns
  net: sun: fix missing release regions in cas_init_one().
  net/mlx4_core: fix a memory leak bug.
  mlxsw: spectrum: Fix use-after-free of split/unsplit/type_set in case reload 
fails
  ARM: dts: rockchip: fix phy nodename for rk3228-evb
  arm64: dts: rockchip: fix status for  in rk3328-evb.dts
  arm64: dts: rockchip: swap interrupts interrupt-names rk3399 gpu node
  ARM: dts: rockchip: swap clock-names of gpu nodes
  ARM: dts: rockchip: fix pinctrl sub nodename for spi in rk322x.dtsi
  gpio: tegra: mask GPIO IRQs during IRQ shutdown
  ALSA: usb-audio: add mapping for ASRock TRX40 Creator
  net: microchip: encx24j600: add missed kthread_stop
  gfs2: move privileged user check to gfs2_quota_lock_check
  cachefiles: Fix race between read_waiter and read_copier involving op->to_do
  usb: dwc3: pci: Enable extcon driver for Intel Merrifield
  usb: gadget: legacy: fix redundant initialization warnings
  net: freescale: select CONFIG_FIXED_PHY where needed
  IB/i40iw: Remove bogus call to netdev_master_upper_dev_get()
  riscv: stacktrace: Fix undefined reference to `walk_stackframe'
  cifs: Fix null pointer check in cifs_read
  samples: bpf: Fix build error
  Input: usbtouchscreen - add support for BonXeon TP
  Input: evdev - call input_flush_device() on release(), not flush()
  Input: xpad - add custom init packet for Xbox One S controllers
  Input: dlink-dir685-touchkeys - fix a typo in driver name
  Input: i8042 - add ThinkPad S230u to i8042 reset list
  Input: synaptics-rmi4 - really fix attn_data use-after-free
  Input: synaptics-rmi4 - fix error return code in rmi_driver_probe()
  ARM: 8970/1: decompressor: increase tag size
  ARM: uaccess: consolidate uaccess asm to asm/uaccess-asm.h
  ARM: uaccess: integrate uaccess_save and uaccess_restore
  ARM: uaccess: fix DACR mismatch with nested exceptions
  gpio: exar: Fix bad handling for ida_simple_get error path
  IB/qib: Call kobject_put() when kobject_init_and_add() fails
  ARM: dts/imx6q-bx50v3: Set display interface clock parents
  ARM: dts: bcm2835-rpi-zero-w: Fix led polarity
  ARM: dts: bcm: HR2: Fix PPI interrupt types
  mmc: block: Fix use-after-free issue for rpmb
  RDMA/pvrdma: Fix missing pci disable in pvrdma_pci_probe()
  ALSA: hwdep: fix a left shifting 1 by 31 UB bug
  ALSA: hda/realtek - Add a model for Thinkpad T570 without DAC workaround
  ALSA: usb-audio: mixer: volume quirk for ESS Technology Asus USB DAC
  exec: Always set cap_ambient in cap_bprm_set_creds
  ALSA: usb-audio: Quirks for Gigabyte TRX40 Aorus Master onboard audio
  ALSA: hda/realtek - Add new codec supported for ALC287
  libceph: ignore pool overlay and cache logic on redirects
  IB/ipoib: Fix double free of skb in case of multicast traffic in CM mode
  mm: remove VM_BUG_ON(PageSlab()) from page_mapcount()
  fs/binfmt_elf.c: allocate initialized memory in fill_thread_core_info()
  include/asm-generic/topology.h: guard cpumask_of_node() macro argument
  iommu: Fix reference count leak in iommu_group_alloc.
  parisc: Fix 

[Kernel-packages] [Bug 1883167] Re: Bionic update: upstream stable patchset 2020-06-11

[Khaled El Mously]

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

Title:
  Bionic update: upstream stable patchset 2020-06-11

Status in linux package in Ubuntu:
  Confirmed
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 2020-06-11

  Ported from the following upstream stable releases: 
  v4.14.183, v4.19.126 

     from git://git.kernel.org/

  ax25: fix setsockopt(SO_BINDTODEVICE)
  net: ipip: fix wrong address family in init error path
  net/mlx5: Add command entry handling completion
  net: revert "net: get rid of an signed integer overflow in 
ip_idents_reserve()"
  net sched: fix reporting the first-time use timestamp
  r8152: support additional Microsoft Surface Ethernet Adapter variant
  sctp: Start shutdown on association restart if in SHUTDOWN-SENT state and 
socket is closed
  net/mlx5e: Update netdev txq on completions during closure
  net: qrtr: Fix passing invalid reference to qrtr_local_enqueue()
  net: sun: fix missing release regions in cas_init_one().
  net/mlx4_core: fix a memory leak bug.
  ARM: dts: rockchip: fix phy nodename for rk3228-evb
  arm64: dts: rockchip: swap interrupts interrupt-names rk3399 gpu node
  ARM: dts: rockchip: fix pinctrl sub nodename for spi in rk322x.dtsi
  gpio: tegra: mask GPIO IRQs during IRQ shutdown
  net: microchip: encx24j600: add missed kthread_stop
  gfs2: move privileged user check to gfs2_quota_lock_check
  cachefiles: Fix race between read_waiter and read_copier involving op->to_do
  usb: gadget: legacy: fix redundant initialization warnings
  net: freescale: select CONFIG_FIXED_PHY where needed
  cifs: Fix null pointer check in cifs_read
  samples: bpf: Fix build error
  Input: usbtouchscreen - add support for BonXeon TP
  Input: evdev - call input_flush_device() on release(), not flush()
  Input: xpad - add custom init packet for Xbox One S controllers
  Input: dlink-dir685-touchkeys - fix a typo in driver name
  Input: i8042 - add ThinkPad S230u to i8042 reset list
  Input: synaptics-rmi4 - really fix attn_data use-after-free
  Input: synaptics-rmi4 - fix error return code in rmi_driver_probe()
  ARM: 8843/1: use unified assembler in headers
  ARM: uaccess: consolidate uaccess asm to asm/uaccess-asm.h
  ARM: uaccess: integrate uaccess_save and uaccess_restore
  ARM: uaccess: fix DACR mismatch with nested exceptions
  gpio: exar: Fix bad handling for ida_simple_get error path
  IB/qib: Call kobject_put() when kobject_init_and_add() fails
  ARM: dts: imx6q-bx50v3: Add internal switch
  ARM: dts/imx6q-bx50v3: Set display interface clock parents
  ARM: dts: bcm2835-rpi-zero-w: Fix led polarity
  mmc: block: Fix use-after-free issue for rpmb
  RDMA/pvrdma: Fix missing pci disable in pvrdma_pci_probe()
  ALSA: hwdep: fix a left shifting 1 by 31 UB bug
  ALSA: usb-audio: mixer: volume quirk for ESS Technology Asus USB DAC
  exec: Always set cap_ambient in cap_bprm_set_creds
  ALSA: hda/realtek - Add new codec supported for ALC287
  libceph: ignore pool overlay and cache logic on redirects
  mm: remove VM_BUG_ON(PageSlab()) from page_mapcount()
  fs/binfmt_elf.c: allocate initialized memory in fill_thread_core_info()
  include/asm-generic/topology.h: guard cpumask_of_node() macro argument
  iommu: Fix reference count leak in iommu_group_alloc.
  parisc: Fix kernel panic in mem_init()
  mac80211: mesh: fix discovery timer re-arming issue / crash
  x86/dma: Fix max PFN arithmetic overflow on 32 bit systems
  copy_xstate_to_kernel(): don't leave parts of destination uninitialized
  xfrm: allow to accept packets with ipv6 NEXTHDR_HOP in xfrm_input
  xfrm: call xfrm_output_gso when inner_protocol is set in xfrm_output
  xfrm: fix a warning in xfrm_policy_insert_list
  xfrm: fix a NULL-ptr deref in xfrm_local_error
  xfrm: fix error in comment
  vti4: eliminated some duplicate code.
  ip_vti: receive ipip packet by calling ip_tunnel_rcv
  netfilter: nft_reject_bridge: enable reject with bridge vlan
  netfilter: ipset: Fix subcounter update skip
  netfilter: nfnetlink_cthelper: unbreak userspace helper support
  netfilter: nf_conntrack_pptp: prevent buffer overflows in debug code
  esp6: get the right proto for transport mode in esp6_gso_encap
  qlcnic: fix missing release in qlcnic_83xx_interrupt_test.
  bonding: Fix 

[Kernel-packages] [Bug 1883314] Re: Bionic update: upstream stable patchset 2020-06-12

[Khaled El Mously]

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

Title:
  Bionic update: upstream stable patchset 2020-06-12

Status in linux package in Ubuntu:
  Confirmed
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 2020-06-12

  Ported from the following upstream stable releases:
  v4.14.184, v4.19.127
     v4.19.128

     from git://git.kernel.org/

  libnvdimm: Fix endian conversion issues 
  spi: dw: use "smp_mb()" to avoid sending spi data error
  s390/ftrace: save traced function caller
  ARC: Fix ICCM & DCCM runtime size checks
  ARC: [plat-eznps]: Restrict to CONFIG_ISA_ARCOMPACT
  i2c: altera: Fix race between xfer_msg and isr thread
  x86/mmiotrace: Use cpumask_available() for cpumask_var_t variables
  net: bmac: Fix read of MAC address from ROM
  net/ethernet/freescale: rework quiesce/activate for ucc_geth
  net: ethernet: stmmac: Enable interface clocks on probe for IPQ806x
  net: smsc911x: Fix runtime PM imbalance on error
  mm: Fix mremap not considering huge pmd devmap
  HID: sony: Fix for broken buttons on DS3 USB dongles
  HID: i2c-hid: add Schneider SCL142ALM to descriptor override
  p54usb: add AirVasT USB stick device-id
  kernel/relay.c: handle alloc_percpu returning NULL in relay_open
  mmc: fix compilation of user API
  scsi: ufs: Release clock if DMA map fails
  airo: Fix read overflows sending packets
  devinet: fix memleak in inetdev_init()
  l2tp: do not use inet_hash()/inet_unhash()
  net: usb: qmi_wwan: add Telit LE910C1-EUX composition
  NFC: st21nfca: add missed kfree_skb() in an error path
  vsock: fix timeout in vsock_accept()
  net: check untrusted gso_size at kernel entry
  l2tp: add sk_family checks to l2tp_validate_socket
  USB: serial: qcserial: add DW5816e QDL support
  USB: serial: usb_wwan: do not resubmit rx urb on fatal errors
  USB: serial: option: add Telit LE910C1-EUX compositions
  usb: musb: start session in resume for host port
  usb: musb: Fix runtime PM imbalance on error
  vt: keyboard: avoid signed integer overflow in k_ascii
  tty: hvc_console, fix crashes on parallel open/close
  staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK
  CDC-ACM: heed quirk also in error handling
  nvmem: qfprom: remove incorrect write support
  iio: vcnl4000: Fix i2c swapped word reading.
  uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned
  drm/i915: fix port checks for MST support on gen >= 11
  s390/mm: fix set_huge_pte_at() for empty ptes
  UBUNTU: upstream stable to v4.14.184, v4.19.128

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

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

[Kernel-packages] [Bug 1885176] Re: Bionic update: upstream stable patchset 2020-06-25

[Khaled El Mously]

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

Title:
  Bionic update: upstream stable patchset 2020-06-25

Status in linux package in Ubuntu:
  Confirmed
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 2020-06-25

  Ported from the following upstream stable releases:
  v4.14.185, v4.19.129

     from git://git.kernel.org/

  ipv6: fix IPV6_ADDRFORM operation logic
  vxlan: Avoid infinite loop when suppressing NS messages with invalid options
  make 'user_access_begin()' do 'access_ok()'
  Fix 'acccess_ok()' on alpha and SH
  arch/openrisc: Fix issues with access_ok()
  x86: uaccess: Inhibit speculation past access_ok() in user_access_begin()
  lib: Reduce user_access_begin() boundaries in strncpy_from_user() and 
strnlen_user()
  serial: imx: Fix handling of TC irq in combination with DMA
  crypto: talitos - fix ECB and CBC algs ivsize
  ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
  sched/fair: Don't NUMA balance for kthreads
  Input: synaptics - add a second working PNP_ID for Lenovo T470s
  drivers/net/ibmvnic: Update VNIC protocol version reporting
  powerpc/xive: Clear the page tables for the ESB IO mapping
  ath9k_htc: Silence undersized packet warnings
  perf probe: Accept the instance number of kretprobe event
  mm: add kvfree_sensitive() for freeing sensitive data objects
  x86_64: Fix jiffies ODR violation
  x86/PCI: Mark Intel C620 MROMs as having non-compliant BARs
  x86/speculation: Prevent rogue cross-process SSBD shutdown
  x86/reboot/quirks: Add MacBook6,1 reboot quirk
  efi/efivars: Add missing kobject_put() in sysfs entry creation error path
  ALSA: es1688: Add the missed snd_card_free()
  ALSA: hda/realtek - add a pintbl quirk for several Lenovo machines
  ALSA: usb-audio: Fix inconsistent card PM state after resume
  ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
  ACPI: CPPC: Fix reference count leak in acpi_cppc_processor_probe()
  ACPI: GED: add support for _Exx / _Lxx handler methods
  ACPI: PM: Avoid using power resources if there are none for D0
  cgroup, blkcg: Prepare some symbols for module and !CONFIG_CGROUP usages
  nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
  spi: bcm2835aux: Fix controller unregister order
  spi: bcm-qspi: when tx/rx buffer is NULL set to 0
  crypto: cavium/nitrox - Fix 'nitrox_get_first_device()' when ndevlist is 
fully iterated
  ALSA: pcm: disallow linking stream to itself
  kvm: x86: Fix L1TF mitigation for shadow MMU
  KVM: x86/mmu: Consolidate "is MMIO SPTE" code
  KVM: x86: only do L1TF workaround on affected processors
  x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS.
  x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
  spi: dw: Fix controller unregister order
  spi: No need to assign dummy value in spi_unregister_controller()
  spi: Fix controller unregister order
  spi: pxa2xx: Fix controller unregister order
  spi: bcm2835: Fix controller unregister order
  crypto: virtio: Fix use-after-free in virtio_crypto_skcipher_finalize_req()
  crypto: virtio: Fix src/dst scatterlist calculation in 
__virtio_crypto_skcipher_do_req()
  crypto: virtio: Fix dest length calculation in 
__virtio_crypto_skcipher_do_req()
  selftests/net: in rxtimestamp getopt_long needs terminating null entry
  ovl: initialize error in ovl_copy_xattr
  proc: Use new_inode not new_inode_pseudo
  video: fbdev: w100fb: Fix a potential double free.
  KVM: nSVM: fix condition for filtering async PF
  KVM: nSVM: leave ASID aside in copy_vmcb_control_area
  KVM: nVMX: Consult only the "basic" exit reason when routing nested exit
  KVM: MIPS: Define KVM_ENTRYHI_ASID to cpu_asid_mask(_cpu_data)
  KVM: MIPS: Fix VPN2_MASK definition for variable cpu_vmbits
  KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts
  ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx
  ath9k: Fix use-after-free Write in ath9k_htc_rx_msg
  ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb
  ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb
  Smack: slab-out-of-bounds in vsscanf
  mm/slub: fix a memory leak in sysfs_slab_add()
  fat: don't allow to mount if the FAT length == 0
  perf: Add cond_resched() to 

[Kernel-packages] [Bug 1881046] Re: ASoC/amd: add audio driver for amd renoir

[Hui Wang]

** Changed in: linux-oem-5.6 (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  ASoC/amd: add audio driver for amd renoir

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Incomplete

Bug description:
  This patchset is for mainline kernel-5.8, after backporting to 5.6,
  there is no need to change anything, but after backporting to 5.4
  kernel, because of API differences, need to do some change to adapt
  to 5.4 kernel's API. So there is one more patch for focal than for
  oem-5.6.

  [Impact]
  We have a couple of LENOVO machines which has amd renoir audio on
  them, our kernel doesn't have the driver for it yet.

  [Fix]
  amd just upstreamed the driver, it is for kernel-5.8, we backport
  them to ubunt kernel.

  [Test Case]
  boot the kernel with those patches, we could see a sound card named
  "acp" and the dmic on it could record sound via arecord.

  [Regression Risk]
  Low, just adding a new driver, no change to existing drivers.

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

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

[Kernel-packages] [Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering

[Khaled El Mously]

** Changed in: linux-kvm (Ubuntu Eoan)
   Status: Triaged => Fix Committed

** Changed in: linux-kvm (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  LXD 4.2 broken on linux-kvm due to missing VLAN filtering

Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Eoan:
  Fix Committed
Status in linux-kvm source package in Focal:
  Fix Committed

Bug description:
  [Description]

  Some VLAN options (BRIDGE_VLAN_FILTERING, and its dependencies
  VLAN_8021Q*) were in a different state in Focal/kvm compared to
  Focal/generic: LXD now depends on BRIDGE_VLAN_FILTERING and due to
  this discrepancy it fails to work on the Focal/kvm kernel: fix it by
  aligning the config with Focal/generic

  [Fix]

  Apply the attached config patch

  [Regression potential]

  Low, just some config changes already present in generic.

  ---
  This is another case of linux-kvm having unexplained differences compared to 
linux-generic in areas that aren't related to hardware drivers (see other bug 
we filed for missing nft).

  This time, CPC is reporting that LXD no longer works on linux-kvm as
  we now set vlan filtering on our bridges to prevent containers from
  escaping firewalling through custom vlan tags.

  This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the
  generic kernel but is apparently missing on linux-kvm (I don't have
  any system running that kernel to confirm its config, but the behavior
  certainly matches that).

  We need this fixed in focal and groovy.

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

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

[Kernel-packages] [Bug 1885330] Re: [nouveau] System unresponsive to keyboard and mouse clicks when changing screen background

[Daniel van Vugt]

We can also reopen this and leave it open. But in an open state you
might be asked by kernel engineers to test various things. If you're no
longer using the offending driver then that could be annoying. It's up
to you.

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

Title:
  [nouveau] System unresponsive to keyboard and mouse clicks when
  changing screen background

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1884767] Re: shiftfs: fix btrfs regression

[Khaled El Mously]

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

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

Title:
  shiftfs: fix btrfs regression

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

Bug description:
  SRU Justification

  Impact: The patch
  commit cfaa482afb97e3c05d020af80b897b061109d51f
  Author: Christian Brauner 
  Date:   Tue Apr 14 22:26:53 2020 +0200

  UBUNTU: SAUCE: shiftfs: fix dentry revalidation

  BugLink: https://bugs.launchpad.net/bugs/1872757

  to fix https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757
  regresses various btrfs + shiftfs users. Creating a btrfs subvolume,
  deleting it, and then trying to recreate it will cause EEXIST to be returned.
  It also leaves some files in a half-visible state because they are not 
revalidated
  correctly.
  Faulty behavior such as this can be reproduced via:

  btrfs subvolume create my-subvol
  btrfs subvolume delete my-subvol

  Fix: We need to revert this patch restoring the old behavior. This will 
briefly
  resurface https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757 which 
I will fix in a follow-up patch on top of this revert. We basically split the 
part that fixes https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872757 
out of the revert.

  Regression Potential: Limited to shiftfs.

  Test Case: Build a kernel with fix applied and run above reproducer.

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

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

Re: [Kernel-packages] [Bug 1885330] Re: [nouveau] System unresponsive to keyboard and mouse clicks when changing screen background

[Lester Potter]

My only concern is whether there will be issues with updates and upgrades
to my box in the future.
Other than that, I am fine with "won't fix".

On Tue, Jun 30, 2020 at 11:10 PM Daniel van Vugt <1885...@bugs.launchpad.net>
wrote:

> Great!
>
> If you don't want/need to discuss the original issue then we can close
> this as 'Won't Fix'.
>
>
> ** Changed in: linux (Ubuntu)
>Status: Incomplete => New
>
> ** Changed in: linux (Ubuntu)
>Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1885330
>
> Title:
>   [nouveau] System unresponsive to keyboard and mouse clicks when
>   changing screen background
>
> Status in linux package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   Right click on screen background and choose settings.
>   Then click a different background.
>   System becomes unresponsive to keyboard input and mouse clicks.
>   System returns to responsiveness after about 10 minutes.
>
>   Description:  Ubuntu 20.04 LTS
>   Release:  20.04
>
>   CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz
>   Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%)
>   Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38
>
>   Expected behavior:
>   Changing the background happens immediately and system remains
> responsive to input.
>
>   What happened:
>   System did not change the background immediately and became unresponsive
> to keyboard and mouse input for 10 minutes at which point the background
> changed to the selected one and responsiveness returned.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-control-center 1:3.36.2-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
>   Uname: Linux 5.4.0-37-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.3
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Jun 26 15:50:44 2020
>   ExecutablePath: /usr/bin/gnome-control-center
>   InstallationDate: Installed on 2020-06-13 (13 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885330/+subscriptions
>

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

Title:
  [nouveau] System unresponsive to keyboard and mouse clicks when
  changing screen background

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1884089] Re: Focal update: v5.4.47 upstream stable release

[Khaled El Mously]

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

Title:
  Focal update: v5.4.47 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
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.47 upstream stable release
     from git://git.kernel.org/

  ipv6: fix IPV6_ADDRFORM operation logic
  mlxsw: core: Use different get_trend() callbacks for different thermal zones
  net_failover: fixed rollback in net_failover_open()
  tun: correct header offsets in napi frags mode
  bridge: Avoid infinite loop when suppressing NS messages with invalid options
  vxlan: Avoid infinite loop when suppressing NS messages with invalid options
  bpf: Support llvm-objcopy for vmlinux BTF
  elfnote: mark all .note sections SHF_ALLOC
  Input: mms114 - fix handling of mms345l
  ARM: 8977/1: ptrace: Fix mask for thumb breakpoint hook
  sched/fair: Don't NUMA balance for kthreads
  Input: synaptics - add a second working PNP_ID for Lenovo T470s
  csky: Fixup abiv2 syscall_trace break a4 & a5
  gfs2: Even more gfs2_find_jhead fixes
  drivers/net/ibmvnic: Update VNIC protocol version reporting
  powerpc/xive: Clear the page tables for the ESB IO mapping
  spi: dw: Fix native CS being unset
  ath9k_htc: Silence undersized packet warnings
  smack: avoid unused 'sip' variable warning
  RDMA/uverbs: Make the event_queue fds return POLLERR when disassociated
  padata: add separate cpuhp node for CPUHP_PADATA_DEAD
  s390/pci: Log new handle in clp_disable_fh()
  x86/cpu/amd: Make erratum #1054 a legacy erratum
  KVM: x86: only do L1TF workaround on affected processors
  PCI/PM: Adjust pcie_wait_for_link_delay() for caller delay
  perf probe: Accept the instance number of kretprobe event
  mm: add kvfree_sensitive() for freeing sensitive data objects
  selftests: fix flower parent qdisc
  fanotify: fix ignore mask logic for events on child and on dir
  aio: fix async fsync creds
  ipv4: fix a RCU-list lock in fib_triestat_seq_show
  iwlwifi: mvm: fix NVM check for 3168 devices
  sctp: fix possibly using a bad saddr with a given dst
  sctp: fix refcount bug in sctp_wfree
  x86_64: Fix jiffies ODR violation
  x86/PCI: Mark Intel C620 MROMs as having non-compliant BARs
  x86/speculation: Prevent rogue cross-process SSBD shutdown
  x86/speculation: Avoid force-disabling IBPB based on STIBP and enhanced IBRS.
  x86/speculation: PR_SPEC_FORCE_DISABLE enforcement for indirect branches.
  x86/reboot/quirks: Add MacBook6,1 reboot quirk
  perf/x86/intel: Add more available bits for OFFCORE_RESPONSE of Intel Tremont
  KVM: x86/mmu: Set mmio_value to '0' if reserved #PF can't be generated
  KVM: x86: respect singlestep when emulating instruction
  KVM: x86: Fix APIC page invalidation race
  powerpc/ptdump: Properly handle non standard page size
  ASoC: max9867: fix volume controls
  io_uring: use kvfree() in io_sqe_buffer_register()
  efi/efivars: Add missing kobject_put() in sysfs entry creation error path
  smb3: fix incorrect number of credits when ioctl MaxOutputResponse > 64K
  smb3: add indatalen that can be a non-zero value to calculation of credit 
charge in smb2 ioctl
  watchdog: imx_sc_wdt: Fix reboot on crash
  ALSA: es1688: Add the missed snd_card_free()
  ALSA: fireface: fix configuration error for nominal sampling transfer 
frequency
  ALSA: hda/realtek - add a pintbl quirk for several Lenovo machines
  ALSA: pcm: disallow linking stream to itself
  ALSA: pcm: fix snd_pcm_link() lockdep splat
  ALSA: usb-audio: Fix inconsistent card PM state after resume
  ALSA: usb-audio: Add vendor, product and profile name for HP Thunderbolt Dock
  ACPI: sysfs: Fix reference count leak in acpi_sysfs_add_hotplug_profile()
  ACPI: CPPC: Fix reference count leak in acpi_cppc_processor_probe()
  ACPI: GED: add support for _Exx / _Lxx handler methods
  ACPI: PM: Avoid using power resources if there are none for D0
  arm64: acpi: fix UBSAN warning
  lib/lzo: fix ambiguous encoding bug in lzo-rle
  nilfs2: fix null pointer dereference at nilfs_segctor_do_construct()
  spi: dw: Fix controller unregister order
  spi: Fix controller unregister order
  spi: pxa2xx: Fix controller unregister order
  spi: pxa2xx: Fix runtime PM ref imbalance on probe error
  spi: bcm2835: Fix controller unregister order
  spi: bcm2835aux: Fix controller unregister order
  spi: 

[Kernel-packages] [Bug 1883962] Re: apparmor reference leak causes refcount_t overflow with af_alg_accept()

[Khaled El Mously]

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

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

Title:
  apparmor reference leak causes refcount_t overflow with
  af_alg_accept()

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

Bug description:
  [Impact]

   * Users of the Crypto (user-space) API (i.e., AF_ALG)
     can trigger refcount errors in AppArmor under high
     load (might lead to memory leak or use after free.)

   * There is a reference leak in AppArmor when af_alg_accept()
     calls security_sock_graft() and then security_sk_clone().

   * Both acquire a reference to a label, to assign it to the
     same pointer, but the latter does not release the former's
     acquired reference (before overwriting the pointer value.)

   * This reference leak builds up over time, and under high
     load can eventually overflow/underflow/saturate refcount,
     depending on which value it has when a program hits that.

   * The fix just checks if the pointer has an assigned label,
     then releases its acquired reference.

  [Test Case]

   * See comment #1 for the test-case 'aa-refcnt-af_alg.c'.

   * Exercise that code path indefinitely until it hits
     the refcount_t overflow/underflow/saturate message
     (or not, with the patch.) (see comment #4)

   * It's possible to monitor refcount values with kprobes,
     to confirm whether or not the problem is happening.
     (see comments #2 and #3)

  [Other Info]

   * Patch applied upstream on v5.8-rc1 [1]
   * Applied on Unstable (tag Ubuntu-5.8-5.8.0-0.1)
   * Not required on Groovy (still 5.4; should sync from Unstable)
   * Not required on Eoan (EOL date before SRU cycle release date)
   * Required on Bionic and Focal.

  [1]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=3b646abc5bc6c0df649daea4c2c976bd4d47e4c8

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

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

[Kernel-packages] [Bug 1884251] Re: Support Audio Mute LED for two new HP laptops

[Khaled El Mously]

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

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

Title:
  Support Audio Mute LED for two new HP laptops

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Mute LED doesn't work on two new HP laptops.

  [Fix]
  Add IDs to apply quirks to enable mute LED.

  [Test]
  After applying the patch the audio mute LED will light up when speaker is 
muted.

  [Regression Potential]
  Low. The fix limits to two specific systems.

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

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

[Kernel-packages] [Bug 1881046] Re: ASoC/amd: add audio driver for amd renoir

[Launchpad Bug Tracker]

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

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

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

Title:
  ASoC/amd: add audio driver for amd renoir

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Incomplete

Bug description:
  This patchset is for mainline kernel-5.8, after backporting to 5.6,
  there is no need to change anything, but after backporting to 5.4
  kernel, because of API differences, need to do some change to adapt
  to 5.4 kernel's API. So there is one more patch for focal than for
  oem-5.6.

  [Impact]
  We have a couple of LENOVO machines which has amd renoir audio on
  them, our kernel doesn't have the driver for it yet.

  [Fix]
  amd just upstreamed the driver, it is for kernel-5.8, we backport
  them to ubunt kernel.

  [Test Case]
  boot the kernel with those patches, we could see a sound card named
  "acp" and the dmic on it could record sound via arecord.

  [Regression Risk]
  Low, just adding a new driver, no change to existing drivers.

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

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

[Kernel-packages] [Bug 1875456] Re: Azure diagnostic/serviceability improvement

[Khaled El Mously]

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

Title:
  Azure diagnostic/serviceability improvement

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure-4.15 package in Ubuntu:
  New
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-4.15 source package in Bionic:
  Fix Committed

Bug description:
  Microsoft would like to request the inclusion of commits in all
  releases supported on Azure.  These commits will enable reporting 4
  Kbytes of dmesg information to Hyper-V when Linux takes a panic.

  Microsoft would like to get all releases reporting this information,
  so that we can automatically get a rich picture of Linux panics in
  Azure.  This will limit the need get serial console logs or other
  steps to manually acquire debug info.

  We would like to request the folloiwng commits to enable the
  diagnostic/serviceability improvement:

  f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is 
set")
  040026df7088 ("x86/Hyper-V: Report crash register data when 
sysctl_record_panic_msg is not set")
  a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running 
crash kernel")
  73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during 
system crash.")
  7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg 
dump")
  74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
  8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up 
hv_ctl_table_hdr")
  ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg 
get dump buffer")
  81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V 
during panic")
  7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")

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

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

[Kernel-packages] [Bug 1885330] Re: [nouveau] System unresponsive to keyboard and mouse clicks when changing screen background

[Daniel van Vugt]

Great!

If you don't want/need to discuss the original issue then we can close
this as 'Won't Fix'.


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

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

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

Title:
  [nouveau] System unresponsive to keyboard and mouse clicks when
  changing screen background

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1883184] Re: Focal update: v5.4.46 upstream stable release

[Khaled El Mously]

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

Title:
  Focal update: v5.4.46 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
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.46 upstream stable release
     from git://git.kernel.org/

  devinet: fix memleak in inetdev_init()
  l2tp: add sk_family checks to l2tp_validate_socket
  l2tp: do not use inet_hash()/inet_unhash()
  net/mlx5: Fix crash upon suspend/resume
  net: stmmac: enable timestamp snapshot for required PTP packets in dwmac 
v5.10a
  net: usb: qmi_wwan: add Telit LE910C1-EUX composition
  NFC: st21nfca: add missed kfree_skb() in an error path
  nfp: flower: fix used time of merge flow statistics
  vsock: fix timeout in vsock_accept()
  net: check untrusted gso_size at kernel entry
  net: be more gentle about silly gso requests coming from user
  USB: serial: qcserial: add DW5816e QDL support
  USB: serial: usb_wwan: do not resubmit rx urb on fatal errors
  USB: serial: option: add Telit LE910C1-EUX compositions
  USB: serial: ch341: add basis for quirk detection
  iio:chemical:sps30: Fix timestamp alignment
  iio: vcnl4000: Fix i2c swapped word reading.
  iio:chemical:pms7003: Fix timestamp alignment and prevent data leak.
  iio: adc: stm32-adc: fix a wrong error message when probing interrupts
  usb: musb: start session in resume for host port
  usb: musb: Fix runtime PM imbalance on error
  vt: keyboard: avoid signed integer overflow in k_ascii
  tty: hvc_console, fix crashes on parallel open/close
  staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK
  CDC-ACM: heed quirk also in error handling
  nvmem: qfprom: remove incorrect write support
  uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned
  Revert "net/mlx5: Annotate mutex destroy for root ns"
  Linux 5.4.46
  UBUNTU: upstream stable to v5.4.46

  -

  Note:  The following commits from v5.4.46 had already been applied as
  UBUNTU SAUCE patches:

  590459086bc9 x86/speculation: Add Ivy Bridge to affected list
  faf187abda94 x86/speculation: Add SRBDS vulnerability and mitigation 
documentation
  b0f61a0503ad x86/speculation: Add Special Register Buffer Data Sampling 
(SRBDS) mitigation
  dab0161b8a0b x86/cpu: Add 'table' argument to cpu_matches()
  749ec6b48a9a x86/cpu: Add a steppings field to struct x86_cpu_id
  e4e57f7bca44 x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2

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

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

[Kernel-packages] [Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release

[Khaled El Mously]

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

Title:
  Freezing on boot since kernel 4.15.0-72-generic release

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

Bug description:
  [SRU Justification]

  [Impact]
  In bug 1840239, HPET is disabled on some systems for they caused TSC
  being marked unstable while it is not. This caused an regression as bug
  1851216 that some systems may then hang at early, so a fix cherry picked
  back from v5.3-rc1. However, this fix also introduce yet another
  regression that some other users may hang at boot while PIT is diabled
  in the previous fix.

  [Fix]
  Commit 979923871f69 ("x86/timer: Don't skip PIT setup when APIC is
  disabled or in legacy mode") from v5.6-rc1, also backported to v5.4.19
  and v5.5.3, fixes PIT setup in this case.

  [Test Case]
  Simply boot a patch kernel on systems affected and it shouldn't hang.

  [Regression Potential]
  Low. Stable patch and trivial backport.

  [Other Info]
  The same fix for bug 1851216 was also backported to Disco and Eoan, but
  they were then fixed with this 979923871f69 commit backported in bug
  1866858 and bug 1867051, which pulls v5.4 stable patches into Disco and
  Eoan correspondingly, leaving B/OEM-B the only victims so far.

  == Original Bug Description ==

  After the update to install kernel 4.15.0-72-generic (a bit over a week ago) 
my computer will not boot. On boot, all I see is the purple screen with:
  Loading Linux 4.15.0-72-generic ...
  Loading initial ramdisk ...
  and nothing happens. Just sits there. I've waited about 5-10 minutes on 
occasion but to no avail.
  I've checked a number of logs in /var/log but not found anything.

  If I go into the advanced options and select kernel
  4.15.0-70-generic, the computer boots normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tony   1977 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 14 21:53:14 2019
  HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1
  InstallationDate: Installed on 2018-09-16 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GIGABYTE Sabre 17WV8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-70-generic N/A
   linux-backports-modules-4.15.0-70-generic  N/A
   linux-firmware 1.173.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Sabre 17WV8
  dmi.board.vendor: GIGABYTE
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: GIGABYTE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A:
  dmi.product.family: Sabre
  dmi.product.name: Sabre 17WV8
  dmi.product.version: Not Applicable
  dmi.sys.vendor: GIGABYTE

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

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

Re: [Kernel-packages] [Bug 1885330] Re: System unresponsive to keyboard and mouse clicks when changing screen background

[Lester Potter]

Switched to the NVIDIA proprietary driver and the problem is solved.
This can be closed.

On Tue, Jun 30, 2020 at 10:10 PM Daniel van Vugt <1885...@bugs.launchpad.net>
wrote:

> Please open the 'Additional Drivers' app and try installing a graphics
> driver from Nvidia instead.
>
> ** Summary changed:
>
> - System unresponsive to keyboard and mouse clicks when changing screen
> background
> + [nouveau] System unresponsive to keyboard and mouse clicks when changing
> screen background
>
> ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
>
> ** Tags added: nouveau
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1885330
>
> Title:
>   [nouveau] System unresponsive to keyboard and mouse clicks when
>   changing screen background
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Right click on screen background and choose settings.
>   Then click a different background.
>   System becomes unresponsive to keyboard input and mouse clicks.
>   System returns to responsiveness after about 10 minutes.
>
>   Description:  Ubuntu 20.04 LTS
>   Release:  20.04
>
>   CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz
>   Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%)
>   Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38
>
>   Expected behavior:
>   Changing the background happens immediately and system remains
> responsive to input.
>
>   What happened:
>   System did not change the background immediately and became unresponsive
> to keyboard and mouse input for 10 minutes at which point the background
> changed to the selected one and responsiveness returned.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-control-center 1:3.36.2-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
>   Uname: Linux 5.4.0-37-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.3
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Jun 26 15:50:44 2020
>   ExecutablePath: /usr/bin/gnome-control-center
>   InstallationDate: Installed on 2020-06-13 (13 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-control-center
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885330/+subscriptions
>

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

Title:
  [nouveau] System unresponsive to keyboard and mouse clicks when
  changing screen background

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1653498] Re: Server reboots every 4.1 weeks

[chudihuang]

Hi,

We have the same issue on our k8s cluster.

Description: ubuntu16.04.1 LTSx86_64
Release: 16.04.1

Kernel: 4.4.0-104-generic

the dump file can be downloaded via following way:
wget http://129.226.115.161/dump.202006231820.tar.gz


I did some analysis, however i still didnot find the root cause:

Load the vmcore in crash (please refer to the hyperlink above). Crash should 
present details similar to the following:
crash> bt
PID: 11388  TASK: 880eb1f79e00  CPU: 29  COMMAND: "heartbeat"
 #0 [8809131a7b08] machine_kexec at 8105c22b
 #1 [8809131a7b68] crash_kexec at 8110e852
 #2 [8809131a7c38] oops_end at 81031c49
 #3 [8809131a7c60] die at 810320fb
 #4 [8809131a7c90] do_trap at 8102f121
 #5 [8809131a7ce0] do_error_trap at 8102f4a9
 #6 [8809131a7da0] do_invalid_op at 8102fa10
 #7 [8809131a7db0] invalid_op at 8184638e
[exception RIP: __fput+541]
RIP: 812126ad  RSP: 8809131a7e68  RFLAGS: 00010246
RAX:   RBX: 880ef6915700  RCX: 000365fb1705
RDX: 0001  RSI: 880fff55a020  RDI: 
RBP: 8809131a7ea0   R8: 0001a020   R9: 811b591d
R10: ea002b69b300  R11: 880ef6915710  R12: 0010
R13: 880ed152aef8  R14: 8800bba18aa0  R15: 880ed1513a40
ORIG_RAX:   CS: 0010  SS: 0018
 #8 [8809131a7e60] __fput at 812125ac
 #9 [8809131a7ea8] fput at 812126ee
#10 [8809131a7eb8] task_work_run at 8109f101
#11 [8809131a7ef8] exit_to_usermode_loop at 81003242
#12 [8809131a7f30] syscall_return_slowpath at 81003c6e
#13 [8809131a7f50] int_ret_from_sys_call at 818449d0
RIP: 0047f704  RSP: 00c423b77c98  RFLAGS: 0246
RAX:   RBX:   RCX: 0047f704
RDX:   RSI:   RDI: 00ca
RBP: 00c423b77ce0   R8:    R9: 
R10:   R11: 0246  R12: 
R13:   R14: 00c423b78ee0  R15: 0008
ORIG_RAX: 0003  CS: 0033  SS: 002b
crash>

crash> log
[19156101.592212] [ cut here ]
[19156101.593103] kernel BUG at 
/build/linux-SwhOyu/linux-4.4.0/include/linux/fs.h:2582!
[19156101.594385] invalid opcode:  [#1] SMP
[19156101.595083] Modules linked in: binfmt_misc af_packet_diag netlink_diag 
dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag veth br_netfilter 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_set xt_mark ip_set_hash_ipportnet 
ip_set_hash_ipportip ip_set_bitmap_port ip_set_hash_ipport ip_set dummy 
xt_comment xt_addrtype iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 
ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs xt_tcpudp bridge stp llc nf_conntrack_netlink 
nfnetlink xfrm_user xfrm_algo iptable_filter ip_tables xt_conntrack x_tables 
nf_nat nf_conntrack aufs isofs ppdev crct10dif_pclmul parport_pc crc32_pclmul 
input_leds joydev ghash_clmulni_intel parport serio_raw ib_iser rdma_cm iw_cm 
ib_cm ib_sa ib_mad ib_core ib_addr sunrpc iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov
[19156101.606434]  async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear aesni_intel aes_x86_64 glue_helper lrw 
gf128mul ablk_helper cryptd psmouse floppy
[19156101.609129] CPU: 29 PID: 11388 Comm: heartbeat Not tainted 
4.4.0-104-generic #127-Ubuntu
[19156101.610384] Hardware name: Smdbmds KVM, BIOS 
seabios-1.9.1-qemu-project.org 04/01/2014
[19156101.611637] task: 880eb1f79e00 ti: 8809131a4000 task.ti: 
8809131a4000
[19156101.612905] RIP: 0010:[]  [] 
__fput+0x21d/0x220
[19156101.614188] RSP: 0018:8809131a7e68  EFLAGS: 00010246
[19156101.614989] RAX:  RBX: 880ef6915700 RCX: 
000365fb1705
[19156101.616143] RDX: 0001 RSI: 880fff55a020 RDI: 

[19156101.617285] RBP: 8809131a7ea0 R08: 0001a020 R09: 
811b591d
[19156101.618422] R10: ea002b69b300 R11: 880ef6915710 R12: 
0010
[19156101.619574] R13: 880ed152aef8 R14: 8800bba18aa0 R15: 
880ed1513a40
[19156101.620785] FS:  00c42085bc90() GS:880fff54() 
knlGS:
[19156101.622074] CS:  0010 DS:  ES:  CR0: 80050033
[19156101.622921] CR2: 7f508b166b04 CR3: 000e0981b000 CR4: 
003406e0
[19156101.624062] DR0:  DR1:  DR2: 

[19156101.625210] DR3:  DR6: fffe0ff0 DR7: 
0400
[19156101.626349] Stack:
[19156101.626765]  880ed152aef8 880ef6915710 880eb1f79e00 
8210ad50
[19156101.628018]  880ef6915700  880eb1f7a4a0 
8809131a7eb0
[19156101.629305]  812126ee 

[Kernel-packages] [Bug 1880975] Re: Request to include two NUMA related commits in Azure kernels

[Khaled El Mously]

** Changed in: linux-azure (Ubuntu Focal)
   Status: Triaged => Fix Committed

** Changed in: linux-azure (Ubuntu Eoan)
   Status: Triaged => Fix Committed

** Changed in: linux-azure (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  Request to include two NUMA related commits in Azure kernels

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

Bug description:
  Microsoft would like to request the following two commits in all
  releases supported on Azure:

  999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support 
PCI_BUS_RELATIONS2")
  f9ad0f361cf3 ("PCI: hv: Decouple the func definition in hv_dr_state from VSP 
message")

  These two commits will add support for PCI protocol version 1.3.  This
  will allow the host to pass NUMA node information for devices on the
  bus.  Currently it is assumed the NUMA node is 0, which these patches
  will correct.  This functionality will provide an increase in
  performance, especially for HPC and AI workloads.

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

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

[Kernel-packages] [Bug 1885330] Re: System unresponsive to keyboard and mouse clicks when changing screen background

[Daniel van Vugt]

Please open the 'Additional Drivers' app and try installing a graphics
driver from Nvidia instead.

** Summary changed:

- System unresponsive to keyboard and mouse clicks when changing screen 
background
+ [nouveau] System unresponsive to keyboard and mouse clicks when changing 
screen background

** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)

** Tags added: nouveau

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

Title:
  [nouveau] System unresponsive to keyboard and mouse clicks when
  changing screen background

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Right click on screen background and choose settings.
  Then click a different background.
  System becomes unresponsive to keyboard input and mouse clicks.
  System returns to responsiveness after about 10 minutes.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
  Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
  Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

  Expected behavior:
  Changing the background happens immediately and system remains responsive to 
input.

  What happened:
  System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 26 15:50:44 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-06-13 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1885330] [NEW] [nouveau] System unresponsive to keyboard and mouse clicks when changing screen background

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Right click on screen background and choose settings.
Then click a different background.
System becomes unresponsive to keyboard input and mouse clicks.
System returns to responsiveness after about 10 minutes.

Description:Ubuntu 20.04 LTS
Release:20.04

CPU: 8-Core AMD Ryzen 7 1700 (-MT MCP-) speed: 2562 MHz 
Kernel: 5.4.0-37-generic x86_64 Up: 48m Mem: 2370.8/32114.5 MiB (7.4%) 
Storage: 1.82 TiB (5.5% used) Procs: 337 Shell: bash 5.0.16 inxi: 3.0.38 

Expected behavior:
Changing the background happens immediately and system remains responsive to 
input.

What happened:
System did not change the background immediately and became unresponsive to 
keyboard and mouse input for 10 minutes at which point the background changed 
to the selected one and responsiveness returned.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 26 15:50:44 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-06-13 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal
-- 
[nouveau] System unresponsive to keyboard and mouse clicks when changing screen 
background
https://bugs.launchpad.net/bugs/1885330
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 1883670] Update Released

[Brian Murray]

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

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

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

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

[Kernel-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

[Launchpad Bug Tracker]

This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu1

---
alsa-lib (1.2.2-2.1ubuntu1) focal; urgency=medium

  * 
debian/patches/0001-conf-USB-Audio-Add-HP-Thunderbolt-Dock-in-the-IEC958.patch:
- Disable IEC958 on HP Thunderbolt Dock (lp: #1883670)

 -- Kai-Heng Feng   Tue, 16 Jun 2020
17:52:07 +0800

** Changed in: alsa-lib (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

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

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

[Kernel-packages] [Bug 1880792] Update Released

[Brian Murray]

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

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

Title:
  linux-firmware: add sof-firmware and tplg files for tgl machines

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-firmware source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  When booting our 20.04 + oem-5.6 kernel on tgl platforms, the sof
  audio driver always fails to load the sof firmware, the audio function
  deosn't work at all on tgl platforms.

  [Fix]
  Intel released sof-firmware including tplg for tgl platforms, after
  putting them in the /lib/firmware/inte/sof|sof-tplg, the audio works
  well on those tgl platforms.

  [Test Case]
  Put those firmware and tplg to linux-firmware folders, boot 20.04
  + oem-5.6 kernel on tgl platforms, the audio works well.

  [Regression Risk]
  Low, just adding some new files, no change on existing files.

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

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

[Kernel-packages] [Bug 1880792] Re: linux-firmware: add sof-firmware and tplg files for tgl machines

[Launchpad Bug Tracker]

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

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

  * Add sof-firmware and tplg files for tgl machines (LP: #1880792)
- SAUCE: add sof firmware and tplg for tgl platforms

 -- Seth Forshee   Wed, 17 Jun 2020 07:36:48
-0500

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

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

Title:
  linux-firmware: add sof-firmware and tplg files for tgl machines

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-firmware source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  When booting our 20.04 + oem-5.6 kernel on tgl platforms, the sof
  audio driver always fails to load the sof firmware, the audio function
  deosn't work at all on tgl platforms.

  [Fix]
  Intel released sof-firmware including tplg for tgl platforms, after
  putting them in the /lib/firmware/inte/sof|sof-tplg, the audio works
  well on those tgl platforms.

  [Test Case]
  Put those firmware and tplg to linux-firmware folders, boot 20.04
  + oem-5.6 kernel on tgl platforms, the audio works well.

  [Regression Risk]
  Low, just adding some new files, no change on existing files.

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

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

[Kernel-packages] [Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once

[Brian Pontarelli]

I just tried firing up 20200629.0.0 and it has the same issue. I'm also
not able to terminate the VMs at all. I've waiting 10+ minutes for them
to stop and nothing. I eventually just killed the PIDs for everything
VirtualBox related.

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

Title:
  ubuntu/focal64 very slow to boot and reboots once

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Using `ubuntu/focal64` version `20200423.0.0`, the boot process is
  extremely slow and the box always reboots once before completing a
  successful boot.  With default settings, this causes a timeout in
  Vagrant waiting for SSH to be available.  Setting a long enough
  timeout it does eventually boot successfully.  For comparison,
  `ubuntu/bionic64` boots successfully in roughly 10 seconds on my
  machine.

  This appears to be the big hang-up:

  Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] 
enabled
  Apr 23 14:00:12 ubuntu-focal kernel: [   76.448371] printk: console [ttyS0] 
enabled

  I have a hard time telling where exactly it reboots because my
  /var/log/syslog only ends up with the second boot.  I can watch it in
  Virtualbox though and it suddenly reboots, then the second boot
  process runs to completion.  The long delay shown above happens both
  times making the total time to a successful boot very long.  Here is
  the head of my /var/log/syslog:

  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel 
File Systems.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File 
System...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild 
Hardware Database being skipped.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform 
Persistent Storage Archival being skipped.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users...
  Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting 
net/ipv4/conf/all/promote_secondaries (explicit setting exists).
  Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting 
net/ipv4/conf/default/promote_secondaries (explicit setting exists).
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File 
System.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent 
Storage.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables.
  Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group 
systemd-coredump with gid 999.
  Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete 
Device Initialization...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes 
in /dev...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes 
in /dev.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device 
Manager...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager.
  Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 
5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 
9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 (
  Ubuntu 5.4.0-26.30-generic 5.4.30)
  Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro 
console=tty1 console=ttyS0

  
  Subsequent boots are also slow but don't seem to have the extra reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 16:02 seq
   crw-rw 1 root audio 116, 33 May  7 16:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  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
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  IwConfig: 

[Kernel-packages] [Bug 1876699] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  add 16-bit width registers support for EEPROM at24 device

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

Bug description:
  SRU For Bionic

  [Impact]
  Larger EEPROM devices that use 16-bit addresses couldn't be accessed.

  The i2c/smbus currently only support to access data with 8-bit width of
  address. In some larger device, such as larger EEPROM, it requires to
  access the address large than 0xff, so it needs to extend address space
  to 16-bit width.

  [Fix]
  This commit is derivated from below commit, and then modified and provided
  by customer
  https://patchwork.ozlabs.org/patch/545292/

  Unfortunately, this commit doesn't get into mainline in the end, so I migrate 
the commit to latest kernel and finally get it merged.
  https://lkml.org/lkml/2020/4/24/635

  [Test]
  Verified on Eurotech's platforms.

  [Regression Potential]
  Low, this patch only changes the behavior of the device which has 
AT24_FLAG_ADDR16 flag and change the page_size to 64 if the device name is 
24c256.

  =
  SRU For Focal

  [Impact]
  Larger EEPROM devices that use 16-bit addresses couldn't be accessed.

  The i2c/smbus currently only support to access data with 8-bit width of
  address. In some larger device, such as larger EEPROM, it requires to
  access the address large than 0xff, so it needs to extend address space
  to 16-bit width.

  [Fix]
  Clear cherry pick from linux-next
  82f25bd73c0b regmap-i2c: add 16-bit width registers support

  [Test]
  Verified on Eurotech's platforms.

  [Regression Potential]
  Low, this patch provides new access functions for 16-bit registers,
  shouldn't affect any other devices which are already working well.

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

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

[Kernel-packages] [Bug 1802691] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Slow send speed with Intel I219-V on Ubuntu 18.04.1

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  The throughput measured by iperf3 is around 70% of 1Gbps (Intel I219-LM
  [8086:15b7])
  I219 is a rather cheap NIC and it impacts its throughput if TSO(TCP
  segmentation offload) is enabled.  
  
  [Fix]   
  Disable TSO on NIC and move this task back to CPU fixes this issue.
  The impact of CPU loading is little to none.
  On target machine with Xeon(R) CPU E3-1505L v6 @ 2.20GHz(4c8t), the CPU
  usage of iperf3 increases from 1% to 4%
  
  [Verify]
  Origin
  [ ID] Interval Transfer Bandwidth Retr
  [ 4] 0.00-10.00 sec 918 MBytes 770 Mbits/sec 0 sender
  [ 4] 0.00-10.00 sec 916 MBytes 769 Mbits/sec receiver

  Becomes
  [ ID] Interval Transfer Bandwidth Retr
  [ 4] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec 0 sender
  [ 4] 0.00-10.00 sec 1.09 GBytes 934 Mbits/sec receiver

  [Regression Potential]
  Low, disable TSO on Ethernet chip will move the TCP segmentation task
  to CPU. This increase CPU loading a little bit, and should not introduce
  any regression. 

  =

  Testing with iperf3 send speed is only 750mbps while receive speed is
  normal - 940mbps.

  Ubuntu 18.04.1
  Msi b250m mortar
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  django 1016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp0s31f6  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7A69
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/29/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M MORTAR ARCTIC (MS-7A69)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A69
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1873325] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  update-initramfs complains of missing amdgpu firmware files

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

Bug description:
  SRU Justification

  Impact: amdgpu references firmware files in modinfo which have not
  been supplied to linux-firmware. This causes update-initramfs to
  generate "Possible missing firmware" warnings.

  Fix: Since the firmware is not available, all we can do is remove the
  files from modinfo.

  Test Case: Confirm that update-initramfs no longer produces the
  warnings.

  Regression Potential: Low. If someone had managed to obtain these
  files they will no longer be added to the initramfs, potentially
  causing regressions for these users. This would be an atypical
  situation.

  ---

  Ubuntu 20.04 during initramfs update reports missing firmware files:
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module 
amdgpu

  Kernel: 5.4.0-24-generic
  linux-firmware: 1.187

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

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

[Kernel-packages] [Bug 1867900] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  CPU stress test fails with focal kernel

Status in kunpeng920:
  Triaged
Status in kunpeng920 ubuntu-18.04-hwe series:
  Triaged
Status in kunpeng920 ubuntu-20.04 series:
  Triaged
Status in kunpeng920 upstream-kernel series:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  We have several crypto accelerators for Hisilicon 1620 but unfortunately one 
of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 
makes kernel to run crypto functions without accelerator.

  [Fix]
  Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver.

  [Test]
  $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz 
--times --af-alg 0
  $ echo $?

  [Regression Potential]
  This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other 
platform.

  ==
  [Bug Description]
  CPU stress test fails with focal kernel

  [Steps to Reproduce]
  1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable
  2) sudo apt-add-repository -y ppa:hardware-certification/public
  3) sudo apt install -y canonical-certification-server
  4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux
  5) Run CPU stress test with `sudo certify-advanced`

  [Actual Results]
  Failed with
  stress-ng: fail:  [6118] stress-ng-af-alg: bind failed, errno=19 (No such 
device)

  [Expected Results]
  Passed

  [Reproducibility]
  100%

  [Additional information]
  Same test with bionic-update kernel passed

  [Resolution]

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

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

[Kernel-packages] [Bug 1876361] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.36 upstream stable release

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

Bug description:
  SRU Justification

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

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

  ext4: fix extent_status fragmentation for plain files
  f2fs: fix to avoid memory leakage in f2fs_listxattr
  net, ip_tunnel: fix interface lookup with no key
  UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1542419
  arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419
  arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419
  arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space
  arm64: Silence clang warning on mismatched value/register sizes
  tools/testing/nvdimm: Fix compilation failure without 
CONFIG_DEV_DAX_PMEM_COMPAT
  watchdog: reset last_hw_keepalive time at start
  scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login
  scsi: lpfc: Fix crash after handling a pci error
  scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG
  scsi: libfc: If PRLI rejected, move rport to PLOGI state
  ceph: return ceph_mdsc_do_request() errors from __get_parent()
  ceph: don't skip updating wanted caps when cap is stale
  pwm: rcar: Fix late Runtime PM enablement
  nvme-tcp: fix possible crash in write_zeroes processing
  scsi: iscsi: Report unbind session event when the target has been removed
  tools/test/nvdimm: Fix out of tree build
  ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map()
  nvme: fix deadlock caused by ANA update wrong locking
  drm/amd/display: Update stream adjust in dc_stream_adjust_vmin_vmax
  dma-direct: fix data truncation in dma_direct_get_required_mask()
  kernel/gcov/fs.c: gcov_seq_next() should increase position index
  selftests: kmod: fix handling test numbers above 9
  ipc/util.c: sysvipc_find_ipc() should increase position index
  kconfig: qconf: Fix a few alignment issues
  lib/raid6/test: fix build on distros whose /bin/sh is not bash
  s390/cio: generate delayed uevent for vfio-ccw subchannels
  s390/cio: avoid duplicated 'ADD' uevents
  loop: Better discard support for block devices
  Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs 
enabled"
  powerpc/pseries: Fix MCE handling on pseries
  nvme: fix compat address handling in several ioctls
  pwm: renesas-tpu: Fix late Runtime PM enablement
  pwm: bcm2835: Dynamically allocate base
  perf/core: Disable page faults when getting phys address
  drm/amd/display: Calculate scaling ratios on every medium/full update
  ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet
  ALSA: usb-audio: Add Pioneer DJ DJM-250MK2 quirk
  drm/amd/display: Not doing optimize bandwidth if flip pending.
  cxgb4: fix adapter crash due to wrong MC size
  cxgb4: fix large delays in PTP synchronization
  ipv4: Update fib_select_default to handle nexthop objects
  ipv6: fix restrict IPV6_ADDRFORM operation
  macsec: avoid to set wrong mtu
  macvlan: fix null dereference in macvlan_device_event()
  mlxsw: Fix some IS_ERR() vs NULL bugs
  net: bcmgenet: correct per TX/RX ring statistics
  net/mlx4_en: avoid indirect call in TX completion
  net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node
  net: openvswitch: ovs_ct_exit to be done under ovs_lock
  net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array
  net/x25: Fix x25_neigh refcnt leak when receiving frame
  sched: etf: do not assume all sockets are full blown
  selftests: Fix suppress test in fib_tests.sh
  tcp: cache line align MAX_TCP_HEADER
  team: fix hang in team_mode_get()
  vrf: Fix IPv6 with qdisc and xfrm
  net: dsa: b53: Lookup VID in ARL searches when VLAN 

[Kernel-packages] [Bug 1874055] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [UBUNTU 20.04] s390x/pci: s390_pci_mmio_write/read fail when MIO
  instructions are available

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Code that is using s390_pci_mmio_write/read system calls on a z15
  (that comes with enhanced PCI load/store instructions), fails with
  "Unable to handle kernel pointer dereference in virtual kernel address
  space".

  * This issue happens if enablement for z15 PCI enhancements is in
  place and where customers run workloads which access PCI adapters from
  user space, like RoCE/RDMA.

  * To solve this, the system call implementation needs to be improved to 
execute the enhanced PCI load/store instructions on behalf of the user space 
application,
    making use of the mappings into its virtual address space.

  [Fix]

  * f058599e22d59e594e5aae1dc10560568d8f4a8b f058599e22d5 "s390/pci: Fix
  s390_mmio_read/write with MIO"

  [Test Case]

  * Setting up a z15 with at least one PCI card (like RoCE) using an
  operating system that includes support and enablement for z15 (line
  20.04).

  * Install the rdma tools: sudo apt install ibverbs-providers ibverbs-
  utils

  * Verify you have some RDMA devices (requires ConnectX adapter)
    $ ibv_devices
    device node GUID
    -- 
    mlx5_0 98039b0300c682b4

  * Verify MIO instructions are enabled for the device
    $ cat /sys/bus/pci/devices/\:00\:00.0/mio_enabled
    1

  * Try to run an RDMA application from user space, e.g. ibv_rc_pingpong
    server side:
    ibv_rc_pingpong -d mlx5_0 -g 0 &
    client side:
    ibv_rc_pingpong -d mlx5_0 -g 0 localhost

  * Verify whether the kernel crashes or not.

  * Verification needs to be done by IBM on z15 hardware.

  [Regression Potential]

  * There is some regression potential with having code changes in the
  zPCI sub-system (zPCI is limited to s390x)

  * It could be that zPCI hardware get harmed, but zPCI hardware is not
  as wide-spread on s390x than ccw hardware components.

  * Only z15 hardware is affected - no other s390x hardware that is
  supported by Ubuntu.

  * However, the zPCI system is s390x only and the patch was accepted upstream 
with v5.7-rc7 and Linus commented: "And none of the fixes look like there's 
anything particularly scary going on. Most of it is very small, and the 
slightly larger patches aren't huge either and are well-contained (the two 
slightly larger patches are to s390 and rxrpc - and even those patches aren't 
really all _that_ big)"
  __

  One of the PCI enhancements on Z15 are the enhanced PCI load/store
  instructions which can be executed directly from user space code. When
  these instructions are available and preexisting user space code still
  uses the old s390_pci_mmio_write/read system calls, the system calls
  fail with an "Unable to handle kernel pointer dereference in virtual
  kernel address space" in the kernel.  This issue affects distributions
  which have the enablement for Z15 PCI enhancements and where customers
  run workloads which accesses PCI adapters from user space, e.g. RDMA
  applications.  To solve this, the system call implementation needs to
  be enhanced to provide to execute enhanced PCI load/store instructions
  on behalf of the user space application making use of the mappings
  into its virtual address space

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

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

[Kernel-packages] [Bug 1876044] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [UBUNTU 20.04] PSI generates overhead on s390x

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * PSI is enabled by default for all architectures in Ubuntu.

  * On s390x this leads to performance degradations on popular workloads
  like web serving (nginx).

  [Fix]

  * Leave 'CONFIG_PSI=y', but change 'CONFIG_PSI_DEFAULT_DISABLED=n' to
  'CONFIG_PSI_DEFAULT_DISABLED=y'

  [Test Case]

  * Measure the overhead with 'CONFIG_PSI_DEFAULT_DISABLED=n' and
  'CONFIG_PSI_DEFAULT_DISABLED=y' on the same environment with nginx.

  [Regression Potential]

  * The regression potential can be considered as moderate, since PSI
  (Pressure stall information tracking),

  * since PSI is just used to collect CPU overcommitted, memory and IO
  metrics.

  * And it can be enabled again with the kernel argument.
  __

  PSI is always enabled in Ubuntu 20.04.
  For a test system with 72 guests on 8 cores running a nginx workload this 
created an overhead of ~1%.

  Can we change this back to
  CONFIG_PSI=y
  CONFIG_PSI_DEFAULT_DISABLED=y

  so that by default the overhead is not there but for debugging or if
  needed it can still be enabled via kernel parm?

  Maybe there has been a reason for this - so feel free to discuss.

  ---uname output---
  Linux t35lp76 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = All s390x architecture

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

  ---Steps to Reproduce---
   root@t35lp76:/boot# grep PSI config-5.4.0-26-generic
  CONFIG_PSI=y
  # CONFIG_PSI_DEFAULT_DISABLED is not set

  Stack trace output:
   no

  Oops output:
   no

  System Dump Info:
    The system is not configured to capture a system dump.

  *Additional Instructions for epasch@de,ibm.com:
  -Attach sysctl -a output output to the bug.

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

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

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

Xenial
==

original:


$ uname -rv
4.4.0-185-generic #215-Ubuntu SMP Mon Jun 8 21:53:19 UTC 2020

$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 5.4, x86_64 Linux 4.4.0-185-generic) 

$ ./stress-ng --af-alg 0 --timeout 30m 2>&1 | tee 
../stress-ng.log.xenial.orig
stress-ng: info:  [11823] dispatching hogs: 11 af-alg
stress-ng: info:  [11825] stress-ng-af-alg: 52 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [11825] stress-ng-af-alg: 105 cryptographic 
algorithms max (with defconfigs)
stress-ng: info:  [11823] successful run completed in 1800.31s (30 
mins, 0.31 secs)


modified:


$ uname -rv
4.4.0-185-generic #215+test20200630b1 SMP Tue Jun 30 18:46:39 -03 2020

$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 5.4, x86_64 Linux 4.4.0-185-generic) 

$ ./stress-ng --af-alg 0 --timeout 30m 2>&1 | tee 
../stress-ng.log.xenial.mod
stress-ng: info:  [12286] dispatching hogs: 11 af-alg
stress-ng: info:  [12288] stress-ng-af-alg: 52 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [12288] stress-ng-af-alg: 105 cryptographic 
algorithms max (with defconfigs)
stress-ng: info:  [12286] successful run completed in 1800.38s (30 
mins, 0.38 secs)

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 

[Kernel-packages] [Bug 1865988] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Performing function level reset of AMD onboard USB and audio devices
  causes system lockup

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justifcation]

  [Impact]

  Devices affected:

  * [1022:148c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Starship
USB 3.0 Host Controller
  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse
USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse HD Audio Controller

  Despite advertising FLReset device capabilities, performing a function level
  reset of either of these devices causes the system to lock up. This is of
  particular issue where these devices appear in their own IOMMU groups and are
  well suited to VFIO passthrough.

  Issue was introduced in AMD's "AGESA Combo-AM4 1.0.0.4 Patch B" microcode
  update, and affects dozens of motherboard models across various vendors.

  Additional discussion of this issue:
  
https://www.reddit.com/r/VFIO/comments/eba5mh/workaround_patch_for_passing_through_usb_and/

  [Fix]

  Two commits currently landed in linux-pci pci/virutualization:
  * 0d14f06cd665 PCI: Avoid FLR for AMD Matisse HD Audio & USB 3.0
  * 5727043c73fd PCI: Avoid FLR for AMD Starship USB 3.0

  [Test Case]

  Peform the test on an impacted system:

  * B350, B450, X370, X470, X570 motherboards (practically anything with an AM4
socket);
  * Ryzen 3000-series CPU (2000-series possibly also affected);
  * BIOS/UEFI firmware that includes "AGESA Combo-AM4 1.0.0.4 Patch B" (check
vendor release notes)

  In the above case where ':10:00.3' is the USB controller '1022:149c', 
issue
  a reset command:

$ echo 1 | sudo tee /sys/bus/pci/devices/\:10\:00.3/reset

  Impacted systems will not return successfully and become unstable, requiring a
  reboot. `/var/logs/syslog` will show something resembling the following:

xhci_hcd :10:00.3: not ready 1023ms after FLR; waiting
xhci_hcd :10:00.3: not ready 2047ms after FLR; waiting
xhci_hcd :10:00.3: not ready 4095ms after FLR; waiting
xhci_hcd :10:00.3: not ready 8191ms after FLR; waiting
xhci_hcd :10:00.3: not ready 16383ms after FLR; waiting
xhci_hcd :10:00.3: not ready 32767ms after FLR; waiting
xhci_hcd :10:00.3: not ready 65535ms after FLR; giving up
clocksource: timekeeping watchdog on CPU14: Marking clocksource 'tsc' as 
unstable because the skew is too large:
clocksource: 'hpet' wd_now: f63fcfe wd_last: d468894 mask: 
clocksource: 'tsc' cs_now: 60e67e17758 cs_last: 60d2a81ce24 mask: 

tsc: Marking TSC unstable due to clocksource watchdog
TSC found unstable after boot, most likely due to broken BIOS. Use 
'tsc=unstable'.
sched_clock: Marking unstable (1817664630139, 314261908)<-(1817981099530, 
-2209419)

  [Regression Risk]
  Low. These two patches affect only systems with a device needs fix.

  == Original Bug Description ==

  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  [Impact]

  Devices affected:

  * [1022:149c] USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] 
Matisse USB 3.0 Host Controller
  * [1022:1487] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] 
Starship/Matisse HD Audio Controller

  Despite 

[Kernel-packages] [Bug 1876667] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Add support for Ambiq micro AM1805 RTC chip

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

Bug description:
  [Impact]
  To enable Ambiq micro AM1805 RTC chip

  [Fix]
  The patch is provided by Eurotech.
  Eurotech doesn't want to upstream this driver, because there are some 
functions are used by Eurotech's platforms only.

  [Test]
  Verified on Eurotech's machine and it works well.

  [Regression Potential]
  Low, it's a standalone file/driver, so no regression could be introduced.

  [Misc]
  We only need this driver in Bionic kernel, but for future possible projects, 
SRU this to Focal kernel, too.

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

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

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

Disco: testing
=

original:


$ uname -rv
5.0.0-38-generic #41-Ubuntu SMP Tue Dec 3 00:27:35 UTC 2019

$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 8.3, x86_64 Linux 5.0.0-38-generic) 

$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.disco.orig
stress-ng: info:  [13699] dispatching hogs: 11 af-alg
stress-ng: info:  [13701] stress-ng-af-alg: 63 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [13701] stress-ng-af-alg: 102 cryptographic 
algorithms max (with defconfigs)
stress-ng: info:  [13699] successful run completed in 3600.49s (1 hour, 
0.49 secs)


modified:


$ uname -rv
5.0.0-56-generic #60+test20200630b1 SMP Tue Jun 30 14:12:46 -03 2020

$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.disco.mod
stress-ng: info:  [2101] dispatching hogs: 11 af-alg
stress-ng: info:  [2103] stress-ng-af-alg: 63 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [2103] stress-ng-af-alg: 102 cryptographic algorithms 
max (with defconfigs)
stress-ng: info:  [2101] successful run completed in 3600.48s (1 hour, 
0.48 secs)

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

Common to all test runs: stress-ng version,
and command to load as many crypto modules
as found/possible in the system.

$ ./stress-ng --version
stress-ng, version 0.11.14 () 

$ sudo modprobe -a \
  $(modinfo \
  /lib/modules/$(uname -r)/kernel/crypto/*.ko \
  /lib/modules/$(uname -r)/kernel/arch/*/crypto/*.ko \
  | grep -ow 'crypto-.*')

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
   af_alg_accept+0x81/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  general protection fault:  [#1] SMP PTI
  ...
  RIP: 0010:__release_sock+0x54/0xe0
  ...
  Call Trace:
   release_sock+0x30/0xa0
   af_alg_accept+0x122/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

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

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

[Kernel-packages] [Bug 1872726] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [Ubuntu 20.04] net/mlx5e: Fix endianness handling in pedit mask

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * An issue with the endianess handling in the Mellanox mlx5 driver was
  found.

  * The mask value is provided as 64 bit and has to be casted in either
  32 or 16 bit.

  * On big endian systems the wrong half was casted which resulted in an
  all zero mask.

  [Fix]

  * Backport: https://launchpadlibrarian.net/476243025/0001-net-mlx5
  -fix-endianness-handling-in-pedit-mask.patch

  [Test Case]

  * An s390x system with RoCE Express 2(.1) system is needed and the
  driver loaded.

  * Check whether the mask value stays zero, or if it also get's non-
  zero values.

  * Functional testing is currently only doable by IBM, since we only
  have RoCE (1) hardware that uses the mlx4 driver.

  [Regression Potential]

  * There is regression potential is moderate, since:

  * the RoCE 2(.1) cards are pretty new and not very wide spread, yet

  * the fix got already upstream accepted with 5.6

  * However, at the end the patch modifies Mellanox common code
  (drivers/net/ethernet/mellanox/mlx5/core/en_tc.c) to make the driver
  work correctly on s390x.

  * but the changes were reviewed, signed off by Mellanox engineers and
  are very limited.

  [Other Info]

  * The above backport (patch-file) is based on commit
  404402abd5f90aa90a134eb9604b1750c1941529 404402abd5f9 "net/mlx5e: Fix
  endianness handling in pedit mask" - the backport was needed for
  getting it applied to focal master-next.

  * The commit itself got upstream accepted with kernel v5.6, hence
  should automatically land in 'gorilla', but since gorilla is still
  based on 5.4, I'm adding 'G' to this SRU.

  __

  Issue found in the Mellanox mlx5 device driver:

  The mask value is provided as 64 bit and has to be casted in
  either 32 or 16 bit. On big endian systems the wrong half was
  casted which resulted in an all zero mask.

  We need to get the upstream commit picked up for the Ubuntu 20.04
  kernel.

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=404402abd5f90aa90a134eb9604b1750c1941529

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

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

[Kernel-packages] [Bug 1861610] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.6 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Touchpad function unavailable on some platforms with new ELAN touchpad
  HIDs.

  [Fix]
  
https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/
  required to match these currently unsupported IDs.

  [Test Case]
  1. check if platform is affected, e.g. with ELAN0634:

 $ sudo acpidump | grep -C3 ELAN
 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF
 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._
 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2.
 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634..
 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U
 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h.
 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions

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

[Kernel-packages] [Bug 1875665] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-riscv package in Ubuntu:
  Fix Released
Status in rtkit package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Released
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-gcp source package in Focal:
  Fix Released
Status in linux-kvm source package in Focal:
  Fix Released
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-riscv source package in Focal:
  Fix Released
Status in rtkit source package in Focal:
  Confirmed

Bug description:
  SRU Justification

  Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the
  lowlatency kernel since we expected most RT users to use that kernel.
  However we are getting RT regressions with the generic kernel. Digging
  deeper into this option, it seems to be pretty specialized and to
  require quite a bit of workload-specific configuration/tuning to be
  useful, so it doesn't really seem to make sense for a general-purpose
  kernel.

  Fix: Turn this option back off.

  Test Case: See comment #4.

  Regression Potential: This was turned on to support some docker
  functionality, so this functionality will no longer be available.
  We've had this option off for all releases prior to focal, so this
  seems acceptable.

  ---

  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

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

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

[Kernel-packages] [Bug 1875863] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  ceph -- Unable to mount ceph volume on s390x

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Unable to mount ceph volumes on big endian systems, like s390x.

  * The mount operation always fails with an IO error.

  * This is caused by an endiness issue in function handle_session where
  variable features is always little endian.

  * But test_bit assumes the host order of bytes, hence causes a problem
  on big endian systems.

  [Fix]

  * 0fa8263367db9287aa0632f96c1a5f93cc478150 0fa8263367db "ceph: fix
  endianness bug when handling MDS session feature bits"

  [Test Case]

  * Setup ceph on s390x.

  * Try to mount a ceph volume.

  * If it mounts correctly the patch is applied and working.

  * Without the patch a mount always fails on big endian / s390x.

  [Regression Potential]

  * There is regression potential with having code changes in ceph's
  session handler, which is common code.

  * However, the patch was accepted (slightly changed) by the ceph
  maintainers and with that got upstream accepted, too.

  * The patch is fairly limited (5 lines removed, 3 added), hence the
  changes are quite traceable.

  __

  When mounting a ceph volume, mount operation fails with an IO error.
  The problem is always reproducible.

  Identified potential root cause as kernel endian bug:

  In the function handle_session() variable @features always
  contains little endian order of bytes. Just because The feature
  mask sent by the MDS is little-endian (bits are packed bytewise
  from left to right in encode_supported_features()).

  However, test_bit(), called to check features availability, assumes
  the host order of bytes in that variable. This leads to problems on
  big endian architectures. Specifically it is impossible to mount
  ceph volume on s390.

  A fixup was proposed to convert little-endian order of bytes to the
  host one. That fixup was modified by ceph maintainers to use existing
  unpacking means for the conversion. The resulted patch attached.

  Related discussion in the ceph-development mailing list:
  https://marc.info/?l=ceph-devel=158815357301332=2

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

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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  New
Status in linux source package in Precise:
  Fix Committed
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  New
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  New

Bug description:
  Ongoing packing resyncs.

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

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

[Kernel-packages] [Bug 1874698] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left]
  Recording problem

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Released

Bug description:
  This is for alsa-ucm-conf:

  The patches are already in the mainline alsa-ucm-conf, so only
  sent the SRU for focal

  [Impact]
  On the machines without Intel HDMI, the sof driver will fail to initialize.

  [Fix]
  After fixing the kernel, we also need to change the ucm2 to make it
  support the machine without Intel hdmi audio.

  [Test Case]
  Boot the kernel on the machines without Intel HDMI audio, everything
  works well including the audio.

  [Regression Risk]
  Low, these 2 patches are already in the mainline alsa-ucm-conf. And we
  already tested them on 4 HP machines.

  
  This is for linux kernel:

  The patch is already in the oem-5.6 kernel and unstable kernel, so only
  sent the SRU for focal

  [Impact]
  On the machines without Intel HDMI, the sof driver will fail to initialize.

  [Fix]
  Intel upstream 2 patches in the kernel to fix it.

  [Test Case]
  Boot the kernel on the machines without Intel HDMI audio, everything
  works well including the audio.

  [Regression Risk]
  Low, these 2 patches are already in the mainline kernel.

  On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy
  output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa-
  base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that
  now "snd-hda-intel" is loaded instead of sof-audio-pci. While the
  speakers are working fine, I do not have the internal microphone
  working (suspect a digital array).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wittawat   2063 F pulseaudio
   /dev/snd/controlC0:  wittawat   2063 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 12:42:32 2020
  InstallationDate: Installed on 2020-04-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Mic, Left
  Symptom_Type: None of the above
  Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] 
Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8600
  dmi.board.vendor: HP
  dmi.board.version: 44.41
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 15-dh0xxx
  dmi.product.sku: 7JX54EA#ABD
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996

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

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

[Kernel-packages] [Bug 1868551] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Intel GPU Hangs : random screen freezing w/ Ubuntu 20.04 (Linux 5.4)
  i915_active_acquire

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

Bug description:
  SRU Justification:

  [Impact]
  Users are experiencing a frequent NULL pointer dereference crash in 
i915_active_acquire when using kms, which is used by default.

  [Fix]
  The fix is a cherry pick from upstream which was supposed to be backported to 
5.4 by upstream, but was neglected. The fix has a subsequent Fixes patch to 
resolve some uninitialized pointer usage.

  [Test]
  Verified by multiple bug reporters.

  [Regression Potential]
  Medium. Although there are a lot of lines added, they're mostly boilerplate, 
and this patch is confirmed by multiple users to fix a crash.
  ---
  uname -a
  Linux xps 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  [ 2556.956079] BUG: kernel NULL pointer dereference, address: 0040
  [ 2556.956084] #PF: supervisor read access in kernel mode
  [ 2556.956084] #PF: error_code(0x) - not-present page
  [ 2556.956085] PGD 0 P4D 0
  [ 2556.956088] Oops:  [#1] SMP NOPTI
  [ 2556.956090] CPU: 2 PID: 1685 Comm: xfwm4 Not tainted 5.4.0-14-generic 
#17-Ubuntu
  [ 2556.956092] Hardware name: Dell Inc. XPS 13 7390/0G2D0W, BIOS 1.2.0 
10/03/2019
  [ 2556.956161] RIP: 0010:i915_active_acquire+0xe/0x80 [i915]
  [ 2556.956163] Code: 00 48 c7 c6 11 4d 6b c0 e8 af a1 d6 c7 5d c3 66 66 2e 0f 
1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 
48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31
  [ 2556.956164] RSP: 0018:ac17c13279c8 EFLAGS: 00010286
  [ 2556.956165] RAX:  RBX: 983831d3e480 RCX: 

  [ 2556.956166] RDX: 983783475200 RSI: 983831d3e480 RDI: 
0008
  [ 2556.956167] RBP: ac17c13279e0 R08:  R09: 
98382d6b6520
  [ 2556.956168] R10: 6cc0 R11: 983838b4db00 R12: 
983783475200
  [ 2556.956169] R13: 0008 R14: 983783475200 R15: 
98382d6b6400
  [ 2556.956170] FS:  7f9031c28f00() GS:98383e50() 
knlGS:
  [ 2556.956171] CS:  0010 DS:  ES:  CR0: 80050033
  [ 2556.956172] CR2: 0040 CR3: 00046eac6001 CR4: 
003606e0
  [ 2556.956173] Call Trace:
  [ 2556.956199]  i915_active_ref+0x24/0x200 [i915]
  [ 2556.956223]  i915_vma_move_to_active+0x74/0xf0 [i915]
  [ 2556.956245]  eb_submit+0xff/0x440 [i915]
  [ 2556.956267]  i915_gem_do_execbuffer+0x88e/0xc20 [i915]
  [ 2556.956271]  ? sock_def_readable+0x40/0x70
  [ 2556.956274]  ? __kmalloc_node+0x205/0x320
  [ 2556.956294]  i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915]
  [ 2556.956314]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956330]  drm_ioctl_kernel+0xae/0xf0 [drm]
  [ 2556.956338]  drm_ioctl+0x234/0x3d0 [drm]
  [ 2556.956358]  ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915]
  [ 2556.956361]  ? vfs_writev+0xc3/0xf0
  [ 2556.956363]  do_vfs_ioctl+0x407/0x670
  [ 2556.956365]  ? fput+0x13/0x15
  [ 2556.956367]  ? __sys_recvmsg+0x88/0xa0
  [ 2556.956369]  ksys_ioctl+0x67/0x90
  [ 2556.956371]  __x64_sys_ioctl+0x1a/0x20
  [ 2556.956373]  do_syscall_64+0x57/0x190
  [ 2556.956376]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 2556.956377] RIP: 0033:0x7f9032b3f68b
  [ 2556.956379] Code: 0f 1e fa 48 8b 05 05 28 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d d5 27 0d 00 f7 d8 64 89 01 48
  [ 2556.956380] RSP: 002b:7ffee39a0078 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 2556.956381] RAX: ffda RBX: 55a8abeb6e48 RCX: 
7f9032b3f68b
  [ 2556.956382] RDX: 7ffee39a0090 RSI: 40406469 RDI: 
000d
  [ 2556.956382] RBP: 7ffee39a0120 R08: 0001 R09: 

  [ 2556.956383] R10: 7ffee39a0140 R11: 0246 R12: 
7f9022a4f460
  

[Kernel-packages] [Bug 1874685] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW),
  REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not
  found due to firmware crash

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Fix Released
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [9.924130] iwlwifi :00:14.3: enabling device ( -> 0002)
  [   10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
58.3.35.22
  [   10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
  [   10.031489] iwlwifi :00:14.3: Found debug configuration: 0
  [   10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 
op_mode iwlmvm
  [   10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 
160MHz Wireless Network Adapter (201NGW), REV=0x354
  [   10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
  [   10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware 
monitor.
  [   11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired.
  [   11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [   11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569
  [   11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0
  [   11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT  
  [   11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0
  [   11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1
  [   11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2
  [   11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1
  [   11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2
  [   11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1
  [   11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2
  [   11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3
  [   11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time
  [   11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low
  [   11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi
  [   11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1
  [   11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2
  [   11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type
  [   11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major
  [   11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor
  [   11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version
  [   11.489447] iwlwifi :00:14.3: 0x160C9445 | board version
  [   11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd
  [   11.489460] iwlwifi :00:14.3: 0x022688AB | isr0
  [   11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1
  [   11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2
  [   11.489480] iwlwifi :00:14.3: 0x606C870F | isr3
  [   11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4
  [   11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id
  [   11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event
  [   11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control
  [   11.489518] iwlwifi :00:14.3: 0x06D3D9B3 | l2p_duration
  [   11.489526] iwlwifi :00:14.3: 0x51B4EEA2 | l2p_mhvalid
  [   11.489533] iwlwifi :00:14.3: 0x51B8C323 | l2p_addr_match
  [   11.489540] iwlwifi :00:14.3: 0x81E0114B | lmpm_pmg_sel
  [   11.489548] iwlwifi :00:14.3: 0xF4D75F29 | timestamp
  [   11.489555] iwlwifi :00:14.3: 0x1AFE14FD 

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

Bionic: testing
==

original:


$ uname -rv
4.15.0-107-generic #108-Ubuntu SMP Mon Jun 8 17:51:33 UTC 2020

$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 7.5, x86_64 Linux 4.15.0-107-generic) 

$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.bionic.orig
stress-ng: info:  [13821] dispatching hogs: 11 af-alg
stress-ng: info:  [13823] stress-ng-af-alg: 59 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [13823] stress-ng-af-alg: 105 cryptographic 
algorithms max (with defconfigs)
stress-ng: info:  [13821] successful run completed in 3600.44s (1 hour, 
0.44 secs)

modified:


$ uname -rv
4.15.0-107-generic #108+test20200623b1 SMP Tue Jun 23 09:55:21 -03 2020

$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.bionic.mod
stress-ng: info:  [1551] dispatching hogs: 11 af-alg
stress-ng: info:  [1553] stress-ng-af-alg: 59 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [1553] stress-ng-af-alg: 105 cryptographic algorithms 
max (with defconfigs)
stress-ng: info:  [1551] successful run completed in 3600.44s (1 hour, 
0.44 secs)

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
     

[Kernel-packages] [Bug 1874057] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [UBUNTU 20.04] s390x/pci: do not allow to create more pci functions
  than configured via CONFIG_PCI_NR_FUNCTIONS

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * PCI Functions with UIDs >128 are currently not accounted correctly
  in the s390x/pci (zPCI) code.

  * Furthermore, the code allows that more than CONFIG_PCI_NR_FUNCTIONS
  are created.

  * This can lead to issues with data structures which were only
  allocated for CONFIG_PCI_NR_FUNCTIONS.

  [Fix]

  * https://launchpadlibrarian.net/478235080/0001-s390-pci-Fix-
  zpci_alloc_domain-over-allocation.patch

  [Test Case]

  * Set the kernel parameter CONFIG_PCI_NR_FUNCTIONS to a specific
  (reasonablly low) number.

  * And check if more PCI functions can be created than specified by
  CONFIG_PCI_NR_FUNCTIONS (e.g. using a RoCE adapter) and watch for
  kernel message 'Adding PCI function ... failed'

  [Regression Potential]

  * There is regression potential can be considered as low, since:

  * the zPCI cards are less wide spread than for example ccw adapters on
  s390x

  * the fix got already upstream accepted in 5.7, hence upstream
  reviewed, too

  * the modifications span just two files and both are s390x arch
  specific

  [Other Info]

  * the above patch-file is based on commit
  969ae01bab2fe938b4c8324836038b5ac1c78fac ("s390/pci: Fix
  zpci_alloc_domain() over allocation"), but this backport was needed
  for getting this applied to focal master-next

  * and this patch got upstream accepted with kernel v5.7-rc1, hence on
  the long term it should be in 'gorilla'

  __

  PCI Functions with UIDs >128 are currently not accounted correctly in
  the s390x/pci code. Furthermore, the code allows that more than
  CONFIG_PCI_NR_FUNCTIONS are created. This can lead to issues with data
  structures which were only allocated for CONFIG_PCI_NR_FUNCTIONS.

  This has been fixed in the following upstream commit:

  969ae01bab2fe938b4c8324836038b5ac1c78fac
  ("s390/pci: Fix zpci_alloc_domain() over allocation")

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

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

[Kernel-packages] [Bug 1876859] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Support DMIC micmute LED on HP platforms

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Incomplete
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  DMIC micmute LED on HP platforms doesn't work.

  [Fix]
  Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to 
control micmute.

  [Test]
  After applying the fix, micmute LED can correctly indicate the status of 
micmute.

  [Regression Potential]
  Low. For now it only affects one platform, and it doesn't touch any core part 
of the subsystem.

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

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

[Kernel-packages] [Bug 1866357] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Pop sound from build-in speaker during cold boot and resume from S3

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

Bug description:
  [Description]
  On a Dell Wyse 5070 ThinClient device with 18.04 installed, during cold boot 
and resume from S3, internal speaker will have a noticeable short pop noise.  

  [More detail]
  There are similar bugs reported indicating it's related to codec powersaving 
[1].  On some devices, disable powersaving can workaround it, but the same 
workaround does not work on this device.
  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663

  [Experiment]
  With Ubuntu 16.04 (4.13 kernel) installed --> NO pop noise
  With Ubuntu 16.04.x (4.15 kernel) installed --> pop noise
  With Ubuntu 18.04.x (4.15, 5.0 kernel) installed --> pop noise
  So I started testing kernels between 4.13 and 4.15, found the issue does not 
present before 4.15.0-58 kernel (including 4.15.0-58), and kernel after that 
started to have the pop noise.

  [HW info]
  Codec: Realtek ALC3253
  00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03)


  Device is not with me at this moment, I will provide more info if required.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1901 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-osp1-sanbernardino+X100
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Wyse 5070 Thin Client
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=22fa172b-895b-4061-834e-d616380befc5 ro mem_sleep_default=deep quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-40-generic N/A
   linux-backports-modules-5.3.0-40-generic  N/A
   linux-firmware1.173.9
  Tags:  bionic
  Uname: Linux 5.3.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd01/08/2020:svnDellInc.:pnWyse5070ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.family: Wyse Thin Client 5000 Series
  dmi.product.name: Wyse 5070 Thin Client
  dmi.product.sku: 080C
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

Focal: testing
=

$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 9.3, x86_64 Linux 5.4.0-38-generic) 

$ sudo modprobe -a \
  $(modinfo \
  /lib/modules/$(uname -r)/kernel/crypto/*.ko \
  /lib/modules/$(uname -r)/kernel/arch/*/crypto/*.ko \
  | grep -ow 'crypto-.*')

No error/strange kernel messages logged in /var/log/kern.log.

original:


$ uname -rv
5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC 2020
  
$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.focal.orig
stress-ng: info:  [27052] dispatching hogs: 11 af-alg
stress-ng: info:  [27054] stress-ng-af-alg: 62 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [27054] stress-ng-af-alg: 101 cryptographic 
algorithms max (with defconfigs)
stress-ng: info:  [27052] successful run completed in 3600.38s (1 hour, 
0.38 secs)

modified:


$ uname -rv
5.4.0-38-generic #42+test20200623b1 SMP Tue Jun 23 09:37:56 -03 2020

$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.focal.mod.2
stress-ng: info:  [2577] dispatching hogs: 11 af-alg
stress-ng: info:  [2579] stress-ng-af-alg: 62 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [2579] stress-ng-af-alg: 101 cryptographic algorithms 
max (with defconfigs)
stress-ng: info:  [2577] successful run completed in 3600.52s (1 hour, 
0.52 secs)

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  

[Kernel-packages] [Bug 1875916] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  upgrading to 4.15.0-99-generic breaks the sound and the trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using kubuntu LTS 18.04.
  This morning I was promped to update the kernel to the 4.15.0-99-generic. 

  After the upgrade I did not manage to get any sound. I checked
  everything, pavucontrol, alsamix, everything was in order, the streams
  showed as if they were playing, however I couldn't get any sound from
  the speakers headphones and I could not get any sound recorded either.

  I then rebooted with the previous version of the Kernel, and have my sound 
back without doing anything at all.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4a7a721a-7a2e-4644-a881-34adcb28e1ba
  InstallationDate: Installed on 2019-01-29 (455 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.
   
   wlp108s0  no wireless extensions.
  MachineType: Dell Inc. Latitude 7390 2-in-1
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-99-generic N/A
   linux-backports-modules-4.15.0-99-generic  N/A
   linux-firmware 1.173.17
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0YNG30
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/27/2018:svnDellInc.:pnLatitude73902-in-1:pvr:rvnDellInc.:rn0YNG30:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390 2-in-1
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1874359] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  alsa/sof: kernel oops on the machine without Intel hdmi audio codec (a
  regression in the  asoc machine driver)

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Fix Released

Bug description:
  Please apply the fix for #1872569 first, then apply this patch.

  [Impact]
  The fix for #1872569 introduces a regression, the driver access a
  NULL pointer on the machiens without Intel hdmi audio codec.

  [Fix]
  pick a fixing patch from alsa/asoc repo, the patch doesn't assume
  the first rtd is for hda codec, it will look for that rtd through
  strstr()

  [Test Case]
  Boot the kenrel on those 2 Dell and 2 Lenovo machines which uses
  this driver, the audio could work. disable the intel hdmi audio codec
  through bios, the analogue audio still works

  
  [Regression Risk]
  Low, I have tested this patch Lenovo / Dell machines, they all worked well.

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

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

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

[E/F/Unstable][PATCH 0/1] crypto: fix regression/use-after-free in 
af_alg_accept()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111620.html

[E/F/Unstable][PATCH 1/1] crypto: af_alg - fix use-after-free in 
af_alg_accept() due to bh_lock_sock() 
https://lists.ubuntu.com/archives/kernel-team/2020-June/111621.html

[D][PATCH] crypto: af_alg - fix use-after-free in af_alg_accept() due to 
bh_lock_sock()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111622.html

[B][PATCH] crypto: af_alg - fix use-after-free in af_alg_accept() due to 
bh_lock_sock()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111623.html

[X][PATCH] crypto: af_alg - fix use-after-free in af_alg_accept() due to 
bh_lock_sock()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111624.html

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
   af_alg_accept+0x81/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
   SyS_accept+0x10/0x20
   do_syscall_64+0x73/0x130
   entry_SYSCALL_64_after_hwframe+0x3d/0xa2

  general protection fault:  [#1] SMP PTI
  ...
  RIP: 0010:__release_sock+0x54/0xe0
  ...
  Call Trace:
   release_sock+0x30/0xa0
   af_alg_accept+0x122/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   

[Kernel-packages] [Bug 1874056] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Mellanox CX5 port multi-pathing is broken on s390x due to non-
  standard topology of PCI IDs (phys. and virtual)

  * The Mellanox Connect-X 5 PCI driver (mlx5) implements multi-path
  that can be used to combine multiple networking ports to improve
  performance and reliability.

  * For that purpose, the mlx5 driver combines PCI functions based on
  topology information (the function number) as determined by their PCI
  ID.

  * Currently the Linux on Z PCI bus does not reflect PCI topology
  information in the PCI ID. As a result, the mlx5 multi-path function
  is broken and cannot be activated.

  [Fix]

  * Backport 1: https://launchpadlibrarian.net/479699471/0001-s390-pci-
  Improve-handling-of-unset-UID.patch

  * Backport 2: https://launchpadlibrarian.net/479699482/0002-s390-pci-
  embedding-hotplug_slot-in-zdev.patch

  * Backport 3: https://launchpadlibrarian.net/479699492/0003-s390-pci-
  Expose-new-port-attribute-for-PCIe-function.patch

  * Backport 4: https://launchpadlibrarian.net/479699497/0004-s390-pci-
  adaptation-of-iommu-to-multifunction.patch

  * Backport 5: https://launchpadlibrarian.net/479700706/0005-s390-pci-
  define-kernel-parameters-for-PCI-multifunct.patch

  * Backport 6: https://launchpadlibrarian.net/479700712/0006-s390-pci-
  define-RID-and-RID-available.patch

  * Backport 7: https://launchpadlibrarian.net/479700739/0007-s390-pci-
  create-zPCI-bus.patch

  * Backport 8: https://launchpadlibrarian.net/479700769/0008-s390-pci-
  adapt-events-for-zbus.patch

  * Backport 9: https://launchpadlibrarian.net/479700786/0009-s390-pci-
  Handling-multifunctions.patch

  * Backport 10: https://launchpadlibrarian.net/479700794/0010-s390-pci-
  Do-not-disable-PF-when-VFs-exist.patch

  * Backport 11: https://launchpadlibrarian.net/479700798/0011-s390-pci-
  Documentation-for-zPCI.patch

  * Backport 12: https://launchpadlibrarian.net/479700799/0012-s390-pci-
  removes-wrong-PCI-multifunction-assignment.patch

  [Test Case]

  * Prepare an IBM z13 or LinuxONE III (or newer) system with two or
  more RoCE Express PCI 2(.1) adapters.

  * Assign the adapters (and it's virtual functions) to an LPAR.

  * Verify whether the physical and virtual functions are grouped in
  arbitrary order or in consecutive order - physical first (for example
  with lspci -t ...)

  [Regression Potential]

  * The regression potential can be considered as moderate, since:

  * It is purely s390x specific code (arch/s390/*
  drivers/iommu/s390-iommu.c and drivers/pci/hotplug/s390_pci_hpc.c -
  and some doc adjustments, too).

  * It largely affects zPCI, the s390x specific PCI code layer.

  * PCI cards available for s390x are optional cards (RoCE and zEDC) and
  not very wide-spread.

  * The situation described above affects the RoCE adapters only
  (Mellanox based).

  * The patches are also upstream accepted and available via linux-next,
  but to apply them to focal kernel 5.4 the above backports are needed.

  * However, the code is modified by several patches (12), hence there
  is a chance to break zPCI with them.

  * For upfront testing a PPA got created with a focal (master-next)
  kernel that incl. all the above patches.

  __

  Today, the enumeration of PCI functions on s390x does not reflect
  which functions belongs to which physical adapter.

  Layout of a PCI function address on Linux:
  :00:00.0
  ::.

  On s390x, each function is presented as individual root complex today,
  e.g.:

  PCHID 0100 VF1 :00:00.0
  PCHID 0100 VF23 0001:00:00.0
  PCHID 0200 VF1 0002:00:00.0
  OCHID 0100 VF17 0003:00:00.0

  On other platforms, the addresses correctly reflect the actual HW
  configuration. Some device drivers (mlx5 for Mellanox adapters) group
  functions of one physical adapter by checking which PCI functions have
  identical values for ::. We need to use the
  same enumeration scheme to achieve this functionality on 

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

Eoan: testing


original:


$ uname -rv
5.3.0-62-generic #56-Ubuntu SMP Tue Jun 23 11:20:52 UTC 2020

$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 9.2, x86_64 Linux 5.3.0-62-generic) 

$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.eoan.orig
stress-ng: info:  [10690] dispatching hogs: 11 af-alg
stress-ng: info:  [10692] stress-ng-af-alg: 64 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [10692] stress-ng-af-alg: 101 cryptographic 
algorithms max (with defconfigs)
stress-ng: info:  [10690] successful run completed in 3600.34s (1 hour, 
0.34 secs)

modified:


$ uname -rv
5.3.0-62-generic #56+test20200630b1 SMP Tue Jun 30 12:33:10 -03 2020

$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee 
../stress-ng.log.eoan.mod
stress-ng: info:  [2453] dispatching hogs: 11 af-alg
stress-ng: info:  [2455] stress-ng-af-alg: 64 cryptographic algorithms 
found in /proc/crypto
stress-ng: info:  [2455] stress-ng-af-alg: 101 cryptographic algorithms 
max (with defconfigs)
stress-ng: info:  [2453] successful run completed in 3600.44s (1 hour, 
0.44 secs)

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

Title:
  use-after-free in af_alg_accept() due to bh_lock_sock()

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Eoan:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.

   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()

  [Fix]

   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.

   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.

   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.

  [Test Case]

   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.

   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.

   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.

   * More tests performed with 'stress-ng --af-alg'
     with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
     (all on same version of stress-ng, V0.11.14)

     No regressions observed from original kernel.
     (the af-alg stressor can exercise almost all
     kernel crypto modules shipped with the kernel;
     so it checks more paths/crypto alg interfaces.)

  [Regression Potential]

   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.

   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.

   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.

   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.

  [Other Info]

   * Not sending for Groovy (should get via Unstable).

   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d

  [Stack Trace Examples]

  Examples:

  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
   

[Kernel-packages] [Bug 1875660] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.35 upstream stable release

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

Bug description:
  SRU Justification

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

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

  ext4: use non-movable memory for superblock readahead
  watchdog: sp805: fix restart handler
  xsk: Fix out of boundary write in __xsk_rcv_memcpy
  arm, bpf: Fix bugs with ALU64 {RSH, ARSH} BPF_K shift by 0
  arm, bpf: Fix offset overflow for BPF_MEM BPF_DW
  objtool: Fix switch table detection in .text.unlikely
  scsi: sg: add sg_remove_request in sg_common_write
  ALSA: hda: Honor PM disablement in PM freeze and thaw_noirq ops
  ARM: dts: imx6: Use gpc for FEC interrupt controller to fix wake on LAN.
  kbuild, btf: Fix dependencies for DEBUG_INFO_BTF
  netfilter: nf_tables: report EOPNOTSUPP on unsupported flags/object type
  irqchip/mbigen: Free msi_desc on device teardown
  ALSA: hda: Don't release card at firmware loading error
  xsk: Add missing check on user supplied headroom size
  of: unittest: kmemleak on changeset destroy
  of: unittest: kmemleak in of_unittest_platform_populate()
  of: unittest: kmemleak in of_unittest_overlay_high_level()
  of: overlay: kmemleak in dup_and_fixup_symbol_prop()
  x86/Hyper-V: Unload vmbus channel in hv panic callback
  x86/Hyper-V: Trigger crash enlightenment only once during system crash.
  x86/Hyper-V: Report crash register data or kmsg before running crash kernel
  x86/Hyper-V: Report crash register data when sysctl_record_panic_msg is not 
set
  x86/Hyper-V: Report crash data in die() when panic_on_oops is set
  afs: Fix missing XDR advance in xdr_decode_{AFS,YFS}FSFetchStatus()
  afs: Fix decoding of inline abort codes from version 1 status records
  afs: Fix rename operation status delivery
  afs: Fix afs_d_validate() to set the right directory version
  afs: Fix race between post-modification dir edit and readdir/d_revalidate
  block, bfq: turn put_queue into release_process_ref in __bfq_bic_change_cgroup
  block, bfq: make reparent_leaf_entity actually work only on leaf entities
  block, bfq: invoke flush_idle_tree after reparent_active_queues in pd_offline
  rbd: avoid a deadlock on header_rwsem when flushing notifies
  rbd: call rbd_dev_unprobe() after unwatching and flushing notifies
  x86/Hyper-V: Free hv_panic_page when fail to register kmsg dump
  drm/ttm: flush the fence on the bo after we individualize the reservation 
object
  clk: Don't cache errors from clk_ops::get_phase()
  clk: at91: usb: continue if clk_hw_round_rate() return zero
  net/mlx5e: Enforce setting of a single FEC mode
  f2fs: fix the panic in do_checkpoint()
  ARM: dts: rockchip: fix vqmmc-supply property name for rk3188-bqedison2qc
  arm64: dts: allwinner: a64: Fix display clock register range
  power: supply: bq27xxx_battery: Silence deferred-probe error
  clk: tegra: Fix Tegra PMC clock out parents
  arm64: tegra: Add PCIe endpoint controllers nodes for Tegra194
  arm64: tegra: Fix Tegra194 PCIe compatible string
  arm64: dts: clearfog-gt-8k: set gigabit PHY reset deassert delay
  soc: imx: gpc: fix power up sequencing
  dma-coherent: fix integer overflow in the reserved-memory dma allocation
  rtc: 88pm860x: fix possible race condition
  NFS: alloc_nfs_open_context() must use the file cred when available
  NFSv4/pnfs: Return valid stateids in nfs_layout_find_inode_by_stateid()
  NFSv4.2: error out when relink swapfile
  ARM: dts: rockchip: fix lvds-encoder ports subnode for rk3188-bqedison2qc
  KVM: PPC: Book3S HV: Fix H_CEDE return code for nested guests
  f2fs: fix to show norecovery mount option
  phy: uniphier-usb3ss: Add Pro5 support
  NFS: direct.c: Fix memory leak of dreq when nfs_get_lock_context fails
  f2fs: 

[Kernel-packages] [Bug 1876767] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.38 upstream stable release

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

Bug description:
  SRU Justification

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

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

  Note: v5.4.38 itself consisted of a single revert (never committed to
  Ubuntu focal)from v5.4.37 -- so this is just a dummy tracking bug,
  really.

  Linux 5.4.38
  UBUNTU: upstream stable to v5.4.38

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

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

[Kernel-packages] [Bug 1876765] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.37 upstream stable release

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

Bug description:
  SRU Justification

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

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

  remoteproc: Fix wrong rvring index computation
  ubifs: Fix ubifs_tnc_lookup() usage in do_kill_orphans()
  printk: queue wake_up_klogd irq_work only if per-CPU areas are ready
  ASoC: stm32: sai: fix sai probe
  usb: dwc3: gadget: Do link recovery for SS and SSP
  kbuild: fix DT binding schema rule again to avoid needless rebuilds
  usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete
  usb: gadget: udc: atmel: Fix vbus disconnect handling
  afs: Make record checking use TASK_UNINTERRUPTIBLE when appropriate
  afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH
  iio:ad7797: Use correct attribute_group
  propagate_one(): mnt_set_mountpoint() needs mount_lock
  counter: 104-quad-8: Add lock guards - generic interface
  s390/ftrace: fix potential crashes when switching tracers
  ASoC: q6dsp6: q6afe-dai: add missing channels to MI2S DAIs
  ASoC: tas571x: disable regulators on failed probe
  ASoC: wm8960: Fix wrong clock after suspend & resume
  drivers: soc: xilinx: fix firmware driver Kconfig dependency
  nfsd: memory corruption in nfsd4_lock()
  bpf: Forbid XADD on spilled pointers for unprivileged users
  i2c: altera: use proper variable to hold errno
  rxrpc: Fix DATA Tx to disable nofrag for UDP on AF_INET6 socket
  net/cxgb4: Check the return from t4_query_params properly
  xfs: acquire superblock freeze protection on eofblocks scans
  svcrdma: Fix trace point use-after-free race
  svcrdma: Fix leak of svc_rdma_recv_ctxt objects
  net/mlx5e: Don't trigger IRQ multiple times on XSK wakeup to avoid WQ overruns
  net/mlx5e: Get the latest values from counters in switchdev mode
  PCI: Add ACS quirk for Zhaoxin multi-function devices
  PCI: Make ACS quirk implementations more uniform
  PCI: Unify ACS quirk desired vs provided checking
  PCI: Add Zhaoxin Vendor ID
  PCI: Add ACS quirk for Zhaoxin Root/Downstream Ports
  PCI: Move Apex Edge TPU class quirk to fix BAR assignment
  ARM: dts: bcm283x: Disable dsi0 node
  cpumap: Avoid warning when CONFIG_DEBUG_PER_CPU_MAPS is enabled
  s390/pci: do not set affinity for floating irqs
  net/mlx5: Fix failing fw tracer allocation on s390
  sched/core: Fix reset-on-fork from RT with uclamp
  perf/core: fix parent pid/tid in task exit events
  netfilter: nat: fix error handling upon registering inet hook
  PM: sleep: core: Switch back to async_schedule_dev()
  blk-iocost: Fix error on iocost_ioc_vrate_adj
  um: ensure `make ARCH=um mrproper` removes arch/$(SUBARCH)/include/generated/
  bpf, x86_32: Fix incorrect encoding in BPF_LDX zero-extension
  bpf, x86_32: Fix clobbering of dst for BPF_JSET
  bpf, x86_32: Fix logic error in BPF_LDX zero-extension
  mm: shmem: disable interrupt when acquiring info->lock in userfaultfd_copy 
path
  xfs: clear PF_MEMALLOC before exiting xfsaild thread
  bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B
  libbpf: Initialize *nl_pid so gcc 10 is happy
  net: fec: set GPR bit on suspend by DT configuration.
  x86: hyperv: report value of misc_features
  signal: check sig before setting info in kill_pid_usb_asyncio
  afs: Fix length of dump of bad YFSFetchStatus record
  xfs: fix partially uninitialized structure in xfs_reflink_remap_extent
  ALSA: hda: Release resources at error in delayed probe
  ALSA: hda: Keep the controller initialization even if no codecs found
  ALSA: hda: Explicitly permit using autosuspend if runtime PM is supported
  scsi: target: fix PR IN / READ FULL STATUS for FC
  scsi: target: tcmu: reset_ring should reset 

[Kernel-packages] [Bug 1877958] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Do not treat unresolved test case in ftrace from
  ubuntu_kernel_selftests as failure

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  == SRU Justification ==
  There are some test cases in ftrace from ubuntu_kernel_selftests that
  would need some kernel configs to be enabled or have some special HW
  requirements:
* https://pad.lv/1869347 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1869349 - missing CONFIG_SAMPLE_TRACE_PRINTK=m
* https://pad.lv/1874198 - nproc > 1

  If the requirement was not met, these test will fail with "unresolved"
  and return 1. So even these is no failed test case, the ftrace test
  will still be marked as "failed" with the presence of unresolved test:
  # # of passed:  28
  # # of failed:  0
  # # of unresolved:  1
  # # of untested:  0
  # # of unsupported:  58
  # # of xfailed:  0
  # # of undefined(test bug):  0
  not ok 1 selftests: ftrace: ftracetest # exit=1

  == Fix ==
  * b730d668138c ("ftrace/selftest: make unresolved cases cause failure if 
--fail-unresolved set")

  This patch will only make unresolved test case return 1 if we ask it
  to fail with unresolved test case.

  It can be cherry-picked to kernels starting from Disco.
  For Bionic and Xenial it needs to be backported with some context
  adjustment as they're missing some other patches to the testing tool.

  == Test ==
  With the patch applied, the ftrace test will not be marked as failed
  with the presence of unresolved test case:
  # # of passed:  28
  # # of failed:  0
  # # of unresolved:  1
  # # of untested:  0
  # # of unsupported:  58
  # # of xfailed:  0
  # # of undefined(test bug):  0
  ok 1 selftests: ftrace: ftracetest

  == Regression Potential ==
  Low, changes limited to testing tools, no actual impacts to our kernels.

  The worst case is to cause false negative in test reports, but in that
  case it's probably a test case issue since a failed case should be
  treated as a failed one, instead of unresolved.

  
  == Original Bug Report ==
  There are some test cases in ftrace from ubuntu_kernel_selftests that would 
need some kernel configs to be enabled.

  bug 1869347
  bug 1869349

  We should not treat unresolved test case as a failure, as it's
  expected to fail with no correlated configs enabeled.

  
https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a
  #diff-33d74da785cbc5da20f71eb1af106d68

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

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

[Kernel-packages] [Bug 1878649] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.41 upstream stable release

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

Bug description:
  SRU Justification

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

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

  USB: serial: qcserial: Add DW5816e support
  nvme: refactor nvme_identify_ns_descs error handling
  nvme: fix possible hang when ns scanning fails during error recovery
  tracing/kprobes: Fix a double initialization typo
  net: macb: Fix runtime PM refcounting
  drm/amdgpu: move kfd suspend after ip_suspend_phase1
  drm/amdgpu: drop redundant cg/pg ungate on runpm enter
  vt: fix unicode console freeing with a common interface
  tty: xilinx_uartps: Fix missing id assignment to the console
  devlink: fix return value after hitting end in region read
  dp83640: reverse arguments to list_add_tail
  fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks
  ipv6: Use global sernum for dst validation with nexthop objects
  mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly
  neigh: send protocol value in neighbor create notification
  net: dsa: Do not leave DSA master with NULL netdev_ops
  net: macb: fix an issue about leak related system resources
  net: macsec: preserve ingress frame ordering
  net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc()
  net_sched: sch_skbprio: add message validation to skbprio_change()
  net: stricter validation of untrusted gso packets
  net: tc35815: Fix phydev supported/advertising mask
  net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict()
  net/tls: Fix sk_psock refcnt leak when in tls_data_ready()
  net: usb: qmi_wwan: add support for DW5816e
  nfp: abm: fix a memory leak bug
  sch_choke: avoid potential panic in choke_reset()
  sch_sfq: validate silly quantum values
  tipc: fix partial topology connection closure
  tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040
  bnxt_en: Fix VF anti-spoof filter setup.
  bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF.
  bnxt_en: Improve AER slot reset.
  bnxt_en: Return error when allocating zero size context memory.
  bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features().
  net/mlx5: DR, On creation set CQ's arm_db member to right value
  net/mlx5: Fix forced completion access non initialized command entry
  net/mlx5: Fix command entry leak in Internal Error State
  net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx()
  net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del()
  HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices
  sctp: Fix bundling of SHUTDOWN with COOKIE-ACK
  Revert "HID: wacom: generic: read the number of expected touches on a per 
collection basis"
  HID: usbhid: Fix race between usbhid_close() and usbhid_stop()
  HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT
  USB: uas: add quirk for LaCie 2Big Quadra
  usb: chipidea: msm: Ensure proper controller reset using role switch API
  USB: serial: garmin_gps: add sanity checking for data length
  tracing: Add a vmalloc_sync_mappings() for safe measure
  crypto: arch/nhpoly1305 - process in explicit 4k chunks
  KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction
  KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path
  KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER
  KVM: arm64: Fix 32bit PC wrap-around
  arm64: hugetlb: avoid potential NULL dereference
  drm: ingenic-drm: add MODULE_DEVICE_TABLE
  ipc/mqueue.c: change __do_notify() to bypass check_kill_permission()
  epoll: atomically remove wait entry on wake up
  eventpoll: fix missing wakeup for ovflist in ep_poll_callback
  mm/page_alloc: fix watchdog soft lockups during 

[Kernel-packages] [Bug 1877013] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Dell XPS 13 9300 mirror mode doesn't work sometimes with WD19TB

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  Connect HDMI monitor on WD19TB dock and connect WD19TB to Dell XPS 13 9300, 
toggling the display mode to mirror sometimes got a blank screen on external 
monitor.

  [Fix]
  After bisect kernel and found below commit(from v5.7-rc2) improves the 
stability
  bcad588dea53 drm/i915/perf: Do not clear pollin for small user read buffers

  [Test]
  Verified on Dell XPS 13 9300 with WD19TB docking station, the fail rate 
becomes from 1/2 to 1/30

  [Regression Potential]
  Low, this commit has been CC'd to stable, so we will have this soon.

  [Misc]
  OEM-5.6 has this commit from v5.6.6 stable update

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

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

[Kernel-packages] [Bug 1878040] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.40 upstream stable release

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

Bug description:
  SRU Justification

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

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

  vhost: vsock: kick send_pkt worker once device is started
  drm/bridge: analogix_dp: Split bind() into probe() and real bind()
  ASoC: topology: Check return value of soc_tplg_create_tlv
  ASoC: topology: Check return value of soc_tplg_*_create
  ASoC: topology: Check soc_tplg_add_route return value
  ASoC: topology: Check return value of pcm_new_ver
  ASoC: topology: Check return value of soc_tplg_dai_config
  selftests/ipc: Fix test failure seen after initial test run
  ASoC: sgtl5000: Fix VAG power-on handling
  ASoC: topology: Fix endianness issue
  usb: dwc3: gadget: Properly set maxpacket limit
  ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode
  ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode
  ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry
  remoteproc: qcom_q6v5_mss: fix a bug in q6v5_probe()
  drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay 
table v0 (e.g Hawaii)
  wimax/i2400m: Fix potential urb refcnt leak
  net: stmmac: fix enabling socfpga's ptp_ref_clock
  net: stmmac: Fix sub-second increment
  ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent
  ASoC: rsnd: Fix "status check failed" spam for multi-SSI
  cifs: protect updating server->dstaddr with a spinlock
  scripts/config: allow colons in option strings for sed
  cifs: do not share tcons with DFS
  tracing: Fix memory leaks in trace_events_hist.c
  lib/mpi: Fix building for powerpc with clang
  mac80211: sta_info: Add lockdep condition for RCU list usage
  net: bcmgenet: suppress warnings on failed Rx SKB allocations
  net: systemport: suppress warnings on failed Rx SKB allocations
  drm/i915: Extend WaDisableDARBFClkGating to icl,ehl,tgl
  sctp: Fix SHUTDOWN CTSN Ack in the peer restart case
  Revert "software node: Simplify software_node_release() function"
  hexagon: clean up ioremap
  hexagon: define ioremap_uc
  ALSA: hda: Match both PCI ID and SSID for driver blacklist
  x86/kvm: fix a missing-prototypes "vmread_error"
  platform/x86: GPD pocket fan: Fix error message when temp-limits are out of 
range
  ACPI: PM: s2idle: Fix comment in acpi_s2idle_prepare_late()
  mac80211: add ieee80211_is_any_nullfunc()
  cgroup, netclassid: remove double cond_resched
  libbpf: Fix readelf output parsing for Fedora
  mm/mremap: Add comment explaining the untagging behaviour of mremap()
  Revert "drm/amd/display: setting the DIG_MODE to the correct value."
  tools headers UAPI: Sync copy of arm64's asm/unistd.h with the kernel sources
  udp: document udp_rcv_segment special case for looped packets
  PM / devfreq: Add missing locking while setting suspend_freq
  Linux 5.4.40
  UBUNTU: upstream stable to v5.4.40

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

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

[Kernel-packages] [Bug 1876885] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  linux: riscv: set max_pfn to the PFN of the last page

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

Bug description:
  == SRU Justification Focal/Groovy ==

  The current max_pfn equals to zero. In this case, I found it caused users
  cannot get some page information through /proc such as kpagecount in v5.6
  kernel because of new sanity checks. The following message is displayed by
  stress-ng test suite with the command "stress-ng --verbose --physpage 1 -t
  1" on HiFive unleashed board.

   # stress-ng --verbose --physpage 1 -t 1
   stress-ng: debug: [109] 4 processors online, 4 processors configured
   stress-ng: info: [109] dispatching hogs: 1 physpage
   stress-ng: debug: [109] cache allocate: reducing cache level from L3 (too 
high) to L0
   stress-ng: debug: [109] get_cpu_cache: invalid cache_level: 0
   stress-ng: info: [109] cache allocate: using built-in defaults as no 
suitable cache found
   stress-ng: debug: [109] cache allocate: default cache size: 2048K
   stress-ng: debug: [109] starting stressors
   stress-ng: debug: [109] 1 stressor spawned
   stress-ng: debug: [110] stress-ng-physpage: started [110] (instance 0)
   stress-ng: error: [110] stress-ng-physpage: cannot read page count for 
address 0x3fd34de000 in /proc/kpagecount, errno=0 (Success)
   stress-ng: error: [110] stress-ng-physpage: cannot read page count for 
address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success)
   ...
   stress-ng: error: [110] stress-ng-physpage: cannot read page count for 
address 0x3fd32db078 in /proc/kpagecount, errno=0 (Success)
   stress-ng: debug: [110] stress-ng-physpage: exited [110] (instance 0)
   stress-ng: debug: [109] process [110] terminated
   stress-ng: info: [109] successful run completed in 1.00s
   #

  == Fix ==

  Upstream commit in linux-next:

  commit c749bb2d554825e007cbc43b791f54e124dadfce
  Author: Vincent Chen 
  Date:   Mon Apr 27 14:59:24 2020 +0800

  riscv: set max_pfn to the PFN of the last page

  == Test Case ==

  Without the patch, running stress-ng --verbose --physpage 1 -t
  1 on HiFive unleashed board will trip the bug.  With the patch, the test 
passes as follows:

   # stress-ng --verbose --physpage 1 -t 1
   stress-ng: debug: [104] 4 processors online, 4 processors configured 
stress-ng: info: [104] dispatching hogs: 1 physpage
   stress-ng: info: [104] cache allocate: using defaults, can't determine cache 
details from sysfs
   stress-ng: debug: [104] cache allocate: default cache size: 2048K
   stress-ng: debug: [104] starting stressors
   stress-ng: debug: [104] 1 stressor spawned
   stress-ng: debug: [105] stress-ng-physpage: started [105] (instance 0) 
stress-ng: debug: [105] stress-ng-physpage: exited [105] (instance 0) 
stress-ng: debug: [104] process [105] terminated
   stress-ng: info: [104] successful run completed in 1.01s
   

  == Regression Potential ==

  Small, this correctly fixes the max_pfn and max_low_pfn to the correct
  end of DRAM location.  The fix now can be shown to set these
  appropriately because stress-ng no longer triggers this corner case.

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

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

[Kernel-packages] [Bug 1877592] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.39 upstream stable release

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

Bug description:
  SRU Justification

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

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

  dma-buf: Fix SET_NAME ioctl uapi
  drm/edid: Fix off-by-one in DispID DTD pixel clock
  drm/amd/display: Fix green screen issue after suspend
  drm/qxl: qxl_release leak in qxl_draw_dirty_fb()
  drm/qxl: qxl_release leak in qxl_hw_surface_alloc()
  drm/qxl: qxl_release use after free
  NFSv4.1: fix handling of backchannel binding in BIND_CONN_TO_SESSION
  btrfs: fix transaction leak in btrfs_recover_relocation
  btrfs: fix block group leak when removing fails
  btrfs: fix partial loss of prealloc extent past i_size after fsync
  btrfs: transaction: Avoid deadlock due to bad initialization timing of 
fs_info::journal_info
  mmc: cqhci: Avoid false "cqhci: CQE stuck on" by not open-coding timeout loop
  mmc: sdhci-xenon: fix annoying 1.8V regulator warning
  mmc: sdhci-pci: Fix eMMC driver strength for BYT-based controllers
  mmc: sdhci-msm: Enable host capabilities pertains to R1b response
  mmc: meson-mx-sdio: Set MMC_CAP_WAIT_WHILE_BUSY
  mmc: meson-mx-sdio: remove the broken ->card_busy() op
  crypto: caam - fix the address of the last entry of S/G
  ALSA: hda/realtek - Two front mics on a Lenovo ThinkCenter
  ALSA: usb-audio: Correct a typo of NuPrime DAC-10 USB ID
  ALSA: hda/hdmi: fix without unlocked before return
  ALSA: line6: Fix POD HD500 audio playback
  ALSA: pcm: oss: Place the plugin buffer overflow checks correctly
  i2c: amd-mp2-pci: Fix Oops in amd_mp2_pci_init() error handling
  Drivers: hv: vmbus: Fix Suspend-to-Idle for Generation-2 VM
  dlmfs_file_write(): fix the bogosity in handling non-zero *ppos
  IB/rdmavt: Always return ERR_PTR from rvt_create_mmap_info()
  PM: ACPI: Output correct message on target power state
  PM: hibernate: Freeze kernel threads in software_resume()
  dm verity fec: fix hash block number in verity_fec_decode
  dm writecache: fix data corruption when reloading the target
  dm multipath: use updated MPATHF_QUEUE_IO on mapping for bio-based mpath
  ARM: dts: imx6qdl-sr-som-ti: indicate powering off wifi is safe
  scsi: qla2xxx: set UNLOADING before waiting for session deletion
  scsi: qla2xxx: check UNLOADING before posting async work
  RDMA/mlx5: Set GRH fields in query QP on RoCE
  RDMA/mlx4: Initialize ib_spec on the stack
  RDMA/siw: Fix potential siw_mem refcnt leak in siw_fastreg_mr()
  RDMA/core: Prevent mixed use of FDs between shared ufiles
  RDMA/core: Fix race between destroy and release FD object
  RDMA/cm: Fix ordering of xa_alloc_cyclic() in ib_create_cm_id()
  RDMA/cm: Fix an error check in cm_alloc_id_priv()
  i2c: iproc: generate stop event for slave writes
  vfio: avoid possible overflow in vfio_iommu_type1_pin_pages
  vfio/type1: Fix VA->PA translation for PFNMAP VMAs in vaddr_get_pfn()
  iommu/qcom: Fix local_base status check
  scsi: target/iblock: fix WRITE SAME zeroing
  iommu/amd: Fix legacy interrupt remapping for x2APIC-enabled system
  i2c: aspeed: Avoid i2c interrupt status clear race condition.
  ALSA: opti9xx: shut up gcc-10 range warning
  Fix use after free in get_tree_bdev()
  nvme: prevent double free in nvme_alloc_ns() error handling
  nfs: Fix potential posix_acl refcnt leak in nfs3_set_acl
  dmaengine: dmatest: Fix iteration non-stop logic
  dmaengine: dmatest: Fix process hang when reading 'wait' parameter
  arm64: vdso: Add -fasynchronous-unwind-tables to cflags
  selinux: properly handle multiple messages in selinux_netlink_send()
  Linux 5.4.39
  UBUNTU: upstream stable to v5.4.39

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1878296] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  rtl8723bu wifi issue after being turned off

Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem-osp1 source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  With the rtl8723bu Wi-Fi/Bluetooth combo adapter, if the wifi is turned
  off and then turned on again under the circumstance that a Bluetooth
  device was paired previously, the system can't connect to a wireless
  network until the system is rebooted.

  [Fix]
  Commit e542e66b7c2e("rtl8xxxu: add bluetooth co-existence support for
  single antenna"), which landed v5.5 and as its subject suggests, support
  bluetooth co-existence for RTL8723BU and fixes WiFi disconnection
  problem when Bluetooth is in action.

  Commit a9bb0b515778("rtl8xxxu: Improve TX performance of RTL8723BU on
  rtl8xxxu driver") was added as a prerequisite to aforementioned fix.

  Commit 4fcef8609132("rtl8xxxu: remove set but not used variable
  'rate_mask'") and commit eac08515d7bd("rtl8xxxu: Remove set but not used
  variable 'vif','dev','len'") are included as minor fixes to previous
  commits.

  [Test Case]
  1. Turn on Wi-Fi and get associated with some AP.
  2. Pair some bluetooth device.
  3. Turn off Wi-Fi and turn again.
  4. Expect Wi-Fi reconnects to the previous associated AP.

  [Regression Potential]
  Low. Both commits only affect RTL8723BU.

  == Original Bug Description ==

  With the rtl8723bu wireless adapter, if the wifi is turned off and then 
turned on again, the system can't connect to a wireless network until the 
system is rebooted.
  The issue is not upstream. With mainline kernel and in other distros, 
everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-29-generic 5.4.0-29.33
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user 1384 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 19:02:49 2020
  InstallationDate: Installed on 2020-05-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 090c:037c Silicon Motion, Inc. - Taiwan (formerly 
Feiya Technology Corp.) 300k Pixel Camera
   Bus 001 Device 003: ID 0bda:b720 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Positivo Tecnologia SA N1240
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=984e1018-1354-474e-83a9-b8ab7a761be7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-29-generic N/A
   linux-backports-modules-5.4.0-29-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: Desenvolvido por Positivo Tecnologia SA
  dmi.bios.version: V1.09.X
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: N14DP6
  dmi.board.vendor: Positivo Tecnologia SA
  dmi.board.version: 11139547
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Positivo Tecnologia SA
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1877955] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Fix for secure boot rules in IMA arch policy on powerpc

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Currently the kernel module appended signature is verified twice
  (finit_module) - once by the module_sig_check() and again by IMA.

  * To prevent this the powerpc secure boot rules define an IMA
  architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
  not enabled.

  * But this doesn't take the ability into account of enabling
  "sig_enforce" at the boot command line (module.sig_enforce=1).

  * Including the IMA module appraise rule results in failing the
  finit_module syscall, unless the module signing public key is loaded
  onto the IMA keyring.

  * This patch fixes secure boot policy rules to be based on
  CONFIG_MODULE_SIG instead.

  [Fix]

  * fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
  Fix secure boot rules in ima arch policy"

  [Test Case]

  * Perform a secure boot on a powerpc system with
  'module.sig_enforce=1' set at the boot command.

  * If the IMA module appraise rule is included, the finit_module
  syscall will fail (unless the module signing public key got loaded
  onto the IMA keyring) without having the patch in place.

  * The verification needs to be done by the IBM Power team.

  [Regression Potential]

  * There is (always) a certain regression risk with having code
  changes, especially in the secure boot area.

  * But this patch is limited to the powerpc platform and will not
  affect any other architecture.

  * It got discussed at 
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
    before it became finally upstream accepted with kernel 5.7-rc7.

  * The secure boot code itself wasn't really touched, rather than it's basis 
for execution.
    The IMA policy rule for module appraisal is now added only if 
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
    Hence the change is very limited and straightforward.

  [Other]

  * Since the patch got upstream with 5.7-rc7, it is already in groovy, hence 
this SRU is for focal only.
  __

  == Comment: #0 - Michael Ranweiler  - 2020-04-22 
14:44:31 ==
  +++ This bug was initially created as a clone of Bug #184073 +++

  This bug is a follow on to LP 1866909 to address a missing piece -
  only half the following patch was included in 5.4.0-24.28.

  The upstream patch has an additional fix but it?s not critical for GA.
  It can get included as part of bug fixes. It also affects only power.
  The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
  posted to linux-integrity and linuxppc-dev mailing list
  (https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
  email-na...@linux.ibm.com/T/#u)

  If there are any issues identified during further testing, they will
  get opened as separate issue to be addressed later.

  Thanks & Regards,
     - Nayna

  == Comment: #4 - Michael Ranweiler  - 2020-05-11 
02:23:35 ==
  Updated posting:

  https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
  email-na...@linux.ibm.com/T/#u

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

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

[Kernel-packages] [Bug 1878147] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Realtek 8723DE [10ec:d723] subsystem [10ec:d738]  disconnects
  unsolicitedly when Bluetooth is paired: Reason: 23=IEEE8021X_FAILED

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Eoan:
  Invalid
Status in linux-oem-5.6 source package in Eoan:
  Invalid
Status in linux-oem-osp1 source package in Eoan:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Invalid
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux-oem-osp1 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]
  Existing Wi-Fi connection may be deauthenticated unsolicitedly with
  reason 23=IEEE8021X_FAILED when the system is also paired with a
  Bluetooth device. A WLAN passphrase dialog propmpts, and system
  disconnects from network:

wlp5s0: deauthenticated from a4:56:30:cc:0f:30 (Reason:
  23=IEEE8021X_FAILED).

  [Fix]
  Realtek proposed a fix[1] to linux-wireless consisting of three patches.

rtw88: coex: 8723d: set antanna control owner
rtw88: coex: 8723d: handle BT inquiry cases
rtw88: fix EAPOL 4-way failure by finish IQK earlier

  The third one actually duplicates the fix we have for bug 1871300 also
  from Realtek and was claimed critical to this issue, therefore those for
  bug 1871300 are reverted in favor of the new one.

  Also revert that Ubuntu sauced "rtw88: 8723d: Add coex support" commit
  and replace it with the upstream one due to dependency to bt coex
  functionality.

  [1]: https://lore.kernel.org/linux-
  wireless/20200518081444.7664-1-yhchu...@realtek.com/

  [Test Case]
  1. Associate to a WLAN,
  2. Pair with some Bluetooth device, e.g. headset,
  3. Run a stress test script to disconnect and reconnect Wi-Fi for 200
 runs,
  4. Make sure Wi-Fi passphrase dialog doesn't prompt at the end of the
 test.

  [Regression Potential]
  Low. These changes are mostly about rtl8723de or 11n, which is also for
  8723de.

  == Original Bug Description ==

  Existing Wi-Fi connection may be deauthenticated unsolicitedly with
  reason 23=IEEE8021X_FAILED when the system is also paired with a
  Bluetooth device. A WLAN passphrase dialog propmpts, and system
  disconnects from network leaving an error message in syslog:

    [ 207.523312] wlp5s0: deauthenticated from a4:56:30:cc:0f:30
  (Reason: 23=IEEE8021X_FAILED).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-oem-osp1 5.0.0.1050.53
  ProcVersionSignature: Ubuntu 5.0.0-1050.55-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1050-oem-osp1 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1667 F pulseaudio
    u  3061 F pulseaudio
   /dev/snd/controlC0:  gdm1667 F pulseaudio
    u  3061 F pulseaudio
  Date: Tue May 12 14:59:32 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-grenn+X39
  InstallationDate: Installed on 2020-04-10 (31 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04d9:0024 Holtek Semiconductor, Inc.
   Bus 001 Device 003: ID 0bda:d739 Realtek Semiconductor Corp.
   Bus 001 Device 005: ID 062a:4c01 Creative Labs
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell 

[Kernel-packages] [Bug 1877394] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Kernel panic due to NULL ringbuffer vaddr dereference in i915

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

Bug description:
  SRU Justification:

  [Impact]
  A sauce fix for a kernel panic in i915 that I frequently experienced was 
fixed by upstream.

  [Fix]
  The sauce patch I made should be dropped in exchange for the proper upstream 
fix.

  [Test]
  I tested the upstream fix and can confirm it fixes the crashes I experienced.

  [Regression Potential]
  Low. The upstream fix for this bug is tiny and we get to remove a nasty sauce 
patch.
  ---
  This is what the crash looks like:
  BUG: unable to handle page fault for address: 3448
  RIP: 0010:gen8_emit_flush_render+0x163/0x190
  Call Trace:
   execlists_request_alloc+0x25/0x40
   __i915_request_create+0x1f4/0x2c0
   i915_request_create+0x71/0xc0
   i915_gem_do_execbuffer+0xb98/0x1a80
   ? preempt_count_add+0x68/0xa0
   ? _raw_spin_lock+0x13/0x30
   ? _raw_spin_unlock+0x16/0x30
   i915_gem_execbuffer2_ioctl+0x1de/0x3c0
   ? i915_gem_busy_ioctl+0x7f/0x1d0
   ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0
   drm_ioctl_kernel+0xb2/0x100
   drm_ioctl+0x209/0x360
   ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0
   ksys_ioctl+0x87/0xc0
   __x64_sys_ioctl+0x16/0x20
   do_syscall_64+0x4e/0x150
   entry_SYSCALL_64_after_hwframe+0x44/0xa9

  This bug was fixed by "UBUNTU: SAUCE: drm/i915: Synchronize active and
  retire callbacks" but there is an upstream fix for it, "drm/i915/gt:
  Make intel_ring_unpin() safe for concurrent pint". Let's replace the
  sauce patch with the upstream fix.

  More info here: https://gitlab.freedesktop.org/drm/intel/issues/1599

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

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

[Kernel-packages] [Bug 1881046] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  ASoC/amd: add audio driver for amd renoir

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Incomplete

Bug description:
  This patchset is for mainline kernel-5.8, after backporting to 5.6,
  there is no need to change anything, but after backporting to 5.4
  kernel, because of API differences, need to do some change to adapt
  to 5.4 kernel's API. So there is one more patch for focal than for
  oem-5.6.

  [Impact]
  We have a couple of LENOVO machines which has amd renoir audio on
  them, our kernel doesn't have the driver for it yet.

  [Fix]
  amd just upstreamed the driver, it is for kernel-5.8, we backport
  them to ubunt kernel.

  [Test Case]
  boot the kernel with those patches, we could see a sound card named
  "acp" and the dmic on it could record sound via arecord.

  [Regression Risk]
  Low, just adding a new driver, no change to existing drivers.

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

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

[Kernel-packages] [Bug 1878897] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  debian/scripts/file-downloader does not handle positive failures
  correctly

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress

Bug description:
  Somehow we are not really correctly handling positive failures, 404
  for example.  Sigh.

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

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

[Kernel-packages] [Bug 1879704] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [UBUNTU 20.04] s390x/pci: fix linking between PF and VF for
  multifunction devices

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * It's currently not possible on s390x to verify the relationships
  between PFs and VFs of network interfaces (neither natively nor in
  libvirt).

  * So s390x currently behaves differently here compared to other
  architectures, but shouldn't, since this is needed for proper
  management.

  * The creation of not only the sysfs, but also the in-kernel link
  (struct pci_dev->physfn), solves this and on top allows the use of a
  common code path for disabling/shutdown of PFs.

  * This code path is right now fenced off by the struct
  pci_dev->no_vf_scan flag of which s390x is currently the only user.

  * This allows to gracefully and orderly shutdown VFs associated with a
  PF as triggered by '/sys/bus/pci/devices//sriov_numvfs'

  * Previously this could leave the card in an unresponsive error state.

  [Fix]

  * a1ceea67f2e5b73cebd456e7fb463b3052bc6344 a1ceea67f2e5 "PCI/IOV:
  Introduce pci_iov_sysfs_link() function"

  * e5794cf1a270d813a5b9373a6876487d4d154195 e5794cf1a270 "s390/pci:
  create links between PFs and VFs"

  [Test Case]

  * Setup an s390x LPAR with at least one SR-IOV card and assign PF and
  VFs to that system.

  * Determine if a device is a virtual function: for other architectures
  this is currently available in the file 'physfn' which is a link to
  the parent PF's device.

  * Determine virtual functions of a physical function: for other
  architectures this is currently available as 'virtfn{index}' links
  under the PF device's directory.

  * Determine the physical function of a virtual function: on x86 this
  is currently available in the file 'physfn' which is a link to the
  parent PF.

  * This verification needs to be done by IBM on a system with SR-IOV
  (PCI-based) hardware.

  [Regression Potential]

  * There is a certain regression risk with having code changes in the PCI/IOV 
space,
    even is they are limited, especially is the patches touche common code.

  * The changes in pci.h are very minimal, and the iov.c changes are
  traceable, too. All other modifications are s390x specific.

  * Nevertheless, it could be that PCI hardware get harmed, here
  especially (SR-)IOV hardware.

  * The patches got cross-company verified (IBM and Google).

  * They were brought upstream and are currently tagged with 20200521,
  and are planned to be included in 5.8.

  * A patched kernel was created based on a LP PPA and successfully
  tested by IBM.

  [Other]

  * Since the fix/patch is planned to be included in kernel v5.8, it
  will later automatically land in groovy.

  * But because groovy is not there yet (5.8 is not yet out), this SRU
  got requested for focal and groovy.

  * This SRU depends on the SRU from LP 1874056, and this has already two ACKs.
    So LP 1874056 needs to be applied before this one!
  __

  As with other architectures, we must be able on s390x to verify the
  following relationships between PFs and VFs for proper management
  (including by libvirt) of network interfaces:

  1. Determine if a device is a virtual function: for other architectures this 
is currently available in the file `physfn` which is a link to the parent PF's 
device.
  2. Determine virtual functions of a physical function: for other 
architectures this is currently available as `virtfn{index}` links under the PF 
device's directory.
  3. Determine the physical function of a virtual function: on x86 this is 
currently available in the file `physfn` which is a link to the parent PF

  More details for the already existing parameters mentioned above can
  be found here: https://www.kernel.org/doc/Documentation/ABI/testing
  /sysfs-bus-pci

  Moreover creating not just the sysfs but also the in-kernel link
  (struct pci_dev->physfn) also allows us to use the common code path
  for disabling/shutdown of PFs.
  This code path is currently fenced off 

[Kernel-packages] [Bug 1879327] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Enforce all config annotations

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress

Bug description:
  [Impact]
  Not all config annotations are enforced, which means config could regress 
without notice.

  [Test case]
  Check the logs mention much more options being enforced. From the hundreds to 
more than 1.

  [Regression potential]
  Builds will start failing when config doesn't match annotations. However, 
this is an opt-in for now, which means only those branches prepared to accept 
it will risk such regression.

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

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

[Kernel-packages] [Bug 1880660] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  security: lockdown: remove trailing semicolon before function body

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  In focal commit 40fc208c8aae ("UBUNTU: SAUCE: (lockdown) security:
  lockdown: expose a hook to lock the kernel down") adds an inline
  function with a trailing semicolon before the function body, that can
  potentially cause build errors.

  [Test case]

  Build anything that includes linux/security.h and check for
  warnings/errors.

  [Fix]

  Fix by removing the trailing semicolon.

  [Regression potential]

  The problem is an obvious syntax error, fix is trivial, so regression
  potential is minimal.

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

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

[Kernel-packages] [Bug 1881710] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  tpm: fix TIS locality timeout problems

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  It has been reported that some TIS based TPMs are giving unexpected errors 
when using the O_NONBLOCK path of the TPM device. The problem is that some TPMs 
don't like it when you get and then relinquish a locality (as the 
tpm_try_get_ops()/tpm_put_ops() pair does) without sending a command. This 
currently happens all the time in the O_NONBLOCK write path. This affects 
Nuvoton TPMs and was a regression caused by the patch d23d12484307 ("tpm: fix 
invalid locking in NONBLOCKING mode").
  PatchLink: https://patchwork.kernel.org/patch/11576453/

  [Fix]
  Fix this by moving the tpm_try_get_ops()
  further down the code to after the O_NONBLOCK determination is made.
  This is safe because the priv->buffer_mutex still protects the priv
  state being modified.

  [Regression Risk]
  Low. This patch only for fix the patch d23d12484307 ("tpm: fix invalid 
locking in NONBLOCKING mode").

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

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

[Kernel-packages] [Bug 1879690] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Docker registry doesn't stay up and keeps restarting

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  [Impact]
  The change applied for bug 1857257 and its followup fix bug 1876645, which 
were released on focal and eoan -updates, introduced a regression on overlayfs, 
breaking docker snap.

  [Test case]
  See original bug report.

  [Fix]
  While we don't have a final fix the solution for now is to revert the 
following commits:

  UBUNTU: SAUCE: overlayfs: fix shitfs special-casing
  UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay

  [Regression potential]
  Low. Reverting these two commits will introduce back the issue reported on 
bug 1857257, but will fix the other use cases which was broken by the latest 
release.

  
  Original bug report.
  ---
  Tested kernels:
  Focal 5.4.0-31.35
  Eoan 5.3.0-53.47

  To reproduce:
  1) Spin up a cloud image
  2) snap install docker
  3) auth_folder=/var/snap/docker/common/auth
  4) mkdir -p $auth_folder
  5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > 
$auth_folder/htpasswd
  6) docker run -d -p 5000:5000 --restart=always --name registry \
    -v $auth_folder:/auth \
    -e "REGISTRY_AUTH=htpasswd" \
    -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \
    -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \
     registry:2

  On a good kernel 'docker ps' shows something like:
  # docker ps
  CONTAINER IDIMAGE   COMMAND  CREATED  
   STATUS  PORTSNAMES
  a346b65b4509registry:2  "/entrypoint.sh /etc…"   14 seconds 
ago  Up 12 seconds   0.0.0.0:5000->5000/tcp   registry

  On a bad kernel:
   docker ps
  CONTAINER IDIMAGE   COMMAND  CREATED  
   STATUSPORTS   NAMES
  0322374f1b1dregistry:2  "/entrypoint.sh /etc…"   5 seconds 
ago   Restarting (2) 1 second ago   registry

  Note status 'Restarting' on the bad kernel.

  This seems to be introduce by any of the following commits:
  b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing
  6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as 
underlay
  629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials
  cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation

  Kernels that don't have these commits seem fine.

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

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

[Kernel-packages] [Bug 1881178] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.43 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
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.43 upstream stable release
     from git://git.kernel.org/

  i2c: dev: Fix the race between the release of i2c_dev and cdev
  KVM: SVM: Fix potential memory leak in svm_cpu_init()
  ima: Set file->f_mode instead of file->f_flags in ima_calc_file_hash()
  evm: Check also if *tfm is an error pointer in init_desc()
  ima: Fix return value of ima_write_policy()
  ubifs: fix wrong use of crypto_shash_descsize()
  ACPI: EC: PM: Avoid flushing EC work when EC GPE is inactive
  mtd: spinand: Propagate ECC information to the MTD structure
  fix multiplication overflow in copy_fdtable()
  ubifs: remove broken lazytime support
  i2c: fix missing pm_runtime_put_sync in i2c_device_probe
  iommu/amd: Fix over-read of ACPI UID from IVRS table
  evm: Fix a small race in init_desc()
  i2c: mux: demux-pinctrl: Fix an error handling path in 
'i2c_demux_pinctrl_probe()'
  ubi: Fix seq_file usage in detailed_erase_block_info debugfs file
  afs: Don't unlock fetched data pages until the op completes successfully
  mtd: Fix mtd not registered due to nvmem name collision
  kbuild: avoid concurrency issue in parallel building dtbs and dtbs_check
  net: drop_monitor: use IS_REACHABLE() to guard net_dm_hw_report()
  gcc-common.h: Update for GCC 10
  HID: multitouch: add eGalaxTouch P80H84 support
  HID: alps: Add AUI1657 device ID
  HID: alps: ALPS_1657 is too specific; use U1_UNICORN_LEGACY instead
  scsi: qla2xxx: Fix hang when issuing nvme disconnect-all in NPIV
  scsi: qla2xxx: Delete all sessions before unregister local nvme port
  configfs: fix config_item refcnt leak in configfs_rmdir()
  vhost/vsock: fix packet delivery order to monitoring devices
  aquantia: Fix the media type of AQC100 ethernet controller in the driver
  component: Silence bind error on -EPROBE_DEFER
  net/ena: Fix build warning in ena_xdp_set()
  scsi: ibmvscsi: Fix WARN_ON during event pool release
  HID: i2c-hid: reset Synaptics SYNA2393 on resume
  x86/mm/cpa: Flush direct map alias during cpa
  ibmvnic: Skip fatal error reset after passive init
  x86/apic: Move TSC deadline timer debug printk
  gtp: set NLM_F_MULTI flag in gtp_genl_dump_pdp()
  HID: quirks: Add HID_QUIRK_NO_INIT_REPORTS quirk for Dell K12A keyboard-dock
  ceph: fix double unlock in handle_cap_export()
  stmmac: fix pointer check after utilization in stmmac_interrupt
  USB: core: Fix misleading driver bug report
  platform/x86: asus-nb-wmi: Do not load on Asus T100TA and T200TA
  iommu/amd: Call domain_flush_complete() in update_domain()
  drm/amd/display: Prevent dpcd reads with passive dongles
  KVM: selftests: Fix build for evmcs.h
  ARM: futex: Address build warning
  scripts/gdb: repair rb_first() and rb_last()
  ALSA: hda - constify and cleanup static NodeID tables
  ALSA: hda: patch_realtek: fix empty macro usage in if block
  ALSA: hda: Manage concurrent reg access more properly
  ALSA: hda/realtek - Add supported new mute Led for HP
  ALSA: hda/realtek - Add HP new mute led supported for ALC236
  ALSA: hda/realtek: Add quirk for Samsung Notebook
  ALSA: hda/realtek - Enable headset mic of ASUS GL503VM with ALC295
  ALSA: hda/realtek - Enable headset mic of ASUS UX550GE with ALC295
  ALSA: hda/realtek: Enable headset mic of ASUS UX581LV with ALC295
  KVM: x86: Fix pkru save/restore when guest CR4.PKE=0, move it to x86.c
  ALSA: iec1712: Initialize STDSP24 properly when using the model=staudio option
  ALSA: pcm: fix incorrect hw_base increase
  ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus Xtreme
  ALSA: hda/realtek - Add more fixup entries for Clevo machines
  scsi: 

[Kernel-packages] [Bug 1880656] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Fix incorrect speed/duplex when I210 device is runtime suspended

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.6 package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-5.6 source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  [Impact]
  When I210 device is runtime suspended, trying to read speed or duplex from 
sysfs causes an error:
  [  385.991957] igb :03:00.0 enp3s0: PCIe link lost

  [Fix]
  Only try to read the device register when it's not runtime suspended.

  [Test]
  Without the fix:
  $ cat /sys/class/net/enp3s0/speed
  1000

  With the fix:
  $ cat /sys/class/net/enp3s0/speed
  -1

  -1 means "unknown speed", which is the correct status when device is
  runtime suspend.

  [Regression Potential]
  Low. It's a trivial fix which limits to one driver.

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

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

[Kernel-packages] [Bug 1879759] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.42 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
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.42 upstream stable release
     from git://git.kernel.org/

  net: dsa: Do not make user port errors fatal
  shmem: fix possible deadlocks on shmlock_user_lock
  net: phy: microchip_t1: add lan87xx_phy_init to initialize the lan87xx phy.
  KVM: arm: vgic: Synchronize the whole guest on GIC{D,R}_I{S,C}ACTIVER read
  gpio: pca953x: Fix pca953x_gpio_set_config
  SUNRPC: Add "@len" parameter to gss_unwrap()
  SUNRPC: Fix GSS privacy computation of auth->au_ralign
  net/sonic: Fix a resource leak in an error handling path in 
'jazz_sonic_probe()'
  net: moxa: Fix a potential double 'free_irq()'
  ftrace/selftests: workaround cgroup RT scheduling issues
  drop_monitor: work around gcc-10 stringop-overflow warning
  virtio-blk: handle block_device_operations callbacks after hot unplug
  sun6i: dsi: fix gcc-4.8
  net_sched: fix tcm_parent in tc filter dump
  scsi: sg: add sg_remove_request in sg_write
  mmc: sdhci-acpi: Add SDHCI_QUIRK2_BROKEN_64_BIT_DMA for AMDI0040
  dpaa2-eth: properly handle buffer size restrictions
  net: fix a potential recursive NETDEV_FEAT_CHANGE
  netlabel: cope with NULL catmap
  net: phy: fix aneg restart in phy_ethtool_set_eee
  net: stmmac: fix num_por initialization
  pppoe: only process PADT targeted at local interfaces
  Revert "ipv6: add mtu lock check in __ip6_rt_update_pmtu"
  tcp: fix error recovery in tcp_zerocopy_receive()
  tcp: fix SO_RCVLOWAT hangs with fat skbs
  virtio_net: fix lockdep warning on 32 bit
  dpaa2-eth: prevent array underflow in update_cls_rule()
  hinic: fix a bug of ndo_stop
  net: dsa: loop: Add module soft dependency
  net: ipv4: really enforce backoff for redirects
  netprio_cgroup: Fix unlimited memory leak of v2 cgroups
  net: tcp: fix rx timestamp behavior for tcp_recvmsg
  nfp: abm: fix error return code in nfp_abm_vnic_alloc()
  r8169: re-establish support for RTL8401 chip version
  umh: fix memory leak on execve failure
  riscv: fix vdso build with lld
  dmaengine: pch_dma.c: Avoid data race between probe and irq handler
  dmaengine: mmp_tdma: Do not ignore slave config validation errors
  dmaengine: mmp_tdma: Reset channel error on release
  selftests/ftrace: Check the first record for kprobe_args_type.tc
  cpufreq: intel_pstate: Only mention the BIOS disabling turbo mode once
  ALSA: hda/hdmi: fix race in monitor detection during probe
  drm/amd/powerplay: avoid using pm_en before it is initialized revised
  drm/amd/display: check if REFCLK_CNTL register is present
  drm/amd/display: Update downspread percent to match spreadsheet for DCN2.1
  drm/qxl: lost qxl_bo_kunmap_atomic_page in qxl_image_init_helper()
  drm/amdgpu: simplify padding calculations (v2)
  drm/amdgpu: invalidate L2 before SDMA IBs (v2)
  ipc/util.c: sysvipc_find_ipc() incorrectly updates position index
  ALSA: hda/realtek - Fix S3 pop noise on Dell Wyse
  gfs2: Another gfs2_walk_metadata fix
  mmc: sdhci-pci-gli: Fix no irq handler from suspend
  IB/hfi1: Fix another case where pq is left on waitlist
  ACPI: EC: PM: Avoid premature returns from acpi_s2idle_wake()
  pinctrl: sunrisepoint: Fix PAD lock register offset for SPT-H
  pinctrl: baytrail: Enable pin configuration setting for GPIO chip
  pinctrl: qcom: fix wrong write in update_dual_edge
  pinctrl: cherryview: Add missing spinlock usage in chv_gpio_irq_handler
  bpf: Fix error return code in map_lookup_and_delete_elem()
  ALSA: firewire-lib: fix 'function sizeof not defined' error of tracepoints 
format
  i40iw: Fix error handling in i40iw_manage_arp_cache()
  drm/i915: Don't enable WaIncreaseLatencyIPCEnabled when IPC is 

[Kernel-packages] [Bug 1879688] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  shiftfs: fix btrfs snapshot deletion

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Confirmed

Bug description:
  SRU Justification

  Impact: Stéphane discovered a problem during NorthSec which makes
  heavy use of shiftfs. In containers with a btrfs root filesystem that
  make use of shiftfs userns root is not able to delete subvolumes that
  have been created by another users which it would be able to do
  otherwise. This makes it impossible for LXD to delete nested
  containers.

  To reproduce this as root in the container:
  btrfs subvolume create my-subvol
  chown 1000:1000 my-subvol
  btrfs subvolume delete my-subvol

  The deletion will fail when it should have succeeded.

  Fix: For improved security we drop all capabilities before we forward
  btrfs ioctls in shiftfs. To fix the above problem we can retain the
  CAP_DAC_OVERRIDE capability only if we are userns root.

  Regression Potential: Limited to shiftfs. Even though we drop all
  capabilities in all capability sets we really mostly care about
  dropping CAP_SYS_ADMIN and we mostly do this for ioctl that e.g. allow
  you to traverse the btrfs filesystem and with CAP_SYS_ADMIN retained
  in the underlay would allow you to list subvolumes you shouldn't be
  able to list. This fix only retains CAP_DAC_OVERRIDE and only for the
  deletion of subvolumes and only by userns root.

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

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

[Kernel-packages] [Bug 1879321] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Fix Pericom USB controller OHCI/EHCI PME# defect

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-oem-5.6 source package in Bionic:
  Won't Fix
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  [Impact]
  Pericom EHCI/OHCI USB Controller can't detect hotplug event when it's 
runtime-suspended, due to its unreliable PME#.

  [Fix]
  Disable PME for all its power state since all of them don't work reliably.

  [Test]
  Hotplugging event can be reliably detected by the device, after the fix gets 
applied.

  [Regression Potentia]
  Low. This targets specific device, without touching any logic.

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

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

[Kernel-packages] [Bug 1881927] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Focal update: v5.4.44 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
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.44 upstream stable release
     from git://git.kernel.org/

  ax25: fix setsockopt(SO_BINDTODEVICE)
  dpaa_eth: fix usage as DSA master, try 3
  net: don't return invalid table id error when we fall back to PF_UNSPEC
  net: dsa: mt7530: fix roaming from DSA user ports
  net: ethernet: ti: cpsw: fix ASSERT_RTNL() warning during suspend
  __netif_receive_skb_core: pass skb by reference
  net: inet_csk: Fix so_reuseport bind-address cache in tb->fast*
  net: ipip: fix wrong address family in init error path
  net/mlx5: Add command entry handling completion
  net: mvpp2: fix RX hashing for non-10G ports
  net: nlmsg_cancel() if put fails for nhmsg
  net: qrtr: Fix passing invalid reference to qrtr_local_enqueue()
  net: revert "net: get rid of an signed integer overflow in 
ip_idents_reserve()"
  net sched: fix reporting the first-time use timestamp
  net/tls: fix race condition causing kernel panic
  nexthop: Fix attribute checking for groups
  r8152: support additional Microsoft Surface Ethernet Adapter variant
  sctp: Don't add the shutdown timer if its already been added
  sctp: Start shutdown on association restart if in SHUTDOWN-SENT state and 
socket is closed
  tipc: block BH before using dst_cache
  net/mlx5e: kTLS, Destroy key object after destroying the TIS
  net/mlx5e: Fix inner tirs handling
  net/mlx5: Fix memory leak in mlx5_events_init
  net/mlx5e: Update netdev txq on completions during closure
  net/mlx5: Fix error flow in case of function_setup failure
  net/mlx5: Annotate mutex destroy for root ns
  net/tls: fix encryption error checking
  net/tls: free record only on encryption error
  net: sun: fix missing release regions in cas_init_one().
  net/mlx4_core: fix a memory leak bug.
  mlxsw: spectrum: Fix use-after-free of split/unsplit/type_set in case reload 
fails
  ARM: dts: rockchip: fix phy nodename for rk3228-evb
  ARM: dts: rockchip: fix phy nodename for rk3229-xms6
  arm64: dts: rockchip: fix status for  in rk3328-evb.dts
  arm64: dts: rockchip: swap interrupts interrupt-names rk3399 gpu node
  ARM: dts: rockchip: swap clock-names of gpu nodes
  ARM: dts: rockchip: fix pinctrl sub nodename for spi in rk322x.dtsi
  gpio: tegra: mask GPIO IRQs during IRQ shutdown
  ALSA: usb-audio: add mapping for ASRock TRX40 Creator
  net: microchip: encx24j600: add missed kthread_stop
  gfs2: move privileged user check to gfs2_quota_lock_check
  gfs2: Grab glock reference sooner in gfs2_add_revoke
  drm/amdgpu: drop unnecessary cancel_delayed_work_sync on PG ungate
  drm/amd/powerplay: perform PG ungate prior to CG ungate
  drm/amdgpu: Use GEM obj reference for KFD BOs
  cachefiles: Fix race between read_waiter and read_copier involving op->to_do
  usb: dwc3: pci: Enable extcon driver for Intel Merrifield
  usb: phy: twl6030-usb: Fix a resource leak in an error handling path in 
'twl6030_usb_probe()'
  usb: gadget: legacy: fix redundant initialization warnings
  net: freescale: select CONFIG_FIXED_PHY where needed
  IB/i40iw: Remove bogus call to netdev_master_upper_dev_get()
  riscv: stacktrace: Fix undefined reference to `walk_stackframe'
  clk: ti: am33xx: fix RTC clock parent
  csky: Fixup msa highest 3 bits mask
  csky: Fixup perf callchain unwind
  csky: Fixup remove duplicate irq_disable
  hwmon: (nct7904) Fix incorrect range of temperature limit registers
  cifs: Fix null pointer check in cifs_read
  csky: Fixup raw_copy_from_user()
  samples: bpf: Fix build error
  drivers: net: hamradio: Fix suspicious RCU usage warning in bpqether.c
  Input: usbtouchscreen - add support for BonXeon TP
  Input: 

[Kernel-packages] [Bug 1883874] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  dkms-build: downloads fail in private PPAs

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  We currently using apt-cache policy to obtain the local URLs this
  eliminates username and password data.  We need the URLs intact in
  order to build in private PPAs.  Switch URL source.

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

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

[Kernel-packages] [Bug 1881576] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  seccomp_benchmark times out on eoan

Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  seccomp selftests will timeout, causing the test to be detected as failure.

  [Fix]
  Set timeout to 90s.

  [Test case]
  Run sudo make run_tests under tools/testing/selftests/seccomp/.

  [Regression potential]
  Minimal, the test could still timeout, but by reading the code, it should 
take around 42s to 50s to execute in the worst cases, so 90s seem safe enough.

  ==

  
  As it tries to calibrate how many samples will take more than 5 seconds to 
execute, it may end up picking up a number of samples that take 10 (but up to 
12) seconds. As the calibration will take double that time, it takes around 20 
seconds. Then, it executes the whole thing again, and then once more, with some 
added overhead. So, the thing might take more than 40 seconds, which is too 
close to the 45s timeout.

  So, it times out once in a while depending on the system. Using a
  timeout of 90 seconds should be safe enough for this test.

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

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

[Kernel-packages] [Bug 1881120] Autopkgtest regression report (linux-oracle-5.4/5.4.0-1019.19~18.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-oracle-5.4 
(5.4.0-1019.19~18.04.1) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

zfs-linux/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-oracle-5.4

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  linux-oem-5.6-tools-common and -tools-host should be dropped

Status in linux package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.6 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  linux-oem-5.6 built -tools-common and -tools-host, which conflict with
  the master kernel versions. These shouldn't be built at all.

  [Test case]

  Check that upgrade removes the oem versions.

  [Regression potential]

  shouldn't be any

  --

  Updating 20.04, unaware of details

  package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share
  /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz
  usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf-
  archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1
  /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz
  usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz
  usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz
  usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf-
  ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf-
  inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1
  /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1
  /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1
  /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1
  /perf-record.1.gz usr/share/man/man1/perf-report.1.gz
  usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script-
  perl.1.gz usr/share/man/man1/perf-script-python.1.gz
  usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz
  usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf-
  timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1
  /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz
  usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz
  usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz]
  failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg',
  which is also in package linux-tools-common 5.4.0-31.35

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu May 28 07:43:09 2020
  ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in 
package linux-tools-common 5.4.0-31.35
  InstallationDate: Installed on 2020-04-28 (29 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: linux-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted

[Califa101]

Yes, I understand you.
Okay. As for the GRUB, as I was saying, I modify anything in this file, a 
simple line with # in front, or anything else simple, I update and TOUCHPAD 
works for me almost always ... Paranormal phenomena? :-).
Let's hope someone enlightens us. In the meantime, and if I want to use 
TOUCHPAD, I have to do what I have said or work in a session with Windows.

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

Title:
  LapBook Pro touchpad (HTIX5288:00) sometimes does not work when
  machine is restarted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad completely ceases to work sometimes upon startup / restart.
  When this happens, I have to plug in an external mouse to navigate as
  touchpad is not even recognised as a device when I use xinput command
  in terminal. I removed and reinstalled xserver-xorg-input-synaptics
  which may have got it working again, although I am not too sure. When
  the trackpad is working, it's device name is listed as HTIX5288:00
  0911:5288 Touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 18:03:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) 
(prog-if 00 [VGA controller])
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E.G140J.D8.E1.016.bin
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: LapBook Pro
  dmi.product.sku: Default string
  dmi.product.version: Default string
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian1619 F pulseaudio
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera
   Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-37-generic N/A
   linux-backports-modules-5.4.0-37-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 11/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

[Brian Murray]

During my +1 maintenance I looked at both gkrellm2-cpufreq and cpufreqd
(ppc64el arch only) both of which are depwait in groovy because Ubuntu
does not have a libcpupower-dev package. If Ubuntu isn't going to
provide the libcpupower-dev package we should blacklist packages which
depend on it so people doing +1 maintenance don't keep spending time on
it.

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

Title:
  libcpupower.so is not installed from linux-tools

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Invalid
Status in linux source package in Eoan:
  In Progress

Bug description:
  The patch for bug 1158668 installs cpupower_$(abi_version) command-
  line tool as well as libcpupower.so.$(abi_version).

  This isn't particularly suitable for projects that previously used
  libcpufreq and intend to migrate to libcpupower, because the
  libcpupower.so symlink is no longer installed. The command-line tools
  can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)).

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

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

[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5

[crysman]

Sorry for delay, I'll look into it on Thursday I hope - just letting you
know I'm still on it, just overwhelmed by work these days...

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

Title:
  touchpad doesn't work at all on ACER Spin 5

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Touchpad is not working at all on ACER Spin 5 SP513-54N.

  According to
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
  I am creating this kernel bug issue.

  There are more issues, too, like touchscreen not working and Ubuntu
  not installable - see here if interrested
  https://askubuntu.com/questions/1251719/

  I would like to run Ubuntu on this machine and I am willing to help
  with any debug or kernel tweaking... Please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4195 F pulseaudio
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 19 10:44:58 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Spin SP513-54N
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.00
  dmi.board.name: Caboom_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.00
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
  dmi.product.family: Spin 5
  dmi.product.name: Spin SP513-54N
  dmi.product.sku: 
  dmi.product.version: V1.00
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

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

** Changed in: linux (Ubuntu Eoan)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

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

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

** Changed in: linux (Ubuntu Groovy)
 Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)

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

** Description changed:

  [Impact]
  
   * Users of the Linux kernel's crypto userspace API
     reported BUG() / kernel NULL pointer dereference
     errors after kernel upgrades.
  
   * The stack trace signature is an accept() syscall
     going through af_alg_accept() and hitting errors
     usually in one of:
     - apparmor_sk_clone_security()
     - apparmor_sock_graft()
     - release_sock()
  
  [Fix]
  
   * This is a regression introduced by upstream commit
     37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
     in sk_destruct") which made its way through stable.
  
   * The offending patch allows the critical regions
     of af_alg_accept() and af_alg_release_parent() to
     run concurrently; now with the "right" events on 2
     CPUs it might drop the non-atomic reference counter
     of the alg_sock then the sock, thus release a sock
     that is still in use.
  
   * The fix is upstream commit 34c86f4c4a7b ("crypto:
     af_alg - fix use-after-free in af_alg_accept() due
     to bh_lock_sock()") [1]. It changes alg_sock's ref
     counter to atomic, which addresses the root cause.
  
  [Test Case]
  
   * There is a synthetic test case available, which
     uses a kprobes kernel module to synchronize the
     concurrent CPUs on the instructions responsible
     for the problem; and a userspace part to run it.
  
   * The organic reproducer is the Varnish Cache Plus
     software with the Crypto vmod (which uses kernel
     crypto userspace API) under long, very high load.
  
   * The patch has been verified on both reproducers
     with the 4.15 and 5.7 kernels.
  
-  * More tests performed with 'stress-ng --af-alg'
-with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
-(all on same version of stress-ng, V0.11.14)
+  * More tests performed with 'stress-ng --af-alg'
+    with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
+    (all on same version of stress-ng, V0.11.14)
  
-No regressions observed from original kernel.
-(the af-alg stressor can exercise almost all
-kernel crypto modules shipped with the kernel;
-so it checks more paths/crypto alg interfaces.)
+    No regressions observed from original kernel.
+    (the af-alg stressor can exercise almost all
+    kernel crypto modules shipped with the kernel;
+    so it checks more paths/crypto alg interfaces.)
  
  [Regression Potential]
  
   * The fix patch does a fundamental change in how
     alg_sock reference counters work, plus another
     change to the 'nokey' counting. This of course
     *has* a risk of regression.
  
   * Regressions theoretically could manifest as use
     after free errors (in case of undercounting) in
     the af_alg functions or silent memory leaks (in
     case of overcounting), but also other behaviors
     since reference counting is key to many things.
  
   * FWIW, this patch has been written by the crypto
     subsystem maintainer, who certainly knows a lot
     of the normal and corner cases, thus giving the
     patch more credit.
  
   * Testing with the organic reproducer ran as long
     as 5 days, without issues, so it does look good.
  
  [Other Info]
+ 
+  * Not sending for Groovy (should get via Unstable).
  
   * [1] Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=34c86f4c4a7be3b3e35aa48bd18299d4c756064d
  
  [Stack Trace Examples]
  
  Examples:
  
  BUG: unable to handle kernel NULL pointer dereference at 
  ...
  RIP: 0010:apparmor_sk_clone_security+0x26/0x70
  ...
  Call Trace:
   security_sk_clone+0x33/0x50
   af_alg_accept+0x81/0x1c0 [af_alg]
   alg_accept+0x15/0x20 [af_alg]
   SYSC_accept4+0xff/0x210
 

[Kernel-packages] [Bug 1884766] Re: use-after-free in af_alg_accept() due to bh_lock_sock()

[Mauricio Faria de Oliveira]

** Description changed:

  [Impact]
  
-  * Users of the Linux kernel's crypto userspace API
-reported BUG() / kernel NULL pointer dereference
-errors after kernel upgrades.
+  * Users of the Linux kernel's crypto userspace API
+    reported BUG() / kernel NULL pointer dereference
+    errors after kernel upgrades.
  
-  * The stack trace signature is an accept() syscall
-going through af_alg_accept() and hitting errors
-usually in one of:
-- apparmor_sk_clone_security()
-- apparmor_sock_graft()
-- release_sock()
+  * The stack trace signature is an accept() syscall
+    going through af_alg_accept() and hitting errors
+    usually in one of:
+    - apparmor_sk_clone_security()
+    - apparmor_sock_graft()
+    - release_sock()
  
  [Fix]
-   
-  * This is a regression introduced by upstream commit
-37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
-in sk_destruct") which made its way through stable.
-
-  * The offending patch allows the critical regions
-of af_alg_accept() and af_alg_release_parent() to
-run concurrently; now with the "right" events on 2
-CPUs it might drop the non-atomic reference counter
-of the alg_sock then the sock, thus release a sock
-that is still in use.
  
-  * The fix is upstream commit 34c86f4c4a7b ("crypto:
-af_alg - fix use-after-free in af_alg_accept() due
-to bh_lock_sock()") [1]. It changes alg_sock's ref
-counter to atomic, which addresses the root cause.
-
+  * This is a regression introduced by upstream commit
+    37f96694cf73 ("crypto: af_alg - Use bh_lock_sock
+    in sk_destruct") which made its way through stable.
+ 
+  * The offending patch allows the critical regions
+    of af_alg_accept() and af_alg_release_parent() to
+    run concurrently; now with the "right" events on 2
+    CPUs it might drop the non-atomic reference counter
+    of the alg_sock then the sock, thus release a sock
+    that is still in use.
+ 
+  * The fix is upstream commit 34c86f4c4a7b ("crypto:
+    af_alg - fix use-after-free in af_alg_accept() due
+    to bh_lock_sock()") [1]. It changes alg_sock's ref
+    counter to atomic, which addresses the root cause.
+ 
  [Test Case]
  
-  * There is a synthetic test case available, which
-uses a kprobes kernel module to synchronize the
-concurrent CPUs on the instructions responsible
-for the problem; and a userspace part to run it.
+  * There is a synthetic test case available, which
+    uses a kprobes kernel module to synchronize the
+    concurrent CPUs on the instructions responsible
+    for the problem; and a userspace part to run it.
  
-  * The organic reproducer is the Varnish Cache Plus
-software with the Crypto vmod (which uses kernel
-crypto userspace API) under long, very high load.
-
-  * The patch has been verified on both reproducers
-with the 4.15 and 5.7 kernels.
-
+  * The organic reproducer is the Varnish Cache Plus
+    software with the Crypto vmod (which uses kernel
+    crypto userspace API) under long, very high load.
+ 
+  * The patch has been verified on both reproducers
+    with the 4.15 and 5.7 kernels.
+ 
   * More tests performed with 'stress-ng --af-alg'
-with 11 CPUs/hogs on Bionic/Disco/Eoan/Focal
+with 11 CPUs on Xenial/Bionic/Disco/Eoan/Focal
 (all on same version of stress-ng, V0.11.14)
+ 
 No regressions observed from original kernel.
 (the af-alg stressor can exercise almost all
 kernel crypto modules shipped with the kernel;
 so it checks more paths/crypto alg interfaces.)
-
+ 
  [Regression Potential]
  
-  * The fix patch does a fundamental change in how
-alg_sock reference counters work, plus another
-change to the 'nokey' counting. This of course
-*has* a risk of regression.
+  * The fix patch does a fundamental change in how
+    alg_sock reference counters work, plus another
+    change to the 'nokey' counting. This of course
+    *has* a risk of regression.
  
-  * Regressions theoretically could manifest as use
-after free errors (in case of undercounting) in
-the af_alg functions or silent memory leaks (in
-case of overcounting), but also other behaviors
-since reference counting is key to many things.
-
-  * FWIW, this patch has been written by the crypto
-subsystem maintainer, who certainly knows a lot
-of the normal and corner cases, thus giving the
-patch more credit.
-
-  * Testing with the organic reproducer ran as long
-as 5 days, without issues, so it does look good.
+  * Regressions theoretically could manifest as use
+    after free errors (in case of undercounting) in
+    the af_alg functions or silent memory leaks (in
+    case of overcounting), but also other behaviors
+    since reference counting is key to many things.
+ 
+  * FWIW, this patch has been written by the crypto
+    subsystem maintainer, who certainly knows a lot
+    of the normal and corner cases, thus giving the
+    

[Kernel-packages] [Bug 1215411] Re: libcpupower.so is not installed from linux-tools

[Brian Murray]

** Tags added: rls-gg-incoming

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

Title:
  libcpupower.so is not installed from linux-tools

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  Invalid
Status in linux source package in Eoan:
  In Progress

Bug description:
  The patch for bug 1158668 installs cpupower_$(abi_version) command-
  line tool as well as libcpupower.so.$(abi_version).

  This isn't particularly suitable for projects that previously used
  libcpufreq and intend to migrate to libcpupower, because the
  libcpupower.so symlink is no longer installed. The command-line tools
  can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)).

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

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

[Kernel-packages] [Bug 1882419] Re: Intel 3945ABG [8086:4227] Subsystem [8086:1010]: syslog flooded with "wlan0: Failed check-sdata-in-driver check, flags: 0x4"

[Ivo Kwee]

These are the part before the start of the error dump looping. One of
the lines is giving a 'Microcode SW error'. Is this the cause

Jun 30 22:46:07 sapporo kernel: [34465.678263] iwlwifi :3b:00.0:
Microcode SW error detected.  Restarting 0x200.

Syslog dump:

Jun 30 22:46:06 sapporo kernel: [34464.164632] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo wpa_supplicant[787]: wlp59s0: 
CTRL-EVENT-STARTED-CHANNEL-SWITCH freq=5540 ht_enabled=1 ch_offset=1 
ch_width=80 MHz cf1=5530 cf2=0
Jun 30 22:46:06 sapporo kernel: [34464.267457] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo kernel: [34464.369259] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo kernel: [34464.471749] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo kernel: [34464.574148] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo kernel: [34464.676582] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo kernel: [34464.778822] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo kernel: [34464.881254] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:06 sapporo kernel: [34464.983611] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:07 sapporo kernel: [34465.086076] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:07 sapporo kernel: [34465.188515] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:07 sapporo kernel: [34465.290813] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:07 sapporo kernel: [34465.393663] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:07 sapporo kernel: [34465.495660] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:07 sapporo kernel: [34465.598069] wlp59s0: cannot understand ECSA 
IE operating class, 0, ignoring
Jun 30 22:46:07 sapporo kernel: [34465.678263] iwlwifi :3b:00.0: Microcode 
SW error detected.  Restarting 0x200.
Jun 30 22:46:07 sapporo kernel: [34465.678486] iwlwifi :3b:00.0: Start IWL 
Error Log Dump:
Jun 30 22:46:07 sapporo kernel: [34465.678489] iwlwifi :3b:00.0: Status: 
0x0040, count: 6
Jun 30 22:46:07 sapporo kernel: [34465.678491] iwlwifi :3b:00.0: Loaded 
firmware version: 36.77d01142.0
Jun 30 22:46:07 sapporo kernel: [34465.678493] iwlwifi :3b:00.0: 0x0039 
| BAD_COMMAND 
Jun 30 22:46:07 sapporo kernel: [34465.678495] iwlwifi :3b:00.0: 0x0230 
| trm_hw_status0
Jun 30 22:46:07 sapporo kernel: [34465.678496] iwlwifi :3b:00.0: 0x 
| trm_hw_status1
Jun 30 22:46:07 sapporo kernel: [34465.678498] iwlwifi :3b:00.0: 0x000248EC 
| branchlink2
Jun 30 22:46:07 sapporo kernel: [34465.678500] iwlwifi :3b:00.0: 0x0003A862 
| interruptlink1
Jun 30 22:46:07 sapporo kernel: [34465.678501] iwlwifi :3b:00.0: 0x 
| interruptlink2
Jun 30 22:46:07 sapporo kernel: [34465.678503] iwlwifi :3b:00.0: 0x0002 
| data1
Jun 30 22:46:07 sapporo kernel: [34465.678504] iwlwifi :3b:00.0: 0xDEADBEEF 
| data2
Jun 30 22:46:07 sapporo kernel: [34465.678506] iwlwifi :3b:00.0: 0xDEADBEEF 
| data3
Jun 30 22:46:07 sapporo kernel: [34465.678507] iwlwifi :3b:00.0: 0x56C052FF 
| beacon time
Jun 30 22:46:07 sapporo kernel: [34465.678509] iwlwifi :3b:00.0: 0x5581DD08 
| tsf low
Jun 30 22:46:07 sapporo kernel: [34465.678511] iwlwifi :3b:00.0: 0x0007 
| tsf hi
Jun 30 22:46:07 sapporo kernel: [34465.678512] iwlwifi :3b:00.0: 0x 
| time gp1
Jun 30 22:46:07 sapporo kernel: [34465.678514] iwlwifi :3b:00.0: 0x69A0D064 
| time gp2
Jun 30 22:46:07 sapporo kernel: [34465.678515] iwlwifi :3b:00.0: 0x0001 
| uCode revision type
Jun 30 22:46:07 sapporo kernel: [34465.678517] iwlwifi :3b:00.0: 0x0024 
| uCode version major
Jun 30 22:46:07 sapporo kernel: [34465.678518] iwlwifi :3b:00.0: 0x77D01142 
| uCode version minor
Jun 30 22:46:07 sapporo kernel: [34465.678520] iwlwifi :3b:00.0: 0x0230 
| hw version
Jun 30 22:46:07 sapporo kernel: [34465.678522] iwlwifi :3b:00.0: 0x00C89000 
| board version
Jun 30 22:46:07 sapporo kernel: [34465.678523] iwlwifi :3b:00.0: 0x00280304 
| hcmd
Jun 30 22:46:07 sapporo kernel: [34465.678525] iwlwifi :3b:00.0: 0x24022080 
| isr0
Jun 30 22:46:07 sapporo kernel: [34465.678526] iwlwifi :3b:00.0: 0x0100 
| isr1
Jun 30 22:46:07 sapporo kernel: [34465.678528] iwlwifi :3b:00.0: 0x08201802 
| isr2
Jun 30 22:46:07 sapporo kernel: [34465.678529] iwlwifi :3b:00.0: 0x004144C0 
| isr3
Jun 30 22:46:07 sapporo kernel: [34465.678531] iwlwifi :3b:00.0: 0x 
| isr4
Jun 30 22:46:07 sapporo kernel: [34465.678532] iwlwifi :3b:00.0: 0x9284009D 
| last cmd Id
Jun 30