[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]

[Alex Tu]

@Zorro, We can not reproduce the AX201 wifi crashing issue with new
firmware #9 + kernel 5.10.0-1037-oem on the machine XPS 13 TGL in the
certification pool. But it happens to Steve's XPS 13 TGL.

Could you please check if this issue can be reproduced on other XPS 13
TGL + AX201 wifi[8086:a0f0] you have?

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

Title:
  [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
  wireless [8086:a0f0]

Status in Linux Firmware:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Whenever I am using a wireless connection, the image freezes roughly
  every two minutes. Sometimes, email cannot be retrieved / computer
  complains the connection was momentarily lost.

  - If I am on a wire, this problem does NOT occur.
  - This problems occurs on wireless independent of the platform used (behavior 
seen in both Google Hangout and Zoom)
  - This problem does NOT occur on Windows. I did a meeting where both my Linux 
and Windows machines were connected to the same meeting and using the same wifi 
router, and while the performance on Windows was flawless, unfortunately it was 
not so on the Ubuntu box. So I don't think my wifi router or network is to 
blame.
  - As far as I can recall, the problem used not to be there 2 weeks ago. So it 
may have been introduced by a recent update.
  - As communicated before, I am on a certified machine from Dell, recently 
purchased with Ubuntu already on board from factory (I assume the logs there 
were sent to you would contain the information).
  - I tried to generate a log on the wireless, but the process did not let me 
do this very easily. I am more than happy to send you additional information - 
but please let me know which package you want me to spy upon exactly, as I am 
not sure what would be helpful in this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
  Uname: Linux 5.10.0-1029-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 18 09:47:58 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0991]
  InstallationDate: Installed on 2021-04-24 (54 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem 
root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 2.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.1
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux-firmware/+bug/1932548/+subscriptions


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

[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Daniel van Vugt]

Seems there's a bug in Launchpad preventing me from creating the missing
focal and hirsute tasks. Let's see if deleting them all and recreating
them helps...

** No longer affects: bluez (Ubuntu Hirsute)

** No longer affects: bluez (Ubuntu Focal)

** Also affects: gnome-settings-daemon (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: bluez (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: gnome-settings-daemon (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: bluez (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: bluez (Ubuntu Hirsute)
   Status: New => Fix Released

** Changed in: bluez (Ubuntu Focal)
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: bluez (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: bluez (Ubuntu Hirsute)
   Importance: Undecided => High

** Changed in: bluez (Ubuntu Hirsute)
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: gnome-settings-daemon (Ubuntu Focal)
   Status: New => In Progress

** Changed in: gnome-settings-daemon (Ubuntu Focal)
 Assignee: (unassigned) => Andy Chi (andch)

** Changed in: gnome-settings-daemon (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: gnome-settings-daemon (Ubuntu Hirsute)
 Assignee: (unassigned) => Andy Chi (andch)

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in gnome-settings-daemon source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  Fix Released
Status in gnome-settings-daemon source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST

[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device

[Hui Wang]

Installed the ubuntu 18.04 to that Dell machine with usb c-media audio
card, enable the -proposed channel and install the alsa-lib
1.1.3-5ubuntu0.6, reboot, open the gnome-sound-setting, there is no
SPDIF in the output device anymore.

Verified on the bionic, it worked very well.


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

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

Title:
  [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-
  Audio.pcm.iec958_device

Status in OEM Priority Project:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-lib source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.

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

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

  [Where problems will occur]
  "Cmedia Audio" is the sound card name of this usb audio dongle, and this 
string is got from usb string descriptor, that is to say the "Cmedia Audio" is 
hard-coded in the firmware of that usb dongle.
  Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't 
set string descriptor, then the audio driver sets a generic name "USB Audio 
Device" for them, if a dongle has string descriptor, it may have different 
string like "C-Media USB Headphone Set", and all dongles I met before don't 
have SPDIF interface.
  So If this SRU could introduce regression, it will happen on a Cmedia usb 
audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor 
and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF 
playback device from the gnome-sound-setting. But this regression chance is 
very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in 
the string descriptor and it is very rare a usb audio dongle has SPDIF 
interface. So far we haven't met such a cmedia usb audio dongle.

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


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

[Kernel-packages] [Bug 1934414] Re: test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with linux/4.15.0-149.153 i386 (Segmentation fault)

[Po-Hsu Lin]

** Summary changed:

- test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with 
linux/4.15.0-149.153
+ test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test failure with 
linux/4.15.0-149.153 i386 (Segmentation fault)

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

Title:
  test_bpf.sh from ubuntu_kernel_selftests.net from linux ADT test
  failure with linux/4.15.0-149.153 i386 (Segmentation fault)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/4.15.0-149.153 on bionic. Whether this is caused by
  the dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  i386: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210702_010055_445cd@/log.gz

  
  03:37:02 DEBUG| [stdout] selftests: test_bpf.sh
  03:37:02 DEBUG| [stdout] 
  03:37:03 ERROR| [stderr] Segmentation fault
  03:37:03 DEBUG| [stdout] test_bpf: [FAIL]
  03:37:03 DEBUG| [stdout] not ok 1..8 selftests:  test_bpf.sh [FAIL]
  03:37:03 DEBUG| [stdout] selftests: netdevice.sh
  03:37:03 DEBUG| [stdout] 

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


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

[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Andy Chi]

** Tags added: originate-from-1936277

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Fix Released
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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


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

[Kernel-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

[Daniel van Vugt]

*** This bug is a duplicate of bug 1926062 ***
https://bugs.launchpad.net/bugs/1926062

Now is a good time to mark this as a duplicate of bug 1926062 since
they're the same bug.

** This bug has been marked a duplicate of bug 1926062
   [hirsute/impish] Can't turn bluetooth on again after turning it off

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released
Status in bluez source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in
  kernels 5.11 (approximately) onward. Devices are not refreshed in the
  list anymore.

  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

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


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

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

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2021-07-14 20:44 EDT---
IBM bugzilla status->closed, Fix Released for all requested distros

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

Title:
  [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink

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

Bug description:
  SRU Justification:
  ==

  [Impact]

  * In addition to 9c9be85f6b59 "net/mlx5e: Add missing capability check
  for uplink follow" (handled in LP#1921104) another fix 1a73704c82ed
  "Fix HW spec violation configuring uplink" (handled in this bug,
  LP#1925452) is needed to fix issues that were introduced with commit
  7d0314b11cdd "net/mlx5e: Modify uplink state on interface up/down".

  * Commit 1a73704c82ed "Fix HW spec violation configuring uplink" fixes
  a regression for mlx5 adapters required to operate in switchdev mode.

  * This fix makes sure that the uplink port is modified to follow only
  if the uplink_follow capability if it's set as required by the hw
  specification.

  * Failure cause traffic to the uplink representer net device to cease
  after switching to switchdev mode.

  [Fix]

  * upstream fix (upstream with v5.12-rc7)
  1a73704c82ed4ee95532ac04645d02075bd1ce3d 1a73704c82ed "Fix HW spec violation 
configuring uplink"

  * can be cleanly cherry picked from hirsute master-next.

  * a backport for groovy:
  
https://launchpadlibrarian.net/534888680/groovy-0001-net-mlx5-Fix-HW-spec-violation-configuring-uplink.patch

  * a backport for focal:
  
https://launchpadlibrarian.net/534847308/focal-0001-net-mlx5-Fix-HW-spec-violation-configuring-uplink.patch

  [Test Case]

  * Two servers, installed with Ubuntu Server 20.04 or 20.10 are needed.

  * Each server needs to have a Mellanox ConnectX4/5 adapter, attached
  to the same switch

  * Adapters must be running adapter firmware level 16.29.1006 or
  earlier.

  * enable SRIOV and switchdev mode on one adapter:
    echo 0 > /sys/bus/pci/devices/0100\:00\:00.0/sriov_drivers_autoprobe
    echo 0 > /sys/bus/pci/devices/0100\:00\:00.1/sriov_drivers_autoprobe
    echo 64 > /sys/bus/pci/devices/0100\:00\:00.0/sriov_numvfs
    echo 64 > /sys/bus/pci/devices/0100\:00\:00.1/sriov_numvfs
    devlink dev eswitch set pci/0100:00:00.0 mode switchdev
    devlink dev eswitch set pci/0100:00:00.1 mode switchdev

  * Assign an IP address to the physical function device of the adapters
  on both systems

  * IP communication will fail

  * With the fix, IP communication can be established.

  [Regression Potential]

  * There is always at least some potential for regression. In this case
  the new code can go wrong (or might become worse than before) in case
  the new if statement is wrong.

  * It checks for the condition of "MLX5_CAP_GEN(mdev, uplink_follow)"
  and in case MLX5_CAP_GEN is calculated erroneous or mdev is other than
  expected, the mlx5_modify_vport_admin_state call might go wrong, too.

  * But since only the If clause was added, the changes are pretty
  minimal and therefore well traceable.

  [Other]

  * Since the patch/commit is upstream with 5.12-rc7, it will be in Impish.
  __

  With the 5.4.0-48 update for Ubuntu 20.04, the commit

  "net/mlx5e: Modify uplink state on interface up/down"

  was integrated which contains a regression for mlx5 adapters with
  older adapter firmware.

  This is the second bugfix to repair the regression, required to operate the 
adapter in switchdev mode.
  The first part was integrated via Bug 192185 - LP1921104.

  This is the upstream fix required to be backported to Ubuntu 20.04:
  
https://github.com/torvalds/linux/commit/1a73704c82ed4ee95532ac04645d02075bd1ce3d

  ---Additional Hardware Info---
  Mellanox ConnectX network adapter

  ---uname output---
  5.4.0-73-generic

  ---Steps to Reproduce---
   enable switchdev mode
  try to ping external host

  Backports need to be provide for 21.04, 20.10 and 20.04 (if not
  cleanly applyable)!

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


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

[Kernel-packages] [Bug 1936211] Re: Cherry-pick "Remove iov_iter_advance() for iter_write"

[Launchpad Bug Tracker]

This bug was fixed in the package zfs-linux - 2.0.3-8ubuntu6

---
zfs-linux (2.0.3-8ubuntu6) impish; urgency=medium

  [ Mo Zhou ]
  * Cherry-pick "Remove iov_iter_advance() for iter_write" (LP: #1936211)
- sync with change between Debian zfs-linux 2.0.3-8 and 2.0.3-9 (Closes: 
#989373)

 -- Colin Ian King   Wed, 14 Jul 2021 14:03:17
+0100

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

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

Title:
  Cherry-pick "Remove iov_iter_advance() for iter_write"

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Hirsute:
  New
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Debian zfs 2.0.3-9 contains the cherry-pick "Remove iov_iter_advance()
  for iter_write", Debian bug #989373.  Apply this fix to zfs 2.0.3.x in
  Impish

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


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

[Kernel-packages] [Bug 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 / F-GKE 5.4

[Guilherme G. Piccoli]

Observed in G/Oracle, cycle sru-20210621.

** Tags added: groovy sru-20210621

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

Title:
  test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP
  5.3 / F-GKE 5.4

Status in ubuntu-kernel-tests:
  Triaged
Status in linux-aws package in Ubuntu:
  New
Status in linux-gcp package in Ubuntu:
  New
Status in linux-aws source package in Bionic:
  New
Status in linux-gcp source package in Bionic:
  New
Status in linux-aws source package in Eoan:
  New
Status in linux-gcp source package in Eoan:
  New

Bug description:
  The test_blackhole_dev from net in ubuntu_kernel_selftests failed on
  B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp)

   # selftests: net: test_blackhole_dev.sh
   # test_blackhole_dev: [FAIL]
   not ok 13 selftests: net: test_blackhole_dev.sh

  Need to run this manually to see what's going on there.

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


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

[Kernel-packages] [Bug 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail with timeout if running the whole suite

[Guilherme G. Piccoli]

Observed in G/Oracle, cycle sru-20210621.

** Tags added: oracle

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

Title:
  xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in
  ubuntu_kernel_selftests will fail with timeout if running the whole
  suite

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Opinion
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-5.6 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Opinion
Status in linux-oem-5.6 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  Opinion
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Opinion
Status in linux-oem-5.6 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Opinion
Status in linux-oem-5.6 source package in Impish:
  Invalid

Bug description:
  [Impact]
  These 3 tests will fail with timeout error when running the whole
  "net" test in ubuntu_kernel_selftests:
    * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT
    * not ok 16 selftests: net: pmtu.sh # TIMEOUT
    * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT

  They will pass if you run them manually. This is because of the
  default 45 seconds timeout in kselftest framework.

  A quick test shows these tests will take about:
xfrm_policy.sh - 2m19.690s
pmtu.sh - 3m6.832s
udpgso_bench.sh - 0m57.985s

  [Fix]
  * b881d089c7c9c7 ("selftests/net: bump timeout to 5 minutes")

  We have commit 852c8cbf34d3b3 ("selftests/kselftest/runner.sh: Add 45
  second timeout per test") for default timeout added since Bionic.

  However there is a SAUCE patch ("UBUNTU: SAUCE: selftests/net --
  disable timeout") to disable timeout for the net test in newer
  releases. I think we can leave it as-is for the moment unless some
  test is hanging too long because of that.

  Therefore Only Bionic needs this patch, the patch can be applied with
  some context adjustment.

  [Test]
  With this patch applied, these tests should have a chance to finish.

  [Where problems could occur]
  The fix is just for testing tool, no actual impact to real kernel
  functions. If this 5 minutes timeout is not enough, we might still
  seeing this kind of failures in the test report.


  [Original Bug Report]
  These 3 tests will fail with timeout when running the whole "net" test in 
ubuntu_kernel_selftests:
    * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT
    * not ok 16 selftests: net: pmtu.sh # TIMEOUT
    * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT

  However they will pass if you run them manually.

  So there must be some test in net that will cause this.

  From the test result it looks like the test was executed in the following 
sequence:
   ok 1 selftests: net: reuseport_bpf
   ok 2 selftests: net: reuseport_bpf_cpu
   ok 3 selftests: net: reuseport_bpf_numa
   ok 4 selftests: net: reuseport_dualstack
   # Successok 5 selftests: net: reuseaddr_conflict
   ok 6 selftests: net: tls
   ok 7 selftests: net: run_netsocktests
   ok 8 selftests: net: run_afpackettests
   ok 9 selftests: net: test_bpf.sh
   ok 10 selftests: net: netdevice.sh
   ok 11 selftests: net: rtnetlink.sh
   not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT
   not ok 13 selftests: net: test_blackhole_dev.sh # exit=1
   ok 14 selftests: net: fib_tests.sh
   ok 15 selftests: net: fib-onlink-tests.sh
   not ok 16 selftests: net: pmtu.sh # TIMEOUT
   ok 17 selftests: net: udpgso.sh
   not ok 18 selftests: net: ip_defrag.sh # exit=255
   not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT
   ok 20 selftests: net: fib_rule_tests.sh
   not ok 21 selftests: net: msg_zerocopy.sh # exit=1
   ok 22 selftests: net: psock_snd.sh
   ok 23 selftests: net: udpgro_bench.sh
   ok 24 selftests: net: udpgro.sh
   ok 25 selftests: net: test_vxlan_under_vrf.sh
   ok 26 selftests: net: reuseport_addr_any.sh
   ok 27 selftests: net: test_vxlan_fdb_changelink.sh
   ok 28 selftests: net: so_txtime.sh
   ok 29 selftests: net: ipv6_flowlabel.sh
   ok 30 selftests: net: tcp_fastopen_backup_key.sh

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10
  ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13
  Uname: Linux 5.3.0-1009-aws aarch64
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: arm64
  Date: Wed Dec 11 06:42:39 2019
  Ec2AMI: ami-047cec24582f6ae0d
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2c
  Ec2InstanceType: a1.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1936255] [NEW] New upstream release 2021.07.14

[Seth Forshee]

Public bug reported:

[Impact]

New upstream release. This is a database of wireless regulations, and
should updated in all releases to ensure users have the most up-to-date
regulatory information.

[Test Case]

Following reboot after installing the new database, it should be
possible to query and change the regulatory domain using 'iw reg get'
and 'iw reg set'.

[Where problems could occur]

If crda or the kernel is unable to use the new database, users may be
stuck using the default "world" regulatory domain which is quite
restrictive, therefore they may be unable to use wireless channels that
they were able to use previously. Regulatory rules may have also changed
for the user's region, which could also make some channels unusable, but
this would not be a bug.

** Affects: wireless-regdb (Ubuntu)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: wireless-regdb (Ubuntu Trusty)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: wireless-regdb (Ubuntu Xenial)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: wireless-regdb (Ubuntu Bionic)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: wireless-regdb (Ubuntu Focal)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: wireless-regdb (Ubuntu Groovy)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: wireless-regdb (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Affects: wireless-regdb (Ubuntu Impish)
 Importance: Medium
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

** Also affects: wireless-regdb (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Impish)
   Importance: Medium
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

** Also affects: wireless-regdb (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: wireless-regdb (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: wireless-regdb (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: wireless-regdb (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: wireless-regdb (Ubuntu Trusty)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: wireless-regdb (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: wireless-regdb (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: wireless-regdb (Ubuntu Xenial)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: wireless-regdb (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: wireless-regdb (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: wireless-regdb (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: wireless-regdb (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: wireless-regdb (Ubuntu Focal)
   Status: New => In Progress

** Changed in: wireless-regdb (Ubuntu Focal)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: wireless-regdb (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: wireless-regdb (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: wireless-regdb (Ubuntu Groovy)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: wireless-regdb (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: wireless-regdb (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: wireless-regdb (Ubuntu Hirsute)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  New upstream release 2021.07.14

Status in wireless-regdb package in Ubuntu:
  In Progress
Status in wireless-regdb source package in Trusty:
  In Progress
Status in wireless-regdb source package in Xenial:
  In Progress
Status in wireless-regdb source package in Bionic:
  In Progress
Status in wireless-regdb source package in Focal:
  In Progress
Status in wireless-regdb source package in Groovy:
  In Progress
Status in wireless-regdb source package in Hirsute:
  In Progress
Status in wireless-regdb source package in Impish:
  In Progress

Bug description:
  [Impact]

  New upstream release. This is a database of wireless regulations, and
  should updated in all 

[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )

[Brian Murray]

** Changed in: libatasmart (Ubuntu Yakkety)
   Status: Confirmed => Won't Fix

** Changed in: libatasmart (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

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

Title:
  constantly shows wrong temperature (99°C )

Status in libatasmart:
  Unknown
Status in libatasmart package in Ubuntu:
  Triaged
Status in libatasmart source package in Trusty:
  Won't Fix
Status in libatasmart source package in Xenial:
  Confirmed
Status in libatasmart source package in Yakkety:
  Won't Fix

Bug description:
  Hello, here's my system info

  ~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ~$ apt-cache policy udisks2
  udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
   *** 2.1.7-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C 
(210°F), but in reality it's 30°C

  
  ~$ sudo smartctl -A /dev/sda
  smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
  Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

  === START OF READ SMART DATA SECTION ===
  SMART Attributes Data Structure revision number: 16
  Vendor Specific SMART Attributes with Thresholds:
  ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b   100   100   050Pre-fail  Always  
 -   0
9 Power_On_Hours  0x0012   100   100   000Old_age   Always  
 -   24
   12 Power_Cycle_Count   0x0012   100   100   000Old_age   Always  
 -   51
  168 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   0
  170 Unknown_Attribute   0x0003   100   100   010Pre-fail  Always  
 -   231
  173 Unknown_Attribute   0x0012   100   100   000Old_age   Always  
 -   65539
  192 Power-Off_Retract_Count 0x0012   100   100   000Old_age   Always  
 -   23
  194 Temperature_Celsius 0x0023   070   070   030Pre-fail  Always  
 -   30 (Min/Max 30/30)
  218 Unknown_Attribute   0x000b   100   100   050Pre-fail  Always  
 -   0
  231 Temperature_Celsius 0x0013   100   100   000Pre-fail  Always  
 -   99
  241 Total_LBAs_Written  0x0012   100   100   000Old_age   Always  
 -   337


  in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
  works well though:

  ~$ sudo hddtemp /dev/sda
  /dev/sda: PNY EU SSD CS1311 240GB: 30°C

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


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

[Kernel-packages] [Bug 1926142] Re: memfd from ubuntu_kernel_selftests failed to build on B-5.4

[Sean Feole]

** Tags added: hinted

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

Title:
  memfd from ubuntu_kernel_selftests failed to build on B-5.4

Status in ubuntu-kernel-tests:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in linux-hwe source package in Bionic:
  New
Status in linux-hwe-5.4 source package in Bionic:
  New

Bug description:
  Test build on B-5.4 (5.4.0-73.82~18.04.1) failed with:
error: ‘F_SEAL_FUTURE_WRITE’ undeclared

  Build log:
  $ sudo make TARGETS=memfd
  make --no-builtin-rules ARCH=x86 -C ../../.. headers_install
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  gcc -D_FILE_OFFSET_BITS=64 -I../../../../include/uapi/ -I../../../../include/ 
-I../../../../usr/include/memfd_test.c common.o  -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test
  memfd_test.c: In function ‘test_seal_future_write’:
  memfd_test.c:749:27: error: ‘F_SEAL_FUTURE_WRITE’ undeclared (first use in 
this function); did you mean ‘F_SEAL_WRITE’?
mfd_assert_add_seals(fd, F_SEAL_FUTURE_WRITE);
 ^~~
 F_SEAL_WRITE
  memfd_test.c:749:27: note: each undeclared identifier is reported only once 
for each function it appears in
  ../lib.mk:141: recipe for target 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test'
 failed
  make[1]: *** 
[/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd/memfd_test]
 Error 1
  make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/memfd'
  Makefile:143: recipe for target 'all' failed
  make: *** [all] Error 2

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


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

[Kernel-packages] [Bug 1936245] [NEW] Focal update: v5.4.131 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.4.131 upstream stable release
   from git://git.kernel.org/

KVM: SVM: Periodically schedule when unregistering regions on destroy
s390/stack: fix possible register corruption with stack switch helper
KVM: SVM: Call SEV Guest Decommission if ASID binding fails
xen/events: reset active flag for lateeoi events later
Linux 5.4.131
UBUNTU: upstream stable to v5.4.131

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

** Description changed:

+ SRU Justification
  
- 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:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.131 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.131 upstream stable release
-from git://git.kernel.org/
+ KVM: SVM: Periodically schedule when unregistering regions on destroy
+ s390/stack: fix possible register corruption with stack switch helper
+ KVM: SVM: Call SEV Guest Decommission if ASID binding fails
+ xen/events: reset active flag for lateeoi events later
+ Linux 5.4.131
+ UBUNTU: upstream stable to v5.4.131

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

Title:
  Focal update: v5.4.131 upstream stable release

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

Bug description:
  SRU Justification

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

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

  KVM: SVM: Periodically schedule when unregistering regions on destroy
  s390/stack: fix possible register corruption with stack switch helper
  KVM: SVM: Call SEV Guest Decommission if ASID binding fails
  xen/events: reset active flag for lateeoi events later
  Linux 5.4.131
  UBUNTU: upstream stable to v5.4.131

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


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

[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Sønke Lorenzen]

You have to install another driver than nvidia-driver-460 in order to
update all your packages again. This is because nvidia-driver-460 does
have the version 460.80 in the repositories now.

Easiest is to change to nvidia-driver-460-server if that works for you,
next easiest is to enable the PPA I mentioned above to install the 470
beta driver.

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

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? rm_init_adapter+0xc5/0xe0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nv_open_device+0x122/0x8e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_open+0x2b7/0x560 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_frontend_open+0x58/0xa0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? chrdev_open+0xf7/0x220
  Jun 03 16:26:57 willow kernel:  ? cdev_device_add+0x90/0x90
  Jun 03 16:26:57 willow kernel:  ? do_dentry_open+0x156/0x370
  Jun 03 16:26:57 willow kernel:  ? vfs_open+0x2d/0x30
  Jun 03 16:26:57 willow kernel:  ? do_open+0x1c3/0x340
  Jun 03 16:26:57 willow kernel:  ? path_openat+0x10a/0x1d0
  Jun 03 16:26:57 willow kernel:  ? do_filp_open+0x8c/0x130
  Jun 03 16:26:57 willow kernel:  ? __check_object_size+0x1c/0x20
  Jun 03 16:26:57 willow kernel:  ? do_sys_openat2+0x9b/0x150
  Jun 03 16:26:57 willow kernel:  ? __x64_sys_openat+0x56/0x90
  Jun 03 16:26:57 willow kernel:  ? do_syscall_64+0x38/0x90
  Jun 03 16:26:57 willow kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) 
zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) >
  Jun 03 16:26:57 willow kernel:  sunrpc ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c>
  Jun 03 16:26:57 willow kernel: CR2: 0170
  Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]---
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  

[Kernel-packages] [Bug 1936244] [NEW] Focal update: v5.4.130 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.4.130 upstream stable release
   from git://git.kernel.org/

scsi: sr: Return appropriate error code when disk is ejected
drm/nouveau: fix dma_address check for CPU/GPU sync
gpio: AMD8111 and TQMX86 require HAS_IOPORT_MAP
UBUNTU: [Config] update annotations for GPIO_TQMX86
RDMA/mlx5: Block FDB rules when not in switchdev mode
Linux 5.4.130
UBUNTU: upstream stable to v5.4.130

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

** Description changed:

+ SRU Justification
  
- 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:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    v5.4.130 upstream stable release
+    from git://git.kernel.org/
  
-v5.4.130 upstream stable release
-from git://git.kernel.org/
+ scsi: sr: Return appropriate error code when disk is ejected
+ drm/nouveau: fix dma_address check for CPU/GPU sync
+ gpio: AMD8111 and TQMX86 require HAS_IOPORT_MAP
+ UBUNTU: [Config] update annotations for GPIO_TQMX86
+ RDMA/mlx5: Block FDB rules when not in switchdev mode
+ Linux 5.4.130
+ UBUNTU: upstream stable to v5.4.130

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

Title:
  Focal update: v5.4.130 upstream stable release

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

Bug description:
  SRU Justification

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

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

  scsi: sr: Return appropriate error code when disk is ejected
  drm/nouveau: fix dma_address check for CPU/GPU sync
  gpio: AMD8111 and TQMX86 require HAS_IOPORT_MAP
  UBUNTU: [Config] update annotations for GPIO_TQMX86
  RDMA/mlx5: Block FDB rules when not in switchdev mode
  Linux 5.4.130
  UBUNTU: upstream stable to v5.4.130

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


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

[Kernel-packages] [Bug 1876684] Re: fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed

[Krzysztof Kozlowski]

** Tags added: hinted

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

Title:
  fanotify09 case 3 (Events on files and dirs with both inode and mount
  marks) from ubuntu_ltp_syscalls  failed

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux source package in Focal:
  Fix Released

Bug description:
  This is a new test case added 7 days ago [1]

  Test failed on Focal 5.4.0-29.33 with:
  fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 
path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint
  fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 
path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint

  
  [1] 
https://github.com/linux-test-project/ltp/commit/70ca1e8806d227d47c6801262d3f7983652159a4#diff-234c27c769cf07468a81748a0e7330dd

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


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

[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed

[Krzysztof Kozlowski]

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  memcg_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  Confirmed
Status in linux-aws source package in Bionic:
  New
Status in linux source package in Cosmic:
  Confirmed
Status in linux-aws source package in Cosmic:
  New

Bug description:
   startup='Wed May 22 05:59:09 2019'
   memcg_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689
   memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689
   memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 
expected
   memcg_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 
failed
   memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no 
cu=5 cs=3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:17:43 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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


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

[Kernel-packages] [Bug 1936242] [NEW] Focal update: v5.4.129 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.4.129 upstream stable release
   from git://git.kernel.org/

module: limit enabling module.sig_enforce
drm/nouveau: wait for moving fence after pinning v2
drm/radeon: wait for moving fence after pinning
ARM: 9081/1: fix gcc-10 thumb2-kernel regression
mmc: meson-gx: use memcpy_to/fromio for dram-access-quirk
kbuild: add CONFIG_LD_IS_LLD
arm64: link with -z norelro for LLD or aarch64-elf
MIPS: generic: Update node names to avoid unit addresses
spi: spi-nxp-fspi: move the register operation after the clock enable
Revert "PCI: PM: Do not read power state in pci_enable_device_flags()"
dmaengine: zynqmp_dma: Fix PM reference leak in zynqmp_dma_alloc_chan_resourc()
mac80211: remove warning in ieee80211_get_sband()
mac80211_hwsim: drop pending frames on stop
cfg80211: call cfg80211_leave_ocb when switching away from OCB
dmaengine: rcar-dmac: Fix PM reference leak in rcar_dmac_probe()
dmaengine: mediatek: free the proper desc in desc_free handler
dmaengine: mediatek: do not issue a new desc if one is still current
dmaengine: mediatek: use GFP_NOWAIT instead of GFP_ATOMIC in prep_dma
net: ipv4: Remove unneed BUG() function
mac80211: drop multicast fragments
net: ethtool: clear heap allocations for ethtool function
ping: Check return value of function 'ping_queue_rcv_skb'
inet: annotate date races around sk->sk_txhash
net: phy: dp83867: perform soft reset and retain established link
net: caif: fix memory leak in ldisc_open
net/packet: annotate accesses to po->bind
net/packet: annotate accesses to po->ifindex
r8152: Avoid memcpy() over-reading of ETH_SS_STATS
sh_eth: Avoid memcpy() over-reading of ETH_SS_STATS
r8169: Avoid memcpy() over-reading of ETH_SS_STATS
KVM: selftests: Fix kvm_check_cap() assertion
net: qed: Fix memcpy() overflow of qed_dcbx_params()
recordmcount: Correct st_shndx handling
PCI: Add AMD RS690 quirk to enable 64-bit DMA
net: ll_temac: Add memory-barriers for TX BD access
net: ll_temac: Avoid ndo_start_xmit returning NETDEV_TX_BUSY
pinctrl: stm32: fix the reported number of GPIO lines per bank
nilfs2: fix memory leak in nilfs_sysfs_delete_device_group
KVM: do not allow mapping valid but non-reference-counted pages
i2c: robotfuzz-osif: fix control-request directions
kthread_worker: split code for canceling the delayed work timer
kthread: prevent deadlock when kthread_mod_delayed_work() races with 
kthread_cancel_delayed_work_sync()
mm: add VM_WARN_ON_ONCE_PAGE() macro
mm/rmap: remove unneeded semicolon in page_not_mapped()
mm/rmap: use page_not_mapped in try_to_unmap()
mm, thp: use head page in __migration_entry_wait()
mm/thp: fix __split_huge_pmd_locked() on shmem migration entry
mm/thp: make is_huge_zero_pmd() safe and quicker
mm/thp: try_to_unmap() use TTU_SYNC for safe splitting
mm/thp: fix vma_address() if virtual address below file offset
mm/thp: fix page_address_in_vma() on file THP tails
mm/thp: unmap_mapping_page() to fix THP truncate_cleanup_page()
mm: thp: replace DEBUG_VM BUG with VM_WARN when unmap fails for split
mm: page_vma_mapped_walk(): use page for pvmw->page
mm: page_vma_mapped_walk(): settle PageHuge on entry
mm: page_vma_mapped_walk(): use pmde for *pvmw->pmd
mm: page_vma_mapped_walk(): prettify PVMW_MIGRATION block
mm: page_vma_mapped_walk(): crossing page table boundary
mm: page_vma_mapped_walk(): add a level of indentation
mm: page_vma_mapped_walk(): use goto instead of while (1)
mm: page_vma_mapped_walk(): get vma_address_end() earlier
mm/thp: fix page_vma_mapped_walk() if THP mapped by ptes
mm/thp: another PVMW_SYNC fix in page_vma_mapped_walk()
mm, futex: fix shared futex pgoff on shmem huge page
UBUNTU: [Config] enable CONFIG_SYSTEM_REVOCATION_LIST
certs: Add EFI_CERT_X509_GUID support for dbx entries
certs: Move load_system_certificate_list to a common function
Linux 5.4.129
UBUNTU: upstream stable to v5.4.129

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

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Changed in: 

[Kernel-packages] [Bug 1829979] Re: memcg_max_usage_in_bytes from controllers test suite in LTP failed

[Krzysztof Kozlowski]

Accepted upstream and in local LTP mirror.

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Committed

** Changed in: ubuntu-kernel-tests
   Status: Fix Committed => Fix Released

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

Title:
  memcg_max_usage_in_bytes from controllers test suite in LTP failed

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Incomplete
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
   startup='Wed May 22 05:58:50 2019'
   memcg_max_usage_in_bytes_test 1 TINFO: Starting test 1
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_max_usage_in_bytes_test 1 TINFO: Warming up pid: 30821
   memcg_max_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 
30821
   memcg_max_usage_in_bytes_test 1 TFAIL: memory.max_usage_in_bytes is 4325376, 
4194304 expected
   memcg_max_usage_in_bytes_test 2 TINFO: Starting test 2
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 2 TCONF: mem+swap is not enabled
   memcg_max_usage_in_bytes_test 2 TINFO: Starting test 3
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 2 TINFO: Running memcg_process --mmap-anon -s 
4194304
   memcg_max_usage_in_bytes_test 2 TINFO: Warming up pid: 30855
   memcg_max_usage_in_bytes_test 2 TINFO: Process is still here after warm up: 
30855
   memcg_max_usage_in_bytes_test 2 TFAIL: memory.max_usage_in_bytes is 4329472, 
4194304 expected
   memcg_max_usage_in_bytes_test 3 TFAIL: memory.max_usage_in_bytes is 8192, 0 
expected 
   memcg_max_usage_in_bytes_test 4 TINFO: Starting test 4
   sh: echo: I/O error
   memcg_max_usage_in_bytes_test 4 TINFO: set /dev/memcg/memory.use_hierarchy 
to 0 failed
   memcg_max_usage_in_bytes_test 4 TCONF: mem+swap is not enabled
   tag=memcg_max_usage_in_bytes stime=1558504730 dur=3 exit=exited stat=33 
core=no cu=8 cs=7

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 22 02:57 seq
   crw-rw 1 root audio 116, 33 May 22 02:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [14538.862950] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
  Date: Wed May 22 07:06:31 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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


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

** Description changed:

  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

-- 
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:
  In Progress

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 1936211] Re: Cherry-pick "Remove iov_iter_advance() for iter_write"

[Colin Ian King]

** No longer affects: zfs

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

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

Title:
  Cherry-pick "Remove iov_iter_advance() for iter_write"

Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Hirsute:
  New
Status in zfs-linux source package in Impish:
  Fix Committed

Bug description:
  Debian zfs 2.0.3-9 contains the cherry-pick "Remove iov_iter_advance()
  for iter_write", Debian bug #989373.  Apply this fix to zfs 2.0.3.x in
  Impish

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


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

[Kernel-packages] [Bug 1936211] Re: Cherry-pick "Remove iov_iter_advance() for iter_write"

[Colin Ian King]

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

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

Title:
  Cherry-pick "Remove iov_iter_advance() for iter_write"

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Committed
Status in zfs-linux source package in Impish:
  Fix Committed

Bug description:
  Debian zfs 2.0.3-9 contains the cherry-pick "Remove iov_iter_advance()
  for iter_write", Debian bug #989373.  Apply this fix to zfs 2.0.3.x in
  Impish

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


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

[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Sønke Lorenzen]

@Keith
This does not seem to be kernel related, when I upgraded to  460.80 and 465.27 
and got hit by this bug, I first tried to boot with older kernels I had 
installed with the same problem then. And look at 
https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782 there users 
have tried a lot of different kernels without it helping. 

You can either install the nvidia-driver-460-server which is at
460.73.01, or install it manually if it gives other problems, see above.
Or use the 470 beta from
https://launchpad.net/~albertomilone/+archive/ubuntu/nvidia-testing

And then just update all other packages including kernels.

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

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? rm_init_adapter+0xc5/0xe0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nv_open_device+0x122/0x8e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_open+0x2b7/0x560 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_frontend_open+0x58/0xa0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? chrdev_open+0xf7/0x220
  Jun 03 16:26:57 willow kernel:  ? cdev_device_add+0x90/0x90
  Jun 03 16:26:57 willow kernel:  ? do_dentry_open+0x156/0x370
  Jun 03 16:26:57 willow kernel:  ? vfs_open+0x2d/0x30
  Jun 03 16:26:57 willow kernel:  ? do_open+0x1c3/0x340
  Jun 03 16:26:57 willow kernel:  ? path_openat+0x10a/0x1d0
  Jun 03 16:26:57 willow kernel:  ? do_filp_open+0x8c/0x130
  Jun 03 16:26:57 willow kernel:  ? __check_object_size+0x1c/0x20
  Jun 03 16:26:57 willow kernel:  ? do_sys_openat2+0x9b/0x150
  Jun 03 16:26:57 willow kernel:  ? __x64_sys_openat+0x56/0x90
  Jun 03 16:26:57 willow kernel:  ? do_syscall_64+0x38/0x90
  Jun 03 16:26:57 willow kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) 
zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) >
  Jun 03 16:26:57 willow kernel:  sunrpc ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c>
  Jun 03 16:26:57 willow kernel: CR2: 0170
  Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]---
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  

[Kernel-packages] [Bug 1931106] Re: bnxt_en NIC driver crashes IO_PAGE_FAULT

[Kai-Heng Feng]

One possible workaround is to make the device use identity mapping, but
that requires change the kernel source code.

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

Title:
  bnxt_en NIC driver crashes IO_PAGE_FAULT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  We received a bunch of new servers with a Supermicro H12SSL-NT
  mainboard that has an embedded Broadcom BCM57416 NIC.

  On all those servers we observe crashes of the NIC driver (bnxt_en)
  from time to time. We're not able to manually reproduce this issue, it
  just occurs at some point. Also our monitoring does not show any
  irregularities(high traffic flow or sth. like this).

  Syslog: https://pastebin.com/yDAyjHvF

  All servers are running with up-to-date packages:
  $ lsb_release -rd
  Description: Ubuntu 20.04.2 LTS
  Release: 20.04
  $ uname -r
  5.4.0-73-generic 

  It also happens on older kernel versions (tested 5.4.0-66) as well as
  the HWE kernel (tested 5.8.0-55).

  
  Thanks in advance.
  ~ Roman

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


-- 
Mailing list: https://launchpad.net/~kernel-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] [NEW] Sync to SGX 1.33.2

[Tim Gardner]

Public bug reported:

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

[Where problems could occur]

SGX functionality could regress

[Other Info]

SF: #00314640

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

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

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

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

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

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

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

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

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

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

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

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

-- 
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:
  In Progress

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

  [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 1931106] Re: bnxt_en NIC driver crashes IO_PAGE_FAULT

[aft2d]

Update:
I've contacted the mail addresses from the Kai-Heng's post.
Michael Chan (from Broadcom) replied that they've seen similar issues on other 
AMD systems and that they were working with AMD to resolve this.
The plan was to establish contact between me and AMD, unfortunately this never 
happened.  The attempt to contact AMD via the official way (tech support) 
failed because I could not answer AMD's questions without feedback from 
Broadcom, who then also did not reply anymore.

Workaround:
Luckily, with the information that came out of the conversation with Broadcom, 
I was able to troubleshoot a bit myself since I knew at least somewhat where to 
look.
It appears that by setting Advanced -> NB Configuration -> IOMMU to "disabled" 
(default is "Auto") in Supermicro BIOS the problem does not occur anymore.

Since then the whole topic is "stuck".

It's just a workaround and not really a fix, but at least servers
running stable now for me. Since I don't know where the actual problem
is (whether in AMD hardware, bios, kernel, or whatever) so I can't say
if this bug report can be marked as closed or not.

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

Title:
  bnxt_en NIC driver crashes IO_PAGE_FAULT

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  We received a bunch of new servers with a Supermicro H12SSL-NT
  mainboard that has an embedded Broadcom BCM57416 NIC.

  On all those servers we observe crashes of the NIC driver (bnxt_en)
  from time to time. We're not able to manually reproduce this issue, it
  just occurs at some point. Also our monitoring does not show any
  irregularities(high traffic flow or sth. like this).

  Syslog: https://pastebin.com/yDAyjHvF

  All servers are running with up-to-date packages:
  $ lsb_release -rd
  Description: Ubuntu 20.04.2 LTS
  Release: 20.04
  $ uname -r
  5.4.0-73-generic 

  It also happens on older kernel versions (tested 5.4.0-66) as well as
  the HWE kernel (tested 5.8.0-55).

  
  Thanks in advance.
  ~ Roman

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


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

[Kernel-packages] [Bug 1936237] [NEW] use the upstream version for the kernel packaging

[Matthias Klose]

Public bug reported:

please use the upstream version for the kernel packaging.

 apw, sforshee, xnox: is there any way to see which upstream version the 
linux package is based on?
 doko, if you are running it?  /proc/version_signature has the full 
upstream version
 doko, for general inquiries we also have: 
https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish 
is missing for some reason
 apw, no, just looking at the package
 doko, with like apt-cache ... likely no
 apw, could you add that information to the changlog, when you're 
uploading?
 doko, i guess it would be reasonably easy to do... what is going to 
consume it?
 doko, are you interested in when it changes?
 just *knowing* which upstream version is used
 it feels like it should be in the package description for "something"
 or even better, a linux-libc-dev with a real upstream version in the 
package version
 we have always avoided having the third digit so we don't explode the 
librarian with new orig files all the time
 perhaps we could put somehting on that linux-libc-dev though with the 
upstream version in it
 if that would make life easier for you?
 documenting it in the changelog would be ok as well, assuming that you 
can parse that kind of information
 are you intending to consume it as a human, or scripted
 yes, or have a different binary version for every binary package built
 human
 i almost want to put a versioned provides on it
 then if something ever did care it could actually do something about it
 and what would be the package that you provide?
 linux-libc-dev-mainline (= foo) perhaps
 apw: TBH I wonder whether the "avoid new orig files" is still the 
right tradeoff.  The size of a linux orig tarball looks rather less significant 
now than it did when we started this practice
 cjwatson, we would provide a new .orig for every single SRU cycle in the 
normal run of things, for every single kernel.  so 180M for each of 82 kernels.
 which by my calculation is 14TB every 3 weeks?
 Hm yeah, I suppose ...
 I always forget what an absurdly enormous number of kernels you have
 or are you able to collesce the orig by contents?  as there is more like 
only 4 for every cycle.
 No
 Well maybe if they're actually bitwise-identical
 they are bitwise identicle
 i assume you _arn't_ currently sharing the bits, but you might be able to?
 I think we are actually
 But I'll check after this meeting
 ack and thanks
 apw: Oh right, yeah, they get temporarily added as duplicates and 
then librarian-gc deduplicates them
 so the space usage wouldn't be an issue in the end?
 So it'd still be a TB a month or so, which isn't entirely 
insignificant
 Maybe better not change it until the librarian is on PS5 and we get 
a feel for what space usage looks like there
 Actually no, neither apw nor I can multiply apparently
 180M * 82 is 14G not 14T
 ;p
 That makes rather more sense, I was wondering how you'd manage to 
generate like a sixth of the librarian's total storage size in three weeks
 So <1G extra per three weeks is noise and will not really be noticed 
from our point of view.  I can't speak to whatever extra rebase work it might 
require of course.
 And of course it would presumably require some tooling changes.  I 
do think it would be ultimately the right thing to do though.

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


** Tags: rls-ii-incoming

** Tags added: rls-ii-incoming

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

Title:
  use the upstream version for the kernel packaging

Status in linux package in Ubuntu:
  New

Bug description:
  please use the upstream version for the kernel packaging.

   apw, sforshee, xnox: is there any way to see which upstream version 
the linux package is based on?
   doko, if you are running it?  /proc/version_signature has the full 
upstream version
   doko, for general inquiries we also have: 
https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish 
is missing for some reason
   apw, no, just looking at the package
   doko, with like apt-cache ... likely no
   apw, could you add that information to the changlog, when you're 
uploading?
   doko, i guess it would be reasonably easy to do... what is going to 
consume it?
   doko, are you interested in when it changes?
   just *knowing* which upstream version is used
   it feels like it should be in the package description for "something"
   or even better, a linux-libc-dev with a real upstream version in the 
package version
   we have always avoided having the third digit so we don't explode the 
librarian with new orig files all the time
   perhaps we could put somehting on that linux-libc-dev though with the 
upstream version in it
   if that would make life easier for you?
   documenting it in the changelog would be ok as well, assuming that you 
can parse that kind 

[Kernel-packages] [Bug 1936231] [NEW] Bionic update: upstream stable patchset 2021-07-14

[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-07-14

Ported from the following upstream stable releases:
v4.14.237, v4.19.195
v4.14.238, v4.19.196

   from git://git.kernel.org/

Revert "UBUNTU: SAUCE: Revert "proc: Check /proc/$pid/attr/ writes against file 
opener""
proc: Track /proc/$pid/attr/ opener mm_struct
net/nfc/rawsock.c: fix a permission check bug
ASoC: sti-sas: add missing MODULE_DEVICE_TABLE
isdn: mISDN: netjet: Fix crash in nj_probe:
bonding: init notify_work earlier to avoid uninitialized use
netlink: disable IRQs for netlink_lock_table()
net: mdiobus: get rid of a BUG_ON()
cgroup: disable controllers at parse time
wq: handle VM suspension in stall detection
net/qla3xxx: fix schedule while atomic in ql_sem_spinlock
scsi: vmw_pvscsi: Set correct residual data length
scsi: target: qla2xxx: Wait for stop_phase1 at WWN removal
net: macb: ensure the device is available before accessing GEMGXL control 
registers
net: appletalk: cops: Fix data race in cops_probe1
MIPS: Fix kernel hang under FUNCTION_GRAPH_TRACER and PREEMPT_TRACER
bnx2x: Fix missing error code in bnx2x_iov_init_one()
powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P2041 i2c controllers
powerpc/fsl: set fsl,i2c-erratum-a004447 flag for P1010 i2c controllers
i2c: mpc: Make use of i2c_recover_bus()
i2c: mpc: implement erratum A-004447 workaround
drm: Fix use-after-free read in drm_getunique()
drm: Lock pointer access in drm_master_release()
kvm: avoid speculation-based attacks from out-of-range memslot accesses
staging: rtl8723bs: Fix uninitialized variables
btrfs: return value from btrfs_mark_extent_written() in case of error
cgroup1: don't allow '\n' in renaming
USB: f_ncm: ncm_bitrate (speed) is unsigned
usb: dwc3: ep0: fix NULL pointer exception
usb: typec: ucsi: Clear PPM capability data in ucsi_init() error path
usb: gadget: f_fs: Ensure io_completion_wq is idle during unbind
USB: serial: ftdi_sio: add NovaTech OrionMX product ID
USB: serial: omninet: add device id for Zyxel Omni 56K Plus
USB: serial: quatech2: fix control-request directions
usb: gadget: eem: fix wrong eem header operation
usb: fix various gadgets null ptr deref on 10gbps cabling.
usb: fix various gadget panics on 10gbps cabling
regulator: core: resolve supply for boot-on/always-on regulators
regulator: max77620: Use device_set_of_node_from_dev()
perf: Fix data race between pin_count increment/decrement
NFS: Fix a potential NULL dereference in nfs_get_client()
perf session: Correct buffer copying when peeking events
kvm: fix previous commit for 32-bit builds
NFS: Fix use-after-free in nfs4_init_client()
NFSv4: nfs4_proc_set_acl needs to restore NFS_CAP_UIDGID_NOMAP on error.
scsi: core: Fix error handling of scsi_host_alloc()
scsi: core: Put .shost_dev in failure path if host state changes to RUNNING
scsi: core: Only put parent device if host state differs from SHOST_CREATED
ftrace: Do not blindly read the ip address in ftrace_bug()
tracing: Correct the length check which causes memory corruption
proc: only require mm_struct for writing
scsi: bnx2fc: Return failure if io_req is already in ABTS processing
ARM: dts: imx6qdl-sabresd: Assign corresponding power supply for LDOs
usb: f_ncm: only first packet of aggregate needs to start timer
usb: pd: Set PD_T_SINK_WAIT_CAP to 310ms
RDMA/mlx4: Do not map the core_clock page to user space unless enabled
vmlinux.lds.h: Avoid orphan section with !SMP
sched/fair: Make sure to update tg contrib for blocked load
UBUNTU: upstream stable to v4.14.237, v4.19.195
net: ieee802154: fix null deref in parse dev addr
HID: hid-sensor-hub: Return error for hid_set_field() failure
HID: Add BUS_VIRTUAL to hid_connect logging
HID: usbhid: fix info leak in hid_submit_ctrl
ARM: OMAP2+: Fix build warning when mmc_omap is not built
HID: gt683r: add missing MODULE_DEVICE_TABLE
gfs2: Fix use-after-free in gfs2_glock_shrink_scan
scsi: target: core: Fix warning on realtime kernels
ethernet: myri10ge: Fix missing error code in myri10ge_probe()
nvme-loop: reset queue count to 1 in nvme_loop_destroy_io_queues()
nvme-loop: clear NVME_LOOP_Q_LIVE when nvme_loop_configure_admin_queue() fails
nvme-loop: check for NVME_LOOP_Q_LIVE in nvme_loop_destroy_admin_queue()
net: ipconfig: Don't override command-line hostnames or domains
rtnetlink: Fix missing error code in rtnl_bridge_notify()
net/x25: Return the correct errno code
net: Return the correct errno code
fib: Return the correct errno code
dmaengine: ALTERA_MSGDMA depends on 

[Kernel-packages] [Bug 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.

[Alex Tu]

A test result on AX201 might not related to this AX210, but it might able be a 
reference for the -63 firmware.
https://bugs.launchpad.net/somerville/+bug/1933755/comments/9

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

Title:
  Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW
  error detected. Restarting 0x0.

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  iwlwifi may encounter firmware crash when running 5.13 kernel with
  outdated firmware.

  [Fix]

  Commit 2b13afc1a0ff82 ("iwlwifi: add new FWs from core60-51 release")
  added new rev -63 firmware.

  [Test Case]

  1. disconnect/connect stress

 $ sudo add-apt-repository ppa:checkbox-dev/ppa
 $ sudo apt install plainbox-provider-checkbox
 $ checkbox-cli run 
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress

 ignore connect bluetooth part, and set the SSID and password to
  proceed.

  2. suspend/resume stress

 $ for i in $(seq 200); do \
 echo "Round $i..."; \
 nmcli d; \
 sleep 15; \
 rtcwake -m mem -s 15; \
 done

  [Where problems could occur]

  Rev -63 firmware is only used by 5.13 kernel or newer.

  [Other Info]

  While 5.13 kernel is only available in Focal and Impish, only Focal is
  nominated here.

  == original bug description ==

  [Reproduce steps]

  1. disconnect/connect stress
  $ sudo add-apt-repository ppa:checkbox-dev/ppa
  $ sudo apt install plainbox-provider-checkbox
  $ checkbox-cli run 
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
  ignore connect bluetooth part, and set the SSID and password to proceed.

  2. suspend/resume stress
  $ for i in $(seq 200); do \
  echo "Round $i..."; \
  nmcli d; \
  sleep 15; \
  rtcwake -m mem -s 15; \
  done

  kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0.
   
[100/1757]
  kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6
  kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0 
ty-a0-gf-a0-59.ucode
  kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0
  kernel: iwlwifi :03:00.0: 0x | trm_hw_status1
  kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2
  kernel: iwlwifi :03:00.0: 0x922A | interruptlink1
  kernel: iwlwifi :03:00.0: 0x922A | interruptlink2
  kernel: iwlwifi :03:00.0: 0x000161C4 | data1
  kernel: iwlwifi :03:00.0: 0x0010 | data2
  kernel: iwlwifi :03:00.0: 0x | data3
  kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time
  kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low
  kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi
  kernel: iwlwifi :03:00.0: 0x | time gp1
  kernel: iwlwifi :03:00.0: 0x00EF1CDC | time gp2
  kernel: iwlwifi :03:00.0: 0x0001 | uCode revision type
  kernel: iwlwifi :03:00.0: 0x003B | uCode version major
  kernel: iwlwifi :03:00.0: 0x601F3A66 | uCode version minor
  kernel: iwlwifi :03:00.0: 0x0420 | hw version
  kernel: iwlwifi :03:00.0: 0x00489002 | board version
  kernel: iwlwifi :03:00.0: 0x8011001C | hcmd
  kernel: iwlwifi :03:00.0: 0xE6863000 | isr0
  kernel: iwlwifi :03:00.0: 0x0104 | isr1
  kernel: iwlwifi :03:00.0: 0x68FA | isr2
  kernel: iwlwifi :03:00.0: 0x00C44C4F | isr3
  kernel: iwlwifi :03:00.0: 0x0020 | isr4
  kernel: iwlwifi :03:00.0: 0x007C019C | last cmd Id
  kernel: iwlwifi :03:00.0: 0x000161C4 | wait_event
  kernel: iwlwifi :03:00.0: 0x00D0 | l2p_control
  kernel: iwlwifi :03:00.0: 0x00018034 | l2p_duration
  kernel: iwlwifi :03:00.0: 0x003F | l2p_mhvalid
  kernel: iwlwifi :03:00.0: 0x00CF00F8 | l2p_addr_match
  kernel: iwlwifi :03:00.0: 0x0009 | lmpm_pmg_sel
  kernel: iwlwifi :03:00.0: 0x | timestamp
  kernel: iwlwifi :03:00.0: 0x9890 | flow_handler
  kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  kernel: iwlwifi :03:00.0: Status: 0x0040, count: 7
  kernel: iwlwifi :03:00.0: 0x2000345A | ADVANCED_SYSASSERT
  kernel: iwlwifi :03:00.0: 0x | umac branchlink1
  kernel: iwlwifi :03:00.0: 0x8045D8DE | umac branchlink2
  kernel: iwlwifi :03:00.0: 0xC0085288 | umac interruptlink1
  kernel: iwlwifi :03:00.0: 0x | umac interruptlink2
  kernel: iwlwifi :03:00.0: 0x0007 | umac data1 
 

[Kernel-packages] [Bug 1933415] Re: Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW error detected. Restarting 0x0.

[Alex Tu]

Just checked with xps13-9310-c5-202007-28045 in the certification pool.
The wifi interfaces no response after `iperf -c` for about 20~30 mins.
Can not find iwlwifi related error nor firmware crash show in dmesg.

bios: 1.0.1
kernel: 5.13.0-1007-oem
firmware: linux-firmware 1.187.15+staging.7
wifi module:
00:14.3 Network controller [0280]: Intel Corporation Device [8086:a0f0] (rev 20)

iwlwifi in dmesg:
ubuntu@xps13-9310-c5-202007-28045:~$ dmesg | grep iwlwifi
[4.975000] iwlwifi :00:14.3: enabling device ( -> 0002)
[4.995558] iwlwifi :00:14.3: api flags index 2 larger than supported by 
driver
[4.995576] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
89.3.35.37
[4.995839] iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0 
QuZ-a0-hr-b0-63.ucode op_mode iwlmvm
[5.074969] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX203, REV=0x354

Steps:

# on ubuntu@xps13-9310-c5-202007-28045
$ ssh -o 'StrictHostKeyChecking=no' -o 'UserKnownHostsFile=/dev/null' 
'ubuntu@10.101.49.132'
# password is `u`
# connect to ubuntu-cert-ax-wpa by nmtui
# get wifi ip 192.168.50.188
ubuntu@xps13-9310-c5-202007-28045:~$ iperf3 -c 192.168.50.177 -B 192.168.50.188 
-t 6000

# on another random machine 202009-28216 for iperf server
$ ssh -o 'StrictHostKeyChecking=no' -o 'UserKnownHostsFile=/dev/null' 
'ubuntu@10.101.49.43'
# password is `u`
# connect to ubuntu-cert-ax-wpa by nmtui
# get wifi ip 192.168.50.177
ubuntu@202009-28216:~$ iperf3 -s -B 192.168.50.177

note:
The 2 machines will be re-deploied during next SRU. So, the ssh connection is 
not expected preserve for debugging forever.

** Attachment added: 
"sosreport-xps13-9310-c5-202007-28045-2021-07-14-jphgowe.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/+attachment/5510940/+files/sosreport-xps13-9310-c5-202007-28045-2021-07-14-jphgowe.tar.xz

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

Title:
  Intel AX210 iwlwifi firmware crash under stress tests: Microcode SW
  error detected. Restarting 0x0.

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

  iwlwifi may encounter firmware crash when running 5.13 kernel with
  outdated firmware.

  [Fix]

  Commit 2b13afc1a0ff82 ("iwlwifi: add new FWs from core60-51 release")
  added new rev -63 firmware.

  [Test Case]

  1. disconnect/connect stress

 $ sudo add-apt-repository ppa:checkbox-dev/ppa
 $ sudo apt install plainbox-provider-checkbox
 $ checkbox-cli run 
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress

 ignore connect bluetooth part, and set the SSID and password to
  proceed.

  2. suspend/resume stress

 $ for i in $(seq 200); do \
 echo "Round $i..."; \
 nmcli d; \
 sleep 15; \
 rtcwake -m mem -s 15; \
 done

  [Where problems could occur]

  Rev -63 firmware is only used by 5.13 kernel or newer.

  [Other Info]

  While 5.13 kernel is only available in Focal and Impish, only Focal is
  nominated here.

  == original bug description ==

  [Reproduce steps]

  1. disconnect/connect stress
  $ sudo add-apt-repository ppa:checkbox-dev/ppa
  $ sudo apt install plainbox-provider-checkbox
  $ checkbox-cli run 
com.canonical.certification::stress/wireless_bluetooth_coex_connect_stress
  ignore connect bluetooth part, and set the SSID and password to proceed.

  2. suspend/resume stress
  $ for i in $(seq 200); do \
  echo "Round $i..."; \
  nmcli d; \
  sleep 15; \
  rtcwake -m mem -s 15; \
  done

  kernel: iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x0.
   
[100/1757]
  kernel: iwlwifi :03:00.0: Start IWL Error Log Dump:
  kernel: iwlwifi :03:00.0: Status: 0x0040, count: 6
  kernel: iwlwifi :03:00.0: Loaded firmware version: 59.601f3a66.0 
ty-a0-gf-a0-59.ucode
  kernel: iwlwifi :03:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
  kernel: iwlwifi :03:00.0: 0x00A08200 | trm_hw_status0
  kernel: iwlwifi :03:00.0: 0x | trm_hw_status1
  kernel: iwlwifi :03:00.0: 0x004D9BDC | branchlink2
  kernel: iwlwifi :03:00.0: 0x922A | interruptlink1
  kernel: iwlwifi :03:00.0: 0x922A | interruptlink2
  kernel: iwlwifi :03:00.0: 0x000161C4 | data1
  kernel: iwlwifi :03:00.0: 0x0010 | data2
  kernel: iwlwifi :03:00.0: 0x | data3
  kernel: iwlwifi :03:00.0: 0x1C405003 | beacon time
  kernel: iwlwifi :03:00.0: 0x72B40004 | tsf low
  kernel: iwlwifi :03:00.0: 0x03E4 | tsf hi
  kernel: iwlwifi :03:00.0: 0x | time gp1
  kernel: iwlwifi 

[Kernel-packages] [Bug 1936211] Re: Cherry-pick "Remove iov_iter_advance() for iter_write"

[Bug Watch Updater]

** Changed in: zfs
   Status: Unknown => Fix Released

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

Title:
  Cherry-pick "Remove iov_iter_advance() for iter_write"

Status in Native ZFS for Linux:
  Fix Released
Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Impish:
  In Progress

Bug description:
  Debian zfs 2.0.3-9 contains the cherry-pick "Remove iov_iter_advance()
  for iter_write", Debian bug #989373.  Apply this fix to zfs 2.0.3.x in
  Impish

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


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

[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]

[Alex Tu]

sorry for confusing, let me break down the steps:
1. # Add PPA from 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2
$ sudo add-apt-repository ppa:vicamo/linux-firmware-staging

2. # to get linux-firmware from Vicamo's PPA
$ sudo apt-get install linux-firmware

3. # to install OEM 5.13
$ sudo apt-get install linux-image-oem-20.04c

4. # reboot, and make sure you are running under oem kernel 5.13
$ uanme -r
5.13.0-1007-oem

5. # check if the target firmware `-63` loaded
$ dmesg  | grep iwlwifi
iwlwifi :00:14.3: loaded firmware version 63.c04f3485.0 
QuZ-a0-hr-b0-63.ucode op_mode iwlmvm

6. # check if the wifi issue can still be reproduced.
- if it is there, please also attach the dmesg here.

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

Title:
  [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
  wireless [8086:a0f0]

Status in Linux Firmware:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Whenever I am using a wireless connection, the image freezes roughly
  every two minutes. Sometimes, email cannot be retrieved / computer
  complains the connection was momentarily lost.

  - If I am on a wire, this problem does NOT occur.
  - This problems occurs on wireless independent of the platform used (behavior 
seen in both Google Hangout and Zoom)
  - This problem does NOT occur on Windows. I did a meeting where both my Linux 
and Windows machines were connected to the same meeting and using the same wifi 
router, and while the performance on Windows was flawless, unfortunately it was 
not so on the Ubuntu box. So I don't think my wifi router or network is to 
blame.
  - As far as I can recall, the problem used not to be there 2 weeks ago. So it 
may have been introduced by a recent update.
  - As communicated before, I am on a certified machine from Dell, recently 
purchased with Ubuntu already on board from factory (I assume the logs there 
were sent to you would contain the information).
  - I tried to generate a log on the wireless, but the process did not let me 
do this very easily. I am more than happy to send you additional information - 
but please let me know which package you want me to spy upon exactly, as I am 
not sure what would be helpful in this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
  Uname: Linux 5.10.0-1029-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 18 09:47:58 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0991]
  InstallationDate: Installed on 2021-04-24 (54 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem 
root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 2.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.1
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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:

[Kernel-packages] [Bug 1936211] [NEW] Cherry-pick "Remove iov_iter_advance() for iter_write"

[Colin Ian King]

Public bug reported:

Debian zfs 2.0.3-9 contains the cherry-pick "Remove iov_iter_advance()
for iter_write", Debian bug #989373.  Apply this fix to zfs 2.0.3.x in
Impish

** Affects: zfs
 Importance: Unknown
 Status: Unknown

** Affects: zfs-linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

** Affects: zfs-linux (Ubuntu Impish)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

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

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Also affects: zfs-linux (Ubuntu Impish)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

** Bug watch added: Debian Bug tracker #989373
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989373

** Also affects: zfs via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989373
   Importance: Unknown
   Status: Unknown

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

Title:
  Cherry-pick "Remove iov_iter_advance() for iter_write"

Status in Native ZFS for Linux:
  Unknown
Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Impish:
  In Progress

Bug description:
  Debian zfs 2.0.3-9 contains the cherry-pick "Remove iov_iter_advance()
  for iter_write", Debian bug #989373.  Apply this fix to zfs 2.0.3.x in
  Impish

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


-- 
Mailing list: https://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 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]

[Steve Barriault]

I am sorry Alex, but I am not sure what you are asking me to do exactly.

I am ready to try what you want, but please give me the howto as well, as I
am not sure what you mean here.

Best Regards,

Steve

On Wed, Jul 14, 2021 at 3:50 AM Alex Tu <1932...@bugs.launchpad.net>
wrote:

> progress update:
>  - Vicamo is SRUing related firmware for both oem 5.10, hwe 5.11 and oem
> 5.13.
>- for OEM 5.10, HWE 5.11:
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217
>- for OEM 5.13:
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415
>
> @Steve,
> per #17, the firmware for OEM 5.10(LP: #1934217) not works for you.
> Could you please have a try on OEM 5.13 + firmware from LP: #1933415?
>
> The firmware crashing looks not happens to every machine using AX201.
>  - Vicamo can not reproduce it with wifi6 AP during both SRU (LP: #1934217
> and LP: 1933415)
>  - It passed with OEM 5.10 + firmware(LP: #1934217)
>  - But it failed with OEM 5.10 + firmware(LP: #1934217) on Steve's machine
> (per #17)
>
> So, we are asking Intel for a suggested combination of Kernel and
> firmware to make sure the stability of AX201.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
>   [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
>   wireless [8086:a0f0]
>
> Status in Linux Firmware:
>   New
> Status in OEM Priority Project:
>   Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
>   New
>
> Bug description:
>   Whenever I am using a wireless connection, the image freezes roughly
>   every two minutes. Sometimes, email cannot be retrieved / computer
>   complains the connection was momentarily lost.
>
>   - If I am on a wire, this problem does NOT occur.
>   - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
>   - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
>   - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
>   - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
>   - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
>   Uname: Linux 5.10.0-1029-oem x86_64
>   ApportVersion: 2.20.11-0ubuntu27.18
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Jun 18 09:47:58 2021
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
># This is the distribution channel descriptor for the OEM CDs
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-focal-amd64-20200502-85
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   EcryptfsInUse: Yes
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA
> controller])
>  Subsystem: Dell Device [1028:0991]
>   InstallationDate: Installed on 2021-04-24 (54 days ago)
>   InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
> 20200502-05:58
>   MachineType: Dell Inc. XPS 13 9310
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem
> root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 03/25/2021
>   dmi.bios.release: 2.1
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 2.1.1
>   dmi.board.name: 08607K
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: XPS
>   dmi.product.name: XPS 13 9310
>   dmi.product.sku: 0991
>   dmi.sys.vendor: Dell Inc.
>   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

[Kernel-packages] [Bug 1738534] Re: Processor turbo dsiabled/throttled after suspend

[Mustapha Hadid]

I'm experiencing the same issue on Ubuntu 21.04 (5.11.0-22-generic)


---
DistroRelease: Ubuntu 21.04
InstallationDate: Installed on 2020-03-14 (487 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
UpgradeStatus: Upgraded to hirsute on 2021-06-03 (40 days ago)
dmi.bios.date: 11/30/2020
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: BHCN41WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Y540-15IRH-PG0
dmi.ec.firmware.release: 1.41
dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN41WW:bd11/30/2020:br1.41:efr1.41:svnLENOVO:pn81SY:pvrLegionY540-15IRH-PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY540-15IRH-PG0:
dmi.product.family: Legion Y540-15IRH-PG0
dmi.product.name: 81SY
dmi.product.sku: LENOVO_MT_81SY_BU_idea_FM_Legion Y540-15IRH-PG0
dmi.product.version: Legion Y540-15IRH-PG0
dmi.sys.vendor: LENOVO

lscpu
---
Architecture:x86_64
CPU op-mode(s):  32-bit, 64-bit
Byte Order:  Little Endian
Address sizes:   39 bits physical, 48 bits virtual
CPU(s):  12
On-line CPU(s) list: 0-11
Thread(s) per core:  2
Core(s) per socket:  6
Socket(s):   1
NUMA node(s):1
Vendor ID:   GenuineIntel
CPU family:  6
Model:   158
Model name:  Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Stepping:10
CPU MHz: 2600.000
CPU max MHz: 2600.
CPU min MHz: 800.
BogoMIPS:5199.98
Virtualization:  VT-x
L1d cache:   192 KiB
L1i cache:   192 KiB
L2 cache:1.5 MiB
L3 cache:12 MiB
NUMA node0 CPU(s):   0-11
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf:  Mitigation; PTE Inversion; VMX vulnerable
Vulnerability Mds:   Vulnerable; SMT vulnerable
Vulnerability Meltdown:  Vulnerable
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1:Vulnerable: __user pointer sanitization and 
usercopy barriers only; no swapgs barriers
Vulnerability Spectre v2:Vulnerable, IBPB: disabled, STIBP: disabled
Vulnerability Srbds: Vulnerable
Vulnerability Tsx async abort:   Not affected
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
syscall nx pdpe1g
 b rdtscp lm constant_tsc art arch_perfmon pebs 
bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 
monitor ds_c
 pl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm 
pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c 
rdrand lahf_lm 
 abm 3dnowprefetch cpuid_fault epb 
invpcid_single ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bm
 i1 avx2 smep bmi2 erms invpcid mpx rdseed adx 
smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_not
 ify hwp_act_window hwp_epp md_clear flush_l1d

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

Title:
  Processor turbo dsiabled/throttled after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After suspending/resuming my laptop on battery power, I noticed choppy
  video playback.  I've narrowed it down to the CPU being locked to
  lower frequencies after suspend/resume (only on battery).  Plugging
  the laptop back in does not restore the normal performance, nor does
  suspend/resume after plugging it back in.  The performance doesn't
  drop until after the suspend/resume, I'm not sure if it is _supposed_
  to throttle when on battery, but either way the behaviour is wrong.

  Doing a full shutdown and restart restores the performance to normal.

  Prior to a suspend/resume cycle, cpupower reports:

  $ sudo cpupower frequency-info
  analyzing CPU 0:
driver: intel_pstate
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency:  Cannot determine or is not supported.
hardware limits: 800 MHz - 3.00 GHz
available cpufreq governors: performance powersave
current 

[Kernel-packages] [Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root

[Heitor Alves de Siqueira]

** Description changed:

  [Impact]
  Encrypted swap partitions may not load correctly with ZFS root, due to 
ordering cycle on zfs-mount.service.
  
  [Test Plan]
  1. Install Ubuntu 20.04 using ZFS-on-root
  2. Add encrypted partition to /etc/crypttab:
-swap/dev/nvme0n1p1  /dev/urandom
swap,cipher=aes-xts-plain64,size=256
+    swap/dev/nvme0n1p1  /dev/urandom
swap,cipher=aes-xts-plain64,size=256
  3. Add swap partition to /etc/fstab:
-/dev/mapper/swapnoneswapsw  0 0
+    /dev/mapper/swapnoneswapsw  0 0
  4. Reboot and check whether swap has loaded correctly, and whether boot logs 
show ordering cycle:
  [6.638228] systemd[1]: systemd-random-seed.service: Found ordering cycle 
on zfs-mount.service/start
  [6.639418] systemd[1]: systemd-random-seed.service: Found dependency on 
zfs-import.target/start
  [6.640474] systemd[1]: systemd-random-seed.service: Found dependency on 
zfs-import-cache.service/start
  [6.641637] systemd[1]: systemd-random-seed.service: Found dependency on 
cryptsetup.target/start
  [6.642734] systemd[1]: systemd-random-seed.service: Found dependency on 
systemd-cryptsetup@swap.service/start
  [6.643951] systemd[1]: systemd-random-seed.service: Found dependency on 
systemd-random-seed.service/start
  [6.645098] systemd[1]: systemd-random-seed.service: Job 
zfs-mount.service/start deleted to break ordering cycle starting with 
systemd-random-seed.service/start
  [ SKIP ] Ordering cycle found, skipping Mount ZFS filesystems
  
  [Where problems could occur]
  Since we're changing the zfs-mount-generator service, regressions could show 
up during mounting of ZFS partitions. We should thoroughly test different 
scenarios of ZFS such as ZFS-on-root, separate ZFS partitions and the presence 
of swap, to make sure all partitions are mounted correctly and no ordering 
cycles are present.
  
+ Below is a list of suggested test scenarios that we should check for 
regressions:
+ 1. ZFS-on-root + encrypted swap (see "Test Plan" section above)
+ 2. Encrypted root + separate ZFS partitions
+ 3. ZFS on LUKS
+ 4. ZFS on dm-raid
+ 
+ Although scenario 4 is usually advised against (ZFS itself should handle
+ RAID), it's a good smoke test to validate that mount order is being
+ handled correctly.
+ 
  [Other Info]
  This has been fixed upstream by the following commits:
  * ec41cafee1da Fix a dependency loop [0]
  * 62663fb7ec19 Fix another dependency loop [1]
  
  The patches above have been introduced in version 2.1.0, with upstream
  backports to zfs-2.0. In Ubuntu, it's present in Groovy and later
  releases, so it's still needed in Focal.
  
  $ rmadison -a source zfs-linux
-  zfs-linux | 0.8.3-1ubuntu12| focal   | source
-  zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
-  zfs-linux | 0.8.3-1ubuntu12.10 | focal-updates   | source
-  zfs-linux | 0.8.4-1ubuntu11| groovy  | source
-  zfs-linux | 0.8.4-1ubuntu11.2  | groovy-updates  | source
-  zfs-linux | 2.0.2-1ubuntu5 | hirsute | source
-  zfs-linux | 2.0.3-8ubuntu5 | impish  | source
+  zfs-linux | 0.8.3-1ubuntu12| focal   | source
+  zfs-linux | 0.8.3-1ubuntu12.9  | focal-security  | source
+  zfs-linux | 0.8.3-1ubuntu12.10 | focal-updates   | source
+  zfs-linux | 0.8.4-1ubuntu11| groovy  | source
+  zfs-linux | 0.8.4-1ubuntu11.2  | groovy-updates  | source
+  zfs-linux | 2.0.2-1ubuntu5 | hirsute | source
+  zfs-linux | 2.0.3-8ubuntu5 | impish  | source
  
  [0] https://github.com/openzfs/zfs/commit/ec41cafee1da
  [1] https://github.com/openzfs/zfs/commit/62663fb7ec19
  
  ORIGINAL DESCRIPTION
  
  
  root@eu1:/var/log# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal
  
  root@eu1:/var/log# apt-cache policy cryptsetup
  cryptsetup:
    Installed: (none)
    Candidate: 2:2.2.2-3ubuntu2
    Version table:
   2:2.2.2-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
  OTHER BACKGROUND INFO:
  ==
  
  1. machine has 2 drives. each drive is partitioned into 2 partitions,
  zfs and swap
  
  2. Ubuntu 20.04 installed on ZFS root using debootstrap
  (debootstrap_1.0.118ubuntu1_all)
  
  3. The ZFS root pool is a 2 partition mirror (the first partition of
  each disk)
  
  4. /etc/crypttab is set up as follows:
  
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802914-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  swap  
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HALR-0_S3W6NX0M802933-part2
/dev/urandom   swap,cipher=aes-xts-plain64,size=256
  
  WHAT I EXPECTED
  ===
  
  I expected machine would reboot and have encrypted swap that used two
  devices under /dev/mapper
  
  WHAT HAPPENED INSTEAD
  

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

[Po-Hsu Lin]

Found on 5.11.0-1013.13-aws

** Tags added: aws

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

Status in ubuntu-kernel-tests:
  In Progress
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:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 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
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]
  If there is no devlink device available, the devlink_port_split.py in 
kselftest/net will fail with:
   # selftests: net: devlink_port_split.py
   # Traceback (most recent call last):
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
   # main()
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
   # dev = list(devs.keys())[0]
   # IndexError: list index out of range 
   not ok 43 selftests: net: devlink_port_split.py # exit=1

  [Fix]
  * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no 
devlink device

  This test only exist in our source tree since Hirsute, this patch can
  be cherry-picked into all affected kernels.

  [Test Plan]
  Run this test manually from the patched source tree, the test will be skipped 
when there is no devlink device:
# selftests: net: devlink_port_split.py
# no devlink device was found, test skipped
ok 7 selftests: net: devlink_port_split.py # SKIP

  [Where problems could occur]
  Change limited to testing tool, if this change is incorrect it might cause 
false-negative result in our test report.

  
  [Original Bug Report]
  This is a scripted bug report about ADT failures while running linux tests 
for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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


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

[Kernel-packages] [Bug 1928890] Re: vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

[Po-Hsu Lin]

Found on 5.11.0-1013.13-aws

** Tags added: aws

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

Title:
  vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Hirsute:
  New
Status in linux-oem-5.10 source package in Hirsute:
  New

Bug description:
  This is a scripted bug report about ADT failures while running linux
  tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  
  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  
  00:09:30 DEBUG| [stdout] # selftests: net: vrf_route_leaking.sh
  00:09:30 DEBUG| [stdout] # 
  00:09:30 DEBUG| [stdout] # 
###
  00:09:30 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP ttl error route lookup 
ping
  00:09:30 DEBUG| [stdout] # 
###
  00:09:30 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:32 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded  
 [ OK ]
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP error route lookup 
traceroute
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute
  00:09:32 DEBUG| [stdout] # 
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # IPv4 (sym route): VRF ICMP fragmentation error 
route lookup ping
  00:09:32 DEBUG| [stdout] # 
###
  00:09:32 DEBUG| [stdout] # 
  00:09:34 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:34 DEBUG| [stdout] # TEST: Ping received ICMP Frag needed   
 [ OK ]
  00:09:34 DEBUG| [stdout] # 
  00:09:34 DEBUG| [stdout] # 
###
  00:09:34 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP ttl error route lookup 
ping
  00:09:34 DEBUG| [stdout] # 
###
  00:09:34 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # TEST: Basic IPv4 connectivity  
 [ OK ]
  00:09:36 DEBUG| [stdout] # TEST: Ping received ICMP ttl exceeded  
 [ OK ]
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # IPv4 (asym route): VRF ICMP error route lookup 
traceroute
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # SKIP: Could not run IPV4 test without traceroute
  00:09:36 DEBUG| [stdout] # 
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP ttl error route lookup 
ping
  00:09:36 DEBUG| [stdout] # 
###
  00:09:36 DEBUG| [stdout] # 
  00:09:40 DEBUG| [stdout] # TEST: Basic IPv6 connectivity  
 [FAIL]
  00:09:40 DEBUG| [stdout] # TEST: Ping received ICMP Hop limit 
 [ OK ]
  00:09:40 DEBUG| [stdout] # 
  00:09:40 DEBUG| [stdout] # 
###
  00:09:40 DEBUG| [stdout] # IPv6 (sym route): VRF ICMP error route lookup 
traceroute
  00:09:40 DEBUG| [stdout] # 

[Kernel-packages] [Bug 1935846] Re: Sony Dualshock 4 usb dongle crashes the whole system

[xcom]

Thank you Alex!
Your kernel seems to be crash free. It fixes the problem for me. 

Uname -a 
ry2600 ~ % uname -a
Linux x-ry2600 5.4.0-77-generic #86 SMP Mon Jul 12 19:43:42 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  Sony Dualshock 4 usb dongle crashes the whole system

Status in linux package in Ubuntu:
  New

Bug description:
  The hid-sony driver has custom DS4 connect/disconnect logic for the
  DS4 dongle, which is a USB dongle acting as a proxy to Bluetooth
  connected DS4.

  The connect/disconnect logic works fine generally, however not in
  conjunction with Steam. Steam implements its own DS4 driver using
  hidraw. Both hid-sony and Steam are issuing their own HID requests
  and are racing each other during DS4 dongle connect/disconnect
  resulting in a kernel crash in hid-sony.

  The problem is that upon a DS4 connect to the dongle, hid-sony kicks
  of 'ds4_get_calibration_data' from within its dongle hotplug code.
  The calibration code issues raw HID feature report for reportID 0x02.
  When Steam is running, it issues a feature report for reportID 0x12
  typically just prior to hid-sony requesting feature reportID 0x02.
  The result is that 'ds4_get_calibration_data' receives the data Steam
  requested as that's the HID report returing first. Currently this
  results in it processing invalid data, which ultimately results in a
  divide by zero upon a future 'dualshock4_parse_report'.

  The solution for now is to check within 'ds4_get_calibration_data' to
  check if we received data for the feature report we issued and if not
  retry. 

  Please consider to add this patch to Ubuntu LTS kernels.

  Commit: 
  
https://github.com/torvalds/linux/commit/f5dc93b7875bcb8be77baa792cc9432aaf65365b

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


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

[Kernel-packages] [Bug 1931301] Re: NIC unavailable after suspend to RAM

[Chris Chiu]

Thanks for the information. Will propose a fix soon.

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

Title:
  NIC unavailable after suspend to RAM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to 21.04 (hirsute) and now the network card is unavailable
  after suspend to RAM (sleep state S3). It worked flawlessly up until
  20.10. My workaround for now is unloading and reloading the kernel
  module, but that won't work for normal users, hence this report.

  NIC in its unavailable state:
2: enp4s0:  mtu 1500 qdisc mq state DOWN group default 
qlen 1000
link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff

  NIC (from lspci):
04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet 
Controller (rev 10)

  Trying to ifconfig it down/up results in:
SIOCSIFFLAGS: No such device

  journalctl shows (right after recovering from suspend):
NetworkManager[1911]:   [1623181236.9371] manager: sleep: wake 
requested (sleeping: yes  enabled: yes)
NetworkManager[1911]:   [1623181236.9372] device (enp4s0): state 
change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
NetworkManager[1911]:   [1623181236.9382] manager: NetworkManager 
state is now CONNECTED_LOCAL

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Jun  8 21:59:15 2021
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-25 (1748 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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

[Kernel-packages] [Bug 1934747] Re: Add support for AMD sensor fusion hub

[AceLan Kao]

** Changed in: linux-oem-5.13 (Ubuntu Focal)
   Status: Confirmed => 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/1934747

Title:
  Add support for AMD sensor fusion hub

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
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.13 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [Impact]
  AMD sensor fusion hub on newer platforms require additional support to
  work.

  [Fix]
  Backport latest addition to amd_sfh.

  [Test]
  This is backport request from AMD for an upcoming platform. We don't
  have access on the hardware to test it.

  [Where problems could occur]
  The driver uses MMIO read to get hardware version, so as soon as the
  reading is reliable the impact is limited.

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


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

[Kernel-packages] [Bug 1934398] Re: Prevent spurious wakeups on amd s2idle

[AceLan Kao]

** Changed in: linux-oem-5.13 (Ubuntu Focal)
   Status: Confirmed => 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/1934398

Title:
  Prevent spurious wakeups on amd s2idle

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:
  Confirmed
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
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:
  [Impact]
  Several AMD based OEM designs have spurious wakeups occurring from EC events 
during s2idle.  This leads to non-functional wakeup sources or higher power 
consumption.

  [Fix]
  Prevent setting the GPE for the EC for wakeup source on AMD systems.

  [Test]
  Verify s2idle on OEM system.

  [Where problems could occur]
  Code is guarded to only run on AMD systems, which are just now getting s2idle 
support in oem kernel.

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


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

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

[AceLan Kao]

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

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

Title:
  Add l2tp.sh in net from ubuntu_kernel_selftests back

Status in ubuntu-kernel-tests:
  In Progress
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:
  In Progress
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Groovy:
  In Progress
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.13 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
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]
  We have this test disabled intentionally in the past because of the
  lack of commit 27d53323664c54 "l2tp: remove skb_dst_set() from
  l2tp_xmit_skb()" in our kernels.

  The way we disable it is to override the executable bit with our
  autotest-client-tests suite [1], but this makes the test suite
  complain about script is not executable. Henceforth we further
  disable it by removing it from the Makefile in the patch "UBUNTU:
  SAUCE: selftests/net -- disable timeout"

  Now with commit 27d53323664c54 landed and l2tp.sh test re-enabled in
  our test suite [2], we still need to revert that SAUCE patch to get
  it tested.

  [1] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=05d7eebf32c6872ebce6c9e5275b1ff9d91ecd16
  [2] 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=7dea7776ce431e5a1c550dc73b1d9ac0ba49698d

  [Fix]
  Revert "UBUNTU: SAUCE: selftests/net -- disable timeout"

  This test only exists in our tree since Focal.

  [Test]
  Run the net test suite in kselftest with patched source tree:
    sudo make -C linux/tools/testing/selftests TARGETS=net run_tests

  The l2tp.sh test will be executed.

  [Where problems could occur]
  This is only for testing tools, however if commit 27d53323664c54 "l2tp:
  remove skb_dst_set() from l2tp_xmit_skb()" didn't land properly we
  might crash our testing node like in bug 1854968. Also, we might see
  new failures caused by this test in the test report.

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


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

[Kernel-packages] [Bug 1934878] Re: Mute/mic LEDs no function on some HP platfroms

[AceLan Kao]

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

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

Title:
  Mute/mic LEDs no function on some HP platfroms

Status in OEM Priority Project:
  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:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 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
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]
  The mic mute/audio mute LEDS are not work on
  1) HP ProBook 630 G8 Notebook PC
  2) HP ProBook 445 G8 Notebook PC
  3) HP ProBook 450 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/1934878/+subscriptions


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

[Kernel-packages] [Bug 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)

[AceLan Kao]

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

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

Title:
  devlink_port_split in net from ubuntu_kernel_selftests linux ADT test
  failure with linux/5.11.0-18.19 ( list index out of range)

Status in ubuntu-kernel-tests:
  In Progress
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:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Committed
Status in linux-oem-5.13 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
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]
  If there is no devlink device available, the devlink_port_split.py in 
kselftest/net will fail with:
   # selftests: net: devlink_port_split.py
   # Traceback (most recent call last):
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
   # main()
   #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
   # dev = list(devs.keys())[0]
   # IndexError: list index out of range 
   not ok 43 selftests: net: devlink_port_split.py # exit=1

  [Fix]
  * 25173dd4093a24 selftests: net: devlink_port_split.py: skip the test if no 
devlink device

  This test only exist in our source tree since Hirsute, this patch can
  be cherry-picked into all affected kernels.

  [Test Plan]
  Run this test manually from the patched source tree, the test will be skipped 
when there is no devlink device:
# selftests: net: devlink_port_split.py
# no devlink device was found, test skipped
ok 7 selftests: net: devlink_port_split.py # SKIP

  [Where problems could occur]
  Change limited to testing tool, if this change is incorrect it might cause 
false-negative result in our test report.

  
  [Original Bug Report]
  This is a scripted bug report about ADT failures while running linux tests 
for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.

  Not a regression. Found to occur previously on hirsute/linux
  5.11.0-14.15

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz

  17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:39:37 DEBUG| [stdout] # Traceback (most recent call last):
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  17:39:37 DEBUG| [stdout] # main()
  17:39:37 DEBUG| [stdout] #   File 
"/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 242, in main
  17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0]
  17:39:37 DEBUG| [stdout] # IndexError: list index out of range
  17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

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


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

[Kernel-packages] [Bug 1928750] Re: Support mic-mute on Dell's platform

[AceLan Kao]

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

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

Title:
  Support mic-mute on Dell's platform

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 Committed
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]
  On Dell's platform, the MIC-Mute can't work.

  [Fix]
  Here's v8 patch, support MIC-Mute of dell e-privacy feature.
  Link: https://patchwork.kernel.org/project/alsa-devel/list/?series=477845
  The set of patches has been verified and works well on dell's machine.
  In the upstream, Hans De Goede ask dell's developer to follow ucm2 and Dell 
will upstream v9.
  For the schedule, can't wait v9 and sru v8 first.
  In the feature, will sru the final solution.

  [Test Case]
  1. fire "arecord record_file"
  2. press mic-mute hot-key and wait 20s.
  3. check the record file and can't hear voice.

  [Where problems could occur]
  Because the rt715 patch doesn't follow the ucm2, dell will upstream v9.
  In the future, will sru the final solution again.

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


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

[Kernel-packages] [Bug 1933617] Re: [ADL-S] Broken PMU hardware detected, using software events only.

[AceLan Kao]

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

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

Title:
  [ADL-S] Broken PMU hardware detected, using software events only.

Status in HWE Next:
  In Progress
Status in linux package in Ubuntu:
  In Progress
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.13 source package in Focal:
  Fix Committed

Bug description:
  [Summary]
  Broken PMU hardware detected, using software events on

  log
  04 16:04:26 u-Inspiron kernel: Broken PMU hardware detected, using software 
events only.
  04 16:04:26 u-Inspiron kernel: Failed to access perfctr msr (MSR 18e is 
)
  04 16:04:26 u-Inspiron kernel: rcu: Hierarchical SRCU implementation.
  04 16:04:26 u-Inspiron kernel: NMI watchdog: Perf NMI watchdog permanently 
disabled
  04 16:04:26 u-Inspiron kernel: smp: Bringing up secondary CPUs ...
  04 16:04:26 u-Inspiron kernel: x86: Booting SMP configuration:

  [Reproduce Steps]
  1. Boot to Ubuntu with 5.13 kernel
  2. Intel PMU driver report Broken HW detected
  3. journalctl -k

  [Results]
  Expected: PMU hardware works normally
  Actual: PMU borken hardware detected

  --
  Upstream bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=213443

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


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

[Kernel-packages] [Bug 1936201] Re: C922 Pro Stream Webcam can not work Ubuntu 21.04

[Yongqin Liu]

there is one bug reported here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885259, my kernel
version is 5.11.0-22-generic now, so the fix mentioned there should not
help for my problem here.

** Summary changed:

- C922 Pro Stream Webcam can not work Ubuntu 21.04
+ Logitech C922 Pro Stream Webcam can not work Ubuntu 21.04

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

Title:
  Logitech C922 Pro Stream Webcam can not work Ubuntu 21.04

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, All

  I just bought one Logitech C922 Pro Stream Webcam, and want to use it with my 
Thinkpad W530 with the Ubuntu 21.04 installed, but the webcamera only worked 
for the first time it's plugged in after the reboot(and sometimes even reboot 
does not help neither).
  In the dmesg log, it shows usb "device descriptor read/64, error -71" like 
the following,
  not sure if anyone has any idea about it.
  Any suggestions or solutions would be appreciated!

  [38085.691994] usb 3-2: new high-speed USB device number 2 using xhci_hcd
  [38088.082290] usb 3-2: New USB device found, idVendor=046d, idProduct=085c, 
bcdDevice= 0.16
  [38088.082303] usb 3-2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=1
  [38088.082308] usb 3-2: Product: C922 Pro Stream Webcam
  [38088.082311] usb 3-2: SerialNumber: 9C4B42DF
  [38088.083969] uvcvideo: Found UVC 1.00 device C922 Pro Stream Webcam 
(046d:085c)
  [38088.085632] input: C922 Pro Stream Webcam as 
/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input21
  [38088.260608] usbcore: registered new interface driver snd-usb-audio
  [38977.914366] loop10: detected capacity change from 0 to 819200
  [38978.461596] EXT4-fs (loop10): mounted filesystem without journal. Opts: 
(null). Quota mode: none.
  [38978.474276] EXT4-fs (loop10): resizing filesystem from 51201 to 102400 
blocks
  [38978.474283] EXT4-fs (loop10): Converting file system to meta_bg
  [38978.474452] EXT4-fs (loop10): resized filesystem to 102400
  [39139.534436] usb 1-1.2.2: USB disconnect, device number 20
  [39179.179197] usb 1-1.2.2: new high-speed USB device number 21 using ehci-pci
  [39179.291690] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
  [39179.291714] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [39179.291715] usb 1-1.2.2: Product: ADB Gadget
  [39179.291716] usb 1-1.2.2: Manufacturer: HISILICON
  [39179.291717] usb 1-1.2.2: SerialNumber: 616A34F301931D53
  [39500.491711] usb 1-1.2.2: USB disconnect, device number 21
  [39531.642830] pl2303 ttyUSB0: error sending break = -32
  [39536.042580] usb 1-1.2.2: new high-speed USB device number 22 using ehci-pci
  [39536.156831] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
  [39536.156845] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [39536.156849] usb 1-1.2.2: Product: ADB Gadget
  [39536.156852] usb 1-1.2.2: Manufacturer: HISILICON
  [39536.156855] usb 1-1.2.2: SerialNumber: 616A34F301931D53
  [39542.978321] pl2303 ttyUSB0: pl2303_get_line_request - failed: -32
  [39551.691951] usb 1-1.2.2: USB disconnect, device number 22
  [39589.813977] usb 1-1.2.2: new high-speed USB device number 23 using ehci-pci
  [39589.939365] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
  [39589.939379] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [39589.939384] usb 1-1.2.2: Product: ADB Gadget
  [39589.939387] usb 1-1.2.2: Manufacturer: HISILICON
  [39589.939390] usb 1-1.2.2: SerialNumber: 616A34F301931D53
  [39741.898063] usb 1-1.2.2: USB disconnect, device number 23
  [39789.991702] usb 1-1.2.2: new high-speed USB device number 24 using ehci-pci
  [39790.102888] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
  [39790.102902] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [39790.102915] usb 1-1.2.2: Product: ADB Gadget
  [39790.102917] usb 1-1.2.2: Manufacturer: HISILICON
  [39790.102918] usb 1-1.2.2: SerialNumber: 616A34F301931D53
  [39808.613276] pl2303 ttyUSB0: error sending break = -32
  [40491.718803] usb 1-1.2.1.3: USB disconnect, device number 12
  [40491.718996] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
  [40491.719021] pl2303 1-1.2.1.3:1.0: device disconnected
  [40492.484803] usb 1-1.2.2: USB disconnect, device number 24
  [40493.530905] usb 3-2: USB disconnect, device number 2
  [40493.916881] usb 3-2: new full-speed USB device number 3 using xhci_hcd
  [40494.048924] usb 3-2: device descriptor read/64, error -71
  [40494.288892] usb 3-2: device descriptor read/64, error -71
  [40494.532877] usb 3-2: new full-speed USB device number 4 using xhci_hcd
  [40494.664868] usb 3-2: device descriptor read/64, error -71
  [40494.900883] usb 3-2: device 

[Kernel-packages] [Bug 1936201] [NEW] Logitech C922 Pro Stream Webcam can not work Ubuntu 21.04

[Yongqin Liu]

Public bug reported:

Hi, All

I just bought one Logitech C922 Pro Stream Webcam, and want to use it with my 
Thinkpad W530 with the Ubuntu 21.04 installed, but the webcamera only worked 
for the first time it's plugged in after the reboot(and sometimes even reboot 
does not help neither).
In the dmesg log, it shows usb "device descriptor read/64, error -71" like the 
following,
not sure if anyone has any idea about it.
Any suggestions or solutions would be appreciated!

[38085.691994] usb 3-2: new high-speed USB device number 2 using xhci_hcd
[38088.082290] usb 3-2: New USB device found, idVendor=046d, idProduct=085c, 
bcdDevice= 0.16
[38088.082303] usb 3-2: New USB device strings: Mfr=0, Product=2, SerialNumber=1
[38088.082308] usb 3-2: Product: C922 Pro Stream Webcam
[38088.082311] usb 3-2: SerialNumber: 9C4B42DF
[38088.083969] uvcvideo: Found UVC 1.00 device C922 Pro Stream Webcam 
(046d:085c)
[38088.085632] input: C922 Pro Stream Webcam as 
/devices/pci:00/:00:14.0/usb3/3-2/3-2:1.0/input/input21
[38088.260608] usbcore: registered new interface driver snd-usb-audio
[38977.914366] loop10: detected capacity change from 0 to 819200
[38978.461596] EXT4-fs (loop10): mounted filesystem without journal. Opts: 
(null). Quota mode: none.
[38978.474276] EXT4-fs (loop10): resizing filesystem from 51201 to 102400 blocks
[38978.474283] EXT4-fs (loop10): Converting file system to meta_bg
[38978.474452] EXT4-fs (loop10): resized filesystem to 102400
[39139.534436] usb 1-1.2.2: USB disconnect, device number 20
[39179.179197] usb 1-1.2.2: new high-speed USB device number 21 using ehci-pci
[39179.291690] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
[39179.291714] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[39179.291715] usb 1-1.2.2: Product: ADB Gadget
[39179.291716] usb 1-1.2.2: Manufacturer: HISILICON
[39179.291717] usb 1-1.2.2: SerialNumber: 616A34F301931D53
[39500.491711] usb 1-1.2.2: USB disconnect, device number 21
[39531.642830] pl2303 ttyUSB0: error sending break = -32
[39536.042580] usb 1-1.2.2: new high-speed USB device number 22 using ehci-pci
[39536.156831] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
[39536.156845] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[39536.156849] usb 1-1.2.2: Product: ADB Gadget
[39536.156852] usb 1-1.2.2: Manufacturer: HISILICON
[39536.156855] usb 1-1.2.2: SerialNumber: 616A34F301931D53
[39542.978321] pl2303 ttyUSB0: pl2303_get_line_request - failed: -32
[39551.691951] usb 1-1.2.2: USB disconnect, device number 22
[39589.813977] usb 1-1.2.2: new high-speed USB device number 23 using ehci-pci
[39589.939365] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
[39589.939379] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[39589.939384] usb 1-1.2.2: Product: ADB Gadget
[39589.939387] usb 1-1.2.2: Manufacturer: HISILICON
[39589.939390] usb 1-1.2.2: SerialNumber: 616A34F301931D53
[39741.898063] usb 1-1.2.2: USB disconnect, device number 23
[39789.991702] usb 1-1.2.2: new high-speed USB device number 24 using ehci-pci
[39790.102888] usb 1-1.2.2: New USB device found, idVendor=18d1, 
idProduct=4ee7, bcdDevice= 2.23
[39790.102902] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[39790.102915] usb 1-1.2.2: Product: ADB Gadget
[39790.102917] usb 1-1.2.2: Manufacturer: HISILICON
[39790.102918] usb 1-1.2.2: SerialNumber: 616A34F301931D53
[39808.613276] pl2303 ttyUSB0: error sending break = -32
[40491.718803] usb 1-1.2.1.3: USB disconnect, device number 12
[40491.718996] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
[40491.719021] pl2303 1-1.2.1.3:1.0: device disconnected
[40492.484803] usb 1-1.2.2: USB disconnect, device number 24
[40493.530905] usb 3-2: USB disconnect, device number 2
[40493.916881] usb 3-2: new full-speed USB device number 3 using xhci_hcd
[40494.048924] usb 3-2: device descriptor read/64, error -71
[40494.288892] usb 3-2: device descriptor read/64, error -71
[40494.532877] usb 3-2: new full-speed USB device number 4 using xhci_hcd
[40494.664868] usb 3-2: device descriptor read/64, error -71
[40494.900883] usb 3-2: device descriptor read/64, error -71
[40495.008926] usb usb3-port2: attempt power cycle
[40495.668857] usb 3-2: new full-speed USB device number 5 using xhci_hcd
[40495.668990] usb 3-2: Device not responding to setup address.
[40495.876978] usb 3-2: Device not responding to setup address.
[40496.084852] usb 3-2: device not accepting address 5, error -71
[40497.968831] usb 3-2: new full-speed USB device number 7 using xhci_hcd
[40498.100843] usb 3-2: device descriptor read/64, error -71
[40498.336855] usb 3-2: device descriptor read/64, error -71
[40498.580839] usb 3-2: new full-speed USB device number 8 using xhci_hcd
[40498.708850] usb 3-2: device descriptor read/64, error -71
[40498.952836] usb 3-2: device descriptor read/64, 

[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~kchsieh/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/405682

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

Title:
  [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
  wireless [8086:a0f0]

Status in Linux Firmware:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Whenever I am using a wireless connection, the image freezes roughly
  every two minutes. Sometimes, email cannot be retrieved / computer
  complains the connection was momentarily lost.

  - If I am on a wire, this problem does NOT occur.
  - This problems occurs on wireless independent of the platform used (behavior 
seen in both Google Hangout and Zoom)
  - This problem does NOT occur on Windows. I did a meeting where both my Linux 
and Windows machines were connected to the same meeting and using the same wifi 
router, and while the performance on Windows was flawless, unfortunately it was 
not so on the Ubuntu box. So I don't think my wifi router or network is to 
blame.
  - As far as I can recall, the problem used not to be there 2 weeks ago. So it 
may have been introduced by a recent update.
  - As communicated before, I am on a certified machine from Dell, recently 
purchased with Ubuntu already on board from factory (I assume the logs there 
were sent to you would contain the information).
  - I tried to generate a log on the wireless, but the process did not let me 
do this very easily. I am more than happy to send you additional information - 
but please let me know which package you want me to spy upon exactly, as I am 
not sure what would be helpful in this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
  Uname: Linux 5.10.0-1029-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 18 09:47:58 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0991]
  InstallationDate: Installed on 2021-04-24 (54 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem 
root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 2.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.1
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/linux-firmware/+bug/1932548/+subscriptions


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

[Kernel-packages] [Bug 1934741] Re: Add new PCI MMIO based thermal driver [8086:461d] for Intel Alder Lake

[You-Sheng Yang]

SRU: https://lists.ubuntu.com/archives/kernel-team/2021-July/122406.html
(impish, oem-5.13)

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]  
   
[18/14083]
+  
+ On Intel Alder Lake platforms, processor thermal device provides an
+ additional thermal zone TCPU_PCI that is based on a new PCI MMIO only
+ driver.
+   
 
+ [Fix] 
 
+   
 
+ Two upstream v5.14-rc1 commits to backport.   
+   
 
+ [Test Case]   
 
+   
 
+ $ lspci -vvnns 00:04.0
 
+ 00:04.0 Signal processing controller [1180]: Intel Corporation Device 

 
+ [8086:461d] (rev 01)  

 
+ Subsystem: Intel Corporation Device [8086:7270]
+ ...
+  
+ # thermal_zones provided by the original driver
+ $ cat /sys/devices/virtual/thermal/thermal_zone*/type
+ acpitz
+ INT3400 Thermal
+ TCPU
+ x86_pkg_temp
+ 
+ # thermal_zones provided by the new driver
+ $ cat /sys/devices/virtual/thermal/thermal_zone*/type
+ acpitz
+ INT3400 Thermal
+ TCPU
+ TCPU_PCI
+ x86_pkg_temp
+ 
+ [Where problems could occur]
+ 
+ These changes do not change existing interface to userspace, but add an
+ additional thermal zone that doesn't involve ACPI method calls for use.
+ 
+ [Other Info]
+ 
+ ADL targets 5.13 kernel, so only Impish and oem-5.13 are nominated.
+ 
+ == original bug description ==
+ 
  $ lspci -vvnns 00:04.0
  00:04.0 Signal processing controller [1180]: Intel Corporation Device 
[8086:461d] (rev 01)
  Subsystem: Intel Corporation Device [8086:7270]
  Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: proc_thermal
  Kernel modules: processor_thermal_device
  
  [original]
  $ cat /sys/devices/virtual/thermal/thermal_zone*/type
  acpitz
  INT3400 Thermal
  TCPU
  x86_pkg_temp
  
  [patched]
  $ cat /sys/devices/virtual/thermal/thermal_zone*/type
  acpitz
  INT3400 Thermal
  TCPU
  TCPU_PCI
  x86_pkg_temp
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1367 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X130
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-06-18 (18 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  IwConfig:
   lono wireless extensions.
  
   enp0s31f6  no wireless extensions.
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-2006-oem 
root=UUID=a4f90fb9-1c2c-4d37-be7a-1b67b667c378 ro automatic-oem-config quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-2006.6+lp1934660.1.adl.pmc.core-oem 5.13.0
  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.13.0-2006-oem N/A
   linux-backports-modules-5.13.0-2006-oem  N/A
   linux-firmware   1.187.15
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  Tags:  focal
  Uname: Linux 5.13.0-2006-oem x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 02/25/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLSFWI1.R00.2081.A02.2102250858
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB
  dmi.board.vendor: Intel 

[Kernel-packages] [Bug 1912811] Re: Update dwarves-dfsg in focal to version 1.21 from hirsute

[Dimitri John Ledkov]

** Description changed:

  [Impact]
  
  BTF is an extremely useful tool for BPF developers. Enabling BTF support
- in the kernel requires pahole 1.16 or later, but in focal we have only
- 1.15. The simplest path for us to get a sufficiently updated version of
- pahole is to backport dwarves-dfsg from groovy, which is at version
- 1.17.
+ in the HWE kernel requires pahole from dwarves-dfsg 1.21 or later, but
+ in focal we have only 1.15. The simplest path for us to get a
+ sufficiently updated version of pahole is to backport dwarves-dfsg from
+ hirsute, which is at version 1.21 with v5.13 compat fixes.
  
  [Test Case]
  
  Building a kernel with CONFIG_DEBUG_INFO_BTF enabled fails with the
  version of pahole currently in focal, complaining that pahole 1.16 or
  later is needed. Building with a newer version of pahole is successful.
  
  [Where problems could occur]
  
  Moving the package forward carries significant risks. The biggest risk
  is clearly new bugs. There may also be interface changes which break
  existing workflows. I believe the following factors indicate that the
  level of risk here is acceptable:
  
-  * Currently there are no bug reports open against the package in groovy
+  * Currently there are no bug reports open against the package in groovy
  (there are virtually no bug reports open at all against the package in
  fact).
  
-  * I have done a review of the changes between 1.15 and 1.17. The bulk
+  * I have done a review of the changes between 1.15 and 1.21. The bulk
  of the changes are for the required BTF support, and the vast majority
  of these are an update of its local copy of libbpf. The balance of the
  changes are bug fixes and enhancements to pahole, none of which look to
  change the user interface in a way which will break existing workflows.
+ Note that in later releases libbpf is now packaged stand alone, so this
+ SRU covers libbpf as well.
  
-  * No packages in focal have dependencies or build dependencies on the
+  * But also the 1.15 dwarves is kind of useless, as it doesn't work with
+ latest kernels for the BPF features.
+ 
+  * No packages in focal have dependencies or build dependencies on the
  dwarves package.

** Also affects: dwarves-dfsg (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: dwarves-dfsg (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

** Changed in: libbpf (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update dwarves-dfsg in focal to version 1.21 from hirsute

Status in dwarves-dfsg package in Ubuntu:
  Invalid
Status in libbpf package in Ubuntu:
  Fix Released
Status in dwarves-dfsg source package in Focal:
  In Progress
Status in libbpf source package in Focal:
  New
Status in dwarves-dfsg source package in Groovy:
  New
Status in libbpf source package in Groovy:
  New
Status in dwarves-dfsg source package in Hirsute:
  New
Status in libbpf source package in Hirsute:
  New

Bug description:
  [Impact]

  BTF is an extremely useful tool for BPF developers. Enabling BTF
  support in the HWE kernel requires pahole from dwarves-dfsg 1.21 or
  later, but in focal we have only 1.15. The simplest path for us to get
  a sufficiently updated version of pahole is to backport dwarves-dfsg
  from hirsute, which is at version 1.21 with v5.13 compat fixes.

  [Test Case]

  Building a kernel with CONFIG_DEBUG_INFO_BTF enabled fails with the
  version of pahole currently in focal, complaining that pahole 1.16 or
  later is needed. Building with a newer version of pahole is
  successful.

  [Where problems could occur]

  Moving the package forward carries significant risks. The biggest risk
  is clearly new bugs. There may also be interface changes which break
  existing workflows. I believe the following factors indicate that the
  level of risk here is acceptable:

   * Currently there are no bug reports open against the package in
  groovy (there are virtually no bug reports open at all against the
  package in fact).

   * I have done a review of the changes between 1.15 and 1.21. The bulk
  of the changes are for the required BTF support, and the vast majority
  of these are an update of its local copy of libbpf. The balance of the
  changes are bug fixes and enhancements to pahole, none of which look
  to change the user interface in a way which will break existing
  workflows. Note that in later releases libbpf is now packaged stand
  alone, so this SRU covers libbpf as well.

   * But also the 1.15 dwarves is kind of useless, as it doesn't work
  with latest kernels for the BPF features.

   * No packages in focal have dependencies or build dependencies on the
  dwarves package.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI

[Keith Jackson]

Do we have an ETA for this? I've had to essentially block any system
upgrades on my desktop since this began after having to roll back a
kernel update that forced this bug on me.

I noticed a new kernel update has just been posted and doesn't seem to
have rolled out this issue yet again.

This isn't a minor annoyance, this is a complete system fail type bug.

This NVidia forum thread has been really useful here:
https://forums.developer.nvidia.com/t/465-24-

It's looking like the bug on NVidia's side seems to have been rectified
in 470.42 - Manjaro have put that to their stable branch, yet I'm not
seeing anything in Ubuntu even in pre-release beyond 460.84.

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

Title:
  Kernel oops with the 460.80 and 465.27 drivers when using DP, but not
  with HDMI

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Triaged

Bug description:
  I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute

  Jun 03 16:26:57 willow kernel: Oops:  [#1] SMP PTI
  Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P 
  OE 5.11.0-18-generic #19-Ubuntu
  Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System 
Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019
  Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia]
  Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 
00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 
44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8>
  Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297
  Jun 03 16:26:57 willow kernel: RAX:  RBX: 0400 
RCX: 0003
  Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 
RDI: 
  Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 
R09: 8e318220acb8
  Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 
R12: 0400
  Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 
R15: 0800
  Jun 03 16:26:57 willow kernel: FS:  7f5807f38a40() 
GS:8e3466dc() knlGS:
  Jun 03 16:26:57 willow kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 
CR4: 003706e0
  Jun 03 16:26:57 willow kernel: DR0:  DR1:  
DR2: 
  Jun 03 16:26:57 willow kernel: DR3:  DR6: fffe0ff0 
DR7: 0400
  Jun 03 16:26:57 willow kernel: Call Trace:
  Jun 03 16:26:57 willow kernel:  ? _nv015556rm+0x7fd/0x1020 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv027155rm+0x22c/0x4f0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017787rm+0x303/0x5e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv017789rm+0xe1/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv022829rm+0xed/0x220 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv023065rm+0x30/0x60 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? _nv000704rm+0x16da/0x22b0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? rm_init_adapter+0xc5/0xe0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nv_open_device+0x122/0x8e0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_open+0x2b7/0x560 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? nvidia_frontend_open+0x58/0xa0 [nvidia]
  Jun 03 16:26:57 willow kernel:  ? chrdev_open+0xf7/0x220
  Jun 03 16:26:57 willow kernel:  ? cdev_device_add+0x90/0x90
  Jun 03 16:26:57 willow kernel:  ? do_dentry_open+0x156/0x370
  Jun 03 16:26:57 willow kernel:  ? vfs_open+0x2d/0x30
  Jun 03 16:26:57 willow kernel:  ? do_open+0x1c3/0x340
  Jun 03 16:26:57 willow kernel:  ? path_openat+0x10a/0x1d0
  Jun 03 16:26:57 willow kernel:  ? do_filp_open+0x8c/0x130
  Jun 03 16:26:57 willow kernel:  ? __check_object_size+0x1c/0x20
  Jun 03 16:26:57 willow kernel:  ? do_sys_openat2+0x9b/0x150
  Jun 03 16:26:57 willow kernel:  ? __x64_sys_openat+0x56/0x90
  Jun 03 16:26:57 willow kernel:  ? do_syscall_64+0x38/0x90
  Jun 03 16:26:57 willow kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) 
zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) >
  Jun 03 16:26:57 willow kernel:  sunrpc ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c>
  Jun 03 16:26:57 willow kernel: CR2: 0170
  Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]---
  Jun 03 16:26:57 willow kernel: RIP: 

[Kernel-packages] [Bug 1931843] Re: Update mlx-bootctl to access new fields in EEPROM MFG

[Stefan Bader]

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

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

Title:
  Update mlx-bootctl to access new fields in EEPROM MFG

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

Bug description:
  SRU Justification:

  [Impact]
  The EEPROM MFG partition on BlueField-2 has been updated to include the VPD 
information for each card. In order to access these newly added fields, the 
mlx-bootctl driver needs to be updated to provide an access mechanism.

  [Fix]
  Add support for VPD fields in the EEPROM MFG and provide access to these via 
sysfs entries. The newly added sysfs entries are: sku (SKU ID), modl (Model 
Number), sn (Serial Number) and uuid (UUID). And the previously added opn_str 
sysfs has been renamed to opn.

  [Test Case]
  Though the driver provides read and write access through sysfs, the contents 
of the MFG partition are written during Manufacturing and then locked in order 
to protect the info. Writing to this partition will therefore require resetting 
the MFG info from the UEFI Device Manager, which will unlock the partition and 
allow for it to be reprogrammed.
  Reading the sysfs entries will print the contents of each field. It could 
also be empty if the field was not programmed earlier.

  [Regression Potential]
  Can be considered minimum, since the new fields have been added without 
interfering with the existing fields which might already be present in the 
EEPROM.

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


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

[Kernel-packages] [Bug 1934819] Re: Fix err check for nf_conntrack_confirm

[Stefan Bader]

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

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

Title:
  Fix err check for nf_conntrack_confirm

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

Bug description:
  
  * Explain the bug(s)

  Conntrack confirm operation wasn't checked, this could result in
  accepting packet which should be dropped.

  * brief explanation of fixes

  Match behavior of ovs and netfilter. Drop the packets which are not
  accepted.

  * How to test

  First observe packets accepted with status of NF_DROP without the fix.
  Then observe packets are correctly dropped with the patch.

  * What it could break.

  Nothing breaks, but fixing security hole.

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


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

[Kernel-packages] [Bug 1934822] Re: Possible memory leak of flow_block_cb

[Stefan Bader]

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

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

Title:
  Possible memory leak of flow_block_cb

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

Bug description:
  * Explain the bug(s)

  When cleaning up the nf_table in tcf_ct_flow_table_cleanup_work
  there is no guarantee that the callback list, added to by
  nf_flow_table_offload_add_cb, is empty. This means that it is
  possible that the flow_block_cb memory allocated will be lost.

  
  * brief explanation of fixes

  Fix this by iterating the list and freeing the flow_block_cb entries
  before freeing the nf_table entry (via freeing ct_ft).

  * How to test

  With mlx5 driver registers flow block callback, cleaning up rule with action 
ct
  frees the ct_ft but with memory leak.

  * What it could break.

  Nothing breaks, memory leak is fixed.

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


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

[Kernel-packages] [Bug 1934401] Re: Control netfilter flow table timeouts via sysctl

[Stefan Bader]

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

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

Title:
  Control netfilter flow table timeouts via sysctl

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

Bug description:
  * Explain the bug(s)
   
  TCP and UDP connections may be offloaded from nf conntrack to nf flow table.
  Offloaded connections are aged after 30 seconds of inactivity. 
  Once aged, ownership is returned to conntrack with a hard coded tcp/udp 
pickup time of 120/30 seconds, after which the connection may be deleted. 

  The current hard-coded pickup intervals may introduce a very
  aggressive aging policy. For example, offloaded tcp connections in
  established state will timeout from nf conntrack after just 150
  seconds of inactivity, instead of 5 days. In addition, the hard-coded
  30 second offload timeout period can significantly increase the
  hardware insertion rate requirements in some use cases.

  
  * Brief explanation of fixes
   
  This patchset provides the user with the ability to configure protocol 
specific offload timeout and pickup intervals via sysctl.

  The first and second patches revert the existing non-upstream solution.
  The next two patches introduce the sysctl configuration for tcp and udp 
protocols.
  The last patch modifies nf flow table aging mechanisms to use the configured 
time intervals. 
   
  * How to test

  Control tcp/udp connection timeout using the following sysctl parameters:
  net.netfilter.nf_flowtable_tcp_pickup = 120 
net.netfilter.nf_flowtable_tcp_timeout = 30 
net.netfilter.nf_flowtable_udp_pickup = 30 
net.netfilter.nf_flowtable_udp_timeout = 30 
   
  * What it could break.
   
  Existing configuration scripts – not kernel related

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


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

[Kernel-packages] [Bug 1870971] Re: [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API when in battery mode

[Jeffrey Walton]

Add an Acer Aspire 5 Laptop
(https://www.amazon.com/gp/product/B07RF1XD36) to the list of problem
platforms.

The machine was just upgraded to Linux Mint 20.2. Mint 20.1 was OK.
Linux Mint 20 is based on Ubuntu 20.04 LTS.

-

$ dmesg | grep -i error
[0.755376] RAS: Correctable Errors collector initialized.
[0.775485] Error adding keys to platform keyring UEFI:db
[0.775487] Error adding keys to platform keyring UEFI:db
[8.440674] EXT4-fs (nvme0n1p2): re-mounted. Opts: errors=remount-ro
[9.210068] snd_rn_pci_acp3x: probe of :05:00.5 failed with error -22
[   20.681023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, 
signaled seq=1, emitted seq=4
[   20.681156] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: 
process Xorg pid 688 thread Xorg:cs0 pid 742
[   25.505358] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
[   25.505562] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
[   25.505769] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
[   25.505985] [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
[   25.506167] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
[   25.506369] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
[   25.506579] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
[   25.506789] [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
[   25.507012] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
[   25.507220] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
[   25.507402] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
[   25.507601] [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3

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

Title:
  [amdgpu] (X)ubuntu 20.04 boots to black screen on Lenovo Ideapad
  L340-17API when in battery mode

Status in linux package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Freshly installed Xubuntu 20.04 shows black screen instead of login
  screen upon boot on Lenovo Ideapad L340-17API. It is not possible to
  chvt to text terminal when boot is stuck on black screen.

  Booting with 'nomodeset' kernel option works properly but is not an
  option (e.g. screen brightness is not adjustable in this case).

  Another workaround is to ssh to laptop and run systemctl restart
  display-manager.service. After 5-10 seconds upon executing this
  command perfectly working login screen appears.

  Check dmesg. There is apparently related messages from amdgpu driver:

  ...
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_crtc_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_crtc_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_pflip_irq_state [amdgpu]] *ERROR* 
amdgpu_dm_set_pflip_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm:amdgpu_dm_set_vupdate_irq_state [amdgpu]] 
*ERROR* amdgpu_dm_set_vupdate_irq_state: crtc is NULL at id :3
  апр 05 20:46:45 kernel: [drm] recover vram bo from shadow start
  апр 05 20:46:45 kernel: [drm] recover vram bo from 

[Kernel-packages] [Bug 1935584] Re: Fix host to pod traffic with ovn cluster using ovs internal port and tc offload

[Stefan Bader]

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

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

Title:
  Fix host to pod traffic with ovn cluster using ovs internal port and
  tc offload

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

Bug description:
  * Explain the bug(s)

  When using ovs internal port with tc the redirect rules to internal port is 
back
  to ingress instead of egress.
  When we reinsert the skb we start from chain 0 but it could be ct state 
already
  set so matching rules on the internal port queue would miss.

  * brief explanation of fixes

  When reinserting skb back to ingress queue to restart tc
  classification then also reset ct.

  * How to test

  The setup was created by using ovn and testing iperf traffic from host 
container to VF pod.
  The result was ip set on the ovs bridge netdev (internal port)
  The rules were from rep to eventually the internal port and internal port to 
rep.
  The rules were with ct actions and chains tc-policy was set to skip-hw.
  Without the commit the traffic doesn’t work when hw-offload was true (offload 
to tc sw only) but
  does work with hw-offload false (ovs dp).

  * What it could break.

  Traffic not working in some cases using internal ports and CT.

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


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

[Kernel-packages] [Bug 1934304] Re: i2c-mlxbf.c: prevent stack overflow in mlxbf_i2c_smbus_start_transaction

[Stefan Bader]

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

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

Title:
  i2c-mlxbf.c: prevent stack overflow in
  mlxbf_i2c_smbus_start_transaction

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

Bug description:
  SRU Justification:

  [Impact]

  There could be stack overflow in mlxbf_i2c_smbus_start_transaction().
  memcpy() is called in a loop while 'operation->length' upper bound is not
  checked and 'data_idx' also increments.

  More details:
  The operation length is verified by the caller functions so it cannot exceed 
I2C_SMBUS_BLOCK_MAX bytes (32 bytes) for each operation that is a part of the 
write. Data_desc array is 128 bytes in size. So potentially a request which 
consists of 4 writes, 32 bytes each can trigger an off-by-one or off-by-two 
overflow, because the first byte of data_desc is used by addr, effectively 
decreasing the available data_desc buffer size by one. Functions like 
mlx_smbus_i2c_block_func() that prepare the request also set the length of the 
first write operation to one and store the command id there, so the target 
buffer size again decreases data_desc by one, making it two bytes less than 
expected.

  [Fix]

  * Add a check for "operation->length" and data_idx and return error if
  reached upper bound.

  [Test Case]

  * Test the i2c-mlxbf.c driver using IPMB functionality.

  [Regression Potential]

  This fix returns a negative value to indicate that a transaction has
  failed. So it will catch more transactions failures.

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


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

[Kernel-packages] [Bug 1932548] Re: [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]

[Alex Tu]

progress update:
 - Vicamo is SRUing related firmware for both oem 5.10, hwe 5.11 and oem 5.13.
   - for OEM 5.10, HWE 5.11: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217
   - for OEM 5.13: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415

@Steve,
per #17, the firmware for OEM 5.10(LP: #1934217) not works for you.
Could you please have a try on OEM 5.13 + firmware from LP: #1933415?

The firmware crashing looks not happens to every machine using AX201.
 - Vicamo can not reproduce it with wifi6 AP during both SRU (LP: #1934217 and 
LP: 1933415)
 - It passed with OEM 5.10 + firmware(LP: #1934217)
 - But it failed with OEM 5.10 + firmware(LP: #1934217) on Steve's machine (per 
#17)

So, we are asking Intel for a suggested combination of Kernel and
firmware to make sure the stability of AX201.

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

Title:
  [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
  wireless [8086:a0f0]

Status in Linux Firmware:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Whenever I am using a wireless connection, the image freezes roughly
  every two minutes. Sometimes, email cannot be retrieved / computer
  complains the connection was momentarily lost.

  - If I am on a wire, this problem does NOT occur.
  - This problems occurs on wireless independent of the platform used (behavior 
seen in both Google Hangout and Zoom)
  - This problem does NOT occur on Windows. I did a meeting where both my Linux 
and Windows machines were connected to the same meeting and using the same wifi 
router, and while the performance on Windows was flawless, unfortunately it was 
not so on the Ubuntu box. So I don't think my wifi router or network is to 
blame.
  - As far as I can recall, the problem used not to be there 2 weeks ago. So it 
may have been introduced by a recent update.
  - As communicated before, I am on a certified machine from Dell, recently 
purchased with Ubuntu already on board from factory (I assume the logs there 
were sent to you would contain the information).
  - I tried to generate a log on the wireless, but the process did not let me 
do this very easily. I am more than happy to send you additional information - 
but please let me know which package you want me to spy upon exactly, as I am 
not sure what would be helpful in this matter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
  Uname: Linux 5.10.0-1029-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 18 09:47:58 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0991]
  InstallationDate: Installed on 2021-04-24 (54 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem 
root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2021
  dmi.bios.release: 2.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.1
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 

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

[Kai-Heng Feng]

** Description changed:

  [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]
- Should be low risk, it's only firmware for renoir systems loaded by amdgpu 
that needs to be updating.
+ 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.

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

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