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

[You-Sheng Yang]

commit 5d6651fe85837b11564a2e2c3c6279c057d078d6
Author: Guo-Feng Fan 
Date:   Tue Feb 2 13:50:12 2021 +0800

rtw88: 8821c: support RFE type2 wifi NIC

RFE type2 is a new NIC which has one RF antenna shares with BT.
Update phy parameter to verstion V57 to allow initial procedure
to load extra AGC table for sharing antenna NIC.

Signed-off-by: Guo-Feng Fan 
Signed-off-by: Ping-Ke Shih 
Tested-by: Kai-Heng Feng 
Signed-off-by: Kalle Valo 
Link: https://lore.kernel.org/r/20210202055012.8296-4-pks...@realtek.com

Will be available in v5.12.

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

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

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

Bug description:
  8821ce is being upstreamed in https://lore.kernel.org/linux-
  wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it
  to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms
  from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce .

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

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

[Kernel-packages] [Bug 1907421] Re: [UBUNTU 21.04] vfio: pass DMA availability information to userspace

[Frank Heimes]

Commit 6507174efc67 "vfio iommu: Add dma available capability" comes with 
Ubuntu-5.4.0-67.
It's still in proposed as of today.

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

Title:
  [UBUNTU 21.04] vfio: pass DMA availability information to userspace

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

Bug description:
  Description:   vfio: pass DMA availability information to userspace
  Symptom:   vfio-pci device on s390 enters error state
  Problem:   Commit 492855939bdb added a limit to the number of concurrent
     DMA requests for a vfio container.  However, lazy unmapping in
     s390 can in fact cause quite a large number of outstanding DMA
     requests to build up prior to being purged, potentially the
     entire guest DMA space.  This results in unexpected errors seen
     in qemu such as 'VFIO_MAP_DMA failed: No space left on device'
  Solution:  The solution requires a change to both kernel and qemu - For
     the kernel, add the ability to provide the number of allowable
     DMA requests via the VFIO_IOMMU_GET_INFO ioctl.
  Reproduction:  Put a vfio-pci device on s390 under I/O load
  Upstream-ID:   a717072007e8aedd3f951726d8cf55454860b30d
     7d6e1329652ed971d1b6e0e7bea66fba5044e271

  Need also to be integrated into 20.10 and 20.04.

  OK, just to clarify we don't need to fix bionic for this one, but rather 
focal (20.04) and groovy (20.10).  Furthermore, for 20.04, 20.10 and 21.04 ONLY 
commit 7d6e1329652ed971d1b6e0e7bea66fba5044e271 is needed, the other was a 
pre-req that is already present.
  __

  SRU Justification:

  [Impact]

  * In case a vfio-pci device on s390x is under I/O load, vfio-pci
  device may end up in error state.

  * The commit 492855939bdb added a limit to the number of concurrent
  DMA requests for a vfio container.

  * However, lazy unmapping in s390x can in fact cause quite a large number of 
outstanding DMA requests
to build up prior to being purged - potentially the entire guest DMA space.

  * This results in unexpected errors seen in qemu such as 'VFIO_MAP_DMA
  failed: No space left on device'.

  * The solution requires a change to both kernel and qemu.

  * The kernel side of things is addressed by this SRU.

  * The fix adds the ability to provide the number of allowable DMA
  requests via VFIO_IOMMU_GET_INFO ioctl.

  * The actual fix comes with commit 7d6e1329652e, but another fix
  ccd59dce1a21 is needed to get it cleanly applied.

  [Fix]

  * ccd59dce1a21f473518bf273bdf5b182bab955b3 ccd59dce1a21 "vfio/type1:
  Refactor vfio_iommu_type1_ioctl()"

  * 7d6e1329652ed971d1b6e0e7bea66fba5044e271 7d6e1329652e "vfio iommu:
  Add dma available capability"

  [Test Case]

  * IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed.

  * PCIe adapters in place that provide vfio, like RoCE Express 2.

  * A KVM host needs to be setup and a KVM guest (use again 20.10) that
  uses vfio.

  * Generate I/O that flows through the vf and watch out for error like
  'VFIO_MAP_DMA failed: No space left on device' in the log.

  [Regression Potential]

  * The first patch ccd59dce1a21 modifies the common code file
  drivers/vfio/vfio_iommu_type1.c quity significantly.

  * But the reason is not that it introduces a lot of new things, it's a
  refactoring patch.

  * Nevertheless if done in a bad way it can significantly harm the IO
  memory management of virtual function adapters.

  * In worst case it may break them entirely, instead of 'just' exeeding
  the entire DMA space.

  * Things could also go wrong while doing the mapping and unmapping of
  DMA, that may even have an impact beyond vf adapters - harming other
  DMA devices.

  * The handling of dirty pages is also touched and the ioctl itself -
  which is important to keep the control of the devices.

  * But as said before, it re-factoring work, it's upstream accepted
  since 5.9 and the provenance shows that many engineers had an eye on
  these changes.

  * The second patch 7d6e1329652e - that inclides the needed fix - comes
  with far less modifications.

  * It also tounches drivers/vfio/vfio_iommu_type1.c but in a way that
  it mainly add one new function (vfio_iommu_dma_avail_build_caps) and
  an add. if statement in vfio_iommu_type1_get_info.

  * That allows to provide the current allowable number of DMA mappings to the 
userspace via the IOMMU info chain,
so that the userspace can take appropriate mitigation.

  * Potential problems here can be that the current allowable number of
  DMA mappings are wrong and in best case just mappings 

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

[Azizkhan]

Tried - 5.4.0-66.74, 5.8.0.44 and 5.11 kernels, nothing worked for me,
but i2c-hid and another one patches fixes problem. What can i do?

-- 
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:
  Fix Released
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
  Pro

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

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: hirsute

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

Title:
  Touchpad / keyboard don't work (randomly) after reboot on HP systems

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

  On some HP laptops (e.g. HP ZBook Fury 15/17 G7, HP EliteBook 850 G7,
  HP ENVY x360 Convertible 15-cp0xxx), the touchpad / keyboard will
  probably be disabled after reboot because the hp-wmi reports the
  system is a tablet system but it's not a tablet system.

  After libinput received "SW_TABLET_MODE", then it will disable the
  keyboard and touchpad.

  [Test case]

  Test 200 times reboot with:
  1. 5.10.0-1013-oem kernel:
   - the SW_TABLET_MODE was detected at 72 round and the keyboard / touchpad 
not work.
  2. 5.10.0-1013-oem kernel + 67fbe02a5cebc3c653610f12e3c0424e58450153:
   - the SW_TABLET_MODE is not be detected within 200 times reboot.

  [Fix]

  Cherry-pick commit 67fbe02a5cebc3c653610f12e3c0424e58450153.
  It turns the tablet mode detection to off as default and could be enabled by 
module parameter "enable_tablet_mode_sw".

  [Regression potential]

  It will break tablet detection on all HP laptops but user can enable it back 
by adding module parameter.
  If without this patch then a lot of HP new laptops (with newer HP BIOS) will 
get the keyboard/touchpad not work after reboot.

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

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

[Kernel-packages] [Bug 1916823] [NEW] Touchpad / keyboard don't work (randomly) after reboot on HP systems

[jeremyszu]

Public bug reported:

[Impact]

On some HP laptops (e.g. HP ZBook Fury 15/17 G7, HP EliteBook 850 G7, HP
ENVY x360 Convertible 15-cp0xxx), the touchpad / keyboard will probably
be disabled after reboot because the hp-wmi reports the system is a
tablet system but it's not a tablet system.

After libinput received "SW_TABLET_MODE", then it will disable the
keyboard and touchpad.

[Test case]

Test 200 times reboot with:
1. 5.10.0-1013-oem kernel:
 - the SW_TABLET_MODE was detected at 72 round and the keyboard / touchpad not 
work.
2. 5.10.0-1013-oem kernel + 67fbe02a5cebc3c653610f12e3c0424e58450153:
 - the SW_TABLET_MODE is not be detected within 200 times reboot.

[Fix]

Cherry-pick commit 67fbe02a5cebc3c653610f12e3c0424e58450153.
It turns the tablet mode detection to off as default and could be enabled by 
module parameter "enable_tablet_mode_sw".

[Regression potential]

It will break tablet detection on all HP laptops but user can enable it back by 
adding module parameter.
If without this patch then a lot of HP new laptops (with newer HP BIOS) will 
get the keyboard/touchpad not work after reboot.

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

** Description changed:

  [Impact]
  
  On some HP laptops (e.g. HP ZBook Fury 15/17 G7, HP EliteBook 850 G7, HP
  ENVY x360 Convertible 15-cp0xxx), the touchpad / keyboard will probably
  be disabled after reboot because the hp-wmi reports the system is a
  tablet system but it's not a tablet system.
  
  After libinput received "SW_TABLET_MODE", then it will disable the
  keyboard and touchpad.
  
  [Test case]
  
  Test 200 times reboot with:
  1. 5.10.0-1013-oem kernel:
-  - the SW_TABLET_MODE was detected at xxx round and the keyboard / touchpad 
not work.
+  - the SW_TABLET_MODE was detected at 72 round and the keyboard / touchpad 
not work.
  2. 5.10.0-1013-oem kernel + 67fbe02a5cebc3c653610f12e3c0424e58450153:
-  - the SW_TABLET_MODE is not be detected within 200 times reboot.
+  - the SW_TABLET_MODE is not be detected within 200 times reboot.
  
  [Fix]
  
  Cherry-pick commit 67fbe02a5cebc3c653610f12e3c0424e58450153.
  It turns the tablet mode detection to off as default and could be enabled by 
module parameter "enable_tablet_mode_sw".
  
  [Regression potential]
  
  It will break tablet detection on all HP laptops but user can enable it back 
by adding module parameter.
  If without this patch then a lot of HP new laptops (with newer HP BIOS) will 
get the keyboard/touchpad not work after reboot.

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

Title:
  Touchpad / keyboard don't work (randomly) after reboot on HP systems

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  On some HP laptops (e.g. HP ZBook Fury 15/17 G7, HP EliteBook 850 G7,
  HP ENVY x360 Convertible 15-cp0xxx), the touchpad / keyboard will
  probably be disabled after reboot because the hp-wmi reports the
  system is a tablet system but it's not a tablet system.

  After libinput received "SW_TABLET_MODE", then it will disable the
  keyboard and touchpad.

  [Test case]

  Test 200 times reboot with:
  1. 5.10.0-1013-oem kernel:
   - the SW_TABLET_MODE was detected at 72 round and the keyboard / touchpad 
not work.
  2. 5.10.0-1013-oem kernel + 67fbe02a5cebc3c653610f12e3c0424e58450153:
   - the SW_TABLET_MODE is not be detected within 200 times reboot.

  [Fix]

  Cherry-pick commit 67fbe02a5cebc3c653610f12e3c0424e58450153.
  It turns the tablet mode detection to off as default and could be enabled by 
module parameter "enable_tablet_mode_sw".

  [Regression potential]

  It will break tablet detection on all HP laptops but user can enable it back 
by adding module parameter.
  If without this patch then a lot of HP new laptops (with newer HP BIOS) will 
get the keyboard/touchpad not work after reboot.

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

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

[Kernel-packages] [Bug 1916763] Re: Night Light setting only working for a few seconds then It's gone

[Daniel van Vugt]

** Tags added: regression-update

** Summary changed:

- Night Light setting only working for a few seconds then It's gone
+ [i915] Night Light setting only working for a few seconds then It's gone

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

Title:
  [i915] Night Light setting only working for a few seconds then It's
  gone

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Ubuntu info is listed blow:

  ```
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  2. the `gnome-control-center` package version is
  ```
  gnome-control-center:
已安装：1:3.36.5-0ubuntu1
候选： 1:3.36.5-0ubuntu1
版本列表：
   *** 1:3.36.5-0ubuntu1 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 
Packages

  ```

  3. I expect when the Night Light settings are set, then it should be
  working as specified.

  4. Instead the Night Light settings only work for a few seconds, and
  then it went back to the original display state as if Night Light is
  not enabled.

  This only happens when I'm booting with kernel 5.4.0-66-generic, and
  everything works like a charm when booting with kernel
  5.4.0-65-generic.

  Please help looking into this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 24 22:43:23 2021
  DistUpgraded: 2020-08-01 23:39:12,134 DEBUG refresh of snap gtk-common-themes 
succeeded
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:5021]
 Subsystem: Lenovo Radeon R7 M260 [17aa:5021]
  InstallationDate: Installed on 2019-11-04 (478 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20EH0001CD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=e96f932e-c0e2-496e-b84d-653876b6b3ea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-08-01 (206 days ago)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J5ET50WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EH0001CD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50518 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:svnLENOVO:pn20EH0001CD:pvrThinkPadE450c:rvnLENOVO:rn20EH0001CD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E450c
  dmi.product.name: 20EH0001CD
  dmi.product.sku: LENOVO_MT_20EH_BU_Think_FM_ThinkPad E450c
  dmi.product.version: ThinkPad E450c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~kernel-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).

[Daniel van Vugt]

** Tags added: fixed-in-15 fixed-upstream

-- 
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 1916811] Re: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to
  install/upgrade: installed nvidia-dkms-460 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  Just doing a package update through synaptic and this one failed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
  Uname: Linux 5.10.17-051017-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 24 17:54:25 2021
  ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-05-24 (276 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-460
  Title: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to focal on 2021-02-17 (7 days ago)

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

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

[Kernel-packages] [Bug 1916811] [NEW] package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error ex

[Lee]

Public bug reported:

Just doing a package update through synaptic and this one failed.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
Uname: Linux 5.10.17-051017-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Feb 24 17:54:25 2021
ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2020-05-24 (276 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: nvidia-graphics-drivers-460
Title: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: Upgraded to focal on 2021-02-17 (7 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to
  install/upgrade: installed nvidia-dkms-460 package post-installation
  script subprocess returned error exit status 10

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

Bug description:
  Just doing a package update through synaptic and this one failed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 460.39-0ubuntu0.20.04.1
  Uname: Linux 5.10.17-051017-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb 24 17:54:25 2021
  ErrorMessage: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2020-05-24 (276 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-460
  Title: package nvidia-dkms-460 460.39-0ubuntu0.20.04.1 failed to 
install/upgrade: installed nvidia-dkms-460 package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: Upgraded to focal on 2021-02-17 (7 days ago)

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

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

[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

[Robert Jonsson]

Thinkpad T400 with non working two finger scroll here running Kubuntu
20.04, I just wanted to comment that none of the above solutions worked
for me, but one that I found buried in a youtube video did get it to
work! And I just can't leave it visible ONLY in a video, it's just not
right.

What it boils down to is running these three xinput commands (I'm sure someone 
with more knowledge can say what this actually does and possibly the 
corresponding configuration file settings)
xinput --set-prop --type=int --format=32 "SynPS/2 Synaptics TouchPad" 
"Synaptics Two-Finger Width" 8
xinput --set-prop --type=int --format=32 "SynPS/2 Synaptics TouchPad" 
"Synaptics Two-Finger Pressure" 4
xinput --set-prop --type=int  --format=8 "SynPS/2 Synaptics TouchPad" 
"Synaptics Two-Finger Scrolling" 1 0

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1916804] [NEW] nvidia-kernel-source-450 450.102.04-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Joseph Malionek]

Public bug reported:

Happens when I open up the "Additional Drivers" part of settings to the
proprietary drivers page. I am not currently using the nvidia 450
drivers

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-450 (not installed)
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.8.0-44-generic
Date: Wed Feb 24 10:43:22 2021
InstallationDate: Installed on 2021-02-07 (17 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
PackageVersion: 450.102.04-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: nvidia-graphics-drivers-450
Title: nvidia-kernel-source-450 450.102.04-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  nvidia-kernel-source-450 450.102.04-0ubuntu0.20.04.1: nvidia kernel
  module failed to build

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

Bug description:
  Happens when I open up the "Additional Drivers" part of settings to
  the proprietary drivers page. I am not currently using the nvidia 450
  drivers

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-450 (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.8.0-44-generic
  Date: Wed Feb 24 10:43:22 2021
  InstallationDate: Installed on 2021-02-07 (17 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  PackageVersion: 450.102.04-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.5, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-450
  Title: nvidia-kernel-source-450 450.102.04-0ubuntu0.20.04.1: nvidia kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files

[Ufos92]

This bug stills persists!
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325

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

Title:
  update-initramfs complains of missing amdgpu firmware files

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in linux-firmware source package in Eoan:
  Fix Released

Bug description:
  SRU Justification

  Impact: With 5.3 update-initramfs reports several missing amdgpu
  firmware files:

  update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic
  W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module 
amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for 
module amdgpu
  W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module 
amdgpu

  Of these, only raven_kicker_rlc.bin has been added to upstream linux-
  firmware.

  Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other
  files from modinfo for amdgpu.

  Test Case: Once fixed, the warnings from update-initramfs should be
  gone.

  Regression Potential: Adding a missing firmware is unlikely to break
  any working hardware. Removing the other missing files from modinfo
  will not cause regressions either, however if the firmware is added
  later update-initramfs will not add the files to the initramfs until
  the firmware is added back to modinfo.

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

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

[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Ufos92]

Still affects me!

```
$ uname -v
#49~20.04.1-Ubuntu SMP Fri Feb 5 09:57:56 UTC 2021
```

```
$ uname -r
5.8.0-43-generic
```

```
$ sudo lshw -c CPU
  *-cpu 
   description: CPU
   product: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
```


While `apt dist-upgrade` to the version above, I got tonns of `W: Possible 
missing firmware /lib/firmware/amdgpu/navi`. I thought something got broken!

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

Title:
  update-initramfs complains of missing amdgpu firmware files

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

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

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

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

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

Title:
  llvmpipe used instead of amdgpu

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I boot into Linux 5.8.0-44, I get a 1024x768 resolution instead
  of full monitor resolution. About page in settings shows that
  `llvmpipe (LLVM 11.0.0, 256 bits)` is used instead of amdgpu.

  This is a regression in Linux 5.8.0-44, the previous versions
  (5.8.0-43 and 5.8.0-41) work fine. I've also tested the proposed
  version (5.8.0-45) and it also had this issue.

  GPU: Radeon RX 570 4GB

  07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-44-generic 5.8.0-44.50
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   2147 F pulseaudio
   /dev/snd/controlC0:  user   2147 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 24 22:25:52 2021
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2019-08-31 (543 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-44-generic N/A
   linux-backports-modules-5.8.0-44-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-20 (127 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50a
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-01-03T13:15:50.415962

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

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

[Kernel-packages] [Bug 1916798] Re: llvmpipe used instead of amdgpu

[MasterProg]

** Summary changed:

- llvmpipe used intead of amdgpu
+ llvmpipe used instead of amdgpu

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

Title:
  llvmpipe used instead of amdgpu

Status in linux package in Ubuntu:
  New

Bug description:
  When I boot into Linux 5.8.0-44, I get a 1024x768 resolution instead
  of full monitor resolution. About page in settings shows that
  `llvmpipe (LLVM 11.0.0, 256 bits)` is used instead of amdgpu.

  This is a regression in Linux 5.8.0-44, the previous versions
  (5.8.0-43 and 5.8.0-41) work fine. I've also tested the proposed
  version (5.8.0-45) and it also had this issue.

  GPU: Radeon RX 570 4GB

  07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-44-generic 5.8.0-44.50
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   2147 F pulseaudio
   /dev/snd/controlC0:  user   2147 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 24 22:25:52 2021
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2019-08-31 (543 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-44-generic N/A
   linux-backports-modules-5.8.0-44-generic  N/A
   linux-firmware1.190.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2020-10-20 (127 days ago)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50a
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2021-01-03T13:15:50.415962

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

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

[Kernel-packages] [Bug 1916798] [NEW] llvmpipe used instead of amdgpu

[MasterProg]

Public bug reported:

When I boot into Linux 5.8.0-44, I get a 1024x768 resolution instead of
full monitor resolution. About page in settings shows that `llvmpipe
(LLVM 11.0.0, 256 bits)` is used instead of amdgpu.

This is a regression in Linux 5.8.0-44, the previous versions (5.8.0-43
and 5.8.0-41) work fine. I've also tested the proposed version
(5.8.0-45) and it also had this issue.

GPU: Radeon RX 570 4GB

07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-44-generic 5.8.0-44.50
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  user   2147 F pulseaudio
 /dev/snd/controlC0:  user   2147 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 24 22:25:52 2021
HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
InstallationDate: Installed on 2019-08-31 (543 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-44-generic N/A
 linux-backports-modules-5.8.0-44-generic  N/A
 linux-firmware1.190.3
SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-10-20 (127 days ago)
dmi.bios.date: 11/27/2019
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50a
dmi.board.asset.tag: Default string
dmi.board.name: AB350-Gaming 3-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350-Gaming 3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2021-01-03T13:15:50.415962

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


** Tags: amd64 apport-bug groovy

** Description changed:

- When booting into Linux 5.8.0-44, I get a 1024x768 resolution instead of
+ When I boot into Linux 5.8.0-44, I get a 1024x768 resolution instead of
  full monitor resolution. About page in settings shows that `llvmpipe
  (LLVM 11.0.0, 256 bits)` is used instead of amdgpu.
  
  This is a regression in Linux 5.8.0-44, the previous versions (5.8.0-43
  and 5.8.0-41) work fine. I've also tested the proposed version
  (5.8.0-45) and it also had this issue.
  
  Ubuntu 20.10
  GPU: Radeon RX 570 4GB
  
  07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
  07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI 
Audio [Radeon RX 470/480 / 570/580/590]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-44-generic 5.8.0-44.50
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  user   2147 F pulseaudio
-  /dev/snd/controlC0:  user   2147 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  user   2147 F pulseaudio
+  /dev/snd/controlC0:  user   2147 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 24 22:25:52 2021
  HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1
  InstallationDate: Installed on 2019-08-31 (543 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.8.0-44-generic N/A
-  linux-backports-modules-5.8.0-44-generic  N/A
-  linux-firmware1.190.3
+  linux-restricted-modules-5.8.0-44-generic N/A
+  linux-backpor

[Kernel-packages] [Bug 1914306] Re: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Steve Marino]

I don't know if this helps. I got this error because, I had my internet
connected to the wrong Ethernet port. When I swapped ports, the problem
went away.

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

Title:
  nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1: nvidia kernel module
  failed to build

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

Bug description:
  I found this issue when I'm installing libgl1-mesa-dev, now I cannot
  either upgrade or -f install.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.4.0-65-generic
  Date: Wed Feb  3 08:29:08 2021
  Dependencies:
   
  DuplicateSignature: 
dkms:nvidia-kernel-source-460:460.39-0ubuntu0.20.04.1:clang: error: unsupported 
option '-dumpspecs'
  InstallationDate: Installed on 2021-01-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  PackageVersion: 460.39-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-kernel-source-460 460.39-0ubuntu0.20.04.1: nvidia kernel module 
failed to build
  UpgradeStatus: Upgraded to focal on 2021-01-26 (7 days ago)

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

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

[Kernel-packages] [Bug 1809972] Re: Samsung SSD 750/850/860/870 EVO/QVO doesn't support queued TRIM command

[Gregory P Smith]

** Summary changed:

- Samsung SSD 750 EVO doesn't support queued TRIM command
+ Samsung SSD 750/850/860/870 EVO/QVO doesn't support queued TRIM command

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

Title:
  Samsung SSD 750/850/860/870 EVO/QVO doesn't support queued TRIM
  command

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SSD drive stops processing requests after a while
  With attached patch system is stable.
  Exact SSD information:
  ---
  Model=Samsung SSD 750 EVO 250GB, FwRev=MAT01B6Q, SerialNo=S33SNWBH536151Z
  ---

  Please note that system uses different SSD during bug reporting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   victor 2307 F...m pulseaudio
   /dev/snd/controlC1:  victor 2307 F pulseaudio
   /dev/snd/controlC0:  victor 2307 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Dec 28 15:25:43 2018
  HibernationDevice: RESUME=/dev/kubuntu-vg/swap_1
  MachineType: LENOVO 20BV0064US
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/kubuntu--vg-root ro resume=/dev/kubuntu-vg/swap_1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-06-11 (200 days ago)
  dmi.bios.date: 07/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET61WW (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV0064US
  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:bvrJBET61WW(1.25):bd07/13/2016:svnLENOVO:pn20BV0064US:pvrThinkPadT450:rvnLENOVO:rn20BV0064US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV0064US
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1916782] [NEW] fixdep, etc. gets built for wrong arch when cross-compiling Ubuntu kernel

[Kamal Mostafa]

Public bug reported:

Cross-compiling the Ubuntu kernel using the standard debian/rules
methods produces a linux-headers-{version}-{flavour} package which
contains executables (e.g. fixdep, several others) built for the build
host architecture, not the target host architecture.  Those executables
are unusable when that linux-headers package gets installed on the
target.

Example from an ARM64 cross-compiled linux-headers package (note the x86-64 
executable):
usr/src/linux-headers-5.10.0-14-generic/scripts/basic/fixdep: ELF 64-bit LSB 
shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter 
/lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=77b1c89ff5560389ea272ec0e81a4770246481a1, for GNU/Linux 3.2.0, 
not stripped

The kernel itself, of course, gets properly cross-compiled and the
generated packages (including linux-headers) will install fine on the
target.  But the bogus executables prevent full functionality on that
installation, i.e. it cannot be used for kernel driver development.

The fundamental reason why this occurs is that the build host needs to
run some of those compiled executables itself during the build, but
those executables should NOT get packaged.  Instead, the build should be
reorganized so that it compiles a set of temporary host-arch-execs for
use during the build, but then separately (cross)-compiles them as
target-arch-execs for inclusion in the linux-headers package.

This bug is Importance:Wishlist because:
 - cross-compiled Ubuntu kernel package builds aren't technically "supported".
 - this glitch only happens with engineer-built cross-compiled test kernels.
 - building natively instead (i.e. in a Launchpad PPA) avoids the problem.
 - this is not a new misbehavior; our cross-compile build rules have always 
been this way.

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

Title:
  fixdep, etc. gets built for wrong arch when cross-compiling Ubuntu
  kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Cross-compiling the Ubuntu kernel using the standard debian/rules
  methods produces a linux-headers-{version}-{flavour} package which
  contains executables (e.g. fixdep, several others) built for the build
  host architecture, not the target host architecture.  Those
  executables are unusable when that linux-headers package gets
  installed on the target.

  Example from an ARM64 cross-compiled linux-headers package (note the x86-64 
executable):
  usr/src/linux-headers-5.10.0-14-generic/scripts/basic/fixdep: ELF 64-bit LSB 
shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter 
/lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=77b1c89ff5560389ea272ec0e81a4770246481a1, for GNU/Linux 3.2.0, 
not stripped

  The kernel itself, of course, gets properly cross-compiled and the
  generated packages (including linux-headers) will install fine on the
  target.  But the bogus executables prevent full functionality on that
  installation, i.e. it cannot be used for kernel driver development.

  The fundamental reason why this occurs is that the build host needs to
  run some of those compiled executables itself during the build, but
  those executables should NOT get packaged.  Instead, the build should
  be reorganized so that it compiles a set of temporary host-arch-execs
  for use during the build, but then separately (cross)-compiles them as
  target-arch-execs for inclusion in the linux-headers package.

  This bug is Importance:Wishlist because:
   - cross-compiled Ubuntu kernel package builds aren't technically "supported".
   - this glitch only happens with engineer-built cross-compiled test kernels.
   - building natively instead (i.e. in a Launchpad PPA) avoids the problem.
   - this is not a new misbehavior; our cross-compile build rules have always 
been this way.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Marton Danko]

I've done it and it's still registered primary action for that user too,
it did not change anything.

-- 
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:
  Fix Released
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
   

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

Title:
  Night Light setting only working for a few seconds then It's gone

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1. Ubuntu info is listed blow:

  ```
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  2. the `gnome-control-center` package version is
  ```
  gnome-control-center:
已安装：1:3.36.5-0ubuntu1
候选： 1:3.36.5-0ubuntu1
版本列表：
   *** 1:3.36.5-0ubuntu1 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 
Packages

  ```

  3. I expect when the Night Light settings are set, then it should be
  working as specified.

  4. Instead the Night Light settings only work for a few seconds, and
  then it went back to the original display state as if Night Light is
  not enabled.

  This only happens when I'm booting with kernel 5.4.0-66-generic, and
  everything works like a charm when booting with kernel
  5.4.0-65-generic.

  Please help looking into this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 24 22:43:23 2021
  DistUpgraded: 2020-08-01 23:39:12,134 DEBUG refresh of snap gtk-common-themes 
succeeded
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:5021]
 Subsystem: Lenovo Radeon R7 M260 [17aa:5021]
  InstallationDate: Installed on 2019-11-04 (478 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20EH0001CD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=e96f932e-c0e2-496e-b84d-653876b6b3ea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-08-01 (206 days ago)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J5ET50WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EH0001CD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50518 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:svnLENOVO:pn20EH0001CD:pvrThinkPadE450c:rvnLENOVO:rn20EH0001CD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E450c
  dmi.product.name: 20EH0001CD
  dmi.product.sku: LENOVO_MT_20EH_BU_Think_FM_ThinkPad E450c
  dmi.product.version: ThinkPad E450c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1916763] Re: Night Light setting only working for a few seconds then It's gone

[Sebastien Bacher]

Thanks, if it's happening with a kernel update then it's a kernel
issue...

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

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

Title:
  Night Light setting only working for a few seconds then It's gone

Status in linux package in Ubuntu:
  New

Bug description:
  1. Ubuntu info is listed blow:

  ```
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  ```

  2. the `gnome-control-center` package version is
  ```
  gnome-control-center:
已安装：1:3.36.5-0ubuntu1
候选： 1:3.36.5-0ubuntu1
版本列表：
   *** 1:3.36.5-0ubuntu1 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.36.1-1ubuntu5 500
  500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 
Packages

  ```

  3. I expect when the Night Light settings are set, then it should be
  working as specified.

  4. Instead the Night Light settings only work for a few seconds, and
  then it went back to the original display state as if Night Light is
  not enabled.

  This only happens when I'm booting with kernel 5.4.0-66-generic, and
  everything works like a charm when booting with kernel
  5.4.0-65-generic.

  Please help looking into this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 24 22:43:23 2021
  DistUpgraded: 2020-08-01 23:39:12,134 DEBUG refresh of snap gtk-common-themes 
succeeded
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:5021]
 Subsystem: Lenovo Radeon R7 M260 [17aa:5021]
  InstallationDate: Installed on 2019-11-04 (478 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: LENOVO 20EH0001CD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=e96f932e-c0e2-496e-b84d-653876b6b3ea ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-08-01 (206 days ago)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J5ET50WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EH0001CD
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50518 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:svnLENOVO:pn20EH0001CD:pvrThinkPadE450c:rvnLENOVO:rn20EH0001CD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E450c
  dmi.product.name: 20EH0001CD
  dmi.product.sku: LENOVO_MT_20EH_BU_Think_FM_ThinkPad E450c
  dmi.product.version: ThinkPad E450c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1916763] [NEW] Night Light setting only working for a few seconds then It's gone

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

1. Ubuntu info is listed blow:

```
Description:Ubuntu 20.04.2 LTS
Release:20.04
```

2. the `gnome-control-center` package version is
```
gnome-control-center:
  已安装：1:3.36.5-0ubuntu1
  候选： 1:3.36.5-0ubuntu1
  版本列表：
 *** 1:3.36.5-0ubuntu1 500
500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.36.1-1ubuntu5 500
500 http://mirrors.tuna.tsinghua.edu.cn/ubuntu focal/main amd64 Packages

```

3. I expect when the Night Light settings are set, then it should be
working as specified.

4. Instead the Night Light settings only work for a few seconds, and
then it went back to the original display state as if Night Light is not
enabled.

This only happens when I'm booting with kernel 5.4.0-66-generic, and
everything works like a charm when booting with kernel 5.4.0-65-generic.

Please help looking into this.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 24 22:43:23 2021
DistUpgraded: 2020-08-01 23:39:12,134 DEBUG refresh of snap gtk-common-themes 
succeeded
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:5021]
   Subsystem: Lenovo Radeon R7 M260 [17aa:5021]
InstallationDate: Installed on 2019-11-04 (478 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 20EH0001CD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=e96f932e-c0e2-496e-b84d-653876b6b3ea ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-08-01 (206 days ago)
dmi.bios.date: 11/20/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: J5ET50WW (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EH0001CD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50518 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:svnLENOVO:pn20EH0001CD:pvrThinkPadE450c:rvnLENOVO:rn20EH0001CD:rvrSDK0E50518STD:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E450c
dmi.product.name: 20EH0001CD
dmi.product.sku: LENOVO_MT_20EH_BU_Think_FM_ThinkPad E450c
dmi.product.version: ThinkPad E450c
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal gnome-control-center ubuntu
-- 
Night Light setting only working for a few seconds then It's gone
https://bugs.launchpad.net/bugs/1916763
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8

[Chris Chiu]

According to https://bugzilla.kernel.org/show_bug.cgi?id=201251#c174,
the Skylake and Kabylake are not supported yet by SOF. From the 5.11
kernel config, seems it's still true so far.

The Dummy output is caused by the Intel SST driver, remove the
CONFIG_SND_SOC_INTEL_KBL in kernel config can get the audio input/output
device back. Seems the Intel SST driver error results in the soundcard
create failure and that's the root cause for this and #1902457.

One more thing, this SWIFT machine needs to quirk the NID 0x19 and 0x1a
to get the headset jack sensing work.

We may need to find out root cause of the soundcard create failure.


** Bug watch added: Linux Kernel Bug Tracker #201251
   https://bugzilla.kernel.org/show_bug.cgi?id=201251

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

Title:
  [Regression] Audio card [8086:9d71] not detected after upgrade from
  linux 5.4 to 5.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: 20.10 (updated from 20.04)
  Kernel: 5.8.0-41-generic #46-Ubuntu
  Manufacturer: Acer
  Product Name: Swift SF314-54
  BIOS Revision: 1.11

  Audio card: Realtek High Definition Audio
  Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD 
Audio [8086:9d71] (rev 21)

  Summary
  ===

  After upgrading from linux kernel 5.4 to 5.8, there is no more sound
  card available. However, if I select kernel 5.4 in GRUB, the sound
  card is available.

  Steps to reproduce
  ==

  1. Install 20.04 or 20.10 with a kenel 5.4
  2. Check that sound output works as excepted (Settings > Sound > Output > 
Test)
  3. Check that `alsa-info` command returns information
  4. Upgrade kernel to 5.8

  Expected results
  

  Sound output still works.

  Actual results
  ==

  2. Sound card is available, and sound can be output to the internal speakers.
  4. No more sound card detected (Sound Settings display "Dummy Output" in the 
list of output devices).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  9 14:42:00 2021
  InstallationDate: Installed on 2019-01-20 (751 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Swift SF314-54
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.release: 1.11
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.name: Strongbow_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.11
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.11
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-54
  dmi.product.sku: 
  dmi.product.version: V1.11
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1898716] Re: Please trust Canonical Livepatch Service kmod signing key

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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-groovy

** Tags added: verification-needed-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/1898716

Title:
  Please trust Canonical Livepatch Service kmod signing key

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

Bug description:
  [Impact]

   * Currently Canonical Livepatch service is signing kernel modules
  that are not trusted by the default Ubuntu kernels

   * to make Canonical Livepatch service out of the box compatible with
  SecureBoot, please add Canonical Livepatch service key as trusted in
  the kernel by default

   * if user wants to distrust the key, they can remove it via mokx,
  dbx, and we can revoke it by signing revocation with 'canonical master
  ca'.

  [Test Case]

   * Boot kernel
   * Check the built-in keyring to ensure that Livepatch key is trusted by the 
built-in keyring

  Bad:
  $ sudo keyctl list %:.builtin_trusted_keys
  1 key in keyring:
  204809401: ---lswrv 0 0 asymmetric: Build time autogenerated kernel 
key: 4182e0d0113d4a8f460783380c9e618ef1597bf5

  Good:
  $ sudo keyctl list %:.builtin_trusted_keys
  2 keys in keyring:
  637801673: ---lswrv 0 0 asymmetric: Build time autogenerated kernel 
key: 52f8757621e8fc6dd500b32c3ead885a3b6d3cbc
  1044383508: ---lswrv 0 0 asymmetric: Canonical Ltd. Live Patch 
Signing: 14df34d1a87cf37625abec039ef2bf521249b969

  [Regression Potential]

   * Kernel keyring size will increase by one key. And thus kernel image
  will too.

  [Other Info]

   * Current livepatch key fingerprints

  mokutil uses der format

  $ openssl x509 -inform der -in 
/snap/canonical-livepatch/current/keys/livepatch-kmod.x509 -noout -fingerprint 
-sha256
  SHA256 
Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA

  kernel use pem format

  $ openssl x509 -inform pem -in debian/canonical-livepatch.pem -noout 
-fingerprint -sha256
  SHA256 
Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA

  [Target kernels]

  bionic and up, across the board, but maybe excluding fips kernels?!

  [Patch]

  https://lists.ubuntu.com/archives/kernel-team/2020-October/113929.html

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

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

[Kernel-packages] [Bug 1911376] Re: [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and advertise to userspace)

[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/1911376

Title:
  [ssbs-0118] backport SSBS bug (arm64: cpufeature: Detect SSBS and
  advertise to userspace)

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-18.04 series:
  Fix Committed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The SSBS patch in 4.14 stable kernel, and mainline kernel adds snippet
  into arm64_cpufeatures but in bionic kernel, it is landed into  
arm64_elf_hwcaps.

  [Fix]
  Move SSBS snippet from arm64_elf_hwcaps back to arm64_features

  [Test]
  No known tool for SSB attack. Regression test only.

  [Regression Potential]
  Regression might be on all arm64 platforms. Regression test on all arm64 
platform we have is recommended.

  =
  [Bug Description]
  ubuntu 18.04.1 fail to enable  this SSBS function, this sys log will call 
trace as follow:

  [0.662089] Call trace:
  [0.662870]  setup_elf_hwcaps+0xb8/0xd4
  [0.664023]  setup_cpu_features+0x60/0xf8
  [0.665216]  smp_cpus_done+0x34/0xa8
  [0.666547]  smp_init+0x120/0x138
  [0.667555]  kernel_init_freeable+0xf4/0x260
  [0.668860]  kernel_init+0x18/0x110
  [0.670025]  ret_from_fork+0x10/0x18

  [Steps to Reproduce]
  1) boot this system
  2) uname -a
  Ubuntu 4.15.0-99.100-generic 4.15.18

  [Actual Results]
   boot error:
  [0.662089] Call trace:
  [0.662870]  setup_elf_hwcaps+0xb8/0xd4
  [0.664023]  setup_cpu_features+0x60/0xf8
  [0.665216]  smp_cpus_done+0x34/0xa8
  [0.666547]  smp_init+0x120/0x138
  [0.667555]  kernel_init_freeable+0xf4/0x260
  [0.668860]  kernel_init+0x18/0x110
  [0.670025]  ret_from_fork+0x10/0x18

  [Expected Results]
  no error

  [Reproducibility]
  NA

  [Additional information]
  (Firmware version, kernel version, affected hardware, etc. if required):
  arm64: cpufeature: Detect SSBS and advertise to userspace

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

  backport this following code into "static const struct
  arm64_cpu_capabilities arm64_elf_hwcaps[]" which will be error.

  1274 #ifdef CONFIG_ARM64_SSBD
  1275 {
  1276 .desc = "Speculative Store Bypassing Safe (SSBS)",
  1277 .capability = ARM64_SSBS,
  1278 .type = ARM64_CPUCAP_WEAK_LOCAL_CPU_FEATURE,
  1279 .matches = has_cpuid_feature,
  1280 .sys_reg = SYS_ID_AA64PFR1_EL1,
  1281 .field_pos = ID_AA64PFR1_SSBS_SHIFT,
  1282 .sign = FTR_UNSIGNED,
  1283 .min_field_value = ID_AA64PFR1_SSBS_PSTATE_ONLY,
  1284 .cpu_enable = cpu_enable_ssbs,
  1285 },

  [Resolution]

  Can you backport aboving code into "static const struct
  arm64_cpu_capabilities arm64_features[] = {"?

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

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

[Kernel-packages] [Bug 1909486] Re: tiocspgrp()" Privilege Escalation Vulnerability

[Nick Moffitt]

** Description changed:

- A race condition error related to the "tiocspgrp()" function
- (drivers/tty/tty_jobctrl.c) can be exploited to trigger a use-after-free
- and subsequently gain elevated privileges.
+ CVE 2020-29661 https://bugs.launchpad.net/bugs/cve/2020-29661
  
- The vulnerability is reported in versions 5.9.x prior to 5.9.14, 5.4.x
- prior to 5.4.83, 4.19.x prior to 4.19.163, 4.14.x prior to 4.14.212,
- 4.9.x prior to 4.9.248, and 4.4.x prior to 4.4.248.
- 
- Affected Software
- 
- The following software is affected by the described vulnerability.
- Please check the vendor links below to see if exactly your version is
- affected.
- 
- Linux Kernel 4.14.x
- Linux Kernel 4.19.x
- Linux Kernel 4.4.x
- Linux Kernel 4.9.x
- Linux Kernel 5.4.x
- Linux Kernel 5.9.x
- 
- Solution
- 
- Update to a fixed version.
- 
- Versions 5.9.x:
- Update to version 5.9.14 or later.
- 
- Versions 5.4.x:
- Update to version 5.4.83 or later.
- 
- Versions 4.19.x:
- Update to version 4.19.163.
- 
- Versions 4.14.x:
- Update to version 4.14.212.
- 
- Versions 4.9.x:
- Update to version 4.9.248.
- 
- Versions 4.4.x:
- Update to version 4.4.248.
- 
- References
- 
- 1. https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.9.14 

- 2. https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.83 

- 3. https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.163 

- 4. https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.212 

- 5. https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.248 

- 6. https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.4.248 

- 7. https://bugs.chromium.org/p/project-zero/issues/detail?id=2125 

- 8. 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=54ffccbf053b5b6ca4f6e45094b942fab92a25fc
 

- 
- 
- Detected in Ubuntu 16, which uses 4.4.x kernel.
+ A locking issue was discovered in the tty subsystem of the Linux kernel
+ through 5.9.13. drivers/tty/tty_jobctrl.c allows a use-after-free attack
+ against TIOCSPGRP, aka CID-54ffccbf053b.

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

Title:
  tiocspgrp()" Privilege Escalation Vulnerability

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CVE 2020-29661 https://bugs.launchpad.net/bugs/cve/2020-29661

  A locking issue was discovered in the tty subsystem of the Linux
  kernel through 5.9.13. drivers/tty/tty_jobctrl.c allows a use-after-
  free attack against TIOCSPGRP, aka CID-54ffccbf053b.

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

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

[Kernel-packages] [Bug 1902672] Re: Support Advantech UNO-420 platform

[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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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

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


** Tags added: verification-needed-focal

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

Title:
  Support Advantech UNO-420 platform

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

Bug description:
  [Impact]
  There are some drivers are required to enable Advantech UNO-420 platform.

  [Fix]
  Advantech is submitting their drivers to upstream for review, and considering 
that the patches are new drivers, it should be safe pull them back to ubuntu 
kernel.
  https://lkml.org/lkml/2021/1/18/500

  [Test]
  Verified on Advantech UNO-420 platform.

  [Where problems could occur]
  Those commits create 3 new drivers, and do not modify any existing drivers. 
Should introduce no regression.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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-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/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:
  Fix Committed
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:
  Fix Committed
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
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 1898716] Re: Please trust Canonical Livepatch Service kmod signing key

[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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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

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

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

Title:
  Please trust Canonical Livepatch Service kmod signing key

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

Bug description:
  [Impact]

   * Currently Canonical Livepatch service is signing kernel modules
  that are not trusted by the default Ubuntu kernels

   * to make Canonical Livepatch service out of the box compatible with
  SecureBoot, please add Canonical Livepatch service key as trusted in
  the kernel by default

   * if user wants to distrust the key, they can remove it via mokx,
  dbx, and we can revoke it by signing revocation with 'canonical master
  ca'.

  [Test Case]

   * Boot kernel
   * Check the built-in keyring to ensure that Livepatch key is trusted by the 
built-in keyring

  Bad:
  $ sudo keyctl list %:.builtin_trusted_keys
  1 key in keyring:
  204809401: ---lswrv 0 0 asymmetric: Build time autogenerated kernel 
key: 4182e0d0113d4a8f460783380c9e618ef1597bf5

  Good:
  $ sudo keyctl list %:.builtin_trusted_keys
  2 keys in keyring:
  637801673: ---lswrv 0 0 asymmetric: Build time autogenerated kernel 
key: 52f8757621e8fc6dd500b32c3ead885a3b6d3cbc
  1044383508: ---lswrv 0 0 asymmetric: Canonical Ltd. Live Patch 
Signing: 14df34d1a87cf37625abec039ef2bf521249b969

  [Regression Potential]

   * Kernel keyring size will increase by one key. And thus kernel image
  will too.

  [Other Info]

   * Current livepatch key fingerprints

  mokutil uses der format

  $ openssl x509 -inform der -in 
/snap/canonical-livepatch/current/keys/livepatch-kmod.x509 -noout -fingerprint 
-sha256
  SHA256 
Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA

  kernel use pem format

  $ openssl x509 -inform pem -in debian/canonical-livepatch.pem -noout 
-fingerprint -sha256
  SHA256 
Fingerprint=A4:1E:49:06:12:DD:38:56:F9:78:82:E3:66:66:9E:95:15:78:8E:65:68:50:35:46:0F:AC:59:72:4A:5B:92:FA

  [Target kernels]

  bionic and up, across the board, but maybe excluding fips kernels?!

  [Patch]

  https://lists.ubuntu.com/archives/kernel-team/2020-October/113929.html

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

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

[Kernel-packages] [Bug 1914447] Re: geneve overlay network on vlan interface broken with offload enabled

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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-groovy

** Tags added: verification-needed-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/1914447

Title:
  geneve overlay network on vlan interface broken with offload enabled

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

Bug description:
  [SRU Justification]

  Impact: In upstream v5.2 geneve tunnel stateless offload support was
  added to the mlx5 driver. This had some issue with VLANs where the
  VLAN ID was set by the driver even when offload support was enabled.

  Fix: Upstream (v5.11-rc3) commit
  378d3783412e38dc3a2b9d524f551c0008ea314a "net/mlx5e: Fix SWP offsets
  when vlan inserted by driver" was backported (dropping some code
  because it did not yet exist in 5.8) and verified to address the
  problem.

  Testcase: Enable geneve tunnel offload support on a mlx5(e) card over
  VLAN.

  Regression potential: The modified code path is sending packets tagged
  for VLAN(s), so outgoing traffic into VLAN(s) would most likely be
  impacted.

  --- original description ---

  Mellanox Connect-X 5 network card

  When using geneve overlay networks over a vlan interface, txvlan
  offload currently has to be disabled as it interferes with the network
  traffic causing general wonkyness.

  Mellanox engineering pointed us at:

    https://www.spinics.net/lists/netdev/msg711911.html

  as a likely fix for this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  3 15:34:23 2021
  ProcEnviron:
   TERM=screen-256color-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T15:17:01.792261

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

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

[Kernel-packages] [Bug 1914447] Re: geneve overlay network on vlan interface broken with offload enabled

[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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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

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

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

Title:
  geneve overlay network on vlan interface broken with offload enabled

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

Bug description:
  [SRU Justification]

  Impact: In upstream v5.2 geneve tunnel stateless offload support was
  added to the mlx5 driver. This had some issue with VLANs where the
  VLAN ID was set by the driver even when offload support was enabled.

  Fix: Upstream (v5.11-rc3) commit
  378d3783412e38dc3a2b9d524f551c0008ea314a "net/mlx5e: Fix SWP offsets
  when vlan inserted by driver" was backported (dropping some code
  because it did not yet exist in 5.8) and verified to address the
  problem.

  Testcase: Enable geneve tunnel offload support on a mlx5(e) card over
  VLAN.

  Regression potential: The modified code path is sending packets tagged
  for VLAN(s), so outgoing traffic into VLAN(s) would most likely be
  impacted.

  --- original description ---

  Mellanox Connect-X 5 network card

  When using geneve overlay networks over a vlan interface, txvlan
  offload currently has to be disabled as it interferes with the network
  traffic causing general wonkyness.

  Mellanox engineering pointed us at:

    https://www.spinics.net/lists/netdev/msg711911.html

  as a likely fix for this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-41-generic 5.8.0-41.46~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  3 15:34:23 2021
  ProcEnviron:
   TERM=screen-256color-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.logrotate.d.apport: 2021-02-03T15:17:01.792261

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

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

[Kernel-packages] [Bug 1914543] Re: Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid driver

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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-groovy

** Tags added: verification-needed-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/1914543

Title:
  Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid
  driver

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:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  In Progress
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:
  [SRU Justification]

  [Impact]

  Device sensors attached to Intel Integrated Sensor Hub (ISH) on TGL-H
  platforms are not detected due to the lack of corresponding PCI ID in
  intel-ish-hid driver.

  [Fix]

  Add PCI ID 8086:43FC the intel-ish-hid driver. Fix also proposed to
  linux-input mailing list as
  
https://patchwork.kernel.org/project/linux-input/patch/20210204083315.122952-1-vicamo.y...@canonical.com/

  [Test Case]

  On the affected platforms, sensors should be probed with this patch
  applied:

$ dmesg | grep ish
ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: 
enum_devices_done OK, num_hid_devices=3
hid-generic 001F:8087:0AC2.0003: hidraw2:  HID v2.00 Device 
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0004: hidraw3:  HID v2.00 Device 
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0005: hidraw4:  HID v2.00 Device 
[hid-ishtp 8087:0AC2] on

$ ls -1 /sys/bus/iio/devices/
iio:device0
iio:device1
trigger0
trigger1

  [Where problems could occur]

  While this would bring up sensor hub and sensors attached to this
  platform, it might affect system power consumption, and might introduce
  unexpected behavior if an unsupported/misbehaved sensor is up.

  == Original Bug Description ==

  Following PCI device not recognized by intel-ish-hid driver:

  00:12.0 Serial controller [0700]: Intel Corporation Device [8086:43fc] 
(prog-if 00 [8250])
   Subsystem: Dell Device [1028:0a66]
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-oem (not installed)
  ProcVersionSignature: Ubuntu 5.10.0-1010.11-oem 5.10.6
  Uname: Linux 5.10.0-1010-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1900 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 14:34:09 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot-14+X81
  InstallationDate: Installed on 2021-01-22 (13 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 5421
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1010-oem 
root=UUID=75317576-b181-4bb4-bdd6-b2911ff95aa2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1010-oem N/A
   linux-backports-modules-5.10.0-1010-oem  N/A
   linux-firmware   1.187.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 99.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.2.3
  dmi.board.name: 020BN6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.2.3:bd12/02/2020:br99.2:svnDellInc.:pnLatitude5421:pvr:rvnDellInc.:rn020BN6:rvrX01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5421
  dmi.product.sku: 0A66
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launch

[Kernel-packages] [Bug 1915403] Re: devlink: don't do reporter recovery if the state is healthy

[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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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

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


** Tags added: verification-needed-focal

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

Title:
  devlink: don't do reporter recovery if the state is healthy

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

Bug description:
  Hi,

  [Impact]
  Currently in focal, devices reporter recovery is enabled even if state is 
healthy.

  [fix]
  402818205c9e devlink: don't do reporter recovery if the state is healthy
  this upstream commit from kernel v5.5-rc1 which is cleanly applied on focal 
tree.
  the commit prevents reporter recovery when device in healthy state.
  when applied, issuing
  # devlink health recover pci/:05:00.0 reporter fw_fatal
  on healthy state reporter return successfully, but dmesg is clean and recover 
counter do not change.

  [test case]

  1)
  display devlink health status
  # devlink health show  pci/:05:00.0 reporter fw_fatal
  pci/:05:00.0:
    reporter fw_fatal
  state healthy error 0 recover 0 grace_period 120 auto_recover true
  2)
  perform reporter recovery using devlink,
  # devlink health recover pci/:05:00.0 reporter fw_fatal

  3)see that recovery was performed.
  # dmesg
  [776733.438708] mlx5_core :05:00.0: mlx5_health_try_recover:316:(pid 
563178): handling bad device here
  [776733.438717] mlx5_core :05:00.0: mlx5_handle_bad_state:278:(pid 
563178): Expected to see disabled
   NIC but it is full driver
  [776735.591522] mlx5_core :05:00.0: mlx5_health_try_recover:328:(pid 
563178): starting health recovery flow
  ...
  # devlink health show  pci/:05:00.0 reporter fw_fatal
  pci/:05:00.0:
    reporter fw_fatal
  state healthy error 0 recover 1 grace_period 120 auto_recover true

  [Regression Potential]
  Very small as it is a very minor change, also this patch has been tested 
internally on upstream setups for a while and no degradation has been found.
  One obvious change is that a user cannot force devlink recovery when state is 
healthy but I'm not aware of such use case.

  Thanks,
  Amir

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

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

[Kernel-packages] [Bug 1914543] Re: Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid driver

[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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.

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

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

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

Title:
  Missing device id for Intel TGL-H ISH [8086:43fc] in intel-ish-hid
  driver

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:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  In Progress
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:
  [SRU Justification]

  [Impact]

  Device sensors attached to Intel Integrated Sensor Hub (ISH) on TGL-H
  platforms are not detected due to the lack of corresponding PCI ID in
  intel-ish-hid driver.

  [Fix]

  Add PCI ID 8086:43FC the intel-ish-hid driver. Fix also proposed to
  linux-input mailing list as
  
https://patchwork.kernel.org/project/linux-input/patch/20210204083315.122952-1-vicamo.y...@canonical.com/

  [Test Case]

  On the affected platforms, sensors should be probed with this patch
  applied:

$ dmesg | grep ish
ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: 
enum_devices_done OK, num_hid_devices=3
hid-generic 001F:8087:0AC2.0003: hidraw2:  HID v2.00 Device 
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0004: hidraw3:  HID v2.00 Device 
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0005: hidraw4:  HID v2.00 Device 
[hid-ishtp 8087:0AC2] on

$ ls -1 /sys/bus/iio/devices/
iio:device0
iio:device1
trigger0
trigger1

  [Where problems could occur]

  While this would bring up sensor hub and sensors attached to this
  platform, it might affect system power consumption, and might introduce
  unexpected behavior if an unsupported/misbehaved sensor is up.

  == Original Bug Description ==

  Following PCI device not recognized by intel-ish-hid driver:

  00:12.0 Serial controller [0700]: Intel Corporation Device [8086:43fc] 
(prog-if 00 [8250])
   Subsystem: Dell Device [1028:0a66]
   Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-oem (not installed)
  ProcVersionSignature: Ubuntu 5.10.0-1010.11-oem 5.10.6
  Uname: Linux 5.10.0-1010-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1900 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  4 14:34:09 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot-14+X81
  InstallationDate: Installed on 2021-01-22 (13 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 5421
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1010-oem 
root=UUID=75317576-b181-4bb4-bdd6-b2911ff95aa2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1010-oem N/A
   linux-backports-modules-5.10.0-1010-oem  N/A
   linux-firmware   1.187.9
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2020
  dmi.bios.release: 99.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 99.2.3
  dmi.board.name: 020BN6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr99.2.3:bd12/02/2020:br99.2:svnDellInc.:pnLatitude5421:pvr:rvnDellInc.:rn020BN6:rvrX01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5421
  dmi.product.sku: 0A66
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kern

[Kernel-packages] [Bug 1915552] Re: Fix oops in skb_segment for Bionic series

[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/1915552

Title:
  Fix oops in skb_segment for Bionic series

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

Bug description:
  [Impact]
  * It was reported upstream [0] that an eBPF NAT64 filter caused an oops due 
to bad handling of GRO headers length on SKB segmentation path; the discussion 
is rich in details, and eventually the reporter sent a fix patch for that [1], 
as well as a test scenario in test_bpf kernel module that reproduces the issue.

  [0] 
https://lore.kernel.org/netdev/9265b93f-253d-6b8c-f2b8-4b54eff18...@fb.com/
  [1] https://lore.kernel.org/netdev/20180321233104.2142764-1-...@fb.com/

  * The fix patch landed on v4.17 and for some reason didn't reach the
  stable kernels; by testing our Bionic v4.15 kernel I was able to
  reproduce the issue, observing the following stack trace (details in
  the testing section below):

  kernel BUG at net/core/skbuff.c:3703!
  Modules linked in: test_bpf(E+) isofs nls_iso8859_1 dm_multipath scsi_dh_rdac 
scsi_dh_emc ...
  RIP: 0010:skb_segment+0xa34/0xce0
  [...]
  Call Trace:
   test_bpf_init.part.7+0x767/0x7d1 [test_bpf]
   test_bpf_init+0xfc/0x82f [test_bpf]
   do_one_initcall+0x52/0x19f
  [...]

  * Interesting to mention that this fix is not complete in the sense
  there was another corner case reported after that [2], which was fixed
  by another patch [3], this one released in kernel v5.3 and present in
  the stable tree (hence backported to our Bionic 4.15 kernels).

  [2] https://lore.kernel.org/netdev/20190826170724.25ff616f@pixies/
  [3] http://git.kernel.org/linus/3dcbdb134f32 ("net: gso: Fix skb_segment 
splat when splitting gso_size mangled skb having linear-headed frag_list")

  * So we are hereby backporting both the original fix patch [4] as well
  as the test_bpf patch (and a fix for it) [5] [6] for Ubuntu Bionic
  v4.15-based kernels

  [4] http://git.kernel.org/linus/13acc94eff12 ("net: permit skb_segment on 
head_frag frag_list skb")
  [5] http://git.kernel.org/linus/76db8087c4c9 ("net: bpf: add a test for 
skb_segment in test_bpf module")
  [6] http://git.kernel.org/linus/99fe29d3a25f ("test_bpf: Fix NULL vs IS_ERR() 
check in test_skb_segment()")

  [Test Case]
  * One could use a NAT64 filter, but with the aforementioned patches [5] [6] 
hereby backported, one can also use the kernel infrastructure, by loading the 
test_bpf module:

  insmod /lib/modules/$(uname -r)/kernel/lib/test_bpf.ko

  If patches [5] [6] are included and kernel doesn't contain the fix
  [4], an oops will be observed.

  [Where problems could occur]
  * The backported patches are present upstream since v4.17, and no fixes were 
released for them (other than [6], included here), so from the testing 
point-of-view, these patches are being exercised for a while with no issues.

  * That said, if a problem would be triggered by these patches,
  hypothetically it would affect SKB segmentation, the net/core code - a
  bad check could case an oops in this code or they could present a
  pretty small overhead due to more checks in the hot path.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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-groovy

-- 
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:
  Fix Released
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 Committed
Status in linux source package in Hirsute:
  Fix Released

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 1907160] Re: intel-hid is not loaded on new Intel platform

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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

Title:
  intel-hid is not loaded on new Intel platform

Status in linux package in Ubuntu:
  Fix Released
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

Bug description:
  [Impact]

   intel-hid is not loaded on Intel Tiger Lake and Rocket Lake platforms 
because the existing
   hardware ids "INT33D5" aren't used in BIOS.

  [Fix]

   New ids "INTC1051" and "INTC1054" are to be added to intel-hid kernel
  driver.

  [Test Case]

   This was tested on a Rocket Lake platform and intel-hid was loaded
  correctly as kernel log below:

   [ 2.938964] input: Intel HID 5 button array as
  /devices/platform/INT1054:00/input/input11

  [Where problems could occur]

   None.

   New IDs were added for new platforms. Previous platforms will not be
  affected.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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-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/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:
  Fix Released
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:
  Fix Committed
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 1913263] Re: Remove scary stack trace from Realtek WiFi driver

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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

Title:
  Remove scary stack trace from Realtek WiFi driver

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

Bug description:
  [Impact]
  Scary stack trace spamming by Realtek WiFi driver.

  [Fix]
  The issue is actually harmless, so replace the WARN macro with dbg
  macro.

  [Test]
  No more scary stack trace in dmesg after applying the patch.

  [Where problems could occur]
  This patch doesn't bring any behavior change, so there won't be any
  regression risk.

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

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

[Kernel-packages] [Bug 1913520] Re: Restore palm ejection on multi-input devices

[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-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.

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

Title:
  Restore palm ejection on multi-input devices

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

Bug description:
  [Impact]
  Palm ejection stops working on Elan and Synaptics touchpads with
  pointstick.

  [Fix]
  Re-apply "confidence" quirk on those devices.

  [Test]
  Move the palm on touchpad, cursor moves too.
  With the fix applied, moving palm on touchpad won't move the cursor and
  won't generate click events.

  [Where problems could occur]
  Not that I can think of. Originally these touchpads are working fine
  with palm ejection, it's just overlooked when enabling pointsticks.

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

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

[Kernel-packages] [Bug 1916570] Re: BlueZ 5.56 release

[Sebastien Bacher]

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

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

Title:
  BlueZ 5.56 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ 5.56 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

  ver 5.56:
  Fix issue with setting AVDTP disconnect timer.
  Fix issue with AVDTP not sending GetCapabilities.
  Fix issue with AVDTP connecting using streaming mode.
  Fix issue with handling A2DP and remote SEP disappearing.
  Fix issue with handling session of A2DP channels.
  Fix issue with GATT and handling device removal.
  Fix issue with GATT not accepting multiple requests.
  Fix issue with HID report value callback registration.
  Add support for new advertising management command.
  Add support for battery D-Bus interface.

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

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

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

[Coiby Xu]

Hi Marton,

On Tue, Feb 23, 2021 at 05:00:30PM -, Marton Danko wrote:
>Hi Coiby,
>
>Did you find anything about why it still doesn't work properly on my
>machine?
>

Your GPIO pin register value for the touchpad is 0x51b00 which means the
root cause has been fixed. I've less certain about the evest result but
I don't find something suspicious when comparing it with my laptop. Can
you create another user and check if the problem still occurs after 
logging in?

-- 
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:
  Fix Released
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...

[Kernel-packages] [Bug 1916570] Re: BlueZ 5.56 release

[Sebastien Bacher]

Those packaging cleanups wouldn't do any difference in practice, we are
a bit late in the cycle now to waste time on that but we should merge
next cycle

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

Title:
  BlueZ 5.56 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ 5.56 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

  ver 5.56:
  Fix issue with setting AVDTP disconnect timer.
  Fix issue with AVDTP not sending GetCapabilities.
  Fix issue with AVDTP connecting using streaming mode.
  Fix issue with handling A2DP and remote SEP disappearing.
  Fix issue with handling session of A2DP channels.
  Fix issue with GATT and handling device removal.
  Fix issue with GATT not accepting multiple requests.
  Fix issue with HID report value callback registration.
  Add support for new advertising management command.
  Add support for battery D-Bus interface.

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

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

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Alberto Milone]

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1873325] Re: update-initramfs complains of missing amdgpu firmware files

[Christian Sarrasin]

Having just upgraded from Focal (w/ original 5.4 kernel) to Groovy
(5.8.0-44), this issue definitely seems to have regressed.

Does it require a new bug since this one is tagged "Focal"?  That said
one of the above reports also claims that it affects the Focal 5.8
series.  Could someone advise?  Very happy to raise a new bug and link
to this one if this is the right approach.

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

Title:
  update-initramfs complains of missing amdgpu firmware files

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

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

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

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

[Kernel-packages] [Bug 1912789] Re: Add support for selective build of special drivers

[Stefan Bader]

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

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

Title:
  Add support for selective build of special drivers

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

Bug description:
  [SRU Justification]

  = Impact =

  We want to add some driver code which exists in the primary kernel
  source but will not get included unless specifically asked for. As
  long as there are no drivers using this, there is no user-visible
  change.

  = Impact =

  This will be done by adding a new config option which gets turned on
  via build setup rules. The default will be off.

  = Testcase =

  As long as there are no consumers changes can only be seen by
  inspecting the build logs (if even that).

  = Regression Potential =

  This prepares for future consumers. At this stage either the build
  will fail completely or pass and in that case the produced kernel
  binaries are the same as they were before.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joe Zhou]

Works fine after installing hwe kernel using apt.(5.8.0.44 Ubuntu 20.04
Lenovo R7000P)

-- 
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:
  Fix Released
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, 

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2021-02-24 05:17 EDT---
IBM Bugzilla status->closed, Fix Released for all requested distros

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

Title:
  NULL pointer dereference when configuring multi-function with devfn !=
  0 before devfn == 0

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * While handling multifunction devices in zPCI the UID of the PCI
  function with function number 0 (that always exists according to the
  PCI spec) is taken as domain number.

  * Therefore if hot plugging functions with a function number larger
  than 0 are used before function 0, these need to be held in standby
  before creating the domain and bus.

  * This has been tested during development of this feature using a
  patched QEMU and in DPM, but unfortunately never in
  classic/traditional HMC mode.

  * On a classic/traditional mode machine with a multi-function device,
  and hot plug ("Reassign I/O Path") of the FID of the second port of
  the LPAR, any additional hotplug (and even just deconfiguring a PCI
  device) will hang - and hotplug now makes the entire Linux instance
  unresponsive.

  * The reason for this is a NULL pointer dereference - inc case
  configuring multi-function with devfn != 0 before devfn == 0.

  * This issue was introduced with the topology-aware PCI enumeration
  code.

  [Fix]

  * 0b2ca2c7d0c9e2731d01b6c862375d44a7e13923 0b2ca2c7d0c9 "s390/pci: fix
  hot-plug of PCI function missing bus"

  [Test Case]

  * IBM Z or LinuxONE hardware, equipped with hot-pluggable, multi-
  functional PCIe cards (like for example RoCE Express 2 adapters) in
  classic/traditional mode.

  * An Ubuntu OS running in LPAR, that comes with a kernel that includes
  the topology-aware PCI enumeration code (like for example 20.04.1 w/o
  further updates or 20.10 GA kernel).

  * Now on a system that is in classic/traditional mode, hot plug
  ("Reassign I/O Path") a multi-function device, but using the FID of
  the second port.

  [Regression Potential]

  * There is at least some regression risk, but I consider it as low,
  because:

  * Even is the modification is a single if statement (that spans two
  lines) in 'zpci_event_availability' it could harm the zPCI event
  management even more, in worst case it could break hot plug not only
  for systems in classic/traditional mode, but also in DPM mode (and
  making the system hang) or for all ports.

  * In such a case no enabling / disabling of devices would be possible.

  * But the fix is very simple and straight-forward, it checks
  zdev->zbus->bus for being NULL and in such a case break the function -
  means breaking instead of calling the PCI common code
  pci_scan_single_device() with the NULL pointer.

  * PCIe devices are usually more optional devices on s390x (compared to
  CCW and OSA devices for network) and this affects the zPCI subsystem
  only, which is unique to s390x.

  [Other]

  * The patch got upstream accepted with kernel v5.10-rc3, hence it will
  land sooner or later in Hirsute.

  * It was initially planned to address groovy via 5.8 upstream stable
  update, and in fact the patch was already marked for this, but it
  didn't made it because 5.8 reached it's EOL already.

  * Hence in addition to the already submitted SRU for focal, this is now a 
separate SRU for groovy.
  __

  Background:

  When handling multifunction devices in zPCI we take the
  UID of the PCI function with function number 0
  (that always exists according to the PCI spec)
  as domain number.
  Therefore when hot plugging functions with function
  number larger than 0 before function 0, we need
  to hold these in standby before creating the
  domain and bus.

  This has been tested during feature development
  using a patched QEMU and with DPM but never in Classic
  Mode.

  Reproduction:

  This issue was introduced with the Topology aware PCI
  Enumeration code so test with a Linux supporting
  that feature. E.g. Upstream, Devel Driver etc.

  On a Classic Mode machine with a multi-function device,
  hot plug ("Reassign I/O Path") only the FID of the
  second port to the LPAR.

  Symptom:

  After this any additional hotplug and even just
  deconfiguring a PCI device will hang. A hotplug
  makes the entire Linux instance unresponsive.

  Analysis:

  The problem occurs in Classic Mode but not with
  previous testing as the LPAR hypervisor does
  hot plug/Reassign I/O Path as a two step process:

  1. zPCI event with PEC 0x0302 to plug the zPCI function in Standby
  2. zPCI event with PEC 0x0301 

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Alberto Milone]

** Tags removed: block-proposed-bionic block-proposed-focal block-
proposed-groovy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1907265] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2021-02-24 05:15 EDT---
IBM Bugzilla status->closed, Fix Released for all requested distros

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

Title:
  [UBUNTU 21.04] s390/pci: vfio-pci mmio being disabled erroneously

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

Bug description:
  Description:   s390/pci: vfio-pci mmio being disabled erroneously
  Symptom:   PCI virtual functions passed through via vfio-pci are unusable 
 
  Problem:   The fix for CVE-2020-12888 'abafbc551fdd vfio-pci: Invalidate
 mmaps and block MMIO access on disabled memory' introduced an
 issue which prevented PCI Virtual Functions from being passed-
 through via vfio-pci as VFs are not allowed to have the
 PCI_COMMAND_MEMORY bit enabled per spec.  This issue was
 initially thought to be fixed via 'ebfa440ce38b vfio/pci: Fix
 SR-IOV VF handling with MMIO blocking' which removes the
 PCI_COMMAND_MEMORY requirement for VFs but this did not solve
 the issue for virtual functions on s390 that are first passed
 through to an LPAR without their associated physical function
 as they are not identified as VFs in the traditional sense
 (there is no PF available to the host kernel to link to).  As a
 result, when passing these devices through to a guest via
 vfio-pci, these devices do not trigger the check added by
 ebfa440ce38b which results in MMIO access from the guest being
 blocked because the PCI_COMMAND_MEMORY bit is off.
  Solution:  Identify devices beyond traditional linked VFs that vfio must
 consider memory-enabled. 
  Reproduction:  Pass a PCI Virtual Function to a qemu-kvm guest via vfio-pci
  Upstream-ID:   12856e7acde4702b7c3238c15fcba86ff6aa507f
 08b6e22b850c28b6032da1e4d767a33116e23dfb
 515ecd5368f1510152fa4f9b9ce55b66ac56c334

  These patches need to be applied for 20.10 and 20.04.
  The git-commits will apply cleanly on the dedicated kernels.

  Manx thx

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

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

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

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2021-02-24 05:16 EDT---
IBM Bugzilla status->closed, Fix Released for all requested distros

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

Title:
  [UBUNTU 20.10] Applications runing in QEMU/KVM get translation faults

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  SRU Justification:
  ==

  [Impact]

  * The commit 0b0ed657fe "s390: remove critical section cleanup from
  entry.S" was introduced in kernel 5.8, but instigated a problem where
  FPU registers were not properly restored when entering the SIE (start
  interpretive execution) instruction.

  * This leads to crashes of applications runnning inside KVM, as most
  of the programs in use nowdays are using FPU registers for backing of
  general register content.

  * To fix this interrupts in load_fpu_regs() need to be disabled -
  otherwise an interrupt might come in after the registers are loaded,
  but before CIF_FPU is cleared in load_fpu_regs().

  * When the interrupt returns, CIF_FPU will be cleared and the
  registers will never be restored.

  [Fix]

  * 1179f170b6f0af7bb0b3b7628136eaac450ddf31 1179f170b6f0 "s390: fix fpu
  restore in entry.S"

  [Test Case]

  * IBM Z or LinuxONE hardware with Ubuntu Server 20.10 installed.

  * A KVM host needs to be setup as well as an KVM guest (use again
  20.10).

  * Run (ideally context switching) workload that makes use of FP
  instructions inside of the KVM guest.

  * Monitor the health of the guest for crashes (logs).

  [Regression Potential]

  * Even if the code changes are quite overseeable, there is still a
  certain risk for regression, because:

  * the modifications affect a critical part of the kernel
  (arch/s390/kernel/entry.S)

  * affect the handling of the FPU registers

  * and are always in use if KVM guests run

  * So in worst case the changes may have an even bigger impact on FPU
  workloads in KVM guests

  * and may not only crash in case of FPU usage, but also KVM in
  general.

  * But the code is peurly s390x specific, hence affects IBM Z only,

  * and it got already upstream accepted with v5.10-rc6

  * and a test kernel (based on groovy master-next) was build for
  further testing.

  [Other]

  * The patch got upstream accepted with kernel v5.10-rc6, hence it will
  land sooner or later in Hirsute.

  * It was initially planned to address groovy via 5.8 upstream stable
  update, and in fact the patch was already marked for this, but it
  didn't made it because 5.8 already reached it's EOL.

  * Hence this SRU is submitted for groovy only.

  __

  commit 0b0ed657fe ("s390: remove critical section cleanup from
  entry.S") introduced a problem where FPU registers were not properly
  restored when entering SIE. This leads to crashes of applications
  runnning inside kvm, as most of the programs in use nowdays are using
  FPU registers for backing of general register content.

  Fix is upstream:
  authorSven Schnelle  2020-11-20 14:17:52 
+0100
  committer Heiko Carstens  2020-11-23 11:52:13 
+0100
  commit1179f170b6f0af7bb0b3b7628136eaac450ddf31 (patch)
  tree  19e8acb64e0968b41de4899cc1315c41b002839e /arch/s390/kernel/entry.S
  parent78d732e1f326f74f240d416af9484928303d9951 (diff)
  download  linux-1179f170b6f0af7bb0b3b7628136eaac450ddf31.tar.gz
  s390: fix fpu restore in entry.S
  We need to disable interrupts in load_fpu_regs(). Otherwise an
  interrupt might come in after the registers are loaded, but before
  CIF_FPU is cleared in load_fpu_regs(). When the interrupt returns,
  CIF_FPU will be cleared and the registers will never be restored.

  The entry.S code usually saves the interrupt state in __SF_EMPTY on the
  stack when disabling/restoring interrupts. sie64a however saves the pointer
  to the sie control block in __SF_SIE_CONTROL, which references the same
  location.  This is non-obvious to the reader. To avoid thrashing the sie
  control block pointer in load_fpu_regs(), move the __SIE_* offsets eight
  bytes after __SF_EMPTY on the stack.

  Cc:  # 5.8
  Fixes: 0b0ed657fe00 ("s390: remove critical section cleanup from entry.S")
  Reported-by: Pierre Morel 
  Signed-off-by: Sven Schnelle 
  Acked-by: Christian Borntraeger 
  Reviewed-by: Heiko Carstens 
  Signed-off-by: Heiko Carstens 

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

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

[Kernel-packages] [Bug 1916731] Re: [SRU][F/G/H] add AMD GPU green sardine firmware

[AaronMa]

** Summary changed:

- [SRU][F/G/H] add AMD GPU green sardine firmwares
+ [SRU][F/G/H] add AMD GPU green sardine firmware

** Description changed:

  SRU justification:
  
  [Impact]
- Add new firmwares of AMD GPU green sardine.
+ AMD new gpu can not work without proper firmware.
  
  [Fix]
+ Add new firmwares of AMD GPU green sardine.
  Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new 
hardware.
  
  [Test]
  Verified on hardware with 5.10 kernel. no errors after benchmark and stress 
test.
  
  [Where problems could occur]
  Introducs the new firmwares to enable support on new GPU.
  GFX can be failed if it is wrong.

** Description changed:

  SRU justification:
  
  [Impact]
  AMD new gpu can not work without proper firmware.
  
  [Fix]
  Add new firmwares of AMD GPU green sardine.
  Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new 
hardware.
  
  [Test]
  Verified on hardware with 5.10 kernel. no errors after benchmark and stress 
test.
  
  [Where problems could occur]
- Introducs the new firmwares to enable support on new GPU.
+ Introducs the new firmware to enable support on new GPU.
  GFX can be failed if it is wrong.

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

Title:
  [SRU][F/G/H] add AMD GPU green sardine firmware

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware source package in Groovy:
  New
Status in linux-firmware source package in Hirsute:
  New

Bug description:
  SRU justification:

  [Impact]
  AMD new gpu can not work without proper firmware.

  [Fix]
  Add new firmwares of AMD GPU green sardine.
  Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new 
hardware.

  [Test]
  Verified on hardware with 5.10 kernel. no errors after benchmark and stress 
test.

  [Where problems could occur]
  Introducs the new firmware to enable support on new GPU.
  GFX can be failed if it is wrong.

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

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

[Kernel-packages] [Bug 1916731] Re: [SRU][F/G/H] add AMD GPU green sardine firmwares

[AaronMa]

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

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

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

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

Title:
  [SRU][F/G/H] add AMD GPU green sardine firmware

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware source package in Groovy:
  New
Status in linux-firmware source package in Hirsute:
  New

Bug description:
  SRU justification:

  [Impact]
  AMD new gpu can not work without proper firmware.

  [Fix]
  Add new firmwares of AMD GPU green sardine.
  Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new 
hardware.

  [Test]
  Verified on hardware with 5.10 kernel. no errors after benchmark and stress 
test.

  [Where problems could occur]
  Introducs the new firmware to enable support on new GPU.
  GFX can be failed if it is wrong.

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

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

[Kernel-packages] [Bug 1902577] Re: TGL system automatically resumes from s2idle when connecting to a docking station with a monitor

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.10: 5.10.0-1014.15 -proposed tracker (LP:
#1913154)

  * Fix  no screen show on display after S3 on CML-R (LP: #1913682)
- SAUCE: drm/i915/gen9bc: Handle TGP PCH during suspend/resume

  * RKL: backport a few fixes from v5.11 (LP: #1914412)
- drm/i915/display/fbc: Implement WA 22010751166
- drm/i915/rkl: Add new cdclk table
- drm/i915: Rename FORCEWAKE_BLITTER to FORCEWAKE_GT
- drm/i915: Update gen12 forcewake table
- drm/i915: Update gen12 multicast register ranges

  * TGL system automatically resumes from s2idle when connecting to a docking
station with a monitor (LP: #1902577)
- SAUCE: ACPI: avoid auto-wakeup with an _OSI string

  * Thinkpad - add palm sensor support needed for WWAN (LP: #1912033)
- platform/x86: thinkpad_acpi: Add palm sensor support
- platform/x86: thinkpad_acpi: correct palmsensor error checking

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs following v5.10.11 import

  [ Ubuntu: 5.10.0-14.15 ]

  * hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
  * Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices
  * intel-hid is not loaded on new Intel platform (LP: #1907160)
- platform/x86: intel-hid: add Rocket Lake ACPI device ID
  * Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
- scsi: target: tcmu: Fix use-after-free of se_cmd->priv
- mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
- mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC 
engine
- i2c: tegra: Wait for config load atomically while in ISR
- i2c: bpmp-tegra: Ignore unknown I2C_M flags
- platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
- ALSA: hda/via: Add minimum mute flag
- crypto: xor - Fix divide error in do_xor_speed()
- dm crypt: fix copy and paste bug in crypt_alloc_req_aead
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- btrfs: don't get an EINTR during drop_snapshot for reloc
- btrfs: do not double free backref nodes on error
- btrfs: fix lockdep splat in btrfs_recover_relocation
- btrfs: don't clear ret in btrfs_start_dirty_block_groups
- btrfs: send: fix invalid clone operations when cloning from the same file
  and root
- fs: fix lazytime expiration handling in __writeback_single_inode()
- pinctrl: ingenic: Fix JZ4760 support
- mmc: core: don't initialize block size from ext_csd if not present
- mmc: sdhci-of-dwcmshc: fix rpmb access
- mmc: sdhci-xenon: fix 1.8v regulator stabilization
- mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
- dm: avoid filesystem lookup in dm_get_dev_t()
- dm integrity: fix a crash if "recalculate" used without "internal_hash"
- dm integrity: conditionally disable "recalculate" feature
- drm/atomic: put state on error path
- drm/syncobj: Fix use-after-free
- drm/amdgpu: remove gpu info firmware of green sardine
- drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
- drm/i915/gt: Prevent use of engine->wa_ctx after error
- drm/i915: Check for rq->hwsp validity after acquiring RCU lock
- ASoC: Intel: haswell: Add missing pm_ops
- ASoC: rt711: mutex between calibration and power state changes
- SUNRPC: Handle TCP socket sends with kernel_sendpage() again
- HID: sony: select CONFIG_CRC32
- dm integrity: select CRYPTO_SKCIPHER
- x86/hyperv: Fix kexec panic/hang issues
- scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- scsi: qedi: Correct max length of CHAP secret
- scsi: scsi_debug: Fix memleak in scsi_debug_init()
- scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
- riscv: Fix kernel time_init()
- riscv: Fix sifive serial driver
- riscv: Enable interrupts during syscalls with M-Mode
- HID: logitech-dj: add the G602 receiver
- HID: Ignore battery for Elan touchscreen on ASUS UX550
- clk: tegra30: Add hda clock default rates to clock driver
- ALSA: hda/tegra: fix tegra-hda on tegra30 soc
- riscv: cacheinfo: Fix using smp_processor_id() in preemptible
- arm64: make atomic helpers __always_inline
- xen: Fix event channel callback via INTX/GSI
- x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
- x86/xen: Fix xen_hvm_smp_init() when vector callback not available
- dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
- dts: phy: add GPIO number

[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1048.52

---
linux-oem-5.6 (5.6.0-1048.52) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1048.52 -proposed tracker (LP: #1913153)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test
result (LP: #1908499)
- selftests: fix the return value for UDP GRO test

  * CVE-2020-27815
- jfs: Fix array index bounds check in dbAdjTree

  * CVE-2020-25704
- perf/core: Fix a memory leak in perf_event_parse_addr_filter()

  * CVE-2020-25643
- hdlc_ppp: add range checks in ppp_cp_parse_cr()

  * CVE-2020-25641
- block: allow for_each_bvec to support zero len bvec

  * CVE-2020-25284
- rbd: require global CAP_SYS_ADMIN for mapping and unmapping

  * CVE-2020-25212
- nfs: Fix getxattr kernel panic and memory overflow

  * CVE-2020-28588
- lib/syscall: fix syscall registers retrieval on 32-bit platforms

  * CVE-2020-29371
- romfs: fix uninitialized memory leak in romfs_dev_read()

  * CVE-2020-29369
- mm/mmap.c: close race between munmap() and expand_upwards()/downwards()

  * CVE-2020-29368
- mm: thp: make the THP mapcount atomic against __split_huge_pmd_locked()

  * CVE-2020-29660
- tty: Fix ->session locking

  * CVE-2020-29661
- tty: Fix ->pgrp locking in tiocspgrp()

  * CVE-2020-35508
- fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent

  * CVE-2020-24490
- Bluetooth: fix kernel oops in store_pending_adv_report

  * CVE-2020-14314
- ext4: fix potential negative array index in do_split()

  * CVE-2020-10135
- Bluetooth: Consolidate encryption handling in hci_encrypt_cfm
- Bluetooth: Disconnect if E0 is used for Level 4

  * CVE-2020-27152
- KVM: ioapic: break infinite recursion on lazy EOI

  * CVE-2020-28915
- fbdev, newport_con: Move FONT_EXTRA_WORDS macros into linux/font.h
- Fonts: Support FONT_EXTRA_WORDS macros for built-in fonts

  * CVE-2020-15437
- serial: 8250: fix null-ptr-deref in serial8250_start_tx()

  * CVE-2020-15436
- block: Fix use-after-free in blkdev_get()

  * switch to an autogenerated nvidia series based core via dkms-versions
(LP: #1912803)
- [Config] dkms-versions -- add transitional/skip information for nvidia
  packages
- [Packaging] nvidia -- use dkms-versions to define versions built
- [Packaging] update-version-dkms -- maintain flags fields

  * S3 stress test fails with amdgpu errors (LP: #1909453)
- drm/amdgpu: asd function needs to be unloaded in suspend phase
- drm/amdgpu: add TMR destory function for psp

 -- Timo Aaltonen   Thu, 18 Feb 2021
13:11:14 +0200

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

Title:
  udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting
  sub-test result

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
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:
  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:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  In udpgro.sh, the exit value is 0 even if there are some failed sub
  test cases:

  $ sudo ./udpgro.sh
  ipv4
   no GRO
  BTF debug data section '.BTF' rejected: Invalid argument (22)!
   - Length: 568
  Verifier analysis:

  magic: 0xeb9f
  version: 1
  flags: 0x0
  hdr_len: 24
  type_off: 0
  type_len: 256
  str_off: 256
  str_len: 288
  btf_total_size: 568
  [1] PTR (anon) type_id=2
  [2] STRUCT xdp_md size=20 vlen=5
   data type_id=3 bits_offset=0
   data_end type_id=3 bits_offset=32
   data_meta type_id=3 bits_offset=64
   ingress_ifindex type_id=3 bits_offset=96
   rx_queue_index type_id=3 bits_offset=128
  [3] TYPEDEF __u32 type_id=4
  [4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
  [5] FUNC_PROTO (anon) return=6 args=(1 ctx)
  [6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
  [7] FUNC xdp_dummy_prog type_id=5
  [8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
  [9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
  [10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
  [11] VAR _license type_id=9 linkage=1
  [12] DATASEC license size=0 vlen=1 size == 0

  ./udpgso_bench_rx: poll: 0x0 expected 0x1

  failed
  ./udpgso_bench_tx: write: Connection refused

  ...

   multiple GRO socks
  BTF debug data section '.BTF' rejected: Invalid argument (22)!
   - Length: 568
  Verifier analysis:

  magic: 0xeb9f
  version: 1
  flags: 0x0
  hdr_len: 24
  type_of

[Kernel-packages] [Bug 1908499] Re: udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test result

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.10: 5.10.0-1014.15 -proposed tracker (LP:
#1913154)

  * Fix  no screen show on display after S3 on CML-R (LP: #1913682)
- SAUCE: drm/i915/gen9bc: Handle TGP PCH during suspend/resume

  * RKL: backport a few fixes from v5.11 (LP: #1914412)
- drm/i915/display/fbc: Implement WA 22010751166
- drm/i915/rkl: Add new cdclk table
- drm/i915: Rename FORCEWAKE_BLITTER to FORCEWAKE_GT
- drm/i915: Update gen12 forcewake table
- drm/i915: Update gen12 multicast register ranges

  * TGL system automatically resumes from s2idle when connecting to a docking
station with a monitor (LP: #1902577)
- SAUCE: ACPI: avoid auto-wakeup with an _OSI string

  * Thinkpad - add palm sensor support needed for WWAN (LP: #1912033)
- platform/x86: thinkpad_acpi: Add palm sensor support
- platform/x86: thinkpad_acpi: correct palmsensor error checking

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs following v5.10.11 import

  [ Ubuntu: 5.10.0-14.15 ]

  * hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
  * Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices
  * intel-hid is not loaded on new Intel platform (LP: #1907160)
- platform/x86: intel-hid: add Rocket Lake ACPI device ID
  * Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
- scsi: target: tcmu: Fix use-after-free of se_cmd->priv
- mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
- mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC 
engine
- i2c: tegra: Wait for config load atomically while in ISR
- i2c: bpmp-tegra: Ignore unknown I2C_M flags
- platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
- ALSA: hda/via: Add minimum mute flag
- crypto: xor - Fix divide error in do_xor_speed()
- dm crypt: fix copy and paste bug in crypt_alloc_req_aead
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- btrfs: don't get an EINTR during drop_snapshot for reloc
- btrfs: do not double free backref nodes on error
- btrfs: fix lockdep splat in btrfs_recover_relocation
- btrfs: don't clear ret in btrfs_start_dirty_block_groups
- btrfs: send: fix invalid clone operations when cloning from the same file
  and root
- fs: fix lazytime expiration handling in __writeback_single_inode()
- pinctrl: ingenic: Fix JZ4760 support
- mmc: core: don't initialize block size from ext_csd if not present
- mmc: sdhci-of-dwcmshc: fix rpmb access
- mmc: sdhci-xenon: fix 1.8v regulator stabilization
- mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
- dm: avoid filesystem lookup in dm_get_dev_t()
- dm integrity: fix a crash if "recalculate" used without "internal_hash"
- dm integrity: conditionally disable "recalculate" feature
- drm/atomic: put state on error path
- drm/syncobj: Fix use-after-free
- drm/amdgpu: remove gpu info firmware of green sardine
- drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
- drm/i915/gt: Prevent use of engine->wa_ctx after error
- drm/i915: Check for rq->hwsp validity after acquiring RCU lock
- ASoC: Intel: haswell: Add missing pm_ops
- ASoC: rt711: mutex between calibration and power state changes
- SUNRPC: Handle TCP socket sends with kernel_sendpage() again
- HID: sony: select CONFIG_CRC32
- dm integrity: select CRYPTO_SKCIPHER
- x86/hyperv: Fix kexec panic/hang issues
- scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- scsi: qedi: Correct max length of CHAP secret
- scsi: scsi_debug: Fix memleak in scsi_debug_init()
- scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
- riscv: Fix kernel time_init()
- riscv: Fix sifive serial driver
- riscv: Enable interrupts during syscalls with M-Mode
- HID: logitech-dj: add the G602 receiver
- HID: Ignore battery for Elan touchscreen on ASUS UX550
- clk: tegra30: Add hda clock default rates to clock driver
- ALSA: hda/tegra: fix tegra-hda on tegra30 soc
- riscv: cacheinfo: Fix using smp_processor_id() in preemptible
- arm64: make atomic helpers __always_inline
- xen: Fix event channel callback via INTX/GSI
- x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
- x86/xen: Fix xen_hvm_smp_init() when vector callback not available
- dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
- dts: phy: add GPIO number

[Kernel-packages] [Bug 1909453] Re: S3 stress test fails with amdgpu errors

[Launchpad Bug Tracker]

This bug was fixed in the package linux-oem-5.6 - 5.6.0-1048.52

---
linux-oem-5.6 (5.6.0-1048.52) focal; urgency=medium

  * focal/linux-oem-5.6: 5.6.0-1048.52 -proposed tracker (LP: #1913153)

  * Packaging resync (LP: #1786013)
- update dkms package versions

  * udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test
result (LP: #1908499)
- selftests: fix the return value for UDP GRO test

  * CVE-2020-27815
- jfs: Fix array index bounds check in dbAdjTree

  * CVE-2020-25704
- perf/core: Fix a memory leak in perf_event_parse_addr_filter()

  * CVE-2020-25643
- hdlc_ppp: add range checks in ppp_cp_parse_cr()

  * CVE-2020-25641
- block: allow for_each_bvec to support zero len bvec

  * CVE-2020-25284
- rbd: require global CAP_SYS_ADMIN for mapping and unmapping

  * CVE-2020-25212
- nfs: Fix getxattr kernel panic and memory overflow

  * CVE-2020-28588
- lib/syscall: fix syscall registers retrieval on 32-bit platforms

  * CVE-2020-29371
- romfs: fix uninitialized memory leak in romfs_dev_read()

  * CVE-2020-29369
- mm/mmap.c: close race between munmap() and expand_upwards()/downwards()

  * CVE-2020-29368
- mm: thp: make the THP mapcount atomic against __split_huge_pmd_locked()

  * CVE-2020-29660
- tty: Fix ->session locking

  * CVE-2020-29661
- tty: Fix ->pgrp locking in tiocspgrp()

  * CVE-2020-35508
- fork: fix copy_process(CLONE_PARENT) race with the exiting ->real_parent

  * CVE-2020-24490
- Bluetooth: fix kernel oops in store_pending_adv_report

  * CVE-2020-14314
- ext4: fix potential negative array index in do_split()

  * CVE-2020-10135
- Bluetooth: Consolidate encryption handling in hci_encrypt_cfm
- Bluetooth: Disconnect if E0 is used for Level 4

  * CVE-2020-27152
- KVM: ioapic: break infinite recursion on lazy EOI

  * CVE-2020-28915
- fbdev, newport_con: Move FONT_EXTRA_WORDS macros into linux/font.h
- Fonts: Support FONT_EXTRA_WORDS macros for built-in fonts

  * CVE-2020-15437
- serial: 8250: fix null-ptr-deref in serial8250_start_tx()

  * CVE-2020-15436
- block: Fix use-after-free in blkdev_get()

  * switch to an autogenerated nvidia series based core via dkms-versions
(LP: #1912803)
- [Config] dkms-versions -- add transitional/skip information for nvidia
  packages
- [Packaging] nvidia -- use dkms-versions to define versions built
- [Packaging] update-version-dkms -- maintain flags fields

  * S3 stress test fails with amdgpu errors (LP: #1909453)
- drm/amdgpu: asd function needs to be unloaded in suspend phase
- drm/amdgpu: add TMR destory function for psp

 -- Timo Aaltonen   Thu, 18 Feb 2021
13:11:14 +0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-10135

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-14314

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-15436

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-15437

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-24490

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25212

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25284

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25641

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25643

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25704

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-27152

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-27815

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28588

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28915

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-29368

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-29369

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-29371

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-29660

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-29661

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-35508

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

Title:
  S3 stress test fails with amdgpu errors

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

Bug description:
  [Impact]
  It fails to resume from S3 with below error messages
 Nov 17 03:15:27 u kernel: amdgpu :04:00.0:[drm:amdgpu_ring_test_helper 
[amdgpu]] ERROR ring vcn_dec test failed (-110)
 Nov 17 03:15:27 u kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] 
ERROR resume of IP block  failed -110
 No

[Kernel-packages] [Bug 1912033] Re: Thinkpad - add palm sensor support needed for WWAN

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.10: 5.10.0-1014.15 -proposed tracker (LP:
#1913154)

  * Fix  no screen show on display after S3 on CML-R (LP: #1913682)
- SAUCE: drm/i915/gen9bc: Handle TGP PCH during suspend/resume

  * RKL: backport a few fixes from v5.11 (LP: #1914412)
- drm/i915/display/fbc: Implement WA 22010751166
- drm/i915/rkl: Add new cdclk table
- drm/i915: Rename FORCEWAKE_BLITTER to FORCEWAKE_GT
- drm/i915: Update gen12 forcewake table
- drm/i915: Update gen12 multicast register ranges

  * TGL system automatically resumes from s2idle when connecting to a docking
station with a monitor (LP: #1902577)
- SAUCE: ACPI: avoid auto-wakeup with an _OSI string

  * Thinkpad - add palm sensor support needed for WWAN (LP: #1912033)
- platform/x86: thinkpad_acpi: Add palm sensor support
- platform/x86: thinkpad_acpi: correct palmsensor error checking

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs following v5.10.11 import

  [ Ubuntu: 5.10.0-14.15 ]

  * hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
  * Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices
  * intel-hid is not loaded on new Intel platform (LP: #1907160)
- platform/x86: intel-hid: add Rocket Lake ACPI device ID
  * Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
- scsi: target: tcmu: Fix use-after-free of se_cmd->priv
- mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
- mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC 
engine
- i2c: tegra: Wait for config load atomically while in ISR
- i2c: bpmp-tegra: Ignore unknown I2C_M flags
- platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
- ALSA: hda/via: Add minimum mute flag
- crypto: xor - Fix divide error in do_xor_speed()
- dm crypt: fix copy and paste bug in crypt_alloc_req_aead
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- btrfs: don't get an EINTR during drop_snapshot for reloc
- btrfs: do not double free backref nodes on error
- btrfs: fix lockdep splat in btrfs_recover_relocation
- btrfs: don't clear ret in btrfs_start_dirty_block_groups
- btrfs: send: fix invalid clone operations when cloning from the same file
  and root
- fs: fix lazytime expiration handling in __writeback_single_inode()
- pinctrl: ingenic: Fix JZ4760 support
- mmc: core: don't initialize block size from ext_csd if not present
- mmc: sdhci-of-dwcmshc: fix rpmb access
- mmc: sdhci-xenon: fix 1.8v regulator stabilization
- mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
- dm: avoid filesystem lookup in dm_get_dev_t()
- dm integrity: fix a crash if "recalculate" used without "internal_hash"
- dm integrity: conditionally disable "recalculate" feature
- drm/atomic: put state on error path
- drm/syncobj: Fix use-after-free
- drm/amdgpu: remove gpu info firmware of green sardine
- drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
- drm/i915/gt: Prevent use of engine->wa_ctx after error
- drm/i915: Check for rq->hwsp validity after acquiring RCU lock
- ASoC: Intel: haswell: Add missing pm_ops
- ASoC: rt711: mutex between calibration and power state changes
- SUNRPC: Handle TCP socket sends with kernel_sendpage() again
- HID: sony: select CONFIG_CRC32
- dm integrity: select CRYPTO_SKCIPHER
- x86/hyperv: Fix kexec panic/hang issues
- scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- scsi: qedi: Correct max length of CHAP secret
- scsi: scsi_debug: Fix memleak in scsi_debug_init()
- scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
- riscv: Fix kernel time_init()
- riscv: Fix sifive serial driver
- riscv: Enable interrupts during syscalls with M-Mode
- HID: logitech-dj: add the G602 receiver
- HID: Ignore battery for Elan touchscreen on ASUS UX550
- clk: tegra30: Add hda clock default rates to clock driver
- ALSA: hda/tegra: fix tegra-hda on tegra30 soc
- riscv: cacheinfo: Fix using smp_processor_id() in preemptible
- arm64: make atomic helpers __always_inline
- xen: Fix event channel callback via INTX/GSI
- x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
- x86/xen: Fix xen_hvm_smp_init() when vector callback not available
- dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
- dts: phy: add GPIO number

[Kernel-packages] [Bug 1913263] Re: Remove scary stack trace from Realtek WiFi driver

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.10: 5.10.0-1014.15 -proposed tracker (LP:
#1913154)

  * Fix  no screen show on display after S3 on CML-R (LP: #1913682)
- SAUCE: drm/i915/gen9bc: Handle TGP PCH during suspend/resume

  * RKL: backport a few fixes from v5.11 (LP: #1914412)
- drm/i915/display/fbc: Implement WA 22010751166
- drm/i915/rkl: Add new cdclk table
- drm/i915: Rename FORCEWAKE_BLITTER to FORCEWAKE_GT
- drm/i915: Update gen12 forcewake table
- drm/i915: Update gen12 multicast register ranges

  * TGL system automatically resumes from s2idle when connecting to a docking
station with a monitor (LP: #1902577)
- SAUCE: ACPI: avoid auto-wakeup with an _OSI string

  * Thinkpad - add palm sensor support needed for WWAN (LP: #1912033)
- platform/x86: thinkpad_acpi: Add palm sensor support
- platform/x86: thinkpad_acpi: correct palmsensor error checking

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs following v5.10.11 import

  [ Ubuntu: 5.10.0-14.15 ]

  * hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
  * Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices
  * intel-hid is not loaded on new Intel platform (LP: #1907160)
- platform/x86: intel-hid: add Rocket Lake ACPI device ID
  * Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
- scsi: target: tcmu: Fix use-after-free of se_cmd->priv
- mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
- mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC 
engine
- i2c: tegra: Wait for config load atomically while in ISR
- i2c: bpmp-tegra: Ignore unknown I2C_M flags
- platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
- ALSA: hda/via: Add minimum mute flag
- crypto: xor - Fix divide error in do_xor_speed()
- dm crypt: fix copy and paste bug in crypt_alloc_req_aead
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- btrfs: don't get an EINTR during drop_snapshot for reloc
- btrfs: do not double free backref nodes on error
- btrfs: fix lockdep splat in btrfs_recover_relocation
- btrfs: don't clear ret in btrfs_start_dirty_block_groups
- btrfs: send: fix invalid clone operations when cloning from the same file
  and root
- fs: fix lazytime expiration handling in __writeback_single_inode()
- pinctrl: ingenic: Fix JZ4760 support
- mmc: core: don't initialize block size from ext_csd if not present
- mmc: sdhci-of-dwcmshc: fix rpmb access
- mmc: sdhci-xenon: fix 1.8v regulator stabilization
- mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
- dm: avoid filesystem lookup in dm_get_dev_t()
- dm integrity: fix a crash if "recalculate" used without "internal_hash"
- dm integrity: conditionally disable "recalculate" feature
- drm/atomic: put state on error path
- drm/syncobj: Fix use-after-free
- drm/amdgpu: remove gpu info firmware of green sardine
- drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
- drm/i915/gt: Prevent use of engine->wa_ctx after error
- drm/i915: Check for rq->hwsp validity after acquiring RCU lock
- ASoC: Intel: haswell: Add missing pm_ops
- ASoC: rt711: mutex between calibration and power state changes
- SUNRPC: Handle TCP socket sends with kernel_sendpage() again
- HID: sony: select CONFIG_CRC32
- dm integrity: select CRYPTO_SKCIPHER
- x86/hyperv: Fix kexec panic/hang issues
- scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- scsi: qedi: Correct max length of CHAP secret
- scsi: scsi_debug: Fix memleak in scsi_debug_init()
- scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
- riscv: Fix kernel time_init()
- riscv: Fix sifive serial driver
- riscv: Enable interrupts during syscalls with M-Mode
- HID: logitech-dj: add the G602 receiver
- HID: Ignore battery for Elan touchscreen on ASUS UX550
- clk: tegra30: Add hda clock default rates to clock driver
- ALSA: hda/tegra: fix tegra-hda on tegra30 soc
- riscv: cacheinfo: Fix using smp_processor_id() in preemptible
- arm64: make atomic helpers __always_inline
- xen: Fix event channel callback via INTX/GSI
- x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
- x86/xen: Fix xen_hvm_smp_init() when vector callback not available
- dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
- dts: phy: add GPIO number

[Kernel-packages] [Bug 1913682] Re: Fix no screen show on display after S3 on CML-R

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.10: 5.10.0-1014.15 -proposed tracker (LP:
#1913154)

  * Fix  no screen show on display after S3 on CML-R (LP: #1913682)
- SAUCE: drm/i915/gen9bc: Handle TGP PCH during suspend/resume

  * RKL: backport a few fixes from v5.11 (LP: #1914412)
- drm/i915/display/fbc: Implement WA 22010751166
- drm/i915/rkl: Add new cdclk table
- drm/i915: Rename FORCEWAKE_BLITTER to FORCEWAKE_GT
- drm/i915: Update gen12 forcewake table
- drm/i915: Update gen12 multicast register ranges

  * TGL system automatically resumes from s2idle when connecting to a docking
station with a monitor (LP: #1902577)
- SAUCE: ACPI: avoid auto-wakeup with an _OSI string

  * Thinkpad - add palm sensor support needed for WWAN (LP: #1912033)
- platform/x86: thinkpad_acpi: Add palm sensor support
- platform/x86: thinkpad_acpi: correct palmsensor error checking

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs following v5.10.11 import

  [ Ubuntu: 5.10.0-14.15 ]

  * hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
  * Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices
  * intel-hid is not loaded on new Intel platform (LP: #1907160)
- platform/x86: intel-hid: add Rocket Lake ACPI device ID
  * Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
- scsi: target: tcmu: Fix use-after-free of se_cmd->priv
- mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
- mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC 
engine
- i2c: tegra: Wait for config load atomically while in ISR
- i2c: bpmp-tegra: Ignore unknown I2C_M flags
- platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
- ALSA: hda/via: Add minimum mute flag
- crypto: xor - Fix divide error in do_xor_speed()
- dm crypt: fix copy and paste bug in crypt_alloc_req_aead
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- btrfs: don't get an EINTR during drop_snapshot for reloc
- btrfs: do not double free backref nodes on error
- btrfs: fix lockdep splat in btrfs_recover_relocation
- btrfs: don't clear ret in btrfs_start_dirty_block_groups
- btrfs: send: fix invalid clone operations when cloning from the same file
  and root
- fs: fix lazytime expiration handling in __writeback_single_inode()
- pinctrl: ingenic: Fix JZ4760 support
- mmc: core: don't initialize block size from ext_csd if not present
- mmc: sdhci-of-dwcmshc: fix rpmb access
- mmc: sdhci-xenon: fix 1.8v regulator stabilization
- mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
- dm: avoid filesystem lookup in dm_get_dev_t()
- dm integrity: fix a crash if "recalculate" used without "internal_hash"
- dm integrity: conditionally disable "recalculate" feature
- drm/atomic: put state on error path
- drm/syncobj: Fix use-after-free
- drm/amdgpu: remove gpu info firmware of green sardine
- drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
- drm/i915/gt: Prevent use of engine->wa_ctx after error
- drm/i915: Check for rq->hwsp validity after acquiring RCU lock
- ASoC: Intel: haswell: Add missing pm_ops
- ASoC: rt711: mutex between calibration and power state changes
- SUNRPC: Handle TCP socket sends with kernel_sendpage() again
- HID: sony: select CONFIG_CRC32
- dm integrity: select CRYPTO_SKCIPHER
- x86/hyperv: Fix kexec panic/hang issues
- scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- scsi: qedi: Correct max length of CHAP secret
- scsi: scsi_debug: Fix memleak in scsi_debug_init()
- scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
- riscv: Fix kernel time_init()
- riscv: Fix sifive serial driver
- riscv: Enable interrupts during syscalls with M-Mode
- HID: logitech-dj: add the G602 receiver
- HID: Ignore battery for Elan touchscreen on ASUS UX550
- clk: tegra30: Add hda clock default rates to clock driver
- ALSA: hda/tegra: fix tegra-hda on tegra30 soc
- riscv: cacheinfo: Fix using smp_processor_id() in preemptible
- arm64: make atomic helpers __always_inline
- xen: Fix event channel callback via INTX/GSI
- x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
- x86/xen: Fix xen_hvm_smp_init() when vector callback not available
- dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
- dts: phy: add GPIO number

[Kernel-packages] [Bug 1913520] Re: Restore palm ejection on multi-input devices

[Launchpad Bug Tracker]

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

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

  * focal/linux-oem-5.10: 5.10.0-1014.15 -proposed tracker (LP:
#1913154)

  * Fix  no screen show on display after S3 on CML-R (LP: #1913682)
- SAUCE: drm/i915/gen9bc: Handle TGP PCH during suspend/resume

  * RKL: backport a few fixes from v5.11 (LP: #1914412)
- drm/i915/display/fbc: Implement WA 22010751166
- drm/i915/rkl: Add new cdclk table
- drm/i915: Rename FORCEWAKE_BLITTER to FORCEWAKE_GT
- drm/i915: Update gen12 forcewake table
- drm/i915: Update gen12 multicast register ranges

  * TGL system automatically resumes from s2idle when connecting to a docking
station with a monitor (LP: #1902577)
- SAUCE: ACPI: avoid auto-wakeup with an _OSI string

  * Thinkpad - add palm sensor support needed for WWAN (LP: #1912033)
- platform/x86: thinkpad_acpi: Add palm sensor support
- platform/x86: thinkpad_acpi: correct palmsensor error checking

  * Miscellaneous Ubuntu changes
- [Config] updateconfigs following v5.10.11 import

  [ Ubuntu: 5.10.0-14.15 ]

  * hirsute/linux: 5.10.0-14.15 -proposed tracker (LP: #1913724)
  * Restore palm ejection on multi-input devices (LP: #1913520)
- HID: multitouch: Apply MT_QUIRK_CONFIDENCE quirk for multi-input devices
  * intel-hid is not loaded on new Intel platform (LP: #1907160)
- platform/x86: intel-hid: add Rocket Lake ACPI device ID
  * Hirsute update: v5.10.11 upstream stable release (LP: #1913430)
- scsi: target: tcmu: Fix use-after-free of se_cmd->priv
- mtd: rawnand: gpmi: fix dst bit offset when extracting raw payload
- mtd: rawnand: nandsim: Fix the logic when selecting Hamming soft ECC 
engine
- i2c: tegra: Wait for config load atomically while in ISR
- i2c: bpmp-tegra: Ignore unknown I2C_M flags
- platform/x86: ideapad-laptop: Disable touchpad_switch for ELAN0634
- ALSA: seq: oss: Fix missing error check in snd_seq_oss_synth_make_info()
- ALSA: hda/realtek - Limit int mic boost on Acer Aspire E5-575T
- ALSA: hda/via: Add minimum mute flag
- crypto: xor - Fix divide error in do_xor_speed()
- dm crypt: fix copy and paste bug in crypt_alloc_req_aead
- ACPI: scan: Make acpi_bus_get_device() clear return pointer on error
- btrfs: don't get an EINTR during drop_snapshot for reloc
- btrfs: do not double free backref nodes on error
- btrfs: fix lockdep splat in btrfs_recover_relocation
- btrfs: don't clear ret in btrfs_start_dirty_block_groups
- btrfs: send: fix invalid clone operations when cloning from the same file
  and root
- fs: fix lazytime expiration handling in __writeback_single_inode()
- pinctrl: ingenic: Fix JZ4760 support
- mmc: core: don't initialize block size from ext_csd if not present
- mmc: sdhci-of-dwcmshc: fix rpmb access
- mmc: sdhci-xenon: fix 1.8v regulator stabilization
- mmc: sdhci-brcmstb: Fix mmc timeout errors on S5 suspend
- dm: avoid filesystem lookup in dm_get_dev_t()
- dm integrity: fix a crash if "recalculate" used without "internal_hash"
- dm integrity: conditionally disable "recalculate" feature
- drm/atomic: put state on error path
- drm/syncobj: Fix use-after-free
- drm/amdgpu: remove gpu info firmware of green sardine
- drm/amd/display: DCN2X Find Secondary Pipe properly in MPO + ODM Case
- drm/i915/gt: Prevent use of engine->wa_ctx after error
- drm/i915: Check for rq->hwsp validity after acquiring RCU lock
- ASoC: Intel: haswell: Add missing pm_ops
- ASoC: rt711: mutex between calibration and power state changes
- SUNRPC: Handle TCP socket sends with kernel_sendpage() again
- HID: sony: select CONFIG_CRC32
- dm integrity: select CRYPTO_SKCIPHER
- x86/hyperv: Fix kexec panic/hang issues
- scsi: ufs: Relax the condition of UFSHCI_QUIRK_SKIP_MANUAL_WB_FLUSH_CTRL
- scsi: ufs: Correct the LUN used in eh_device_reset_handler() callback
- scsi: qedi: Correct max length of CHAP secret
- scsi: scsi_debug: Fix memleak in scsi_debug_init()
- scsi: sd: Suppress spurious errors when WRITE SAME is being disabled
- riscv: Fix kernel time_init()
- riscv: Fix sifive serial driver
- riscv: Enable interrupts during syscalls with M-Mode
- HID: logitech-dj: add the G602 receiver
- HID: Ignore battery for Elan touchscreen on ASUS UX550
- clk: tegra30: Add hda clock default rates to clock driver
- ALSA: hda/tegra: fix tegra-hda on tegra30 soc
- riscv: cacheinfo: Fix using smp_processor_id() in preemptible
- arm64: make atomic helpers __always_inline
- xen: Fix event channel callback via INTX/GSI
- x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
- x86/xen: Fix xen_hvm_smp_init() when vector callback not available
- dts: phy: fix missing mdio device and probe failure of vsc8541-01 device
- dts: phy: add GPIO number

[Kernel-packages] [Bug 1916066] Re: Focal update: v5.4.97 upstream stable release

[Stefan Bader]

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

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

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

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

Title:
  Focal update: v5.4.97 upstream stable release

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

Bug description:
  SRU Justification

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

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

  USB: serial: cp210x: add pid/vid for WSDA-200-USB
  USB: serial: cp210x: add new VID/PID for supporting Teraoka AD2000
  USB: serial: option: Adding support for Cinterion MV31
  arm64: dts: qcom: c630: keep both touchpad devices enabled
  arm64: dts: amlogic: meson-g12: Set FL-adj property value
  arm64: dts: rockchip: fix vopl iommu irq on px30
  bpf, cgroup: Fix optlen WARN_ON_ONCE toctou
  bpf, cgroup: Fix problematic bounds check
  um: virtio: free vu_dev only with the contained struct device
  rxrpc: Fix deadlock around release of dst cached on udp tunnel
  arm64: dts: ls1046a: fix dcfg address range
  igc: set the default return value to -IGC_ERR_NVM in igc_write_nvm_srwr
  igc: check return value of ret_val in igc_config_fc_after_link_up
  i40e: Revert "i40e: don't report link up for a VF who hasn't enabled queues"
  net/mlx5: Fix leak upon failure of rule creation
  net: lapb: Copy the skb before sending a packet
  net: mvpp2: TCAM entry enable should be written after SRAM data
  r8169: fix WoL on shutdown if CONFIG_DEBUG_SHIRQ is set
  ARM: dts: sun7i: a20: bananapro: Fix ethernet phy-mode
  nvmet-tcp: fix out-of-bounds access when receiving multiple h2cdata PDUs
  memblock: do not start bottom-up allocations with kernel_end
  USB: gadget: legacy: fix an error code in eth_bind()
  USB: usblp: don't call usb_set_interface if there's a single alt
  usb: renesas_usbhs: Clear pipe running flag in usbhs_pkt_pop()
  usb: dwc2: Fix endpoint direction check in ep_from_windex
  usb: dwc3: fix clock issue during resume in OTG mode
  usb: xhci-mtk: fix unreleased bandwidth data
  usb: xhci-mtk: skip dropping bandwidth of unchecked endpoints
  usb: xhci-mtk: break loop when find the endpoint to drop
  usb: host: xhci-plat: add priv quirk for skip PHY initialization
  ovl: fix dentry leak in ovl_get_redirect
  mac80211: fix station rate table updates on assoc
  fgraph: Initialize tracing_graph_pause at task creation
  kretprobe: Avoid re-registration of the same kretprobe earlier
  libnvdimm/dimm: Avoid race between probe and available_slots_show()
  genirq/msi: Activate Multi-MSI early when MSI_FLAG_ACTIVATE_EARLY is set
  xhci: fix bounce buffer usage for non-sg list case
  cifs: report error instead of invalid when revalidating a dentry fails
  smb3: Fix out-of-bounds bug in SMB2_negotiate()
  smb3: fix crediting for compounding when only one request in flight
  mmc: core: Limit retries when analyse of SDIO tuples fails
  drm/amd/display: Revert "Fix EDID parsing after resume from suspend"
  nvme-pci: avoid the deepest sleep state on Kingston A2000 SSDs
  KVM: SVM: Treat SVM as unsupported when running as an SEV guest
  KVM: x86: Update emulator context mode if SYSENTER xfers to 64-bit mode
  ARM: footbridge: fix dc21285 PCI configuration accessors
  mm: hugetlbfs: fix cannot migrate the fallocated HugeTLB page
  mm: hugetlb: fix a race between freeing and dissolving the page
  mm: hugetlb: fix a race between isolating and freeing page
  mm: hugetlb: remove VM_BUG_ON_PAGE from page_huge_active
  mm, compaction: move high_pfn to the for loop scope
  mm: thp: fix MADV_REMOVE deadlock on shmem THP
  x86/build: Disable CET instrumentation in the kernel
  x86/apic: Add extra serialization for non-serializing MSRs
  iwlwifi: mvm: don't send RFH_QUEUE_CONFIG_CMD with no queues
  Input: xpad - sync supported devices with fork on GitHub
  iommu/vt-d: Do not use flush-queue when caching-mode is on
  md: Set prev_flush_start and flush_bio in an atomic way
  neighbour: Prevent a dead entry from updating gc_list
  net: ip_tunnel: fix mtu calculation
  net: dsa: mv88e6xxx: override existent unicast portvec in port_fdb_add
  net: sched: replaced invalid qdisc tree flush helper in qdisc_replace
  usb: host: xhci: mvebu: make USB 3.0 PHY optional for Armada 3720
  Linux 5.4.97
  UBUNTU: upstream stable to v5.4.97

To manage notifications abo

[Kernel-packages] [Bug 1916731] [NEW] [SRU][F/G/H] add AMD GPU green sardine firmwares

[AaronMa]

Public bug reported:

SRU justification:

[Impact]
Add new firmwares of AMD GPU green sardine.

[Fix]
Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new 
hardware.

[Test]
Verified on hardware with 5.10 kernel. no errors after benchmark and stress 
test.

[Where problems could occur]
Introducs the new firmwares to enable support on new GPU.
GFX can be failed if it is wrong.

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

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

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

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

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


** Tags: oem-priority originate-from-1912428 originate-from-1912558 sutton

** Tags added: oem-priority originate-from-1912558 sutton

** Tags added: originate-from-1912428

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

Title:
  [SRU][F/G/H] add AMD GPU green sardine firmwares

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware source package in Groovy:
  New
Status in linux-firmware source package in Hirsute:
  New

Bug description:
  SRU justification:

  [Impact]
  Add new firmwares of AMD GPU green sardine.

  [Fix]
  Firmware files are needed by amdgpu in Ubuntu kernel 5.10+ to support new 
hardware.

  [Test]
  Verified on hardware with 5.10 kernel. no errors after benchmark and stress 
test.

  [Where problems could occur]
  Introducs the new firmwares to enable support on new GPU.
  GFX can be failed if it is wrong.

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

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

[Kernel-packages] [Bug 1916061] Re: Focal update: v5.4.96 upstream stable release

[Stefan Bader]

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

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

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

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

Title:
  Focal update: v5.4.96 upstream stable release

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

Bug description:
  SRU Justification

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

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

  net: dsa: bcm_sf2: put device node before return
  net: switchdev: don't set port_obj_info->handled true when -EOPNOTSUPP
  ibmvnic: Ensure that CRQ entry read are correctly ordered
  Revert "Revert "block: end bio with BLK_STS_AGAIN in case of non-mq devs and 
REQ_NOWAIT""
  ACPI: thermal: Do not call acpi_thermal_check() directly
  arm64: Fix kernel address detection of __is_lm_address()
  arm64: Do not pass tagged addresses to __is_lm_address()
  tcp: make TCP_USER_TIMEOUT accurate for zero window probes
  btrfs: backref, only collect file extent items matching backref offset
  btrfs: backref, don't add refs from shared block when resolving normal backref
  btrfs: backref, only search backref entries from leaves of the same root
  btrfs: backref, use correct count to resolve normal data refs
  net_sched: gen_estimator: support large ewma log
  phy: cpcap-usb: Fix warning for missing regulator_disable
  platform/x86: touchscreen_dmi: Add swap-x-y quirk for Goodix touchscreen on 
Estar Beauty HD tablet
  platform/x86: intel-vbtn: Support for tablet mode on Dell Inspiron 7352
  x86: __always_inline __{rd,wr}msr()
  scsi: scsi_transport_srp: Don't block target in failfast state
  scsi: libfc: Avoid invoking response handler twice if ep is already completed
  scsi: fnic: Fix memleak in vnic_dev_init_devcmd2
  ASoC: SOF: Intel: hda: Resume codec to do jack detection
  mac80211: fix fast-rx encryption check
  scsi: ibmvfc: Set default timeout to avoid crash during migration
  udf: fix the problem that the disc content is not displayed
  nvme: check the PRINFO bit before deciding the host buffer length
  selftests/powerpc: Only test lwm/stmw on big endian
  drm/amd/display: Update dram_clock_change_latency for DCN2.1
  drm/amd/display: Change function decide_dp_link_settings to avoid infinite 
looping
  objtool: Don't fail on missing symbol table
  kthread: Extract KTHREAD_IS_PER_CPU
  workqueue: Restrict affinity change to rescuer
  Linux 5.4.96
  UBUNTU: upstream stable to v5.4.96

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

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

[Kernel-packages] [Bug 1916056] Re: Focal update: v5.4.95 upstream stable release

[Stefan Bader]

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

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

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

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

Title:
  Focal update: v5.4.95 upstream stable release

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

Bug description:
  SRU Justification

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

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

  ICMPv6: Add ICMPv6 Parameter Problem, code 3 definition
  IPv6: reply ICMP error if the first fragment don't include all headers
  nbd: freeze the queue while we're adding connections
  ACPI: sysfs: Prefer "compatible" modalias
  kernel: kexec: remove the lock operation of system_transition_mutex
  ALSA: hda/realtek: Enable headset of ASUS B1400CEPE with ALC256
  ALSA: hda/via: Apply the workaround generically for Clevo machines
  media: rc: ensure that uevent can be read directly after rc device register
  ARM: dts: imx6qdl-gw52xx: fix duplicate regulator naming
  wext: fix NULL-ptr-dereference with cfg80211's lack of commit()
  net: usb: qmi_wwan: added support for Thales Cinterion PLSx3 modem family
  s390/vfio-ap: No need to disable IRQ after queue reset
  PM: hibernate: flush swap writer after marking
  drivers: soc: atmel: Avoid calling at91_soc_init on non AT91 SoCs
  drivers: soc: atmel: add null entry at the end of at91_soc_allowed_list[]
  btrfs: fix possible free space tree corruption with online conversion
  KVM: x86/pmu: Fix HW_REF_CPU_CYCLES event pseudo-encoding in 
intel_arch_events[]
  KVM: x86/pmu: Fix UBSAN shift-out-of-bounds warning in intel_pmu_refresh()
  KVM: nVMX: Sync unsync'd vmcs02 state to vmcs12 on migration
  KVM: x86: get smi pending status correctly
  KVM: Forbid the use of tagged userspace addresses for memslots
  xen: Fix XenStore initialisation for XS_LOCAL
  leds: trigger: fix potential deadlock with libata
  arm64: dts: broadcom: Fix USB DMA address translation for Stingray
  mt7601u: fix kernel crash unplugging the device
  mt7601u: fix rx buffer refcounting
  drm/nouveau/svm: fail NOUVEAU_SVM_INIT ioctl on unsupported devices
  drm/i915: Check for all subplatform bits
  tee: optee: replace might_sleep with cond_resched
  xen-blkfront: allow discard-* nodes to be optional
  ARM: imx: build suspend-imx6.S with arm instruction set
  netfilter: nft_dynset: add timeout extension to template
  xfrm: Fix oops in xfrm_replay_advance_bmp
  xfrm: fix disable_xfrm sysctl when used on xfrm interfaces
  selftests: xfrm: fix test return value override issue in xfrm_policy.sh
  xfrm: Fix wraparound in xfrm_policy_addr_delta()
  arm64: dts: ls1028a: fix the offset of the reset register
  ARM: dts: imx6qdl-kontron-samx6i: fix i2c_lcd/cam default status
  firmware: imx: select SOC_BUS to fix firmware build
  RDMA/cxgb4: Fix the reported max_recv_sge value
  ASoC: Intel: Skylake: skl-topology: Fix OOPs ib skl_tplg_complete
  pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()
  iwlwifi: pcie: use jiffies for memory read spin time limit
  iwlwifi: pcie: reschedule in long-running memory reads
  mac80211: pause TX while changing interface type
  i40e: acquire VSI pointer only after VF is initialized
  igc: fix link speed advertising
  net/mlx5: Fix memory leak on flow table creation error flow
  net/mlx5e: E-switch, Fix rate calculation for overflow
  net/mlx5e: Reduce tc unsupported key print level
  can: dev: prevent potential information leak in can_fill_info()
  nvme-multipath: Early exit if no path is available
  selftests: forwarding: Specify interface when invoking mausezahn
  iommu/vt-d: Gracefully handle DMAR units with no supported address widths
  iommu/vt-d: Don't dereference iommu_device if IOMMU_API is not built
  rxrpc: Fix memory leak in rxrpc_lookup_local
  NFC: fix resource leak when target index is invalid
  NFC: fix possible resource leak
  ASoC: topology: Fix memory corruption in soc_tplg_denum_create_values()
  team: protect features update by RCU to avoid deadlock
  tcp: fix TLP timer not set when CA_STATE changes from DISORDER to OPEN
  Linux 5.4.95
  UBUNTU: upstream stable to v5.4.95

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

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

[Kernel-packages] [Bug 1809972] Re: Samsung SSD 750 EVO doesn't support queued TRIM command

[Gregory P Smith]

I'm seeing this with my 870 EVO on 20.04 kernel 5.4.0-65-generic.

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

Title:
  Samsung SSD 750 EVO doesn't support queued TRIM command

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SSD drive stops processing requests after a while
  With attached patch system is stable.
  Exact SSD information:
  ---
  Model=Samsung SSD 750 EVO 250GB, FwRev=MAT01B6Q, SerialNo=S33SNWBH536151Z
  ---

  Please note that system uses different SSD during bug reporting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   victor 2307 F...m pulseaudio
   /dev/snd/controlC1:  victor 2307 F pulseaudio
   /dev/snd/controlC0:  victor 2307 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Dec 28 15:25:43 2018
  HibernationDevice: RESUME=/dev/kubuntu-vg/swap_1
  MachineType: LENOVO 20BV0064US
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/kubuntu--vg-root ro resume=/dev/kubuntu-vg/swap_1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-06-11 (200 days ago)
  dmi.bios.date: 07/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET61WW (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV0064US
  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:bvrJBET61WW(1.25):bd07/13/2016:svnLENOVO:pn20BV0064US:pvrThinkPadT450:rvnLENOVO:rn20BV0064US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV0064US
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1809972] Re: Samsung SSD 750 EVO doesn't support queued TRIM command

[Gregory P Smith]

This also happens on the brand new Samsung 870 EVO.

And based on https://bugzilla.kernel.org/show_bug.cgi?id=203475 and
https://bugzilla.kernel.org/show_bug.cgi?id=201693 a variety of other
Samsung 8* devices on a wide variety of SATA controllers (it doesn't
seem controller related).

At the very least, the upstream change
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ca6bfcb2f6d9deab3924bf901e73622a94900473
is wrong and really needs to be rolled back... And adjusted further
given this issue was filed for a 750 which that change didn't even
cover.

The patch attached to this issue does exactly that.

Distros should patch that change out in their kernels.

** Bug watch added: Linux Kernel Bug Tracker #203475
   https://bugzilla.kernel.org/show_bug.cgi?id=203475

** Bug watch added: Linux Kernel Bug Tracker #201693
   https://bugzilla.kernel.org/show_bug.cgi?id=201693

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

Title:
  Samsung SSD 750 EVO doesn't support queued TRIM command

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SSD drive stops processing requests after a while
  With attached patch system is stable.
  Exact SSD information:
  ---
  Model=Samsung SSD 750 EVO 250GB, FwRev=MAT01B6Q, SerialNo=S33SNWBH536151Z
  ---

  Please note that system uses different SSD during bug reporting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   victor 2307 F...m pulseaudio
   /dev/snd/controlC1:  victor 2307 F pulseaudio
   /dev/snd/controlC0:  victor 2307 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Dec 28 15:25:43 2018
  HibernationDevice: RESUME=/dev/kubuntu-vg/swap_1
  MachineType: LENOVO 20BV0064US
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/kubuntu--vg-root ro resume=/dev/kubuntu-vg/swap_1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-06-11 (200 days ago)
  dmi.bios.date: 07/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET61WW (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV0064US
  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:bvrJBET61WW(1.25):bd07/13/2016:svnLENOVO:pn20BV0064US:pvrThinkPadT450:rvnLENOVO:rn20BV0064US:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV0064US
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.18.04.1) bionic; 
urgency=medium

  * Initial release (LP: #1913200).

 -- Alberto Milone   Mon, 25 Jan 2021
19:21:38 +0100

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1905446] Re: Touchpad not working in Ubuntu on Acer Aspire E3-112

[Po-Hsu Lin]

Hello Murat,

The BIOS is the same no matter what your OS is.

For your touchpad issue, can you try this latest mainline kernel out? 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11.1/
Instructions can be found here:
https://wiki.ubuntu.com/Kernel/MainlineBuilds

And attach dmesg output along with your test result (with command
"dmesg" in a terminal window, CTRL+ALT+T)

For your camera issue, please open a new bug with "ubuntu-bug linux", it's 
easier to track different issues in their own bug report.
Thank you!

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

Title:
  Touchpad not working in Ubuntu on  Acer Aspire E3-112

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello y'all!

  I'm quite a newbie in Linux/Ubuntu, so please bear with me :) My
  touchpad is not working. I'm using Ubuntu and Windows in my computer
  with dual boot, I have to choose Ubuntu each time I open the computer.
  The Touchpad works just fine in Wİndows, but in Ubuntu it doesn't
  detect it. I came here following the infor in this link:
  https://wiki.ubuntu.com/DebuggingTouchpadDetection

  My computer is Acer Aspire E 11 // E3-112-C536, I have a Fn key which
  I use in Windows to activate/disable the touchpad and many other
  things, in Ubuntu, when I press Fn and f7 (the touchpad activation key
  in my computer) all the mouse movement is disabled and I have to
  restart the system.

  Do you have any suggestions that I can follow?

  All the best

  Murat

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  siriuscoder947 F pulseaudio
   /dev/snd/pcmC0D0p:   siriuscoder947 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 20:35:44 2020
  InstallationDate: Installed on 2020-08-25 (91 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Acer Aspire E3-112
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=a0eea036-3d58-49f8-8ccb-78ec9f51b043 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-52-generic N/A
   linux-backports-modules-5.4.0-52-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: R2
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.10:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire E3-112
  dmi.product.sku: Aspire E3-112_0843_1_10
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460 -
460.39-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-460 (460.39-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream release (LP: #1913200):
- 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".

 -- Alberto Milone   Mon, 25 Jan 2021
11:47:08 +0100

** Changed in: nvidia-graphics-drivers-460 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.18.04.1) bionic; 
urgency=medium

  * Initial release (LP: #1913200).

 -- Alberto Milone   Mon, 25 Jan 2021
19:21:38 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1914022] Lsusb-v.txt

[Mladen Marinović]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466543/+files/Lsusb-v.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-offload

[Kernel-packages] [Bug 1914022] acpidump.txt

[Mladen Marinović]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466550/+files/acpidump.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentatio

[Kernel-packages] [Bug 1914022] UdevDb.txt

[Mladen Marinović]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1914022/+attachment/5466548/+files/UdevDb.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-offload: o

[Kernel-packages] [Bug 1914022] WifiSyslog.txt

[Mladen Marinović]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466549/+files/WifiSyslog.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-o

[Kernel-packages] [Bug 1914022] ProcModules.txt

[Mladen Marinović]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466547/+files/ProcModules.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation

[Kernel-packages] [Bug 1914022] ProcCpuinfo.txt

[Mladen Marinović]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466544/+files/ProcCpuinfo.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation

[Kernel-packages] [Bug 1914022] Lspci-vt.txt

[Mladen Marinović]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466540/+files/Lspci-vt.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-offlo

[Kernel-packages] [Bug 1914022] ProcInterrupts.txt

[Mladen Marinović]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466546/+files/ProcInterrupts.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmen

[Kernel-packages] [Bug 1914022] ProcCpuinfoMinimal.txt

[Mladen Marinović]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466545/+files/ProcCpuinfoMinimal.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generi

[Kernel-packages] [Bug 1914022] CurrentDmesg.txt

[Mladen Marinović]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466538/+files/CurrentDmesg.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentati

[Kernel-packages] [Bug 1914022] Lsusb.txt

[Mladen Marinović]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1914022/+attachment/5466541/+files/Lsusb.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-offload: on

[Kernel-packages] [Bug 1914022] Lspci.txt

[Mladen Marinović]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1914022/+attachment/5466539/+files/Lspci.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-offload: on

[Kernel-packages] [Bug 1914022] Lsusb-t.txt

[Mladen Marinović]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1914022/+attachment/5466542/+files/Lsusb-t.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/1914022

Title:
  Netdev watchdog closes link on  PowerEdge R6515 Realtek  BCM5720

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):

  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex

  For some reason, the link is disconnected and reconnected a few
  seconds later. This happens randomly on all 3 servers and it does not
  seem to correlate with the current traffic on that interface. The
  problem seems to be very similar to Bug #1331513 but this happens on
  the up to date Ubutnu 20.04 (last updated mid last week).

  If you need any additional info, feel free to ask.

  Additional info:
  --

  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64

  --

  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]

  --

  modinfo tg3 | grep ^version
  version:3.137

  --

  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717

  

  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-offload

[Kernel-packages] [Bug 1914022] Re: Netdev watchdog closes link on PowerEdge R6515 Realtek BCM5720

[Mladen Marinović]

apport information

** Tags added: apport-collected

** Description changed:

  A few months ago we got 3 Dell PowerEdge™ R6515 machines and installed
  Ubuntu 20.04 LTS. After a few days problems started showing on the
  network interface for the internal network. The network link is
  disconnected, and a few seconds later it is connected again. We have
  updated all the server firmware, checked the cables and switch but the
  problem persists. Digging deeper in the logs we found this in dmesg
  (full log in the attached file):
  
  [Sat Jan 30 09:57:07 2021] NETDEV WATCHDOG: eno2 (tg3): transmit queue 0 
timed out
  [Sat Jan 30 09:57:07 2021] tg3 :c1:00.1 eno2: transmit timed out, 
resetting
  [Sat Jan 30 09:57:08 2021] tg3 :c1:00.1 eno2: Link is down
  [Sat Jan 30 09:57:12 2021] tg3 :c1:00.1 eno2: Link is up at 1000 Mbps, 
full duplex
  
  For some reason, the link is disconnected and reconnected a few seconds
  later. This happens randomly on all 3 servers and it does not seem to
  correlate with the current traffic on that interface. The problem seems
  to be very similar to Bug #1331513 but this happens on the up to date
  Ubutnu 20.04 (last updated mid last week).
  
  If you need any additional info, feel free to ask.
  
  Additional info:
  --
  
  linux-firmware/now 1.187.8 all
  linux-image-5.4.0-64-generic/focal-updates,focal-updates,now 5.4.0-64.72 amd64
  linux-image-generic/now 5.4.0.64.67 amd64
  
  --
  
  lspci -nnk | grep -iA2 net
  c1:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC1
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  --
  c1:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme 
BCM5720 2-port Gigabit Ethernet PCIe [14e4:165f]
  DeviceName: NIC2
  Subsystem: Dell PowerEdge R6515/R7515 LOM [1028:08fd]
  
  --
  
  modinfo tg3 | grep ^version
  version:3.137
  
  --
  
  lshw -C network
*-network:0   
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0
 bus info: pci@:c1:00.0
 logical name: eno1
 version: 00
 serial: 34:48:ed:ef:07:0e
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 
ip=213.133.114.208 latency=0 link=yes multicast=yes port=twisted pair 
speed=1Gbit/s
 resources: irq:160 memory:c703-c703 memory:c704-c704 
memory:c705-c705 memory:c710-c713
*-network:1
 description: Ethernet interface
 product: NetXtreme BCM5720 2-port Gigabit Ethernet PCIe
 vendor: Broadcom Inc. and subsidiaries
 physical id: 0.1
 bus info: pci@:c1:00.1
 logical name: eno2
 version: 00
 serial: 34:48:ed:ef:07:0f
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm vpd msi msix pciexpress bus_master cap_list rom 
ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd 
autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=tg3 
driverversion=3.137 duplex=full firmware=FFV21.60.16 bc 5720-v1.39 ip=10.0.1.6 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:163 memory:c700-c700 memory:c701-c701 
memory:c702-c702 memory:c714-c717
  
  
  
  ethtool --show-offload eno2
  Features for eno2:
  rx-checksumming: on
  tx-checksumming: on
  tx-checksum-ipv4: on
  tx-checksum-ip-generic: off [fixed]
  tx-checksum-ipv6: on
  tx-checksum-fcoe-crc: off [fixed]
  tx-checksum-sctp: off [fixed]
  scatter-gather: on
  tx-scatter-gather: on
  tx-scatter-gather-fraglist: off [fixed]
  tcp-segmentation-offload: on
  tx-tcp-segmentation: on
  tx-tcp-ecn-segmentation: on
  tx-tcp-mangleid-segmentation: off
  tx-tcp6-segmentation: on
  generic-segmentation-offload: on
  generic-receive-offload: on
  large-receive-offload: off [fixed]
  rx-vlan-offload: on [fixed]
  tx-vlan-offload: on [fixed]
  ntuple-filters: off [fixed]
  receive-hashing: off [fixed]
  highdma: on
  rx-vlan-filter: off [fixed]
  vlan-challenged: off [fixed]
  tx-lockless: off [fixed]
  netns-local: off [fixed]
  tx-gso-robust: o

[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro HW

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Importance: High => Medium

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

Title:
  System shutdown directly by pressing power button and releasing
  immediately on Dell Vostro HW

Status in OEM Priority Project:
  Incomplete
Status in gnome-session package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kchsieh@kchsieh-laptop:~$ lsb_release -rd
  Description:  Ubuntu 20.04 LTS (fossa-bulbasaur X23)
  Release:  20.04

  kchsieh@kchsieh-laptop:~$ apt-cache policy systemd
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect: When press the button, the endSeesionDialog should show up.
  Actual: The system shutdown directly.

  When the issue happend:
  endSessionDialog is not triggered immediately after the first power button 
event, but triggered after the second power button event.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-10 (3 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Vostro 5301
  Package: systemd 245.4-4ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem 
root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8
  Tags:  focal
  Uname: Linux 5.6.0-1010-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.1.12
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5301
  dmi.product.sku: 09FC
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460 -
460.39-0ubuntu0.20.10.1

---
nvidia-graphics-drivers-460 (460.39-0ubuntu0.20.10.1) groovy; urgency=medium

  * New upstream release (LP: #1913200):
- 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".

 -- Alberto Milone   Mon, 25 Jan 2021
11:42:33 +0100

** Changed in: nvidia-graphics-drivers-460 (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
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 Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.04.1) focal; 
urgency=medium

  * Initial release (LP: #1913200).

 -- Alberto Milone   Mon, 25 Jan 2021
18:53:55 +0100

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
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 Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.04.1) focal; 
urgency=medium

  * Initial release (LP: #1913200).

 -- Alberto Milone   Mon, 25 Jan 2021
18:53:55 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
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 Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460-server -
460.32.03-0ubuntu0.20.10.1

---
nvidia-graphics-drivers-460-server (460.32.03-0ubuntu0.20.10.1) groovy; 
urgency=medium

  * Initial release (LP: #1913200).

 -- Alberto Milone   Mon, 25 Jan 2021
18:53:55 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
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 Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460 -
460.39-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-460 (460.39-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1913200):
- 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".

 -- Alberto Milone   Mon, 25 Jan 2021
11:45:30 +0100

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
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 Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1913200] Update Released

[Andy Whitcroft]

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
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 Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1913200] Re: Introduce the new NVIDIA 460-server series and update the 460 series

[Launchpad Bug Tracker]

This bug was fixed in the package nvidia-graphics-drivers-460 -
460.39-0ubuntu0.20.04.1

---
nvidia-graphics-drivers-460 (460.39-0ubuntu0.20.04.1) focal; urgency=medium

  * New upstream release (LP: #1913200):
- 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".

 -- Alberto Milone   Mon, 25 Jan 2021
11:45:30 +0100

** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: nvidia-graphics-drivers-460 (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 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:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
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 Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released

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 1916721] [NEW] hirsute/linux-raspi: Upstream raspberrypi patchset 2021-02-18

[Juerg Haefliger]

Public bug reported:

Upstream raspberrypi patchset 2021-02-18

   Ported from the following raspberrypi branch:
  rpi-5.11.y

from https://github.com/raspberrypi/linux.git

configs: Add various missing IPV6 modules
overlays: fsm-demo: Ensure all LEDs are turned off
gpio-fsm: Fix shutdown timeout handling
gpio-fsm: Show state info in /sys/class/gpio-fsm
drm/vc4: Change the default DPI format to being 18bpp, not 24.
dtoverlays: Add an overlay for the VGA666 when used with vc4-kms-v3d
defconfigs: Add DRM_DISPLAY_CONNECTOR and DRM_SIMPLE_BRIDGE for VGA666
dt: Add option for dpi without DE and PCLK (for VGA666)
staging: rpivid: Fix crash when CMA alloc fails
drm/vc4: Add connector check to trigger mode_change when hdr metadata changes
drm/vc4: Add HDR metadata property to the VC5 HDMI connectors
drm: fix HDR static metadata type field numbering
overlays: Rename gpio-fsm property num-soft-gpios
gpio-fsm: Rename 'num-soft-gpios' to avoid warning
Revert "ARM: dts: bcm2711: Add the BSC interrupt controller"
Partial revert "bcm2711: Disable bsc_intr and aon_intr by default and enable in 
overlay"
Added hflip and vflip controls to ov9281
Fixed picture line bug in all ov9281 modes
bcm2835-isp: Allow formats with different colour spaces.
Hifiberry DAC+ADC Pro fix for the PLL when changing sample rates
Added PiFi-Mini to rpi-simple-soundcard.c
Overlays for PiFi-Mini amp
staging:bcm2835-camera: Fix the cherry-pick of AWB Greyworld
w1: w1_therm: Fix conversion result for negative temperatures
bcm2711: Remove old GIC interrupt
bcm2711: Disable bsc_intr and aon_intr by default and enable in overlay
ARM: dts: bcm2711: Add the CEC interrupt controller
ARM: dts: bcm2711: Add the BSC interrupt controller
dt-binding: display: bcm2711-hdmi: Add CEC and hotplug interrupts
drm/vc4: hdmi: Don't register the CEC adapter if there's no interrupts
drm/vc4: hdmi: Remove cec_available flag
drm/vc4: hdmi: Support BCM2711 CEC interrupt setup
drm/vc4: hdmi: Split the interrupt handlers
drm/vc4: hdmi: Introduce a CEC clock
drm/vc4: hdmi: Update the CEC clock divider on HSM rate change
drm/vc4: hdmi: Compute the CEC clock divider from the clock rate
drm/vc4: hdmi: Restore cec physical address on reconnect
drm/vc4: hdmi: Fix up CEC registers
drm/vc4: hdmi: Fix register offset with longer CEC messages
drm/vc4: hdmi: Move hdmi reset to bind
ARM: bcm: Select BRCMSTB_L2_IRQ for bcm2835
Revert "vc4_hdmi: Fix up CEC registers"
Revert "vc4_hdmi: BCM2835 requires a fixed hsm clock for CEC to work"
Revert "vc4_hdmi: Fix register offset when sending longer CEC messages"
Revert "vc4_hdmi_regs: Add Intr2 register block"
Revert "vc4_hdmi_regs: Make interrupt mask variant specific"
Revert "vc4_hdmi: Make irq shared"
Revert "vc4_hdmi: Adjust CEC ref clock based on its input clock"
Revert "vc4_hdmi: Remove cec_available flag as always supported"
Revert "vc4: cec: Restore cec physical address on reconnect"
Revert "drm/vc4: Reading the hotplug register is only valid if no GPIO defined"
Revert "vc4_hdmi: Move hdmi reset to bind"
Revert "drm/vc4: hdmi: Limit the BCM2711 to the max without scrambling"
configs: Add MICREL_PHY=y
i2c: bcm2835: Handle untimely DONE signal
media: i2c: imx290: Fix number of controls in v4l2_ctrl_handler_init
media: i2c: imx290: Replace V4L2_CID_GAIN with V4L2_CID_ANALOGUE_GAIN
configs: Enable CONFIG_MEDIA_CEC_RC
ARM: dts: Declare Pi400 and CM4 have no audio pins
Enhances the Hifiberry DAC+ driver for Hifiberry AMP100 support
Adds the DT-overlays to support Hifiberry AMP100
kbuild: Silence unavoidable dtc overlay warnings
spi: bcm2835: Workaround/fix for zero-length transfers

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

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

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

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

** Description changed:

- 
  Upstream raspberrypi patchset 2021-02-18
  
-Ported from the following raspberrypi branch:
-   rpi-5.11.y
+    Ported from the following raspberrypi branch:
+   rpi-5.11.y
  
  from https://github.com/raspberrypi/linux.git
+ 
+ configs: Add various missing IPV6 modules
+ overlays: fsm-demo: Ensure all LEDs are turned off
+ gpio-fsm: Fix shutdown timeout handling
+ gpio-fsm: Show state info in /sys/class/gpio-fsm
+ drm/vc4: Change the default DPI format to being 18bpp, not 24.
+ dtoverlays: Add an overlay for the VGA666 when used with vc4-kms-v3d
+ defconfigs: Add DRM_DISPLAY_CONNECTOR and DRM_SIMPLE_BRIDGE for VGA666
+ dt: Add option for dpi without DE and PCLK (for VGA666)
+ staging: rpivid: Fix crash when CMA alloc fails
+ drm/vc4: Add connector check to trigger mode_change when hdr metadata changes
+ drm/vc4: Add HDR metadata property to the VC5 HDMI connectors
+ drm: fix HDR static metadata type field numbering
+ overlays: Rename gpio-fsm property num-soft-gpios
+ gpio-fsm

[Kernel-packages] [Bug 1909428] Re: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8

[Po-Hsu Lin]

https://lists.ubuntu.com/archives/kernel-team/2021-February/117505.html

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

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

** Changed in: linux (Ubuntu Groovy)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with
  unexpected operator on F-5.8

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Groovy:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Impact] 
  The fail check in the end of powerpc/eeh/eeh-basic.sh script will complain 
about "unexpected operator"

  This is caused by the following line in the script:
$ test "$failed" == 0
/bin/sh: 4: test: 0: unexpected operator

  [Fix]
  * 3db380570af705 ("selftests/powerpc: Make the test check in eeh-basic.sh 
posix compliant")

  This is affecting F/G/H and can be cherry-picked for all of them.

  [Test case]
  Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/
  This error message should be gone.

  [Where problems could occur]
  This fix is limited to PowerPC testing tool, it's unlike to cause any issue.

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

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

[Kernel-packages] [Bug 1912789] Re: Add support for selective build of special drivers

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-66.74

---
linux (5.4.0-66.74) focal; urgency=medium

  * focal/linux: 5.4.0-66.74 -proposed tracker (LP: #1913152)

  * Add support for selective build of special drivers (LP: #1912789)
- [Packaging] Add support for ODM drivers
- [Packaging] Turn on ODM support for amd64

  * Packaging resync (LP: #1786013)
- update dkms package versions
- update dkms package versions

  * Introduce the new NVIDIA 460-server series and update the 460 series
(LP: #1913200)
- [Config] dkms-versions -- drop NVIDIA 435 455 and 440-server
- [Config] dkms-versions -- add the 460-server nvidia driver

  * Enable mute and micmute LED on HP EliteBook 850 G7 (LP: #1910102)
- ALSA: hda/realtek: Enable mute and micmute LED on HP EliteBook 850 G7

  * SYNA30B4:00 06CB:CE09 Mouse  on HP EliteBook 850 G7 not working at all
(LP: #1908992)
- HID: multitouch: Enable multi-input for Synaptics pointstick/touchpad 
device

  * HD Audio Device PCI ID for the Intel Cometlake-R platform (LP: #1912427)
- SAUCE: ALSA: hda: Add Cometlake-R PCI ID

  * switch to an autogenerated nvidia series based core via dkms-versions
(LP: #1912803)
- [Packaging] nvidia -- use dkms-versions to define versions built
- [Packaging] update-version-dkms -- maintain flags fields
- [Config] dkms-versions -- add transitional/skip information for nvidia
  packages

  * udpgro.sh in net from ubuntu_kernel_selftests seems not reflecting sub-test
result (LP: #1908499)
- selftests: fix the return value for UDP GRO test

  * qede: Kubernetes Internal DNS Failure due to QL41xxx NIC not supporting IPIP
tx csum offload (LP: #1909062)
- qede: fix offload for IPIP tunnel packets

  * Use DCPD to control HP DreamColor panel (LP: #1911001)
- SAUCE: drm/dp: Another HP DreamColor panel brigntness fix

  * kvm: Windows 2k19 with Hyper-v role gets stuck on pending hypervisor
requests on cascadelake based kvm hosts (LP: #1911848)
- KVM: x86: Set KVM_REQ_EVENT if run is canceled with req_immediate_exit set

  * Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB
adapters' (LP: #1905574)
- net/mlx5: Fix a race when moving command interface to polling mode

  * Fix right sounds and mute/micmute LEDs for HP ZBook Fury 15/17 G7 Mobile
Workstation (LP: #1910561)
- ALSA: hda/realtek: fix right sounds and mute/micmute LEDs for HP machines

  * Ubuntu 20.04 - multicast counter is not increased in ip -s (LP: #1901842)
- net/mlx5e: Fix multicast counter not up-to-date in "ip -s"

  * eeh-basic.sh in powerpc from ubuntu_kernel_selftests timeout with 5.4 P8 /
P9 (LP: #1882503)
- selftests/powerpc/eeh: disable kselftest timeout setting for eeh-basic

  * DMI entry syntax fix for Pegatron / ByteSpeed C15B (LP: #1910639)
- Input: i8042 - unbreak Pegatron C15B

  * CVE-2020-29372
- mm: check that mm is still valid in madvise()

  * update ENA driver, incl. new ethtool stats (LP: #1910291)
- net: ena: Change WARN_ON expression in ena_del_napi_in_range()
- net: ena: ethtool: convert stat_offset to 64 bit resolution
- net: ena: ethtool: Add new device statistics
- net: ena: ethtool: add stats printing to XDP queues
- net: ena: xdp: add queue counters for xdp actions
- net: ena: Change license into format to SPDX in all files
- net: ena: Change log message to netif/dev function
- net: ena: Capitalize all log strings and improve code readability
- net: ena: Remove redundant print of placement policy
- net: ena: Change RSS related macros and variables names
- net: ena: Fix all static chekers' warnings
- drivers/net/ethernet: remove incorrectly formatted doc
- net: ena: handle bad request id in ena_netdev
- net: ena: fix packet's addresses for rx_offset feature

  * s390x broken with unknown syscall number on kernels < 5.8 (LP: #1895132)
- s390/ptrace: return -ENOSYS when invalid syscall is supplied

  * Focal update: v5.4.86 upstream stable release (LP: #1910822)
- ARM: dts: sun7i: bananapi: Enable RGMII RX/TX delay on Ethernet PHY
- ARM: dts: sun8i: r40: bananapi-m2-berry: Fix dcdc1 regulator
- ARM: dts: sun8i: v40: bananapi-m2-berry: Fix ethernet node
- 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
- ARM: dts: sun7i: pcduino3-nano: enable RGMII RX/TX delay on PHY
- ARM: dts: imx6qdl-wandboard-revd1: Remove PAD_GPIO_6 from enetgrp
- ARM: dts: imx6qdl-kontron-samx6i: fix I2C_PM scl pin
- PM: runtime: Add pm_runtime_resume_and_get to deal with usage counter
- gpio: zynq: fix reference leak in zynq_gpio functions
- gpio: mvebu: fix potential user-after-free on probe
- scsi: bnx2i: Requires MMU
- xsk: Fix xsk_poll()'s return type
- xsk: Replace datag

[Kernel-packages] [Bug 1909428] Re: eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with unexpected operator on F-5.8

[Po-Hsu Lin]

** Description changed:

- Issue found on 5.8.0-34.37~20.04.2 with P8 node dryden
+ [Impact] 
+ The fail check in the end of powerpc/eeh/eeh-basic.sh script will complain 
about "unexpected operator"
  
- This is a test case issue，caused by the following line in the script:
- $ test "$failed" == 0
- /bin/sh: 4: test: 0: unexpected operator
+ This is caused by the following line in the script:
+   $ test "$failed" == 0
+   /bin/sh: 4: test: 0: unexpected operator
+ 
+ [Fix]
+ * 3db380570af705 ("selftests/powerpc: Make the test check in eeh-basic.sh 
posix compliant")
+ 
+ This is affecting F/G/H and can be cherry-picked for all of them.
+ 
+ [Test case]
+ Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/
+ This error message should be gone.
+ 
+ [Where problems could occur]
+ This fix is limited to PowerPC testing tool, it's unlike to cause any issue.

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

Title:
  eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with
  unexpected operator on F-5.8

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Groovy:
  Incomplete
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  [Impact] 
  The fail check in the end of powerpc/eeh/eeh-basic.sh script will complain 
about "unexpected operator"

  This is caused by the following line in the script:
$ test "$failed" == 0
/bin/sh: 4: test: 0: unexpected operator

  [Fix]
  * 3db380570af705 ("selftests/powerpc: Make the test check in eeh-basic.sh 
posix compliant")

  This is affecting F/G/H and can be cherry-picked for all of them.

  [Test case]
  Run the eeh-basic.sh script in tools/testing/selftests/powerpc/eeh/
  This error message should be gone.

  [Where problems could occur]
  This fix is limited to PowerPC testing tool, it's unlike to cause any issue.

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

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

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

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

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

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

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

Title:
  eeh-basic.sh from powerpc in ubuntu_kernel_selftests failed with
  unexpected operator on F-5.8

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete
Status in linux source package in Groovy:
  Incomplete
Status in linux source package in Hirsute:
  Incomplete

Bug description:
  Issue found on 5.8.0-34.37~20.04.2 with P8 node dryden

  This is a test case issue，caused by the following line in the script:
  $ test "$failed" == 0
  /bin/sh: 4: test: 0: unexpected operator

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

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