[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.11.0.31.33)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta (5.11.0.31.33) for hirsute 
have finished running.
The following regressions have been reported in tests triggered by the package:

snapd/2.49.2+21.04ubuntu1 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta

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

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1939473] Re: mute/micmute LEDs no function on HP ProBook 650 G8

[jeremyszu]

Verified using 5.10.0-1044-oem from -proposed and the function works as
expected.

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

** Changed in: oem-priority
   Status: Triaged => Fix Committed

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

Title:
  mute/micmute LEDs no function on HP ProBook 650 G8

Status in OEM Priority Project:
  Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

[Kernel-packages] [Bug 1939539] Re: Fix Intel IPU6 camera sensor HM11b1 brightness

[You-Sheng Yang]

Testing staging kernel but I got following failure:

[6.298333] hm11b1 i2c-HIMX11B1:00: failed to find sensor: -5
[6.298427] hm11b1: probe of i2c-HIMX11B1:00 failed with error -5

** Attachment added: "dmesg.202101-28640.5.13.0-9010-oem.hm11b1"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1939539/+attachment/5517656/+files/dmesg.202101-28640.5.13.0-9010-oem.hm11b1

** Changed in: linux-oem-5.13 (Ubuntu Focal)
   Status: In Progress => Incomplete

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

Title:
  Fix Intel IPU6 camera sensor HM11b1 brightness

Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Incomplete

Bug description:
  Intel has released fix for HM11B1 sensor on IPU6 platform for its
  brightness problem in
  
https://github.com/intel/ipu6-drivers/commit/eca28d1aa048216dc034b134e65e1b47602ee4a6

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


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

[Kernel-packages] [Bug 1939845] Re: Kernal update 5.4.0-81 broke samba network

[Alexius]

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

Title:
  Kernal update 5.4.0-81 broke samba network

Status in linux package in Ubuntu:
  New

Bug description:
  Introduction:
  I use Samba for linux/windows based network, this involves a shared, ext4 
folder on linux mint pc and ntfs drive on router and ntfs folder on windows 7 
pc.

  thereabouts:
  I had all previous updates, that were current before kernal 5.4.0-81, and my 
network worked fine.
  I used the update manager to install kernal 5.4.0-81, from the tray icons (or 
whatever they are called in linux), as well as updating the relating 
dependencies when that popped up.
  I restarted, and then, I cant, see or acces, the, router storage or windows 7 
pc, likewise my windows 7 pc cant, see or access, the linux pc.
  I waited a good amount of time, and tried restarting, this didnt work.
  I reverted the kernal and dependencies to their earlier version, still same 
problem, even after several, restarts and waiting.
  I notice the modifications to the samba config are still present, that were 
required for samba to network correctly with, windows pc and router, shares.
  I then updated to the new kernal again, because it makes no difference, seems 
as previous kernal has broken share, therefore, fix will likely be same for 
both now.

  furthermore:
  I have asus rt-n65u router with latest firmware.
  I am using samba (maybe this, has been affected or needs its code updating?).
  the internet is still working, that are a usb dongle through router, to linux 
mint pc.

  

  System:Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.0.5 
 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 
20.04 focal 
  Machine:   Type: Desktop Mobo: MSI model: FM2-A55M-P33 (MS-7721) v: 3.0 
serial:  
 UEFI: American Megatrends v: 11.6 date: 02/12/2015 
  CPU:   Topology: Quad Core model: AMD A10-6700 APU with Radeon HD 
Graphics bits: 64 type: MCP 
 arch: Piledriver rev: 1 L2 cache: 2048 KiB 
 flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
bogomips: 29546 
 Speed: 2350 MHz min/max: 1800/3700 MHz Core speeds (MHz): 1: 2321 
2: 2310 3: 2207 
 4: 2156 
  Graphics:  Device-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 
1024SP] 
 vendor: PC Partner Limited driver: radeon v: kernel bus ID: 
01:00.0 chip ID: 1002:6819 
 Display: x11 server: X.Org 1.20.11 driver: ati,radeon unloaded: 
fbdev,modesetting,vesa 
 resolution: 1920x1080~60Hz 
 OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 5.4.0-81-generic LLVM 
12.0.1) 
 v: 4.5 Mesa 21.3.0-devel (git-513fb54 2021-08-12 focal-oibaf-ppa) 
direct render: Yes 
  Audio: Device-1: AMD FCH Azalia vendor: Micro-Star MSI driver: 
snd_hda_intel v: kernel 
 bus ID: 00:14.2 chip ID: 1022:780d 
 Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon 
HD 7000 Series] 
 vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 
01:00.1 
 chip ID: 1002:aab0 
 Device-3: Generalplus USB Audio Device type: USB 
 driver: hid-generic,snd-usb-audio,usbhid bus ID: 7-2:2 chip ID: 
1b3f:2008 
 Sound Server: ALSA v: k5.4.0-81-generic 
  Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI 
 driver: r8169 v: kernel port: d000 bus ID: 02:00.0 chip ID: 
10ec:8168 
 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac:  
  Drives:Local Storage: total: 380.08 GiB used: 86.82 GiB (22.8%) 
 ID-1: /dev/sda type: USB vendor: Micron model: MT-32 VLI size: 
29.82 GiB 
 speed: 3.0 Gb/s serial:  
 ID-2: /dev/sdb model: BT58SSD10S size: 238.47 GiB speed: 3.0 Gb/s 
serial:  
 temp: 40 C 
 ID-3: /dev/sdc vendor: SanDisk model: SDSSDHII120G size: 111.79 
GiB speed: 3.0 Gb/s 
 serial:  temp: 30 C 
  Partition: ID-1: / size: 233.24 GiB used: 78.37 GiB (33.6%) fs: ext4 dev: 
/dev/sdb2 
 ID-2: swap-1 size: 55.89 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sdc1 
  Sensors:   System Temperatures: cpu: 20.5 C mobo: N/A gpu: radeon temp: 36 C 
 Fan Speeds (RPM): N/A 
  Repos: No active apt repos in: /etc/apt/sources.list 
 Active apt repos in: 
/etc/apt/sources.list.d/additional-repositories.list 
 1: deb https: //dl.winehq.org/wine-builds/ubuntu/ bionic main
 Active apt repos in: 
/etc/apt/sources.list.d/cybermax-dexter-sdl2-backport-focal.list 
 1: deb http: 
//ppa.launchpad.net/cybermax-dexter/sdl2-backport/ubuntu focal main
 Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
  

[Kernel-packages] [Bug 1939845] [NEW] Kernal update 5.4.0-81 broke samba network

[Alexius]

Public bug reported:

Introduction:
I use Samba for linux/windows based network, this involves a shared, ext4 
folder on linux mint pc and ntfs drive on router and ntfs folder on windows 7 
pc.

thereabouts:
I had all previous updates, that were current before kernal 5.4.0-81, and my 
network worked fine.
I used the update manager to install kernal 5.4.0-81, from the tray icons (or 
whatever they are called in linux), as well as updating the relating 
dependencies when that popped up.
I restarted, and then, I cant, see or acces, the, router storage or windows 7 
pc, likewise my windows 7 pc cant, see or access, the linux pc.
I waited a good amount of time, and tried restarting, this didnt work.
I reverted the kernal and dependencies to their earlier version, still same 
problem, even after several, restarts and waiting.
I notice the modifications to the samba config are still present, that were 
required for samba to network correctly with, windows pc and router, shares.
I then updated to the new kernal again, because it makes no difference, seems 
as previous kernal has broken share, therefore, fix will likely be same for 
both now.

furthermore:
I have asus rt-n65u router with latest firmware.
I am using samba (maybe this, has been affected or needs its code updating?).
the internet is still working, that are a usb dongle through router, to linux 
mint pc.



System:Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
Desktop: Cinnamon 5.0.5 
   wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 
20.04 focal 
Machine:   Type: Desktop Mobo: MSI model: FM2-A55M-P33 (MS-7721) v: 3.0 serial: 
 
   UEFI: American Megatrends v: 11.6 date: 02/12/2015 
CPU:   Topology: Quad Core model: AMD A10-6700 APU with Radeon HD Graphics 
bits: 64 type: MCP 
   arch: Piledriver rev: 1 L2 cache: 2048 KiB 
   flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
bogomips: 29546 
   Speed: 2350 MHz min/max: 1800/3700 MHz Core speeds (MHz): 1: 2321 2: 
2310 3: 2207 
   4: 2156 
Graphics:  Device-1: AMD Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] 
   vendor: PC Partner Limited driver: radeon v: kernel bus ID: 01:00.0 
chip ID: 1002:6819 
   Display: x11 server: X.Org 1.20.11 driver: ati,radeon unloaded: 
fbdev,modesetting,vesa 
   resolution: 1920x1080~60Hz 
   OpenGL: renderer: AMD PITCAIRN (DRM 2.50.0 5.4.0-81-generic LLVM 
12.0.1) 
   v: 4.5 Mesa 21.3.0-devel (git-513fb54 2021-08-12 focal-oibaf-ppa) 
direct render: Yes 
Audio: Device-1: AMD FCH Azalia vendor: Micro-Star MSI driver: 
snd_hda_intel v: kernel 
   bus ID: 00:14.2 chip ID: 1022:780d 
   Device-2: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 
7000 Series] 
   vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 
01:00.1 
   chip ID: 1002:aab0 
   Device-3: Generalplus USB Audio Device type: USB 
   driver: hid-generic,snd-usb-audio,usbhid bus ID: 7-2:2 chip ID: 
1b3f:2008 
   Sound Server: ALSA v: k5.4.0-81-generic 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
vendor: Micro-Star MSI 
   driver: r8169 v: kernel port: d000 bus ID: 02:00.0 chip ID: 
10ec:8168 
   IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac:  
Drives:Local Storage: total: 380.08 GiB used: 86.82 GiB (22.8%) 
   ID-1: /dev/sda type: USB vendor: Micron model: MT-32 VLI size: 29.82 
GiB 
   speed: 3.0 Gb/s serial:  
   ID-2: /dev/sdb model: BT58SSD10S size: 238.47 GiB speed: 3.0 Gb/s 
serial:  
   temp: 40 C 
   ID-3: /dev/sdc vendor: SanDisk model: SDSSDHII120G size: 111.79 GiB 
speed: 3.0 Gb/s 
   serial:  temp: 30 C 
Partition: ID-1: / size: 233.24 GiB used: 78.37 GiB (33.6%) fs: ext4 dev: 
/dev/sdb2 
   ID-2: swap-1 size: 55.89 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sdc1 
Sensors:   System Temperatures: cpu: 20.5 C mobo: N/A gpu: radeon temp: 36 C 
   Fan Speeds (RPM): N/A 
Repos: No active apt repos in: /etc/apt/sources.list 
   Active apt repos in: 
/etc/apt/sources.list.d/additional-repositories.list 
   1: deb https: //dl.winehq.org/wine-builds/ubuntu/ bionic main
   Active apt repos in: 
/etc/apt/sources.list.d/cybermax-dexter-sdl2-backport-focal.list 
   1: deb http: 
//ppa.launchpad.net/cybermax-dexter/sdl2-backport/ubuntu focal main
   Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
   1: deb https: 
//www.mirrorservice.org/sites/packages.linuxmint.com/packages uma main upstream 
import backport
   2: deb http: //mirror.as29550.net/archive.ubuntu.com focal main 
restricted universe multiverse
   3: deb http: //mirror.as29550.net/archive.ubuntu.com focal-updates 
main restricted universe multiverse
   4: deb http: 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1014.15)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1014.15) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

v4l2loopback/0.12.5-1ubuntu1 (amd64)
backport-iwlwifi-dkms/8613-0ubuntu2 (amd64)
systemd/247.3-3ubuntu3.4 (amd64)
virtualbox/6.1.18-dfsg-5 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
oss4/4.2-build2010-5ubuntu8 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64)
lttng-modules/2.12.2-1ubuntu3 (amd64)
rtl8821ce/5.5.2.1-0ubuntu6 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-kvm

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

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock

[Bin Li]

I could reproduce this issue on L15, when I insert DP cable, it show a
lot of '*ERROR* Link Training Unsuccessful'. And from the xrandr I found
the DP monitor was recognized, and I could move mouse to this external
monitor, but the screen is black.

Aug 12 23:45:05 u-ThinkPad-L15-Gen-1 kernel: i915 :00:02.0: [drm] *ERROR* 
Link Training Unsuccessful
Aug 12 23:45:05 u-ThinkPad-L15-Gen-1 kernel: i915 :00:02.0: [drm] *ERROR* 
Link Training Unsuccessful

u@u-ThinkPad-L15-Gen-1:~$ uname -an
Linux u-ThinkPad-L15-Gen-1 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 
17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

$ xrandr
DP-1-3 connected 1600x900+1920+0 (normal left inverted right x axis y axis) 
434mm x 236mm
   1600x900  59.98*+
   1280x1024 75.0260.02··
   1152x864  75.00··
   1024x768  75.0360.00··
   800x600   75.0060.32··
   640x480   75.0059.94··
   720x400   70.08··

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

Title:
  External displays not working on Thinkpad T490 with ThinkPad
  Thunderbolt 3 Dock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have two external displays chained via Display port connected to the
  ThinkPad Thunderbolt 3 Dock.

  They are working with kernel 5.8.0-63 but not with the new 5.11.0-25
  kernel.

  I could reproduce this behavior several times for both kernels, as
  follows: I booted up with disconnected dock, logged in, then I
  connected it, disconnected it, and connected it again.

  With the 5.11.0-25 kernel the external displays go black; the main
  screen turns off and on several times. Sometimes the main screen
  remains working, but UI is lagging.

  I'm attaching the logs. Two separate boots for each variant are marked
  'a'/'b'.

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


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

[Kernel-packages] [Bug 1939844] Re: Intel GT2 ID[8086:46A0] is required

[AceLan Kao]

** Description changed:

  [Impact]
+ The GT2 ID is required.
  
  [Fix]
+ This commit adds some ADL-P IDs and need to be cherry-picked
+ 760759f2cf71 drm/i915/adl_p: Add PCI Devices IDs
  
  [Test]
+ Currently we have no h/w to verify it.
  
  [Where problems could occur]

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

Title:
  Intel GT2 ID[8086:46A0] is required

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

Bug description:
  [Impact]
  The GT2 ID is required.

  [Fix]
  This commit adds some ADL-P IDs and need to be cherry-picked
  760759f2cf71 drm/i915/adl_p: Add PCI Devices IDs

  [Test]
  Currently we have no h/w to verify it.

  [Where problems could occur]

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


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

[Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)

[Daniel van Vugt]

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

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

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

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

Title:
  System freeze (amdgpu kernel crash on resume from suspend)

Status in linux-hwe-5.11 package in Ubuntu:
  Incomplete
Status in linux-hwe-5.8 package in Ubuntu:
  New

Bug description:
  System freezes after I close the lid on the laptop and leave it closed 
overnight. It doesn't respond to any key presses or mouse clicks including 
Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the 
"suspend" screen showing but mostly it's just black. The Power settings -Dim 
screen when inactive = yes
Blank screen = never
Wifi and Bluetooth can be turned off to save power = yes
Automatic suspend on battery power = yes
Power button action = Power off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 22 17:34:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:87cf]
  InstallationDate: Installed on 2021-06-30 (22 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP Laptop 15-ef1xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 15.34
  dmi.bios.vendor: AMI
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8707
  dmi.board.vendor: HP
  dmi.board.version: 37.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 37.19
  dmi.modalias: 
dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ef1xxx
  dmi.product.sku: 27A48UA#ABA
  dmi.sys.vendor: HP
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1939539] Re: Fix Intel IPU6 camera sensor HM11b1 brightness

[You-Sheng Yang]

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

** Changed in: linux-oem-5.13 (Ubuntu Focal)
 Assignee: (unassigned) => You-Sheng Yang (vicamo)

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

Title:
  Fix Intel IPU6 camera sensor HM11b1 brightness

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

Bug description:
  Intel has released fix for HM11B1 sensor on IPU6 platform for its
  brightness problem in
  
https://github.com/intel/ipu6-drivers/commit/eca28d1aa048216dc034b134e65e1b47602ee4a6

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


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

[Kernel-packages] [Bug 1939844] Re: Intel GT2 ID[8086:46A0] is required

[AceLan Kao]

commit 760759f2cf711be86f360e6a7cdd01a9d4252b8e
Author: Clinton Taylor 
Date:   Thu May 6 19:19:22 2021 +0300

drm/i915/adl_p: Add PCI Devices IDs

Add 18 known PCI device IDs

Bspec: 55376
Cc: Caz Yokoyama 
Cc: Matt Atwood 
Cc: Matt Roper 
Signed-off-by: Clinton Taylor 
Signed-off-by: Matt Roper 
Reviewed-by: Anusha Srivatsa 
Signed-off-by: Imre Deak 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20210506161930.309688-3-imre.d...@intel.com


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

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

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

Title:
  Intel GT2 ID[8086:46A0] is required

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

Bug description:
  [Impact]

  [Fix]

  [Test]

  [Where problems could occur]

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


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

[Kernel-packages] [Bug 1939844] [NEW] Intel GT2 ID[8086:46A0] is required

[AceLan Kao]

Public bug reported:

[Impact]

[Fix]

[Test]

[Where problems could occur]

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

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

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

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

Title:
  Intel GT2 ID[8086:46A0] is required

Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.13 source package in Focal:
  New

Bug description:
  [Impact]

  [Fix]

  [Test]

  [Where problems could occur]

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


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

[Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)

[Daniel van Vugt]

Thanks. The log in comment #40 shows the system sleeping but never
waking up again. It's not clear if that's the same bug and just missing
log entries or a new bug. To help us figure it out please try:

1. Suspend.

2. Open the lid.

3. Wait 10 seconds.

4. Reboot or REISUB.

5. Run this command:

   journalctl -b-1 > prevboot.txt

6. Attach the resulting text file here.

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

Title:
  System freeze (amdgpu kernel crash on resume from suspend)

Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  System freezes after I close the lid on the laptop and leave it closed 
overnight. It doesn't respond to any key presses or mouse clicks including 
Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the 
"suspend" screen showing but mostly it's just black. The Power settings -Dim 
screen when inactive = yes
Blank screen = never
Wifi and Bluetooth can be turned off to save power = yes
Automatic suspend on battery power = yes
Power button action = Power off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 22 17:34:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:87cf]
  InstallationDate: Installed on 2021-06-30 (22 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP Laptop 15-ef1xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 15.34
  dmi.bios.vendor: AMI
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8707
  dmi.board.vendor: HP
  dmi.board.version: 37.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 37.19
  dmi.modalias: 
dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ef1xxx
  dmi.product.sku: 27A48UA#ABA
  dmi.sys.vendor: HP
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1938149] Re: To support AMD W6600 and W6700

[AceLan Kao]

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

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

Title:
  To support AMD W6600 and W6700

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]
  To support AMD Radeon Pro W6600/W6700 graphic card, we need some new firmware.

  [Fix]
  AMD suggests us to include below 2 commits, and to avoid conflicts I cherry 
pick sienna cichlid firmware from the beginning when it's been added. Impish 
already have both commits.

  amdgpu: add initial dimgrey cavefish firmware from 21.20
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=87619e4114cc631efcb6868dca54d481dc467034

  amdgpu: update sienna cichlid firmware from 21.20
  
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=4043da4f77f84b75a0f818ab7e83ead187ebf441

  [Test]
  Verified on AMD Radeon Pro W6600 graphic card.

  [Where problems could occur]
  This series of patches introduce dimgrey cavefish and sienna cichlid 
firmware. The 2 GPUs are still new and have little chance to affect old 
platforms, should be safe to include them.

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


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

[Kernel-packages] [Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table

[Kelsey Skunberg]

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

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

Title:
  Support importing mokx keys into revocation list from the mok table

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
  which revokes many Ubuntu kernel hashes and 2012 signing key.

   * Kernel should import those into it's %:.blacklist keyring such that
  it prohibits signed kexec of the revoked kernels.

   * v5.13-rc1 kernel has learned how to import mokx and how to import
  full certs into the %:.blacklist keyring.

   * However, it only does so by reading MokListXRT efi variable.

   * Due to the large size of Ubuntu's vendor-dbx, shim does not create
  MokListXRT efi variable, but instead creates MokListXRT1 MokListXRT2
  MokListXRT3 which currently v5.13-rc1 kernel cannot read. Shim also
  exposes MokListXRT via mokvar table, which is easier to parse and
  contains all the revocations in full. Kernel needs a patch to read
  MokListXRT via mokvar table.

   * We have two options on how to proceed from here, either we include
  the same hashes and certs as our vendordbx in in the kernel as
  revocation list, or we fix kernel to read MokListXRT via mokvar table

   * The above is known as CVE-2020-26541

   * Separately it would be nice to add informational dmesg messages
  when revoking signing certificates, as a good indication that signing
  key rotation events have happened and have been applied correctly.

  [Test Plan]

   * Boot kernel with 15.4 based Ubuntu shim

   * Install keyutils package

   * Execute $ sudo keyctl list %:.blacklist it should list in exccess
  of 300+ hash entries. It also must list assymetric Canonical signing
  key from 2012.

   * Separately check dmesg to observe that asymmetric canonical signing
  key from 2012 is revoked.

  [Where problems could occur]

   * EFI variable storage can be full thus preventing shim to mirror
  efivars and the moktable. On decent hardware this should not happen,
  but has been observed to be corrupted on some older EDKII based OVMF
  instances with small EFI variable storage space (pre-4MB).

  [Other Info]
   
   * The patches to fix the above have been submitted upstream

  
https://lore.kernel.org/keyrings/20210512153100.285169-1-dimitri.led...@canonical.com/

  
https://lore.kernel.org/keyrings/20210512110302.262104-1-dimitri.led...@canonical.com/

  This will now be submitted as SAUCE patches for the Ubuntu UNSTABLE
  kernel, until accepted upstream.

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


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

[Kernel-packages] [Bug 1938143] Re: Include product_sku info to modalias

[Kelsey Skunberg]

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

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

Title:
  Include product_sku info to modalias

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

Bug description:
  [Impact]
  When we add DMI quirks for the new platforms, it's hard to prevent from 
leaking its model name. Our customer doesn't like it.

  [Fix]
  Introduce the product sku modalias to DMI table, so that we can use more 
meaningless product sku string to match the platform.

  [Test]
  No real DMI quirk is added in this commit, so need to do any tests.

  [Where problems could occur]
  It's safe to add one more DMI entry, nothing could be affected.

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


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

[Kernel-packages] [Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E

[Kelsey Skunberg]

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

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

Title:
  Fix Ethernet not working by hotplug - RTL8106E

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-oem-5.13 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.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  After hot-plug the Ethernet cable, the status of Ethernet is always down.

  [Fix]
  Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired 
immediately.
  Must wait a long time to get the link change interrupt.
  After discuss with maintainer, he give some suggestions
  1. use PHY_POLL.
  2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E.

  For 2, because don't know the details about operated registers in
  rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during
  suspend.

  For 1, Use PHY_POLL have a lower risk because don't change any register 
operations and use polling method to query link change status.
  SRU the patches for 1 first.

  Currently keep discussing with Realtek but don't figure out yet.
  Will re-SRU the official solution once Realtek resolve the issue.

  Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207

  [Test]
  Verified on machines with Realtek Ethernet device, the Ethernet works well 
after hotplug 30 times.

  [Regression Potential]
  Medium, use polling methond may have higher cpu usage.

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


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

[Kernel-packages] [Bug 1938689] Re: [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock

[Kelsey Skunberg]

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

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

Title:
  [SRU][H/OEM-5.10/OEM-5.13/U] Fix system hang after unplug tbt dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.10 source package in Focal:
  New
Status in linux-oem-5.13 source package in Focal:
  New
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  New

Bug description:
  SRU justification:

  [Impact]
  System hang after unplug thunderbolt dock with Intel igc lan.

  [Fix]
  igc driver continue reading and writing MMIO address after PCI device is 
unplugged.
  This cause system page fault, and system hang.
  Add safe check and prevent reading and writing the MMIO.

  The patch is in maintainer's tree, but not merged to Linus's tree.
  Due to the schedule, send SRU as SAUCE patch.

  [Test]
  Verified on hardware, after unplug the thunderbolt cable,
  system work fine.

  [Where problems could occur]
  It may break the igc driver.

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


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

[Kelsey Skunberg]

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

-- 
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/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
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in alsa-ucm-conf source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-firmware source package in Focal:
  Confirmed
Status in alsa-ucm-conf source package in Groovy:
  Won't Fix
Status in linux source package in Groovy:
  Won't Fix
Status in linux-firmware source package in Groovy:
  Won't Fix
Status in alsa-ucm-conf source package in Hirsute:
  Won't Fix
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-firmware source package in Hirsute:
  Confirmed
Status in alsa-ucm-conf source package in Impish:
  Won't Fix
Status in linux source package in Impish:
  Confirmed
Status in linux-firmware source package in Impish:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact]
  Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where 
audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration 
is supported on these with skylake driver since kernel 5.8. However, no sound 
card can be detected w/o the topology binary file in /lib/firmware and 
corresponding ucm file.

  [Fix]
  The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be 
enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the 
topology binary file and UCM files need to be located in the correct path based 
on Intel's suggestion. 
https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb.

  [Test]
  On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 
8086:9d71, boot up the machine and check the existence of the sound card by 
either 'aplay -l' or 'pactl list' command. 

  [Where problems could occur]
  Should be low risk, it only affects limited Intel Platforms with particular 
PCI device IDs + HDA plus DMIC configuration.

  
  == Original 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: 
  

[Kernel-packages] [Bug 1934557] Re: Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop

[Kelsey Skunberg]

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

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

Title:
  Backlight (screen brightness) on Lenovo P14s AMD Gen2 inop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.13 package in Ubuntu:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  New
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Confirmed

Bug description:
  Backlight does not change. Neither with the keys, nor with the slider.
  Values in /sys/class/backlight/amdgpu_bl0/brightness do change.
  However without effect on the actual brightness of the screen, which
  seems to be stuck at maximum brightness.

  Following the instructions from here:
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-22-generic 5.11.0-22.23
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  simon  1886 F pulseaudio
   /dev/snd/pcmC2D0p:   simon  1886 F...m pulseaudio
   /dev/snd/controlC1:  simon  1886 F pulseaudio
   /dev/snd/controlC0:  simon  1886 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  3 09:46:53 2021
  InstallationDate: Installed on 2021-07-03 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 21A0CTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-22-generic N/A
   linux-backports-modules-5.11.0-22-generic  N/A
   linux-firmware 1.197.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET35W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET35W(1.05):bd04/23/2021:br1.5:efr1.5:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

  
  ==
  SRU justification:

  [Impact]
  backlight can't be controlled on AMD platform.

  [Fix]
  AUX doesn't work on HDR panel, fallback to PWM mode to make backlight be 
controlled.

  [Test]
  Verified on hardware, backlight brightness works fine.

  [Where problems could occur]
  It may break backlight control on AMD platform.

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


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

[Kernel-packages] [Bug 1935040] Re: dev_forward_skb: do not scrub skb mark within the same name space

[Kelsey Skunberg]

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

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

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

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

Title:
  dev_forward_skb: do not scrub skb mark within the same name space

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

Bug description:
  [Impact]

  The ebpf function 'bpf_redirect' reset the mark when used with the flag 
BPF_F_INGRESS.
  There are two main problems with that:
   - it's not consistent between legacy tunnels and ebpf;
   - it's not consistent between ingress and egress.

  In fact, the eBPF program can easily reset the mark, but it cannot
  preserve it.

  This kind of patch was already done in the past, see commit
  963a88b31ddb ("tunnels: harmonize cleanup done on skb on xmit path"),
  commit ea23192e8e57 ("tunnels: harmonize cleanup done on skb on rx
  path") and commit 213dd74aee76 ("skbuff: Do not scrub skb mark within
  the same name space").

  This is fixed upstream with commit ff70202b2d1a ("dev_forward_skb: do
  not scrub skb mark within the same name space").

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

  [Test Case]

  Mark a packet in the POSTROUTING hook, redirect it to another
  interface and display it with a netfilter log rule to check the mark.

  [Regression Potential]

  A user could expect that the mark is reset after a call to
  bpf_redirect(BPF_F_INGRESS), but he could easily reset it in the eBPF
  program himself.

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


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

[Kernel-packages] [Bug 1937056] Re: Touchpad not working with ASUS TUF F15

[Kelsey Skunberg]

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

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

Title:
  Touchpad not working with ASUS TUF F15

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

Bug description:
  == SRU Justification ==

  [Impact]
  Touchpad and touchscreen don't work on TGL-H laptops.

  [Fix]
  Update GPIO mapping so the values can match between Linux and BIOS.

  [Test]
  After applying the patch, both touchpad and touchscreen can work
  correctly.

  [Where problems could occur]
  If somehow any of the new pin value is incorrect, it can break devices
  that require Intel GPIO to work.

  == Original Bug Report ==

  I am using Kubuntu 21.04 on my ASUS TUF F15 FX506HM_FX566HM. The
  touchpad isn't detected in Settings and neither in xinput, nor in cat
  /proc/bus/input/devices.

  Laptop model: ASUS TUF F15 FX506HM_FX566HM.
  Manufacturer of the Touchpad: Probably ELAN1203
  When the symptom first appeared: From beginning

  Output of lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04

  Using kernel version 5.13.6. Also tried 5.11, 5.12.8, 5.12.15, 5.13.1,
  5.13.2, 5.13.4, 5.13.5, 5.14-rc2, 5.14-rc3

  Output of xinput

  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Asus Wireless Radio Control   id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Power Button  id=9[slave  keyboard (3)]
  ↳ Sleep Button  id=10   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=11   [slave  keyboard (3)]
  ↳ Intel HID events  id=12   [slave  keyboard (3)]
  ↳ Intel HID 5 button array  id=13   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=14   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=15   [slave  keyboard (3)]

  Output of lspci

  :00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host 
Bridge/DRAM Registers (rev 05)
  :00:01.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe 
Controller #1 (rev 05)
  :00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 
[Iris Xe Graphics] (rev 01)
  :00:04.0 Signal processing controller: Intel Corporation TigerLake-LP 
Dynamic Tuning Processor Participant (rev 05)
  :00:06.0 System peripheral: Intel Corporation Device 09ab
  :00:07.0 PCI bridge: Intel Corporation Tiger Lake-H Thunderbolt 4 PCI 
Express Root Port #0 (rev 05)
  :00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator 
module (rev 05)
  :00:0a.0 Signal processing controller: Intel Corporation Tigerlake 
Telemetry Aggregator Driver (rev 01)
  :00:0d.0 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 USB 
Controller (rev 05)
  :00:0d.2 USB controller: Intel Corporation Tiger Lake-H Thunderbolt 4 NHI 
#0 (rev 05)
  :00:0e.0 RAID bus controller: Intel Corporation Volume Management Device 
NVMe RAID Controller
  :00:14.0 USB controller: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 
xHCI Host Controller (rev 11)
  :00:14.2 RAM memory: Intel Corporation Tiger Lake-H Shared SRAM (rev 11)
  :00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H 
Serial IO I2C Controller #0 (rev 11)
  :00:16.0 Communication controller: Intel Corporation Tiger Lake-H 
Management Engine Interface (rev 11)
  :00:1c.0 PCI bridge: Intel Corporation Device 43bf (rev 11)
  :00:1d.0 PCI bridge: Intel Corporation Device 43b6 (rev 11)
  :00:1f.0 ISA bridge: Intel Corporation Tiger Lake-H LPC/eSPI Controller 
(rev 11)
  :00:1f.3 Audio device: Intel Corporation Tiger Lake-H HD Audio Controller 
(rev 11)
  :00:1f.4 SMBus: Intel Corporation Tiger 

[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot

[Kelsey Skunberg]

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

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

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

Title:
  [regression] USB device is not detected during boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed

Bug description:
  [SRU Justification]

  [Impact]
  The USB devices (keyboard, storage...) are failed to be detected when 
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood 
delay than it claims in the hub descriptor. It's caused by the upstream fix 
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").

  
  [Fix]
  Reverting the upstream fix until a formal fix been placed.

  [Test Case]
  1. Plug the USB device to the ports of problematic root hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.

  [Regression Potential]
  Low. The longer delay is proven safe in old kernels.

  == Original Bug Description ==

  [Summary]

  The USB devices (keyboard, storage...) are failed to be detected during boot 
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, 
they will be detected and working ok after re-plugging. The kernel output shows 
as down below during boot
  [ 39.350435] hub 1-0:1.0: USB hub found
  [ 39.398835] hub 1-0:1.0: 12 ports detected
  [ 39.622744] usb usb1-port3: couldn't allocate usb_device

  And when I plug out then plug in the same device, it shows
  [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
  [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, 
bcdDevice= 1.14
  [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0

  After doing kernel bisecting, we found the upstream commit 
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
 makes the difference. It indicates that the delay for the root hub from 
power_on to power_good is not long enough. There was no problem if the delay is 
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 
milliseconds. And the XHCI spec also says in section 5.4.8
  """
  The host is required to have power stable to the port within 20 milliseconds 
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for 
waiting 20ms.
  """

  The commit seems to follow the SPEC but could cause problems on some
  hubs.

  [Reproduce Steps]
  1. Plug the USB device to the physical port #1 and #4 which belongs to 
high-speed hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.

  [Results]
  Expected:
    All usb devices connect to the hub should work OK.

  Actual:
    USB devices connects to high-speed hub can not be probed.

  [Additional Information]
  Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26

  [Upstream bug]
  https://bugzilla.kernel.org/show_bug.cgi?id=214021

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


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

[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver

[Don Brace]

What you need is some verification tests?

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

Title:
  Update SmartPQI driver

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  Improves support in SmartPQI for most recent controllers

  [Fixes]
  All are in mainline currently and cleanly cherry pick into Hirsute.
  c64aab41c5e1 scsi: smartpqi: Remove unused functions
  5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static 
checker issue
  667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue
  d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045
  75fbeacca3ad scsi: smartpqi: Add new PCI IDs
  43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from 
hibernation
  d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs
  18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets
  55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and 
target_port_protocols
  ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives
  a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf()
  3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues
  66f1c2b40270 scsi: smartpqi: Update device scan operations
  2790cd4d3f6a scsi: smartpqi: Update OFA management
  5be9db069d3f scsi: smartpqi: Update RAID bypass handling
  9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown
  37f3318199ce scsi: smartpqi: Synchronize device resets with mutex
  4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA
  06b41e0d1800 scsi: smartpqi: Update event handler
  7a84a821f194 scsi: smartpqi: Add support for wwid
  ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds
  99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks
  5be746d7d74b scsi: smartpqi: Add host level stream detection enable
  c7ffedb3a774 scsi: smartpqi: Add stream detection
  583891c9e509 scsi: smartpqi: Align code with oob driver
  598bef8d7942 scsi: smartpqi: Add support for long firmware version
  f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and 
feature bits
  7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes
  6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes
  1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code
  281a817f232e scsi: smartpqi: Refactor aio submission code
  2708a25643ab scsi: smartpqi: Add support for new product ids
  b622a601a13a scsi: smartpqi: Correct request leakage during reset operations
  c6d3ee209b9e scsi: smartpqi: Use host-wide tag space

  The patches they provided only apply the hunk that applies to the SmartPQI 
driver. This commit was a much wider commit that removes references to 
MODULE_SUPPORTED_DEVICE in many drivers across the kernel.
  6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE

  [Testing]
  On machines equipped with SmartPQI SCSI controller:
  1. reboot tests
  2. insmod/rmmod tests
  3. fio testing: no performance regressions

  [Regression Risk]
  Patchset changes only smartpqi driver so regression is limited to systems 
equipped with this SCSI device.  On such SmartPQI-equipped systems the patchset 
can cause data corruption, data loss or unavailability of SCSI storage and boot 
failure.

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


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

[Kernel-packages] [Bug 1939349] Re: frequent hangs with latest hirsute kernel (nvidia graphics)

[Andreas]

I'm not sure that I have the same problem. 
But on a Dell Precision 7530 with kernel 5.11 I get a black screen and nothing 
works.
Intel UHD P630 on Xeon E-2186M
Nvidia Quadro P3200

This happens on Ubuntu 21.04 or Ubuntu 20.04 with kernel 5.11.
But I can boot usb live in failsafe mode with llvmpipe.

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

Title:
  frequent hangs with latest hirsute kernel (nvidia graphics)

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to the latest kernel, I am experiencing frequent
  kernel hangs.  The system does not respond to Alt+SysRq, and I have to
  power it off.

  In some cases the hang happens before X has even been launched at
  boot.

  When it hangs, the fan spins up to full speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon10452 F pulseaudio
   /dev/snd/controlC0:  vorlon10452 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  9 14:15:58 2021
  InstallationDate: Installed on 2019-12-23 (594 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QVCTO1WW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_di672m@/vmlinuz-5.11.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_di672m ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2019
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET40W (1.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET40W(1.27):bd10/17/2019:br1.27:efr1.19:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1939157] Re: HWE kernels: NFSv4.1 NULL pointer dereference

[Malcolm Scott]

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

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

Title:
  HWE kernels: NFSv4.1 NULL pointer dereference

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid

Bug description:
  Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing
  crashes (in this case with a NetApp filer mounted):

  [  266.199481] BUG: kernel NULL pointer dereference, address: 
  [  266.199495] #PF: supervisor read access in kernel mode
  [  266.199500] #PF: error_code(0x) - not-present page
  [  266.199503] PGD 0 P4D 0
  [  266.199511] Oops:  [#1] SMP PTI
  [  266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 
5.11.0-25-generic #27~20.04.1-Ubuntu
  [  266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS 
SE5C600.86B.02.06.0006.032420170950 03/24/2017
  [  266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4]
  [  266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 
45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 
24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20
  [  266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297
  [  266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: 

  [  266.199646] RDX: a04847636780 RSI: a04847636780 RDI: 
a048621ef200
  [  266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: 
a086febdcc10
  [  266.199653] R10: a0677ffd6b80 R11: 0003 R12: 

  [  266.199657] R13: a048621ef228 R14: a048621ef228 R15: 

  [  266.199661] FS:  7f9de3440340() GS:a086febc() 
knlGS:
  [  266.199665] CS:  0010 DS:  ES:  CR0: 80050033
  [  266.199669] CR2:  CR3: 00012ed86006 CR4: 
001706e0
  [  266.199674] Call Trace:
  [  266.199682]  _pnfs_return_layout+0x13d/0x2c0 [nfsv4]
  [  266.199755]  ? nfs_put_delegation+0x4c/0x70 [nfsv4]
  [  266.199814]  nfs4_evict_inode+0x78/0x80 [nfsv4]
  [  266.199870]  evict+0xd2/0x180
  [  266.199879]  iput+0x18f/0x200
  [  266.199884]  nfs_dentry_iput+0x33/0x60 [nfs]
  [  266.199934]  dentry_unlink_inode+0xb8/0x110
  [  266.199946]  __dentry_kill+0xdf/0x180
  [  266.199953]  dput+0x171/0x320
  [  266.199960]  do_renameat2+0x387/0x500
  [  266.199968]  __x64_sys_rename+0x45/0x50
  [  266.199974]  do_syscall_64+0x38/0x90
  [  266.199987]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  266.16] RIP: 0033:0x7f9de644200b
  [  266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 
1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8
  [  266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 
0052
  [  266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 
7f9de644200b
  [  266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 
55a5ed4aea00
  [  266.200022] RBP: 55a5ed503060 R08:  R09: 

  [  266.200025] R10: 000d R11: 0246 R12: 
0001
  [  266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 
55a5ed37b980
  [  266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr 
intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
crct10dif_
  pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 
rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec 
rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s
  ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl 
ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common 
xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn

  This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11).
  I believe it is fixed by https://patchwork.kernel.org/project/linux-
  nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please
  consider backporting this patch.

  (The bug was briefly also present in the 5.4 kernels, but was fixed in
  5.4.0-79: see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673)

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


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

[Kernel-packages] [Bug 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match

[Launchpad Bug Tracker]

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

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

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

Title:
  When using HWE, zfs-kmod and zfs user tools versions must match

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04.2 LTS

  I ran into a problem recently
  (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due
  to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11
  where the userspace tools don't match the zfs-kmod version. After the
  update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs-
  kmod-2.0.2-1ubuntu5

  My understanding from asking in the OpenZFS github is that the two
  versions must match.

  This bug is to figure out what to do for those of us who use HWE and
  zfs.

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


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

[Kernel-packages] [Bug 1933518] Re: Update SmartPQI 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!


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

Title:
  Update SmartPQI driver

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  Improves support in SmartPQI for most recent controllers

  [Fixes]
  All are in mainline currently and cleanly cherry pick into Hirsute.
  c64aab41c5e1 scsi: smartpqi: Remove unused functions
  5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static 
checker issue
  667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue
  d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045
  75fbeacca3ad scsi: smartpqi: Add new PCI IDs
  43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from 
hibernation
  d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs
  18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets
  55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and 
target_port_protocols
  ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives
  a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf()
  3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues
  66f1c2b40270 scsi: smartpqi: Update device scan operations
  2790cd4d3f6a scsi: smartpqi: Update OFA management
  5be9db069d3f scsi: smartpqi: Update RAID bypass handling
  9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown
  37f3318199ce scsi: smartpqi: Synchronize device resets with mutex
  4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA
  06b41e0d1800 scsi: smartpqi: Update event handler
  7a84a821f194 scsi: smartpqi: Add support for wwid
  ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds
  99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks
  5be746d7d74b scsi: smartpqi: Add host level stream detection enable
  c7ffedb3a774 scsi: smartpqi: Add stream detection
  583891c9e509 scsi: smartpqi: Align code with oob driver
  598bef8d7942 scsi: smartpqi: Add support for long firmware version
  f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and 
feature bits
  7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes
  6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes
  1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code
  281a817f232e scsi: smartpqi: Refactor aio submission code
  2708a25643ab scsi: smartpqi: Add support for new product ids
  b622a601a13a scsi: smartpqi: Correct request leakage during reset operations
  c6d3ee209b9e scsi: smartpqi: Use host-wide tag space

  The patches they provided only apply the hunk that applies to the SmartPQI 
driver. This commit was a much wider commit that removes references to 
MODULE_SUPPORTED_DEVICE in many drivers across the kernel.
  6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE

  [Testing]
  On machines equipped with SmartPQI SCSI controller:
  1. reboot tests
  2. insmod/rmmod tests
  3. fio testing: no performance regressions

  [Regression Risk]
  Patchset changes only smartpqi driver so regression is limited to systems 
equipped with this SCSI device.  On such SmartPQI-equipped systems the patchset 
can cause data corruption, data loss or unavailability of SCSI storage and boot 
failure.

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


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

[Kernel-packages] [Bug 1939157] Re: HWE kernels: NFSv4.1 NULL pointer dereference

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

Title:
  HWE kernels: NFSv4.1 NULL pointer dereference

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid

Bug description:
  Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing
  crashes (in this case with a NetApp filer mounted):

  [  266.199481] BUG: kernel NULL pointer dereference, address: 
  [  266.199495] #PF: supervisor read access in kernel mode
  [  266.199500] #PF: error_code(0x) - not-present page
  [  266.199503] PGD 0 P4D 0
  [  266.199511] Oops:  [#1] SMP PTI
  [  266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 
5.11.0-25-generic #27~20.04.1-Ubuntu
  [  266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS 
SE5C600.86B.02.06.0006.032420170950 03/24/2017
  [  266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4]
  [  266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 
45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 
24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20
  [  266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297
  [  266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: 

  [  266.199646] RDX: a04847636780 RSI: a04847636780 RDI: 
a048621ef200
  [  266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: 
a086febdcc10
  [  266.199653] R10: a0677ffd6b80 R11: 0003 R12: 

  [  266.199657] R13: a048621ef228 R14: a048621ef228 R15: 

  [  266.199661] FS:  7f9de3440340() GS:a086febc() 
knlGS:
  [  266.199665] CS:  0010 DS:  ES:  CR0: 80050033
  [  266.199669] CR2:  CR3: 00012ed86006 CR4: 
001706e0
  [  266.199674] Call Trace:
  [  266.199682]  _pnfs_return_layout+0x13d/0x2c0 [nfsv4]
  [  266.199755]  ? nfs_put_delegation+0x4c/0x70 [nfsv4]
  [  266.199814]  nfs4_evict_inode+0x78/0x80 [nfsv4]
  [  266.199870]  evict+0xd2/0x180
  [  266.199879]  iput+0x18f/0x200
  [  266.199884]  nfs_dentry_iput+0x33/0x60 [nfs]
  [  266.199934]  dentry_unlink_inode+0xb8/0x110
  [  266.199946]  __dentry_kill+0xdf/0x180
  [  266.199953]  dput+0x171/0x320
  [  266.199960]  do_renameat2+0x387/0x500
  [  266.199968]  __x64_sys_rename+0x45/0x50
  [  266.199974]  do_syscall_64+0x38/0x90
  [  266.199987]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  266.16] RIP: 0033:0x7f9de644200b
  [  266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 
1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8
  [  266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 
0052
  [  266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 
7f9de644200b
  [  266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 
55a5ed4aea00
  [  266.200022] RBP: 55a5ed503060 R08:  R09: 

  [  266.200025] R10: 000d R11: 0246 R12: 
0001
  [  266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 
55a5ed37b980
  [  266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 
auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr 
intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
crct10dif_
  pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 
rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec 
rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s
  ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl 
ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common 
xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn

  This bug occurs in all recent 20.04 HWE kernels 

[Kernel-packages] [Bug 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL

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

Title:
  REGRESSION: shiftfs lets sendfile fail with EINVAL

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux-meta-hwe-5.11 source package in Focal:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux-meta-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-hwe-5.11 source package in Impish:
  Invalid
Status in linux-meta-hwe-5.11 source package in Impish:
  Invalid

Bug description:
  With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC
  tools we're using in bionic containers as part of Anbox Cloud start to
  fail when executed on the 5.11 kernel.

  A simple reproducer looks like this:

  1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 
5.11.0-25-generic #27~20.04.1-Ubuntu)
  2. Install LXD and enable shiftfs
  $ snap install lxd
  $ snap set lxd shiftfs.enable true
  $ snap restart --reload lxd
  3. Launch bionic container and run `lxc-info`
  $ lxc launch ubuntu:b c0
  $ lxc shell c0
  c0$ apt update
  c0$ apt install -y lxc-utils
  root@c1:~# apt show lxc-utils | grep Version
  Version: 3.0.3-0ubuntu1~18.04.1
  c0$ mkdir -p containers/test
  c0$ touch containers/test/config
  c0$ lxc-info -P containers -n test
  Failed to load config for test
  Failure to retrieve information on containers:test

  Looking into the failing `lxc-info` call with strace reveals:

  ...
  memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4
  openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5
  sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument
  ...

  LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't
  affected. Any other tool using sendfile however is affected and will
  fail. Bionic is affected as the 3.0.3 version of LXC it includes still
  uses sendfile.

  Disabling shiftfs makes things work again and can be considered as a
  workaround to a certain degree, but not be applicable in all cases.

  Further analysis with Christian (cbrauner) from the LXD team this
  morning showed that shiftfs is missing an implementation for the now
  required slice_read handler in the file_operations structure. So
  whenever shiftfs is being used, all calls to sendfile will fail
  because of the missing implementation. The generic handler for this
  got removed in the following upstream change:
  https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/

  Christian implemented a quick fix:
  https://paste.ubuntu.com/p/TPsjfCpnD5/

  As of today I don't know of any customer of Anbox Cloud who is
  affected by this as most of them run with one of our cloud kernels.
  However as soon as 5.11 rolls out to the cloud kernels, we will hit
  production systems and cause them to fail.

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


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

[Kernel-packages] [Bug 1939473] Re: mute/micmute LEDs no function on HP ProBook 650 G8

[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-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1939473

Title:
  mute/micmute LEDs no function on HP ProBook 650 G8

Status in OEM Priority Project:
  Triaged
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The mic mute/audio mute LEDS are not work on HP ProBook 650 G8 Notebook PC

  [Fix]
  It needs the specific quirk for the hardware layout.
  Thus, add the quirks to make it works.

  [Test]
  After applying the quirk, the audio/mic mute LEDs are working good.

  [Where problems could occur]
  If HP ships the different system boards design with the same subsystem ID of 
audio codec which is using different GPIO pins (different layout), then the 
quirk will not work (LEDs will not work when muting audio-output or microphone).

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1013.14)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1013.14) for 
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:

v4l2loopback/0.12.5-1ubuntu1 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64)
lttng-modules/2.12.2-1ubuntu3 (amd64)
oss4/4.2-build2010-5ubuntu8 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64)
systemd/247.3-3ubuntu3.4 (amd64)
rtl8821ce/5.5.2.1-0ubuntu6 (amd64)
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
backport-iwlwifi-dkms/8613-0ubuntu2 (amd64)
virtualbox/6.1.22-dfsg-2~ubuntu1.21.04.1 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-kvm

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

Thank you!

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

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1939301] Re: REGRESSION: shiftfs lets sendfile fail with EINVAL

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

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

Title:
  REGRESSION: shiftfs lets sendfile fail with EINVAL

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux-meta-hwe-5.11 source package in Focal:
  Invalid
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux-meta-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-hwe-5.11 source package in Impish:
  Invalid
Status in linux-meta-hwe-5.11 source package in Impish:
  Invalid

Bug description:
  With the 5.11 HWE kernel landing for Ubuntu 20.04 we noticed that LXC
  tools we're using in bionic containers as part of Anbox Cloud start to
  fail when executed on the 5.11 kernel.

  A simple reproducer looks like this:

  1. Run Ubuntu 20.04 with HWE kernel (linux-generic-hwe-20.04, 
5.11.0-25-generic #27~20.04.1-Ubuntu)
  2. Install LXD and enable shiftfs
  $ snap install lxd
  $ snap set lxd shiftfs.enable true
  $ snap restart --reload lxd
  3. Launch bionic container and run `lxc-info`
  $ lxc launch ubuntu:b c0
  $ lxc shell c0
  c0$ apt update
  c0$ apt install -y lxc-utils
  root@c1:~# apt show lxc-utils | grep Version
  Version: 3.0.3-0ubuntu1~18.04.1
  c0$ mkdir -p containers/test
  c0$ touch containers/test/config
  c0$ lxc-info -P containers -n test
  Failed to load config for test
  Failure to retrieve information on containers:test

  Looking into the failing `lxc-info` call with strace reveals:

  ...
  memfd_create(".lxc_config_file", MFD_CLOEXEC) = 4
  openat(AT_FDCWD, "containers/test/config", O_RDONLY|O_CLOEXEC) = 5
  sendfile(4, 5, NULL, 2147479552)= -1 EINVAL (Invalid argument
  ...

  LXC >= 4.0.0 doesn't use sendfile anymore and with that isn't
  affected. Any other tool using sendfile however is affected and will
  fail. Bionic is affected as the 3.0.3 version of LXC it includes still
  uses sendfile.

  Disabling shiftfs makes things work again and can be considered as a
  workaround to a certain degree, but not be applicable in all cases.

  Further analysis with Christian (cbrauner) from the LXD team this
  morning showed that shiftfs is missing an implementation for the now
  required slice_read handler in the file_operations structure. So
  whenever shiftfs is being used, all calls to sendfile will fail
  because of the missing implementation. The generic handler for this
  got removed in the following upstream change:
  https://lore.kernel.org/lkml/20200626075836.1998185-10-...@lst.de/

  Christian implemented a quick fix:
  https://paste.ubuntu.com/p/TPsjfCpnD5/

  As of today I don't know of any customer of Anbox Cloud who is
  affected by this as most of them run with one of our cloud kernels.
  However as soon as 5.11 rolls out to the cloud kernels, we will hit
  production systems and cause them to fail.

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


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

[Kernel-packages] [Bug 1939673] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

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

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

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

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

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

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Committed

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

  == 470.63.01 (470) ==

* New upstream release (LP: #1939673):
  - Added support for the following GPUs:
  NVIDIA RTX A2000
  - Fixed a Vulkan performance regression that affected rFactor2.
* debian/nvidia_supported,
  debian/rules:
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

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


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

[Kernel-packages] [Bug 1939673] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-470-server into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-470-server/470.57.02-0ubuntu0.18.04.3 in a few hours, and then
in the -proposed repository.

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

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

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

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

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Committed

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

  == 470.63.01 (470) ==

* New upstream release (LP: #1939673):
  - Added support for the following GPUs:
  NVIDIA RTX A2000
  - Fixed a Vulkan performance regression that affected rFactor2.
* debian/nvidia_supported,
  debian/rules:
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

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


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

[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-470-server into hirsute-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-470-server/470.57.02-0ubuntu0.21.04.3 in a few hours, and then
in the -proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Committed

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

  == 470.63.01 (470) ==

* New upstream release (LP: #1939673):
  - Added support for the following GPUs:
  NVIDIA RTX A2000
  - Fixed a Vulkan performance regression that affected rFactor2.
* debian/nvidia_supported,
  debian/rules:
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

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


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

[Kernel-packages] [Bug 1939673] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-470 into bionic-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-470/470.63.01-0ubuntu0.18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Committed

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

  == 470.63.01 (470) ==

* New upstream release (LP: #1939673):
  - Added support for the following GPUs:
  NVIDIA RTX A2000
  - Fixed a Vulkan performance regression that affected rFactor2.
* debian/nvidia_supported,
  debian/rules:
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

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


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

[Kernel-packages] [Bug 1939673] Please test proposed package

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

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

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

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

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

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Committed

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

  == 470.63.01 (470) ==

* New upstream release (LP: #1939673):
  - Added support for the following GPUs:
  NVIDIA RTX A2000
  - Fixed a Vulkan performance regression that affected rFactor2.
* debian/nvidia_supported,
  debian/rules:
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

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


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

[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers

[Andy Whitcroft]

Hello Alberto, or anyone else affected,

Accepted nvidia-graphics-drivers-470 into hirsute-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-470/470.63.01-0ubuntu0.21.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Committed

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

  == 470.63.01 (470) ==

* New upstream release (LP: #1939673):
  - Added support for the following GPUs:
  NVIDIA RTX A2000
  - Fixed a Vulkan performance regression that affected rFactor2.
* debian/nvidia_supported,
  debian/rules:
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.
* debian/pm-aliases-gen:
  - Fix aliases generation for runtimepm.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and subvendor ids.

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


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

[Kernel-packages] [Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1932367] Re: Pixel format change broken for Elgato Cam Link 4K

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1934293] Re: Add l2tp.sh in net from ubuntu_kernel_selftests back

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1933851] Re: Focal update: v5.4.127 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1933074] Re: large_dir in ext4 broken

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1935833] Re: linux-azure CIFS DFS oops

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1932957] Re: Focal update: v5.4.125 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1934282] Re: Some test in kselftest/net on focal source tree were not tested at all

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1933369] Re: Focal update: v5.4.126 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1934179] Re: Focal update: v5.4.128 upstream stable release

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 5.4.0-81.91

---
linux (5.4.0-81.91) focal; urgency=medium

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

  * large_dir in ext4 broken (LP: #1933074)
- SAUCE: ext4: fix directory index node split corruption

  * Some test in kselftest/net on focal source tree were not tested at all
(LP: #1934282)
- selftests/net: add missing tests to Makefile

  * curtin: install flash-kernel in arm64 UEFI unexpected (LP: #1918427)
- [Packaging] Allow grub-efi-arm* to satisfy recommends on ARM

  * Add l2tp.sh in net from ubuntu_kernel_selftests back (LP: #1934293)
- Revert "UBUNTU: SAUCE: selftests/net -- disable l2tp.sh test"

  * icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 /
F-OEM-5.10 / F-OEM-5.13 / F / G / H (LP: #1880645)
- selftests: icmp_redirect: support expected failures

  * Focal update: v5.4.128 upstream stable release (LP: #1934179)
- dmaengine: ALTERA_MSGDMA depends on HAS_IOMEM
- dmaengine: QCOM_HIDMA_MGMT depends on HAS_IOMEM
- dmaengine: stedma40: add missing iounmap() on error in d40_probe()
- afs: Fix an IS_ERR() vs NULL check
- mm/memory-failure: make sure wait for page writeback in memory_failure
- kvm: LAPIC: Restore guard to prevent illegal APIC register access
- batman-adv: Avoid WARN_ON timing related checks
- net: ipv4: fix memory leak in netlbl_cipsov4_add_std
- vrf: fix maximum MTU
- net: rds: fix memory leak in rds_recvmsg
- net: lantiq: disable interrupt before sheduling NAPI
- udp: fix race between close() and udp_abort()
- rtnetlink: Fix regression in bridge VLAN configuration
- net/sched: act_ct: handle DNAT tuple collision
- net/mlx5e: Remove dependency in IPsec initialization flows
- net/mlx5e: Fix page reclaim for dead peer hairpin
- net/mlx5: Consider RoCE cap before init RDMA resources
- net/mlx5e: allow TSO on VXLAN over VLAN topologies
- net/mlx5e: Block offload of outer header csum for UDP tunnels
- netfilter: synproxy: Fix out of bounds when parsing TCP options
- sch_cake: Fix out of bounds when parsing TCP options and header
- alx: Fix an error handling path in 'alx_probe()'
- net: stmmac: dwmac1000: Fix extended MAC address registers definition
- net: make get_net_ns return error if NET_NS is disabled
- qlcnic: Fix an error handling path in 'qlcnic_probe()'
- netxen_nic: Fix an error handling path in 'netxen_nic_probe()'
- net: qrtr: fix OOB Read in qrtr_endpoint_post
- ptp: improve max_adj check against unreasonable values
- net: cdc_ncm: switch to eth%d interface naming
- lantiq: net: fix duplicated skb in rx descriptor ring
- net: usb: fix possible use-after-free in smsc75xx_bind
- net: fec_ptp: fix issue caused by refactor the fec_devtype
- net: ipv4: fix memory leak in ip_mc_add1_src
- net/af_unix: fix a data-race in unix_dgram_sendmsg / unix_release_sock
- be2net: Fix an error handling path in 'be_probe()'
- net: hamradio: fix memory leak in mkiss_close
- net: cdc_eem: fix tx fixup skb leak
- cxgb4: fix wrong shift.
- bnxt_en: Rediscover PHY capabilities after firmware reset
- bnxt_en: Call bnxt_ethtool_free() in bnxt_init_one() error path
- icmp: don't send out ICMP messages with a source address of 0.0.0.0
- net: ethernet: fix potential use-after-free in ec_bhf_remove
- regulator: bd70528: Fix off-by-one for buck123 .n_voltages setting
- ASoC: rt5659: Fix the lost powers for the HDA header
- spi: stm32-qspi: Always wait BUSY bit to be cleared in 
stm32_qspi_wait_cmd()
- pinctrl: ralink: rt2880: avoid to error in calls is pin is already enabled
- radeon: use memcpy_to/fromio for UVD fw upload
- hwmon: (scpi-hwmon) shows the negative temperature properly
- can: bcm: fix infoleak in struct bcm_msg_head
- can: bcm/raw/isotp: use per module netdevice notifier
- can: j1939: fix Use-after-Free, hold skb ref while in use
- can: mcba_usb: fix memory leak in mcba_usb
- usb: core: hub: Disable autosuspend for Cypress CY7C65632
- tracing: Do not stop recording cmdlines when tracing is off
- tracing: Do not stop recording comms if the trace file is being read
- tracing: Do no increment trace_clock_global() by one
- PCI: Mark TI C667X to avoid bus reset
- PCI: Mark some NVIDIA GPUs to avoid bus reset
- PCI: aardvark: Don't rely on jiffies while holding spinlock
- PCI: aardvark: Fix kernel panic during PIO transfer
- PCI: Add ACS quirk for Broadcom BCM57414 NIC
- PCI: Work around Huawei Intelligent NIC VF FLR erratum
- KVM: x86: Immediately reset the MMU context when the SMM flag is cleared
- ARCv2: save ABI registers across signal handling
- x86/process: Check PF_KTHREAD and not current->mm for kernel threads
- x86/pkru: Write hardware init value to PKRU when xstate is init
- x86/fpu: 

[Kernel-packages] [Bug 1938413] Re: Shutdown hangs on EHL board

[Brad Figg]

** Changed in: intel
   Status: New => Fix Committed

** Tags added: lookout-canyon

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

Title:
  Shutdown hangs on EHL board

Status in intel:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  [Summary]Go to Power -> Shutdown and the screen goes blank, but the
  system does not shut down.  You cannot recover and have to perform a
  hard reboot.

  [Steps to reproduce]
  1. Boot up Ubuntu
  2. Power -> Shutdown (click ok)

  [Expected result]
  System should cleanly shut down.

  [Actual result]
  Screen blanks with a blinking cursor, the system does not shut down, the fan 
is still on.  System is unresponsive, forcing you to do a hard reset.

  [Failure rate]100%

  [Additional information]
  CID: 20215-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

  
  [Stage]
  Device froze, issue reported and logs collected right after a reboot

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


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

[Kernel-packages] [Bug 1929902] Re: [EHL] enable USB-dw3

[Brad Figg]

** Changed in: intel
   Status: New => Fix Committed

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

Title:
  [EHL] enable USB-dw3

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  Description
  Enable USB-dw3 for Elkhart Lake

  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

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


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

[Kernel-packages] [Bug 1938408] Re: EHL board does not support soft reboot

[Brad Figg]

** Changed in: intel
   Status: New => Fix Committed

** Tags added: lookout-canyon

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

Title:
  EHL board does not support soft reboot

Status in intel:
  Fix Committed
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  [Summary]Telling the EHL board to reboot from within Ubuntu causes it
  to hang, forcing you to do a hard reboot.

  [Steps to reproduce]
  1. Open terminal window.
  2. $ reboot

  [Expected result]
  System should gracefullyl reboot.

  [Actual result]
  Screen goes blank except for a cursor.  System does not reboot. You must hard 
reboot (pull the plug)

  [Failure rate]100%

  [Additional information]
  CID: 202105-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

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


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

[Kernel-packages] [Bug 1937321] Re: System freeze (amdgpu kernel crash on resume from suspend)

[sheepscrossing]

8/12/21 Line 37

** Attachment added: "Kernel suspend lockup journal"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1937321/+attachment/5517620/+files/prevboot.txt

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

Title:
  System freeze (amdgpu kernel crash on resume from suspend)

Status in linux-hwe-5.8 package in Ubuntu:
  Incomplete

Bug description:
  System freezes after I close the lid on the laptop and leave it closed 
overnight. It doesn't respond to any key presses or mouse clicks including 
Ctrl-Alt+F4. my only recourse is to force the power off. Sometimes it has the 
"suspend" screen showing but mostly it's just black. The Power settings -Dim 
screen when inactive = yes
Blank screen = never
Wifi and Bluetooth can be turned off to save power = yes
Automatic suspend on battery power = yes
Power button action = Power off

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 22 17:34:17 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:87cf]
  InstallationDate: Installed on 2021-06-30 (22 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: HP HP Laptop 15-ef1xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic 
root=UUID=f66ca4c6-ec88-43af-81a3-7d994d7a217b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2021
  dmi.bios.release: 15.34
  dmi.bios.vendor: AMI
  dmi.bios.version: F.34
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8707
  dmi.board.vendor: HP
  dmi.board.version: 37.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 37.19
  dmi.modalias: 
dmi:bvnAMI:bvrF.34:bd03/10/2021:br15.34:efr37.19:svnHP:pnHPLaptop15-ef1xxx:pvr:rvnHP:rn8707:rvr37.19:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-ef1xxx
  dmi.product.sku: 27A48UA#ABA
  dmi.sys.vendor: HP
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1939743] [NEW] No Touchpad on TravelMate-P2 laptop

[Stephen Austin Hale]

Public bug reported:

On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the
trackpad is entirely non-functional and does not appear in the
/proc/bus/input/devices list. A wired usb mouse works perfectly, but
there does not seem to be a tweak that enables the trackpad to be seen
by the kernel.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 12 14:30:39 2021
InstallationDate: Installed on 2020-12-09 (245 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Acer TravelMate P215-53
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-54-generic N/A
 linux-backports-modules-5.4.0-54-generic  N/A
 linux-firmware1.187.15
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 12/17/2020
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BassDrum_TL
dmi.board.vendor: TGL
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: TravelMate P2
dmi.product.name: TravelMate P215-53
dmi.product.sku: 
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug 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/1939743

Title:
  No Touchpad on TravelMate-P2 laptop

Status in linux package in Ubuntu:
  New

Bug description:
  On the TravelMate P215-53 V1.10 by Acer when running Ubuntu, the
  trackpad is entirely non-functional and does not appear in the
  /proc/bus/input/devices list. A wired usb mouse works perfectly, but
  there does not seem to be a tweak that enables the trackpad to be seen
  by the kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-54-generic 5.4.0-54.60
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 12 14:30:39 2021
  InstallationDate: Installed on 2020-12-09 (245 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Acer TravelMate P215-53
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=/dev/nvme0n1p2 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-54-generic N/A
   linux-backports-modules-5.4.0-54-generic  N/A
   linux-firmware1.187.15
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 12/17/2020
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BassDrum_TL
  dmi.board.vendor: TGL
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrV1.10:bd12/17/2020:svnAcer:pnTravelMateP215-53:pvrV1.10:rvnTGL:rnBassDrum_TL:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: TravelMate P2
  dmi.product.name: TravelMate P215-53
  dmi.product.sku: 
  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/1939743/+subscriptions


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

[Kernel-packages] [Bug 1939738] [NEW] Hirsute update: upstream stable patchset 2021-08-12

[Kamal Mostafa]

Public bug reported:

SRU Justification

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

   upstream stable patchset 2021-08-12

Ported from the following upstream stable releases:
v5.10.52, v5.12.19

   from git://git.kernel.org/

certs: add 'x509_revocation_list' to gitignore
cifs: handle reconnect of tcon when there is no cached dfs referral
KVM: mmio: Fix use-after-free Read in kvm_vm_ioctl_unregister_coalesced_mmio
KVM: x86: Use guest MAXPHYADDR from CPUID.0x8000_0008 iff TDP is enabled
KVM: x86/mmu: Do not apply HPA (memory encryption) mask to GPAs
KVM: nSVM: Check the value written to MSR_VM_HSAVE_PA
KVM: X86: Disable hardware breakpoints unconditionally before kvm_x86->run()
scsi: core: Fix bad pointer dereference when ehandler kthread is invalid
scsi: zfcp: Report port fc_security as unknown early during remote cable pull
tracing: Do not reference char * as a string in histograms
drm/i915/gtt: drop the page table optimisation
drm/i915/gt: Fix -EDEADLK handling regression
cgroup: verify that source is a string
fbmem: Do not delete the mode that is still in use
drm/dp_mst: Do not set proposed vcpi directly
drm/dp_mst: Avoid to mess up payload table by ports in stale topology
drm/dp_mst: Add missing drm parameters to recently added call to drm_dbg_kms()
net: bridge: multicast: fix PIM hello router port marking race
net: bridge: multicast: fix MRD advertisement router port marking race
leds: tlc591xx: fix return value check in tlc591xx_probe()
ASoC: Intel: sof_sdw: add mutual exclusion between PCH DMIC and RT715
dmaengine: fsl-qdma: check dma_set_mask return value
scsi: arcmsr: Fix the wrong CDB payload report to IOP
srcu: Fix broken node geometry after early ssp init
rcu: Reject RCU_LOCKDEP_WARN() false positives
tty: serial: fsl_lpuart: fix the potential risk of division or modulo by zero
serial: fsl_lpuart: disable DMA for console and fix sysrq
misc/libmasm/module: Fix two use after free in ibmasm_init_one
misc: alcor_pci: fix null-ptr-deref when there is no PCI bridge
ASoC: intel/boards: add missing MODULE_DEVICE_TABLE
partitions: msdos: fix one-byte get_unaligned()
iio: gyro: fxa21002c: Balance runtime pm + use pm_runtime_resume_and_get().
iio: magn: bmc150: Balance runtime pm + use pm_runtime_resume_and_get()
ALSA: usx2y: Avoid camelCase
ALSA: usx2y: Don't call free_pages_exact() with NULL address
Revert "ALSA: bebob/oxfw: fix Kconfig entry for Mackie d.2 Pro"
usb: common: usb-conn-gpio: fix NULL pointer dereference of charger
w1: ds2438: fixing bug that would always get page0
scsi: arcmsr: Fix doorbell status being updated late on ARC-1886
scsi: hisi_sas: Propagate errors in interrupt_init_v1_hw()
scsi: lpfc: Fix "Unexpected timeout" error in direct attach topology
scsi: lpfc: Fix crash when lpfc_sli4_hba_setup() fails to initialize the SGLs
scsi: core: Cap scsi_host cmd_per_lun at can_queue
ALSA: ac97: fix PM reference leak in ac97_bus_remove()
tty: serial: 8250: serial_cs: Fix a memory leak in error handling path
scsi: mpt3sas: Fix deadlock while cancelling the running firmware event
scsi: core: Fixup calling convention for scsi_mode_sense()
scsi: scsi_dh_alua: Check for negative result value
fs/jfs: Fix missing error code in lmLogInit()
scsi: megaraid_sas: Fix resource leak in case of probe failure
scsi: megaraid_sas: Early detection of VD deletion through RaidMap update
scsi: megaraid_sas: Handle missing interrupts while re-enabling IRQs
scsi: iscsi: Add iscsi_cls_conn refcount helpers
scsi: iscsi: Fix conn use after free during resets
scsi: iscsi: Fix shost->max_id use
scsi: qedi: Fix null ref during abort handling
scsi: qedi: Fix race during abort timeouts
scsi: qedi: Fix TMF session block/unblock use
scsi: qedi: Fix cleanup session block/unblock use
mfd: da9052/stmpe: Add and modify MODULE_DEVICE_TABLE
mfd: cpcap: Fix cpcap dmamask not set warnings
ASoC: img: Fix PM reference leak in img_i2s_in_probe()
fsi: Add missing MODULE_DEVICE_TABLE
serial: tty: uartlite: fix console setup
s390/sclp_vt220: fix console name to match device
s390: disable SSP when needed
ALSA: sb: Fix potential double-free of CSP mixer elements
powerpc/ps3: Add dma_mask to ps3_dma_region
iommu/arm-smmu: Fix arm_smmu_device refcount leak when arm_smmu_rpm_get fails
iommu/arm-smmu: Fix arm_smmu_device refcount leak in address translation
ASoC: soc-pcm: fix the return value in dpcm_apply_symmetry()
gpio: zynq: Check return value of pm_runtime_get_sync
gpio: zynq: Check return value of irq_get_irq_data
scsi: storvsc: Correctly handle multiple flags in srb_status
ALSA: ppc: fix error return code in 

[Kernel-packages] [Bug 1939424] Re: FTBFS with Linux 5.13/GCC 11

[Launchpad Bug Tracker]

This bug was fixed in the package llvm-toolchain-11 - 1:11.0.1-2ubuntu5

---
llvm-toolchain-11 (1:11.0.1-2ubuntu5) impish; urgency=medium

  * Fix FTBFS with Linux 5.13 and GCC 11. (LP: #1939424)
- d/p/libsanitizer-remove-cyclades.patch: Fix FTBFS with Linux 5.13,
  where the Cyclades TTY code has been removed.  For this reason,
  libsanitizer's Cyclades support also needs to be removed.
- d/p/fix-missing-include-limit.patch: Fix FTBFS with GCC 11, which now
  requires that  be included if the source wants to use
  std::numeric_limits.

 -- Sergio Durigan Junior   Mon, 09 Aug
2021 20:05:15 -0400

** Changed in: llvm-toolchain-11 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  FTBFS with Linux 5.13/GCC 11

Status in llvm-toolchain-11 package in Ubuntu:
  Fix Released

Bug description:
  llvm-toolchain-11 is FTBFS'ing with Linux 5.13 because of:

  [  8%] Building CXX object 
projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o
  cd /<>/build-llvm/projects/compiler-rt/lib/sanitizer_common && 
/usr/bin/g++-11 -DHAVE_RPC_XDR_H=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I/<>/build-llvm/projects/compiler-rt/lib/sanitizer_common 
-I/<>/compiler-rt/lib/sanitizer_common 
-I/<>/build-llvm/include -I/<>/llvm/include 
-I/<>/compiler-rt/lib/sanitizer_common/.. -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -fvisibility-inlines-hidden -Werror=date-time 
-Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual 
-Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough 
-Wno-maybe-uninitialized -Wno-class-memaccess -Wno-redundant-move 
-Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -ffunction-sections 
-fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1  -m64 
-fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables 
-fno-stack-protector -fvisibility=hidden -fno-lto -O3 -g -Wno-variadic-macros 
-Wno-non-virtual-dtor -fno-rtti -Wframe-larger-than=570 -std=c++14 -o 
CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_posix.cpp.o -c 
/<>/compiler-rt/lib/sanitizer_common/sanitizer_posix.cpp
  
/<>/compiler-rt/lib/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10:
 fatal error: linux/cyclades.h: No such file or directory
133 | #include 
|  ^~
  compilation terminated.
  make[5]: *** 
[projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/build.make:358:
 
projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommon.x86_64.dir/sanitizer_platform_limits_posix.cpp.o]
 Error 1
  make[5]: *** Waiting for unfinished jobs
  make  -f 
projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/build.make
 
projects/compiler-rt/lib/sanitizer_common/CMakeFiles/RTSanitizerCommonCoverage.x86_64.dir/depend
  make[5]: Entering directory '/<>/build-llvm'

  This is happening because the Cyclades driver has been finally removed
  from Linux (after being orphaned 13 years ago):

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/include/uapi/linux?h=v5.12=f76edd8f7ce06cdff2fe5b6b39a49644c684a161

  LLVM includes cyclades.h when building libsanitizer, and therefore the
  FTBFS occurs.

  Upstream has fixed this by removing support for Cyclades from
  libsanitizer:

  https://github.com/llvm/llvm-
  project/commit/884040db086936107ec81656aa5b4c607235fb9a

  
  As for the GCC 11 failure, the problem is:

  [ 19%] Building CXX object 
tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangDiagnosticsEmitter.cpp.o
  cd 
/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen 
&& /<>/build-llvm/./bin/clang++ -DCLANG_VENDOR="\"Ubuntu \"" 
-D_GNU_SOURCE -D__STDC_CONSTANT_M
  ACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/utils/TableGen
 -I/<>/clang/utils/TableGen -I/<
  >/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/tools/clang/include 
-I/<>/build-llvm/tools/clang/stage2-bins/include 
-I/<>/llvm/include -fuse
  -ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option 
-fPIC -fvisibility-inlines-hidden -Werror=date-time 
-Werror=unguarded-availability-new -Wall -Wextra -Wno-unused
  -parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
-Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default 
-Wno-class-memaccess -Wno-noexcept-type -Wnon-vi
  rtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections 
-fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O2 
-DNDEBUG -g1  -fno-exceptions -std=c
  

[Kernel-packages] [Bug 1939721] [NEW] Touchpad not getting detected

[Akshay Venkatesh]

Public bug reported:

Touchpad not being listed in devices

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 12 22:03:16 2021
InstallationDate: Installed on 2021-08-12 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Touchpad not getting detected

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  Touchpad not being listed in devices

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 12 22:03:16 2021
  InstallationDate: Installed on 2021-08-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1934014] Re: [SRU] Update amdgpu/renoir firmware

[Kai-Heng Feng]

Verified that Renior can do s2idle on Focal.

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

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

Title:
  [SRU] Update amdgpu/renoir firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Renoir based systems can't resume from s2idle.

  [Fix]
  Update firmware for renoir into 21.10 or 21.20 release in linux-firmware.git
  Accompanying kernel driver updates are distributed with linux-oem-5.10.

  [Test]
  Verify s2idle on OEM system.

  [Where problems could occur]
  The firmware update is specific to Renoir systems, which are relative new so 
the impact is limited. We also have direct involvement with AMD, in case any 
regression happens.

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


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

[Kernel-packages] [Bug 1939222] Re: DisplayPort over USB-C not working after release update

[Geri Joskowicz]

Got 5.13 to boot - with nvidia removed (running nouveau)
Exactly the same symptoms as in 5.11: on/off flicker / only VGA resolution.
DP over usb-c not working correctly
I attached the dmesg output - there is a nouveau error message at the end.


** Attachment added: "dmesg after start 5.13"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939222/+attachment/5517539/+files/dmesg.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/1939222

Title:
  DisplayPort over USB-C not working after release update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over 
usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working 
properly.
  Revert to 5.8.0-63 resolves the problem.
  The problem is independent of nvdia-drivers (tried 470, 460 and intel only  
drivers). Same Monitors connected over HDMI work properly. Problem is limited 
to displayport over usb-c.

  Problem symptoms: Monitor atttached over displayport allows only VGA 
resolution(1024 * 768)  and
  flickers (on/off periodically). 

  no special error messages found in dmesg except for abundance of
  "i915 :00:02.0: [drm] *ERROR* failed to enable link training"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 09:12:10 2021
  InstallationDate: Installed on 2021-06-14 (54 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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


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

[Kernel-packages] [Bug 1937846] Re: linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11 kernels

[Marcelo Cerri]

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

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

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

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

Title:
  linux-azure: Ensure the latest linux-image-sgx is installed with the
  5.11 kernels

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-5.11 package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  Invalid
Status in linux-azure-5.11 source package in Focal:
  Fix Committed
Status in linux-azure source package in Hirsute:
  Fix Committed
Status in linux-azure-5.11 source package in Hirsute:
  Invalid

Bug description:
  [Impact]

  The 5.11 kernels include the upstream version of the SGX support. To
  ensure a better transition from the DCAP module, it's necessary to
  ensure the latest linux-base-sgx is installed with the kernel.

  [Test Plan]

  Check if the latest linux-base-sgx is installed when installing the
  5.11 linux-azure kernels.

  [Where problems could occur]

  Problems with the linux-base-sgx dependency will cause the kernel to
  not be installed.

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


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

[Kernel-packages] [Bug 1939708] [NEW] Impish update: v5.13.10 upstream stable release

[Kamal Mostafa]

Public bug reported:


SRU Justification

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

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

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

** Affects: linux (Ubuntu Impish)
 Importance: Undecided
 Status: Confirmed


** Tags: kernel-stable-tracking-bug

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

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

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   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/1939708

Title:
  Impish update: v5.13.10 upstream stable release

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

Bug description:
  
  SRU Justification

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

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

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


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

[Kernel-packages] [Bug 1818811] Re: The swapfile on the Btrfs file system is not activated

[Norbert]

Latest Ubuntu MATE 21.10 20210812 - btrfs rootfs, swapfile is not
attached (output of `swapon -s` is empty).

** Also affects: ubuntu-mate
   Importance: Undecided
   Status: New

** Tags removed: disco
** Tags added: impish iso-testing

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

Title:
  The swapfile on the Btrfs file system is not activated

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  From 5.0 kernel is implemented support for the swapfile on Btrfs
  (https://patchwork.kernel.org/cover/10584515/), today arrived on the
  repositories of Ubuntu 19.04 proposed kernel 5.0, but the swapfile is
  not activated.

  Log:

  mar 06 11:17:55 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): 
swapfile must not be copy-on-write
  mar 06 11:17:55 notebook-Lenovo-V110 swapon[517]: swapon: /swapfile: swapon 
failed: Argomento non valido
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile...
  mar 06 11:17:57 notebook-Lenovo-V110 swapon[916]: swapon: /swapfile: swapon 
failed: Argomento non valido
  mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): 
swapfile must not be copy-on-write
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process 
exited, code=exited, status=255/EXCEPTION
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with 
result 'exit-code'.
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap 
/swapfile.
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile...
  mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): 
swapfile must not be copy-on-write
  mar 06 11:17:57 notebook-Lenovo-V110 swapon[1006]: swapon: /swapfile: swapon 
failed: Argomento non valido
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process 
exited, code=exited, status=255/EXCEPTION
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with 
result 'exit-code'.
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap 
/swapfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-generic 5.0.0.7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emanu  1744 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 11:19:52 2019
  InstallationDate: Installed on 2019-01-30 (34 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5745 IMC Networks 
   Bus 001 Device 002: ID 10c4:8105 Cygnal Integrated Products, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80TL
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-7-generic 
root=UUID=91fdf6c0-1b5d-4bb5-9aa4-aeb946236b8a ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.177
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1KCN46WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V110-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr1KCN46WW:bd10/29/2018:svnLENOVO:pn80TL:pvrLenovoV110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV110-15ISK:
  dmi.product.family: V110-15ISK
  dmi.product.name: 80TL
  dmi.product.sku: LENOVO_MT_80TL_BU_idea_FM_V110-15ISK
  dmi.product.version: Lenovo V110-15ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1818811/+subscriptions


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

[Kernel-packages] [Bug 1938408] Re: EHL board does not support soft reboot

[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-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1938408

Title:
  EHL board does not support soft reboot

Status in intel:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  [Summary]Telling the EHL board to reboot from within Ubuntu causes it
  to hang, forcing you to do a hard reboot.

  [Steps to reproduce]
  1. Open terminal window.
  2. $ reboot

  [Expected result]
  System should gracefullyl reboot.

  [Actual result]
  Screen goes blank except for a cursor.  System does not reboot. You must hard 
reboot (pull the plug)

  [Failure rate]100%

  [Additional information]
  CID: 202105-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

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


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

[Kernel-packages] [Bug 1929892] Re: [TGL] enable USB-dw3

[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-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1929892

Title:
  [TGL] enable USB-dw3

Status in intel:
  New
Status in linux package in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  In Progress

Bug description:
  Description
  Enable USB-dw3 for Tiger Lake

  Hardware: Tiger Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

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


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

[Kernel-packages] [Bug 1929902] Re: [EHL] enable USB-dw3

[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-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1929902

Title:
  [EHL] enable USB-dw3

Status in intel:
  New
Status in linux package in Ubuntu:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  Description
  Enable USB-dw3 for Elkhart Lake

  Hardware: Elkhart Lake

  Target Release: 21.04
  Target Kernel: TBD

  External links:
  
https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z

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


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

[Kernel-packages] [Bug 1938413] Re: Shutdown hangs on EHL board

[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-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1938413

Title:
  Shutdown hangs on EHL board

Status in intel:
  New
Status in linux-intel package in Ubuntu:
  Fix Committed

Bug description:
  [Summary]Go to Power -> Shutdown and the screen goes blank, but the
  system does not shut down.  You cannot recover and have to perform a
  hard reboot.

  [Steps to reproduce]
  1. Boot up Ubuntu
  2. Power -> Shutdown (click ok)

  [Expected result]
  System should cleanly shut down.

  [Actual result]
  Screen blanks with a blinking cursor, the system does not shut down, the fan 
is still on.  System is unresponsive, forcing you to do a hard reset.

  [Failure rate]100%

  [Additional information]
  CID: 20215-29063 
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Elkhart Lake Embedded Platform
  bios-version: EHLSFWI1.R00.2091.A00.2002250754
  CPU: Genuine Intel(R) CPU  @ 1.90GHz (4x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:4571]
  kernel-version: 5.11.0-1009-intel

  
  [Stage]
  Device froze, issue reported and logs collected right after a reboot

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


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

[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot

[Chris Chiu]

https://lists.ubuntu.com/archives/kernel-team/2021-August/123129.html
https://lists.ubuntu.com/archives/kernel-team/2021-August/123130.html

sent to kernel mailing list

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

Title:
  [regression] USB device is not detected during boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  The USB devices (keyboard, storage...) are failed to be detected when 
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood 
delay than it claims in the hub descriptor. It's caused by the upstream fix 
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").

  
  [Fix]
  Reverting the upstream fix until a formal fix been placed.

  [Test Case]
  1. Plug the USB device to the ports of problematic root hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.

  [Regression Potential]
  Low. The longer delay is proven safe in old kernels.

  == Original Bug Description ==

  [Summary]

  The USB devices (keyboard, storage...) are failed to be detected during boot 
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, 
they will be detected and working ok after re-plugging. The kernel output shows 
as down below during boot
  [ 39.350435] hub 1-0:1.0: USB hub found
  [ 39.398835] hub 1-0:1.0: 12 ports detected
  [ 39.622744] usb usb1-port3: couldn't allocate usb_device

  And when I plug out then plug in the same device, it shows
  [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
  [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, 
bcdDevice= 1.14
  [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0

  After doing kernel bisecting, we found the upstream commit 
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
 makes the difference. It indicates that the delay for the root hub from 
power_on to power_good is not long enough. There was no problem if the delay is 
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 
milliseconds. And the XHCI spec also says in section 5.4.8
  """
  The host is required to have power stable to the port within 20 milliseconds 
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for 
waiting 20ms.
  """

  The commit seems to follow the SPEC but could cause problems on some
  hubs.

  [Reproduce Steps]
  1. Plug the USB device to the physical port #1 and #4 which belongs to 
high-speed hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.

  [Results]
  Expected:
    All usb devices connect to the hub should work OK.

  Actual:
    USB devices connects to high-speed hub can not be probed.

  [Additional Information]
  Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26

  [Upstream bug]
  https://bugzilla.kernel.org/show_bug.cgi?id=214021

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


-- 
Mailing list: https://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 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0

[Daniel Gutson]

I think this is a symptom of a bug which cause we don't know and need to
find out.

El jue., 12 ago. 2021 2:20 a. m., Kai-Heng Feng <1900...@bugs.launchpad.net>
escribió:

> So what we need to do is to lower the log level?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1900388
>
> Title:
>   blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
>   flags 0x80700 phys_seg 1 prio class 0
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
>   flags 0x80700 phys_seg 1 prio class 0
>
>   PIONEER BD-RW   BDR-205
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: linux-image-5.8.0-23-generic 5.8.0-23.24
>   ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
>   Uname: Linux 5.8.0-23-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu50
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC2:  navycat2032 F pulseaudio
>/dev/snd/controlC0:  navycat2032 F pulseaudio
>/dev/snd/controlC1:  navycat2032 F pulseaudio
>   CasperMD5CheckResult: skip
>   Date: Mon Oct 19 10:11:53 2020
>   InstallationDate: Installed on 2020-10-07 (11 days ago)
>   InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64
> (20201007)
>   IwConfig:
>lono wireless extensions.
>
>eno1  no wireless extensions.
>   MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
>   ProcFB: 0 EFI VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic
> root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-5.8.0-23-generic N/A
>linux-backports-modules-5.8.0-23-generic  N/A
>linux-firmware1.190
>   RfKill:
>
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/09/2018
>   dmi.bios.release: 4.6
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 4.6.5
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: 150-SE-E789
>   dmi.board.vendor: EVGA
>   dmi.board.version: Patsburg
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg:
>   dmi.product.family: X86 AT
>   dmi.product.name: MODEL_NAME
>   dmi.product.sku: PROJECT_SUB_TAG
>   dmi.product.version: BASE_BOARD_VERSION
>   dmi.sys.vendor: BASE_BOARD_MANUFACTURER
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+subscriptions
>
>

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

Title:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ)
  flags 0x80700 phys_seg 1 prio class 0

  PIONEER BD-RW   BDR-205

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-23-generic 5.8.0-23.24
  ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14
  Uname: Linux 5.8.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  navycat2032 F pulseaudio
   /dev/snd/controlC0:  navycat2032 F pulseaudio
   /dev/snd/controlC1:  navycat2032 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Oct 19 10:11:53 2020
  InstallationDate: Installed on 2020-10-07 (11 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic 
root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-23-generic N/A
   linux-backports-modules-5.8.0-23-generic  N/A
   linux-firmware1.190
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2018
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  

[Kernel-packages] [Bug 306003] Re: smartctl short test hangs at 90%

[Austin]

I can confirm this bug as well.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal

Self-test execution status:  ( 249) Self-test routine in progress...
90% of test remaining.

Appears to be common for WD shucked drives. 
Ran across it on my wd 8 TB HDD WD80EMAZ-00WJTA0 (FW ver. 83.H0A83)
Some via CLI finished the smart test, some are hung, the ubuntu disk manager 
did not complete its scans either.

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

Title:
  smartctl short test hangs at 90%

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems that after upgrading to 8.04 smartctl short test seems to
  hang at 90% (ie it never finishes).

  The following test hangs at 90%:

  sudo smartctl -t short /dev/sda

  Output from smartcrl -a /dev/sda
   

  Self-test execution status:  ( 249)   Self-test routine in progress...
90% of test remaining.

  according to this report
  http://smartmontools.markmail.org/message/afuajgivzxhjjgzd?q=test+90%25
  a recent kernel fixed it

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


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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[bmaupin]

I don't understand; doesn't the commit say it changed files?

> 6 files changed, 42 insertions(+), 18 deletions(-)

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1936240] Re: Sync to SGX 1.33.2

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2021-August/123118.html

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

Title:
  Sync to SGX 1.33.2

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Groovy:
  Won't Fix

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested updating ubuntu/sgx support to 1.33.2.

  [Fix]

  https://github.com/intel/SGXDataCenterAttestationPrimitives ld_133
  56a183872786d9ad3f2f395dc1d740ccb22d01a1 Linux Driver: Version 1.33.2

  [Test Case]

  Microsoft tested
  Look for "sgx: intel_sgx: Intel SGX DCAP Driver v1.33.2" in dmesg.

  [Where problems could occur]

  SGX functionality could regress

  [Other Info]

  SF: #00314640

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


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

[Kernel-packages] [Bug 1936240] Re: Sync to SGX 1.33.2

[Tim Gardner]

** Changed in: linux-azure (Ubuntu Groovy)
   Status: In Progress => Won't Fix

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

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

Title:
  Sync to SGX 1.33.2

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Groovy:
  Won't Fix

Bug description:
  SRU Justification

  [Impact]

  Microsoft has requested updating ubuntu/sgx support to 1.33.2.

  [Fix]

  https://github.com/intel/SGXDataCenterAttestationPrimitives ld_133
  56a183872786d9ad3f2f395dc1d740ccb22d01a1 Linux Driver: Version 1.33.2

  [Test Case]

  Microsoft tested
  Look for "sgx: intel_sgx: Intel SGX DCAP Driver v1.33.2" in dmesg.

  [Where problems could occur]

  SGX functionality could regress

  [Other Info]

  SF: #00314640

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


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

[Kernel-packages] [Bug 1939222] Re: DisplayPort over USB-C not working after release update

[Geri Joskowicz]

Trying, but I'm stuck with the libc6 (>= 2.33) dependency. 
Install of 5.13 fails. 
Sorry

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

Title:
  DisplayPort over USB-C not working after release update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over 
usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working 
properly.
  Revert to 5.8.0-63 resolves the problem.
  The problem is independent of nvdia-drivers (tried 470, 460 and intel only  
drivers). Same Monitors connected over HDMI work properly. Problem is limited 
to displayport over usb-c.

  Problem symptoms: Monitor atttached over displayport allows only VGA 
resolution(1024 * 768)  and
  flickers (on/off periodically). 

  no special error messages found in dmesg except for abundance of
  "i915 :00:02.0: [drm] *ERROR* failed to enable link training"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 09:12:10 2021
  InstallationDate: Installed on 2021-06-14 (54 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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


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

[Kernel-packages] [Bug 1818811] Re: The swapfile on the Btrfs file system is not activated

[Launchpad Bug Tracker]

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

** Changed in: ubiquity (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/1818811

Title:
  The swapfile on the Btrfs file system is not activated

Status in linux package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  From 5.0 kernel is implemented support for the swapfile on Btrfs
  (https://patchwork.kernel.org/cover/10584515/), today arrived on the
  repositories of Ubuntu 19.04 proposed kernel 5.0, but the swapfile is
  not activated.

  Log:

  mar 06 11:17:55 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): 
swapfile must not be copy-on-write
  mar 06 11:17:55 notebook-Lenovo-V110 swapon[517]: swapon: /swapfile: swapon 
failed: Argomento non valido
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile...
  mar 06 11:17:57 notebook-Lenovo-V110 swapon[916]: swapon: /swapfile: swapon 
failed: Argomento non valido
  mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): 
swapfile must not be copy-on-write
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process 
exited, code=exited, status=255/EXCEPTION
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with 
result 'exit-code'.
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap 
/swapfile.
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile...
  mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): 
swapfile must not be copy-on-write
  mar 06 11:17:57 notebook-Lenovo-V110 swapon[1006]: swapon: /swapfile: swapon 
failed: Argomento non valido
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process 
exited, code=exited, status=255/EXCEPTION
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with 
result 'exit-code'.
  mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap 
/swapfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-generic 5.0.0.7.8
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  emanu  1744 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 11:19:52 2019
  InstallationDate: Installed on 2019-01-30 (34 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 13d3:5745 IMC Networks 
   Bus 001 Device 002: ID 10c4:8105 Cygnal Integrated Products, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80TL
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-7-generic 
root=UUID=91fdf6c0-1b5d-4bb5-9aa4-aeb946236b8a ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.177
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1KCN46WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V110-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr1KCN46WW:bd10/29/2018:svnLENOVO:pn80TL:pvrLenovoV110-15ISK:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV110-15ISK:
  dmi.product.family: V110-15ISK
  dmi.product.name: 80TL
  dmi.product.sku: LENOVO_MT_80TL_BU_idea_FM_V110-15ISK
  dmi.product.version: Lenovo V110-15ISK
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS

[Frank Heimes]

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

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

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

Title:
  EP11 cards going offline => Fix backport to U20.04LTS

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

Bug description:
  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

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


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

[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers

[Alberto Milone]

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Description changed:

  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.
  
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.
  
  See the changelog entry below for a full list of changes and bugs.
  
  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates
  
  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
  
  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.
  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.
  
  [Discussion]
  
  [Changelog]
  
  == 470.57.02 (470-server) ==
  
-   *
+   * debian/nvidia_supported,
+ debian/rules (LP: #1939673):
+ - Use the json database file to generate the modaliases.
+ - Fix aliases generation.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.
+   * debian/pm-aliases-gen:
+ - Fix aliases generation for runtimepm.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.
+ 
+ == 470.63.01 (470) ==
+ 
+   * New upstream release (LP: #1939673):
+ - Added support for the following GPUs:
+ NVIDIA RTX A2000
+ - Fixed a Vulkan performance regression that affected rFactor2.
+   * debian/nvidia_supported,
+ debian/rules:
+ - Use the json database file to generate the modaliases.
+ - Fix aliases generation.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.
+   * debian/pm-aliases-gen:
+ - Fix aliases generation for runtimepm.
+   We were not matching some of the aliases because of some missing
+   zeroes in the subdevice and subvendor ids.

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  In Progress

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* debian/nvidia_supported,
  debian/rules (LP: #1939673):
  - Use the json database file to generate the modaliases.
  - Fix aliases generation.
We were not matching some of the aliases because of some missing
zeroes in the subdevice and 

[Kernel-packages] [Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS

[Krzysztof Kozlowski]

As Frank mentioned, the patches cannot be accepted in that form. There
is no information where these came from and what was changed in the
backport. This is a series of 33 commits, it's enormous. Are these all
fixes? Looks like not because only two patches have stable tags, +three
patches have Fixes tag. What's with the rest? Are they going to stable
trees?

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

Title:
  EP11 cards going offline => Fix backport to U20.04LTS

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

Bug description:
  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

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


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

[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Pham Quoc Hung]

Same issue for me. Bluetooth is one of the most annoying issues on Linux.
- OS: Ubuntu 20.04.1 LTS
- Kernel: 5.4.0-80-generic
- Machine: Dell precision M4700
- Headset: Sony WH-CH510

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot

[Chris Chiu]

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ The USB devices (keyboard, storage...) are failed to be detected when 
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood 
delay than it claims in the hub descriptor. It's caused by the upstream fix 
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
+ 
+ 
+ [Fix]
+ Reverting the upstream fix until a formal fix been placed.
+ 
+ [Test Case]
+ 1. Plug the USB device to the ports of problematic root hub.
+ 2. Power on the machine.
+ 3. Check if the USB device can work or not after boot.
+ 
+ [Regression Potential]
+ Low. The longer delay is proven safe in old kernels.
+ 
+ == Original Bug Description ==
+ 
  [Summary]
  
  The USB devices (keyboard, storage...) are failed to be detected during boot 
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, 
they will be detected and working ok after re-plugging. The kernel output shows 
as down below during boot
  [ 39.350435] hub 1-0:1.0: USB hub found
  [ 39.398835] hub 1-0:1.0: 12 ports detected
  [ 39.622744] usb usb1-port3: couldn't allocate usb_device
  
  And when I plug out then plug in the same device, it shows
  [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
  [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, 
bcdDevice= 1.14
  [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  
  After doing kernel bisecting, we found the upstream commit 
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
 makes the difference. It indicates that the delay for the root hub from 
power_on to power_good is not long enough. There was no problem if the delay is 
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 
milliseconds. And the XHCI spec also says in section 5.4.8
  """
  The host is required to have power stable to the port within 20 milliseconds 
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for 
waiting 20ms.
  """
  
  The commit seems to follow the SPEC but could cause problems on some
  hubs.
  
  [Reproduce Steps]
  1. Plug the USB device to the physical port #1 and #4 which belongs to 
high-speed hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.
  
  [Results]
  Expected:
-   All usb devices connect to the hub should work OK.
+   All usb devices connect to the hub should work OK.
  
  Actual:
-   USB devices connects to high-speed hub can not be probed.
+   USB devices connects to high-speed hub can not be probed.
  
  [Additional Information]
  Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
  
  [Upstream bug]
  https://bugzilla.kernel.org/show_bug.cgi?id=214021

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

Title:
  [regression] USB device is not detected during boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]
  The USB devices (keyboard, storage...) are failed to be detected when 
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood 
delay than it claims in the hub descriptor. It's caused by the upstream fix 
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").

  
  [Fix]
  Reverting the upstream fix until a formal fix been placed.

  [Test Case]
  1. Plug the USB device to the ports of problematic root hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.

  [Regression Potential]
  Low. The longer delay is proven safe in old kernels.

  == Original Bug Description ==

  [Summary]

  The USB devices (keyboard, storage...) are failed to be detected during boot 
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, 
they will be detected and working ok after re-plugging. The kernel output shows 
as down below during boot
  [ 39.350435] hub 1-0:1.0: USB hub found
  [ 39.398835] hub 1-0:1.0: 12 ports detected
  [ 39.622744] usb usb1-port3: couldn't allocate usb_device

  And when I plug out then plug in the same device, it shows
  [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
  [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, 
bcdDevice= 1.14
  [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0

  After doing kernel bisecting, we found the upstream commit 
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
 makes the difference. It indicates that the delay for the root hub from 
power_on to power_good is not long enough. There was no problem if the delay is 
100 ms. 

[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot

[Chris Chiu]

** Tags added: austin oem-priority originate-from-1939113

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

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

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

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

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

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

Title:
  [regression] USB device is not detected during boot

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress

Bug description:
  [Summary]

  The USB devices (keyboard, storage...) are failed to be detected during boot 
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, 
they will be detected and working ok after re-plugging. The kernel output shows 
as down below during boot
  [ 39.350435] hub 1-0:1.0: USB hub found
  [ 39.398835] hub 1-0:1.0: 12 ports detected
  [ 39.622744] usb usb1-port3: couldn't allocate usb_device

  And when I plug out then plug in the same device, it shows
  [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
  [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, 
bcdDevice= 1.14
  [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0

  After doing kernel bisecting, we found the upstream commit 
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
 makes the difference. It indicates that the delay for the root hub from 
power_on to power_good is not long enough. There was no problem if the delay is 
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 
milliseconds. And the XHCI spec also says in section 5.4.8
  """
  The host is required to have power stable to the port within 20 milliseconds 
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for 
waiting 20ms.
  """

  The commit seems to follow the SPEC but could cause problems on some
  hubs.

  [Reproduce Steps]
  1. Plug the USB device to the physical port #1 and #4 which belongs to 
high-speed hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.

  [Results]
  Expected:
All usb devices connect to the hub should work OK.

  Actual:
USB devices connects to high-speed hub can not be probed.

  [Additional Information]
  Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26

  [Upstream bug]
  https://bugzilla.kernel.org/show_bug.cgi?id=214021

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


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

[Kernel-packages] [Bug 1934014] Re: [SRU] Update amdgpu/renoir firmware

[Timo Aaltonen]

still missing verification

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

Title:
  [SRU] Update amdgpu/renoir firmware

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  Renoir based systems can't resume from s2idle.

  [Fix]
  Update firmware for renoir into 21.10 or 21.20 release in linux-firmware.git
  Accompanying kernel driver updates are distributed with linux-oem-5.10.

  [Test]
  Verify s2idle on OEM system.

  [Where problems could occur]
  The firmware update is specific to Renoir systems, which are relative new so 
the impact is limited. We also have direct involvement with AMD, in case any 
regression happens.

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


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

[Kernel-packages] [Bug 1939160] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log)

[Eugeny Bachar]

Exact same behaviour for me and my collegues on HP Probook 450 G7:

HP ProBook 450 G7 (8VU58EA#ACB)
CPU: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
RAM: 16Gb
GPU: Intel UDH Graphics
Disk: SSD WDC PC SN520 SDAPNUW-512G-1006

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

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work (updated system log)

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

Bug description:
  I had previously submitted this bug here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914 , but I
  submitted a system log from an older, working version of Ubuntu rather
  than from the failing version. This report has the updated log.

  While starting the my laptop

  (Computer Model: HP Probook 450 G6
  ProdID 5YH15UT#ABA
  Memory: 15.5 GB
  Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8
  Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2)
  Disk Capacity: 256.1 GB)

  which runs

  (OS Name: Ubuntu 20.04.2 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.8
  Windowing System: X11)

  the monitor turns off as soon as Ubuntu loads. The OS loads as normal
  and my external monitor still works, but my laptop monitor does not. I
  was able to fix the problem by pressing ESC as soon as the HP logo
  appears during start-up, then selecting "Advanced Ubuntu Options",
  then choosing an older version of Ubuntu (currently that's
  ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...).

  It seems clear that this problem is caused by a bug that was
  introduced in one of the more recent updates (...5.8.0-59..., maybe?).
  I am not at all sure that the problem is in xorg; the package
  identification webpage just suggested that, if the monitor is blank
  when I would expect to see the Ubuntu logo during startup, then I
  should say that the relevant package is xorg.

  I am more than happy to run additional diagnostics that you would
  recommend if that would help you diagnose and fix the problem.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  6 10:34:40 2021
  InstallationDate: Installed on 2021-07-06 (30 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1938818] Re: Add support for packet-per-second policing

[Stefan Bader]

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

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

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

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

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

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

Title:
  Add support for packet-per-second policing

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

Bug description:
  
  * Explain the bug(s)

  It’s a missing feature in current kernel. 
   
  * brief explanation of fixes

  Cherry-pick and backport the related patches from upstream kernel.

  * How to test

  Add tc filter rule with police action, and check it is offloaded.
  For example:
  tc filter add dev enp8s0f0_0 ingress protocol ip  flower \
  dst_mac b8:ce:f6:7b:d9:24 \
  action police pkts_rate 1000 pkts_burst 100 conform-exceed drop/pipe \
  action mirred egress redirect dev enp8s0f0

  * What it could break.

  New feature, doesn't break existing features.

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


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

[Kernel-packages] [Bug 1937914] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work

[Launchpad Bug Tracker]

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

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

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

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While starting the my laptop

  (Computer Model: HP Probook 450 G6
  ProdID 5YH15UT#ABA 
  Memory: 15.5 GB
  Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8
  Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2)
  Disk Capacity: 256.1 GB) 

  which runs

  (OS Name: Ubuntu 20.04.2 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.8
  Windowing System: X11)

  the monitor turns off as soon as Ubuntu loads. The OS loads as normal
  and my external monitor still works, but my laptop monitor does not. I
  was able to fix the problem by pressing ESC as soon as the HP logo
  appears during start-up, then selecting "Advanced Ubuntu Options",
  then choosing an older version of Ubuntu (currently that's
  ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...).

  It seems clear that this problem is caused by a bug that was
  introduced in one of the more recent updates (...5.8.0-59..., maybe?).
  I am not at all sure that the problem is in xorg; the package
  identification webpage just suggested that, if the monitor is blank
  when I would expect to see the Ubuntu logo during startup, then I
  should say that the relevant package is xorg.

  I am more than happy to run additional diagnostics that you would
  recommend if that would help you diagnose and fix the problem.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 24 14:28:51 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:8538]
 Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542]
  InstallationDate: Installed on 2021-07-06 (17 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. 
   Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/27/2020
  dmi.bios.vendor: HP
  dmi.bios.version: R71 Ver. 01.11.01
  dmi.board.name: 8538
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 51.2A.00
  dmi.chassis.asset.tag: 5CD9308H3X
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 450 G6
  dmi.product.sku: 5YH15UT#ABA
  dmi.sys.vendor: HP
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1939160] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work (updated system log)

[Launchpad Bug Tracker]

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

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

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

Title:
  [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older
  kernel versions work (updated system log)

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

Bug description:
  I had previously submitted this bug here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914 , but I
  submitted a system log from an older, working version of Ubuntu rather
  than from the failing version. This report has the updated log.

  While starting the my laptop

  (Computer Model: HP Probook 450 G6
  ProdID 5YH15UT#ABA
  Memory: 15.5 GB
  Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8
  Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2)
  Disk Capacity: 256.1 GB)

  which runs

  (OS Name: Ubuntu 20.04.2 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.8
  Windowing System: X11)

  the monitor turns off as soon as Ubuntu loads. The OS loads as normal
  and my external monitor still works, but my laptop monitor does not. I
  was able to fix the problem by pressing ESC as soon as the HP logo
  appears during start-up, then selecting "Advanced Ubuntu Options",
  then choosing an older version of Ubuntu (currently that's
  ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...).

  It seems clear that this problem is caused by a bug that was
  introduced in one of the more recent updates (...5.8.0-59..., maybe?).
  I am not at all sure that the problem is in xorg; the package
  identification webpage just suggested that, if the monitor is blank
  when I would expect to see the Ubuntu logo during startup, then I
  should say that the relevant package is xorg.

  I am more than happy to run additional diagnostics that you would
  recommend if that would help you diagnose and fix the problem.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  6 10:34:40 2021
  InstallationDate: Installed on 2021-07-06 (30 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1939673] Re: Update the 470 and the 470-server NVIDIA drivers

[Alberto Milone]

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
   Status: New => In Progress

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  In Progress
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  In Progress

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

*

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


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

[Kernel-packages] [Bug 1939673] [NEW] Update the 470 and the 470-server NVIDIA drivers

[Alberto Milone]

Public bug reported:

Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
Focal, Hirsute.

[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates

Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.

[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.

[Discussion]

[Changelog]

== 470.57.02 (470-server) ==

  *

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: Triaged

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

** Affects: nvidia-graphics-drivers-470 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470 (Ubuntu Focal)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470-server (Ubuntu Focal)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
 Status: New

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

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

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

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

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Bionic)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-470-server (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  Update the 470 and the 470-server NVIDIA drivers

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 source package in Bionic:
  New
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-470 source package in Focal:
  New
Status in nvidia-graphics-drivers-470-server source package in Focal:
  New
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  New
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  New

Bug description:
  Update the 470 (UDA) and 470-server (ERD) NVIDIA series in Bionic,
  Focal, Hirsute.

  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  

[Kernel-packages] [Bug 1936899] Re: [IoTG] [TGL-H] TPM tests fail

[Anthony Wong]

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

** Changed in: intel
   Status: New => Invalid

** Changed in: intel
   Importance: Critical => Undecided

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

Title:
  [IoTG] [TGL-H] TPM tests fail

Status in intel:
  Invalid
Status in linux-intel package in Ubuntu:
  Invalid

Bug description:
  [Summary]TPM tests from CDTS 20 automated fail

  [Steps to reproduce]Run cdts.odm_certification, select TPM

  [Expected result]All tests should pass.

  [Actual result]
  Failed Jobs (TPM 2.0):
  tpm2.0_4.1.1/tpm2_clockratedadjust
  tpm2.0_4.1.1/tpm2_createprimary
  tpm2.0_4.1.1/tpm2_import
  tpm2.0_4.1.1/tpm2_loadexternal

  Jobs with failed dependencies
  tpm2.0_4.1.1/tpm2_rc_decode

  [Failure rate]100%

  [Additional information]
  CID: 202106-29175
  SKU: 
  system-manufacturer: Intel Corporation
  system-product-name: Tiger Lake Client Platform
  bios-version: TGLIFUI1.R00.3455.A03.2011281547
  CPU: Genuine Intel(R) CPU  @ 2.60GHz (16x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9a60]
  kernel-version: 5.11.0-1009-intel


  [Stage]
  Issue reported and logs collected right after it happened

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


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

[Kernel-packages] [Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E

[koba]

** No longer affects: linux-oem (Ubuntu)

** No longer affects: linux-oem (Ubuntu Focal)

** No longer affects: linux-oem (Ubuntu Hirsute)

** No longer affects: linux-oem (Ubuntu Impish)

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

Title:
  Fix Ethernet not working by hotplug - RTL8106E

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-oem-5.13 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.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  After hot-plug the Ethernet cable, the status of Ethernet is always down.

  [Fix]
  Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired 
immediately.
  Must wait a long time to get the link change interrupt.
  After discuss with maintainer, he give some suggestions
  1. use PHY_POLL.
  2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E.

  For 2, because don't know the details about operated registers in
  rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during
  suspend.

  For 1, Use PHY_POLL have a lower risk because don't change any register 
operations and use polling method to query link change status.
  SRU the patches for 1 first.

  Currently keep discussing with Realtek but don't figure out yet.
  Will re-SRU the official solution once Realtek resolve the issue.

  Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207

  [Test]
  Verified on machines with Realtek Ethernet device, the Ethernet works well 
after hotplug 30 times.

  [Regression Potential]
  Medium, use polling methond may have higher cpu usage.

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


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

[Kernel-packages] [Bug 1938143] Re: Include product_sku info to modalias

[Stefan Bader]

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

** Changed in: linux (Ubuntu Hirsute)
   Importance: Medium => Wishlist

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

Title:
  Include product_sku info to modalias

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

Bug description:
  [Impact]
  When we add DMI quirks for the new platforms, it's hard to prevent from 
leaking its model name. Our customer doesn't like it.

  [Fix]
  Introduce the product sku modalias to DMI table, so that we can use more 
meaningless product sku string to match the platform.

  [Test]
  No real DMI quirk is added in this commit, so need to do any tests.

  [Where problems could occur]
  It's safe to add one more DMI entry, nothing could be affected.

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


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

[Kernel-packages] [Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS

[Frank Heimes]

Well, this is a patch set of 34 commits, which is significant, and looks
to me that they cover much more than just fixing "EP11 cards going
offline", rather than bringing the entire driver to the latest level.
The usual way is to pick the minimal set of patches that fix a
particular issue and get these SRUed.

And btw. this is a relatively unusual way of sharing patches or backports -- if 
about a handful of patches (or two) are needed, we would do cherry-picks or 
apply selective backport patch-files.
In case of more patches the usual way is a branch with a pull-request.

But the patches seem to apply cleanly to the current focal master-next
tree and touch s390x specific files only (either in /arch/s390/ or in
/drivers/s390/).

Please notice that hirsute's 5.11 kernel would need to be on the same
level, to avoid any potential regressions on upgrades.

I'll bring this to the kernel teams attention and we'll discuss if this
is doable as SRU.


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

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel 
Team (canonical-kernel-team)

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

Title:
  EP11 cards going offline => Fix backport to U20.04LTS

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

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


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

[Kernel-packages] [Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock

[AaronMa]

I am trying to find T490 to reproduce.
Please wait a while.

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

Title:
  External displays not working on Thinkpad T490 with ThinkPad
  Thunderbolt 3 Dock

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have two external displays chained via Display port connected to the
  ThinkPad Thunderbolt 3 Dock.

  They are working with kernel 5.8.0-63 but not with the new 5.11.0-25
  kernel.

  I could reproduce this behavior several times for both kernels, as
  follows: I booted up with disconnected dock, logged in, then I
  connected it, disconnected it, and connected it again.

  With the 5.11.0-25 kernel the external displays go black; the main
  screen turns off and on several times. Sometimes the main screen
  remains working, but UI is lagging.

  I'm attaching the logs. Two separate boots for each variant are marked
  'a'/'b'.

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


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

[Kernel-packages] [Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E

[Stefan Bader]

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

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

Title:
  Fix Ethernet not working by hotplug - RTL8106E

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem source package in Focal:
  New
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem source package in Hirsute:
  New
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem source package in Impish:
  New
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  After hot-plug the Ethernet cable, the status of Ethernet is always down.

  [Fix]
  Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired 
immediately.
  Must wait a long time to get the link change interrupt.
  After discuss with maintainer, he give some suggestions
  1. use PHY_POLL.
  2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E.

  For 2, because don't know the details about operated registers in
  rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during
  suspend.

  For 1, Use PHY_POLL have a lower risk because don't change any register 
operations and use polling method to query link change status.
  SRU the patches for 1 first.

  Currently keep discussing with Realtek but don't figure out yet.
  Will re-SRU the official solution once Realtek resolve the issue.

  Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207

  [Test]
  Verified on machines with Realtek Ethernet device, the Ethernet works well 
after hotplug 30 times.

  [Regression Potential]
  Medium, use polling methond may have higher cpu usage.

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


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

[Kernel-packages] [Bug 1939222] Re: DisplayPort over USB-C not working after release update

[AaronMa]

Could you try 5.13 kernel too?
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13/amd64/

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

Title:
  DisplayPort over USB-C not working after release update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After (automated) update from 5.8.0-63 to 5.11.0.-25 the displayport over 
usb-c (Thinkpad e15gen2 i5-1135G7 / GeForce MX450/PCIe/SSE2) is not working 
properly.
  Revert to 5.8.0-63 resolves the problem.
  The problem is independent of nvdia-drivers (tried 470, 460 and intel only  
drivers). Same Monitors connected over HDMI work properly. Problem is limited 
to displayport over usb-c.

  Problem symptoms: Monitor atttached over displayport allows only VGA 
resolution(1024 * 768)  and
  flickers (on/off periodically). 

  no special error messages found in dmesg except for abundance of
  "i915 :00:02.0: [drm] *ERROR* failed to enable link training"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.35
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 09:12:10 2021
  InstallationDate: Installed on 2021-06-14 (54 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IL
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

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


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

[Kernel-packages] [Bug 1939638] Re: [regression] USB device is not detected during boot

[Anthony Wong]

** Summary changed:

- USB device is not detected during boot
+ [regression] USB device is not detected during boot

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

Title:
  [regression] USB device is not detected during boot

Status in linux package in Ubuntu:
  New

Bug description:
  [Summary]

  The USB devices (keyboard, storage...) are failed to be detected during boot 
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However, 
they will be detected and working ok after re-plugging. The kernel output shows 
as down below during boot
  [ 39.350435] hub 1-0:1.0: USB hub found
  [ 39.398835] hub 1-0:1.0: 12 ports detected
  [ 39.622744] usb usb1-port3: couldn't allocate usb_device

  And when I plug out then plug in the same device, it shows
  [57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
  [57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099, 
bcdDevice= 1.14
  [57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0

  After doing kernel bisecting, we found the upstream commit 
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
 makes the difference. It indicates that the delay for the root hub from 
power_on to power_good is not long enough. There was no problem if the delay is 
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2 
milliseconds. And the XHCI spec also says in section 5.4.8
  """
  The host is required to have power stable to the port within 20 milliseconds 
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for 
waiting 20ms.
  """

  The commit seems to follow the SPEC but could cause problems on some
  hubs.

  [Reproduce Steps]
  1. Plug the USB device to the physical port #1 and #4 which belongs to 
high-speed hub.
  2. Power on the machine.
  3. Check if the USB device can work or not after boot.

  [Results]
  Expected:
All usb devices connect to the hub should work OK.

  Actual:
USB devices connects to high-speed hub can not be probed.

  [Additional Information]
  Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26

  [Upstream bug]
  https://bugzilla.kernel.org/show_bug.cgi?id=214021

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


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

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

[Kai-Heng Feng]

But that commit didn't modify any file...

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  - 4.20.0-rc7

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585: https://evilazrael.de/node/401

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1939618] Re: EP11 cards going offline => Fix backport to U20.04LTS

[Frank Heimes]

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

Title:
  EP11 cards going offline => Fix backport to U20.04LTS

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

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


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