[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

[You-Sheng Yang]

@Kayvee, you should be able to install linux-oem-20.04b directly without
any additional ppa on Focal: https://packages.ubuntu.com/focal-updates
/linux-oem-20.04b.

Note it's linux-oem-20.04"b", not linux-oem-20.04.

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

Title:
  Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.10 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:
  Won't Fix
Status in linux-firmware source package in Groovy:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification: oem-5.6]

  [Impact]

  Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
  its prerequisite drivers.

  $ lspci
  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  [Fix]

  Tag ath11k-qca6390-bringup-202011301608 from ath tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
  first stable milestone on the platform/device under development since
  v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
  in vanilla kernel v5.10-rc4 except those starting from commit
  065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").

  While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
  in these components are also pulled.

  Besides, tx encapsulation
  https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
  and a couple more inclusive of 6 GHz capability, BSS Color were also
  pulled to satisfy API changes in mac80211/cfg80211.

  [Test Case]

  1. Install firmwares & boot from patched kernel,
  2. ath11k should be now up and running. Check with
 `sudo dmesg | grep ath11k`

  While this is going to bring massive changes to the kernel, as well as
  shared wireless stack that is not only used by ath11k but also many
  others, prebuilt kernel/firmware packages were deployed on platforms
  with and without ath11k for regression tests, and so far the results are
  positive.

  [Where problems could occur]

  ath11k and its relying parts have never been enabled in oem-5.6, so
  changes to them should have little effect on most platforms. For
  platforms equip QCA6390, this will be the first time they're probed and
  enabled, and as the driver is still under polishing, there can be
  regressions, performance lost, power consumption increase at this
  moment.

  Changes to wireless stack could also be an issue as this introduces
  interface changes to the API, so maybe DKMS packages in the wild will be
  affected.

  == SRU for U/OEM-5.10 ==

  [SRU Justification: U/OEM-5.10]

  [Impact]

  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  $ lspci
  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  [Fix]

  25 additional fixes in ath tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag
  ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms,
  and firmware updates from mainline are required.

  [Test Case]

  1. Install firmwares & boot from patched kernel,
  2. ath11k should be now up and running. Check with
     `sudo dmesg | grep ath11k`

  [Where problems could occur]

  There has been a lot patches landed in kernel since 5.7 devel cycle. The
  last bits here has merge base with mainline at v5.10-rc4, and since then
  only patches for ath11k itself has been committed.

  == Original Bug Description ==

  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1842 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubun

[Kernel-packages] [Bug 1906817] Re: Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535]: ath10k_pci: failed to receive scan abortion completion: timed out

[You-Sheng Yang]

Dec  4 10:45:16 notebook kernel: [ 3696.140418] ath10k_pci :3a:00.0: failed 
to receive scan abortion completion: timed out
Dec  4 10:45:16 notebook kernel: [ 3696.140427] ath10k_pci :3a:00.0: failed 
to stop scan: -110
Dec  4 10:45:16 notebook kernel: [ 3696.140429] ath10k_pci :3a:00.0: failed 
to start hw scan: -110
Dec  4 10:46:17 notebook kernel: [ 3756.803675] ath10k_pci :3a:00.0: wmi 
command 20482 timeout, restarting hardware
Dec  4 10:46:17 notebook kernel: [ 3756.803713] ath10k_pci :3a:00.0: failed 
to delete WMI vdev 1: -11
Dec  4 10:46:17 notebook kernel: [ 3756.803750] ath10k_pci :3a:00.0: failed 
to set 2g txpower 20: -108
Dec  4 10:46:17 notebook kernel: [ 3756.803755] ath10k_pci :3a:00.0: failed 
to setup tx power 20: -108
Dec  4 10:46:17 notebook kernel: [ 3756.803826] ath10k_pci :3a:00.0: failed 
to recalc tx power: -108
Dec  4 10:46:17 notebook kernel: [ 3756.804046] ath10k_pci :3a:00.0: failed 
to set inactivity time for vdev 0: -108
Dec  4 10:46:17 notebook kernel: [ 3756.804065] ath10k_pci :3a:00.0: failed 
to setup powersave: -108
Dec  4 10:46:17 notebook kernel: [ 3756.804139] wlp58s0: deauthenticating from 
d8:07:b6:86:e9:57 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec  4 10:46:17 notebook kernel: [ 3756.804154] ath10k_pci :3a:00.0: failed 
to set inactivity time for vdev 0: -108
Dec  4 10:46:17 notebook kernel: [ 3756.804173] ath10k_pci :3a:00.0: failed 
to setup powersave: -108
Dec  4 10:46:17 notebook kernel: [ 3756.804185] ath10k_pci :3a:00.0: failed 
to set PS Mode 0 for vdev 0: -108
Dec  4 10:46:20 notebook kernel: [ 3759.859953] ath10k_pci :3a:00.0: failed 
to receive initialized event from target: 
Dec  4 10:46:23 notebook kernel: [ 3763.135730] ath10k_pci :3a:00.0: failed 
to receive initialized event from target: 
Dec  4 10:46:23 notebook kernel: [ 3763.135735] ath10k_warn: 3 callbacks 
suppressed
Dec  4 10:46:23 notebook kernel: [ 3763.135737] ath10k_pci :3a:00.0: failed 
to wait for target init: -110
Dec  4 10:46:23 notebook kernel: [ 3763.137928] ieee80211 phy0: Hardware 
restart was requested
Dec  4 10:46:23 notebook kernel: [ 3763.137978] ath10k_pci :3a:00.0: failed 
to flush transmit queue (skip 1 ar-state 2): 1250
Dec  4 10:46:23 notebook kernel: [ 3763.139611] ath10k_pci :3a:00.0: failed 
to delete peer d8:07:b6:86:e9:57 for vdev 0: -108

** Summary changed:

- kernel crash with ath10k_pci
+ Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535]: ath10k_pci: 
failed to receive scan abortion completion: timed out

** Tags added: hwe-networking-wifi

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

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

Title:
  Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1a56:1535]:
  ath10k_pci: failed to receive scan abortion completion: timed out

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Dell XPS 13 9360 has experienced in the past week three kernel
  crashes related to ath10k_pci. I was using my laptop and no particular
  network activity was taking place: ssh connections in one case, web
  browsing in another, email sync in the third. The symptom is the
  network stops working. When I try from Network Manager to set wireless
  off, the system starts to go nuts. Trying to reboot leads to a
  deadlock with the message:

  Virtual device wlp58s0 asks to queue packet!

  going on and on and the only way out is through the power button
  cycle. At the reboot, the wireless network is turned off. The kernel
  reports a WARNING, and I am attaching it.

  OS is

  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=78036de6-f421-45db-96fa-2cb1f579cfd5
  InstallationDate: Installed on 2016-10-29 (1496 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=45391f5c-b192-4a4e-95b1-68cc8390ca8b ro pci=noaer quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1001) is not owned by us (

[Kernel-packages] [Bug 1913342] Re: zfs.8 man page snapshot listing instructions are confusing

[Paul Jackson]

Filed upstream, as you suggested:

https://github.com/openzfs/zfs/issues/11562

It's been a couple of years since I've pushed a pull request on github,
so I'll probably remain lazy and not get around to it in this case, to
avoid the extra time it would take me to recall just how to do it.  A
few minutes work for someone actively familiar with the process is
likely a couple hours work for a (relapsed back to) clueless git such as
myself.

Thanks for your spot on initial response to this here bug.  Keep up the
good zfs work.

** Bug watch added: github.com/openzfs/zfs/issues #11562
   https://github.com/openzfs/zfs/issues/11562

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

Title:
  zfs.8 man page snapshot listing instructions are confusing

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  The zfs.8 man page describes in 3 places how to include snapshots in
  "zfs list":

  1) Snapshots are displayed if the listsnaps property is on (the default is 
off).
  2) Snapshots are displayed if the listsnaps property is on.  The default is 
off.  See zpool(8) for more information on pool properties.
  3) For example, specifying -t snapshot displays only snapshots.

  The first of these has twice now (I'm just learning zfs) sent me down
  a rabbit hole, looking for a zfs dataset property "listsnaps".  There
  is no such property (of datasets).

  I'm on version 0.8.3 of zfsutils-linux that has this man page, but
  when I look at https://zfsonlinux.org/manpages/0.8.6/man8/zfs.8.html
  it seems that the above is still true in 0.8.6

  Suggestion, to help us newbies reduce our learning time to list
  snapshots:

  Change both of the first 2 of the above 3 places in zfs.8 to:
  "
  "zfs list" displays snapshots only if either the "listsnapshots" property of 
the underlying zpool is on, or if the "zfs list -t snapshot" option is 
specified.

  Extra Credit:

  Just now it seems to me that the following command does _NOT_ list
  snapshots, on a dataset that has some snapshots ... so the zfs.8
  documentation that the "zfs list -t type" can be a "comma-separated
  list of types to display" seems incorrect:

  zfs list -t filesystem,snapshot myzfsdataset

  Whether this "Extra Credit" discrepancy is a bug in the documentation,
  or in the zfs command code, or newbie operator error, I'll leave as an
  exercise to the reader .

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.5
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Jan 26 13:41:16 2021
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

[Aksahat]

Thankyou :fabinanbur for you help :) very helpful.

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 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:
  Fix Released
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
  vectors") currently in vanilla kernel tree for v5.11.

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Where problems could occur]

  An unpatched kernel will not be able to probe SATA controllers moved
  behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
  attached on it completely unusable. With this change, kernel would
  then be able to probe them but may also suffer from issues that only
  occur under such configuration. However, the worst case is to move away
  sata disks from VMD bus as they are currently without this fix, so the
  risk here should be justified.

  == Previous SRU ==

  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

[Kernel-packages] [Bug 1894977] Re: IBM-iobrick patches for Ubuntu 20.04

[Launchpad Bug Tracker]

[Expired for Ubuntu on IBM z Systems because there has been no activity
for 60 days.]

** Changed in: ubuntu-z-systems
   Status: Incomplete => Expired

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

Title:
   IBM-iobrick patches for Ubuntu 20.04

Status in Ubuntu on IBM z Systems:
  Expired
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  The request is to backport 
  09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during 
create and destroy
  with it the below list (divided to four sets) is required.

  most of the patches applied cleanly above focal tree four exceptions.

  1. 806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
  2. b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
  3. 1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying 
them
  4. b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
  the rejected hunks need to be manually applied.
  The rejected hunks are due to true<-->1 false<-->0 exchange added support for 
wc (b9358bdbc713) and other minor reasons.  

   set 0: Unrelated code cleanups (needed for applying  cleanly the mr cache 
set)
   https://patchwork.kernel.org/cover/11170991/
   909624d8db5b IB/cm: Use container_of() instead of typecast
   6f26b2ac699c IB/mlx5: Remove unnecessary else statement
   2d67c0798821 IB/mlx5: Remove unnecessary return statement
   4b2a67362e78 RDMA/mlx5: Group boolean parameters to take less space

   set 1: Rework the locking and datastructures for mlx5 implicit ODP
   https://patchwork.kernel.org/cover/11181509/
   46870b2391d5 RDMA/odp: Remove broken debugging call to invalidate_range
   09689703d29a RDMA/mlx5: Do not race with mlx5_ib_invalidate_range during 
create and destroy
   d561987f34f2 RDMA/mlx5: Do not store implicit children in the odp_mkeys 
xarray
   5256edcb98a1 RDMA/mlx5: Rework implicit ODP destroy
   b70d785d237c RDMA/mlx5: Avoid double lookups on the pagefault path
   3389baa831b6 RDMA/mlx5: Reduce locking in implicit_mr_get_data()
   423f52d65005 RDMA/mlx5: Use an xarray for the children of an implicit ODP
   54375e738295 RDMA/mlx5: Split implicit handling from pagefault_mr
   9162420dde49 RDMA/mlx5: Set the HW IOVA of the child MRs to their place in 
the tree
   c2edcd69351f RDMA/mlx5: Lift implicit_mr_alloc() into the two routines that 
call it
   3d5f3c54e7bc RDMA/mlx5: Rework implicit_mr_get_data
   74bddb3682f6 RDMA/mlx5: Delete struct mlx5_priv->mkey_table
   806b101b2bfa RDMA/mlx5: Use a dedicated mkey xarray for ODP
   50211ec9443f RDMA/mlx5: Split sig_err MR data into its own xarray
   fb985e278a30 RDMA/mlx5: Use SRCU properly in ODP prefetch

  
   set 2: Consolidate the mmu notifier interval_tree and locking (only first 
two patches from this set)
   https://patchwork.kernel.org/cover/11240081/
   99cb252f5e68 mm/mmu_notifier: add an interval tree notifier
   56f434f40f05 mm/mmu_notifier: define the header pre-processor parts even if 
disabled

  
   also needed for applying  mr cache set cleanly.
   03232cc43cff IB/mlx5: Introduce and use mkey context setting helper routine

   set 3: MR cache fixes and refactoring
   https://www.spinics.net/lists/linux-rdma/msg89706.html
   aad719dcf379 RDMA/mlx5: Allow MRs to be created in the cache synchronously
   1c78a21a0c6f RDMA/mlx5: Revise how the hysteresis scheme works for cache 
filling
   b9358bdbc713 RDMA/mlx5: Fix locking in MR cache work queue
   ad2d3ef46d2a RDMA/mlx5: Lock access to ent->available_mrs/limit when doing 
queue_work
   a1d8854aae4e RDMA/mlx5: Fix MR cache size and limit debugfs
   1769c4c57548 RDMA/mlx5: Always remove MRs from the cache before destroying 
them
   b91e1751fbce RDMA/mlx5: Simplify how the MR cache bucket is located
   7c8691a396bd RDMA/mlx5: Rename the tracking variables for the MR cache
   f743ff3b37df RDMA/mlx5: Replace spinlock protected write with atomic var
   a3cfdd392811 {IB,net}/mlx5: Move asynchronous mkey creation to mlx5_ib
   fc6a9f86f08a {IB,net}/mlx5: Assign mkey variant in mlx5_ib only
   54c62e13ad76 {IB,net}/mlx5: Setup mkey variant before mr create command 
invocation

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

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

[Kernel-packages] [Bug 1906817] Re: kernel crash with ath10k_pci

[Launchpad Bug Tracker]

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

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

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

Title:
  kernel crash with ath10k_pci

Status in linux package in Ubuntu:
  Expired

Bug description:
  My Dell XPS 13 9360 has experienced in the past week three kernel
  crashes related to ath10k_pci. I was using my laptop and no particular
  network activity was taking place: ssh connections in one case, web
  browsing in another, email sync in the third. The symptom is the
  network stops working. When I try from Network Manager to set wireless
  off, the system starts to go nuts. Trying to reboot leads to a
  deadlock with the message:

  Virtual device wlp58s0 asks to queue packet!

  going on and on and the only way out is through the power button
  cycle. At the reboot, the wireless network is turned off. The kernel
  reports a WARNING, and I am attaching it.

  OS is

  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  Codename: focal
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 20.04
  HibernationDevice: RESUME=UUID=78036de6-f421-45db-96fa-2cb1f579cfd5
  InstallationDate: Installed on 2016-10-29 (1496 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic 
root=UUID=45391f5c-b192-4a4e-95b1-68cc8390ca8b ro pci=noaer quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1001) is not owned by us (uid 0), but by uid 1001! (This could e.g. 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-56-generic N/A
   linux-backports-modules-5.4.0-56-generic  N/A
   linux-firmware1.187.4
  Tags:  focal
  Uname: Linux 5.4.0-56-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-11 (206 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 07/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.14.2
  dmi.board.name: 05JK94
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.product.sku: 075B
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1872128] Re: Lenovo QCA9377 802.11ac Wireless Network Adapter [168c:0042] Subsystem [17aa:4035]: Broken firmware, no 802.11n support

[You-Sheng Yang]

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Lenovo QCA9377 802.11ac Wireless Network Adapter [168c:0042] Subsystem
  [17aa:4035]: Broken firmware, no 802.11n support

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  /lib/firmware/ath10k/QCA9377/hw1.0/firmware_6.bin
  Results in no support for 5GHz bands at all, speed limited to about 25 MBit/s
  /lib/firmware/ath10k/QCA9377/hw1.0/firmware_5.bin
  Seems to support 5GHz bands, but speed is still stuck at about 25 MBit/s

  Downloading and installing as firmware_5.bin (and deleting firmware_6.bin):
  
https://github.com/kvalo/ath10k-firmware/blob/master/QCA9377/hw1.0/CNSS.TF.1.0/firmware-5.bin_CNSS.TF.1.0-00267-QCATFSWPZ-1?raw=true
  speed easily reaches 250MBit/s

  Firmware tip found on
  
https://www.reddit.com/r/linuxmint/comments/fjkg4x/qualcomm_atheros_qca9377_5ghz_issue/

  Router in use is Synology MR2200ac

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187 [modified: 
lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin]
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Apr 10 21:07:20 2020
  Dependencies:
   
  InstallationDate: Installed on 2017-05-28 (1048 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to focal on 2020-04-04 (6 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  reimar 1653 F pulseaudio
reimar 1659 F pipewire-media-
   /dev/snd/seq:reimar 1652 F pipewire
  CasperMD5CheckResult: skip
  Dependencies:
   
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2017-05-28 (1337 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80MX
  Package: linux-firmware 1.190.3
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-40-generic 
root=UUID=6f186662-358a-46e3-8b78-e4fcb06f7401 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18
  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.8.0-40-generic N/A
   linux-backports-modules-5.8.0-40-generic  N/A
   linux-firmware1.190.3
  StagingDrivers: ashmem_linux
  Tags:  groovy staging
  Uname: Linux 5.8.0-40-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-10-07 (109 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 06/29/2018
  dmi.bios.release: 2.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DCCN43WW(V2.12)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo E31-80
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo E31-80
  dmi.ec.firmware.release: 2.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrDCCN43WW(V2.12):bd06/29/2018:br2.43:efr2.43:svnLENOVO:pn80MX:pvrLenovoE31-80:rvnLENOVO:rnLenovoE31-80:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoE31-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MX
  dmi.product.sku: LENOVO_MT_80MX_BU_idea_FM_Lenovo E31-80
  dmi.product.version: Lenovo E31-80
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change

[jeremyszu]

** Tags added: originate-from-1912603

** Tags added: originate-from-1912599

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

Title:
   Fix regression introduced by codec PM change

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After the codec PM optimization, laptops with SOF may take very long to
  suspend. In addition to that, HDA may not be able to be runtim suspended
  again after resume from hibernation.

  [Fix]
  Prevent the SOF driver touches codec during system suspend, and properly
  refcount the PM usage counter.

  [Test]
  On an affected SOF system, it takes 5 mins to suspend.
  On another affected HDA system, S4 resume causes high power consumption
  becuase HDA controller can't be runtime suspended.

  Both issues are gone by applying these patches.

  [Where problems could occur]
  If somehow any laptop depends on the old behavior to work properly, this
  can break them. It's highly unlikely though.

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

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

[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot

[Kai-Heng Feng]

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

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

Title:
  kernel 5.8 general protection fault at boot

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26)
  crashes at boot with many general protection faults, on my Intel NUC
  10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-28-generic 5.8.0-28.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benp   2912 F pulseaudio
   /dev/snd/controlC1:  benp   2912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 11:51:07 2020
  InstallationDate: Installed on 2020-10-08 (35 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago)
  dmi.bios.date: 08/17/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0045.2020.0817.1709
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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

[Kernel-packages] [Bug 1879633] Re: Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

[Kayvee]

Hello @andch,
I am also having similar issues. I have a XPS 13 9310, Core i7-1165g7 with 32GB 
of RAM and followed your steps to add the canonical-kernel-team ppa and install 
the two packages. That repository no longer has linux-headers-oem-20.04b but 
has linux-headers-oem-20.04. 

Here's what I have: 
linux-image-oem-20.04/groovy,now 5.8.0.42.46 amd64 [installed]
linux-headers-oem-20.04/groovy,now 5.8.0.42.46 amd64 [installed]

My XPS firmware (bios version) is 1.2.5.
After running fwupdmgr get-updates and fwupdmgr get-upgrades I do not see any 
new updates available for my machine. 

I cannot get the WiFi working. Any help is appreciated.

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

Title:
  Killer 500s (QCA6390) WLAN/BT [17cb:1101] unavailable

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-5.10 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:
  Won't Fix
Status in linux-firmware source package in Groovy:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification: oem-5.6]

  [Impact]

  Qualcomm QCA6390 series not recognized due to the lack of ath11k and all
  its prerequisite drivers.

  $ lspci
  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  [Fix]

  Tag ath11k-qca6390-bringup-202011301608 from ath tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git) marks
  first stable milestone on the platform/device under development since
  v5.6-rc1. Most of the commits under this tag, ~350 commits, have been
  in vanilla kernel v5.10-rc4 except those starting from commit
  065c9528cc50 ("ath11k: add 64bit check before reading msi high addr").

  While ath11k depends on MHI bus, qrtr and qmi helpers, changes falling
  in these components are also pulled.

  Besides, tx encapsulation
  https://lore.kernel.org/linux-wireless/20200908123702.88454-1-...@nbd.name/
  and a couple more inclusive of 6 GHz capability, BSS Color were also
  pulled to satisfy API changes in mac80211/cfg80211.

  [Test Case]

  1. Install firmwares & boot from patched kernel,
  2. ath11k should be now up and running. Check with
 `sudo dmesg | grep ath11k`

  While this is going to bring massive changes to the kernel, as well as
  shared wireless stack that is not only used by ath11k but also many
  others, prebuilt kernel/firmware packages were deployed on platforms
  with and without ath11k for regression tests, and so far the results are
  positive.

  [Where problems could occur]

  ath11k and its relying parts have never been enabled in oem-5.6, so
  changes to them should have little effect on most platforms. For
  platforms equip QCA6390, this will be the first time they're probed and
  enabled, and as the driver is still under polishing, there can be
  regressions, performance lost, power consumption increase at this
  moment.

  Changes to wireless stack could also be an issue as this introduces
  interface changes to the API, so maybe DKMS packages in the wild will be
  affected.

  == SRU for U/OEM-5.10 ==

  [SRU Justification: U/OEM-5.10]

  [Impact]

  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  $ lspci
  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  [Fix]

  25 additional fixes in ath tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git), tag
  ath11k-qca6390-bringup-202011301608 to resolve issues on TGL platforms,
  and firmware updates from mainline are required.

  [Test Case]

  1. Install firmwares & boot from patched kernel,
  2. ath11k should be now up and running. Check with
     `sudo dmesg | grep ath11k`

  [Where problems could occur]

  There has been a lot patches landed in kernel since 5.7 devel cycle. The
  last bits here has merge base with mainline at v5.10-rc4, and since then
  only patches for ath11k itself has been committed.

  == Original Bug Description ==

  Qualcomm QCA6390 series not recognized due to the lack of ath11k
  driver.

  :55:00.0 Unassigned class [ff00]: Qualcomm Device [17cb:1101]
   Subsystem: Bigfoot Networks, Inc. Device [1a56:a501]

  Depending on bug 1891632 to fix Wi-Fi dead after resumed from suspend.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  

[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load

[Tony Eckel]

Have an EliteDesk mini 705 G2 with identical issue and none of the fixes worked.
running Ubuntu 20.04.2 LTS
So it isn't fixed.

What do you need to troubleshoot this?

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

Title:
  14e4:1687 broadcom tg3 network driver disconnects under high load

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The tg3 broadcom network driver that binds with chipset 5762 goes offline and 
unable to recover (even with tg3 watchdog timeout) when network transmit is 
under high load.  Call trace:
  https://launchpadlibrarian.net/204185480/dmesg

  When this happens, only a reboot would be able to fix it.  Sometimes,
  however, bringing the interface offline and online (via ifconfig)
  would recover networking.  I've also tested with the latest tg3 driver
  (dec 2014 version) and networking is still problematic.  I have also
  disabled TSO, GSO etc... with ethtool and the bug still surfaces.
  This bug may be related to the integrated Firmware.

  Here is the procedure to replicate the issue because it is hard to
  replicate it under moderate network load.

  1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a 
Ubuntu/Kubunu Live CD 14.04-15.04.
  2. from another machine: start 5 sessions, repetitively copy (scp with public 
key authentication) a 70 meg file back and forth to the tg3 machine in each 
session. (not sure if this is necessary)
  3. create a 1GB file on the tg3 machine, with something like dd 
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
  4. from another machine: repetitively scp copy that 1GB file from the tg3 
machine. This can be done with something like:

  while [ 0 ]; do
     scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
  done;

  Networking will mostly goes offline in about 10-30 minutes.

  WORKAROUND: Add udev rule to make the changes permanent in 
/etc/udev/rules.d/80-tg3-fix.rules :
  ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", 
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kubuntu3748 F pulseaudio
   /dev/snd/controlC0:  kubuntu3748 F pulseaudio
  CasperVersion: 1.360
  Date: Thu Apr 23 11:16:24 2015
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash ---
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  RfKill:

  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L06 v02.15
  dmi.board.asset.tag: 2UA5041TG4
  dmi.board.name: 2215
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA5041TG4
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP EliteDesk 705 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1913812] Re: snd_fireworks module fails to load

[Len Ovens]

$ uname -a
Linux studio2104 5.11.0-051100rc5-lowlatency #202101242134 SMP PREEMPT Mon Jan 
25 02:40:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

$ sudo dmesg |grep fire
[sudo] password for joe: 
[0.662618] firewire_ohci :04:00.0: added OHCI v1.10 device as card 0, 8 
IR + 8 IT contexts, quirks 0x2
[1.162720] firewire_core :04:00.0: created device fw0: GUID 
7856341278563412, S800
[1.162727] firewire_core :04:00.0: phy config: new root=ffc1, 
gap_count=5
[4.182294] firewire_core :04:00.0: created device fw1: GUID 
0014860268b568f1, S400
[7.795669] systemd[1]: Starting Uncomplicated firewall...
[7.805444] systemd[1]: Finished Uncomplicated firewall.
[8.586593] snd_fireworks fw1.0: EFW transaction timed out
[8.586612] snd_fireworks fw1.0: Sound card registration failed: -5

$ ls /proc/asound
AudioPCI  card2  cardshwdep  modules  PCH  seq version
card1 card3  devices  M66oss  pcm  timers

No Audiofire12

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

Title:
  snd_fireworks module fails to load

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg contains these two lines:
  [8.593334] snd_fireworks fw1.0: EFW transaction timed out
  [8.594276] snd_fireworks fw1.0: Sound card registration failed: -5
  And ALSA therefore does not see my echo audiofire 12.

  The device continues to work fine as a backend for jackdbus2 using the
  FFADO kernel modules. The snd_fireworks did work fine with this device
  in ubuntustudio 20.04 but also fails in ubuntustudio 20.10 (which I
  don't use)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-modules-5.8.0-36-lowlatency 5.8.0-36.40+21.04.1
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-lowlatency 5.8.18
  Uname: Linux 5.8.0-36-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Jan 29 13:14:58 2021
  Dependencies:
   
  InstallationDate: Installed on 2021-01-29 (0 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210128)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  Lsusb:
   Bus 002 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
  MachineType: ASUS All Series
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb3
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-36-lowlatency N/A
   linux-backports-modules-5.8.0-36-lowlatency  N/A
   linux-firmware   1.194
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0604:bd07/16/2013:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1911331] Re: Bionic update: upstream stable patchset 2021-01-12

[Kelsey Skunberg]

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

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

Title:
  Bionic update: upstream stable patchset 2021-01-12

Status in linux package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-raspi2 source package in Bionic:
  Fix Committed
Status in linux-snapdragon source package in Bionic:
  New

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-12

  Ported from the following upstream stable releases:
  v4.14.213, v4.19.164

     from git://git.kernel.org/

  spi: bcm2835aux: Fix use-after-free on unbind
  spi: bcm2835aux: Restore err assignment in bcm2835aux_spi_probe
  iwlwifi: pcie: limit memory read spin time
  arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.
  iwlwifi: mvm: fix kernel panic in case of assert during CSA
  ARC: stack unwinding: don't assume non-current task is sleeping
  scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE
  soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)
  platform/x86: acer-wmi: add automatic keyboard background light toggle key as 
KEY_LIGHTS_TOGGLE
  Input: cm109 - do not stomp on control URB
  Input: i8042 - add Acer laptops to the i8042 reset list
  pinctrl: amd: remove debounce filter setting in IRQ type setting
  kbuild: avoid static_assert for genksyms
  scsi: be2iscsi: Revert "Fix a theoretical leak in beiscsi_create_eqs()"
  x86/mm/mem_encrypt: Fix definition of PMD_FLAGS_DEC_WP
  PCI: qcom: Add missing reset for ipq806x
  net: stmmac: free tx skb buffer in stmmac_resume()
  tcp: fix cwnd-limited bug for TSO deferral where we send nothing
  net/mlx4_en: Avoid scheduling restart task if it is already running
  net/mlx4_en: Handle TX error CQE
  net: stmmac: delete the eee_ctrl_timer after napi disabled
  net: stmmac: dwmac-meson8b: fix mask definition of the m250_sel mux
  net: bridge: vlan: fix error return code in __vlan_add()
  mac80211: mesh: fix mesh_pathtbl_init() error path
  USB: dummy-hcd: Fix uninitialized array use in init()
  USB: add RESET_RESUME quirk for Snapscan 1212
  ALSA: usb-audio: Fix potential out-of-bounds shift
  ALSA: usb-audio: Fix control 'access overflow' errors from chmap
  xhci: Give USB2 ports time to enter U3 in bus suspend
  USB: UAS: introduce a quirk to set no_write_same
  USB: sisusbvga: Make console support depend on BROKEN
  UBUNTU: [Config] updateconfigs for USB_SISUSBVGA_CON
  ALSA: pcm: oss: Fix potential out-of-bounds shift
  serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
  drm: fix drm_dp_mst_port refcount leaks in drm_dp_mst_allocate_vcpi
  pinctrl: merrifield: Set default bias in case no particular value given
  pinctrl: baytrail: Avoid clearing debounce value when turning it off
  ARM: dts: sun8i: v3s: fix GIC node memory range
  gpio: mvebu: fix potential user-after-free on probe
  scsi: bnx2i: Requires MMU
  can: softing: softing_netdev_open(): fix error handling
  RDMA/cm: Fix an attempt to use non-valid pointer when cleaning timewait
  kernel/cpu: add arch override for clear_tasks_mm_cpumask() mm handling
  drm/tegra: sor: Disable clocks on error in tegra_sor_init()
  vxlan: Add needed_headroom for lower device
  vxlan: Copy needed_tailroom from lowerdev
  scsi: mpt3sas: Increase IOCInit request timeout to 30s
  dm table: Remove BUG_ON(in_interrupt())
  soc/tegra: fuse: Fix index bug in get_process_id
  USB: serial: option: add interface-number sanity check to flag handling
  USB: gadget: f_acm: add support for SuperSpeed Plus
  USB: gadget: f_midi: setup SuperSpeed Plus descriptors
  usb: gadget: f_fs: Re-use SS descriptors for SuperSpeedPlus
  USB: gadget: f_rndis: fix bitrate for SuperSpeed and above
  usb: chipidea: ci_hdrc_imx: Pass DISABLE_DEVICE_STREAMING flag to imx6ul
  ARM: dts: exynos: fix roles of USB 3.0 ports on Odroid XU
  ARM: dts: exynos: fix USB 3.0 VBUS control and over-current pins on Exynos5410
  ARM: dts: exynos: fix USB 3.0 pins supply being turned off on Odroid XU
  HID: i2c-hid: add Vero K147 to descriptor override
  serial_core: Check for port state when tty is in error state
  quota: Sanity-check quota file headers on load
  media: msi2500: assign SPI bus nu

[Kernel-packages] [Bug 1911235] Re: Groovy update: upstream stable patchset 2021-01-12

[Kelsey Skunberg]

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

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: New => Fix Committed

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

Title:
  Groovy update: upstream stable patchset 2021-01-12

Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux source package in Groovy:
  Fix Committed
Status in linux-gcp source package in Groovy:
  Fix Committed
Status in linux-raspi source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-12

  Ported from the following upstream stable releases:
  v5.4.79, v5.9.10
  v5.4.80, v5.9.11
  v5.4.81, v5.9.12
  v5.4.82, v5.9.13
  v5.4.83, v5.9.14

     from git://git.kernel.org/

  powerpc: Only include kup-radix.h for 64-bit Book3S
  leds: lm3697: Fix out-of-bound access
  Input: sunkbd - avoid use-after-free in teardown paths
  mac80211: always wind down STA state
  can: proc: can_remove_proc(): silence remove_proc_entry warning
  powerpc/smp: Call rcu_cpu_starting() earlier
  KVM: x86: clflushopt should be treated as a no-op by emulation
  ACPI: GED: fix -Wformat
  net: lantiq: Add locking for TX DMA channel
  UBUNTU: upstream stable to v5.4.79, v5.9.10
  ah6: fix error return code in ah6_input()
  atm: nicstar: Unmap DMA on send error
  bnxt_en: read EEPROM A2h address using page 0
  devlink: Add missing genlmsg_cancel() in devlink_nl_sb_port_pool_fill()
  enetc: Workaround for MDIO register access issue
  Exempt multicast addresses from five-second neighbor lifetime
  inet_diag: Fix error path to cancel the meseage in inet_req_diag_fill()
  ipv6: Fix error path to cancel the meseage
  lan743x: fix issue causing intermittent kernel log warnings
  lan743x: prevent entire kernel HANG on open, for some platforms
  mlxsw: core: Use variable timeout for EMAD retries
  net: b44: fix error return code in b44_init_one()
  net: bridge: add missing counters to ndo_get_stats64 callback
  netdevsim: set .owner to THIS_MODULE
  net: dsa: mv88e6xxx: Avoid VTU corruption on 6097
  net: ethernet: mtk-star-emac: fix error return code in mtk_star_enable()
  net: ethernet: mtk-star-emac: return ok when xmit drops
  net: ethernet: ti: am65-cpts: update ret when ptp_clock is ERROR
  net: ethernet: ti: cpsw: fix cpts irq after suspend
  net: ethernet: ti: cpsw: fix error return code in cpsw_probe()
  net: ftgmac100: Fix crash when removing driver
  net: Have netpoll bring-up DSA management interface
  net: ipa: lock when freeing transaction
  netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
  netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
  net: lantiq: Wait for the GPHY firmware to be ready
  net/mlx4_core: Fix init_hca fields offset
  net/mlx5e: Fix refcount leak on kTLS RX resync
  net/ncsi: Fix netlink registration
  net: phy: mscc: remove non-MACSec compatible phy
  net: qualcomm: rmnet: Fix incorrect receive packet handling during cleanup
  net/smc: fix direct access to ib_gid_addr->ndev in smc_ib_determine_gid()
  net: stmmac: Use rtnl_lock/unlock on netif_set_real_num_rx_queues() call
  net/tls: fix corrupted data in recvmsg
  net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
  page_frag: Recover from memory pressure
  qed: fix error return code in qed_iwarp_ll2_start()
  qed: fix ILT configuration of SRC block
  qlcnic: fix error return code in qlcnic_83xx_restart_hw()
  sctp: change to hold/put transport for proto_unreach_timer
  tcp: only postpone PROBE_RTT if RTT is < current min_rtt estimate
  vsock: forward all packets to the host when no H2G is registered
  net/mlx5e: Fix check if netdev is bond slave
  net/mlx5: Add handling of port type in rule deletion
  net/mlx5: Clear bw_share upon VF disable
  net/mlx5: Disable QoS when min_rates on all VFs are zero
  PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter
  net: fec: Fix reference count leak in fec series ops
  net/tls: Fix wrong record sn in async mode of device resync
  net: usb: qmi_wwan: Set DTR quirk for

[Kernel-packages] [Bug 1911476] Re: Groovy update: upstream stable patchset 2021-01-13

[Kelsey Skunberg]

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

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: New => 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/1911476

Title:
  Groovy update: upstream stable patchset 2021-01-13

Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux source package in Groovy:
  Fix Committed
Status in linux-gcp source package in Groovy:
  Fix Committed
Status in linux-kvm source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-13

  Ported from the following upstream stable releases:
  v5.4.84, v5.9.15,
  v5.4.85, v5.9.16

     from git://git.kernel.org/

  Kbuild: do not emit debug info for assembly with LLVM_IAS=1
  mm/zsmalloc.c: drop ZSMALLOC_PGTABLE_MAPPING
  UBUNTU: [Config] updateconfigs for ZSMALLOC_PGTABLE_MAPPING
  kprobes: Remove NMI context check
  kprobes: Tell lockdep about kprobe nesting
  ASoC: Intel: bytcr_rt5640: Fix HP Pavilion x2 Detachable quirks
  tools/bootconfig: Fix to check the write failure correctly
  net, xsk: Avoid taking multiple skbuff references
  bpftool: Fix error return value in build_btf_type_table
  vhost-vdpa: fix page pinning leakage in error path (rework)
  powerpc/64s: Fix hash ISA v3.0 TLBIEL instruction generation
  batman-adv: Consider fragmentation for needed_headroom
  batman-adv: Reserve needed_*room for fragments
  batman-adv: Don't always reallocate the fragmentation skb head
  ipvs: fix possible memory leak in ip_vs_control_net_init
  ibmvnic: handle inconsistent login with reset
  ibmvnic: stop free_all_rwi on failed reset
  ibmvnic: avoid memset null scrq msgs
  ibmvnic: delay next reset if hard reset fails
  ibmvnic: track pending login
  ibmvnic: send_login should check for crq errors
  ibmvnic: reduce wait for completion time
  drm/rockchip: Avoid uninitialized use of endpoint id in LVDS
  drm/panel: sony-acx565akm: Fix race condition in probe
  can: m_can: tcan4x5x_can_probe(): fix error path: remove erroneous 
clk_disable_unprepare()
  can: sja1000: sja1000_err(): don't count arbitration lose as an error
  can: sun4i_can: sun4i_can_err(): don't count arbitration lose as an error
  can: c_can: c_can_power_up(): fix error handling
  can: kvaser_pciefd: kvaser_pciefd_open(): fix error handling
  samples/ftrace: Mark my_tramp[12]? global
  scsi: storvsc: Fix error return in storvsc_probe()
  net: broadcom CNIC: requires MMU
  iwlwifi: pcie: invert values of NO_160 device config entries
  perf/x86/intel: Fix a warning on x86_pmu_stop() with large PEBS
  zlib: export S390 symbols for zlib modules
  phy: usb: Fix incorrect clearing of tca_drv_sel bit in SETUP reg for 7211
  arm64: dts: rockchip: Remove system-power-controller from pmic on Odroid Go 
Advance
  iwlwifi: pcie: limit memory read spin time
  arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.
  arm64: dts: rockchip: Reorder LED triggers from mmc devices on rk3399-roc-pc.
  iwlwifi: sta: set max HE max A-MPDU according to HE capa
  iwlwifi: pcie: set LTR to avoid completion timeout
  iwlwifi: mvm: fix kernel panic in case of assert during CSA
  powerpc: Drop -me200 addition to build flags
  arm64: dts: broadcom: clear the warnings caused by empty dma-ranges
  ARC: stack unwinding: don't assume non-current task is sleeping
  scsi: ufs: Fix unexpected values from ufshcd_read_desc_param()
  scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE
  interconnect: qcom: msm8916: Remove rpm-ids from non-RPM nodes
  interconnect: qcom: qcs404: Remove GPU and display RPM IDs
  ibmvnic: skip tx timeout reset while in resetting
  irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend
  drm/exynos: depend on COMMON_CLK to fix compile tests
  spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts
  arm-smmu-qcom: Ensure the qcom_scm driver has finished probing
  btrfs: do nofs allocations when adding and removing qgroup relations
  btrfs: fix lockdep splat when enabling and disablin

[Kernel-packages] [Bug 1912027] Re: Groovy update: upstream stable patchset 2021-01-15

[Kelsey Skunberg]

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

** Changed in: linux-riscv (Ubuntu Groovy)
   Status: New => Fix Committed

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

Title:
  Groovy update: upstream stable patchset 2021-01-15

Status in linux package in Ubuntu:
  Confirmed
Status in linux-riscv package in Ubuntu:
  New
Status in linux source package in Groovy:
  Fix Committed
Status in linux-riscv source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-15

  Ported from the following upstream stable releases:
   v5.10.3,
  v5.4.86, v5.10.4

     from git://git.kernel.org/

  net: ipconfig: Avoid spurious blank lines in boot log
  x86/split-lock: Avoid returning with interrupts enabled
  exfat: Avoid allocating upcase table using kcalloc()
  soc/tegra: fuse: Fix index bug in get_process_id
  usb: mtu3: fix memory corruption in mtu3_debugfs_regset()
  USB: serial: option: add interface-number sanity check to flag handling
  USB: gadget: f_acm: add support for SuperSpeed Plus
  USB: gadget: f_midi: setup SuperSpeed Plus descriptors
  usb: gadget: f_fs: Re-use SS descriptors for SuperSpeedPlus
  USB: gadget: f_rndis: fix bitrate for SuperSpeed and above
  usb: chipidea: ci_hdrc_imx: Pass DISABLE_DEVICE_STREAMING flag to imx6ul
  ARM: dts: exynos: fix roles of USB 3.0 ports on Odroid XU
  ARM: dts: exynos: fix USB 3.0 VBUS control and over-current pins on Exynos5410
  ARM: dts: exynos: fix USB 3.0 pins supply being turned off on Odroid XU
  coresight: tmc-etf: Fix NULL ptr dereference in tmc_enable_etf_sink_perf()
  coresight: tmc-etr: Check if page is valid before dma_map_page()
  coresight: tmc-etr: Fix barrier packet insertion for perf buffer
  coresight: etb10: Fix possible NULL ptr dereference in etb_enable_perf()
  f2fs: fix to seek incorrect data offset in inline data file
  scsi: megaraid_sas: Check user-provided offsets
  HID: i2c-hid: add Vero K147 to descriptor override
  serial_core: Check for port state when tty is in error state
  fscrypt: remove kernel-internal constants from UAPI header
  fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME
  fscrypt: add fscrypt_is_nokey_name()
  ubifs: prevent creating duplicate encrypted filenames
  ext4: prevent creating duplicate encrypted filenames
  f2fs: prevent creating duplicate encrypted filenames
  Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
  quota: Sanity-check quota file headers on load
  fs: quota: fix array-index-out-of-bounds bug by passing correct argument to 
vfs_cleanup_quota_inode()
  media: msi2500: assign SPI bus number dynamically
  crypto: af_alg - avoid undefined behavior accessing salg_name
  nl80211: validate key indexes for cfg80211_registered_device
  md: fix a warning caused by a race between concurrent md_ioctl()s
  UBUNTU: upstream stable to v5.10.3
  drm/gma500: fix double free of gma_connector
  drm/aspeed: Fix Kconfig warning & subsequent build errors
  drm/mcde: Fix handling of platform_get_irq() error
  drm/tve200: Fix handling of platform_get_irq() error
  arm64: dts: renesas: hihope-rzg2-ex: Drop rxc-skew-ps from ethernet-phy node
  arm64: dts: renesas: cat875: Remove rxc-skew-ps from ethernet-phy node
  soc: renesas: rmobile-sysc: Fix some leaks in rmobile_init_pm_domains()
  soc: mediatek: Check if power domains can be powered on at boot time
  arm64: dts: mediatek: mt8183: fix gce incorrect mbox-cells value
  arm64: dts: ipq6018: update the reserved-memory node
  soc: qcom: geni: More properly switch to DMA mode
  Revert "i2c: i2c-qcom-geni: Fix DMA transfer race"
  RDMA/bnxt_re: Set queue pair state when being queried
  rtc: pcf2127: fix pcf2127_nvmem_read/write() returns
  selinux: fix error initialization in inode_doinit_with_dentry()
  ARM: dts: aspeed-g6: Fix the GPIO memory size
  ARM: dts: aspeed: s2600wf: Fix VGA memory region location
  RDMA/core: Fix error return in _ib_modify_qp()
  RDMA/rxe: Compute PSN windows correctly
  x86/mm/ident_map: Check for errors from ident_pud_init()
  ARM: p2v: fix handling of LPAE translation in BE mode
  RDMA/rtrs-clt: Remove destroy_con_cq_qp in case route resolving failed
  RDMA/rtrs-clt: Missing error from rtrs_rdma_conn_established
  RDMA/rtrs-srv: Don't guard the whole __alloc_srv with srv_mutex
  

[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Seth Arnold]

Re test rebuilds, that's certainly the intention, but there are
occasional problems:

https://launchpad.net/bugs/1910555
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1910709
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910503 (virtualbox, 
probably not in scope)

These three were discussed a bit on https://discourse.ubuntu.com/t
/improvements-for-hardware-support-in-ubuntu-desktop-installation-
media/20606

Thanks

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Maton Danko]

Tested on kernel 5.11.0-rc6.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bi

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Maton Danko]

I've checked and it's true that working, but not fully. The secondary mouse 
click doesn't work if I press the right bottom corner of the touchpad 
(registers primary mouse click).
Rotation, pitching, swipe with 3/4 fingers doesn't seem to work either.

** Attachment added: "evtest"
   
https://bugs.launchpad.net/fedora/+source/linux/+bug/1887190/+attachment/5459188/+files/evtest

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckRe

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Maton Danko]

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

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no u

[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload

[Matthew Ruffell]

Hi Manish,

Thanks for testing the Groovy 5.8 kernel in -proposed!

The Focal 5.4 / Bionic 5.4 HWE kernel will be in -proposed next week
sometime, if you are looking to verify that as well.

I will also ask our customer in common to verify the Bionic HWE kernel
when it becomes available.

Thanks for making the patch!
Matthew

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

Title:
  qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not
  supporting IPIP tx csum offload

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1909062

  [Impact]

  For users with QLogic QL41xxx series NICs, such as the FastLinQ
  QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the
  4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will
  fail, due to these packets getting corrupted.

  Kubernetes uses IPIP tunnelled packets for internal DNS resolution,
  and this particular packet type is not supported for hardware tx
  checksum offload, and the packets end up corrupted when the qede
  driver attempts to checksum them.

  This only affects internal Kubernetes DNS, as regular DNS lookups to
  regular external domains will succeed, due to them not using IPIP
  packet types.

  [Fix]

  Marvell has developed a fix for the qede driver, which checks the
  packet type, and if it is IPPROTO_IPIP, then csum offloads are
  disabled for socket buffers of type IPIP.

  commit 5d5647dad259bb416fd5d3d87012760386d97530
  Author: Manish Chopra 
  Date: Mon Dec 21 06:55:30 2020 -0800
  Subject: qede: fix offload for IPIP tunnel packets
  Link: 
https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530

  This commit landed in mainline in 5.11-rc3. The commit was accepted
  into upstream stable 4.14.215, 4.19.167, 5.4.89 and 5.10.7.

  Note, this SRU isn't targeted for Bionic due to tx csum offload
  support only landing in 5.0 and onward, meaning the 4.15 kernel still
  works even without this patch. Because of this, Bionic can pick the
  patch up naturally from upstream stable.

  [Testcase]

  The system must have a QLogic QL41xxx series NIC fitted, and needs to
  be a part of a Kubernetes cluster.

  Firstly, get a list of all devices in the system:

  $ sudo ifconfig

  Next, set all devices down with:

  $ sudo ifconfig  down

  Next, bring up the QLogic QL41xxx device:

  $ sudo ifconfig  up

  Then, attempt to lookup an internal Kubernetes domain:

  $ nslookup 

  Without the patch, the connection will time out:

  ;; connection timed out; no servers could be reached

  If we look at packet traces with tcpdump, we see it leaves the source,
  but never arrives at the destination.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf297772-test

  If you install it, then Kubernetes internal DNS lookups will succeed.

  [Where problems could occur]

  If a regression were to occur, then users of the qede driver would be
  affected. This is limited to those with QLogic QL41xxx series NICs.
  The patch explicitly checks for IPIP type packets, so only those
  particular packets would be affected.

  Since IPIP type packets are uncommon, it would not cause a total
  outage on regression, since most packets are not IPIP tunnelled. It
  could potentially cause problems for users who frequently handle VPN
  or Kubernetes internal DNS traffic.

  A workaround would be to use ethtool to disable tx csum offload for
  all packet types, or to revert to an older kernel.

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

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

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

[fabianbur]

Aksahat:

Could something go wrong while doing this?

No, it couldn't be worse than what you already have. The OEM kernel is
tested and resolves this particular bug and others.

How long before patched kernel is released for ubuntu-20.04?

That question is for the Ubuntu development team. I dare to calculate
that between two and four weeks. Maybe less, but no more than that.

How can I be sure of my error is this same error and will be relsolved
by patch?

If you use sudo apt install linux-oem-20.04 you reboot and in grub you
select the OEM kernel and it fixes the error, that's it.

If you don't want to do that, check the detail of the error in this
thread and compare it with yours.

The command output you share says nothing more than the kernel version
you have.

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 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:
  Fix Released
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
  vectors") currently in vanilla kernel tree for v5.11.

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Where problems could occur]

  An unpatched kernel will not be able to probe SATA controllers moved
  behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
  attached on it completely unusable. With this change, kernel would
  then be able to probe them but may also suffer from issues that only
  occur under such configuration. However, the worst case is to move away
  sata disks from VMD bus as they are currently without this fix, so the
  risk here should be justified.

  == Previous SRU ==

  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation 

[Kernel-packages] [Bug 1909062] Re: qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP tx csum offload

[Manish Chopra]

Hi Matthew,

We have verified the fix with proposed kernel.
I hope that I have corrected the "tags" appropriately.

Thanks,
Manish

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

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

Title:
  qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not
  supporting IPIP tx csum offload

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1909062

  [Impact]

  For users with QLogic QL41xxx series NICs, such as the FastLinQ
  QL41000 Series 10/25/40/50GbE Controller, when they upgrade from the
  4.15 kernel to the 5.4 kernel, Kubernetes Internal DNS requests will
  fail, due to these packets getting corrupted.

  Kubernetes uses IPIP tunnelled packets for internal DNS resolution,
  and this particular packet type is not supported for hardware tx
  checksum offload, and the packets end up corrupted when the qede
  driver attempts to checksum them.

  This only affects internal Kubernetes DNS, as regular DNS lookups to
  regular external domains will succeed, due to them not using IPIP
  packet types.

  [Fix]

  Marvell has developed a fix for the qede driver, which checks the
  packet type, and if it is IPPROTO_IPIP, then csum offloads are
  disabled for socket buffers of type IPIP.

  commit 5d5647dad259bb416fd5d3d87012760386d97530
  Author: Manish Chopra 
  Date: Mon Dec 21 06:55:30 2020 -0800
  Subject: qede: fix offload for IPIP tunnel packets
  Link: 
https://github.com/torvalds/linux/commit/5d5647dad259bb416fd5d3d87012760386d97530

  This commit landed in mainline in 5.11-rc3. The commit was accepted
  into upstream stable 4.14.215, 4.19.167, 5.4.89 and 5.10.7.

  Note, this SRU isn't targeted for Bionic due to tx csum offload
  support only landing in 5.0 and onward, meaning the 4.15 kernel still
  works even without this patch. Because of this, Bionic can pick the
  patch up naturally from upstream stable.

  [Testcase]

  The system must have a QLogic QL41xxx series NIC fitted, and needs to
  be a part of a Kubernetes cluster.

  Firstly, get a list of all devices in the system:

  $ sudo ifconfig

  Next, set all devices down with:

  $ sudo ifconfig  down

  Next, bring up the QLogic QL41xxx device:

  $ sudo ifconfig  up

  Then, attempt to lookup an internal Kubernetes domain:

  $ nslookup 

  Without the patch, the connection will time out:

  ;; connection timed out; no servers could be reached

  If we look at packet traces with tcpdump, we see it leaves the source,
  but never arrives at the destination.

  There is a test kernel available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf297772-test

  If you install it, then Kubernetes internal DNS lookups will succeed.

  [Where problems could occur]

  If a regression were to occur, then users of the qede driver would be
  affected. This is limited to those with QLogic QL41xxx series NICs.
  The patch explicitly checks for IPIP type packets, so only those
  particular packets would be affected.

  Since IPIP type packets are uncommon, it would not cause a total
  outage on regression, since most packets are not IPIP tunnelled. It
  could potentially cause problems for users who frequently handle VPN
  or Kubernetes internal DNS traffic.

  A workaround would be to use ethtool to disable tx csum offload for
  all packet types, or to revert to an older kernel.

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

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

[Kernel-packages] [Bug 1912935] Re: battery drain while notebook off / shutdown

[asgard2]

@kaihengfeng
Your kernel is installed. At a first 10 hour test, it stopped on the same 
percentage. With the  previous kernel impossible.

I will check again tomorrow!

But I have no wifi or other network connection, the module is not
building (same on the mainline kernel).

Would be an integration to the current ubuntu release possible?

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

Title:
  battery drain while notebook off / shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu.
  It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 .

  Tested:

  - with ubuntu 20.04
  - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4)
  - no usb devices are plugged in
  - no wake ob lan available
  - no USB power when off (checked with optical mouse)
  - no visible LEDs are on when shutdown

  I reinstalled window 10, when shutdown from windows there is no
  (visible) battery drain (or significantly lower).

  Linux is unusable on this device, if the battery drains in a short
  time to 0% percent. This cause battery damage ...

  ---

  Tested TLP with default settings and activated
  DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power
  consumption after shutdown.

  Same power consumption on 20.10 (Groovy Gorilla).

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  test953 F pulseaudio
   /dev/snd/controlC0:  test953 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-01-24 (0 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: HP HP Laptop 15s-eq0xxx
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-64-generic N/A
   linux-backports-modules-5.4.0-64-generic  N/A
   linux-firmware1.187.8
  Tags:  focal
  Uname: Linux 5.4.0-64-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/18/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FD
  dmi.board.vendor: HP
  dmi.board.version: 99.40
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15s-eq0xxx
  dmi.product.sku: 20T63EA#ABD
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1911235] Re: Groovy update: upstream stable patchset 2021-01-12

[Kelsey Skunberg]

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

** Changed in: linux-gcp (Ubuntu Groovy)
   Status: New => Fix Committed

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

Title:
  Groovy update: upstream stable patchset 2021-01-12

Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux source package in Groovy:
  Fix Committed
Status in linux-gcp source package in Groovy:
  Fix Committed
Status in linux-raspi source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-12

  Ported from the following upstream stable releases:
  v5.4.79, v5.9.10
  v5.4.80, v5.9.11
  v5.4.81, v5.9.12
  v5.4.82, v5.9.13
  v5.4.83, v5.9.14

     from git://git.kernel.org/

  powerpc: Only include kup-radix.h for 64-bit Book3S
  leds: lm3697: Fix out-of-bound access
  Input: sunkbd - avoid use-after-free in teardown paths
  mac80211: always wind down STA state
  can: proc: can_remove_proc(): silence remove_proc_entry warning
  powerpc/smp: Call rcu_cpu_starting() earlier
  KVM: x86: clflushopt should be treated as a no-op by emulation
  ACPI: GED: fix -Wformat
  net: lantiq: Add locking for TX DMA channel
  UBUNTU: upstream stable to v5.4.79, v5.9.10
  ah6: fix error return code in ah6_input()
  atm: nicstar: Unmap DMA on send error
  bnxt_en: read EEPROM A2h address using page 0
  devlink: Add missing genlmsg_cancel() in devlink_nl_sb_port_pool_fill()
  enetc: Workaround for MDIO register access issue
  Exempt multicast addresses from five-second neighbor lifetime
  inet_diag: Fix error path to cancel the meseage in inet_req_diag_fill()
  ipv6: Fix error path to cancel the meseage
  lan743x: fix issue causing intermittent kernel log warnings
  lan743x: prevent entire kernel HANG on open, for some platforms
  mlxsw: core: Use variable timeout for EMAD retries
  net: b44: fix error return code in b44_init_one()
  net: bridge: add missing counters to ndo_get_stats64 callback
  netdevsim: set .owner to THIS_MODULE
  net: dsa: mv88e6xxx: Avoid VTU corruption on 6097
  net: ethernet: mtk-star-emac: fix error return code in mtk_star_enable()
  net: ethernet: mtk-star-emac: return ok when xmit drops
  net: ethernet: ti: am65-cpts: update ret when ptp_clock is ERROR
  net: ethernet: ti: cpsw: fix cpts irq after suspend
  net: ethernet: ti: cpsw: fix error return code in cpsw_probe()
  net: ftgmac100: Fix crash when removing driver
  net: Have netpoll bring-up DSA management interface
  net: ipa: lock when freeing transaction
  netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
  netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
  net: lantiq: Wait for the GPHY firmware to be ready
  net/mlx4_core: Fix init_hca fields offset
  net/mlx5e: Fix refcount leak on kTLS RX resync
  net/ncsi: Fix netlink registration
  net: phy: mscc: remove non-MACSec compatible phy
  net: qualcomm: rmnet: Fix incorrect receive packet handling during cleanup
  net/smc: fix direct access to ib_gid_addr->ndev in smc_ib_determine_gid()
  net: stmmac: Use rtnl_lock/unlock on netif_set_real_num_rx_queues() call
  net/tls: fix corrupted data in recvmsg
  net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
  page_frag: Recover from memory pressure
  qed: fix error return code in qed_iwarp_ll2_start()
  qed: fix ILT configuration of SRC block
  qlcnic: fix error return code in qlcnic_83xx_restart_hw()
  sctp: change to hold/put transport for proto_unreach_timer
  tcp: only postpone PROBE_RTT if RTT is < current min_rtt estimate
  vsock: forward all packets to the host when no H2G is registered
  net/mlx5e: Fix check if netdev is bond slave
  net/mlx5: Add handling of port type in rule deletion
  net/mlx5: Clear bw_share upon VF disable
  net/mlx5: Disable QoS when min_rates on all VFs are zero
  PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter
  net: fec: Fix reference count leak in fec series ops
  net/tls: Fix wrong record sn in async mode of device resync
  net: usb: qmi_wwan: Set DTR quirk for MR400
  Revert "Revert "gpio: omap: Fix lost edge wake-up interrupts""
  tools, bpftool: Avoid array index warning

[Kernel-packages] [Bug 1911331] Re: Bionic update: upstream stable patchset 2021-01-12

[Kelsey Skunberg]

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

** Changed in: linux-raspi2 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Bionic update: upstream stable patchset 2021-01-12

Status in linux package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-raspi2 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 2021-01-12

  Ported from the following upstream stable releases:
  v4.14.213, v4.19.164

     from git://git.kernel.org/

  spi: bcm2835aux: Fix use-after-free on unbind
  spi: bcm2835aux: Restore err assignment in bcm2835aux_spi_probe
  iwlwifi: pcie: limit memory read spin time
  arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.
  iwlwifi: mvm: fix kernel panic in case of assert during CSA
  ARC: stack unwinding: don't assume non-current task is sleeping
  scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE
  soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)
  platform/x86: acer-wmi: add automatic keyboard background light toggle key as 
KEY_LIGHTS_TOGGLE
  Input: cm109 - do not stomp on control URB
  Input: i8042 - add Acer laptops to the i8042 reset list
  pinctrl: amd: remove debounce filter setting in IRQ type setting
  kbuild: avoid static_assert for genksyms
  scsi: be2iscsi: Revert "Fix a theoretical leak in beiscsi_create_eqs()"
  x86/mm/mem_encrypt: Fix definition of PMD_FLAGS_DEC_WP
  PCI: qcom: Add missing reset for ipq806x
  net: stmmac: free tx skb buffer in stmmac_resume()
  tcp: fix cwnd-limited bug for TSO deferral where we send nothing
  net/mlx4_en: Avoid scheduling restart task if it is already running
  net/mlx4_en: Handle TX error CQE
  net: stmmac: delete the eee_ctrl_timer after napi disabled
  net: stmmac: dwmac-meson8b: fix mask definition of the m250_sel mux
  net: bridge: vlan: fix error return code in __vlan_add()
  mac80211: mesh: fix mesh_pathtbl_init() error path
  USB: dummy-hcd: Fix uninitialized array use in init()
  USB: add RESET_RESUME quirk for Snapscan 1212
  ALSA: usb-audio: Fix potential out-of-bounds shift
  ALSA: usb-audio: Fix control 'access overflow' errors from chmap
  xhci: Give USB2 ports time to enter U3 in bus suspend
  USB: UAS: introduce a quirk to set no_write_same
  USB: sisusbvga: Make console support depend on BROKEN
  UBUNTU: [Config] updateconfigs for USB_SISUSBVGA_CON
  ALSA: pcm: oss: Fix potential out-of-bounds shift
  serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
  drm: fix drm_dp_mst_port refcount leaks in drm_dp_mst_allocate_vcpi
  pinctrl: merrifield: Set default bias in case no particular value given
  pinctrl: baytrail: Avoid clearing debounce value when turning it off
  ARM: dts: sun8i: v3s: fix GIC node memory range
  gpio: mvebu: fix potential user-after-free on probe
  scsi: bnx2i: Requires MMU
  can: softing: softing_netdev_open(): fix error handling
  RDMA/cm: Fix an attempt to use non-valid pointer when cleaning timewait
  kernel/cpu: add arch override for clear_tasks_mm_cpumask() mm handling
  drm/tegra: sor: Disable clocks on error in tegra_sor_init()
  vxlan: Add needed_headroom for lower device
  vxlan: Copy needed_tailroom from lowerdev
  scsi: mpt3sas: Increase IOCInit request timeout to 30s
  dm table: Remove BUG_ON(in_interrupt())
  soc/tegra: fuse: Fix index bug in get_process_id
  USB: serial: option: add interface-number sanity check to flag handling
  USB: gadget: f_acm: add support for SuperSpeed Plus
  USB: gadget: f_midi: setup SuperSpeed Plus descriptors
  usb: gadget: f_fs: Re-use SS descriptors for SuperSpeedPlus
  USB: gadget: f_rndis: fix bitrate for SuperSpeed and above
  usb: chipidea: ci_hdrc_imx: Pass DISABLE_DEVICE_STREAMING flag to imx6ul
  ARM: dts: exynos: fix roles of USB 3.0 ports on Odroid XU
  ARM: dts: exynos: fix USB 3.0 VBUS control and over-current pins on Exynos5410
  ARM: dts: exynos: fix USB 3.0 pins supply being turned off on Odroid XU
  HID: i2c-hid: add Vero K147 to descriptor override
  serial_core: Check for port state when tty is in error state
  quota: Sanity-check quota file headers on load
  media: msi2500: assign SPI bus number dynamically
  crypto: af_alg - av

[Kernel-packages] [Bug 1911476] Re: Groovy update: upstream stable patchset 2021-01-13

[Kelsey Skunberg]

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

** Changed in: linux-gcp (Ubuntu Groovy)
   Status: New => 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/1911476

Title:
  Groovy update: upstream stable patchset 2021-01-13

Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  New
Status in linux-kvm package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux source package in Groovy:
  Fix Committed
Status in linux-gcp source package in Groovy:
  Fix Committed
Status in linux-kvm source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-13

  Ported from the following upstream stable releases:
  v5.4.84, v5.9.15,
  v5.4.85, v5.9.16

     from git://git.kernel.org/

  Kbuild: do not emit debug info for assembly with LLVM_IAS=1
  mm/zsmalloc.c: drop ZSMALLOC_PGTABLE_MAPPING
  UBUNTU: [Config] updateconfigs for ZSMALLOC_PGTABLE_MAPPING
  kprobes: Remove NMI context check
  kprobes: Tell lockdep about kprobe nesting
  ASoC: Intel: bytcr_rt5640: Fix HP Pavilion x2 Detachable quirks
  tools/bootconfig: Fix to check the write failure correctly
  net, xsk: Avoid taking multiple skbuff references
  bpftool: Fix error return value in build_btf_type_table
  vhost-vdpa: fix page pinning leakage in error path (rework)
  powerpc/64s: Fix hash ISA v3.0 TLBIEL instruction generation
  batman-adv: Consider fragmentation for needed_headroom
  batman-adv: Reserve needed_*room for fragments
  batman-adv: Don't always reallocate the fragmentation skb head
  ipvs: fix possible memory leak in ip_vs_control_net_init
  ibmvnic: handle inconsistent login with reset
  ibmvnic: stop free_all_rwi on failed reset
  ibmvnic: avoid memset null scrq msgs
  ibmvnic: delay next reset if hard reset fails
  ibmvnic: track pending login
  ibmvnic: send_login should check for crq errors
  ibmvnic: reduce wait for completion time
  drm/rockchip: Avoid uninitialized use of endpoint id in LVDS
  drm/panel: sony-acx565akm: Fix race condition in probe
  can: m_can: tcan4x5x_can_probe(): fix error path: remove erroneous 
clk_disable_unprepare()
  can: sja1000: sja1000_err(): don't count arbitration lose as an error
  can: sun4i_can: sun4i_can_err(): don't count arbitration lose as an error
  can: c_can: c_can_power_up(): fix error handling
  can: kvaser_pciefd: kvaser_pciefd_open(): fix error handling
  samples/ftrace: Mark my_tramp[12]? global
  scsi: storvsc: Fix error return in storvsc_probe()
  net: broadcom CNIC: requires MMU
  iwlwifi: pcie: invert values of NO_160 device config entries
  perf/x86/intel: Fix a warning on x86_pmu_stop() with large PEBS
  zlib: export S390 symbols for zlib modules
  phy: usb: Fix incorrect clearing of tca_drv_sel bit in SETUP reg for 7211
  arm64: dts: rockchip: Remove system-power-controller from pmic on Odroid Go 
Advance
  iwlwifi: pcie: limit memory read spin time
  arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.
  arm64: dts: rockchip: Reorder LED triggers from mmc devices on rk3399-roc-pc.
  iwlwifi: sta: set max HE max A-MPDU according to HE capa
  iwlwifi: pcie: set LTR to avoid completion timeout
  iwlwifi: mvm: fix kernel panic in case of assert during CSA
  powerpc: Drop -me200 addition to build flags
  arm64: dts: broadcom: clear the warnings caused by empty dma-ranges
  ARC: stack unwinding: don't assume non-current task is sleeping
  scsi: ufs: Fix unexpected values from ufshcd_read_desc_param()
  scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE
  interconnect: qcom: msm8916: Remove rpm-ids from non-RPM nodes
  interconnect: qcom: qcs404: Remove GPU and display RPM IDs
  ibmvnic: skip tx timeout reset while in resetting
  irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend
  drm/exynos: depend on COMMON_CLK to fix compile tests
  spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts
  arm-smmu-qcom: Ensure the qcom_scm driver has finished probing
  btrfs: do nofs allocations when adding and removing qgroup relations
  btrfs: fix lockdep splat when enabling and disabling qgroups
  soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)
  intel_idle: Fix intel_idle() vs tracing
  arm

[Kernel-packages] [Bug 1904054] Re: kernel 5.8 general protection fault at boot

[Ben Poliakoff]

As of 5.8.0-40-generic (and possibly the previous version as well) this
issue seems to be 100% resolved for me.

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

Title:
  kernel 5.8 general protection fault at boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu kernel version 5.8.0-28 (as well as the previous 5.8.0-26)
  crashes at boot with many general protection faults, on my Intel NUC
  10. Ubuntu kernel version 5.4.0-52 did not exhibit this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-28-generic 5.8.0-28.30
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benp   2912 F pulseaudio
   /dev/snd/controlC1:  benp   2912 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 11:51:07 2020
  InstallationDate: Installed on 2020-10-08 (35 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Intel(R) Client Systems NUC10i7FNH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.190.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (15 days ago)
  dmi.bios.date: 08/17/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0045.2020.0817.1709
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i7FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K61360-302
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0045.2020.0817.1709:bd08/17/2020:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: FN
  dmi.product.name: NUC10i7FNH
  dmi.product.sku: BXNUC10i7FNH
  dmi.product.version: K61081-302
  dmi.sys.vendor: Intel(R) Client Systems

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

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

[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Jeff Nappi]

>Jean- (jean-helou) wrote 6 hours ago:  #87
>the next step to get a full fix and improved sound quality for voip calls over 
>BT headset is >coming in 
>https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254

This is good news! Proper support for mSBC is critical for me to
consider this bug resolved. It was the original intention of opening the
bug in the first place :)

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1911235] Re: Groovy update: upstream stable patchset 2021-01-12

[Kelsey Skunberg]

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

** Changed in: linux-raspi (Ubuntu Groovy)
   Status: New => Fix Committed

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

Title:
  Groovy update: upstream stable patchset 2021-01-12

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-12

  Ported from the following upstream stable releases:
  v5.4.79, v5.9.10
  v5.4.80, v5.9.11
  v5.4.81, v5.9.12
  v5.4.82, v5.9.13
  v5.4.83, v5.9.14

     from git://git.kernel.org/

  powerpc: Only include kup-radix.h for 64-bit Book3S
  leds: lm3697: Fix out-of-bound access
  Input: sunkbd - avoid use-after-free in teardown paths
  mac80211: always wind down STA state
  can: proc: can_remove_proc(): silence remove_proc_entry warning
  powerpc/smp: Call rcu_cpu_starting() earlier
  KVM: x86: clflushopt should be treated as a no-op by emulation
  ACPI: GED: fix -Wformat
  net: lantiq: Add locking for TX DMA channel
  UBUNTU: upstream stable to v5.4.79, v5.9.10
  ah6: fix error return code in ah6_input()
  atm: nicstar: Unmap DMA on send error
  bnxt_en: read EEPROM A2h address using page 0
  devlink: Add missing genlmsg_cancel() in devlink_nl_sb_port_pool_fill()
  enetc: Workaround for MDIO register access issue
  Exempt multicast addresses from five-second neighbor lifetime
  inet_diag: Fix error path to cancel the meseage in inet_req_diag_fill()
  ipv6: Fix error path to cancel the meseage
  lan743x: fix issue causing intermittent kernel log warnings
  lan743x: prevent entire kernel HANG on open, for some platforms
  mlxsw: core: Use variable timeout for EMAD retries
  net: b44: fix error return code in b44_init_one()
  net: bridge: add missing counters to ndo_get_stats64 callback
  netdevsim: set .owner to THIS_MODULE
  net: dsa: mv88e6xxx: Avoid VTU corruption on 6097
  net: ethernet: mtk-star-emac: fix error return code in mtk_star_enable()
  net: ethernet: mtk-star-emac: return ok when xmit drops
  net: ethernet: ti: am65-cpts: update ret when ptp_clock is ERROR
  net: ethernet: ti: cpsw: fix cpts irq after suspend
  net: ethernet: ti: cpsw: fix error return code in cpsw_probe()
  net: ftgmac100: Fix crash when removing driver
  net: Have netpoll bring-up DSA management interface
  net: ipa: lock when freeing transaction
  netlabel: fix our progress tracking in netlbl_unlabel_staticlist()
  netlabel: fix an uninitialized warning in netlbl_unlabel_staticlist()
  net: lantiq: Wait for the GPHY firmware to be ready
  net/mlx4_core: Fix init_hca fields offset
  net/mlx5e: Fix refcount leak on kTLS RX resync
  net/ncsi: Fix netlink registration
  net: phy: mscc: remove non-MACSec compatible phy
  net: qualcomm: rmnet: Fix incorrect receive packet handling during cleanup
  net/smc: fix direct access to ib_gid_addr->ndev in smc_ib_determine_gid()
  net: stmmac: Use rtnl_lock/unlock on netif_set_real_num_rx_queues() call
  net/tls: fix corrupted data in recvmsg
  net: x25: Increase refcnt of "struct x25_neigh" in x25_rx_call_request
  page_frag: Recover from memory pressure
  qed: fix error return code in qed_iwarp_ll2_start()
  qed: fix ILT configuration of SRC block
  qlcnic: fix error return code in qlcnic_83xx_restart_hw()
  sctp: change to hold/put transport for proto_unreach_timer
  tcp: only postpone PROBE_RTT if RTT is < current min_rtt estimate
  vsock: forward all packets to the host when no H2G is registered
  net/mlx5e: Fix check if netdev is bond slave
  net/mlx5: Add handling of port type in rule deletion
  net/mlx5: Clear bw_share upon VF disable
  net/mlx5: Disable QoS when min_rates on all VFs are zero
  PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter
  net: fec: Fix reference count leak in fec series ops
  net/tls: Fix wrong record sn in async mode of device resync
  net: usb: qmi_wwan: Set DTR quirk for MR400
  Revert "Revert "gpio: omap: Fix lost edge wake-up interrupts""
  tools, bpftool: Avoid array index warnings.
  habanalabs/gaudi: mask WDT error in QMAN
  pinctrl: rockchip: enable gpio pclk for rockchip_gpio

[Kernel-packages] [Bug 1910139] Re: Xenial update: v4.4.249 upstream stable release

[Kelsey Skunberg]

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Xenial update: v4.4.249 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux-raspi2 source package in Xenial:
  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:

     v4.4.249 upstream stable release
     from git://git.kernel.org/

  spi: bcm2835aux: Fix use-after-free on unbind
  spi: bcm2835aux: Restore err assignment in bcm2835aux_spi_probe
  ARC: stack unwinding: don't assume non-current task is sleeping
  platform/x86: acer-wmi: add automatic keyboard background light toggle key as 
KEY_LIGHTS_TOGGLE
  Input: cm109 - do not stomp on control URB
  Input: i8042 - add Acer laptops to the i8042 reset list
  pinctrl: amd: remove debounce filter setting in IRQ type setting
  UBUNTU: [Config] updateconfigs for SPI_DYNAMIC
  spi: Prevent adding devices below an unregistering controller
  net/mlx4_en: Avoid scheduling restart task if it is already running
  tcp: fix cwnd-limited bug for TSO deferral where we send nothing
  net: stmmac: delete the eee_ctrl_timer after napi disabled
  net: bridge: vlan: fix error return code in __vlan_add()
  USB: dummy-hcd: Fix uninitialized array use in init()
  USB: add RESET_RESUME quirk for Snapscan 1212
  ALSA: usb-audio: Fix potential out-of-bounds shift
  ALSA: usb-audio: Fix control 'access overflow' errors from chmap
  xhci: Give USB2 ports time to enter U3 in bus suspend
  USB: sisusbvga: Make console support depend on BROKEN
  UBUNTU: [Config] updateconfigs for USB_SISUSBVGA_CON
  ALSA: pcm: oss: Fix potential out-of-bounds shift
  serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
  USB: serial: cp210x: enable usb generic throttle/unthrottle
  scsi: bnx2i: Requires MMU
  can: softing: softing_netdev_open(): fix error handling
  RDMA/cm: Fix an attempt to use non-valid pointer when cleaning timewait
  dm table: Remove BUG_ON(in_interrupt())
  soc/tegra: fuse: Fix index bug in get_process_id
  USB: serial: option: add interface-number sanity check to flag handling
  USB: gadget: f_rndis: fix bitrate for SuperSpeed and above
  usb: chipidea: ci_hdrc_imx: Pass DISABLE_DEVICE_STREAMING flag to imx6ul
  media: msi2500: assign SPI bus number dynamically
  Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
  drm/gma500: fix double free of gma_connector
  ARM: p2v: fix handling of LPAE translation in BE mode
  crypto: talitos - Fix return type of current_desc_hdr()
  spi: img-spfi: fix reference leak in img_spfi_resume
  ASoC: pcm: DRAIN support reactivation
  Bluetooth: Fix null pointer dereference in hci_event_packet()
  spi: spi-ti-qspi: fix reference leak in ti_qspi_setup
  spi: tegra20-slink: fix reference leak in slink ops of tegra20
  spi: tegra20-sflash: fix reference leak in tegra_sflash_resume
  spi: tegra114: fix reference leak in tegra spi ops
  RDMa/mthca: Work around -Wenum-conversion warning
  MIPS: BCM47XX: fix kconfig dependency bug for BCM47XX_BCMA
  media: solo6x10: fix missing snd_card_free in error handling case
  drm/omap: dmm_tiler: fix return error code in omap_dmm_probe()
  Input: ads7846 - fix integer overflow on Rt calculation
  Input: ads7846 - fix unaligned access on 7845
  powerpc/feature: Fix CPU_FTRS_ALWAYS by removing CPU_FTRS_GENERIC_32
  soc: ti: knav_qmss: fix reference leak in knav_queue_probe
  soc: ti: Fix reference imbalance in knav_dma_probe
  drivers: soc: ti: knav_qmss_queue: Fix error return code in knav_queue_probe
  memstick: fix a double-free bug in memstick_check
  ARM: dts: at91: sama5d4_xplained: add pincontrol for USB Host
  ARM: dts: at91: sama5d3_xplained: add pincontrol for USB Host
  orinoco: Move context allocation after processing the skb
  cw1200: fix missing destroy_workqueue() on error in cw1200_init_common
  mips: cdmm: fix use-after-free in mips_cdmm_bus_discover
  NFSv4.2: condition READDIR's mask for security label based on LSM state
  lockd: don't use interval-based rebinding over TCP
  NFS: switch nfsiod to be an UNBOUND workqueue.
  media: saa7146: fix array overflow in vidioc_s_audio()
  pinctrl: falcon: add missing put_device() call in pinctrl_falcon_

[Kernel-packages] [Bug 1911476] Re: Groovy update: upstream stable patchset 2021-01-13

[Kelsey Skunberg]

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

** Changed in: linux-raspi (Ubuntu Groovy)
   Status: New => 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/1911476

Title:
  Groovy update: upstream stable patchset 2021-01-13

Status in linux package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux-raspi package in Ubuntu:
  New
Status in linux source package in Groovy:
  Fix Committed
Status in linux-kvm source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  Fix Committed

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-13

  Ported from the following upstream stable releases:
  v5.4.84, v5.9.15,
  v5.4.85, v5.9.16

     from git://git.kernel.org/

  Kbuild: do not emit debug info for assembly with LLVM_IAS=1
  mm/zsmalloc.c: drop ZSMALLOC_PGTABLE_MAPPING
  UBUNTU: [Config] updateconfigs for ZSMALLOC_PGTABLE_MAPPING
  kprobes: Remove NMI context check
  kprobes: Tell lockdep about kprobe nesting
  ASoC: Intel: bytcr_rt5640: Fix HP Pavilion x2 Detachable quirks
  tools/bootconfig: Fix to check the write failure correctly
  net, xsk: Avoid taking multiple skbuff references
  bpftool: Fix error return value in build_btf_type_table
  vhost-vdpa: fix page pinning leakage in error path (rework)
  powerpc/64s: Fix hash ISA v3.0 TLBIEL instruction generation
  batman-adv: Consider fragmentation for needed_headroom
  batman-adv: Reserve needed_*room for fragments
  batman-adv: Don't always reallocate the fragmentation skb head
  ipvs: fix possible memory leak in ip_vs_control_net_init
  ibmvnic: handle inconsistent login with reset
  ibmvnic: stop free_all_rwi on failed reset
  ibmvnic: avoid memset null scrq msgs
  ibmvnic: delay next reset if hard reset fails
  ibmvnic: track pending login
  ibmvnic: send_login should check for crq errors
  ibmvnic: reduce wait for completion time
  drm/rockchip: Avoid uninitialized use of endpoint id in LVDS
  drm/panel: sony-acx565akm: Fix race condition in probe
  can: m_can: tcan4x5x_can_probe(): fix error path: remove erroneous 
clk_disable_unprepare()
  can: sja1000: sja1000_err(): don't count arbitration lose as an error
  can: sun4i_can: sun4i_can_err(): don't count arbitration lose as an error
  can: c_can: c_can_power_up(): fix error handling
  can: kvaser_pciefd: kvaser_pciefd_open(): fix error handling
  samples/ftrace: Mark my_tramp[12]? global
  scsi: storvsc: Fix error return in storvsc_probe()
  net: broadcom CNIC: requires MMU
  iwlwifi: pcie: invert values of NO_160 device config entries
  perf/x86/intel: Fix a warning on x86_pmu_stop() with large PEBS
  zlib: export S390 symbols for zlib modules
  phy: usb: Fix incorrect clearing of tca_drv_sel bit in SETUP reg for 7211
  arm64: dts: rockchip: Remove system-power-controller from pmic on Odroid Go 
Advance
  iwlwifi: pcie: limit memory read spin time
  arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.
  arm64: dts: rockchip: Reorder LED triggers from mmc devices on rk3399-roc-pc.
  iwlwifi: sta: set max HE max A-MPDU according to HE capa
  iwlwifi: pcie: set LTR to avoid completion timeout
  iwlwifi: mvm: fix kernel panic in case of assert during CSA
  powerpc: Drop -me200 addition to build flags
  arm64: dts: broadcom: clear the warnings caused by empty dma-ranges
  ARC: stack unwinding: don't assume non-current task is sleeping
  scsi: ufs: Fix unexpected values from ufshcd_read_desc_param()
  scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE
  interconnect: qcom: msm8916: Remove rpm-ids from non-RPM nodes
  interconnect: qcom: qcs404: Remove GPU and display RPM IDs
  ibmvnic: skip tx timeout reset while in resetting
  irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend
  drm/exynos: depend on COMMON_CLK to fix compile tests
  spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts
  arm-smmu-qcom: Ensure the qcom_scm driver has finished probing
  btrfs: do nofs allocations when adding and removing qgroup relations
  btrfs: fix lockdep splat when enabling and disabling qgroups
  soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)
  intel_idle: Fix intel_idle() vs tracing
  arm64: tegra: Disable the ACONNECT for Jetson TX2
  platform/x86: thinkpad_acpi: add P1 gen3 second fan su

[Kernel-packages] [Bug 1909840] Re: SDXC card reader not working properly

[Bruno Luis dos Santos Costa]

Installed the mainline kernel 5.11-rc5 and the "cannot verify signal
voltage" persists. Also now i have the new message "Deprecated parameter
'namecase'".

by dmesg i got

[  102.774340] mmc1: card e624 removed
[  151.977592] mmc1: cannot verify signal voltage switch
[  152.103194] mmc1: new ultra high speed SDR104 SDXC card at address 
[  152.111605] mmcblk1: mmc1: SB128 119 GiB 
[  152.131962]  mmcblk1: p1
[  157.293946] exfat: Deprecated parameter 'namecase'
[  258.519565] mmc1: card  removed
[  321.168230] mmc1: cannot verify signal voltage switch
[  321.293643] mmc1: new ultra high speed SDR104 SDXC card at address 
[  321.302028] mmcblk1: mmc1: SB128 119 GiB 
[  321.306774]  mmcblk1: p1
[  327.189197] exfat: Deprecated parameter 'namecase'

Again, i can "use" the card but, as soon as large data or any data is
put inside some directories in the sdxc card the data get corrupted.

if i use a sdhc card (8GB) everything works fine and, by dmesg

[ 2041.881666] mmc1: new high speed SDHC card at address e624
[ 2041.887000] mmcblk1: mmc1:e624 SU08G 7.40 GiB 
[ 2041.920884]  mmcblk1: p1
[ 2048.181250] exfat: Deprecated parameter 'namecase'

should i use apport-collect with that kernel too?

thanks in advance

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

Title:
  SDXC card reader not working properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have tried to use a 8GB flash and it works without any flaw in
  ubuntu 20.04, kernel 5.4.0-58-generic (machine: Ideapad 130s-11IGM),
  but i need to use my 128GB SDXC card and it only works in my windows
  system in the same machine. I am "able" to copy files to it  in ubuntu
  (to the 128GB SDXC card) but most of the copies appear as corrupted
  files, which does not happen in windows. The 8GB card had been tested
  by f3 in ubuntu and h2testw in windows, and the SDXC had been tested
  by h2testw in windows (testing the SDXC with f3 in ubuntu causes
  input/output error), so i assume there are no problems in the sd
  cards.


  I think that this problem is related to (or almost the same as)

  https://bugzilla.kernel.org/show_bug.cgi?id=202473


  by lspci i get

  00:00.0 Host bridge: Intel Corporation Gemini Lake Host Bridge (rev 03)
  00:00.1 Signal processing controller: Intel Corporation Celeron/Pentium 
Silver Processor Dynamic Platform and Thermal Framework Processor Participant 
(rev 03)
  00:00.3 System peripheral: Intel Corporation Device 3190 (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 605 (rev 03)
  00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03)
  00:0f.0 Communication controller: Intel Corporation Celeron/Pentium Silver 
Processor Trusted Execution Engine Interface (rev 03)
  00:12.0 SATA controller: Intel Corporation Device 31e3 (rev 03)
  00:13.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:14.0 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:14.1 PCI bridge: Intel Corporation Gemini Lake PCI Express Root Port (rev 
f3)
  00:15.0 USB controller: Intel Corporation Device 31a8 (rev 03)
  00:17.0 Signal processing controller: Intel Corporation Device 31b4 (rev 03)
  00:1c.0 SD Host controller: Intel Corporation Celeron/Pentium Silver 
Processor SDA Standard Compliant SD Host Controller (rev 03)
  00:1f.0 ISA bridge: Intel Corporation Device 31e8 (rev 03)
  00:1f.1 SMBus: Intel Corporation Celeron/Pentium Silver Processor Gaussian 
Mixture Model (rev 03)
  -
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader (rev 01)
  -
  03:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus 
Bluetooth (rev 99)


  booting up and putting the SDXC card and removing it gives

  by dmesg

  [  119.612298] mmc1: cannot verify signal voltage switch
  [  119.737024] mmc1: new ultra high speed SDR104 SDXC card at address 
  [  119.737955] mmcblk1: mmc1: SB128 119 GiB 
  [  119.755488]  mmcblk1: p1
  [  208.417246] mmc1: card  removed


  The module used is rtsx_pci.

  by lspci -nnk|grep -A2 RTS5229

  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI 
Express Card Reader [10ec:5229] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card 
Reader [10ec:5229]
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci


  
  Sorry for the lack of information, i tried to use ubuntu-bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bruno  1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-12-01 (33 days ago)
  

[Kernel-packages] [Bug 1914287] [NEW] PANIC at zfs_vfsops.c:585:zfs_space_delta_cb / VERIFY3(sa.sa_magic == SA_MAGIC) failed

[John Stumbles]

Public bug reported:

When running rsync or tree (haven't tried much else) on much of the
filesystem it will pretty routinely throw a panic report in
syslog/kern.log, and the rsync/tree operation will later hang solidly
such that even ^C doesn't break back to the shell, and any further file
operations will likely hang and lock up their shells. Often requires
power cycle rather than just shutdown -r to reboot.

syslog/kern.log:

Feb  2 16:52:43 donny kernel: [  517.355790] VERIFY3(sa.sa_magic == SA_MAGIC) 
failed (*value* == 3100762) <- *value* varies e.g. 1612270437, 1612270437, 
1612283815
Feb  2 16:52:43 donny kernel: [  517.362904] PANIC at 
zfs_vfsops.c:585:zfs_space_delta_cb()
Feb  2 16:52:43 donny kernel: [  517.368512] Showing stack for process *pid*  
<- *pid* varies
Feb  2 16:52:43 donny kernel: [  517.368522] CPU: 1 PID: *pid* Comm: 
dp_sync_taskq Tainted: P C OE 5.4.0-1028-raspi #31-Ubuntu <- *pid* 
as above
Feb  2 16:52:43 donny kernel: [  517.368525] Hardware name: Raspberry Pi 4 
Model B Rev 1.4 (DT)
Feb  2 16:52:43 donny kernel: [  517.368527] Call trace:
Feb  2 16:52:43 donny kernel: [  517.368540]  dump_backtrace+0x0/0x198
Feb  2 16:52:43 donny kernel: [  517.368544]  show_stack+0x28/0x38
Feb  2 16:52:43 donny kernel: [  517.368549]  dump_stack+0xd8/0x134
Feb  2 16:52:43 donny kernel: [  517.368583]  spl_dumpstack+0x2c/0x34 [spl]
Feb  2 16:52:43 donny kernel: [  517.368606]  spl_panic+0xe0/0xf8 [spl]
Feb  2 16:52:43 donny kernel: [  517.368837]  zfs_space_delta_cb+0x180/0x278 
[zfs]
Feb  2 16:52:43 donny kernel: [  517.368968]  
dmu_objset_userquota_get_ids+0x15c/0x3b8 [zfs]
Feb  2 16:52:43 donny kernel: [  517.369094]  dnode_sync+0x11c/0x568 [zfs]
Feb  2 16:52:43 donny kernel: [  517.369216]  dmu_objset_sync_dnodes+0x48/0xf0 
[zfs]
Feb  2 16:52:43 donny kernel: [  517.369333]  sync_dnodes_task+0x34/0x58 [zfs]
Feb  2 16:52:43 donny kernel: [  517.369353]  taskq_thread+0x20c/0x3b0 [spl]
Feb  2 16:52:43 donny kernel: [  517.369363]  kthread+0x150/0x170
Feb  2 16:52:43 donny kernel: [  517.369368]  ret_from_fork+0x10/0x18


rsync/tree command carries on running (for a while), then later log file shows:


Feb  2 16:56:11 donny kernel: [  725.993423] INFO: task dp_sync_taskq:*pid* 
blocked for more than 120 seconds.
Feb  2 16:56:11 donny kernel: [  726.000633]   Tainted: P C OE 
5.4.0-1028-raspi #31-Ubuntu
Feb  2 16:56:11 donny kernel: [  726.007610] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb  2 16:56:11 donny kernel: [  726.015586] dp_sync_taskq   D0  *pid*  
2 0x0028
Feb  2 16:56:11 donny kernel: [  726.015595] Call trace:
Feb  2 16:56:11 donny kernel: [  726.015608]  __switch_to+0x108/0x1c0
Feb  2 16:56:11 donny kernel: [  726.015615]  __schedule+0x328/0x828
Feb  2 16:56:11 donny kernel: [  726.015621]  schedule+0x4c/0xe8
Feb  2 16:56:11 donny kernel: [  726.015650]  spl_panic+0xf4/0xf8 [spl]
Feb  2 16:56:11 donny kernel: [  726.015829]  zfs_space_delta_cb+0x180/0x278 
[zfs]
Feb  2 16:56:11 donny kernel: [  726.015939]  
dmu_objset_userquota_get_ids+0x15c/0x3b8 [zfs]
Feb  2 16:56:11 donny kernel: [  726.016045]  dnode_sync+0x11c/0x568 [zfs]
Feb  2 16:56:11 donny kernel: [  726.016151]  dmu_objset_sync_dnodes+0x48/0xf0 
[zfs]
Feb  2 16:56:11 donny kernel: [  726.016256]  sync_dnodes_task+0x34/0x58 [zfs]
Feb  2 16:56:11 donny kernel: [  726.016276]  taskq_thread+0x20c/0x3b0 [spl]
Feb  2 16:56:11 donny kernel: [  726.016283]  kthread+0x150/0x170
Feb  2 16:56:11 donny kernel: [  726.016288]  ret_from_fork+0x10/0x18
Feb  2 16:56:11 donny kernel: [  726.016298] INFO: task txg_sync:*num* blocked 
for more than 120 seconds. <- *num* varies
Feb  2 16:56:11 donny kernel: [  726.023051]   Tainted: P C OE 
5.4.0-1028-raspi #31-Ubuntu
Feb  2 16:56:11 donny kernel: [  726.029957] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb  2 16:56:11 donny kernel: [  726.037919] txg_syncD0  *num*  
2 0x0028
Feb  2 16:56:11 donny kernel: [  726.037929] Call trace:
Feb  2 16:56:11 donny kernel: [  726.037939]  __switch_to+0x108/0x1c0
Feb  2 16:56:11 donny kernel: [  726.037945]  __schedule+0x328/0x828
Feb  2 16:56:11 donny kernel: [  726.037951]  schedule+0x4c/0xe8
Feb  2 16:56:11 donny kernel: [  726.037973]  taskq_wait+0x78/0xb0 [spl]
Feb  2 16:56:11 donny kernel: [  726.038142]  dmu_objset_sync+0x25c/0x3e0 [zfs]
Feb  2 16:56:11 donny kernel: [  726.038263]  dsl_dataset_sync+0x74/0x240 [zfs]
Feb  2 16:56:11 donny kernel: [  726.038391]  dsl_pool_sync+0xb0/0x3b8 [zfs]
Feb  2 16:56:11 donny kernel: [  726.038509]  
spa_sync_iterate_to_convergence+0xf8/0x1f0 [zfs]
Feb  2 16:56:11 donny kernel: [  726.038617]  spa_sync+0x2ec/0x520 [zfs]
Feb  2 16:56:11 donny kernel: [  726.038736]  txg_sync_thread+0x244/0x2a0 [zfs]
Feb  2 16:56:11 donny kernel: [  726.038756]  thread_generic_wrapper+0x78/0xa8 
[spl]
Feb  2 16:56:11 donny kernel: [  726.038768]  kthread+0x150/0x170
Feb  2 16:56:11 

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

[Aksahat]

https://pastebin.ubuntu.com/p/4pyrWCYryT/

:fabianbur , Here are results of those commands, will switching my
kernel from boot menu to hwe-20.04 might help?

uname -sr returns >Linux 5.8.0-41-generic

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 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:
  Fix Released
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
  vectors") currently in vanilla kernel tree for v5.11.

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Where problems could occur]

  An unpatched kernel will not be able to probe SATA controllers moved
  behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
  attached on it completely unusable. With this change, kernel would
  then be able to probe them but may also suffer from issues that only
  occur under such configuration. However, the worst case is to move away
  sata disks from VMD bus as they are currently without this fix, so the
  risk here should be justified.

  == Previous SRU ==

  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

[Kernel-packages] [Bug 1894778] Re: Cannot probe sata disk on sata controller behind VMD: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

[Aksahat]

Thankyou :fabianbur for replying, I have a few questions...

Could something go wrong while doing this?
How long before patched kernel is released for ubuntu-20.04?
How can I be sure of my error is this same error and will be relsolved by patch?

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

Title:
  Cannot probe sata disk on sata controller behind VMD: ata1.00: failed
  to IDENTIFY (I/O error, err_mask=0x4)

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 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:
  Fix Released
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

[ 6.163286] ata1.00: qc timeout (cmd 0xec)
[ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Upstream commit f6b7bb847ca8 ("PCI: vmd: Offset Client VMD MSI-X
  vectors") currently in vanilla kernel tree for v5.11.

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

$ lspci -vvnn

Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
Address: fee01000  Data: 

  [Where problems could occur]

  An unpatched kernel will not be able to probe SATA controllers moved
  behind VMD when VMD/RAID mode is enabled in BIOS, leaving disks
  attached on it completely unusable. With this change, kernel would
  then be able to probe them but may also suffer from issues that only
  occur under such configuration. However, the worst case is to move away
  sata disks from VMD bus as they are currently without this fix, so the
  risk here should be justified.

  == Previous SRU ==

  [SRU Justification]

  [Impact]

  When booting with a certain platforms with boot disk attached to SATA
  bus behind Intel VMD controller, disk probing may fail with following
  error messages left in dmesg:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)

  [Fix]

  Proposed kernel patch https://patchwork.kernel.org/patch/11758345/

  [Test Case]

  Check dmesg/lsblk for disk probe.

  For pci MSI address, check lspci output:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee0  Data: 

  When it fails, the address is fee0. And with a patched kernel:

    $ lspci -vvnn
    
    Capabilities: [80] MSI: Enable+ Count=1/1 maskable- 64bit-
    Address: fee01000  Data: 

  [Regression Potential]
  Low.  For previous NVMe based platforms, this patch brings no effective
  change for NVMe devices because they will still stay in fast-interrupt
  list.

  == Original Bug Description ==

  When booting with root filesystem on sata disks under Intel VMD mode,
  following errors printed in dmesg and no disk is found, nor booting
  into it:

    [ 6.163286] ata1.00: qc timeout (cmd 0xec)
    [ 6.165630] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 6.483649] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 16.659284] ata1.00: qc timeout (cmd 0xec)
    [ 16.661717] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 16.663161] ata1: limiting SATA link speed to 1.5 Gbps
    [ 16.983890] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    [ 48.147294] ata1.00: qc timeout (cmd 0xec)
    [ 48.149737] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    [ 48.467889] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

    $ lspci
    ...
    1:e0:17.0 SATA controller: Intel Corporation Device a0d3 (rev 20)

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

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

[Kernel-packages] [Bug 1914283] [NEW] Enable CONFIG_PCI_MSI in the linux-kvm derivative

[Guilherme G. Piccoli]

Public bug reported:

To be filled - I'm just reserving the LP number for now.

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

** Affects: linux-kvm (Ubuntu Xenial)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

** Affects: linux-kvm (Ubuntu Bionic)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

** Affects: linux-kvm (Ubuntu Focal)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

** Affects: linux-kvm (Ubuntu Groovy)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

** Affects: linux-kvm (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
 Status: In Progress

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

** No longer affects: linux (Ubuntu)

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

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

** Changed in: linux-kvm (Ubuntu)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

** Also affects: linux-kvm (Ubuntu Hirsute)
   Importance: Medium
 Assignee: Guilherme G. Piccoli (gpiccoli)
   Status: In Progress

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

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

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

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

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

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

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

** Changed in: linux-kvm (Ubuntu Groovy)
   Importance: Undecided => Medium

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

** Changed in: linux-kvm (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux-kvm (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux-kvm (Ubuntu Groovy)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: linux-kvm (Ubuntu Focal)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: linux-kvm (Ubuntu Bionic)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

** Changed in: linux-kvm (Ubuntu Xenial)
 Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)

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

Title:
  Enable CONFIG_PCI_MSI in the linux-kvm derivative

Status in linux-kvm package in Ubuntu:
  In Progress
Status in linux-kvm source package in Xenial:
  In Progress
Status in linux-kvm source package in Bionic:
  In Progress
Status in linux-kvm source package in Focal:
  In Progress
Status in linux-kvm source package in Groovy:
  In Progress
Status in linux-kvm source package in Hirsute:
  In Progress

Bug description:
  To be filled - I'm just reserving the LP number for now.

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

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

[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Julian Andres Klode]

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

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1914279

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules

[Marc Deslauriers]

I agree this sounds like an undesirable scenario. I think all dkms
packages should get built in -security as part of the SRU process to
prevent this sort of thing from happening in the future.

Do we do test rebuilds of all the dkms modules before switching the
kernel meta package to a new upstream version?

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

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

[Kernel-packages] [Bug 1914279] [NEW] linux from security may force reboots without complete dkms modules

[Dimitri John Ledkov]

*** This bug is a security vulnerability ***

Public security bug reported:

Whilst discussing

https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
ubuntu-desktop-installation-media/20606

We have noticed a reference to somebody not having working backport-
iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
switch.

However, kernel meta switch was pushed to security pocket, but the dkms
modules are all in -updates only.

This may result in people automatically installing the new kernel with
unatanded upgrades; dkms modules failing to build; and a reboot required
flag left on disk.

At this point launching update manager will not offer to install dkms
modules from updates, and will guide the users to reboot. which will
then cause them to boot the new kernel without the dkms modules that
might be providing networking for them.

Should dkms modules SRUs always getting published into -security pocket,
as well as the -updates pocket?

Should linux maintainer scripts prevent touching reboot required flag if
any dkms modules fail to build?

Should apt / unattanded-upgrades / update-manager always update dkms
modules with kernels?

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

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

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

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

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (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/1914279

Title:
  linux from security may force reboots without complete dkms modules

Status in apt package in Ubuntu:
  New
Status in dkms package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in linux-meta package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Whilst discussing

  https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
  ubuntu-desktop-installation-media/20606

  We have noticed a reference to somebody not having working backport-
  iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8
  switch.

  However, kernel meta switch was pushed to security pocket, but the
  dkms modules are all in -updates only.

  This may result in people automatically installing the new kernel with
  unatanded upgrades; dkms modules failing to build; and a reboot
  required flag left on disk.

  At this point launching update manager will not offer to install dkms
  modules from updates, and will guide the users to reboot. which
  will then cause them to boot the new kernel without the dkms modules
  that might be providing networking for them.

  Should dkms modules SRUs always getting published into -security
  pocket, as well as the -updates pocket?

  Should linux maintainer scripts prevent touching reboot required flag
  if any dkms modules fail to build?

  Should apt / unattanded-upgrades / update-manager always update dkms
  modules with kernels?

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

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

[Kernel-packages] [Bug 1911438] Re: CIFS: Request for backport

[Marcelo Cerri]

** Description changed:

  [Impact]
  
  Microsoft CIFS team requested below patches to be backported (it was
  marked for stable last month) to Ubuntu 18.04 and newer.
  
  6988a619f5b7 "cifs: allow syscalls to be restarted in __smb_send_rqst()"
- 2659d3bff3e1 cifs: fix interrupted close commands
+ 2659d3bff3e1 "cifs: fix interrupted close commands"
+ 214a5ea081e7 "cifs: do not fail __smb_send_rqst if non-fatal signals are 
pending"
  
  Since 6988a619f5b79e4efadea6e19dcfe75fbcd350b5 hasn't been picked up for
  5.4.0-1031-azure (the current 18.04 kernel version for Azure image), I
  would like make a request for backport.
  
  [Test Case]
  
  Since those are small improvements a basic smoke test can be used to
  avoid regressions:
  
  1. Install cifs-utils and dbench:
  
-   $ sudo apt-get install cifs-utils dbench
+   $ sudo apt-get install cifs-utils dbench
  
  2. Mount a CIFS share using:
  
-$ sudo mount -t cifs -o username=REMOTEUSER
+    $ sudo mount -t cifs -o username=REMOTEUSER
  \\remoteip\path\to\shared\folder /mnt
  
  3. Run dbench and check for regressions:
  
-$ cd /mnt; dbench 20 -t 120 -D .
+    $ cd /mnt; dbench 20 -t 120 -D .
  
  [Where problems could occur]
  
  The regression potential is restricted to the ability of mounting and
  accessing CIFS volumes.

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

Title:
  CIFS: Request for backport

Status in linux package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Invalid
Status in linux-azure source package in Groovy:
  Invalid

Bug description:
  [Impact]

  Microsoft CIFS team requested below patches to be backported (it was
  marked for stable last month) to Ubuntu 18.04 and newer.

  6988a619f5b7 "cifs: allow syscalls to be restarted in __smb_send_rqst()"
  2659d3bff3e1 "cifs: fix interrupted close commands"
  214a5ea081e7 "cifs: do not fail __smb_send_rqst if non-fatal signals are 
pending"

  Since 6988a619f5b79e4efadea6e19dcfe75fbcd350b5 hasn't been picked up
  for 5.4.0-1031-azure (the current 18.04 kernel version for Azure
  image), I would like make a request for backport.

  [Test Case]

  Since those are small improvements a basic smoke test can be used to
  avoid regressions:

  1. Install cifs-utils and dbench:

    $ sudo apt-get install cifs-utils dbench

  2. Mount a CIFS share using:

     $ sudo mount -t cifs -o username=REMOTEUSER
  \\remoteip\path\to\shared\folder /mnt

  3. Run dbench and check for regressions:

     $ cd /mnt; dbench 20 -t 120 -D .

  [Where problems could occur]

  The regression potential is restricted to the ability of mounting and
  accessing CIFS volumes.

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

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

[Kernel-packages] [Bug 1914271] [NEW] LXD virtual machine freezes on bootup and accessing storage driver

[nean]

Public bug reported:

LXD virtual machine freezes on bootup and when accessing mounted
external storage driver


The 2 issues has been raised on github at the LXD project, where it turned out, 
the issue is related to the kvm kernel using for vm (qemu), switching the 
generic kernel within the vm (qemu) has solved the issues.

All the steps to reproduce the issue incl. output and panics has been
documented, thus I'm kindly ask to refer to the github issues:
https://github.com/lxc/lxd/issues/8400 and
https://github.com/lxc/lxd/issues/7224


Steps to reproduce:
lxc init ubuntu:focal v1 --vm
lxc config set v1 limits.cpu 4
lxc config device add v1 extv1 disk source=/external/mount/backup 
path=/mnt/external
lxc start v1
lxc console v1


workaround:
apt install linux-generic
apt remove linux-image-5.4.0-1032-kvm
update-grub

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


** Tags: linux-kvm lxd qemu

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

Title:
  LXD virtual machine freezes on bootup and accessing storage driver

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  LXD virtual machine freezes on bootup and when accessing mounted
  external storage driver

  
  The 2 issues has been raised on github at the LXD project, where it turned 
out, the issue is related to the kvm kernel using for vm (qemu), switching the 
generic kernel within the vm (qemu) has solved the issues.

  All the steps to reproduce the issue incl. output and panics has been
  documented, thus I'm kindly ask to refer to the github issues:
  https://github.com/lxc/lxd/issues/8400 and
  https://github.com/lxc/lxd/issues/7224


  Steps to reproduce:
  lxc init ubuntu:focal v1 --vm
  lxc config set v1 limits.cpu 4
  lxc config device add v1 extv1 disk source=/external/mount/backup 
path=/mnt/external
  lxc start v1
  lxc console v1


  workaround:
  apt install linux-generic
  apt remove linux-image-5.4.0-1032-kvm
  update-grub

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

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

[Kernel-packages] [Bug 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade

[Kai-Heng Feng]

Thanks for testing. According to upstream dev, we need to enable more kernel 
config options. Please test this kernel:
https://people.canonical.com/~khfeng/lp1902457-enable-hda-codecs/

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

Title:
  regression: no sound cards detected on lenovo yoga c930 after
  focal->groovy upgrade

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no 
soundcards detected"
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-07-25 (465 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M
   |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M
   |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic 
root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-26-generic N/A
   linux-backports-modules-5.8.0-26-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-26-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago)
  UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo 
video
  _MarkForUpload: False
  dmi.bios.date: 10/09/2018
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN32WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-07-25 (487 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: linux (not installed)
  Tags:  groovy
  Uname: Linux 5.10.0-051000rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago)
  UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo 
video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2019-07-25 (496 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth 
Adapter
   Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
   Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic 
root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-31-generic N/A
   linux-backports-modules-5.8.0-31-generic  N/A
   linux-firmware  

[Kernel-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

[Dave Jones]

There's a version of bluez with the patches that I've submitted upstream
built in the following PPA against the hirsute branch (the patch changes
are pretty minimal; basically amounts to removal of the arbitrary
sleep(1) as during December's tests I couldn't find a single platform
that actually required that, even amongst the Pi's we don't support like
the zero):

https://launchpad.net/~waveform/+archive/ubuntu/bluez

I'm happy to convert that to a git-ubuntu branch if that's preferable.
Once sponsored, we should consider SRU'ing to focal given that Pi400
support is now being SRU'd there generally.

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Groovy:
  Fix Released
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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

[Kernel-packages] [Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools

[Guilherme G. Piccoli]

In fact Anders, I just thought of a potential alternative issue, so do
you mind to run a 3rd test?

(c) After running tests (a) and (b) from the last comment, please boot
the machine and edit the file "/etc/default/grub.d/kdump-tools.cfg",
changing the crashkernel parameter there to be exactly
"crashkernel=384M" - after that, please execute "sudo update-grub" and
reboot the machine, finally trying a kdump again.

With that test, we can be sure it's not a memory issue on kdump environment, 
since ZFS might consume more memory than kdump boot had reserved.
Thanks,


Guilherme

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

Title:
  linux-crashdump is not capable of mounting zfs root pools

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I could not get any crash logs after using this package.

  I tried using it and triggering a crash from a terminal. The alternate
  kernel boots successfully, but the initrd for linux-crashdump is not
  capable of loading my rpool.

  running: linux-crashdump:amd64 5.4.0.64.67

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-crashdump:amd64 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jan 28 20:15:19 2021
  InstallationDate: Installed on 2019-08-15 (532 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7885
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-65-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1b81,10de:10f0,1b21:1242 
video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
crashkernel=2096M-:2096M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-22 (281 days ago)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.E0
  dmi.board.asset.tag: Default string
  dmi.board.name: X99A SLI PLUS(MS-7885)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7885
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962

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

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

[Kernel-packages] [Bug 1913639] Re: linux-crashdump is not capable of mounting zfs root pools

[Guilherme G. Piccoli]

Hi Anders, thanks for your testing. You can show all the initrd scripts
debug output to console, for that you'd need to add the kernel parameter
"debug=vc" for example. But I don't suggest to do that here, since you
seem not able to capture the full console log in plain/text form.
Pictures/snapshots might help to spot some issue, but they are very
limited.

So, instead of dumping the output to console, I'll suggest you 2 more
tests:

a) Add the following parameter to kernel command-line: "debug" . With
that, boot normally, and collect/save the following file, in order to
attach it here: "/run/initramfs/initramfs.debug" . This is the full
output of initrd scripts executed. After that, try the kdump - you need
to be sure it inherited this "debug" flag (check the kdump command-line
in "kdump-config show" output to validate it's there). Kdump will fail,
and you can try to SSH the file from the (initramfs) failure shell (or
even dump it there using the "cat" command and grab some pictures,
specially from the final portions of it). You may try to disconnect and
reconnect the keyboard, or use another USB port to see if you can get
that working in the failing (initramfs) shell.


b) Please execute the following 2 commands and submit the 2 resulting files 
here:

lsinitramfs /boot/initrd.img-$(uname -r) > regular_initrd.out
lsinitramfs /var/lib/kdump/initrd.img-$(uname -r) > kdump_initrd.out


Thanks in advance!

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

Title:
  linux-crashdump is not capable of mounting zfs root pools

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I could not get any crash logs after using this package.

  I tried using it and triggering a crash from a terminal. The alternate
  kernel boots successfully, but the initrd for linux-crashdump is not
  capable of loading my rpool.

  running: linux-crashdump:amd64 5.4.0.64.67

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-crashdump:amd64 (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Jan 28 20:15:19 2021
  InstallationDate: Installed on 2019-08-15 (532 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7885
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-65-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
intel_iommu=on iommu=pt vfio-pci.ids=10de:1b81,10de:10f0,1b21:1242 
video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
crashkernel=2096M-:2096M vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-65-generic N/A
   linux-backports-modules-5.4.0-65-generic  N/A
   linux-firmware1.187.8
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-22 (281 days ago)
  dmi.bios.date: 06/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.E0
  dmi.board.asset.tag: Default string
  dmi.board.name: X99A SLI PLUS(MS-7885)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E0:bd06/15/2018:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7885
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962

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

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

[Kernel-packages] [Bug 1913853] Re: Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

[Kleber Sacilotto de Souza]

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

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

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

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Critical

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

Title:
  Ubuntu 16.04 kernel 4.4.0-202 basic commands hanging

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Hi there,
  I've updated kernel on my Ubuntu 16.04 from 4.4.0-201-generic to 
4.4.0.202-generic today and it broke my system.
  Basic commands, such as pidof, lsof, ps fax (ps -a works) hang indefinitely 
and not even root issued kill -KILL will terminate them. Only thing that helps 
is to kill the shell that started such commands.

  I had to reboot back to 4.4.0-201, however during shutdown various
  stop jobs hanged as well and after more than 25 minutes I had to go
  for hard reboot.

  My current—NOT BROKEN—kernel has signature (cat /proc/version_signature):
  Ubuntu 4.4.0-201.233-generic 4.4.247

  I am attaching the lspci-vnvn.log, also created with the non-broken
  kernel.

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

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

[Kernel-packages] [Bug 1906168] Re: Prevent thermal shutdown during boot process

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.10 - 5.10.0-1013.14

---
linux-oem-5.10 (5.10.0-1013.14) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1013.14 -proposed tracker (LP:
#1914024)

  * Fix no video output when boot up system with type-c port  (LP: #1914020)
- drm/i915/tgl: Fix typo during output setup

 -- Timo Aaltonen   Mon, 01 Feb 2021
12:47:03 +0200

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

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

Title:
  Prevent thermal shutdown during boot process

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 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:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed

Bug description:
  [Impact]
  Surprising thermal shutdown at boot on Intel based mobile workstations.
   
  [Fix]
  Since these thermal devcies are not in ACPI ThermalZone, OS shouldn't
  shutdown the system.

  These critial temperatures are for usespace to handle, so let kernel
  know it shouldn't handle it.

  SRU for stable kernels will be sent after the fix is in upstream.

  [Test]
  Use reboot stress as a reproducer. 5% chance to see a surprising
  shutdown at boot.

  With the fix applied, the thermal shutdown is no longer reproducible.

  [Where problems could occur]
  For ACPI based platforms, we still have "acpitz" to protect systems from
  overheating. If these acpitz sensors don't work, then the system could
  face real overheating issue.

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

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

[Kernel-packages] [Bug 1911830] Re: alsa/sdw: support soundwire audio for TGL-H machines

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.10 - 5.10.0-1013.14

---
linux-oem-5.10 (5.10.0-1013.14) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1013.14 -proposed tracker (LP:
#1914024)

  * Fix no video output when boot up system with type-c port  (LP: #1914020)
- drm/i915/tgl: Fix typo during output setup

 -- Timo Aaltonen   Mon, 01 Feb 2021
12:47:03 +0200

** Changed in: linux-oem-5.10 (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/1911830

Title:
  alsa/sdw: support soundwire audio for TGL-H machines

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

Bug description:
  [Impact]
  In the OEM project, we have a new TGL-H soundwire machine, with
  the current oem-5.10 kernel, the audio can't work.

  [Fix]
  Backport 6 patches from Intel thesofproject kernel.

  [Test]
  Put the testing sof-tgl-h.ri in the /lib/firmware/intel/sof,
  boot the patched kernel, we could see speakers and microphone
  from gnome-setting, and they all work well.

  
  [Where problems could occur]
  The patches changed soundwire machine driver, it is possible
  to make the audio on old soundwire machines not work anymore.
  But we tested the patches on TGL-U and cml soundwire machines,
  all worked well.

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

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

[Kernel-packages] [Bug 1912676] Re: Fix regression introduced by codec PM change

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.10 - 5.10.0-1013.14

---
linux-oem-5.10 (5.10.0-1013.14) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1013.14 -proposed tracker (LP:
#1914024)

  * Fix no video output when boot up system with type-c port  (LP: #1914020)
- drm/i915/tgl: Fix typo during output setup

 -- Timo Aaltonen   Mon, 01 Feb 2021
12:47:03 +0200

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

Title:
   Fix regression introduced by codec PM change

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Confirmed
Status in linux-oem-5.10 source package in Groovy:
  Invalid

Bug description:
  [Impact]
  After the codec PM optimization, laptops with SOF may take very long to
  suspend. In addition to that, HDA may not be able to be runtim suspended
  again after resume from hibernation.

  [Fix]
  Prevent the SOF driver touches codec during system suspend, and properly
  refcount the PM usage counter.

  [Test]
  On an affected SOF system, it takes 5 mins to suspend.
  On another affected HDA system, S4 resume causes high power consumption
  becuase HDA controller can't be runtime suspended.

  Both issues are gone by applying these patches.

  [Where problems could occur]
  If somehow any laptop depends on the old behavior to work properly, this
  can break them. It's highly unlikely though.

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

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

[Kernel-packages] [Bug 1913372] Re: Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.10 - 5.10.0-1013.14

---
linux-oem-5.10 (5.10.0-1013.14) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1013.14 -proposed tracker (LP:
#1914024)

  * Fix no video output when boot up system with type-c port  (LP: #1914020)
- drm/i915/tgl: Fix typo during output setup

 -- Timo Aaltonen   Mon, 01 Feb 2021
12:47:03 +0200

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

Title:
  Fix the video can't output through WD19TB connected  on TGL's Type-C
  port during cold-boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  WD19TB would report the number of lane(2-lane) and it works well on Type-C 
port of TGL platform.
  Change the LTTPR mode to non-transparent mode, WD19TB would report the larger 
number of lane(4-lane). It's over the type-c port's bandwidth.

  [Fix]
  The patch is provided by 
Imre(https://patchwork.freedesktop.org/series/86267/).
  Calculate the PBN divider value based on the rate and lane count link 
parameters that the driver uses for all other computation.

  [Test Case]
  1. Connected the WD19TB with the TGL platform's Type-C port and
  connected the external monitor on WD19TB with HDMI/Displayport.
  2. Cold boot the TGL platform.
  3. Check the monitor can be blinked and the video can output to the monitor.

  [Where problems could occur]
  It's more reasonable to calculate the PBN divider based on the source's rate 
and lane count, not the mst's capability.

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

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

[Kernel-packages] [Bug 1914020] Re: Fix no video output when boot up system with type-c port

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.10 - 5.10.0-1013.14

---
linux-oem-5.10 (5.10.0-1013.14) focal; urgency=medium

  * focal/linux-oem-5.10: 5.10.0-1013.14 -proposed tracker (LP:
#1914024)

  * Fix no video output when boot up system with type-c port  (LP: #1914020)
- drm/i915/tgl: Fix typo during output setup

 -- Timo Aaltonen   Mon, 01 Feb 2021
12:47:03 +0200

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

Title:
  Fix no video output when boot up system with type-c port

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  [Impact]
  Connect a WD19SC/WD19TB/typeC2hdmi converter on the machine type-c port, 
video can't output to the external monitor.

  [Fix]
  The patch is provided by 
Imre(https://patchwork.freedesktop.org/patch/msgid/2020110401.4165574-1-imre.d...@intel.com).

  Correct the typo during output setup.
  Fix a typo that led to some MST short pulse event handling issue (the
  short pulse event was handled for both encoder instances, each having
  its own state).

  [Test Case]
  1. Connected the WD19SC/WD19TB/typeC2hdmi converter with the TGL platform's 
Type-C port and
  connected the external monitor on WD19SC/WD19TB/type-c2hdmi with 
HDMI/Displayport.
  2. Cold boot the TGL platform.
  3. Check the monitor can be blinked and the video can output to the monitor.

  [Where problems could occur]
  Just correct the typo and have low regression risk.

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

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

[Kernel-packages] [Bug 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)

[Frank Heimes]

Yes, the two kernel are on the same level - I did a rebuild since the
above patch is common code and the kernel needed to be build on all
significant architectures - that's what I did based on the PPA.

So looks like the messages/warning are gone, but that there is another issue.
I'm changing the status to Incomplete for the time being ...

** Changed in: ubuntu-z-systems
   Status: Triaged => Incomplete

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

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

Title:
  [Ubuntu 20.04] Problem leading IUCV service down (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Incomplete

Bug description:
  When I deployed a Ubuntu20.04 instance with kernel version of
  5.4.0-58-generic under z/VM, I saw below messages from kernel and the
  iucvserv program malfunctioned. Hence it caused some devices like
  network device configuration failure and deployment failure.

  
  Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from 
IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check 
authorization.
  Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, 
len=7
  Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded 
version is 0.0.0.1
  Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd  2>&1; 
echo iucvcmdrc=$? sent from IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message 
length=14,#012 /#012iucvcmdrc=0
  Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here 
]
  Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy 
whitelist? Kernel memory exposure attempt detected from SLUB object 
'dma-kmalloc-1k' (offset 0, size 20)!
  Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at 
mm/usercopy.c:75 usercopy_warn+0xa0/0xd0
  Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag 
udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT 
nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr
  ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmur vfio_ccw vfio_mdev mdev 
s390_trng vfio_iommu_type1 vfio sch_fq_codel drm drm
  _panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress 
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear
   pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes 
sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common 
dasd_fba_mod dasd_mod qeth_l2 qeth qdio ccwgroup
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] CPU: 1 PID: 697 Comm: 
iucvserv Not tainted 5.4.0-58-generic #64-Ubuntu
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] Hardware name: IBM 8561 LT1 
400 (z/VM 7.1.0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184719] Krnl PSW : 0704c0018000 
b3c37a60 (usercopy_warn+0xa0/0xd0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184721]R:0 T:1 IO:1 EX:1 
Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
  Dec 14 22:02:26 ub2004img kernel: [63084.184722] Krnl GPRS: 0004 
0006 0081 0007
  Dec 14 22:02:26 ub2004img kernel: [63084.184722]0007 
f2ecb400 b43fdc6a 03e00014
  Dec 14 22:02:26 ub2004img kernel: [63084.184723] 
0014  b43f01f0
  Dec 14 22:02:26 ub2004img kernel: [63084.184723]aae13300 
e9332a00 b3c37a5c 03e000987a10
  Dec 14 22:02:26 ub2004img kernel: [63084.184728] Krnl Code: b3c37a50: 
c020003e310f  larl%r2,b43fdc6e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a56: 
c0e5ffedbe85  brasl   %r14,b39ef760
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   #b3c37a5c: 
a7f40001  brc 15,b3c37a5e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   >b3c37a60: 
eb6ff0c4  lmg %r6,%r15,192(%r15)
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a66: 
07fe  bcr 15,%r14
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a68: 
47000700  bc  0,1792
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a6c: 
c020003e30fa  larl%r2,b43fdc60
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a72: 
a7f4ffd4  brc 15,b3c37a1a
  Dec 14 22:02:26 ub2004img kernel: [63084.184735] Ca

[Kernel-packages] [Bug 1910749] Re: stop building nvidia dkms on kernels with no lrm

[Thadeu Lima de Souza Cascardo]

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

** Changed in: linux-hwe-5.0 (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-hwe-5.0 (Ubuntu Xenial)
   Status: New => Invalid

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

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

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

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

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

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

** Changed in: linux-gke-5.0 (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-gke-5.0 (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  stop building nvidia dkms on kernels with no lrm

Status in linux package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-hwe-5.0 package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-hwe-5.0 source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-gke-5.0 source package in Bionic:
  Fix Committed
Status in linux-hwe-5.0 source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Building these modules wastes build time, and also may potentially lead to 
unnecessary updates.

  [Fix]
  Set do_dkms_nvidia = false on amd64.mk.

  [Test case]
  Build test the kernel.

  [Potential regression]
  Missing signed bits for these modules, in case someone uses them without LRMs.

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

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

[Kernel-packages] [Bug 1911476] Re: Groovy update: upstream stable patchset 2021-01-13

[William Breathitt Gray]

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

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

Title:
  Groovy update: upstream stable patchset 2021-01-13

Status in linux package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Groovy:
  Fix Committed
Status in linux-kvm source package in Groovy:
  New

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-01-13

  Ported from the following upstream stable releases:
  v5.4.84, v5.9.15,
  v5.4.85, v5.9.16

     from git://git.kernel.org/

  Kbuild: do not emit debug info for assembly with LLVM_IAS=1
  mm/zsmalloc.c: drop ZSMALLOC_PGTABLE_MAPPING
  UBUNTU: [Config] updateconfigs for ZSMALLOC_PGTABLE_MAPPING
  kprobes: Remove NMI context check
  kprobes: Tell lockdep about kprobe nesting
  ASoC: Intel: bytcr_rt5640: Fix HP Pavilion x2 Detachable quirks
  tools/bootconfig: Fix to check the write failure correctly
  net, xsk: Avoid taking multiple skbuff references
  bpftool: Fix error return value in build_btf_type_table
  vhost-vdpa: fix page pinning leakage in error path (rework)
  powerpc/64s: Fix hash ISA v3.0 TLBIEL instruction generation
  batman-adv: Consider fragmentation for needed_headroom
  batman-adv: Reserve needed_*room for fragments
  batman-adv: Don't always reallocate the fragmentation skb head
  ipvs: fix possible memory leak in ip_vs_control_net_init
  ibmvnic: handle inconsistent login with reset
  ibmvnic: stop free_all_rwi on failed reset
  ibmvnic: avoid memset null scrq msgs
  ibmvnic: delay next reset if hard reset fails
  ibmvnic: track pending login
  ibmvnic: send_login should check for crq errors
  ibmvnic: reduce wait for completion time
  drm/rockchip: Avoid uninitialized use of endpoint id in LVDS
  drm/panel: sony-acx565akm: Fix race condition in probe
  can: m_can: tcan4x5x_can_probe(): fix error path: remove erroneous 
clk_disable_unprepare()
  can: sja1000: sja1000_err(): don't count arbitration lose as an error
  can: sun4i_can: sun4i_can_err(): don't count arbitration lose as an error
  can: c_can: c_can_power_up(): fix error handling
  can: kvaser_pciefd: kvaser_pciefd_open(): fix error handling
  samples/ftrace: Mark my_tramp[12]? global
  scsi: storvsc: Fix error return in storvsc_probe()
  net: broadcom CNIC: requires MMU
  iwlwifi: pcie: invert values of NO_160 device config entries
  perf/x86/intel: Fix a warning on x86_pmu_stop() with large PEBS
  zlib: export S390 symbols for zlib modules
  phy: usb: Fix incorrect clearing of tca_drv_sel bit in SETUP reg for 7211
  arm64: dts: rockchip: Remove system-power-controller from pmic on Odroid Go 
Advance
  iwlwifi: pcie: limit memory read spin time
  arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.
  arm64: dts: rockchip: Reorder LED triggers from mmc devices on rk3399-roc-pc.
  iwlwifi: sta: set max HE max A-MPDU according to HE capa
  iwlwifi: pcie: set LTR to avoid completion timeout
  iwlwifi: mvm: fix kernel panic in case of assert during CSA
  powerpc: Drop -me200 addition to build flags
  arm64: dts: broadcom: clear the warnings caused by empty dma-ranges
  ARC: stack unwinding: don't assume non-current task is sleeping
  scsi: ufs: Fix unexpected values from ufshcd_read_desc_param()
  scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE
  interconnect: qcom: msm8916: Remove rpm-ids from non-RPM nodes
  interconnect: qcom: qcs404: Remove GPU and display RPM IDs
  ibmvnic: skip tx timeout reset while in resetting
  irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend
  drm/exynos: depend on COMMON_CLK to fix compile tests
  spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts
  arm-smmu-qcom: Ensure the qcom_scm driver has finished probing
  btrfs: do nofs allocations when adding and removing qgroup relations
  btrfs: fix lockdep splat when enabling and disabling qgroups
  soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)
  intel_idle: Fix intel_idle() vs tracing
  arm64: tegra: Disable the ACONNECT for Jetson TX2
  platform/x86: thinkpad_acpi: add P1 gen3 second fan support
  platform/x86: thinkpad_acpi: Do not report SW_TABLET_MODE on Yoga 11e
  platform/x86: thinkpad_acpi: Add BAT1 is primary battery quirk for Thinkpad 
Yoga 11e 4th gen
  platform/x86: thi

[Kernel-packages] [Bug 1910749] Re: stop building nvidia dkms on kernels with no lrm

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  stop building nvidia dkms on kernels with no lrm

Status in linux package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-hwe-5.0 package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-hwe-5.0 source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-gke-5.0 source package in Bionic:
  Fix Committed
Status in linux-hwe-5.0 source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Building these modules wastes build time, and also may potentially lead to 
unnecessary updates.

  [Fix]
  Set do_dkms_nvidia = false on amd64.mk.

  [Test case]
  Build test the kernel.

  [Potential regression]
  Missing signed bits for these modules, in case someone uses them without LRMs.

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

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

[Kernel-packages] [Bug 1910749] Re: stop building nvidia dkms on kernels with no lrm

[William Breathitt Gray]

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

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

Title:
  stop building nvidia dkms on kernels with no lrm

Status in linux package in Ubuntu:
  Invalid
Status in linux-gke-5.0 package in Ubuntu:
  Invalid
Status in linux-hwe-5.0 package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in linux-gke-5.0 source package in Xenial:
  Invalid
Status in linux-hwe-5.0 source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-gke-5.0 source package in Bionic:
  Fix Committed
Status in linux-hwe-5.0 source package in Bionic:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Building these modules wastes build time, and also may potentially lead to 
unnecessary updates.

  [Fix]
  Set do_dkms_nvidia = false on amd64.mk.

  [Test case]
  Build test the kernel.

  [Potential regression]
  Missing signed bits for these modules, in case someone uses them without LRMs.

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2021-02-02 08:14 EDT---
The latest update from Canonical is the same as the one updated last week.
During testingsted I don't see the kernel warning/error messages in the console 
log.
But I got a new issue.
Basically, the Nic device cannot be online via znetconfig.
I will attach the console log. That's the only thing we can get.
The guest didn't seem in emergency mode or other shell env.
So there is no way for me to check in the shell mode.
>From the z/VM guest side, we saw the Nic was created and attached the vswitch.

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

Title:
  [Ubuntu 20.04] Problem leading IUCV service down (on s390x)

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Triaged

Bug description:
  When I deployed a Ubuntu20.04 instance with kernel version of
  5.4.0-58-generic under z/VM, I saw below messages from kernel and the
  iucvserv program malfunctioned. Hence it caused some devices like
  network device configuration failure and deployment failure.

  
  Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from 
IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check 
authorization.
  Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, 
len=7
  Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded 
version is 0.0.0.1
  Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd  2>&1; 
echo iucvcmdrc=$? sent from IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message 
length=14,#012 /#012iucvcmdrc=0
  Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here 
]
  Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy 
whitelist? Kernel memory exposure attempt detected from SLUB object 
'dma-kmalloc-1k' (offset 0, size 20)!
  Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at 
mm/usercopy.c:75 usercopy_warn+0xa0/0xd0
  Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag 
udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT 
nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr
  ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmur vfio_ccw vfio_mdev mdev 
s390_trng vfio_iommu_type1 vfio sch_fq_codel drm drm
  _panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress 
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear
   pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes 
sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common 
dasd_fba_mod dasd_mod qeth_l2 qeth qdio ccwgroup
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] CPU: 1 PID: 697 Comm: 
iucvserv Not tainted 5.4.0-58-generic #64-Ubuntu
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] Hardware name: IBM 8561 LT1 
400 (z/VM 7.1.0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184719] Krnl PSW : 0704c0018000 
b3c37a60 (usercopy_warn+0xa0/0xd0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184721]R:0 T:1 IO:1 EX:1 
Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
  Dec 14 22:02:26 ub2004img kernel: [63084.184722] Krnl GPRS: 0004 
0006 0081 0007
  Dec 14 22:02:26 ub2004img kernel: [63084.184722]0007 
f2ecb400 b43fdc6a 03e00014
  Dec 14 22:02:26 ub2004img kernel: [63084.184723] 
0014  b43f01f0
  Dec 14 22:02:26 ub2004img kernel: [63084.184723]aae13300 
e9332a00 b3c37a5c 03e000987a10
  Dec 14 22:02:26 ub2004img kernel: [63084.184728] Krnl Code: b3c37a50: 
c020003e310f  larl%r2,b43fdc6e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a56: 
c0e5ffedbe85  brasl   %r14,b39ef760
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   #b3c37a5c: 
a7f40001  brc 15,b3c37a5e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   >b3c37a60: 
eb6ff0c4  lmg %r6,%r15,192(%r15)
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a66: 
07fe  bcr 15,%r14
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a68: 
47000700  bc  0,1792
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a6c: 
c020003e30fa  larl%r2,b43fdc60
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a72: 
a7f4ffd4  

[Kernel-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup

[Ronald Huetter]

In Ubuntu-Budgie the above trick doesn't solve the problem. I notice
that Ubuntu Desktop is using gdm3 whereas Ubuntu Budgie is using
lightdm. They are calling xorg with different arguments. So I
reconfigured Budgie for gdm3 and, after creating the monitor.xml file,
the flicker is gone.

I hope, this helps to fix the problem in Budgie. Let me know, if I can
do something else.

Respective xorg command lines:

Ubuntu-Budgie:
/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch

Ubuntu Desktop:
/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority 
-nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3

Ubuntu-Budgie with gdm3:
/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority 
-nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3

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

Title:
  [Cherry Trail] [modeset] Cursor flickering on dual screen setup

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When running on dual screen config, the cursor is heavily flickering.
  Makes it a very unpleasant experience, if not renders it unusable. If
  switched to only single screen, cursor is completely stable.

  When issuing 
  xrandr --output HDMI-2 --scale 0.99x0.99
  again cursor is stable. Switching to 200% scaling in the desktop settings, 
doesn't help.

  I tried to catch the effect in a movie. However, because of frame
  rate, it is not possible to show the effect. If if its helpful, let me
  know and I'll try harder.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jan 31 19:55:12 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2021-01-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  MachineType: BESSTAR (HK) LIMITED Z83-F
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 08/13/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A
  dmi.board.asset.tag: Default string
  dmi.board.name: T3 MRD
  dmi.board.vendor: BESSTAR Tech
  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.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z83-F
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: BESSTAR (HK) LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Jean-]

the next step to get a full fix and improved sound quality for voip
calls over BT headset is coming in
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1913442] console log with the patch kernel

[bugproxy]

--- Comment (attachment only) From y...@cn.ibm.com 2021-02-02 07:38 
EDT---


** Attachment added: "console log with the patch kernel"
   
https://bugs.launchpad.net/bugs/1913442/+attachment/5459100/+files/l5000ab9-0129.txt

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

Title:
  [Ubuntu 20.04] Problem leading IUCV service down (on s390x)

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Focal:
  Triaged

Bug description:
  When I deployed a Ubuntu20.04 instance with kernel version of
  5.4.0-58-generic under z/VM, I saw below messages from kernel and the
  iucvserv program malfunctioned. Hence it caused some devices like
  network device configuration failure and deployment failure.

  
  Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from 
IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check 
authorization.
  Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, 
len=7
  Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded 
version is 0.0.0.1
  Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd  2>&1; 
echo iucvcmdrc=$? sent from IUCV client.
  Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message 
length=14,#012 /#012iucvcmdrc=0
  Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here 
]
  Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy 
whitelist? Kernel memory exposure attempt detected from SLUB object 
'dma-kmalloc-1k' (offset 0, size 20)!
  Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at 
mm/usercopy.c:75 usercopy_warn+0xa0/0xd0
  Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag 
udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT 
nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr
  ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmur vfio_ccw vfio_mdev mdev 
s390_trng vfio_iommu_type1 vfio sch_fq_codel drm drm
  _panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress 
zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 linear
   pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes 
sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common 
dasd_fba_mod dasd_mod qeth_l2 qeth qdio ccwgroup
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] CPU: 1 PID: 697 Comm: 
iucvserv Not tainted 5.4.0-58-generic #64-Ubuntu
  Dec 14 22:02:26 ub2004img kernel: [63084.184718] Hardware name: IBM 8561 LT1 
400 (z/VM 7.1.0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184719] Krnl PSW : 0704c0018000 
b3c37a60 (usercopy_warn+0xa0/0xd0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184721]R:0 T:1 IO:1 EX:1 
Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
  Dec 14 22:02:26 ub2004img kernel: [63084.184722] Krnl GPRS: 0004 
0006 0081 0007
  Dec 14 22:02:26 ub2004img kernel: [63084.184722]0007 
f2ecb400 b43fdc6a 03e00014
  Dec 14 22:02:26 ub2004img kernel: [63084.184723] 
0014  b43f01f0
  Dec 14 22:02:26 ub2004img kernel: [63084.184723]aae13300 
e9332a00 b3c37a5c 03e000987a10
  Dec 14 22:02:26 ub2004img kernel: [63084.184728] Krnl Code: b3c37a50: 
c020003e310f  larl%r2,b43fdc6e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a56: 
c0e5ffedbe85  brasl   %r14,b39ef760
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   #b3c37a5c: 
a7f40001  brc 15,b3c37a5e
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]   >b3c37a60: 
eb6ff0c4  lmg %r6,%r15,192(%r15)
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a66: 
07fe  bcr 15,%r14
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a68: 
47000700  bc  0,1792
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a6c: 
c020003e30fa  larl%r2,b43fdc60
  Dec 14 22:02:26 ub2004img kernel: [63084.184728]b3c37a72: 
a7f4ffd4  brc 15,b3c37a1a
  Dec 14 22:02:26 ub2004img kernel: [63084.184735] Call Trace:
  Dec 14 22:02:26 ub2004img kernel: [63084.184736] ([] 
usercopy_warn+0x9c/0xd0)
  Dec 14 22:02:26 ub2004img kernel: [63084.184740]  [] 
__check_heap_object+0xd8/0x150
  Dec 14 22:02:26 ub2004img kernel: [63084.184

[Kernel-packages] [Bug 1913933] Re: System freeze while dbus-daemon execution

[Kai-Heng Feng]

Just wait until the issue re-appeared.

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chshr  2241 F pulseaudio
   /dev/snd/controlC0:  chshr  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago

[Kernel-packages] [Bug 1913933] Re: System freeze while dbus-daemon execution

[ch shr]

Thank you, i did install the latest mainline kernel. Do you need another
dump of all the log files?

Or should i now wait if the issue appears again?

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

Title:
  System freeze while dbus-daemon execution

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I regularly get my system frozen while using. It does not occur on any
  user interaction I do periodically, so I checked the log files last
  time it happened:

  These are the last 3 kernel log entries before the freeze:

  Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1400 
audit(1612017269.344:43): apparmor="DENIED" operation="open" 
profile="snap.standard-notes.standard-notes" 
name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 
comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 
audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 
subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call"  
bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 
label="snap.standard-notes.standard-notes"
  Jan 30 15:34:29 ubuntu kernel: [24749.903525]  exe="/usr/bin/dbus-daemon" 
sauid=103 hostname=? addr=? terminal=?'
  
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

  So I think this is related to the dbus-daemon.

  If you need any more information, please let me know so I can provide
  them.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: dbus 1.12.20-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sun Jan 31 09:22:49 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  SourcePackage: dbus
  UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chshr  2241 F pulseaudio
   /dev/snd/controlC0:  chshr  2241 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=a16d1655-2fcf-4952-8a1b-3a45eb9b2c52
  MachineType: Micro-Star International Co., Ltd MS-7A34
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=4542740f-595f-4809-a71b-f170ee2827e3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  Tag

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Alberto Milone]

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

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

Title:
  Introduce the new NVIDIA 460-server series and update the 460 series

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Committed

Bug description:
  Introduce the new NVIDIA 460-server series and update the 460 series.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 460-server ==

    * Initial release:
  - Added support for the following GPUs:
  NVIDIA A40
  NVIDIA RTX A6000
  - Added support for CUDA 11.2.

  == 460 ==

    * New upstream release:
  - Added support for the following GPUs:
  GeForce RTX 3080 Laptop GPU
  GeForce RTX 3070 Laptop GPU
  GeForce RTX 3060 Laptop GPU
  GeForce GT 1010
  - Updated the NVIDIA driver to restore functionality of some
    features, including runtime power management, hotplugging
    audio-capable display devices, and S0ix-based system suspend,
    with recent kernels such as Linux 5.10.
  - Fixed a bug that caused bindless texture samplers to be
    incorrectly counted towards the MAX_COMPUTE_TEXTURE_IMAGE_UNITS
    limit.
  - Fixed a bug that could cause the GPU to hang when attempting to
    perform link training on an HDMI 2.1 Fixed Rate Link (FRL)
    display, while the display is powered off.
  - Fixed a bug that could intermittently cause NvFBC applications
    to fail with the error message "Unable to send exported fds".

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1914224

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: focal

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

Title:
  Use hardware switch to turn off ariplane mode problem in Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a HP 15-r014TX model numbered laptop. I recently installed
  Ubuntu 20.04 in it alongside windows 8 (actually upgraded fro 18.04).
  It had a hardware problem causing wifi to not connect but only scan
  nearby network. So I attached a usb wifi adapter and everything was
  working till yesterday. Now I have airplane mode turned on and saying
  it can only be turned of by hardware switch by default that laptop has
  F12 as the default button to toggle hardware airplane mode. I tried it
  and popup showed that it has turned it on but it didn't help me to
  turn that off again. Referring to many forums I tried popular
  solutions to fix the problem but nothing worked for me. I also checked
  bios to whether there is an option but found nothing. No I discovered
  that the problem is only with Ubuntu and in windows every thing works
  fine.

  **output of rfkill list all**

  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

  **Output of lshw**

*-network 
 description: Ethernet interface
 product: RTL810xE PCI Express Fast Ethernet controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:08:00.0
 logical name: enp8s0
 version: 07
 serial: d0:bf:9c:07:07:fe
 capacity: 100Mbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII
 resources: irq:18 ioport:4000(size=256) memory:b560-b5600fff 
memory:b540-b5403fff
*-network DISABLED
 description: Wireless interface
 product: RT3290 Wireless 802.11n 1T/1R PCIe
 vendor: Ralink corp.
 physical id: 0
 bus info: pci@:0a:00.0
 logical name: wlp10s0f0
 version: 00
 serial: 74:29:af:80:e9:47
 width: 32 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=rt2800pci 
driverversion=5.4.0-42-generic firmware=N/A latency=0 link=no multicast=yes 
wireless=IEEE 802.11
 resources: irq:16 memory:b551-b551

  **information of usb wifi card**

  Bus 002 Device 010: ID 0bda:8179 Realtek Semiconductor Corp.
  RTL8188EUS 802.11n Wireless Network Adapter

  details of wireless pci card

  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 
0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT 
Integrated Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller 
(rev 0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 
04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 
04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 
(rev e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 
(rev e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 
[AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  08:00.0 Ethernet controller: Realtek Sem

[Kernel-packages] [Bug 1914224] [NEW] Use hardware switch to turn off ariplane mode problem in Ubuntu 20.04

[Ron Stephen Mathew]

Public bug reported:

I have a HP 15-r014TX model numbered laptop. I recently installed Ubuntu
20.04 in it alongside windows 8 (actually upgraded fro 18.04). It had a
hardware problem causing wifi to not connect but only scan nearby
network. So I attached a usb wifi adapter and everything was working
till yesterday. Now I have airplane mode turned on and saying it can
only be turned of by hardware switch by default that laptop has F12 as
the default button to toggle hardware airplane mode. I tried it and
popup showed that it has turned it on but it didn't help me to turn that
off again. Referring to many forums I tried popular solutions to fix the
problem but nothing worked for me. I also checked bios to whether there
is an option but found nothing. No I discovered that the problem is only
with Ubuntu and in windows every thing works fine.

**output of rfkill list all**

1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

**Output of lshw**

  *-network 
   description: Ethernet interface
   product: RTL810xE PCI Express Fast Ethernet controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0
   bus info: pci@:08:00.0
   logical name: enp8s0
   version: 07
   serial: d0:bf:9c:07:07:fe
   capacity: 100Mbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list 
ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII
   resources: irq:18 ioport:4000(size=256) memory:b560-b5600fff 
memory:b540-b5403fff
  *-network DISABLED
   description: Wireless interface
   product: RT3290 Wireless 802.11n 1T/1R PCIe
   vendor: Ralink corp.
   physical id: 0
   bus info: pci@:0a:00.0
   logical name: wlp10s0f0
   version: 00
   serial: 74:29:af:80:e9:47
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
   configuration: broadcast=yes driver=rt2800pci 
driverversion=5.4.0-42-generic firmware=N/A latency=0 link=no multicast=yes 
wireless=IEEE 802.11
   resources: irq:16 memory:b551-b551

**information of usb wifi card**

Bus 002 Device 010: ID 0bda:8179 Realtek Semiconductor Corp.
RTL8188EUS 802.11n Wireless Network Adapter

details of wireless pci card

00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller 
(rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 
04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 
04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev 
e4)
00:1c.5 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 6 (rev 
e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI 
mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI 
Express Fast Ethernet controller (rev 07)
09:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 
610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1)
0a:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
0a:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth


  I tried switching desktop environments and network managers but nothing 
worked.


Is there any fix for this problem.

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


** Tags: focal

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

Title:
  Use hardware switch to turn off ariplane mode problem in Ubuntu 20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a HP 15-r014TX model numbered laptop. I recently installed
  Ubuntu 20.04 in it alongside windows 8 (actually upgraded fro 18.04).
  It had a hardware problem causing wifi to no

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [Cherry Trail] [modeset] Cursor flickering on dual screen setup

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When running on dual screen config, the cursor is heavily flickering.
  Makes it a very unpleasant experience, if not renders it unusable. If
  switched to only single screen, cursor is completely stable.

  When issuing 
  xrandr --output HDMI-2 --scale 0.99x0.99
  again cursor is stable. Switching to 200% scaling in the desktop settings, 
doesn't help.

  I tried to catch the effect in a movie. However, because of frame
  rate, it is not possible to show the effect. If if its helpful, let me
  know and I'll try harder.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jan 31 19:55:12 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2021-01-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  MachineType: BESSTAR (HK) LIMITED Z83-F
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 08/13/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A
  dmi.board.asset.tag: Default string
  dmi.board.name: T3 MRD
  dmi.board.vendor: BESSTAR Tech
  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.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z83-F
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: BESSTAR (HK) LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

[Henrik Juul Hansen]

Good news!

Before suspend/resume:
Powertop: around 1.5W - pc2,3,7,8,10
ASPM L1 enabled for all controllers

After suspend/resume:
Powertop: around 1.5W - pc2,3,7,8,10
ASPM L1 enabled for all controllers

Fn-keys and touchpad working.

Dmesg is attached.

** Attachment added: "dmesg.5.11.0-7"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912057/+attachment/5459064/+files/dmesg.5.11.0-7

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  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.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup

[Ronald Huetter]

Have to add to the above: after first login, I rearranged the screens
using the Display Settings. That creates a file ~/.config/monitors.xml.
That file does some magic in preventing the flickering. However, it
becomes effective only after logging out and logging in again, so I was
mislead when testing the flickering above. Anyways: deleting the file,
logging out, logging in (Xorg) and the flickering is back. Rearranging
screens, logging out/in: flickering is gone.

With this, I'll try on Ubuntu-Budgie again.

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

Title:
  [Cherry Trail] [modeset] Cursor flickering on dual screen setup

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When running on dual screen config, the cursor is heavily flickering.
  Makes it a very unpleasant experience, if not renders it unusable. If
  switched to only single screen, cursor is completely stable.

  When issuing 
  xrandr --output HDMI-2 --scale 0.99x0.99
  again cursor is stable. Switching to 200% scaling in the desktop settings, 
doesn't help.

  I tried to catch the effect in a movie. However, because of frame
  rate, it is not possible to show the effect. If if its helpful, let me
  know and I'll try harder.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jan 31 19:55:12 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2021-01-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  MachineType: BESSTAR (HK) LIMITED Z83-F
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 08/13/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A
  dmi.board.asset.tag: Default string
  dmi.board.name: T3 MRD
  dmi.board.vendor: BESSTAR Tech
  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.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z83-F
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: BESSTAR (HK) LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1913739] Re: aws: properly support instance types with > 255 cpu cores

[Andrea Righi]

** Description changed:

  [Impact]
  
  To properly support instance types in AWS with > 255 cores we need to
  make sure that commit c40c1018ff1382f2d35df5129a6bcea3df6b
  ("iommu/vt-d: Gracefully handle DMAR units with no supported address
  widths") is applied across all our linux-aws kernels.
  
  [Test Case]
  
  Tests performed by AWS.
  
  [Fix]
  
  Apply/backport commit c40c1018ff1382f2d35df5129a6bcea3df6b.
  
+ For groovy it's a clean cherry pick.
+ 
+ For Focal/Bionic the backport activity is to simply rename the patched
+ file.
+ 
+ Only Xenial requires a little more backporting activity, in particular
+ we need to change the condition in free_iommu() checking if
+ iommu->iommu_dev is defined (instead of checking for iommu->iommu.ops,
+ that is not available in the 4.4 kernel).
+ 
  [Regression potential]
  
- The fix is affecting only intel IOMMU and it is an upstream fix, so the
- regression potential is minimal.
+ This change allows to use DMAR units that were not used before (for
+ interrupt remapping). Theoretically this should provide a performance
+ improvement, but we should keep an eye about potential performance
+ regressions of drivers that are using IOMMU, in case they're using this
+ new behavior incorrectly.
+ 
+ Moreover, the Xenial backport required an adjustment in free_iommu() to
+ check when we need to call iommu_device_destroy(), if the adjustment is
+ not 100% correct we could introduce a potential memory leak.

** No longer affects: linux-aws (Ubuntu Hirsute)

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

Title:
  aws: properly support instance types with > 255 cpu cores

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux-aws source package in Focal:
  In Progress
Status in linux-aws source package in Groovy:
  In Progress

Bug description:
  [Impact]

  To properly support instance types in AWS with > 255 cores we need to
  make sure that commit c40c1018ff1382f2d35df5129a6bcea3df6b
  ("iommu/vt-d: Gracefully handle DMAR units with no supported address
  widths") is applied across all our linux-aws kernels.

  [Test Case]

  Tests performed by AWS.

  [Fix]

  Apply/backport commit c40c1018ff1382f2d35df5129a6bcea3df6b.

  For groovy it's a clean cherry pick.

  For Focal/Bionic the backport activity is to simply rename the patched
  file.

  Only Xenial requires a little more backporting activity, in particular
  we need to change the condition in free_iommu() checking if
  iommu->iommu_dev is defined (instead of checking for iommu->iommu.ops,
  that is not available in the 4.4 kernel).

  [Regression potential]

  This change allows to use DMAR units that were not used before (for
  interrupt remapping). Theoretically this should provide a performance
  improvement, but we should keep an eye about potential performance
  regressions of drivers that are using IOMMU, in case they're using
  this new behavior incorrectly.

  Moreover, the Xenial backport required an adjustment in free_iommu()
  to check when we need to call iommu_device_destroy(), if the
  adjustment is not 100% correct we could introduce a potential memory
  leak.

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

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

[Kernel-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup

[Daniel van Vugt]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => 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/1913963

Title:
  [Cherry Trail] [modeset] Cursor flickering on dual screen setup

Status in linux package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  When running on dual screen config, the cursor is heavily flickering.
  Makes it a very unpleasant experience, if not renders it unusable. If
  switched to only single screen, cursor is completely stable.

  When issuing 
  xrandr --output HDMI-2 --scale 0.99x0.99
  again cursor is stable. Switching to 200% scaling in the desktop settings, 
doesn't help.

  I tried to catch the effect in a movie. However, because of frame
  rate, it is not possible to show the effect. If if its helpful, let me
  know and I'll try harder.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jan 31 19:55:12 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2021-01-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  MachineType: BESSTAR (HK) LIMITED Z83-F
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 08/13/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A
  dmi.board.asset.tag: Default string
  dmi.board.name: T3 MRD
  dmi.board.vendor: BESSTAR Tech
  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.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z83-F
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: BESSTAR (HK) LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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

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

[Kernel-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup

[Ronald Huetter]

Hi,
first to say: I've been testing Ubuntu-Budgie. There is no option to run on 
Wayland. So I downloaded (2021-02-02) and installed Ubuntu 21.04 Desktop to 
perform the test and found some surprising results:
1. fresh installation, running on Xorg: the flickering is clearly visible. In 
fact, the cursor flickers, if anywhere on the screen some redrawing happens. 
To reproduce: open Term. A slight flickering is visible whenever the console 
cursor is disappearing and reappearing. This is also the case outside the Term 
window. Increase the effect by launching Firefox and browse to cnn.com. While 
opening the page, a lot of redrawing is happening (the little bullet in the 
tab, some line in the bottom about loading, and the many items on the page. 
During the pay load, cursor is flickering anywhere on the screen.
2. logout and login, this time on Wayland: No such effect.
3. logout and login, again on Xorg, again no such effect!

Btw.: I cancelled to install updates to keep a stable environment, so
just the version as indicated above.

If you have any idea, how logging in on Wayland cured this effect
(reinstalled two times to be sure), I might be able to check on Ubuntu-
Budgie (where I can't simply select Wayland).

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

Title:
  [Cherry Trail] [modeset] Cursor flickering on dual screen setup

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  When running on dual screen config, the cursor is heavily flickering.
  Makes it a very unpleasant experience, if not renders it unusable. If
  switched to only single screen, cursor is completely stable.

  When issuing 
  xrandr --output HDMI-2 --scale 0.99x0.99
  again cursor is stable. Switching to 200% scaling in the desktop settings, 
doesn't help.

  I tried to catch the effect in a movie. However, because of frame
  rate, it is not possible to show the effect. If if its helpful, let me
  know and I'll try harder.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu56
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jan 31 19:55:12 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270]
  InstallationDate: Installed on 2021-01-30 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 
(20210115)
  MachineType: BESSTAR (HK) LIMITED Z83-F
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 08/13/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A
  dmi.board.asset.tag: Default string
  dmi.board.name: T3 MRD
  dmi.board.vendor: BESSTAR Tech
  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.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z83-F
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: BESSTAR (HK) LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou

[Kernel-packages] [Bug 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

[Kai-Heng Feng]

So, saving parent device stat in child's suspend routine doesn't keep
parent device at D0.

Please test this one instead, it prevents NVMe with HMB shutting down:
https://people.canonical.com/~khfeng/lp1912057-keep-hmb-nvme-d0/

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

Title:
  Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After boot the idle power consumption is around 2.3 W but after suspend it is 
4.7 W.
  The measurement is 5-10 min after boot/resume - looking at "top" to see 
system was idle.
  This is consistent - I have tried more that 10 times. 
  BIOS is updated to latest version.
  I have checked power consumption with external meter - and confirmed that it 
is higher.

  I have attached output of:
  sudo powertop -t 60 -r --html=before.html  (and after)

  I have noticed that Package C-state 6 is reached before suspend but
  not after.

  I expect that idle power consumption after suspend should be the same
  as before.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-38-generic 5.8.0-38.43
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hjh1448 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 16 15:49:32 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-01-03 (13 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-38-generic N/A
   linux-backports-modules-5.8.0-38-generic  N/A
   linux-firmware1.190.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425JA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425JA
  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.ec.firmware.release: 3.4
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425JA_UX425JA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

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

[Trent Lloyd]

I can confirm 100% this bug is still happening with 2.0.1 from hirsute-
proposed, even with a brand new install, on a different disk (SATA SSD
instead of NVMe Intel Optane 900p SSD), using 2.0.1 inside the installer
and from first boot. I can reproduce it reliably within about 2 hours
just using the desktop with google chrome (after restoring my google
chrome sync, so common set of data and extensions), it always seems to
trigger first on an access from Google Chrome for some reason - that
part is very reliable - but other files can get corrupt or lose access
including git trees and the like.

So I am at a loss to explain the cause given no one outside of Ubuntu
seems to be hitting this. It also, for whatever reason, seems to always
cause my tampermonkey and lastpass extension files to show as corrupt -
but not other extensions - very reliably happens every time.

The only notable change from default is I am using encryption=on with
passphrase for /home/user. I have not tested with encryption off.

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

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

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  In Progress

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

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

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

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

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packa

[Kernel-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10

[Mark Fraser]

** Attachment added: ".config/pulse directory of audio not working"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906267/+attachment/5459010/+files/pulse_not_working.tar.gz

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

Title:
  IntelHD audio not detected after upgrading to Ubuntu 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn
  my computer on the sound card doesn't work. If I load Pulse Audio
  Volume Control and disable and then re-enable the audio controller
  (Family 17h (Models 00h-0fh) HD Audio Controller it will work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Nov 30 15:19:50 2020
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-29-generic N/A
   linux-backports-modules-5.8.0-29-generic  N/A
   linux-firmware1.190.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-

[Kernel-packages] [Bug 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10

[Mark Fraser]

Happened again this morning and I had to move the pulse config directory
so that the computer would create a fresh version.

** Attachment added: ".config/pulse directory of audio working"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906267/+attachment/5459009/+files/pulse.tar.gz

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

Title:
  IntelHD audio not detected after upgrading to Ubuntu 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn
  my computer on the sound card doesn't work. If I load Pulse Audio
  Volume Control and disable and then re-enable the audio controller
  (Family 17h (Models 00h-0fh) HD Audio Controller it will work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Nov 30 15:19:50 2020
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-29-generic N/A
   linux-backports-modules-5.8.0-29-generic  N/A
   linux-firmware1.190.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  groovy
  Uname: Linux 5.8.0-29-generic x86_64
  UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.90
  dmi.board.name: B450M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.10
  HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d
  InstallationDate: Installed on 2020-03-21 (254 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root

[Kernel-packages] [Bug 1913739] Re: aws: properly support instance types with > 255 cpu cores

[Stefan Bader]

** Changed in: linux-aws (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

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

** Changed in: linux-aws (Ubuntu Groovy)
   Importance: Undecided => Medium

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

** Changed in: linux-aws (Ubuntu Groovy)
 Assignee: (unassigned) => Andrea Righi (arighi)

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

Title:
  aws: properly support instance types with > 255 cpu cores

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Xenial:
  In Progress
Status in linux-aws source package in Bionic:
  In Progress
Status in linux-aws source package in Focal:
  In Progress
Status in linux-aws source package in Groovy:
  In Progress
Status in linux-aws source package in Hirsute:
  New

Bug description:
  [Impact]

  To properly support instance types in AWS with > 255 cores we need to
  make sure that commit c40c1018ff1382f2d35df5129a6bcea3df6b
  ("iommu/vt-d: Gracefully handle DMAR units with no supported address
  widths") is applied across all our linux-aws kernels.

  [Test Case]

  Tests performed by AWS.

  [Fix]

  Apply/backport commit c40c1018ff1382f2d35df5129a6bcea3df6b.

  [Regression potential]

  The fix is affecting only intel IOMMU and it is an upstream fix, so
  the regression potential is minimal.

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

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

[Kernel-packages] [Bug 1910561] Re: Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile Workstation

[jeremyszu]

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

** Changed in: oem-priority
   Status: Triaged => Fix Released

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

Title:
  Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7
  Mobile Workstation

Status in OEM Priority Project:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  * Mute and micmute LED are not work accurately on HP ZBook Fury 15/17 G7 
Mobile Workstation when muting corresponding audio devices.
  * The right channel of internal speaker has not sound.

  [Fix]
  Apply ALC285_FIXUP_HP_GPIO_AMP_INIT quirk to expose GPIOs for controlling 
LEDs and initialing AMP.

  [Test]
  Built a test kernel with applying this patch, the mute/micmute LEDs are work 
as expected.
  The internal speaker could play the sounds from left and right channels.

  [Where problems could occur]
  This quirk is specific for these two platforms. It should not cause the 
regression to other systems.

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

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

[Kernel-packages] [Bug 1913809] Re: internal webcams of HP Elite X2 G2 not supported

[Kai-Heng Feng]

It requires userspace support. I am unsure how mature it is.

** Also affects: libcamera (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/1913809

Title:
  internal webcams of HP Elite X2 G2 not supported

Status in libcamera package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Both internal webcams of my HP Elite X2 G2 work well in Windows, but don't 
work in Ubuntu 20.10 or Manjaro. The driver seems to be missing or 
misconfigured. According to linux-hardware.org, it's a "Xeon E3-1200 v5/E3-1500 
v5/6th Gen Core Processor Imaging Unit". Guvcview recognises the Cameras as 
"Intel IPU3 CIO2", but doesn't show an image.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elis   6420 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 004: ID 044e:1216 Alps Electric Co., Ltd 
   Bus 001 Device 002: ID 0424:2422 Microchip Technology, Inc. (formerly SMSC) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Elite x2 1012 G2
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=8e01b873-3dab-4fbf-86ce-04c4932b3c0a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-41-generic N/A
   linux-backports-modules-5.8.0-41-generic  N/A
   linux-firmware1.190.3
  Tags:  groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 10/20/2020
  dmi.bios.release: 1.37
  dmi.bios.vendor: HP
  dmi.bios.version: P87 Ver. 01.37
  dmi.board.name: 82CA
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 50.72
  dmi.chassis.asset.tag: 5CG7272QT5
  dmi.chassis.type: 32
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 80.114
  dmi.modalias: 
dmi:bvnHP:bvrP87Ver.01.37:bd10/20/2020:br1.37:efr80.114:svnHP:pnHPElitex21012G2:pvr:rvnHP:rn82CA:rvrKBCVersion50.72:cvnHP:ct32:cvr:
  dmi.product.family: 103C_5336AN HP Elite x2
  dmi.product.name: HP Elite x2 1012 G2
  dmi.product.sku: Y5E21AV
  dmi.sys.vendor: HP

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

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