[Kernel-packages] [Bug 1957026] Re: AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

[You-Sheng Yang]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127429.html 
(linux-firmware/focal)

** Description changed:

- TBD.
+ [SRU Justification]
+ 
+ [Impact]
+ 
+ On AMD Yellow Carp B0 platforms, S0i3 is still not working.
+ 
+ [Fix]
+ 
+ This denpends on a few fixes for kernel driver that are all either in
+ v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed
+ dmcub firmware.
+ 
+ [Test Case]
+ 
+ On AMD RMT CRB board,
+ 1. apply both kernel and firmware fixes
+ 2. module blacklist amd_sfh as it's still under development,
+ 3. trigger system suspend. Use power button to wake up the device.
+ 4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero
+ 
+ On without any of above, the board may not cut device power during
+ suspend, and/or fail to resume and leaving a blank screen, and/or s0ix
+ stats remain all zeros.
+ 
+ [Where problems could occur]
+ 
+ So far all the patches can be cleanly applied, and they're being
+ progressively proposed to linux-stable.
+ 
+ [Other Info]
+ 
+ For kernel driver fixes, patches for both oem-5.14 and jammy are
+ necessary; for firmware, that has been available in jammy branch but not
+ yet released, so only Focal will be nominated.

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

Title:
  AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  In Progress
Status in linux source package in Jammy:
  In Progress
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  On AMD Yellow Carp B0 platforms, S0i3 is still not working.

  [Fix]

  This denpends on a few fixes for kernel driver that are all either in
  v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed
  dmcub firmware.

  [Test Case]

  On AMD RMT CRB board,
  1. apply both kernel and firmware fixes
  2. module blacklist amd_sfh as it's still under development,
  3. trigger system suspend. Use power button to wake up the device.
  4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero

  On without any of above, the board may not cut device power during
  suspend, and/or fail to resume and leaving a blank screen, and/or s0ix
  stats remain all zeros.

  [Where problems could occur]

  So far all the patches can be cleanly applied, and they're being
  progressively proposed to linux-stable.

  [Other Info]

  For kernel driver fixes, patches for both oem-5.14 and jammy are
  necessary; for firmware, that has been available in jammy branch but
  not yet released, so only Focal will be nominated.

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


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

[Kernel-packages] [Bug 1959064] Re: [SRU][F] Add mt8183 SCP firmware

[Juerg Haefliger]

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

Title:
  [SRU][F] Add mt8183 SCP firmware

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

Bug description:
  [Impact]
  No driver is loaded for scp firmware on the mt8183 platform, and fw is 
missing too.

  [Fix]
  Add mt8183 SCP firmware

  [Test]
  Verified on the mt8183 platform, it can be loaded and powered up.

  [Where problems could occur]
  This firmware is specific for mt8183, it should be low risk.

  The firmware is already in impish and jammy, only SRU fw for focal.

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


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

[Kernel-packages] [Bug 1959073] [NEW] kernel unable to detect disks on ASMedia Technology Inc. ASM1062 controller

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Upgraded from 21.10 to 22.04. Kernel is no longer able to detect speed of disks 
on "ASMedia Technology Inc. ASM1062" controller:
[1.262159] ata5: SATA max UDMA/133 abar m512@0xdf81 port 0xdf810100 irq 
166
[1.945237] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[1.945242] ata5.00: link online but device misclassified
[1.945243] ata5: link online but 1 devices misclassified, retrying
[1.945244] ata5: reset failed (errno=-11), retrying in 10 secs
[   11.941338] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   11.941436] ata5.00: link online but device misclassified
[   11.941586] ata5: link online but 1 devices misclassified, retrying
[   11.941759] ata5: reset failed (errno=-11), retrying in 10 secs
[   22.181347] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   22.181443] ata5.00: link online but device misclassified
[   22.181594] ata5: link online but 1 devices misclassified, retrying
[   22.181740] ata5: reset failed (errno=-11), retrying in 35 secs
[   58.569320] ata5: limiting SATA link speed to 1.5 Gbps
[   59.045347] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   59.045359] ata5.00: link online but device misclassified
[   59.045519] ata5: link online but 1 devices misclassified, device detection 
might fail

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: udisks2 2.9.4-1
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: unknown
CustomUdevRuleFiles: md126.rules md127.rules 60-vboxdrv.rules 70-snap.core.rules
Date: Wed Jan 26 08:44:00 2022
InstallationDate: Installed on 2020-04-10 (655 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046d:c317 Logitech, Inc. Wave Corded Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=d2123ad2-32ac-4a77-abf1-468ac80f097c ro
SourcePackage: udisks2
Symptom: storage
Title: Internal hard disk partition cannot be mounted manually
UpgradeStatus: Upgraded to jammy on 2022-01-26 (0 days ago)
dmi.bios.date: 03/14/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3801
dmi.board.asset.tag: Default string
dmi.board.name: Z170-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PRO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug jammy uec-images
-- 
kernel unable to detect disks on ASMedia Technology Inc. ASM1062 controller
https://bugs.launchpad.net/bugs/1959073
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1959073] Re: kernel unable to detect disks on ASMedia Technology Inc. ASM1062 controller

[Sebastien Bacher]

** Package changed: udisks2 (Ubuntu) => linux (Ubuntu)

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

Title:
  kernel unable to detect disks on ASMedia Technology Inc. ASM1062
  controller

Status in linux package in Ubuntu:
  New

Bug description:
  Upgraded from 21.10 to 22.04. Kernel is no longer able to detect speed of 
disks on "ASMedia Technology Inc. ASM1062" controller:
  [1.262159] ata5: SATA max UDMA/133 abar m512@0xdf81 port 0xdf810100 
irq 166
  [1.945237] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [1.945242] ata5.00: link online but device misclassified
  [1.945243] ata5: link online but 1 devices misclassified, retrying
  [1.945244] ata5: reset failed (errno=-11), retrying in 10 secs
  [   11.941338] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [   11.941436] ata5.00: link online but device misclassified
  [   11.941586] ata5: link online but 1 devices misclassified, retrying
  [   11.941759] ata5: reset failed (errno=-11), retrying in 10 secs
  [   22.181347] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
  [   22.181443] ata5.00: link online but device misclassified
  [   22.181594] ata5: link online but 1 devices misclassified, retrying
  [   22.181740] ata5: reset failed (errno=-11), retrying in 35 secs
  [   58.569320] ata5: limiting SATA link speed to 1.5 Gbps
  [   59.045347] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
  [   59.045359] ata5.00: link online but device misclassified
  [   59.045519] ata5: link online but 1 devices misclassified, device 
detection might fail

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CustomUdevRuleFiles: md126.rules md127.rules 60-vboxdrv.rules 
70-snap.core.rules
  Date: Wed Jan 26 08:44:00 2022
  InstallationDate: Installed on 2020-04-10 (655 days ago)
  InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 
(20200402)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c317 Logitech, Inc. Wave Corded Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=d2123ad2-32ac-4a77-abf1-468ac80f097c ro
  SourcePackage: udisks2
  Symptom: storage
  Title: Internal hard disk partition cannot be mounted manually
  UpgradeStatus: Upgraded to jammy on 2022-01-26 (0 days ago)
  dmi.bios.date: 03/14/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3801
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3801:bd03/14/2018:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-PRO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Kernel-packages] [Bug 1959083] [NEW] ?

[timoti69]

Public bug reported:

?

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-49-generic 5.11.0-49.55
ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22
Uname: Linux 5.11.0-49-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  thierry5638 F pulseaudio
 /dev/snd/controlC1:  thierry5638 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Jan 26 10:08:38 2022
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-49-generic 
root=UUID=d6ff8388-8b51-437e-b6df-eee0ecab45ee ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.11.0-49-generic N/A
 linux-backports-modules-5.11.0-49-generic  N/A
 linux-firmware 1.197.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug hirsute

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

Title:
  ?

Status in linux package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-49-generic 5.11.0-49.55
  ProcVersionSignature: Ubuntu 5.11.0-49.55-generic 5.11.22
  Uname: Linux 5.11.0-49-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thierry5638 F pulseaudio
   /dev/snd/controlC1:  thierry5638 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Jan 26 10:08:38 2022
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-49-generic 
root=UUID=d6ff8388-8b51-437e-b6df-eee0ecab45ee ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-49-generic N/A
   linux-backports-modules-5.11.0-49-generic  N/A
   linux-firmware 1.197.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:skuSKU:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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

[Kernel-packages] [Bug 1958774] Re: Blackscreen after suspending and closing LID

[Chuyang Chen]

To Thomas: Thank you very much for providing me these tips.
Unfortunately, I'm not an OS developer and quite unfamiliar with OS
debugging and developing... What I can give is only the above bug
description. 😢

** Description changed:

  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:
  
  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).
  
  These bugs really trouble me. It will be very helpful if you fix it.
  
  UPDATE at 2022/01/25: After I upgraded the "core" package using "snap
  refresh", the first bug has been fixed. However, the second bug related
  to laptop devices is still there.
+ 
+ UPDATE at 2022/01/26: The first bug is still there. It seems that the
+ bug just occasionally disappeared when I tried it yesterday, but
+ actually it is still there since today I enter the bleaking-cursor-
+ black-screen situation again.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: NH5x_7xDCx_DDx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

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

Title:
  Blackscreen after suspending and closing LID

Status in linux package in Ubuntu:
  New

Bug description:
  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:

  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).

  These bugs really trouble me. It will be very helpful if you fix it.

  UPDATE at 2022/01/25: After I upgraded the "core" package using "snap
  refresh", the first bug has been fixed. However, the second bug
  related to laptop devices is still there.

  UPDATE at 2022/01/26: The first bug is still there. It seems that the
  bug just occasionally disappeared when I tried it yesterday, but
  actually it is still there since today I enter the bleaking-cursor-
  black-screen situation again.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinu

[Kernel-packages] [Bug 1956467] Re: powerlight stays on after shutdown

[Christian]

version 5.13.0-27-generic - will not boot cleanly, just get a flashing
screen

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

Title:
  powerlight stays on after shutdown

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43,
  5.11.0.44 power-button light fails to switch off, after shutdown.

  shutdown can be triggered from command line or via desktop menu,
  result is the same. After rebooting from 5.11.0.40 normal
  functionality is restored.

  systemd appears to complete shutdown looking at the logs (see
  attached)

  Switching to suspend mode (sleep) functions as expected (power light blinks) 
and stays permanently on after wake-up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christian   1896 F pulseaudio
   /dev/snd/controlC0:  christian   1896 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-05-06 (609 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81MT
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-40-generic N/A
   linux-backports-modules-5.11.0-40-generic  N/A
   linux-firmware 1.187.24
  Tags:  focal
  Uname: Linux 5.11.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/09/2019
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8ZCN23WW(V2.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  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 V145-15AST
  dmi.ec.firmware.release: 2.23
  dmi.modalias: 
dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST:
  dmi.product.family: V145-15AST
  dmi.product.name: 81MT
  dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST
  dmi.product.version: Lenovo V145-15AST
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1956670] Re: Extend support for runtime power management for AMD's Yellow Carp

[Alex Hung]

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
   Extend support for runtime power management for AMD's Yellow Carp

Status in HWE Next:
  Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

Some OEM designs may populate the secured USB port without runtime
  power management supported.

  [Fix]

Adds two IDs for XHCI controllers and enable runtime PM as default.

This is from kernel 5.16-rc6.

  [Test]

This is requested by AMD.

  [Where problems could occur]

Low risk. This patch adds two additional hardware IDs and has no
  impacts on other systems.

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


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

[Kernel-packages] [Bug 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems

[Alex Hung]

** Changed in: hwe-next
   Status: New => Fix Committed

** Changed in: hwe-next
   Status: Fix Committed => In Progress

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

Title:
   Fix for rare (~1%) s0ix failures o AMD systems

Status in HWE Next:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Committed

Bug description:
  [Impact]

A rare (~1%) failure has been reported in the community for a period
  of time on Renoir platforms with s0ix. This failure was also
  corroborated once by a Cezanne user.

  [Fix]

In the s0ix entry need retain gfx in the gfxoff state, so skipping
  setting gfx cgpg in the S0ix suspend-resume process.

The fix was cherry-picked from 5.16-rc8.

  [Test]

This is requested by AMD.

  [Where problems could occur]

Low risk. This only affects AMD systems that support s0ix.

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


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

[Kernel-packages] [Bug 1959102] [NEW] Kernel fails to boot in ScalingStack

[Juerg Haefliger]

Public bug reported:

[ Impact ]

The raspi kernel fails to boot in ScalingStack which is our OpenStack
cluster for running ADT/autopkgtest tests.

** Affects: linux-raspi (Ubuntu)
 Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
 Status: New

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

** Affects: linux-raspi-5.4 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
 Status: New

** Affects: linux-raspi (Ubuntu Focal)
 Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
 Status: New

** Affects: linux-raspi (Ubuntu Impish)
 Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
 Status: New

** Affects: linux-raspi (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Juerg Haefliger (juergh)
 Status: New

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

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

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

** Summary changed:

- Fails to boot in ScalingStack
+ raspi kernel fails to boot in ScalingStack

** Summary changed:

- raspi kernel fails to boot in ScalingStack
+ Kernel fails to boot in ScalingStack

** Changed in: linux-raspi (Ubuntu Jammy)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: linux-raspi (Ubuntu Impish)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: linux-raspi (Ubuntu Focal)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

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

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

** No longer affects: linux-raspi (Ubuntu Bionic)

** No longer affects: linux-raspi-5.4 (Ubuntu Focal)

** No longer affects: linux-raspi-5.4 (Ubuntu Impish)

** No longer affects: linux-raspi-5.4 (Ubuntu Jammy)

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

** Changed in: linux-raspi-5.4 (Ubuntu Bionic)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

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

Title:
  Kernel fails to boot in ScalingStack

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi-5.4 package in Ubuntu:
  Invalid
Status in linux-raspi-5.4 source package in Bionic:
  New
Status in linux-raspi source package in Focal:
  New
Status in linux-raspi source package in Impish:
  New
Status in linux-raspi source package in Jammy:
  New

Bug description:
  [ Impact ]

  The raspi kernel fails to boot in ScalingStack which is our OpenStack
  cluster for running ADT/autopkgtest tests.

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


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

[Kernel-packages] [Bug 1921355] Re: cgroups related kernel panics

[Artem Kustikov]

Greetings!
No luck with 5.4.0-80.90, still getting the same bug as before even on kernel 
version 5.4.0-86. Still no clue on how to reproduce it – hypervisor nodes just 
randomly crash. I have attached dmesg of the most recent encounter, but it 
seems identical to previous ones.

Here is fresh crash dump –
https://drive.google.com/file/d/1skA238DVtxpY8t8ANdzX1gBC8muChxto/view?usp=sharing


** Attachment added: "crash-260122.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1921355/+attachment/5557608/+files/crash-260122.log

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

Title:
  cgroups related kernel panics

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  Recently (throughout the last 6 months) we've upgraded our hypervisor
  compute hosts from ubuntu bionic kernel 4.15.* to ubuntu bionic hwe
  kernel 5.4.

  This month we noticed that several nodes failed due to bugs in cgroups.
  Trace was different almost every time, but it all revolves around cgroups - 
either null pointer failures, or panic caught by BUG_ON() macro. Looked like 
some cgroup didn't exist anymore but somebody tried to access it, thus causing 
kernel panic.
  Please find the logs attached.

  3 of 4 cases happened after a VM shutdown. We tried to spawn lots of VMs, 
load them, shut them down, but didn't manage to reproduce the behavior.
  Actually, every case is sort of different - patch kernel versions (5.4.0-42 
to 5.4.0-66), uptime vary (from 1 day to ~half a year). There are also lots of 
hosts with several months of uptime, no issue with them. Also, on 4.15 we've 
never seen this behavior, at all.
  That's quite disturbing, as I don't want dozens of VMs crash (due to host 
outage) at random times for some vague reason...
  I didn't manage to find any related bugs on the bug tracker, thus creating 
this one.

  I wonder if anybody in the community came across something like that.
  Could somebody give an advice how to debug further, or where else to report / 
look for a similar the case?

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


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

[Kernel-packages] [Bug 1959109] [NEW] Audio not detected

[Shekhar Suman]

Public bug reported:

Audio is not working .

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-17-generic 5.15.0-17.17
ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
Uname: Linux 5.15.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  shekhar 921 F pipewire-media-
 /dev/snd/seq:shekhar 920 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 26 19:29:55 2022
InstallationDate: Installed on 2022-01-06 (20 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:5830 Realtek Semiconductor Corp. USB Camera
 Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 002: ID 1c4f:007f SiGma Micro USB Keyboard
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: AVITA NE14A2
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=c7c2a843-8c85-4110-9083-7bcad959f880 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-17-generic N/A
 linux-backports-modules-5.15.0-17-generic  N/A
 linux-firmware 1.204
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-01-25 (0 days ago)
dmi.bios.date: 06/25/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: BSWBHK-N6814G6-AVI-V07
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: GCG514WW80
dmi.board.vendor: AVITA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: To be filled by O.E.M.
dmi.ec.firmware.release: 1.6
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBSWBHK-N6814G6-AVI-V07:bd06/25/2021:br5.13:efr1.6:svnAVITA:pnNE14A2:pvrTobefilledbyO.E.M.:rvnAVITA:rnGCG514WW80:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct10:cvrTobefilledbyO.E.M.:skuCN6814C45M1IN:
dmi.product.family: CN6814
dmi.product.name: NE14A2
dmi.product.sku: CN6814C45M1IN
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: AVITA

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "Sound option in setting"
   
https://bugs.launchpad.net/bugs/1959109/+attachment/5557610/+files/Screenshot%20from%202022-01-26%2019-33-36.png

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

Title:
  Audio not detected

Status in linux package in Ubuntu:
  New

Bug description:
  Audio is not working .

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shekhar 921 F pipewire-media-
   /dev/snd/seq:shekhar 920 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 26 19:29:55 2022
  InstallationDate: Installed on 2022-01-06 (20 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5830 Realtek Semiconductor Corp. USB Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 1c4f:007f SiGma Micro USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: AVITA NE14A2
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic 
root=UUID=c7c2a843-8c85-4110-9083-7bcad959f880 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-01-25 (0 days ago)
  dmi.bios.date: 06/25/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BSWBHK-N6814G6-AVI-V07
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GCG514WW80
  dmi.board.vendor: AVITA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBSWBHK-N6814G6-AVI-V07:bd06/25/2021:br5.13:efr1.6:svnAVITA:pnNE14A2:pvrTobefilledbyO.E.M.:rvnAVITA:rnGCG514WW80:rvrTobefille

[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

[Ilya Leoshkevich]

We pushed this fix into s390/for-next
(https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=for-
next&id=f3b7e73b2c6619884351a3a0a7468642f852b8a2).

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

Title:
  jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >=
  11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  New
Status in gcc-11 source package in Jammy:
  Fix Released
Status in zfs-linux source package in Jammy:
  New

Bug description:
  [Impact]

  Installing zfs-dkms seems to trigger a soft lockup issue as soon as
  zfs.ko is loaded. When the soft lockup happens the system isn't
  reachable anymore via ssh and on the console we can see some exlicit
  rcu stall warnings.

  This seems to happen only when zfs is compile with gcc >=
  11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show
  the problem and zfs is working just fine.

  [Test case]

  On s390x install the latest 5.15 Jammy kernel and run:
  apt install zfs-dkms

  [Fix]

  Temporary workaround is to build zfs with gcc-10 on s390x.

  [Regression potential]

  Building a kernel module with a different compiler is never 100% safe,
  we may experience potential crashes / panics if the ABI is not
  compatible. Moreover, if we build zfs with gcc-10 we are going to lose
  some of the performance benefits provided by gcc-11.

  However these regressions are limited to zfs on s390x and without this
  change zfs is broken anyway on this architecture.

  [Further analysis]

  @IBM

  Issue report to zfs upstream at
  https://github.com/openzfs/zfs/issues/12942

  Reverting
  
https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7
  appears to make everything work, the compiled kernel and zfs.ko are
  loadable/unloadable once again.

  Please bring this issue to the attention of  Ilya Leoshkevich

  Potentially this means we may have missbuilt userspace binaries in the
  archive for s390x.

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


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

[Kernel-packages] [Bug 1959110] [NEW] pl2303 serial adapter no longer recognized

[Fredrik Olofsson]

Public bug reported:

Hi,

After upgrading the Linux kernel to 5.13.0-27 my pl2303 device stopped
working.

Error from dmesg:

jan 26 07:39:24 semalx0017 kernel: Linux version 5.13.0-27-generic 
(buildd@lgw01-amd64-045) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 
(Ubuntu 5.13.0>
...
jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: pl2303 converter detected
jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: unknown device type, 
please report to linux-...@vger.kernel.org

This works fine in the previous 5.11.0-27-generic kernel.

Probably this patch needs backporting 
"USB: serial: pl2303: fix GC type detection"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5721a9e0c9fb8a4bdfe0c8751377cd537d6174

lsusb:

Bus 003 Device 012: ID 067b:23a3 Prolific Technology, Inc. 
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x067b Prolific Technology, Inc.
  idProduct  0x23a3 
  bcdDevice1.05
  iManufacturer   1 
  iProduct2 
  iSerial 3 
  bNumConfigurations  1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity
Date: Wed Jan 26 15:11:11 2022
InstallationDate: Installed on 2022-01-24 (2 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  pl2303 serial adapter no longer recognized

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

Bug description:
  Hi,

  After upgrading the Linux kernel to 5.13.0-27 my pl2303 device stopped
  working.

  Error from dmesg:

  jan 26 07:39:24 semalx0017 kernel: Linux version 5.13.0-27-generic 
(buildd@lgw01-amd64-045) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 
(Ubuntu 5.13.0>
  ...
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: pl2303 converter 
detected
  jan 26 07:39:24 semalx0017 kernel: pl2303 3-5.1.3:1.0: unknown device type, 
please report to linux-...@vger.kernel.org

  This works fine in the previous 5.11.0-27-generic kernel.

  Probably this patch needs backporting 
  "USB: serial: pl2303: fix GC type detection"
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa5721a9e0c9fb8a4bdfe0c8751377cd537d6174

  lsusb:

  Bus 003 Device 012: ID 067b:23a3 Prolific Technology, Inc. 
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x067b Prolific Technology, Inc.
idProduct  0x23a3 
bcdDevice1.05
iManufacturer   1 
iProduct2 
iSerial 3 
bNumConfigurations  1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic:amd64 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Wed Jan 26 15:11:11 2022
  InstallationDate: Installed on 2022-01-24 (2 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1954676] Re: jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >= 11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

[Frank Heimes]

Thanks you, Ilya.
Do you plan to tag this for any of the upstream stable release kernels (like 
5.15)?

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

Title:
  jammy 5.15 kernel soft lockup when zfs.ko is loaded on s390x w/ gcc >=
  11.2.0-10ubuntu1 / gcc-11 PLT regression on s390x

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in gcc-11 package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  New
Status in gcc-11 source package in Jammy:
  Fix Released
Status in zfs-linux source package in Jammy:
  New

Bug description:
  [Impact]

  Installing zfs-dkms seems to trigger a soft lockup issue as soon as
  zfs.ko is loaded. When the soft lockup happens the system isn't
  reachable anymore via ssh and on the console we can see some exlicit
  rcu stall warnings.

  This seems to happen only when zfs is compile with gcc >=
  11.2.0-10ubuntu1. Downgrading gcc to previous versions doesn't show
  the problem and zfs is working just fine.

  [Test case]

  On s390x install the latest 5.15 Jammy kernel and run:
  apt install zfs-dkms

  [Fix]

  Temporary workaround is to build zfs with gcc-10 on s390x.

  [Regression potential]

  Building a kernel module with a different compiler is never 100% safe,
  we may experience potential crashes / panics if the ABI is not
  compatible. Moreover, if we build zfs with gcc-10 we are going to lose
  some of the performance benefits provided by gcc-11.

  However these regressions are limited to zfs on s390x and without this
  change zfs is broken anyway on this architecture.

  [Further analysis]

  @IBM

  Issue report to zfs upstream at
  https://github.com/openzfs/zfs/issues/12942

  Reverting
  
https://gcc.gnu.org/git/?p=gcc.git;a=patch;h=2335aa8771acd06b082d3e15d9f21ae0a802afd7
  appears to make everything work, the compiled kernel and zfs.ko are
  loadable/unloadable once again.

  Please bring this issue to the attention of  Ilya Leoshkevich

  Potentially this means we may have missbuilt userspace binaries in the
  archive for s390x.

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


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

[Kernel-packages] [Bug 1959112] [NEW] Can not boot jammy in our power8 server

[Diego Mascialino]

Public bug reported:

Hi, I am testing image deploy in order to promote them from candidate to
stable in the https://images.maas.io/

During this task I could not deploy and boot our server: IBM 8247-22L
[0]

Please find attached the log I captured with ipmiconsole.


Let me know any other information I could provide.


[0] 
https://www.ibm.com/docs/en/power8/8348-21C?topic=HW4P4/p8hdx/8247_22l_landing.htm

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

** Attachment added: "console log"
   
https://bugs.launchpad.net/bugs/1959112/+attachment/5557637/+files/jammy_ppc_ipmiconsole

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

Title:
  Can not boot jammy in our power8 server

Status in linux package in Ubuntu:
  New

Bug description:
  Hi, I am testing image deploy in order to promote them from candidate
  to stable in the https://images.maas.io/

  During this task I could not deploy and boot our server: IBM 8247-22L
  [0]

  Please find attached the log I captured with ipmiconsole.

  
  Let me know any other information I could provide.

  
  [0] 
https://www.ibm.com/docs/en/power8/8348-21C?topic=HW4P4/p8hdx/8247_22l_landing.htm

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


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

[Kernel-packages] [Bug 1953689] Re: smartpqi: Update 20.04.4 to latest kernel.org patch level

[Stefan Bader]

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

Title:
  smartpqi: Update 20.04.4 to latest kernel.org patch level

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

Bug description:
  SRU Justification:

  Impact:
  Update the smartpqi driver with latest kernel.org patches from git repo:
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  These patches will align the Canonical smartpqi driver with kernel.org

  
  Fix:
  This is targeted at 5.13 for 20.04.4 HWE

  Here is a list of patches that need applied to 20.04.4 to bring the
  smartpqi up to date with kernel.org.

  
  605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055
  80982656b78e scsi: smartpqi: Add 3252-8i PCI id
  d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers
  987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild
  28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs
  4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices
  be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation
  6ce1ddf53252 scsi: smartpqi: Update LUN reset handler
  5d1f03e6f49a scsi: smartpqi: Capture controller reason codes
  9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump
  819225b03dc7 scsi: smartpqi: Update device removal management
  5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array 
member

  These patches should all be upstream as of 5.16.

  Testcase:
  kdump tests.
  fio performance testing to demonstrate no performance regressions.

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


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

[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()

[Stefan Bader]

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

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

Title:
  ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with
  dump_page()

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux-oem-5.13 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Fix Released
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:
  Fix Committed
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Released
Status in linux-oem-5.10 source package in Jammy:
  Invalid
Status in linux-oem-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The memory-hotplug test has been intermittently timing out (or trashing the 
test
  VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now.

  While the offline memory test obey ratio limit, the same test with
  error injection does not and tries to offline all the hotpluggable
  memory, spamming system logs with hundreds of thousands of dump_page()
  entries, slowing system down (to the point the test itself timesout and
  gets terminated) and excessive fs occupation:

  ...
  [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 
mapping:c001fc03e950 index:0xe7b
  [ 9784.393355] def_blk_aops
  [ 9784.393356] flags: 0x382062(referenced|active|workingset|private)
  [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 
c001fc03e950
  [ 9784.393359] raw: 0e7b c6607b18 0003 
c490d000
  [ 9784.393359] page dumped because: migration failure
  [ 9784.393360] page->mem_cgroup:c490d000
  [ 9784.393416] migrating pfn 1f46d failed ret:1
  ...

  $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l
  2405558

  $ ls -la /var/log/kern.log
  -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log

  [Fix]
  * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with 
dump_page(), ratio limit hot-remove error test

  [Test Plan]
  Run the memory-hotplug test, this log spamming issue should not happen again.

  [Where problems could occur]
  If this fix is incorrect we might be unable to catch some other issue.

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


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

[Kernel-packages] [Bug 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce

[Stefan Bader]

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

Title:
  [uacc-0623] hisi_sec2  fail to alloc uacce

Status in kunpeng920:
  Fix Committed
Status in kunpeng920 ubuntu-20.04-hwe series:
  Fix Committed
Status in kunpeng920 ubuntu-21.10 series:
  Fix Committed
Status in kunpeng920 ubuntu-22.04 series:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification
  =

  [Impact]
  * Users with HiSilicon Security Engine (SEC) version 2 controller fail to 
allocate Uacce.

  [Fix]
  * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - 
modify the uacce mode check

  [Test Plan]
  * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with 
HiSilicon Security Engine (SEC) version 2 controller
  * Boot the system
  * 'dmesg | grep "fail to alloc uacce"' and you will see complains from 
hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc 
uacce (-22)

  [Where problems could occur]
  * The regression can be considered as low, since it is HiSilicon crypto 
system specific

  == Original Bug Description ==

  [Bug Description]

  ubuntu 20.04.2 boot system and fail to alloc uacce (-22)

  [Steps to Reproduce]
  1) boot ubuntu 20.04.2 system
  2) dmesg | grep fail

  [Actual Results]
  [   27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12
  [   27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID
  [   27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45
  [   27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22)

  [Expected Results]
  no fail
  [Reproducibility]
  100%

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

  [Resolution]
  this following patches will solve this bug.

  commit f8408d2b79b834f79b6c578817e84f74a85d2190
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:42 2021 +0800

  crypto: hisilicon - add ZIP device using mode parameter

  Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1.
  '0' means ZIP is only registered to kernel crypto, and '1' means it's
  registered to both kernel crypto and UACCE.

  Signed-off-by: Kai Ye 
  Reviewed-by: Zhou Wang 
  Reviewed-by: Zaibo Xu 
  Signed-off-by: Herbert Xu 

  commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:43 2021 +0800

  crypto: hisilicon/hpre - register HPRE device to uacce

  commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc
  Author: Kai Ye 
  Date:   Tue Jan 5 14:16:44 2021 +0800

  crypto: hisilicon/sec - register SEC device to uacce

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


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

[Kernel-packages] [Bug 1958155] Re: Pod traffic not taking advantage of interfaces with multiple tx queues

[Stefan Bader]

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

Title:
  Pod traffic not taking advantage of interfaces with multiple tx queues

Status in linux package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-hwe-5.11 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-hwe-5.11 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in linux-hwe-5.11 source package in Impish:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/

  Performance is impacted when multiple TX queues are enabled.

  [Fix]
  commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx 
queue hint in veth_xmit")

  This patch is already scheduled for release in these stable kernel
  versions:

  linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record 
rx queue hint in veth_xmit
  linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record 
rx queue hint in veth_xmit
  linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record 
rx queue hint in veth_xmit
  linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record 
rx queue hint in veth_xmit

  [Test Plan]

  Upstream tested

  [Where things could go wrong]

  Transmit performance could be impacted in other ways.

  [Other Info]

  SF: #00326544

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


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

[Kernel-packages] [Bug 1958151] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922

[Stefan Bader]

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

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

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

Title:
  [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add basic support of MT7922, and add ID of AMD RZ616/RZ608.
  Enable 160Mhz channel.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  It may break MT7921 wifi support which shares mt7921e driver.
  Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.

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


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

[Kernel-packages] [Bug 1956461] Re: Creative HD720p webcam doesn't work

[Pawel J.]

This affects me as well, kernel 5.4.0-96 atm.
When I plug in the camera and run dmesg | egrep 'usb|uvc|video|cam|Cam':

[23785.501888] usb 1-4: new high-speed USB device number 12 using xhci_hcd
[23785.745623] usb 1-4: New USB device found, idVendor=041e, idProduct=4095, 
bcdDevice=20.20
[23785.745625] usb 1-4: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[23785.745627] usb 1-4: Product: Live! Cam Sync HD VF0770
[23785.745628] usb 1-4: Manufacturer: Creative Technology Ltd.
[23785.745629] usb 1-4: SerialNumber: 2015012638825
[23785.754877] usb 1-4: 3:0: cannot get min/max values for control 2 (id 3)
[23786.361794] usb 1-4: 3:0: cannot get min/max values for control 2 (id 3)
[23786.362795] usb 1-4: 3:0: cannot get min/max values for control 2 (id 3)
[23786.364790] usb 1-4: 3:0: cannot get min/max values for control 2 (id 3)
[23786.365776] usb 1-4: 3:0: cannot get min/max values for control 2 (id 3)

The camera mic works fine but the camera is not detected as a video
device. The integrated latpop camera works fine.

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

Title:
  Creative HD720p webcam doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen 
by the system. There is no  /dev/vl4/ folder
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piotr  3094 F pulseaudio
   /dev/snd/controlC0:  piotr  3094 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.2
  InstallationDate: Installed on 2020-06-07 (578 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-92-generic N/A
   linux-backports-modules-5.4.0-92-generic  N/A
   linux-firmware1.187.24
  RfKill:
   
  Tags:  uma
  Uname: Linux 5.4.0-92-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 10/27/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Stefan Bader]

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

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

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

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  The ESW_ALLOWED marco was later converted into a helper routine in
  commit b16f2bb6.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

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

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1871015] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with H (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL])

[Ian May]

Found also on 2022.01.03/impish/linux-aws: 5.13.0-1012.13

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

Title:
  test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
  with H (Check VM connectivity through VXLAN (underlay in the default
  VRF) [FAIL])

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

Bug description:
  Issue found with GCP 5.3.0-1017.18~18.04.1

   # selftests: net: test_vxlan_under_vrf.sh
   # Checking HV connectivity [ OK ]
   # Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]
   not ok 25 selftests: net: test_vxlan_under_vrf.sh # exit=1

  
  The failure is different from bug 1837348

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


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

[Kernel-packages] [Bug 1935082] Re: [MIR] egl-wayland

[Alberto Milone]

** Also affects: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-495 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: nvidia-graphics-drivers-495 (Ubuntu)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-495 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: nvidia-graphics-drivers-495 (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [MIR] egl-wayland

Status in egl-wayland package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-495 package in Ubuntu:
  In Progress

Bug description:
  MIR Template:

  [Availability]
  Already available in universe now for impish with the minimum required 1.1.7 
version.

  [Rationale]
  Past nvidia driver releases are in restricted.  If the 470 release follows 
the pattern and ultimately ends up in restricted it will suffer a performance 
penalty when used with Xwayland unless egl-wayland version 1.1.7 (or later) 
from outside the main+restricted repository set (universe) has also been 
installed.

  [Security]
  No search results found for CVS, oss-security.
  No Ubuntu CVE results for egl-wayland or variations thereof.
  The egl-wayland package installs a library with mode 0644 for use by the 
nvidia egl driver.
  While this does not seem to present security issues of its own, the library 
will be loaded and used by the nvidia egl driver and may therefore share any 
security concerns applicable to that driver.

  [Quality assurance]
  Once installed, use of egl-wayland by the nvidia egl driver is automatic, the 
single configuration file 
(/usr/share/egl/egl_external_platform.d/10_nvidia_wayland.json) installed by 
the egl-wayland package makes that happen.
  There is no configuration or other end user interaction.  The package itself 
does not have any UI of its own.
  The current universe version of the package comes from the upstream Debian 
package.
  There is a debian/watch file present.

  [Dependencies]
  The required dependencies (libc6, libwayland-client, libwayland-server) are 
already present in main.

  [Standards compliance]
  Appears to comply with both the FHS and Debian Policy standards.  The 
"/usr/share/egl/egl_external_platform.d/" directory is not specifically 
mentioned by those standards, but that directory location is required by the 
installed "10_nvidia_wayland.json" file in order for the nvidia egl driver to 
load the library that the egl-wayland package installs.

  [Maintenance]
  The egl-wayland package is a small package with few dependencies that is 
already being maintained upstream by Debian.
  Since it only installs a library and a config file and does not have any of 
its own UI, there are no i18n or l10n support issues.

  [Background information]

  The libnvidia-gl 470 drivers have been officially released as of
  2021-07-19 and have since become available in multiverse.

  The libnvidia-gl 470 release notes discuss performance under xwayland
  here:

  


  Quoting from those release notes:

  > The following are necessary to enable accelerated rendering on
  > Xwayland with the NVIDIA driver:
  >
  > * DRM KMS must be enabled. See Chapter 35, Direct Rendering Manager
  >   Kernel Modesetting (DRM KMS) for details.
  >
  > * The installed copy of Xwayland should be a build from the master
  >   branch of https://gitlab.freedesktop.org/xorg/xserver at least
  >   as recent as commit c468d34c. Note that if this requirement is
  >   not satisfied, the NVIDIA GPU can still be used for rendering,
  >   however it will fall back to a suboptimal path for presentation
  >   resulting in degraded performance.
  >
  > * libxcb version 1.13 or later must be present.
  >
  > * egl-wayland version 1.1.7 or later must be present (if installed
  >   separately from the the NVIDIA driver).
  >
  > * If using the GNOME desktop environment, kms-modifiers must be
  >   enabled through gsettings. This can be done with the following
  >   command:
  > gsettings set org.gnome.mutter experimental-features [\"kms-modifiers\"]

  The first item is easily accomplished with something like this:

  /etc/modprobe.d/nvidia-drm.conf:
  options nvidia-drm modeset=1

  For the second item, commit 763f4fb278 in the freedesktop.org xserver
  repository cherry-pic

[Kernel-packages] [Bug 1959119] [NEW] Fix sprintf usage that may lead to buffer overflow

[Jitendra Lanka]

Public bug reported:

SRU Justification:

[Impact]
Fix references to sprintf that have a possibility for buffer overflow

[Fix]
Replace sprintf with snprintf containing a defined boundary of PAGE_SIZE for 
sysfs store/show functions and max array size defined otherwise.

[Test Case]
Existing testcases should work as is as no functional change has been 
introduced by this patch.

[Regression Potential]
Regression potential can be considered minimal since the patch does not change 
any function of the driver other than limiting the upper bound of sprintf where 
the usual lengths parsed are < PAGE_SIZE and requests > PAGE_SIZE are limited.

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

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

Title:
  Fix sprintf usage that may lead to buffer overflow

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  SRU Justification:

  [Impact]
  Fix references to sprintf that have a possibility for buffer overflow

  [Fix]
  Replace sprintf with snprintf containing a defined boundary of PAGE_SIZE for 
sysfs store/show functions and max array size defined otherwise.

  [Test Case]
  Existing testcases should work as is as no functional change has been 
introduced by this patch.

  [Regression Potential]
  Regression potential can be considered minimal since the patch does not 
change any function of the driver other than limiting the upper bound of 
sprintf where the usual lengths parsed are < PAGE_SIZE and requests > PAGE_SIZE 
are limited.

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


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

[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part

[Frank Heimes]

Collin just confirmed that my results show the proper verification (and
that the 'cpnc to 0' can happen on top). Hence adjusting the tags
accordingly ...

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

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

Title:
  [UBUNTU 20.04] KVM hardware diagnose data improvements for guest
  kernel - kernel part

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  Fix Committed

Bug description:
  SRU Justification:
  ==

  [Impact]

  * Hardware diagnose data (diag 318) of KVM guest kernel cannot be
  handled.

  * A fix is needed to enhance problem determination of guest kernel
  under KVM using DIAG 0x318 instruction execution.

  * The s390x diagnose 318 instruction sets the control program name
  code (CPNC) and control program version code (CPVC) to provide useful
  information regarding the OS during debugging.

  * The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.

  [Fix]

  * In general the following 4 commits are needed:

  * 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug 
statement for diag 318 CPNC data"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch

  * 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove 
diag318 reset code"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch

  * 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose 
0x318 sync and reset"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch

  * a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag 
318: refactor struct"
    
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch

  * For jammy, hirsute and impish only the first commit is needed, the
  others are already in.

  * For focal all 4 commits are needed, but since they do not apply
  cleanly on focal, the attached backports need to be used instead.

  [Test Case]

  * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.

  * And setup an Ubuntu KVM virtual machine on top.

  * It can then be observed if the CPNC (diag318 data) has been
  successfully set by looking at the s390dbf messages for the KVM guest.

  * The CPNC will always be 4 (denotes Linux environment).

  * Another way to test this is by running the sync_regs_test under
  tools/testing/selftests/kvm/s390x/sync_regs_test.   Just running the
  kernel self test suite can trigger this.

  [Where problems could occur]

  * The approach here is to provide additional debug and diagnose
  information on top.

  * Hence even if the diag318 changes are broken, the existing
  functionality shouldn't be harmed.

  * The changes themselves are relatively discernible and mostly
  introduce new structures.

  * However, with the functional changes broken code could be introduced
  (e.g. due to erroneous pointer arithmetic for example) that does not
  compile or causes crashes. But this is what the test builds are for
  (https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).

  * On top the diag318 diagnose data might not properly provided - maybe
  empty or wrong. Again that is what the test builds and the
  verification later is targeted at.

  * Since diag318 is s390x specific, all the modifications touch s390x
  code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
  arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
  diag.h). At least no other other architecture will be affected.

  * Well, there is one tiny bit of a common code change, but it's just a
  new define statement in include/uapi/linux/kvm.h ('#define
  KVM_CAP_S390_DIAG318 186').

  [Other]

  * Request was to add the patches to focal / 20.04, but to avoid
  potential regressions on upgrades, the patches need to be added to
  jammy, impish and hirsute, too.

  * As mentioned above, Jammy, Hirsute and Impish includes almost
  everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
  for diag 318 CPNC data".

  * Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
  invasive for Jammy, Hirsute and Impish, also because commit
  3fd8417f2c72 can be cleanly cherr

[Kernel-packages] [Bug 1958151] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922

[Shengyao Xue]

I tested the 5.14.0.1021.18 in focal-proposed, the Wifi and BT works
only with 3 additional firmwares:

WIFI_RAM_CODE_MT7922_1.bin
WIFI_MT7922_patch_mcu_1_1_hdr.bin
BT_RAM_CODE_MT7922_1_1_hdr.bin

which are not available in latest linux-firmware(1.187.25) in Focal. We
need those firmwares lands to linux-firmware package.

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

Title:
  [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  No driver is loaded for MT7922, and fw is missing too.

  [Fix]
  Add basic support of MT7922, and add ID of AMD RZ616/RZ608.
  Enable 160Mhz channel.

  [Test]
  Verified on RZ616, it works fine, suspend OK.
  iperf test result looks fine.
  Bluetooth works fine.

  [Where problems could occur]
  It may break MT7921 wifi support which shares mt7921e driver.
  Almost the code is specific for MT7922, checking security fw is based on 
MT7922 fw.

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


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

[Kernel-packages] [Bug 1959121] [NEW] nvidia graphics driver stopped working, screen resolution has been degraded

[Eric Perry]

Public bug reported:

Description:Ubuntu 20.04.3 LTS
Release:20.04
N: Unable to locate package pkgname
I expected my computer to recognize my graphics card.  It has been working fine 
until this morning.  When I turned on my computer it took longer than normal to 
load and now it does not identify my graphics card and the resolution is 
degraded.

apt.log
log time: 2021-06-17 15:56:46.835636
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) linux-modules-nvidia-460-5.8.0-53-generic:amd64 < 5.8.0-53.60>
Broken linux-modules-nvidia-460-5.8.0-53-generic:amd64 Depends on nvidia-kernel>
  Considering nvidia-kernel-common-460:amd64 13 as a solution to linux-modules->
  Removing linux-modules-nvidia-460-5.8.0-53-generic:amd64 rather than change n>
Done
Log time: 2021-06-17 16:16:26.065339
  MarkPurge libsratom-0-0:amd64 < 0.6.4-1 @ii gK > FU=1
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii gK Ib >
Broken liblilv-0-0:amd64 Depends on libsratom-0-0:amd64 < 0.6.4-1 @ii pgP > (>=>
  Considering libsratom-0-0:amd64 1 as a solution to liblilv-0-0:amd64 2
  Removing liblilv-0-0:amd64 rather than change libsratom-0-0:amd64
  MarkDelete liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii gK Ib > FU=0
Investigating (0) libavfilter7:amd64 < 7:4.2.4-1ubuntu0.1 @ii gK Ib >
Broken libavfilter7:amd64 Depends on liblilv-0-0:amd64 < 0.24.6-1ubuntu0.1 @ii >
  Considering liblilv-0-0:amd64 2 as a solution to libavfilter7:amd64 1
[ File 'apt.log' is unwritable ]

Start-Date: 2021-06-17  16:14:39
Requested-By: office (1000)
Install: linux-signatures-nvidia-5.8.0-55-generic:amd64 (5.8.0-55.62~20.04.1, a>
Upgrade: gnome-control-center-data:amd64 (1:3.36.5-0ubuntu1, 1:3.36.5-0ubuntu2)>
Remove: linux-modules-nvidia-460-5.8.0-53-generic:amd64 (5.8.0-53.60~20.04.1)
End-Date: 2021-06-17  16:16:24

Start-Date: 2021-06-17  16:16:39
Requested-By: office (1000)
Purge: libavfilter7:amd64 (7:4.2.4-1ubuntu0.1), libopencore-amrnb0:amd64 (0.1.5>
End-Date: 2021-06-17  16:16:41

Log started: 2021-06-17  16:14:39
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(R>
Preparing to unpack .../0-nvidia-driver-460_460.80-0ubuntu0.20.04.2_amd64.deb .>
Unpacking nvidia-driver-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubuntu0.>
Preparing to unpack .../1-libnvidia-gl-460_460.80-0ubuntu0.20.04.2_amd64.deb ...
De-configuring libnvidia-gl-460:i386 (460.73.01-0ubuntu0.20.04.1) ...
Unpacking libnvidia-gl-460:amd64 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubu>
Preparing to unpack .../2-libnvidia-gl-460_460.80-0ubuntu0.20.04.2_i386.deb ...
Unpacking libnvidia-gl-460:i386 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubun>
Preparing to unpack .../3-nvidia-dkms-460_460.80-0ubuntu0.20.04.2_amd64.deb ...
Removing all DKMS Modules
Done.
Unpacking nvidia-dkms-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0ubuntu0.20>
Preparing to unpack .../4-nvidia-kernel-source-460_460.80-0ubuntu0.20.04.2_amd6>
Unpacking nvidia-kernel-source-460 (460.80-0ubuntu0.20.04.2) over (460.73.01-0u>
Preparing to unpack .../5-linux-modules-nvidia-460-generic-hwe-20.04_5.8.0-55.6>
Unpacking linux-modules-nvidia-460-generic-hwe-20.04 (5.8.0-55.62~20.04.1) over>
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(R>
Removing linux-modules-nvidia-460-5.8.0-53-generic (5.8.0-53.60~20.04.1) ...
 [ File 'apt-term.log' is unwritable ]

7zXZ^@^@^D�ִF^B^@!^A^V^@^@^@t/���]^@)^YJ'�H�^Uh�TZۄUّ���|y�^R^Q��ya��^S��^Y�>
ʆ��G�$^LE�^H��C;}�l^9Ꭱ^V^@���f^S)^Y^H
e17ӕ�ozұ^R�
�^P^N�}^W^^���§��Ԙ#�^W�1�UvĬ^WӺY�e�"^B��fS��"^R^F�^[�(,(^C�H��Վ8J5^Zhi�E+^O>
j!#�b�"?�ˉ��:���F�v�SN^]��V|*S7�^AC^Y^]f��^\})�wɼ���^Fh^h^[Ɓ�>-^ZSj2#^^^Qif>
Yҙ~<�LΎ9oĥ�~K,iyӼ��6mս�ω��$�\k`���^_
½�%�j��ԅ+
�^HA�$G�^B�B��H�zuG�h^D{Ձ!ű�-�^R)5��Qi�O^_Jk�^?˳��T�T�b8^^w��[�^N�X^DX�>
�^K:jw�n^Aئ� ^PWܖ�4��/@^P^C�n� �#�Ҵ��_��^L;i�Ku�~��^F���ʽ��^[�^]��bq�z�>
�^F^P���B�Ԯ^D^Y�^U" �^T�^E;�F���Z�`�^C��^\䒁+�,=�F^^�W���K�mNx-`藬A�,�Y�1��A�?ՠ>
GJ���H�]A<�^R]�c�o�^]Ţ#�^^�^Y���N帹��/^S�^_-��{:^^B�Y7^SCJT���9|c��@==�>
Ӡ1o�j}�r��^X^W!F^@�^E$㲐#ja(^Z��\��^]�5�D^Z��6Xx��}eL��^PۗC�^S�#^Z�q�ٝR�{�^K�>
r��^Zڤ�^Smf��^[w^Wl[^E�>�H���v^F�^(��gSz)�̥���;�^@,TQ�8��ސ��r�^D@/��2��'��[fK�U�>
�^^v�J[���^W�:�9���^KX�9��_^Zq�ZPu}Efi�DoZ���^[�G&^Y'^XU�^_~^B�*}y4V�^S^E  >
baY�q^@�@^N�^Y���j��fB���U�^E^H�'qx��S)��+c՟��V��l��*�
WsVA�I7^C�^���AZ�5^S_���^Wj�,B�Į�(�^S^Cd4��InVB>^^ר�'^U^W^^�M�$�a�^L��O>
�E���9^PE��Q�^W���^Yn�e��g^V�oc��?U^D�L��M��7�kx�-^\^X/���^\J�k^O��>
^O�2D�ln���ڇV'��G���_�+��`�u��s�dAn�U�^[���4^]�E~L^D�a��^E�ء^�B^Z^F�JO�U�,�>
��r�/z�Ybn��⺌I^B^N��� w�M^R^B�:��/�D���C�c�^]W�1�7��T^\��^Z���ȥ.��q۝p�H= ��^B^>
^Z._dH��^xu�/��:-��-*5`0p�ȧ%^P���^Hh��;�.��^V47^K�3wQ�^Vً�9�v��^O^T^U�I�>
  [ File 'eipp.l

[Kernel-packages] [Bug 1957753] Re: net/mlx5e: EPERM on vlan 0 programming

[Stefan Bader]

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

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

Title:
  net/mlx5e: EPERM on vlan 0 programming

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [Impact]
  There is an issue with hypervisor host side mlx5 driver operation on
  Bluefield devices in kernels <=5.16

  From patch description:
  When using libvirt to passthrough VF to VM it will always set the VF vlan
  to 0 even if user didn’t request it, this will cause libvirt to fail to
  boot in case the PF isn't eswitch owner.

  Example of such case is the DPU host PF which isn't eswitch manager, so
  any attempt to passthrough VF of it using libvirt will fail.

  [Fix]
  * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't
   eswitch manager

  This patch can be cherry-picked into Impish and newer kernels, but it
  requires some backport work on F/H due to they're missing commit
  b55b3538 that split the legacy code out.

  The ESW_ALLOWED marco was later converted into a helper routine in
  commit b16f2bb6.

  [Test]
  Test kernels can be found here:
  F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/
  H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/
  I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/
  J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/

  Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test
  passed with positive feedback.

  [Where problems could occur]
  If this patch is erroneous, it might cause issue to this mlx5 driver
  with certain operations (setting vid 0). And other programs such as
  libvirt that depends on this return value might be affected as well.

  [Original Bug Description]
  There is an issue with hypervisor host side mlx5 driver operation on 
Bluefield devices in kernels <=5.16 that was recently fixed in master with a 
one-liner:

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

  It would be good to have this fix in Focal+ kernels.

  This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux-
  bluefield since it's used at the DPU side whereas the issue in
  question affects the hypervisor side.

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


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

[Kernel-packages] [Bug 1951924] Re: linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure

[Marcelo Cerri]

Kernel version 4.15.0-1130.143 is booting fine on M416s_v2 instances.

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

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

Title:
  linux-azure 4.15 fails to boot on Standard_M416s_v2 in Azure

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

Bug description:
  To reproduce:

   * start a bionic VM in azure:
  az vm create --name bionic --resource-group test-bionic --image 
"Canonical:UbuntuServer:18_04-lts-gen2:latest" --size Standard_M416s_v2 
--admin-username ubuntu --ssh-key-value SSH_KEY_PATH

   * "downgrade" the kernel to 4.15 and delete the 5.4 kernel

   * reboot (the machine should fail to boot)

  The serial console logs can be found on the azure portal (boot
  diagnostic needs to be enabled for the VM first).

  Logs: https://pastebin.ubuntu.com/p/mhKMdMJCtX/

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


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

[Kernel-packages] [Bug 1958774] Re: Blackscreen after suspending and closing LID

[Thomas]

it is just written what to do on the webpage and this informations are not for 
OS developers.
Without your help nobody can do something about it and the bug report can be 
closed.

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

Title:
  Blackscreen after suspending and closing LID

Status in linux package in Ubuntu:
  New

Bug description:
  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:

  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).

  These bugs really trouble me. It will be very helpful if you fix it.

  UPDATE at 2022/01/25: After I upgraded the "core" package using "snap
  refresh", the first bug has been fixed. However, the second bug
  related to laptop devices is still there.

  UPDATE at 2022/01/26: The first bug is still there. It seems that the
  bug just occasionally disappeared when I tried it yesterday, but
  actually it is still there since today I enter the bleaking-cursor-
  black-screen situation again.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: NH5x_7xDCx_DDx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

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


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

[Kernel-packages] [Bug 1958774] Re: Blackscreen after suspending and closing LID

[Thomas]

I will help you a little:

1. edit your /etc/default/grub
a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this:

GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

2. run 'sudo update-grub' to reflect the changes
3. reboot your pc
4. put your pc into STR, eg with 'echo mem | sudo tee /sys/power/state'

5. when your PC is suspended, wake it up and report back what you find.

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

Title:
  Blackscreen after suspending and closing LID

Status in linux package in Ubuntu:
  New

Bug description:
  These bugs occur after I upgrade the linux-generic package from 5.11
  (not sure) to 5.13 today. After that, I have met two similar bugs:

  1. Every time I suspend my computer and re-activate it, I will get a black 
screen with a bleaking cursor.
  2. Every time I close my laptop's LID and reopen it, I will get an empty 
black screen (without anything).

  These bugs really trouble me. It will be very helpful if you fix it.

  UPDATE at 2022/01/25: After I upgraded the "core" package using "snap
  refresh", the first bug has been fixed. However, the second bug
  related to laptop devices is still there.

  UPDATE at 2022/01/26: The first bug is still there. It seems that the
  bug just occasionally disappeared when I tried it yesterday, but
  actually it is still there since today I enter the bleaking-cursor-
  black-screen situation again.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-generic 5.13.0.27.37
  ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nomanous   5648 F pulseaudio
   /dev/snd/controlC1:  nomanous   5648 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 23 23:02:24 2022
  InstallationDate: Installed on 2021-06-29 (208 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HASEE Computer NH5x_7xDCx_DDx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=018344b7-14eb-4d4a-b012-cf2577a7bc6a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-27-generic N/A
   linux-backports-modules-5.13.0-27-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-15 (100 days ago)
  dmi.bios.date: 04/18/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03THZX
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NH5x_7xDCx_DDx
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.1
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03THZX:bd04/18/2020:br7.3:efr7.1:svnHASEEComputer:pnNH5x_7xDCx_DDx:pvrNotApplicable:rvnNotebook:rnNH5x_7xDCx_DDx:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: NH5x_7xDCx_DDx
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: HASEE Computer

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


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

[Kernel-packages] [Bug 1958968] Re: failed to resume PC

[Thomas]

In short:

1. edit your /etc/default/grub
a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this:

GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

2. run 'sudo update-grub' to reflect the changes
3. reboot your pc
4. put your pc into STR, eg with 'echo mem | sudo tee /sys/power/state'

5. when your PC is suspended, wake it up and report back what you find.

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

Title:
  failed to resume PC

Status in linux package in Ubuntu:
  New

Bug description:
  Sometimes I cannot resume my PC after suspend. Pressing keys or moving
  the mouse doesn't help: the login screen doesn't appear. In some cases
  pressing Ctrl+Alt+F1 helps, but not always. This time I had to make a
  hard reset. Check 25 January 10:43 in the logs.

  Ubuntu 20.04.3 LTS
  5.4.0-96-generic x86_64
  GNOME 3.36.8 X11

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


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

[Kernel-packages] [Bug 1957808] Re: Kernel soft lockup after resume

[Thomas]

Have a look at this webpage..

https://01.org/blogs/rzhang/2015/best-practice-debug-linux-
suspend/hibernate-issues

In short:

1. edit your /etc/default/grub
a. make a COPY of the line GRUB_CMDLINE_LINUX_DEFAULT and modify like this:

GRUB_CMDLINE_LINUX_DEFAULT="initcall_debug no_console_suspend ignore_loglevel"
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

2. run 'sudo update-grub' to reflect the changes
3. reboot your pc
4. put your pc into STR, eg with 'echo mem | sudo tee /sys/power/state'

5. when your PC is suspended, wake it up and report back what you find.

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

Title:
  Kernel soft lockup after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the kernel hangs after resuming from suspend.
  It might be a problem when suspending, while the DELL thunderbolt dock is 
connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-25-generic 5.13.0-25.26
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  minni  5443 F pulseaudio
   /dev/snd/pcmC0D0c:   minni  5443 F...m pulseaudio
   /dev/snd/pcmC0D0p:   minni  5443 F...m pulseaudio
   /dev/snd/timer:  minni  5443 f pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 13 15:53:19 2022
  InstallationDate: Installed on 2020-12-19 (389 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. XPS 15 9500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash acpi_osi=Linux vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-25-generic N/A
   linux-backports-modules-5.13.0-25-generic  N/A
   linux-firmware 1.201.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-17 (88 days ago)
  dmi.bios.date: 05/26/2021
  dmi.bios.release: 1.8
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 05XYW7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd05/26/2021:br1.8:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:sku097D:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9500
  dmi.product.sku: 097D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1817513] Re: 4.19 causes disk read errors on CT256M550SSD3 SSD

[shemgp]

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

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

Title:
  4.19 causes disk read errors on CT256M550SSD3 SSD

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Upgraded to disco, and I noticed that my SSD had read errors while
  looking at dmesg.  When I rebooted, it won't boot any more due to disk
  errors.

  But when I tried booting with a 4.18 kernel, it allows me to boot
  successfully without any errors.  Also, I booted an 18.10 USB disk to
  check which SSD was failing and when I used GNOME disks to check the
  filesystem, and there were no errors.

  I'll try download disco-current to see if the errors can be shown and
  be submitted here since I can't boot using 4.19 with my SSD.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-13-generic 4.19.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shemgp13115 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Feb 25 15:12:17 2019
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cc5ba738-82e8-404a-9bcc-f1dfed94fce0
  InstallationDate: Installed on 2015-09-28 (1245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-02-16 (9 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETB1WW (2.71 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETB1WW(2.71):bd06/19/2018:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.sku: LENOVO_MT_3436
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works

[ooshlablu]

I've been having the suspend issue for the past week or so with the 5.13 
kernels on an Atari VCS, which has a AMD Ryzen Embedded R1606G with Radeon Vega 
Gfx. Current kernel installed is 5.13.0-27-generic. I've also noticed that 
anything that tries to use Vulkan as a display driver segfaults.
Upon bootup, dmesg has some bad looking errors in it:
[2.772683] kfd kfd: amdgpu: error getting iommu info. is the iommu enabled?
[2.772687] kfd kfd: amdgpu: Error initializing iommuv2
[2.772899] kfd kfd: amdgpu: device 1002:15d8 NOT added due to errors

FWIW, I have this setup cloned to an Intel laptop, and everything
appears fine there. The 5.13 series even enabled my wireless card on
that laptop, since that wireless card wasn't supported until 5.12 or
later.

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

Title:
  amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
  works

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  This does not occur with linux-image-5.13.0-22-generic, but does with 
linux-image-5.13.0-23-generic.
  On startup, I get about a 60 second hang, with the following in the kernel 
dmesg:
  Jan  4 15:26:36 inspiron-3505 kernel: [   34.160572] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:26:56 inspiron-3505 kernel: [   54.189055] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  Jan  4 15:27:16 inspiron-3505 kernel: [   74.329264] amdgpu :04:00.0: 
amdgp : failed to write reg 28b4 wait reg 28c6
  Jan  4 15:27:36 inspiron-3505 kernel: [   94.337904] amdgpu :04:00.0: 
amdgp : failed to write reg 1a6f4 wait reg 1a706
  I have the following GPU:
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Picass
  o (rev c2) (prog-if 00 [VGA controller])
  04:00.0 0300: 1002:15d8 (rev c2)
  (This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)

  I get a similar hang if I start firefox (when it's probing OpenGL
  contexts), and even with glxgears and glxinfo. Seems like anything
  that'd kick on a OpenGL context does it.  I had a freeze as well when
  I tried running firefox and glxgears both.  Along with odd BUG:
  messages logged (I have some in the attached log.)

  I was running with "iommu=pt", but did try with this removed, still
  got the errors (I think amdgpu driver uses the IOMMU even when it's
  set to IOMMU=pt though.).  See the attached log for some very odd
  "[Hardware Error]" messages that were logged on one test run.  I think
  this was when I tried to run firestorm (second life viewer) -- that
  had a large pause then opened to a black window.

  Per Google, I see there was a bug like this that turned up in kernel
  5.14.15 but fixed in 5.14.17.  See
  https://gitlab.freedesktop.org/drm/amd/-/issues/1770

  Thanks!
  --Henry

  Fix:
  upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is 
disabled in Picasso.")

  Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
  from an upstream patch set. multiple confirmations the problem is
  resolved with the kernel in -proposed.

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


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

[Kernel-packages] [Bug 1957786] Re: Enable CONFIG_NO_HZ_FULL in Jammy realtime kernel

[Krzysztof Kozlowski]

** Summary changed:

- Enable CONFIG_NO_HZ_FULL in relatime kernel
+ Enable CONFIG_NO_HZ_FULL in Jammy realtime kernel

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

Title:
  Enable CONFIG_NO_HZ_FULL in Jammy realtime kernel

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  nohz_full should be enabled by default as it improves certain
  workloads. No actual data was given, just strong opinion nohz_full is
  needed. CONFIG_NO_HZ_FULL is also in Intel’s BSP for Yocto RT.

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


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

[Kernel-packages] [Bug 1957788] Re: Enable CONFIG_RT_GROUP_SCHED in realatime kernel

[Krzysztof Kozlowski]

** Summary changed:

- Enable CONFIG_RT_GROUP_SCHED in relatime kernel
+ Enable CONFIG_RT_GROUP_SCHED in realatime kernel

** Summary changed:

- Enable CONFIG_RT_GROUP_SCHED in realatime kernel
+ Enable CONFIG_RT_GROUP_SCHED in Jammy realtime kernel

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

Title:
  Enable CONFIG_RT_GROUP_SCHED in Jammy realtime kernel

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  CONFIG_RT_GROUP_SCHED makes sense in realtime workloads, especially
  ones involving multiple realtime tasks. It is also enabled in Intel’s
  BSP for Yocto RT.

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


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

[Kernel-packages] [Bug 1959130] [NEW] Add rtla to tools Jammy realtime kernel

[Krzysztof Kozlowski]

Public bug reported:

Include new rtla (Real-Time Linux Analysis tool) in Jammy realtime
kernel.

The rtla is a meta-tool that includes a set of commands that aims to analyze 
the real-time properties of Linux. But instead of testing Linux as a black box, 
rtla leverages kernel tracing capabilities to provide precise information about 
the properties and root causes of
unexpected results.

Including the tool gives more way to investigate realtime capabilities
and issues of the kernel.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Krzysztof Kozlowski (krzk)
 Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Krzysztof Kozlowski (krzk)

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

Title:
  Add rtla to tools Jammy realtime kernel

Status in linux package in Ubuntu:
  New

Bug description:
  Include new rtla (Real-Time Linux Analysis tool) in Jammy realtime
  kernel.

  The rtla is a meta-tool that includes a set of commands that aims to analyze 
the real-time properties of Linux. But instead of testing Linux as a black box, 
rtla leverages kernel tracing capabilities to provide precise information about 
the properties and root causes of
  unexpected results.

  Including the tool gives more way to investigate realtime capabilities
  and issues of the kernel.

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


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

[Kernel-packages] [Bug 1956793] Re: linux-azure-cvm: Avoid leaking guest memory when communicating with the host

[Ubuntu Kernel Bot]

This bug is awaiting verification that the linux-azure-
cvm/5.4.0-1068.71+cvm1 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal' to 'verification-
done-focal'. If the problem still exists, change the tag 'verification-
needed-focal' to 'verification-failed-focal'.

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

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


** Tags added: verification-needed-focal

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

Title:
  linux-azure-cvm: Avoid leaking guest memory when communicating with
  the host

Status in linux-azure-cvm package in Ubuntu:
  New
Status in linux-azure-cvm source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Initialize memory of request offers message to be sent to the host so
  padding or uninitialized fields do not leak guest memory contents.

  Patch:

  
https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv-
  next

  [Test case]

  Testing the information leakage to the host is not viable, but since
  the patch the vmbus layer that affects all the hyper-v drivers, a boot
  test on Hyper-V and on Azure should be enough to validate the patch,
  considering how small the change is.

  [Potential regression]

  The change is very restricted, but on an eventual regression it might
  affect any of the hyperv guest drivers.

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


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

[Kernel-packages] [Bug 1959130] Re: Add rtla to tools Jammy realtime kernel

[Krzysztof Kozlowski]

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

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

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

Title:
  Add rtla to tools Jammy realtime kernel

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Include new rtla (Real-Time Linux Analysis tool) in Jammy realtime
  kernel.

  The rtla is a meta-tool that includes a set of commands that aims to analyze 
the real-time properties of Linux. But instead of testing Linux as a black box, 
rtla leverages kernel tracing capabilities to provide precise information about 
the properties and root causes of
  unexpected results.

  Including the tool gives more way to investigate realtime capabilities
  and issues of the kernel.

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


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

[Kernel-packages] [Bug 1959134] [NEW] Impish update: upstream stable patchset 2022-01-26

[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 2022-01-26

Ported from the following upstream stable releases:
v5.10.90, v5.15.13

   from git://git.kernel.org/

Input: i8042 - add deferred probe support
Input: i8042 - enable deferred probe quirk for ASUS UM325UA
tomoyo: Check exceeded quota early in tomoyo_domain_quota_is_ok().
tomoyo: use hwight16() in tomoyo_domain_quota_is_ok()
parisc: Clear stale IIR value on instruction access rights trap
platform/x86: apple-gmux: use resource_size() with res
memblock: fix memblock_phys_alloc() section mismatch error
recordmcount.pl: fix typo in s390 mcount regex
selinux: initialize proto variable in selinux_ip_postroute_compat()
scsi: lpfc: Terminate string in lpfc_debugfs_nvmeio_trc_write()
net/mlx5: DR, Fix NULL vs IS_ERR checking in dr_domain_init_resources
net/mlx5e: Wrap the tx reporter dump callback to extract the sq
net/mlx5e: Fix interoperability between XSK and ICOSQ recovery flow
net/mlx5e: Fix ICOSQ recovery flow for XSK
udp: using datalen to cap ipv6 udp max gso segments
selftests: Calculate udpgso segment count without header adjustment
sctp: use call_rcu to free endpoint
net/smc: fix using of uninitialized completions
net: usb: pegasus: Do not drop long Ethernet frames
net: ag71xx: Fix a potential double free in error handling paths
net: lantiq_xrx200: fix statistics of received bytes
NFC: st21nfca: Fix memory leak in device probe and remove
net/smc: don't send CDC/LLC message if link not ready
net/smc: fix kernel panic caused by race of smc_sock
igc: Fix TX timestamp support for non-MSI-X platforms
ionic: Initialize the 'lif->dbid_inuse' bitmap
net/mlx5e: Fix wrong features assignment in case of error
selftests/net: udpgso_bench_tx: fix dst ip argument
net/ncsi: check for error return from call to nla_put_u32
fsl/fman: Fix missing put_device() call in fman_port_probe
i2c: validate user data in compat ioctl
nfc: uapi: use kernel size_t to fix user-space builds
uapi: fix linux/nfc.h userspace compilation errors
drm/amdgpu: When the VCN(1.0) block is suspended, powergating is explicitly 
enabled
drm/amdgpu: add support for IP discovery gc_info table v2
xhci: Fresco FL1100 controller should not have BROKEN_MSI quirk set.
usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.
usb: mtu3: add memory barrier before set GPD's HWO
usb: mtu3: fix list_head check warning
usb: mtu3: set interval of FS intr and isoc endpoint
binder: fix async_free_space accounting for empty parcels
scsi: vmw_pvscsi: Set residual data length conditionally
Input: appletouch - initialize work before device registration
Input: spaceball - fix parsing of movement data packets
net: fix use-after-free in tw_timer_handler
perf script: Fix CPU filtering of a script's switch events
net/sched: Extend qdisc control block with tc control block
platform/mellanox: mlxbf-pmc: Fix an IS_ERR() vs NULL bug in 
mlxbf_pmc_map_counters
net/mlx5: Fix SF health recovery flow
net/mlx5: Fix tc max supported prio for nic mode
selftests: net: Fix a typo in udpgro_fwd.sh
selftests: net: using ping6 for IPv6 in udpgro_fwd.sh
fs/mount_setattr: always cleanup mount_kattr
UBUNTU: upstream stable to v5.10.90, v5.15.13

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

** Affects: linux (Ubuntu Impish)
 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 Impish)
   Importance: Undecided
   Status: New

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

[Kernel-packages] [Bug 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy

[Launchpad Bug Tracker]

This bug was fixed in the package backport-iwlwifi-dkms - 9340-0ubuntu5

---
backport-iwlwifi-dkms (9340-0ubuntu5) jammy; urgency=medium

  [ Andrea Righi ]
  * Fix build error with Linux 5.15 (LP: #1951580)

  [ Dimitri John Ledkov ]
  * Bump obsoleted by to Linux 5.16

 -- Andrea Righi   Fri, 19 Nov 2021 11:59:00
+

** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy)
   Status: New => Fix Released

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

Title:
  backport-iwlwifi-dkms fails to build with kernel 5.15 jammy

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in backport-iwlwifi-dkms source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  Incomplete

Bug description:
  [Impact]

  backport-iwlwifi-dkms fails to build on the latest jammy kernel 5.15:

  CC [M]  
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o
  In file included from 
/tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3,
   from ./arch/x86/include/asm/bug.h:84,
   from ./include/linux/bug.h:5,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4,
   from ./include/linux/skbuff.h:13,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3,
   from ./include/linux/if_ether.h:19,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3,
   from ./include/linux/etherdevice.h:20,
   from 
/tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3,
   from 
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6:
  /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In 
function ‘iwl_mei_free_shared_mem’:
  
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17:
 error: implicit declaration of function ‘mei_cldev_dma_unmap’ 
[-Werror=implicit-function-declaration]
    243 | WARN_ON(mei_cldev_dma_unmap(cldev));
    | ^~~

  [Test case]

  sudo apt install backport-iwlwifi-dkms

  [Fix]

  The driver assumes that kernels > 5.13 provide
  mei_cldev_dma_map/unmap() when CONFIG_WLAN_VENDOR_INTEL_MEI is
  defined.

  However these functions and the config option are not available at all
  in recent kernels.

  So instead of relying on the specific kernel version simply rely on
  the availability of CONFIG_WLAN_VENDOR_INTEL_MEI to determine if the
  kernel has the required functions defined, or if the driver needs to
  provide a custom implementation of these functions.

  [Regression potential]

  We may see build errors in newer kernel if
  CONFIG_WLAN_VENDOR_INTEL_MEI is merged upstream and these functions
  are actually provided by recent kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1951580/+subscriptions


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

[Kernel-packages] [Bug 1958283] Re: linux-firmware missing renoir_ta

[simonschmeisser]

Not being able to use my T14s builtin screen is pretty annoying, can the
SRU already be tested somewhere? Do you need further information?

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

Title:
  linux-firmware missing renoir_ta

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

Bug description:
  [ Impact ]

  After today's update to the 5.13 kernel, my laptop's screen stopped
  working, showing random patterns instead.  The laptop is ThinkPad X13
  with an AMD GPU.

  In dmesg there was a message about amdgpu/renoir_ta.bin missing.
  Following some StackOverflow advice, I downloaded and installed linux-
  firmware_1.201_all.deb from the 21.10 repo, which has
  amdgpu/renoir_ta.bin and rebooted, which fixed my issue.

  Proposed Solution

  Add amdgpu/renoir_ta.bin to the current version of the linux-firmware
  package for 20.04 LTS.

  Additional Data

    $ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  Codename: focal

    $ uname -a
  Linux ainar-ThinkPad-X13-Gen-1 5.13.0-25-generic #26~20.04.1-Ubuntu SMP Fri 
Jan 7 16:27:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  [ Test Case ]

  See above. Kernel log shows firmware load failures for amdgpu firmware
  in combination with the OEM 5.13 kernel.

  [ Fix ]

  Kernel fixes for new amdgpu firmware have landed in linux-oem-5.13 so
  it's now safe to update amdgpu firmware on focal to match impish.

  [ Where Problems Could Occur ]

  Display issues with amdgpu.

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


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

[Kernel-packages] [Bug 1959041] Re: STR (suspend-to-RAM) freezes at suspend

[Thomas]

** Tags added: regression

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

Title:
  STR (suspend-to-RAM) freezes at suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  I want to report, that Ubuntu's shipped kernel has a problem with STR on my 
Laptop.
  When I run `echo mem | sudo tee /sys/power/state` the systems try to go in 
standby mode. Everything shuts down, but the power led flashes fast (how it 
does every time between going into standby and before the standby is reached). 
It never reaches the state that the led starts slowly "breathing in and out". 
So the final step is missing and the machine can only be forced to poweroff and 
on again.

  I already tested with the mainline kernel from
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.15/

  And there standby works flawless.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1409 F pipewire-media-
    thomas 1410 F pulseaudio
   /dev/snd/seq:thomas 1408 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Jan 25 20:06:44 2022
  InstallationDate: Installed on 2022-01-21 (4 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  MachineType: LENOVO 20ELS03U00
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-17-generic 
root=UUID=28ca1143-6369-4859-83f1-307e09a49858 ro initcall_debug 
no_console_suspend ignore_loglevel
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-17-generic N/A
   linux-backports-modules-5.15.0-17-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2019
  dmi.bios.release: 1.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R05ET81W (1.59)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ELS03U00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrR05ET81W(1.59):bd05/14/2019:br1.59:efr1.25:svnLENOVO:pn20ELS03U00:pvrThinkPadYoga460:rvnLENOVO:rn20ELS03U00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20EL_BU_Think_FM_ThinkPadYoga460:
  dmi.product.family: ThinkPad Yoga 460
  dmi.product.name: 20ELS03U00
  dmi.product.sku: LENOVO_MT_20EL_BU_Think_FM_ThinkPad Yoga 460
  dmi.product.version: ThinkPad Yoga 460
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1941660] Re: Fix incorrect keyboard backlight behaviours

[Alex Hung]

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

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

** Changed in: hwe-next
   Status: New => Invalid

** Changed in: linux (Ubuntu)
 Assignee: Alex Hung (alexhung) => (unassigned)

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

Title:
  Fix incorrect keyboard backlight behaviours

Status in HWE Next:
  Invalid
Status in linux 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.13 source package in Focal:
  Invalid

Bug description:
  [Impact]
   The keyboard backlight was turning on when entering suspend and turning
   off when exiting (the opposite of how it should be).

  [Fix]
   Swaps the on / off commands. The fix commit is in 5.14-rc7.

  [Test]
   This is requested by AMD.

  [Where problems could occur]
   This fixes the incorrect LED on/off behaviours in 5dbf50997578, and
   the risk is very slow.

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


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

[Kernel-packages] [Bug 1957813] Re: nvidia-driver-460 haven't transit to 470 but linux-modules-nvidia-460-* transited

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  nvidia-driver-460 haven't transit to 470 but linux-modules-
  nvidia-460-* transited

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Triaged
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Won't Fix

Bug description:
  # apt show linux-modules-nvidia-460-oem-20.04d
  Package: linux-modules-nvidia-460-oem-20.04d
  Version: 5.14.0-1018.19
  ...
  Depends: linux-modules-nvidia-470-oem-20.04d

  ---

  # apt show nvidia-driver-460
  Package: nvidia-driver-460
  Version: 460.91.03-0ubuntu0.20.04.1
  Priority: optional
  Section: restricted/libs
  Source: nvidia-graphics-drivers-460
  Origin: Ubuntu
  Maintainer: Ubuntu Core Developers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 1509 kB
  Depends: libnvidia-gl-460 (= 460.91.03-0ubuntu0.20.04.1), nvidia-dkms-460 (<= 
460.91.03-1), nvidia-dkms-460 (>= 460.91.03), nvidia-kernel-common-460 (<= 
460.91.03-1), nvidia-kernel-common-460 (>= 460.91.03), nvidia-kernel-source-460 
(= 460.91.03-0ubuntu0.20.04.1), libnvidia-compute-460 (= 
460.91.03-0ubuntu0.20.04.1), libnvidia-extra-460 (= 
460.91.03-0ubuntu0.20.04.1), nvidia-compute-utils-460 (= 
460.91.03-0ubuntu0.20.04.1), libnvidia-decode-460 (= 
460.91.03-0ubuntu0.20.04.1), libnvidia-encode-460 (= 
460.91.03-0ubuntu0.20.04.1), nvidia-utils-460 (= 460.91.03-0ubuntu0.20.04.1), 
xserver-xorg-video-nvidia-460 (= 460.91.03-0ubuntu0.20.04.1), 
libnvidia-cfg1-460 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-ifr1-460 (= 
460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460 (= 460.91.03-0ubuntu0.20.04.1)
  Recommends: nvidia-settings, nvidia-prime (>= 0.8), 
libnvidia-compute-460:i386 (= 460.91.03-0ubuntu0.20.04.1), 
libnvidia-decode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), 
libnvidia-encode-460:i386 (= 460.91.03-0ubuntu0.20.04.1), 
libnvidia-ifr1-460:i386 (= 460.91.03-0ubuntu0.20.04.1), libnvidia-fbc1-460:i386 
(= 460.91.03-0ubuntu0.20.04.1), libnvidia-gl-460:i386 (= 
460.91.03-0ubuntu0.20.04.1)

  ---

  The nvidia-driver-460 (460.91.03-0ubuntu0.20.04.1) is now failed to be
  compiled on 5.14.0-1018-oem (at least) because `struct
  task_struct->state` changed to ->__state[1].

  [1]
  Author: Peter Zijlstra 
  Date:   Fri Jun 11 10:28:17 2021 +0200

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


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

[Kernel-packages] [Bug 1948898] Re: Bluetooth HCI reset fail during airplane mode switch stress tests

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Bluetooth HCI reset fail during airplane mode switch stress tests

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Won't Fix
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:
  Bug 1928838 fixed possible kernel panic when doing rfkill block on
  Intel Bluetooth controller. The fix was also upstreamed in v5.14-rc1
  as commit 0ea9fd001a14e ("Bluetooth: Shutdown controller after
  workqueues are flushed or cancelled") and was backported to v5.10.51,
  v5.12.18, and v5.13.3. However, as indicated in
  https://lore.kernel.org/linux-bluetooth/8735ryk0o7@baylibre.com/ ,
  it caused a regression to mtkbtsdio and was then fixed in upstream
  commit 0ea53674d07f (" Bluetooth: Move shutdown callback before
  flushing tx and rx queue") since v5.15-rc1 and has been backported to
  v5.14.3. Current statuses:

  * v5.10.x:
* 0ea9fd001a14e: backported(v5.10.51), reverted(v5.10.57)
* 0ea53674d07f: backported(v5.10.65), reverted(v5.10.66)
  * v5.11.x: N/A
  * v5.12.x:
* 0ea9fd001a14e: backported(v5.12.18)
  * v5.13.x:
* 0ea9fd001a14e: backported(v5.13.3), reverted(v5.13.9)
* 0ea53674d07f: backported(v5.13.17), reverted(v5.13.18)
  * v5.14.x:
* 0ea9fd001a14e: committed(v5.14-rc1)
* 0ea53674d07f: backported(v5.14.3)
  * v5.15.x:
* 0ea53674d07f: committed(v5.15-rc1)

  As a result, this affects 5.10/11/13 kernels.

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


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

[Kernel-packages] [Bug 1956984] Re: hirsute:linux 5.11.0-45.49 fails to boot

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  hirsute:linux 5.11.0-45.49 fails to boot

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  [ Impact ]

  hirsute:linux 5.11.0-45.49 is not booting on several
  systems/instances.

  The boot failure is caused at least in most of the cases by systemd
  services failing to start. On a amd64 test VM the journald service
  times out when it's configured to use any storage type (which is the
  default config).

  [ Fix ]
  I was able to boot a VM with the following commit reverted:

  327aa2137d989f278ece7e8e31c218dfb3416c35 - mm: filemap: check if THP
  has hwpoisoned subpage for PMD page fault

  [ Additional Info ]
  On an affected VM, after a bit more than 1 hour after booting I get the 
following soft lockup which helped identify a suspicious commit:

  [12164.210808] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! 
[systemd-journal:478]
  [12164.211616] Modules linked in: binfmt_misc nls_iso8859_1 dm_multipath 
scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper 
drm_ttm_helper input_leds ttm joydev drm_kms_helper cec rc_core serio_raw 
fb_sys_fops syscopyarea sysfillrect sysimgblt mac_hid parport_pc parport 
qemu_fw_cfg sch_fq_codel msr drm ip_tables x_tables autofs4 btrfs 
blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover 
i2c_piix4 pata_acpi floppy
  [12164.211649] CPU: 1 PID: 478 Comm: systemd-journal Tainted: G L 
   5.11.0-45-generic #49-Ubuntu
  [12164.211651] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.14.0-2 04/01/2014
  [12164.211653] RIP: 0010:xas_load+0x33/0x80
  [12164.211659] Code: 48 89 c2 83 e2 03 48 83 fa 02 75 08 48 3d 00 10 00 00 77 
02 5d c3 0f b6 48 fe 48 8d 70 fe 38 4f 10 77 f1 48 8b 57 08 48 d3 ea <83> e2 3f 
89 d0 48 83 c0 04 48 8b 44 c6 08 48 89 77 18 48 89 c1 83
  [12164.211661] RSP: :b17440c7fb68 EFLAGS: 0246
  [12164.211662] RAX: 92d2823ea6ca RBX: 92d282e52ee8 RCX: 

  [12164.211664] RDX: 003b RSI: 92d2823ea6c8 RDI: 
b17440c7fb78
  [12164.211665] RBP: b17440c7fb68 R08: 92d2823eb47a R09: 
92d28674b750
  [12164.211666] R10:  R11:  R12: 
003b
  [12164.211667] R13: 003b R14: 92d282e52ee8 R15: 
61c8864680b583eb
  [12164.211669] FS:  7fdf28760900() GS:92d2fdc8() 
knlGS:
  [12164.211670] CS:  0010 DS:  ES:  CR0: 80050033
  [12164.211672] CR2: 7fdf28522018 CR3: 02d34000 CR4: 
06e0
  [12164.211675] Call Trace:
  [12164.211678]  find_get_entry+0x5a/0x160
  [12164.211682]  find_lock_entry+0x2d/0x120
  [12164.211685]  shmem_getpage_gfp+0xe8/0x8c0
  [12164.211687]  ? asm_sysvec_apic_timer_interrupt+0x12/0x20
  [12164.211691]  shmem_fault+0x7b/0x220
  [12164.211693]  ? file_update_time+0x62/0x140
  [12164.211696]  __do_fault+0x3c/0xe0
  [12164.211699]  do_shared_fault+0x19/0xb0
  [12164.211701]  do_fault+0x1cd/0x1f0
  [12164.211704]  handle_pte_fault+0x1e5/0x260
  [12164.211706]  __handle_mm_fault+0x59a/0x7c0
  [12164.211709]  ? timerqueue_add+0x68/0xa0
  [12164.211711]  handle_mm_fault+0xd7/0x2b0
  [12164.211714]  do_user_addr_fault+0x1a0/0x450
  [12164.211717]  exc_page_fault+0x69/0x150
  [12164.211720]  ? asm_exc_page_fault+0x8/0x30
  [12164.211722]  asm_exc_page_fault+0x1e/0x30
  [12164.211723] RIP: 0033:0x7fdf28fbece1
  [12164.211727] Code: 0f 11 5f 30 0f 11 64 17 f0 0f 11 6c 17 e0 0f 11 74 17 d0 
0f 11 7c 17 c0 c3 0f 10 06 0f 10 4e 10 0f 10 54 16 f0 0f 10 5c 16 e0 <0f> 11 07 
0f 11 4f 10 0f 11 54 17 f0 0f 11 5c 17 e0 c3 48 39 f7 0f
  [12164.211728] RSP: 002b:7fffd18bffd8 EFLAGS: 00010287
  [12164.211730] RAX: 7fdf28522018 RBX: 7fffd18c0520 RCX: 
7fdf28521fd8
  [12164.211731] RDX: 002b RSI: 7fffd18c0520 RDI: 
7fdf28522018
  [12164.211732] RBP: 5643719d90c0 R08: 0001 R09: 
0003afd8
  [12164.211733] R10: 0002 R11: 7fffd1947090 R12: 
002b
  [12164.211734] R13: 23e0650ff2b8eb94 R14:  R15: 
7fffd18c

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


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

[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-raspi (Ubuntu Hirsute)
   Status: Fix Committed => Won't Fix

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

Title:
  Boot time from snap in 20/stable increases boot time on 3.5 seconds

Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-raspi-5.4 package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi-5.4 source package in Bionic:
  Fix Committed
Status in linux-raspi2 source package in Bionic:
  Fix Committed
Status in linux-raspi source package in Focal:
  Fix Committed
Status in linux-raspi source package in Hirsute:
  Won't Fix
Status in linux-raspi source package in Impish:
  Fix Committed

Bug description:
  [ Impact ]

  I am seeing what looks as a regression in pi-kernel snap for UC20:
  there are around 3.5 additional seconds spent in boot time. In the
  image from cdimage (2021-06-30), I see:

  [1.856540] random: crng init done
  [1.871798] loop: module loaded

  (see https://paste.ubuntu.com/p/CkfWXY5Vgf/)
  while if I build an image from latest snaps in the 20/stable channel, I get:

  [1.855481] random: crng init done
  [5.349491] loop: module loaded

  (see https://paste.ubuntu.com/p/CNt42gdDcZ/)
  The pi-kernel snap revision is 353.

  [ Test Case ]

  $ sudo dmesg | grep -B1 -A1 'loop: module'
  [0.791122] cacheinfo: Unable to detect cache hierarchy for CPU 0
  [4.903386] loop: module loaded
  [4.906092] spi-bcm2835 fe204000.spi: could not get clk: -517

  [ Fix ]

  Set CONFIG_BLK_DEV_LOOP_MIN_COUNT to the default value (8).

  [ Where Problems Could Occur ]

  Loop devices need to be created on-demand if more than 8 are required.
  If that fails, user space will fail.

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


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

[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  NVIDIA CVE-2021-{1093|1094|1094}

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-460 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  In Progress
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-460 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-460 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Groovy:
  Fix Released
Status in fabric-manager-460 source package in Groovy:
  Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Won't Fix
Status in linux-restricted-modules source package in Groovy:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Won't Fix
Status in nvidia-settings source package in Groovy:
  Fix Released
Status in fabric-manager-450 source package in Hirsute:
  Fix Released
Status in fabric-manager-460 source package in Hirsute:
  Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-restricted-modules source package in Hirsute:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Won't Fix
Status in nvidia-settings source package in Hirsute:
  Fix Released

Bug description:
  As per the subject, the update includes fixes for the following CVEs:

  CVE-2021-1093
  CVE-2021-1094
  CVE-2021-1095

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

[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  ath10k: "add target IRAM recovery feature support" breaks QCA9984
  Firmware load capability

Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Triaged
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
  in v5.11 fails firmware loading without IRAM recovery feature. However,
  the latest firmware from
  https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
  doesn't support IRAM, it follows new official ath10k firmwares may no
  longer be loadable for kernel newer than v5.11.

  [Fix]

  A fix is proposed to
  http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
  turns the lack/failure of IRAM recovery support a warning instead.

  [Test Case]

  With this fix, kernel gives errors about the IRAM supportness, but
  proceeds to remaining procedures as before.

ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12

  [Where problems could occur]

  So the IRAM recovery feature may or may not be supported in the
  officially released firmware, and people meet problems when using
  non-IRAM supported firmware may still have a fallback to use older, but
  IRAM recovery supported ones.

  == original bug report ==

  Hello, I use Ubuntu 20.04.2 LTS.

  The kernel was recently updated to 5.11

  5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
  x86_64 x86_64 x86_64 GNU/Linux

  Since then the ath10k_core driver for my QCA9984 card is broken and
  only loads ~3 firmware versions from the 3.9.0.2 branch

  https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2

  The firmware versions 70 / 86 / 91 are functional (but these firmware
  versions are already 2 years old)

  Responsible for this is the defective patch "ath10k: add target IRAM
  recovery feature support"

  https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11&id=9af7c32ceca85da27867dd863697d2aafc80a3f8

  If I understand the patch correctly then the driver tries to load
  firmware with the feature "iram recovery" into the memory of the host
  (for recvovery purposes).

  If this fails, the firmware is discarded and the network controller
  remains unusable.

  Of course, this is not a desirable behavior for optional firmware
  features.

  dmesg:

  [3.074952] ath: loading out-of-tree module taints kernel.
  [3.090522] ath: module verification failed: signature and/or required key 
missing - tainting kernel
  [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 
0 reset_mode 0
  [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
 crc32 5f41acd7
  [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 
0x0100 chip_id 0x sub 168c:cafe
  [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 
features 
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
 crc32 5f41acd7
  [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 
85498734
  [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 
85498734
  [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: 
-12
  [7.103260] ath10k_pci :03:00.0: could not init core (-12)
  [7.103267] ath10k_pci :03:00.0: could not probe fw (-12)
  [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: 
-12
  [7.163247] ath10k_pci :04:00.0: could not init core (-1

[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-restricted-modules (Ubuntu Hirsute)
   Status: Triaged => Won't Fix

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

Title:
  NVIDIA CVE-2021-{1093|1094|1094}

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-460 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  In Progress
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-460 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-460 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Groovy:
  Fix Released
Status in fabric-manager-460 source package in Groovy:
  Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Won't Fix
Status in linux-restricted-modules source package in Groovy:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Won't Fix
Status in nvidia-settings source package in Groovy:
  Fix Released
Status in fabric-manager-450 source package in Hirsute:
  Fix Released
Status in fabric-manager-460 source package in Hirsute:
  Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-restricted-modules source package in Hirsute:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Won't Fix
Status in nvidia-settings source package in Hirsute:
  Fix Released

Bug description:
  As per the subject, the update includes fixes for the following CVEs:

  CVE-2021-1093
  CVE-2021-1094
  CVE-2021-1095

To manage notifications about this bug go to:
https://bugs.launchpad.net/ub

[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: nvidia-graphics-drivers-465 (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  NVIDIA CVE-2021-{1093|1094|1094}

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-460 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Triaged
Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  In Progress
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-460 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Triaged
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
  In Progress
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-460 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Triaged
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
  In Progress
Status in nvidia-settings source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Groovy:
  Fix Released
Status in fabric-manager-460 source package in Groovy:
  Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
  Fix Released
Status in linux source package in Groovy:
  Won't Fix
Status in linux-restricted-modules source package in Groovy:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Won't Fix
Status in nvidia-settings source package in Groovy:
  Fix Released
Status in fabric-manager-450 source package in Hirsute:
  Fix Released
Status in fabric-manager-460 source package in Hirsute:
  Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-restricted-modules source package in Hirsute:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Won't Fix
Status in nvidia-settings source package in Hirsute:
  Fix Released

Bug description:
  As per the subject, the update includes fixes for the following CVEs:

  CVE-2021-1093
  CVE-2021-1094
  CVE-2021-1095

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

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

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  HWE kernels: NFSv4.1 NULL pointer dereference

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

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

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

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

  [  266.199657] R13: a048621ef228 R14: a048621ef228 R15: 

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

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

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

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

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

[Kernel-packages] [Bug 1958461] Re: Hirsute update: upstream stable patchset 2022-01-19

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2022-01-19

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-01-19

  Ported from the following upstream stable releases:
  v5.10.86, v5.15.9
  v5.10.87, v5.15.10
  v5.10.88, v5.15.11

     from git://git.kernel.org/

  netfilter: selftest: conntrack_vrf.sh: fix file permission
  UBUNTU: upstream stable to v5.10.86, v5.15.9
  nfc: fix segfault in nfc_genl_dump_devices_done
  drm/msm/dsi: set default num_data_lanes
  KVM: arm64: Save PSTATE early on exit
  s390/test_unwind: use raw opcode instead of invalid instruction
  Revert "tty: serial: fsl_lpuart: drop earlycon entry for i.MX8QXP"
  net/mlx4_en: Update reported link modes for 1/10G
  ALSA: hda: Add Intel DG2 PCI ID and HDMI codec vid
  ALSA: hda/hdmi: fix HDA codec entry table order for ADL-P
  parisc/agp: Annotate parisc agp init functions with __init
  i2c: rk3x: Handle a spurious start completion interrupt flag
  net: netlink: af_netlink: Prevent empty skb by adding a check on len.
  drm/amd/display: Fix for the no Audio bug with Tiled Displays
  drm/amd/display: add connector type check for CRC source set
  tracing: Fix a kmemleak false positive in tracing_map
  staging: most: dim2: use device release method
  bpf: Fix integer overflow in argument calculation for bpf_map_area_alloc
  fuse: make sure reclaim doesn't write the inode
  hwmon: (dell-smm) Fix warning on /proc/i8k creation error
  ethtool: do not perform operations on net devices being unregistered
  perf inject: Fix itrace space allowed for new attributes
  perf intel-pt: Fix some PGE (packet generation enable/control flow packets) 
usage
  perf intel-pt: Fix sync state when a PSB (synchronization) packet is found
  perf intel-pt: Fix intel_pt_fup_event() assumptions about setting state type
  perf intel-pt: Fix state setting when receiving overflow (OVF) packet
  perf intel-pt: Fix next 'err' value, walking trace
  perf intel-pt: Fix missing 'instruction' events with 'q' option
  perf intel-pt: Fix error timestamp setting on the decoder error path
  memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER
  memblock: align freed memory map on pageblock boundaries with SPARSEMEM
  memblock: ensure there is no overflow in memblock_overlaps_region()
  arm: extend pfn_valid to take into account freed memory map alignment
  arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM
  hwmon: (corsair-psu) fix plain integer used as NULL pointer
  drm/msm/dp: Avoid unpowered AUX xfers that caused crashes
  UBUNTU: upstream stable to v5.10.87, v5.15.10
  KVM: selftests: Make sure kvm_create_max_vcpus test won't hit RLIMIT_NOFILE
  KVM: downgrade two BUG_ONs to WARN_ON_ONCE
  mac80211: fix regression in SSN handling of addba tx
  mac80211: mark TX-during-stop for TX in in_reconfig
  mac80211: send ADDBA requests using the tid/queue of the aggregation session
  mac80211: validate extended element ID is present
  firmware: arm_scpi: Fix string overflow in SCPI genpd driver
  bpf: Fix signed bounds propagation after mov32
  bpf: Make 32->64 bounds propagation slightly more robust
  bpf, selftests: Add test case trying to taint map value pointer
  virtio_ring: Fix querying of maximum DMA mapping size for virtio device
  vdpa: check that offsets are within bounds
  recordmcount.pl: look for jgnop instruction as well as bcrl on s390
  dm btree remove: fix use after free in rebalance_children()
  audit: improve robustness of the audit queue handling
  arm64: dts: imx8m: correct assigned clocks for FEC
  arm64: dts: imx8mp-evk: Improve the Ethernet PHY description
  arm64: dts: rockchip: remove mmc-hs400-enhanced-strobe from rk3399-khadas-edge
  arm64: dts: rockchip: fix rk3308-roc-cc vcc-sd supply
  arm64: dts: rockchip: fix rk3399-leez-p710 vcc3v3-lan supply
  arm64: dts: rockchip: fix audio-supply for Rock Pi 4
  mac80211: track only QoS data frames for admission control
  tee: amdtee: fix an IS_ERR() vs NULL bug
  ceph: fix duplicate increment of op

[Kernel-packages] [Bug 1957842] Re: Hirsute update: upstream stable patchset 2022-01-13

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2022-01-13

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-01-13

  Ported from the following upstream stable releases:
  v5.10.85, v5.15.8

     from git://git.kernel.org/

  usb: gadget: uvc: fix multiple opens
  HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
  HID: google: add eel USB id
  HID: add hid_is_usb() function to make it simpler for USB detection
  HID: add USB_HID dependancy to hid-prodikeys
  HID: add USB_HID dependancy to hid-chicony
  HID: add USB_HID dependancy on some USB HID drivers
  HID: bigbenff: prevent null pointer dereference
  HID: wacom: fix problems when device is not a valid USB device
  HID: check for valid USB device for many HID drivers
  nft_set_pipapo: Fix bucket load in AVX2 lookup routine for six 8-bit groups
  IB/hfi1: Insure use of smp_processor_id() is preempt disabled
  IB/hfi1: Fix early init panic
  IB/hfi1: Fix leak of rcvhdrtail_dummy_kvaddr
  can: kvaser_usb: get CAN clock frequency from device
  can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct 
stats->{rx,tx}_errors counter
  can: sja1000: fix use after free in ems_pcmcia_add_card()
  x86/sme: Explicitly map new EFI memmap table as encrypted
  drm/amd/amdkfd: adjust dummy functions' placement
  drm/amdkfd: separate kfd_iommu_resume from kfd_resume
  drm/amdgpu: add amdgpu_amdkfd_resume_iommu
  drm/amdgpu: move iommu_resume before ip init/resume
  drm/amdgpu: init iommu after amdkfd device init
  drm/amdkfd: fix boot failure when iommu is disabled in Picasso.
  nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
  selftests: netfilter: add a vrf+conntrack testcase
  vrf: don't run conntrack on vrf with !dflt qdisc
  bpf, x86: Fix "no previous prototype" warning
  bpf: Fix the off-by-two error in range markings
  ice: ignore dropped packets during init
  bonding: make tx_rebalance_counter an atomic
  nfp: Fix memory leak in nfp_cpp_area_cache_add()
  seg6: fix the iif in the IPv6 socket control block
  udp: using datalen to cap max gso segments
  netfilter: conntrack: annotate data-races around ct->timeout
  iavf: restore MSI state on reset
  iavf: Fix reporting when setting descriptor count
  IB/hfi1: Correct guard on eager buffer deallocation
  devlink: fix netns refcount leak in devlink_nl_cmd_reload()
  net/sched: fq_pie: prevent dismantle issue
  KVM: x86: Wait for IPIs to be delivered when handling Hyper-V TLB flush 
hypercall
  mm: bdi: initialize bdi_min_ratio when bdi is unregistered
  ALSA: ctl: Fix copy of updated id with element read/write
  ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
  ALSA: hda/realtek: Fix quirk for TongFang PHxTxX1
  ALSA: pcm: oss: Fix negative period/buffer sizes
  ALSA: pcm: oss: Limit the period size to 16MB
  ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
  scsi: qla2xxx: Format log strings only if needed
  btrfs: clear extent buffer uptodate when we fail to write it
  btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
  md: fix update super 1.0 on rdev size change
  nfsd: fix use-after-free due to delegation race
  nfsd: Fix nsfd startup race (again)
  tracefs: Have new files inherit the ownership of their parent
  mmc: renesas_sdhi: initialize variable properly when tuning
  clk: qcom: regmap-mux: fix parent clock lookup
  drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
  can: pch_can: pch_can_rx_normal: fix use after free
  can: m_can: Disable and ignore ELO interrupt
  libata: add horkage for ASMedia 1092
  wait: add wake_up_pollfree()
  UBUNTU: SAUCE: binder: export __wake_up_pollfree for binder module
  binder: use wake_up_pollfree()
  signalfd: use wake_up_pollfree()
  aio: keep poll requests on waitqueue until completed
  aio: fix use-after-free due to missing POLLFREE handling
  net: mvpp2: fix XDP rx queues registering
  tracefs: Set all files to the same group ownership as the mount option
  block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2

[Kernel-packages] [Bug 1956800] Re: Hirsute update: upstream stable patchset 2022-01-07

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2022-01-07

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-01-07

  Ported from the following upstream stable releases:
  v5.10.84, v5.15.7

     from git://git.kernel.org/

  NFSv42: Fix pagecache invalidation after COPY/CLONE
  can: j1939: j1939_tp_cmd_recv(): check the dst address of TP.CM_BAM
  gfs2: release iopen glock early in evict
  gfs2: Fix length of holes reported at end-of-file
  powerpc/pseries/ddw: Revert "Extend upper limit for huge DMA window for 
persistent memory"
  drm/sun4i: fix unmet dependency on RESET_CONTROLLER for PHY_SUN6I_MIPI_DPHY
  mac80211: do not access the IV when it was stripped
  net/smc: Transfer remaining wait queue entries during fallback
  atlantic: Fix OOB read and write in hw_atl_utils_fw_rpc_wait
  net: return correct error code
  platform/x86: thinkpad_acpi: Add support for dual fan control
  platform/x86: thinkpad_acpi: Fix WWAN device disabled issue after S3 deep
  s390/setup: avoid using memblock_enforce_memory_limit
  btrfs: check-integrity: fix a warning on write caching disabled disk
  thermal: core: Reset previous low and high trip during thermal zone init
  scsi: iscsi: Unblock session then wake up error handler
  drm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
  drm/amd/amdgpu: fix potential memleak
  ata: ahci: Add Green Sardine vendor ID as board_ahci_mobile
  ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in 
hns_dsaf_ge_srst_by_port()
  ipv6: check return value of ipv6_skip_exthdr
  net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of 
bound
  net: ethernet: dec: tulip: de4x5: fix possible array overflows in 
type3_infoblock()
  perf inject: Fix ARM SPE handling
  perf hist: Fix memory leak of a perf_hpp_fmt
  perf report: Fix memory leaks around perf_tip()
  net/smc: Avoid warning of possible recursive locking
  ACPI: Add stubs for wakeup handler functions
  vrf: Reset IPCB/IP6CB when processing outbound pkts in vrf dev xmit
  kprobes: Limit max data_size of the kretprobe instances
  rt2x00: do not mark device gone on EPROTO errors during start
  cpufreq: Fix get_cpu_device() failure in add_cpu_dev_symlink()
  s390/pci: move pseudo-MMIO to prevent MIO overlap
  fget: check that the fd still exists after getting a ref to it
  sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl
  sata_fsl: fix warning in remove_proc_entry when rmmod sata_fsl
  ipv6: fix memory leak in fib6_rule_suppress
  drm/amd/display: Allow DSC on supported MST branch devices
  KVM: Disallow user memslot with size that exceeds "unsigned long"
  KVM: nVMX: Flush current VPID (L1 vs. L2) for KVM_REQ_TLB_FLUSH_GUEST
  KVM: x86: Use a stable condition around all VT-d PI paths
  KVM: arm64: Avoid setting the upper 32 bits of TCR_EL2 and CPTR_EL2 to 1
  KVM: X86: Use vcpu->arch.walk_mmu for kvm_mmu_invlpg()
  tracing/histograms: String compares should not care about signed values
  wireguard: selftests: increase default dmesg log size
  wireguard: allowedips: add missing __rcu annotation to satisfy sparse
  wireguard: selftests: actually test for routing loops
  wireguard: selftests: rename DEBUG_PI_LIST to DEBUG_PLIST
  wireguard: device: reset peer src endpoint when netns exits
  wireguard: receive: use ring buffer for incoming handshakes
  wireguard: receive: drop handshakes if queue lock is contended
  wireguard: ratelimiter: use kvcalloc() instead of kvzalloc()
  i2c: stm32f7: flush TX FIFO upon transfer errors
  i2c: stm32f7: recover the bus on access timeout
  i2c: stm32f7: stop dma transfer in case of NACK
  i2c: cbus-gpio: set atomic transfer callback
  natsemi: xtensa: fix section mismatch warnings
  tcp: fix page frag corruption on page fault
  net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings()
  net: mpls: Fix notifications when deleting a device
  siphash: use _unaligned version by default
  arm64: ftrace: add missing BTIs
  net/mlx4_en: Fix an use-after-free bug in mlx4_en_try_al

[Kernel-packages] [Bug 1955083] Re: Hirsute update: upstream stable patchset 2021-12-16

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2021-12-16

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-12-16

  Ported from the following upstream stable releases:
  v5.10.81, v5.14.21, v5.15.4

     from git://git.kernel.org/

 Note: upstream stable v5.14 has now reached EOL, as of
  v5.14.21.

  fortify: Explicitly disable Clang support
  block: Add a helper to validate the block size
  loop: Use blk_validate_block_size() to validate block size
  bootconfig: init: Fix memblock leak in xbc_make_cmdline()
  net: stmmac: add clocks management for gmac driver
  net: stmmac: platform: fix build error with !CONFIG_PM_SLEEP
  net: stmmac: fix missing unlock on error in stmmac_suspend()
  net: stmmac: fix system hang if change mac address after interface ifdown
  net: stmmac: fix issue where clk is being unprepared twice
  net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings
  x86/iopl: Fake iopl(3) CLI/STI usage
  parisc/entry: fix trace test in syscall exit path
  PCI/MSI: Destroy sysfs before freeing entries
  PCI/MSI: Deal with devices lying about their MSI mask capability
  PCI: Add MSI masking quirk for Nvidia ION AHCI
  erofs: remove the occupied parameter from z_erofs_pagevec_enqueue()
  erofs: fix unsafe pagevec reuse of hooked pclusters
  scripts/lld-version.sh: Rewrite based on upstream ld-version.sh
  perf/core: Avoid put_page() when GUP fails
  thermal: Fix NULL pointer dereferences in of_thermal_ functions
  selftests/x86/iopl: Adjust to the faked iopl CLI/STI usage
  Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device.
  Bluetooth: btusb: Add support for TP-Link UB500 Adapter
  string: uninline memcpy_and_pad
  btrfs: introduce btrfs_is_data_reloc_root
  btrfs: zoned: only allow one process to add pages to a relocation inode
  UBUNTU: upstream stable to v5.10.81, v5.14.21, v5.15.4

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


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

[Kernel-packages] [Bug 1956513] Re: Hirsute update: upstream stable patchset 2022-01-05

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2022-01-05

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-01-05

  Ported from the following upstream stable releases:
  v5.10.83, v5.15.6

     from git://git.kernel.org/

  ACPI: Get acpi_device's parent from the parent field
  USB: serial: option: add Telit LE910S1 0x9200 composition
  USB: serial: option: add Fibocom FM101-GL variants
  usb: dwc2: gadget: Fix ISOC flow for elapsed frames
  usb: dwc2: hcd_queue: Fix use of floating point literal
  usb: dwc3: gadget: Ignore NoStream after End Transfer
  usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer
  usb: dwc3: gadget: Fix null pointer exception
  net: nexthop: fix null pointer dereference when IPv6 is not enabled
  usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in probe
  usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts
  usb: hub: Fix usb enumeration issue due to address0 race
  usb: hub: Fix locking issues with address0_mutex
  binder: fix test regression due to sender_euid change
  ALSA: ctxfi: Fix out-of-range access
  ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100
  ALSA: hda/realtek: Fix LED on HP ProBook 435 G7
  media: cec: copy sequence field for the reply
  Revert "parisc: Fix backtrace to always include init funtion names"
  HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts
  staging/fbtft: Fix backlight
  staging: greybus: Add missing rwsem around snd_ctl_remove() calls
  staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect()
  fuse: release pipe buf after last use
  xen: don't continue xenstore initialization in case of errors
  xen: detect uninitialized xenbus in xenbus_init
  KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB
  tracing/uprobe: Fix uprobe_perf_open probes iteration
  tracing: Fix pid filtering when triggers are attached
  mmc: sdhci-esdhc-imx: disable CMDQ support
  mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB
  mdio: aspeed: Fix "Link is Down" issue
  powerpc/32: Fix hardlockup on vmap stack overflow
  PCI: aardvark: Deduplicate code in advk_pcie_rd_conf()
  PCI: aardvark: Implement re-issuing config requests on CRS response
  PCI: aardvark: Simplify initialization of rootcap on virtual bridge
  PCI: aardvark: Fix link training
  proc/vmcore: fix clearing user buffer by properly using clear_user()
  netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY
  netfilter: ctnetlink: do not erase error code with EINVAL
  netfilter: ipvs: Fix reuse connection if RS weight is 0
  netfilter: flowtable: fix IPv6 tunnel addr match
  ARM: dts: BCM5301X: Fix I2C controller interrupt
  ARM: dts: BCM5301X: Add interrupt properties to GPIO node
  ARM: dts: bcm2711: Fix PCIe interrupts
  ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer
  ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling
  ASoC: topology: Add missing rwsem around snd_ctl_remove() calls
  ASoC: codecs: wcd934x: return error code correctly from hw_params
  net: ieee802154: handle iftypes as u32
  firmware: arm_scmi: pm: Propagate return value to caller
  NFSv42: Don't fail clone() unless the OP_CLONE operation failed
  ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE
  drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks
  scsi: mpt3sas: Fix kernel panic during drive powercycle test
  drm/vc4: fix error code in vc4_create_object()
  net: marvell: prestera: fix double free issue on err path
  iavf: Prevent changing static ITR values if adaptive moderation is on
  ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec
  mptcp: fix delack timer
  firmware: smccc: Fix check for ARCH_SOC_ID not implemented
  ipv6: fix typos in __ip6_finish_output()
  nfp: checking parameter process for rx-usecs/tx-usecs is invalid
  net: stmmac: fix system hang caused by eee_ctrl_timer during suspend/resume
  net: stmmac: retain PTP clock time during SIOCSHWTSTAMP ioctls
  net: ipv6: add fib6_nh_release_dsts stub
  net: nexthop: release IPv6 per-cpu dsts when replacing a nex

[Kernel-packages] [Bug 1954815] Re: Support newer kernels

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: crash (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Support newer kernels

Status in crash package in Ubuntu:
  Invalid
Status in crash source package in Focal:
  In Progress
Status in crash source package in Hirsute:
  Won't Fix
Status in crash source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Kernels newer than 5.4 cannot be analyzed using the crash tool from Focal.

  [Test case]
  Install a linux dbgsym package and run the command below, replacing 
vmlinux-5.11.0-1023-azure by the appropriate kernel debug file.

  crash /usr/lib/debug/boot/vmlinux-5.11.0-1023-azure /proc/kcore

  [Potential regression]
  crash might fail to work with older kernels, or some of its commands might 
not work anymore.

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


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

[Kernel-packages] [Bug 1955277] Re: Hirsute update: upstream stable patchset 2021-12-17

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2021-12-17

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-12-17

  Ported from the following upstream stable releases:
  v5.10.82, v5.15.5

     from git://git.kernel.org/

  arm64: zynqmp: Do not duplicate flash partition label property
  arm64: zynqmp: Fix serial compatible string
  ARM: dts: sunxi: Fix OPPs node name
  arm64: dts: allwinner: h5: Fix GPU thermal zone node name
  arm64: dts: allwinner: a100: Fix thermal zone node name
  staging: wfx: ensure IRQ is ready before enabling it
  ARM: dts: NSP: Fix mpcore, mmc node names
  scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq()
  arm64: dts: rockchip: Disable CDN DP on Pinebook Pro
  arm64: dts: hisilicon: fix arm,sp805 compatible string
  RDMA/bnxt_re: Check if the vlan is valid before reporting
  bus: ti-sysc: Add quirk handling for reinit on context lost
  bus: ti-sysc: Use context lost quirk for otg
  usb: musb: tusb6010: check return value after calling platform_get_resource()
  usb: typec: tipd: Remove WARN_ON in tps6598x_block_read
  ARM: dts: ux500: Skomer regulator fixes
  staging: rtl8723bs: remove possible deadlock when disconnect (v2)
  ARM: BCM53016: Specify switch ports for Meraki MR32
  arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
  arm64: dts: qcom: ipq6018: Fix qcom,controlled-remotely property
  arm64: dts: freescale: fix arm,sp805 compatible string
  ASoC: SOF: Intel: hda-dai: fix potential locking issue
  clk: imx: imx6ul: Move csi_sel mux to correct base register
  ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect
  scsi: advansys: Fix kernel pointer leak
  ALSA: intel-dsp-config: add quirk for APL/GLK/TGL devices based on ES8336 
codec
  firmware_loader: fix pre-allocated buf built-in firmware use
  ARM: dts: omap: fix gpmc,mux-add-data type
  usb: host: ohci-tmio: check return value after calling platform_get_resource()
  ARM: dts: ls1021a: move thermal-zones node out of soc/
  ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash
  ALSA: ISA: not for M68K
  tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc
  MIPS: sni: Fix the build
  scsi: scsi_debug: Fix out-of-bound read in resp_readcap16()
  scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs()
  scsi: target: Fix ordered tag handling
  scsi: target: Fix alua_tg_pt_gps_count tracking
  iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr()
  powerpc/5200: dts: fix memory node unit name
  ARM: dts: qcom: fix memory and mdio nodes naming for RB3011
  ALSA: gus: fix null pointer dereference on pointer block
  powerpc/dcr: Use cmplwi instead of 3-argument cmpli
  powerpc/8xx: Fix Oops with STRICT_KERNEL_RWX without DEBUG_RODATA_TEST
  sh: check return code of request_irq
  maple: fix wrong return value of maple_bus_init().
  f2fs: fix up f2fs_lookup tracepoints
  f2fs: fix to use WHINT_MODE
  sh: fix kconfig unmet dependency warning for FRAME_POINTER
  sh: math-emu: drop unused functions
  sh: define __BIG_ENDIAN for math-emu
  f2fs: compress: disallow disabling compress on non-empty compressed file
  f2fs: fix incorrect return value in f2fs_sanity_check_ckpt()
  clk: ingenic: Fix bugs with divided dividers
  clk/ast2600: Fix soc revision for AHB
  clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk
  mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set
  sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain()
  perf/x86/vlbr: Add c->flags to vlbr event constraints
  blkcg: Remove extra blkcg_bio_issue_init
  tracing/histogram: Do not copy the fixed-size char array field over the field 
size
  perf bpf: Avoid memory leak from perf_env__insert_btf()
  perf bench futex: Fix memory leak of perf_cpu_map__new()
  perf tests: Remove bash construct from record+zstd_comp_decomp.sh
  drm/nouveau: hdmigv100.c: fix corrupted HDMI Vendor InfoFrame
  tcp: Fix uninitialized access in skb frags array for Rx 0cp.
  tracing: Add length protection to histogram string c

[Kernel-packages] [Bug 1954533] Re: Hirsute update: upstream stable patchset 2021-12-10

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2021-12-10

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-12-10

  Ported from the following upstream stable releases:
  v5.10.80, v5.14.19
v5.14.20

     from git://git.kernel.org/

  Note: This patch set includes patches from v5.10.80 and v5.14.19.
  v5.14.20 was comprised entirely of a handful of reverts to patches we
  never carried in Hirsute.

  xhci: Fix USB 3.1 enumeration issues by increasing roothub power-on-good delay
  usb: xhci: Enable runtime-pm by default on AMD Yellow Carp platform
  Input: iforce - fix control-message timeout
  Input: elantench - fix misreporting trackpoint coordinates
  Input: i8042 - Add quirk for Fujitsu Lifebook T725
  libata: fix read log timeout value
  ocfs2: fix data corruption on truncate
  scsi: core: Remove command size deduction from scsi_setup_scsi_cmnd()
  scsi: qla2xxx: Fix kernel crash when accessing port_speed sysfs file
  scsi: qla2xxx: Fix use after free in eh_abort path
  mmc: mtk-sd: Add wait dma stop done flow
  mmc: dw_mmc: Dont wait for DRTO on Write RSP error
  exfat: fix incorrect loading of i_blocks for large files
  parisc: Fix set_fixmap() on PA1.x CPUs
  parisc: Fix ptrace check on syscall return
  tpm: Check for integer overflow in tpm2_map_response_body()
  firmware/psci: fix application of sizeof to pointer
  crypto: s5p-sss - Add error handling in s5p_aes_probe()
  media: rkvdec: Do not override sizeimage for output format
  media: ite-cir: IR receiver stop working after receive overflow
  media: rkvdec: Support dynamic resolution changes
  media: ir-kbd-i2c: improve responsiveness of hauppauge zilog receivers
  media: v4l2-ioctl: Fix check_ext_ctrls
  ALSA: hda/realtek: Fix mic mute LED for the HP Spectre x360 14
  ALSA: hda/realtek: Add a quirk for HP OMEN 15 mute LED
  ALSA: hda/realtek: Add quirk for Clevo PC70HS
  ALSA: hda/realtek: Headset fixup for Clevo NH77HJQ
  ALSA: hda/realtek: Add a quirk for Acer Spin SP513-54N
  ALSA: hda/realtek: Add quirk for ASUS UX550VE
  ALSA: hda/realtek: Add quirk for HP EliteBook 840 G7 mute LED
  ALSA: ua101: fix division by zero at probe
  ALSA: 6fire: fix control and bulk message timeouts
  ALSA: line6: fix control and interrupt message timeouts
  ALSA: usb-audio: Line6 HX-Stomp XL USB_ID for 48k-fixed quirk
  ALSA: usb-audio: Add registration quirk for JBL Quantum 400
  ALSA: hda: Free card instance properly at probe errors
  ALSA: synth: missing check for possible NULL after the call to kstrdup
  ALSA: timer: Fix use-after-free problem
  ALSA: timer: Unconditionally unlink slave instances, too
  ext4: fix lazy initialization next schedule time computation in more granular 
unit
  ext4: ensure enough credits in ext4_ext_shift_path_extents
  ext4: refresh the ext4_ext_path struct after dropping i_data_sem.
  fuse: fix page stealing
  x86/sme: Use #define USE_EARLY_PGTABLE_L5 in mem_encrypt_identity.c
  x86/cpu: Fix migration safety with X86_BUG_NULL_SEL
  x86/irq: Ensure PI wakeup handler is unregistered before module unload
  ASoC: soc-core: fix null-ptr-deref in snd_soc_del_component_unlocked()
  ALSA: hda/realtek: Fixes HP Spectre x360 15-eb1xxx speakers
  cavium: Return negative value when pci_alloc_irq_vectors() fails
  scsi: qla2xxx: Return -ENOMEM if kzalloc() fails
  scsi: qla2xxx: Fix unmap of already freed sgl
  mISDN: Fix return values of the probe function
  cavium: Fix return values of the probe function
  sfc: Export fibre-specific supported link modes
  sfc: Don't use netif_info before net_device setup
  hyperv/vmbus: include linux/bitops.h
  ARM: dts: sun7i: A20-olinuxino-lime2: Fix ethernet phy-mode
  reset: socfpga: add empty driver allowing consumers to probe
  mmc: winbond: don't build on M68K
  drm: panel-orientation-quirks: Add quirk for Aya Neo 2021
  fcnal-test: kill hanging ping/nettest binaries on cleanup
  bpf: Define bpf_jit_alloc_exec_limit for arm64 JIT
  bpf: Prevent increasing bpf_jit_limit above max
  gpio: mlxbf2.c: Add check for 

[Kernel-packages] [Bug 1952785] Re: Hirsute update: upstream stable patchset 2021-11-30

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute update: upstream stable patchset 2021-11-30

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  SRU Justification

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

     upstream stable patchset 2021-11-30

  Ported from the following upstream stable releases:
  v5.10.77, v5.14.16
  v5.10.78, v5.14.17
  v5.10.79, v5.14.18

     from git://git.kernel.org/

  ARM: 9132/1: Fix __get_user_check failure with ARM KASAN images
  ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned
  ARM: 9134/1: remove duplicate memcpy() definition
  ARM: 9138/1: fix link warning with XIP + frame-pointer
  ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype
  ARM: 9141/1: only warn about XIP address when not compile testing
  ext4: fix possible UAF when remounting r/o a mmp-protected file system
  usbnet: sanity check for maxpacket
  usbnet: fix error return code in usbnet_probe()
  Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode"
  pinctrl: amd: disable and mask interrupts on probe
  ata: sata_mv: Fix the error handling of mv_chip_id()
  nfc: port100: fix using -ERRNO as command type mask
  net/tls: Fix flipped sign in tls_err_abort() calls
  mmc: vub300: fix control-message timeouts
  mmc: cqhci: clear HALT state after CQE enable
  mmc: mediatek: Move cqhci init behind ungate clock
  mmc: dw_mmc: exynos: fix the finding clock sample value
  mmc: sdhci: Map more voltage level to SDHCI_POWER_330
  mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning 
circuit
  ocfs2: fix race between searching chunks and release journal_head from 
buffer_head
  nvme-tcp: fix H2CData PDU send accounting (again)
  cfg80211: scan: fix RCU in cfg80211_add_nontrans_list()
  cfg80211: fix management registrations locking
  net: lan78xx: fix division by zero in send path
  mm, thp: bail out early in collapse_file for writeback page
  drm/amdgpu: fix out of bounds write
  cgroup: Fix memory leak caused by missing cgroup_bpf_offline
  riscv, bpf: Fix potential NULL dereference
  tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function
  bpf: Fix potential race in tail call compatibility check
  bpf: Fix error usage of map_fd and fdget() in generic_map_update_batch()
  IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields
  IB/hfi1: Fix abba locking issue with sc_disable()
  nvmet-tcp: fix data digest pointer calculation
  nvme-tcp: fix data digest pointer calculation
  nvme-tcp: fix possible req->offset corruption
  octeontx2-af: Display all enabled PF VF rsrc_alloc entries.
  RDMA/mlx5: Set user priority for DCT
  arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node
  reset: brcmstb-rescal: fix incorrect polarity of status bit
  regmap: Fix possible double-free in regcache_rbtree_exit()
  net: batman-adv: fix error handling
  net-sysfs: initialize uid and gid before calling net_ns_get_ownership
  cfg80211: correct bridge/4addr mode check
  net: Prevent infinite while loop in skb_tx_hash()
  RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string
  gpio: xgs-iproc: fix parsing of ngpios property
  nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST
  mlxsw: pci: Recycle received packet upon allocation failure
  net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume 
fails
  net: ethernet: microchip: lan743x: Fix dma allocation failure by using 
dma_set_mask_and_coherent
  net: nxp: lpc_eth.c: avoid hang when bringing interface down
  net/tls: Fix flipped sign in async_wait.err assignment
  phy: phy_ethtool_ksettings_get: Lock the phy for consistency
  phy: phy_ethtool_ksettings_set: Move after phy_start_aneg
  phy: phy_start_aneg: Add an unlocked version
  phy: phy_ethtool_ksettings_set: Lock the PHY while changing settings
  sctp: use init_tag from inithdr for ABORT chunk
  sctp: fix the processing for INIT_ACK chunk
  sctp: fix the processing for COOKIE_ECHO chunk
  sctp: add vtag check in sctp_sf_violation
  sctp: add vtag check in sctp_sf_do_8_5_1_E_sa
  sctp: add vtag check in sctp_sf_ootb
  lan743x: fix endianness when acc

[Kernel-packages] [Bug 1951011] Re: linux-aws: Make a signed kernel

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-aws (Ubuntu Hirsute)
   Status: Fix Committed => Won't Fix

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

Title:
  linux-aws: Make a signed kernel

Status in linux-aws package in Ubuntu:
  New
Status in linux-aws-5.11 package in Ubuntu:
  Invalid
Status in linux-aws-5.13 package in Ubuntu:
  Invalid
Status in linux-aws-hwe package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Invalid
Status in linux-aws-5.11 source package in Xenial:
  Invalid
Status in linux-aws-5.13 source package in Xenial:
  Invalid
Status in linux-aws-hwe source package in Xenial:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws-5.11 source package in Bionic:
  Invalid
Status in linux-aws-5.13 source package in Bionic:
  Invalid
Status in linux-aws-hwe source package in Bionic:
  Invalid
Status in linux-aws source package in Focal:
  Fix Released
Status in linux-aws-5.11 source package in Focal:
  Fix Committed
Status in linux-aws-5.13 source package in Focal:
  Fix Committed
Status in linux-aws-hwe source package in Focal:
  Invalid
Status in linux-aws source package in Hirsute:
  Won't Fix
Status in linux-aws-5.11 source package in Hirsute:
  Invalid
Status in linux-aws-5.13 source package in Hirsute:
  Invalid
Status in linux-aws-hwe source package in Hirsute:
  Invalid
Status in linux-aws source package in Impish:
  In Progress
Status in linux-aws-5.11 source package in Impish:
  Invalid
Status in linux-aws-5.13 source package in Impish:
  Invalid
Status in linux-aws-hwe source package in Impish:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  Ubuntu AWS kernels on secure boot instances will not load.

  [Fix]

  Generate signed kernels and packages

  [Test Plan]

  Boot in a secure boot (UEFI) environment.

  [Where things could go wrong]

  This is a new packaging feature.

  [Other Info]

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


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

[Kernel-packages] [Bug 1950666] Re: system crash when removing ipmi_msghandler module

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  system crash when removing ipmi_msghandler module

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  Fix Committed
Status in linux source package in Jammy:
  In Progress

Bug description:
  [IMPACT]

  Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup SRCU 
user->release_barrier)
  pushes the removal of an ipmi_user into the system's workqueue.

  Whenever an ipmi_user struct is about to be removed it is scheduled as
  a work on the system's workqueue to guarantee the free operation won't
  be executed in atomic context. When the work is executed the
  free_user_work() function is invoked which frees the ipmi_user.

  When ipmi_msghandler module is removed in cleanup_ipmi() function, there is 
no check if there are any pending works to be executed.
  Therefore, there is a potential race condition :
  An ipmi_user is scheduled for removal and shortly after to remove the 
ipmi_msghandler module.
  If the scheduled work delays execution for any reason and the module is 
removed first, then when the work is executed the pages of free_user_work() are 
gone and the system crashes with the following :

  BUG: unable to handle page fault for address: c05c3450
  #PF: supervisor instruction fetch in kernel mode
  #PF: error_code(0x0010) - not-present page
  PGD 635420e067 P4D 635420e067 PUD 6354210067 PMD 4711e51067 PTE 0
  Oops: 0010 [#1] SMP PTI
  CPU: 19 PID: 29646 Comm: kworker/19:1 Kdump: loaded Not tainted 
5.4.0-77-generic #86~18.04.1-Ubuntu
  Hardware name: Ciara Technologies ORION RS610-G4-DTH4S/MR91-FS1-Y9, BIOS F29 
05/23/2019
  Workqueue: events 0xc05c3450
  RIP: 0010:0xc05c3450
  Code: Bad RIP value.
  RSP: 0018:b721333c3e88 EFLAGS: 00010286
  RAX: c05c3450 RBX: 92a95f56a740 RCX: b7221cfd14e8
  RDX: 0001 RSI: 92616040d4b0 RDI: b7221cf404e0
  RBP: b721333c3ec0 R08: 73746e657665 R09: 8080808080808080
  R10: b721333c3de0 R11: fefefefefefefeff R12: 92a95f570700
  R13: 92a0a40ece40 R14: b7221cf404e0 R15: 092a95f57070
  FS: () GS:92a95f54() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: c05c3426 CR3: 0081e9bfc005 CR4: 007606e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  PKRU: 5554
  Call Trace:
  ? process_one_work+0x20f/0x400
  worker_thread+0x34/0x410
  kthread+0x121/0x140
  ? process_one_work+0x400/0x400
  ? kthread_park+0x90/0x90
  ret_from_fork+0x35/0x40
  Modules linked in: xt_REDIRECT xt_owner ipt_rpfilter xt_CT xt_multiport 
xt_set ip_set_hash_ip veth xt_statistic ipt_REJECT
  ... megaraid_sas ahci libahci wmi [last unloaded: ipmi_msghandler]
  CR2: c05c3450

  [TEST CASE]

  The user who reported the issue can reproduce reliably by stopping the ipmi 
related services and then removing the ipmi modules.
  I could reproduce the issue only when turning the normal 'work' to delayed 
work.

  [WHERE PROBLEMS COULD OCCUR]

  The fixing patch creates a dedicated workqueue for the remove_work
  struct of ipmi_user when loading the ipmi_msghandler modules and
  destroys the workqueue when removing the module. Therefore any
  potential problems would occur during these two operations or when
  scheduling works on the dedicated workqueue.

  [OTHER]

  Upstream patches : 
  1d49eb91e86e (ipmi: Move remove_work to dedicated workqueue)
  5a3ba99b62d8 (ipmi: msghandler: Make symbol 'remove_work_wq' static)

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


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

[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-aws (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

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

Title:
  kernel package does not build nvme-tcp module

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Focal:
  Confirmed
Status in linux-aws source package in Hirsute:
  Won't Fix
Status in linux-aws source package in Impish:
  Confirmed
Status in linux-aws source package in Jammy:
  Fix Released

Bug description:
  linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is 
no option to use it.
  The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used 
to build the kernel image.

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


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

[Kernel-packages] [Bug 1933547] Re: tpm driver causes non-fatal kernel crash on boot

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  tpm driver causes non-fatal kernel crash on boot

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  tpm driver appears to be causng a non-fatal crash on boot.

  Trace below

  Jun 24 07:22:45 munin kernel: [1.138595] [ cut here 
]
  Jun 24 07:22:45 munin kernel: [1.138596] TPM returned invalid status
  Jun 24 07:22:45 munin kernel: [1.138611] WARNING: CPU: 8 PID: 1 at 
drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_st
  atus+0x82/0x90
  Jun 24 07:22:45 munin kernel: [1.138627] Modules linked in:
  Jun 24 07:22:45 munin kernel: [1.138631] CPU: 8 PID: 1 Comm: swapper/0 
Not tainted 5.11.0-22-generic #23-Ubuntu
  Jun 24 07:22:45 munin kernel: [1.138635] Hardware name: IT Channel Pty 
Ltd NH50_70RA /NH50_70
  RA , BIOS 1.07.13TMB1 06/06/2020
  Jun 24 07:22:45 munin kernel: [1.138638] RIP: 
0010:tpm_tis_status+0x82/0x90
  Jun 24 07:22:45 munin kernel: [1.138644] Code: 25 28 00 00 00 75 2b c9 c3 
31 c0 80 3d 8d df 76 01 00 75 e4 48 c7 
  c7 24 44 04 a2 88 45 ef c6 05 7a df 76 01 01 e8 fb a3 43 00 <0f> 0b 0f b6 45 
ef eb c6 e8 71 77 49 00 90 0f 1f 44 00 0
  0 55 48 89
  Jun 24 07:22:45 munin kernel: [1.138649] RSP: :bfc80007b860 
EFLAGS: 00010286
  Jun 24 07:22:45 munin kernel: [1.138653] RAX:  RBX: 
9a2617bf8000 RCX: a2723528
  Jun 24 07:22:45 munin kernel: [1.138656] RDX: c000dfff RSI: 
 RDI: 0247
  Jun 24 07:22:45 munin kernel: [1.138659] RBP: bfc80007b878 R08: 
 R09: bfc80007b640
  Jun 24 07:22:45 munin kernel: [1.138661] R10: bfc80007b638 R11: 
a2753568 R12: 9a2617bf8000
  Jun 24 07:22:45 munin kernel: [1.138663] R13: 9a26032fa558 R14: 
9a260330 R15: 9a2617bf8000
  Jun 24 07:22:45 munin kernel: [1.138666] FS:  () 
GS:9a2d5060() knlGS:
  
  Jun 24 07:22:45 munin kernel: [1.138670] CS:  0010 DS:  ES:  CR0: 
80050033
  Jun 24 07:22:45 munin kernel: [1.138673] CR2:  CR3: 
000288e10001 CR4: 003706e0
  Jun 24 07:22:45 munin kernel: [1.138676] Call Trace:
  Jun 24 07:22:45 munin kernel: [1.138680]  tpm_tis_send_data+0x42/0x250
  Jun 24 07:22:45 munin kernel: [1.138688]  tpm_tis_send_main+0x32/0xf0
  Jun 24 07:22:45 munin kernel: [1.138693]  ? 
kernel_init_free_pages+0x4a/0x60
  Jun 24 07:22:45 munin kernel: [1.138699]  tpm_tis_send+0x30/0xa0
  Jun 24 07:22:45 munin kernel: [1.138704]  tpm_try_transmit+0x64/0x1d0
  Jun 24 07:22:45 munin kernel: [1.138709]  tpm_transmit+0x92/0x250
  Jun 24 07:22:45 munin kernel: [1.138713]  tpm_transmit_cmd+0x2a/0x90
  Jun 24 07:22:45 munin kernel: [1.138717]  tpm2_get_tpm_pt+0xe9/0x150
  Jun 24 07:22:45 munin kernel: [1.138722]  
tpm_tis_probe_irq_single+0x17f/0x223
  Jun 24 07:22:45 munin kernel: [1.138728]  ? tpm_tcg_write32+0x1a/0x20
  Jun 24 07:22:45 munin kernel: [1.138734]  
tpm_tis_core_init.cold+0x179/0x2e7
  Jun 24 07:22:45 munin kernel: [1.138739]  tpm_tis_init.part.0+0xa0/0x120
  Jun 24 07:22:45 munin kernel: [1.138744]  tpm_tis_plat_probe+0xd4/0x100
  Jun 24 07:22:45 munin kernel: [1.138751]  platform_probe+0x45/0xa0
  Jun 24 07:22:45 munin kernel: [1.138757]  really_probe+0xff/0x460
  Jun 24 07:22:45 munin kernel: [1.138762]  driver_probe_device+0xe9/0x160
  Jun 24 07:22:45 munin kernel: [1.138767]  device_driver_attach+0xab/0xb0
  Jun 24 07:22:45 munin kernel: [1.138772]  __driver_attach+0x8f/0x150
  Jun 24 07:22:45 munin kernel: [1.138776]  ? device_driver_attach+0xb0/0xb0
  Jun 24 07:22:45 munin kernel: [1.138781]  bus_for_each_dev+0x7e/0xc0
  Jun 24 07:22:45 munin kernel: [1.138785]  driver_attach+0x1e/0x20
  Jun 24 07:22:45 munin kernel: [1.138789]  bus_add_driver+0x135/0x1f0
  Jun 24 07:22:45 munin kernel: [1.138793]  driver_register+0x95/0xf0
  Jun 24 07:22:45 munin kernel: [1.138798]  ? tpm_init+0xf6/0xf6
  Jun 24 07:22:45 munin kernel: [1.138805]  
__platform_driver_register+0x1e/0x20
  Jun 24 07:22:45 munin kernel: [1.138811]  init_tis+0x87/0xdd
  Jun 24 07:22:45 munin kernel: [1.138817]  ? kobject_uevent+0xb/0x10
  Jun 24 07:22:45 munin kernel: [1.138823]  ? driver_register+0xcd/0xf0
  Jun 24 07:22:45 munin kernel: [1.138828]  ? agp_intel_init+0x2f/0x2f
  Jun 24 07:22:45 munin kernel: [1.138833]  ? 
__pci_register_driver+0x54/0x60
  Jun 24 07:22:45 munin kernel: [1.138838]  ? tpm_ini

[Kernel-packages] [Bug 1936577] Re: Introduce the 470-server series

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-restricted-modules (Ubuntu Hirsute)
   Status: Triaged => Won't Fix

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

Title:
  Introduce the 470-server series

Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Hirsute:
  Won't Fix
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Won't Fix

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

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* Initial release (LP: #1936577).

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


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

[Kernel-packages] [Bug 1936577] Re: Introduce the 470-server series

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: nvidia-graphics-drivers-460-server (Ubuntu Hirsute)
   Status: Fix Committed => Won't Fix

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

Title:
  Introduce the 470-server series

Status in linux-restricted-modules package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in linux-restricted-modules source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in linux-restricted-modules source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Hirsute:
  Won't Fix
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Won't Fix

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

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 470.57.02 (470-server) ==

* Initial release (LP: #1936577).

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


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

[Kernel-packages] [Bug 1933112] Re: fallocate05 from ltp-syscalls fails on H-azure

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  fallocate05 from ltp-syscalls fails on H-azure

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  In Progress

Bug description:
  Found on hirsute/azure 5.11.0-1007.7 and 5.11.0-1006.6. might be re-
  appearance of lp:1783880, btrfs file system, only on Azure instance
  Standard_F32s_v2:

  tst_test.c:1379: TINFO: Testing on btrfs
  tst_test.c:888: TINFO: Formatting /dev/loop3 with btrfs opts='' extra opts=''
  tst_test.c:1311: TINFO: Timeout per run is 0h 05m 00s
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file0 size 21710183
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file1 size 8070086
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file2 size 3971177
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file3 size 36915315
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file4 size 70310993
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file5 size 4807935
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file6 size 90739786
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file7 size 76896492
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file8 size 72228649
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file9 size 36207821
  tst_fill_fs.c:32: TINFO: Creating file mntpoint/file10 size 81483962
  tst_fill_fs.c:59: TINFO: write(): ENOSPC (28)
  fallocate05.c:81: TPASS: write() wrote 65536 bytes
  fallocate05.c:102: TINFO: fallocate()d 0 extra blocks on full FS
  fallocate05.c:114: TPASS: fallocate() on full FS
  fallocate05.c:130: TPASS: fallocate(FALLOC_FL_PUNCH_HOLE | 
FALLOC_FL_KEEP_SIZE)
  fallocate05.c:134: TFAIL: write(): ENOSPC (28)

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


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

[Kernel-packages] [Bug 1932549] Re: seltests/net: devlink port split failing in H-5.11 KVM kernels (Error sending command: devlink -j dev show)

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-kvm (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

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

Title:
  seltests/net: devlink port split failing in H-5.11 KVM kernels (Error
  sending command: devlink -j dev show)

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Hirsute:
  Won't Fix

Bug description:
  Got the following selftests/net failure in Hirsute, cycle sru-20210531
  :

  03:28:51 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  03:28:51 DEBUG| [stdout] # Error sending command: devlink -j dev show
  03:28:51 DEBUG| [stdout] # 
  03:28:51 DEBUG| [stdout] # Failed to connect to devlink Netlink
  03:28:51 DEBUG| [stdout] # 
  03:28:51 DEBUG| [stdout] # Traceback (most recent call last):
  03:28:51 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 277, in 
  03:28:51 DEBUG| [stdout] # main()
  03:28:51 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 239, in main
  03:28:51 DEBUG| [stdout] # assert stderr == ""
  03:28:51 DEBUG| [stdout] # AssertionError
  03:28:51 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # 
exit=1

  
  Noticed that it also failed in previous cycles (I'm not sure why I couldn't 
find a report...)

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


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

[Kernel-packages] [Bug 1932586] Re: Processes launched during the NIC load is high may hang up.

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-raspi (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

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

Title:
  Processes launched during the NIC load is high may hang up.

Status in linux-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi source package in Hirsute:
  Won't Fix

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  ❯ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  ❯ LANG=C apt-cache policy linux-raspi
  linux-raspi:
Installed: 5.11.0.1009.7
Candidate: 5.11.0.1009.7
Version table:
   *** 5.11.0.1009.7 500
  500 http://ports.ubuntu.com/ubuntu-ports hirsute-updates/main arm64 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports hirsute-security/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.11.0.1007.5 500
  500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages

  3) What you expected to happen
  Processes launched during the NIC load is high will exit normally.

  4) What happened instead
  I'm using hirsute on Raspberry Pi 4 model B(4GB RAM).
  Some processes launched during the NIC load is high might not exit.

  What "NIC load is high" means:
  - I have configured crontab to run Ookla's speedtest-cli which generates 
heavy network traffic every 15 minites.
  - During speedtest-cli, Softirq becomes higher.
  - SoC(BCM2711) built-in NIC(driver is bcmgenet)

  What "may not exit" means:
  - Some processes launched during speedtest-cli is running will not exit. It 
remains with consuming CPU 100% and not accept any signals including SIGKILL.
  - Those processes can't be attached by gdb or strace. Trying to do so, gdb 
and strace will freeze.

  I could't terminate the processes in any way. But the system could be
  rebooted by "sudo reboot" command.

  I configured RFS/RPS to distribute Softirq among CPU cores. It was
  quite effective, but did not prevent the problem completely.

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


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

[Kernel-packages] [Bug 1921902] Re: Security-Fix Xen XSA 371 for Kernel 5.4.0-71

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Security-Fix Xen XSA 371 for Kernel 5.4.0-71

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

Bug description:
  [SRU Justification]

  See [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html). commit
  871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error
  handling in xen_blkbk_map()") introduced a security vulnerability.

  Original Commit:
  871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error handling in 
xen_blkbk_map()")

  New commit with security fix:
  a846738f8c3788d846ed1f587270d2f2e3d32432 ("xen-blkback: don't leak persistent 
grants from xen_blkbk_map()")

  [Test Plan]
  none

  [Where problems could occur]
  Unknown

  [Other Info]
  - http://xenbits.xen.org/xsa/advisory-371.html
  - http://xenbits.xen.org/xsa/xsa371-linux.patch
  - http://xenbits.xen.org/xsa/advisory-365.html
  - http://xenbits.xen.org/xsa/xsa365-linux.patch

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


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

[Kernel-packages] [Bug 1922350] Re: missing firmware reported when updating initramfs

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-firmware (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  missing firmware reported when updating initramfs

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-firmware source package in Focal:
  In Progress
Status in linux-firmware source package in Groovy:
  Won't Fix
Status in linux-firmware source package in Hirsute:
  Won't Fix

Bug description:
  [SRU Justification]

  [Impact]

  Some kernel firmwares might be landed after linux-firmware forked for
  each series, or for LTS series, kernels of new versions may claim
  additional ones that were not previously available. This leaves devices
  fail to function correctly while they ought to.

  With a checking script that enumerates all the blobs available in
  upstream repo and in the Ubuntu fork of a given series, e.g. hirsute,
  iterate through all the installed kernel modules of a given version to
  check if claimed firmware blobs are available in Ubuntu's fork.
  Following kernel version/series have been checked:

* 5.11.0-14-generic/hirsute
* 5.8.0-48-generic/groovy
* 5.4.0-70-generic/focal
* 5.6.0-1052-oem/focal
* 5.8.0-48-generic/focal
* 5.10.0-1019-oem/focal
* 4.15.0-140-generic/bionic
* 4.18.0-25-generic/bionic
* 5.0.0-65-generic/bionic
* 5.4.0-70-generic/bionic

  And it gives following files were missing in at least one of above
  cases:

* amdgpu/arcturus_asd.bin
* amdgpu/arcturus_gpu_info.bin
* amdgpu/arcturus_mec.bin
* amdgpu/arcturus_mec2.bin
* amdgpu/arcturus_rlc.bin
* amdgpu/arcturus_sdma.bin
* amdgpu/arcturus_smc.bin
* amdgpu/arcturus_sos.bin
* amdgpu/arcturus_ta.bin
* amdgpu/arcturus_vcn.bin
* amdgpu/navi12_asd.bin
* amdgpu/navi12_ce.bin
* amdgpu/navi12_dmcu.bin
* amdgpu/navi12_gpu_info.bin
* amdgpu/navi12_me.bin
* amdgpu/navi12_mec.bin
* amdgpu/navi12_mec2.bin
* amdgpu/navi12_pfp.bin
* amdgpu/navi12_rlc.bin
* amdgpu/navi12_sdma.bin
* amdgpu/navi12_sdma1.bin
* amdgpu/navi12_smc.bin
* amdgpu/navi12_sos.bin
* amdgpu/navi12_ta.bin
* amdgpu/navi12_vcn.bin
* amdgpu/navy_flounder_ce.bin
* amdgpu/navy_flounder_dmcub.bin
* amdgpu/navy_flounder_me.bin
* amdgpu/navy_flounder_mec.bin
* amdgpu/navy_flounder_mec2.bin
* amdgpu/navy_flounder_pfp.bin
* amdgpu/navy_flounder_rlc.bin
* amdgpu/navy_flounder_sdma.bin
* amdgpu/navy_flounder_smc.bin
* amdgpu/navy_flounder_sos.bin
* amdgpu/navy_flounder_ta.bin
* amdgpu/navy_flounder_vcn.bin
* amdgpu/oland_uvd.bin
* amdgpu/pitcairn_uvd.bin
* amdgpu/renoir_asd.bin
* amdgpu/renoir_ce.bin
* amdgpu/renoir_gpu_info.bin
* amdgpu/renoir_me.bin
* amdgpu/renoir_mec.bin
* amdgpu/renoir_mec2.bin
* amdgpu/renoir_pfp.bin
* amdgpu/renoir_rlc.bin
* amdgpu/renoir_sdma.bin
* amdgpu/renoir_ta.bin
* amdgpu/renoir_vcn.bin
* amdgpu/sienna_cichlid_ce.bin
* amdgpu/sienna_cichlid_dmcub.bin
* amdgpu/sienna_cichlid_me.bin
* amdgpu/sienna_cichlid_mec.bin
* amdgpu/sienna_cichlid_mec2.bin
* amdgpu/sienna_cichlid_pfp.bin
* amdgpu/sienna_cichlid_rlc.bin
* amdgpu/sienna_cichlid_sdma.bin
* amdgpu/sienna_cichlid_smc.bin
* amdgpu/sienna_cichlid_sos.bin
* amdgpu/sienna_cichlid_ta.bin
* amdgpu/sienna_cichlid_vcn.bin
* amdgpu/tahiti_uvd.bin
* amdgpu/vega20_ta.bin
* amdgpu/verde_uvd.bin
* atmel/wilc1000_wifi_firmware-1.bin
* cmmb_vega_12mhz.inp
* cmmb_venice_12mhz.inp
* dvb_nova_12mhz.inp
* dvb_nova_12mhz_b0.inp
* i915/bxt_guc_33.0.0.bin
* i915/glk_guc_33.0.0.bin
* i915/icl_guc_33.0.0.bin
* i915/kbl_guc_33.0.0.bin
* i915/skl_guc_33.0.0.bin
* i915/tgl_dmc_ver2_04.bin
* i915/tgl_huc_7.5.0.bin
* isdbt_nova_12mhz.inp
* isdbt_nova_12mhz_b0.inp
* isdbt_rio.inp
* iwlwifi-Qu-b0-hr-b0-59.ucode
* iwlwifi-Qu-b0-jf-b0-50.ucode
* iwlwifi-Qu-b0-jf-b0-59.ucode
* iwlwifi-Qu-c0-hr-b0-50.ucode
* iwlwifi-Qu-c0-hr-b0-59.ucode
* iwlwifi-QuZ-a0-hr-b0-50.ucode
* iwlwifi-QuZ-a0-hr-b0-59.ucode
* iwlwifi-QuZ-a0-jf-b0-50.ucode
* iwlwifi-QuZ-a0-jf-b0-59.ucode
* iwlwifi-cc-a0-50.ucode
* iwlwifi-cc-a0-59.ucode
* mediatek/mt7663pr2h.bin
* mellanox/mlxsw_spectrum-13.2000.1886.mfa2
* mellanox/mlxsw_spectrum-13.2008.1310.mfa2
* mellanox/mlxsw_spectrum2-29.2008.1310.mfa2
* mellanox/mlxsw_spectrum3-30.2008.1310.mfa2
* mrvl/sdsd8977_combo_v2.bin
* mrvl/sdsd8997_combo_v4.bin
* rtl_nic/rtl8125a-3.fw
* rtl_nic/rtl8168fp-3.fw
* rtw88/rtw8822

[Kernel-packages] [Bug 1931131] Re: Update the 465 and the 460 NVIDIA driver series

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Update the 465 and the 460 NVIDIA driver series

Status in linux package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  In Progress
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
  Fix Released
Status in nvidia-settings source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  In Progress
Status in nvidia-graphics-drivers-390 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Won't Fix
Status in nvidia-settings source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Fix Released
Status in nvidia-settings source package in Hirsute:
  Fix Released

Bug description:
  Update the 465 and the 460 NVIDIA driver series, and add support for
  Linux 5.13 to all the driver series.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 460.84 ==

* New upstream release (LP: #1931131):
  - Added support for the following GPUs:
  GeForce RTX 3080 Ti
* debian/additional_card_ids:
  - Drop the additional IDs.
* debian/rules:
  - Skip lines that start with "#"
in debian/additional_card_ids.
* debian/templates/dkms_nvidia.conf.in:
  - Drop buildfix_kernel_5.13.patch.

  
  == 465.31 ==

* New upstream release (LP: #1931131):
  - Added support for the following GPUs:
  GeForce RTX 3080 Ti
  GeForce RTX 30

[Kernel-packages] [Bug 1930694] Re: Hirsute Hippo terminal not working

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  Hirsute Hippo terminal not working

Status in linux-raspi package in Ubuntu:
  New
Status in linux-raspi source package in Hirsute:
  Won't Fix

Bug description:
  Good Morning,

  Hirtute Hippois working great on the RPI 4. Except one strange
  behavior.

  I'am using a wireless keyboard type Logitech K400. Works well with
  most of the applications.

  This keyboard does't show characters in the Terminal mode. But if I
  connect another keyboard to the usb port, but without using it. Then
  the Logitech wireless keyboard works. Without touching the other
  connected keyboard.

  Not found the cause of this problem.

  Regards,

  Bram Verkerk

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


-- 
Mailing list: https://launchpad.net/~kernel-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.sh in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

-- 
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.sh 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:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux-oem-5.10 source package in Hirsute:
  Won't Fix

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] 

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

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  curtin: install flash-kernel in arm64 UEFI unexpected

Status in cloud-images:
  Confirmed
Status in curtin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in curtin source package in Focal:
  New
Status in linux source package in Focal:
  Fix Released
Status in curtin source package in Hirsute:
  Won't Fix
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  [Impact (linux)]
  The only package that currently satisfies the bootloader Recommends 
relationship on ARM systems is flash-kernel. This ignores EFI-based systems, 
which will instead require GRUB. Our installers know to install GRUB anyway - 
but flash-kernel also gets installed. Normally flash-kernel realizes it is not 
needed and just exits - so the impact is limited to wasting space and CPU 
cycles on each kernel update. However, there can be cases where calling 
flash-kernel can cause problems. The original report here describes one where 
flash-kernel thinks it recognizes the system and tries to run anyway, when in 
fact GRUB is the correct boot loader.

  [Test Case (linux)]
  On an arm64 system, confirm that grub-efi-arm64 is an option in the 
Recommends field:

  $ apt show linux-image-unsigned-5.4.0-78-generic  | grep Recommends

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  Recommends: flash-kernel | grub-efi-arm64, initramfs-tools | linux-
  initramfs-tool

  [What Could Go Wrong (linux)]
  First let me describe the mitigations against something going wrong. The 
proposed patch was already in the hirsute kernel at the time of hirsute GA, so 
it's had some real world testing, including in our installers. In addition, the 
patch still leaves flash-kernel as the *default* bootloader Recommends (first 
in the |'d list) - it only adds grub-efi-arm64 as a secondary option, 
preventing the installation of flash-kernel if GRUB is already there.

  So, the only scenario where I can see a problem might be if something
  depends on flash-kernel getting installed due to a Recommends even
  though GRUB is already present.

  = Original Report Follows =

  I used APM Mustang which flash-kernel supported in u-boot mode.
  But I used it with UEFI environment.
  It will cause fatal error when I used ARM64 ubuntu live server ISO to install 
system.

  In code[1], this will not install `flash-kernel` for APM Mustang because of 
UEFI.
  So that means code[2] will not disable `flash-kernel` in target system, only 
disable `update-initramfs`.

  When curtin execute to `install_kernel` stage, code[3,4] will not install 
`flash-kernel` either.
  But in code[5], it will install `linux-generic`.
  `linux-generic` has a long dependency tree and it will get `flash-kernel` in 
Recommended field.
  Apt by default will install Recommended package before kernel is installed.[6]
  So it will still execute `zz-flash-kernel` and `flash-kernel` when installing 
kernel.
  But system didn't create any `initrd.img` ever because curtin disable 
`update-initramfs` in code[2].
  This will cause that `flash-kernel` cannot find `initrd.img.` and fail 
when installing it.

  This issue didn't effect all ARM64 UEFI platform because `flash-kernel` 
didn't support them and skip.[7]
  I'm not sure which is best solution for this.
  But I think we should apply PR-27 in `flash-kernel`[8] for enhancement and 
fix curtin process with this patch both.

  If we only apply PR-27, it should work fine as well because it will be 
skipped when detecting UEFI
  and install `flash-kernel` before `disable_update_initranfs` in ARM platform 
without UEFI.[9]

  [Patch-1,2,3] might have side effect.
  Picking one patch for curtin should be enough.
  But I need your advice for this to determine which one is better for curtin.
  There are two categories
  1. avoid installing flash-kernel if no need, [Patch1,2]
  2. always install flash-kernel in arm/arm64 and make sure it be installed 
before code[2] [Patch3]
  (I will attach patch in reply.)

  Thanks a lot
  Regards,
  Date

  [1] 
https://github.com/canonical/curtin/blob/master/curtin/deps/__init__.py#L57-L58
  [2] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L1693-L1699
  [3] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L365-L370
  [4] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L311-L327
  [5] 
https://github.com/canonical/curtin/blob/master/curtin/commands/curthooks.py#L372-L374
  [6] https://github.com/Debian/apt/blob/master/apt-pkg/init.cc#L132
  [7] 
https://salsa.debian.org/installer-team/flash-kernel/-/blob/mas

[Kernel-packages] [Bug 1923683] Re: ftrace from ubuntu_kernel_selftests failed with "test for function event triggers" on F/G/H/I

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  ftrace from ubuntu_kernel_selftests failed with "test for function
  event triggers" on F/G/H/I

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Won't Fix
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  New

Bug description:
  ftrace from ubuntu_kernel_selftests failed with "test for function
  event triggers" on Groovy riscv 5.8.0-21.23

  This test was recently added, not considering a regression

  Log is getting cut off from regression test report. the below is all
  that could be retrieved at the moment:

  04/13 23:48:00 DEBUG| utils:0116| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  04/13 23:48:00 DEBUG| utils:0116| Running 'sudo make -C 
linux/tools/testing/selftests TARGETS=ftrace run_tests'
  04/13 23:48:00 DEBUG| utils:0153| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  04/13 23:48:01 DEBUG| utils:0153| [stdout] make --no-builtin-rules 
ARCH=riscv -C ../../.. headers_install
  04/13 23:48:01 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  04/13 23:48:14 DEBUG| utils:0153| [stdout]   INSTALL ./usr/include
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Nothing to be done 
for 'all'.
  04/13 23:48:15 DEBUG| utils:0153| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  04/13 23:48:16 DEBUG| utils:0153| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  04/13 23:48:16 DEBUG| utils:0153| [stdout] TAP version 13
  04/13 23:48:16 DEBUG| utils:0153| [stdout] 1..1
  04/13 23:48:16 DEBUG| utils:0153| [stdout] # selftests: ftrace: ftracetest
  04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Setting locale 
failed.
  04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Please check 
that your locale settings:
  04/13 23:48:16 ERROR| utils:0153| [stderr]LANGUAGE = (unset),
  04/13 23:48:16 ERROR| utils:0153| [stderr]LC_ALL = (unset),
  04/13 23:48:16 ERROR| utils:0153| [stderr]LC_CTYPE = "C.UTF-8",
  04/13 23:48:16 ERROR| utils:0153| [stderr]LANG = "en_US.UTF-8"
  04/13 23:48:16 ERROR| utils:0153| [stderr] are supported and 
installed on your system.
  04/13 23:48:16 ERROR| utils:0153| [stderr] perl: warning: Falling back to 
the standard locale ("C").
  04/13 23:48:17 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
  04/13 23:48:21 DEBUG| utils:0153| [stdout] # [1] Basic trace file check   
[PASS]
  04/13 23:49:02 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers   
[PASS]
  04/13 23:49:09 DEBUG| utils:0153| [stdout] # [3] Basic trace clock test   
[PASS]
  04/13 23:49:13 DEBUG| utils:0153| [stdout] # [4] Basic event tracing 
check[PASS]
  04/13 23:49:18 DEBUG| utils:0153| [stdout] # [5] Change the ringbuffer 
size   [PASS]
  04/13 23:49:23 DEBUG| utils:0153| [stdout] # [6] Snapshot and tracing 
setting [PASS]
  04/13 23:49:27 DEBUG| utils:0153| [stdout] # [7] trace_pipe and 
trace_marker  [PASS]
  04/13 23:49:32 DEBUG| utils:0153| [stdout] # [8] Test ftrace direct 
functions against tracers [UNRESOLVED]
  04/13 23:49:33 DEBUG| utils:0153| [stdout] # [9] Test ftrace direct 
functions against kprobes [UNSUPPORTED]
  04/13 23:49:37 DEBUG| utils:0153| [stdout] # [10] Generic dynamic event - 
add/remove kprobe events[FAIL]
  04/13 23:49:37 DEBUG| utils:0153| [stdout] # [11] Generic dynamic event - 
add/remove synthetic events [UNSUPPORTED]
  04/13 23:49:38 DEBUG| utils:0153| [stdout] # [12] Generic dynamic event - 
selective clear (compatibility) [UNSUPPORTED]
  04/13 23:49:39 DEBUG| utils:0153| [stdout] # [13] Generic dynamic event - 
generic clear event [UNSUPPORTED]
  04/13 23:49:44 DEBUG| utils:0153| [stdout] # [14] event tracing - 
enable/disable with ev

[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-restricted-modules (Ubuntu Hirsute)
   Status: Fix Committed => Won't Fix

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

Title:
  Introduce the 465 driver series, fabric-manager, and libnvidia-nscq

Status in fabric-manager-450 package in Ubuntu:
  Fix Released
Status in fabric-manager-460 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
  Fix Released
Status in libnvidia-nscq-460 package in Ubuntu:
  Fix Released
Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  In Progress
Status in fabric-manager-450 source package in Bionic:
  Fix Released
Status in fabric-manager-460 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
  Fix Released
Status in libnvidia-nscq-460 source package in Bionic:
  Fix Released
Status in linux-restricted-modules source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in fabric-manager-450 source package in Focal:
  Fix Released
Status in fabric-manager-460 source package in Focal:
  Fix Released
Status in libnvidia-nscq-450 source package in Focal:
  Fix Released
Status in libnvidia-nscq-460 source package in Focal:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
  Fix Released
Status in nvidia-settings source package in Focal:
  Fix Released
Status in fabric-manager-450 source package in Groovy:
  Fix Released
Status in fabric-manager-460 source package in Groovy:
  Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
  Fix Released
Status in libnvidia-nscq-460 source package in Groovy:
  Fix Released
Status in linux-restricted-modules source package in Groovy:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
  Fix Released
Status in nvidia-settings source package in Groovy:
  Fix Released
Status in fabric-manager-450 source package in Hirsute:
  Fix Released
Status in fabric-manager-460 source package in Hirsute:
  Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
  Fix Released
Status in libnvidia-nscq-460 source package in Hirsute:
  Fix Released
Status in linux-restricted-modules source package in Hirsute:
  Won't Fix
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
  Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
  Fix Released
Status in nvidia-settings source package in Hirsute:
  Fix Released

Bug description:
  Introduce the new NVIDIA 465 driver series, fabric-manager and
  libnvidia-nscq. Also migrate the UDA 450 series to the 460 series.

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

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

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

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

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

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

  [Discussion]

  [Changelog]

  == 450-server ==

    * New upstream release (LP: #1925522).
  - Fixed an issue with the NSCQ library that caused clients such as
    DCGM to fail to load the library. Since the NSCQ library version
    needs to ma

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

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

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

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Groovy:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix

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

  [Impact]

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

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

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

  [Fix]

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

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

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

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

  [Testcase]

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

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

  $ sudo ifconfig

  Next, set all devices down with:

  $ sudo ifconfig  down

  Next, bring up the QLogic QL41xxx device:

  $ sudo ifconfig  up

  Then, attempt to lookup an internal Kubernetes domain:

  $ nslookup 

  Without the patch, the connection will time out:

  ;; connection timed out; no servers could be reached

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

  There is a test kernel available in the following ppa:

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

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

  [Where problems could occur]

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

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

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

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


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

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

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: alsa-topology-conf (Ubuntu Hirsute)
   Status: New => Won't Fix

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

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

Status in alsa-topology-conf package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in alsa-topology-conf source package in Focal:
  New
Status in linux source package in Focal:
  Confirmed
Status in alsa-topology-conf source package in Hirsute:
  Won't Fix
Status in linux source package in Hirsute:
  Fix Released
Status in alsa-topology-conf source package in Impish:
  Fix Released
Status in linux source package in Impish:
  Fix Released

Bug description:
  [SRU Justification]

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

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

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

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

  
  == Original Bug Description ==

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

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

  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected results
  

  Sound output still works.

  Actual results
  ==

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

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

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


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

[Kernel-packages] [Bug 1947016] Re: cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux-realtime

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux-
  realtime

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Jammy:
  Confirmed

Bug description:
  cpufreq_boost from ubuntu_ltp.kernel_misc failed with hirsute/linux-
  realtime 5.11.0-27.28 on amd64 nodes. This test seems to be flaky as
  it doesn't fail consistently.

  07:34:27 DEBUG| [stdout] startup='Tue Oct 12 07:21:09 2021'
  07:34:27 DEBUG| [stdout] cpufreq_boost0  TINFO  :  found 'intel_pstate' 
driver, sysfs knob '/sys/devices/system/cpu/intel_pstate/no_turbo'
  07:34:27 DEBUG| [stdout] cpufreq_boost0  TINFO  :  maximum speed is 
300 KHz
  07:34:27 DEBUG| [stdout] cpufreq_boost0  TINFO  :  load CPU0 with boost 
enabled
  07:34:27 DEBUG| [stdout] cpufreq_boost0  TINFO  :  elapsed time is 1588 ms
  07:34:27 DEBUG| [stdout] cpufreq_boost0  TINFO  :  load CPU0 with boost 
disabled
  07:34:27 DEBUG| [stdout] cpufreq_boost0  TINFO  :  elapsed time is 1543 ms
  07:34:27 DEBUG| [stdout] cpufreq_boost1  TFAIL  :  cpufreq_boost.c:189: 
compare time spent with and without boost (-2%)
  07:34:27 DEBUG| [stdout] tag=cpufreq_boost stime=1634023269 dur=4 exit=exited 
stat=1 core=no cu=303 cs=0

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


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

[Kernel-packages] [Bug 1947043] Re: nvidia drivers do not update initramfs properly

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute)
   Status: New => Won't Fix

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

Title:
  nvidia drivers do not update initramfs properly

Status in linux-restricted-modules package in Ubuntu:
  New
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  New
Status in linux-restricted-modules source package in Bionic:
  New
Status in nvidia-graphics-drivers-470 source package in Bionic:
  New
Status in linux-restricted-modules source package in Focal:
  New
Status in nvidia-graphics-drivers-470 source package in Focal:
  New
Status in linux-restricted-modules source package in Hirsute:
  New
Status in nvidia-graphics-drivers-470 source package in Hirsute:
  Won't Fix
Status in linux-restricted-modules source package in Impish:
  New
Status in nvidia-graphics-drivers-470 source package in Impish:
  New

Bug description:
  When Nvidia drivers are installing, they are only rebuilding the
  initramfs for the currently running kernel and/or the newest kernel
  when installed. Unfortunately, that means that if one has two kernel
  flavors installed (such as -generic and -lowlatency) this means that
  the initramfs is only getting rebuild for the currently installed
  kernel flavor and its newest version. When a user then switches to the
  other kernel flavor, their video fails because the kernel they
  switched to does not have the kernel module in the initramfs despite
  the kernel module being compiled and available.

  The root cause seems to be in nvidia-kernel-common-*.postinst and
  nvidia-dkms-*.postinst:

  # Update initramfs so that the blacklist ends up in the initramfs
  if [ -x /usr/sbin/update-initramfs ]; then
  /usr/sbin/update-initramfs -u

  if [ -n "$NEWEST_KERNEL" ] && [ ${CURRENT_KERNEL} != 
${NEWEST_KERNEL} ]; then
  # This can fail when dealing with a chroot see LP: #556653
  /usr/sbin/update-initramfs -u -k $CURRENT_KERNEL
  fi
  fi

  Instead of looking for the conditions to be met, this should be
  rebuilding for *all* installed kernels, despite the longer amount of
  time needed to do so in some cases. The rationale is that systems
  should work as expected and saving time, in this case, can cause that
  not to happen. As such the postinst scripts should do the following in
  lieu of the above:

  /usr/sbin/update-initramfs -u -k all

  This ensures that all installed kernel initramfs images get rebuilt,
  which adds increased safety at the expense of speed during the
  install. This will also prevent a race condition where, if a kernel
  and the nvidia driver are updated at the same time, that the proper
  initramfs image will exist despite which order the nvidia driver and
  kernel get installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.74-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-lowlatency 5.13.14
  Uname: Linux 5.13.0-19-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 13 13:12:23 2021
  InstallationDate: Installed on 2021-03-20 (206 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-06-13 (122 days ago)

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


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

[Kernel-packages] [Bug 1942999] Re: [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt dock

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  [SRU][H/OEM-5.13/OEM-5.14/U] Fix invalid MAC address after hotplug tbt
  dock

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux source package in Impish:
  Fix Released

Bug description:
  SRU justification:

  [Impact]
  igc driver can not connect to network after re-plugin thunderbolt dock when
  MAC passthrough enabled in BIOS.

  [Fix]
  Wait for the MAC copy of BIOS when enabled MAC passthrough.
  Intel engineer wants a different solution and promise to discuss with 
firmware engineer.
  Due to the schedule, made this as a short term solution to fix the issue, and 
wait for the other
  fix from Intel.

  [Test]
  Verified on hardware, after hotplug the thunderbolt cable,
  Ethernet works fine.

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

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


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

[Kernel-packages] [Bug 1941898] Re: ubuntu_kernel_selftests.ftrace timeout on H/riscv

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-riscv (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

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

Title:
  ubuntu_kernel_selftests.ftrace timeout on H/riscv

Status in ubuntu-kernel-tests:
  New
Status in linux-riscv package in Ubuntu:
  New
Status in linux-riscv source package in Hirsute:
  Won't Fix

Bug description:
  ubuntu_kernel_selftests.ftrace times out always after the same step
  when running on hirsute/linux-riscv on the regression tests
  infrastructure (QEMU VM).

  Log from the tests running with hirsute/linux-riscv 5.11.0-1018.19:

  18:02:56 INFO |   START   ubuntu_kernel_selftests.ftrace  
ubuntu_kernel_selftests.ftrace  timestamp=1629568976timeout=1800
localtime=Aug 21 18:02:56   
  18:02:56 DEBUG| Persistent state client._record_indent now set to 2
  18:02:56 DEBUG| Persistent state client.unexpected_reboot now set to 
('ubuntu_kernel_selftests.ftrace', 'ubuntu_kernel_selftests.ftrace')
  18:02:56 DEBUG| Waiting for pid 29328 for 1800 seconds
  18:02:56 WARNI| System python is too old, crash handling disabled
  18:02:56 DEBUG| Running 'sudo sh -c 'echo 1 > 
/proc/sys/net/ipv4/conf/all/accept_local''
  18:02:56 DEBUG| Running 'sudo make -C linux/tools/testing/selftests 
TARGETS=ftrace run_tests'
  18:02:57 DEBUG| [stdout] make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
  18:02:57 DEBUG| [stdout] make --no-builtin-rules ARCH=riscv -C ../../.. 
headers_install
  18:02:57 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  18:03:13 DEBUG| [stdout]   INSTALL ./usr/include
  18:03:14 DEBUG| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
  18:03:14 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  18:03:14 DEBUG| [stdout] make[1]: Nothing to be done for 'all'.
  18:03:14 DEBUG| [stdout] make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  18:03:15 DEBUG| [stdout] make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
  18:03:15 DEBUG| [stdout] TAP version 13
  18:03:15 DEBUG| [stdout] 1..1
  18:03:15 DEBUG| [stdout] # selftests: ftrace: ftracetest
  18:03:15 ERROR| [stderr] perl: warning: Setting locale failed.
  18:03:15 ERROR| [stderr] perl: warning: Please check that your locale 
settings:
  18:03:15 ERROR| [stderr]  LANGUAGE = (unset),
  18:03:15 ERROR| [stderr]  LC_ALL = (unset),
  18:03:15 ERROR| [stderr]  LC_CTYPE = "C.UTF-8",
  18:03:15 ERROR| [stderr]  LANG = "en_US.UTF-8"
  18:03:15 ERROR| [stderr] are supported and installed on your system.
  18:03:15 ERROR| [stderr] perl: warning: Falling back to the standard locale 
("C").
  18:03:16 DEBUG| [stdout] # === Ftrace unit tests ===
  18:03:21 DEBUG| [stdout] # [1] Basic trace file check [PASS]
  18:03:58 DEBUG| [stdout] # [2] Basic test for tracers [PASS]
  18:04:04 DEBUG| [stdout] # [3] Basic trace clock test [PASS]
  18:04:10 DEBUG| [stdout] # [4] Basic event tracing check  [PASS]
  18:04:16 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS]
  18:04:21 DEBUG| [stdout] # [6] Snapshot and tracing setting   [PASS]
  18:04:27 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS]
  18:04:32 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers   
[UNRESOLVED]
  18:04:33 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes   
[UNSUPPORTED]
  18:04:38 DEBUG| [stdout] # [10] Generic dynamic event - add/remove kprobe 
events  [FAIL]
  18:04:39 DEBUG| [stdout] # [11] Generic dynamic event - add/remove synthetic 
events   [UNSUPPORTED]
  18:04:39 DEBUG| [stdout] # [12] Generic dynamic event - selective clear 
(compatibility)   [UNSUPPORTED]
  18:04:40 DEBUG| [stdout] # [13] Generic dynamic event - generic clear event   
[UNSUPPORTED]
  18:04:46 DEBUG| [stdout] # [14] event tracing - enable/disable with event 
level files [PASS]
  18:04:54 DEBUG| [stdout] # [15] event tracing - restricts events based on pid 
notrace filtering   [PASS]
  18:05:00 DEBUG| [stdout] # [16] event tracing - restricts events based on pid 
[PASS]
  18:05:07 DEBUG| [stdout] # [17] event tracing - enable/disable with subsystem 
level files [PASS]
  18:05:14 DEBUG| [stdout] # [18] event tracing - enable/disable with top level 
files   [PASS]
  18:05:21 DEBUG| [stdout] # [19] Test trace_printk from module [PASS]
  18:05:39 DEBUG| [stdout] # [20] ftrace - function graph filters with stack 
tracer [PA

[Kernel-packages] [Bug 1940564] Re: Azure kernels fail to boot on some large Azure instance types

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Azure kernels fail to boot on some large Azure instance types

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-5.11 package in Ubuntu:
  Invalid
Status in linux-azure-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-5.11 source package in Bionic:
  Invalid
Status in linux-azure-5.4 source package in Bionic:
  Fix Released
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-azure-5.11 source package in Focal:
  Fix Released
Status in linux-azure-5.4 source package in Focal:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-azure source package in Hirsute:
  Fix Released
Status in linux-azure-5.11 source package in Hirsute:
  Invalid
Status in linux-azure-5.4 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-azure source package in Impish:
  Fix Released
Status in linux-azure-5.11 source package in Impish:
  Invalid
Status in linux-azure-5.4 source package in Impish:
  Invalid

Bug description:
  [Impact]

  Azure kernels fail to boot on large Azure instance types.

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1942347] Re: proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  proc01 from ubuntu_ltp.fs fails to read spl/hostid on s390x on Hirsute

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  Testcase proc01 from ubuntu_ltp.fs fails on Hirsute s390x systems
  with:

  12:48:34 DEBUG| [stdout] proc01  1  TFAIL  :  proc01.c:400: read
  failed: /proc/sys/kernel/spl/hostid: errno=EFAULT(14): Bad address

  I was also able to reproduce this on a amd64 VM running
  5.11.0-31-generic by loading the spl module and running:

  $ sudo cat /proc/sys/kernel/spl/hostid 
  cat: /proc/sys/kernel/spl/hostid: Bad address

  This is probably not a regression, affecting only s390x now likely
  because the spl module wasn't loaded on the previous runs. s390x
  systems are not re-deployed for the regression tests, so this could be
  a lingering module loaded for previous tests.

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


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

[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Groovy:
  Won't Fix
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz

  The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x:

  15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh
  15:45:23 DEBUG| [stdout] # PASS: policy routing
  15:45:23 DEBUG| [stdout] # PASS: route get
  15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired
  15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete
  15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy
  15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint
  15:45:29 DEBUG| [stdout] # PASS: gretap
  15:45:29 DEBUG| [stdout] # PASS: ip6gretap
  15:45:29 DEBUG| [stdout] # PASS: erspan
  15:45:29 DEBUG| [stdout] # PASS: ip6erspan
  15:45:30 DEBUG| [stdout] # PASS: bridge setup
  15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel
  15:45:31 DEBUG| [stdout] # PASS: set ifalias 
b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0
  15:45:31 DEBUG| [stdout] # PASS: vrf
  15:45:31 DEBUG| [stdout] # PASS: vxlan
  15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test
  15:45:31 DEBUG| [stdout] # PASS: macsec
  15:45:32 DEBUG| [stdout] # PASS: ipsec
  15:45:33 DEBUG| [stdout] # 3,7c3,7
  15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 
salt=0x64636261 crypt=1
  15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 
33343536
  15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x   
c0a87b03
  15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 
salt=0x64636261 crypt=1
  15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 
33343536
  15:45:33 DEBUG| [stdout] # ---
  15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 
salt=0x61626364 crypt=1
  15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 
36353433
  15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x   
037ba8c0
  15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 
salt=0x61626364 crypt=1
  15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 
36353433
  15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data
  15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload
  15:45:33 DEBUG| [stdout] # PASS: bridge fdb get
  15:45:33 DEBUG| [stdout] # PASS: neigh get
  15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1

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


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

[Kernel-packages] [Bug 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels
  (config not enabled)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux-kvm source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux-kvm source package in Groovy:
  New
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-kvm source package in Hirsute:
  Won't Fix

Bug description:
  This test failed because of the unsuccessful attempt to add a dummy device 
with ip link command:
  # devdummy="test-dummy0"
  # ip link add name "$devdummy" type dummy
  RTNETLINK answers: Operation not supported

  
   selftests: rtnetlink.sh
   
   RTNETLINK answers: Operation not supported
   Cannot find device "test-dummy0"
   FAIL: cannot add dummy interface
   not ok 1..10 selftests: rtnetlink.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 10:21:02 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Fix  Intel AC9560 BT function cannot turn on if BT turn off before S3
  entry

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
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:
  Fix Released
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]
  1. On Troy JSL platform, add AC9560
  2. Enter Settings -> Bluetooth menu
  3. Default Bluetooth option is ON, try to toggle the BT option to OFF
  4. Into suspend mode(S3) and resume the system
  5. Enter BT settings and try to turn on BT,
  6. BT function cannot enabled until reboot.

  [Fix]
  Turn off the msft ext only for AC9560.
  Maintainer thought Intel should take care this and reject this workaround.
  https://marc.info/?l=linux-bluetooth&m=162938546804458&w=2

  Intel is working on this issue and sru the workaround for the
  schedule.

  [Test]
  Verified with the bellow steps 10 times.
  1. On Troy JSL and add AC9560
  2. Turn off BT
  3. suspend&resume the machine 10 times.
  4. turn on BT and works well.

  [Regression Potential]
  Medium, it's a workaround to turn off the MSFT ext only for ac9560.

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


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

[Kernel-packages] [Bug 1947012] Re: ubuntu_kernel_selftests.net times out with hirsute/linux-realtime

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  ubuntu_kernel_selftests.net times out with hirsute/linux-realtime

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  ubuntu_kernel_selftests.net consistently times out with hirsute/linux-
  realtime.

  The last testcase which runs is usually fib_nexthops.sh, although
  there doesn't seem to be any problems with this particular testcase as
  looking at the log timestamp it is usually not running for too long
  when the timeout happens (this testcase takes around 10min to run on
  hirsute/linux).

  06:00:07 INFO | STARTubuntu_kernel_selftests.net
ubuntu_kernel_selftests.nettimestamp=1634018407timeout=1800
localtime=Oct 12 06:00:07
  [...]
  06:22:58 DEBUG| [stdout] # selftests: net: fib_nexthops.sh
  06:23:00 DEBUG| [stdout] # 
  06:23:00 DEBUG| [stdout] # Basic functional tests
  06:23:00 DEBUG| [stdout] # --
  06:23:00 DEBUG| [stdout] # TEST: List with nothing defined
 [ OK ]
  [...]
  06:28:52 DEBUG| [stdout] # IPv6 runtime torture
  06:28:52 DEBUG| [stdout] # 
  06:30:09 INFO | Timer expired (1800 sec.), nuking pid 30045
  06:30:10 INFO | ERRORubuntu_kernel_selftests.net
ubuntu_kernel_selftests.nettimestamp=1634020210localtime=Oct 12 
06:30:10Test timeout expired, rc=15

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


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

[Kernel-packages] [Bug 1831573] Re: Host arch executables are installed in /lib/modules/$(uname -r)/build when cross compiling kernel

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

Title:
  Host arch executables are installed in /lib/modules/$(uname -r)/build
  when cross compiling kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  When cross-compiling linux deb packages host arch binaries gets placed
  in target deb making it impossible to build kernel modules on target.
  I'm attaching linux-4.9 patches which solves this issue for us.

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


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

[Kernel-packages] [Bug 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels
  (config not enabled)

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-kvm source package in Bionic:
  New
Status in linux source package in Focal:
  New
Status in linux-kvm source package in Focal:
  New
Status in linux source package in Groovy:
  New
Status in linux-kvm source package in Groovy:
  New
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-kvm source package in Hirsute:
  Won't Fix

Bug description:
  This test failed because of the unsuccessful attempt to add a dummy device 
with ip link command:
  # devdummy="test-dummy0"
  # ip link add name "$devdummy" type dummy
  RTNETLINK answers: Operation not supported

  
   selftests: rtnetlink.sh
   
   RTNETLINK answers: Operation not supported
   Cannot find device "test-dummy0"
   FAIL: cannot add dummy interface
   not ok 1..10 selftests: rtnetlink.sh [FAIL]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
  ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
  Uname: Linux 4.15.0-1028-kvm x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Jan 17 10:21:02 2019
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1939035] Re: memory.usage_in_bytes from ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  memory.usage_in_bytes from
  ubuntu_ltp.controllers.memcg_subgroup_charge times out in Hirsute 5.11

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  memory.usage_in_bytes from
  ubuntu_ltp.controllers.memcg_subgroup_charge times out when running
  with hirsute/linux 5.11.

  startup='Mon Jul 19 15:17:41 2021'
  memcg_subgroup_charge 1 TINFO: timeout per run is 0h 5m 0s
  memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed
  memcg_subgroup_charge 1 TINFO: Test that group and subgroup have no 
relationship
  memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 270336
  memcg_subgroup_charge 1 TINFO: Warming up pid: 443417
  memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 443417
  memcg_subgroup_charge 1 TBROK: timed out on memory.usage_in_bytes
  memcg_subgroup_charge 1 TINFO: AppArmor enabled, this may affect test results
  memcg_subgroup_charge 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 
(requires super/root)
  memcg_subgroup_charge 1 TINFO: loaded AppArmor profiles: none
   
  Summary:
  passed   0
  failed   0
  broken   1
  skipped  0
  warnings 0
  tag=memcg_subgroup_charge stime=1626707861 dur=11 exit=exited stat=2 core=no 
cu=19 cs=12

  
  This is not a regression as it already failed on previous releases.

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


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

[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

** Changed in: linux-firmware (Ubuntu Hirsute)
   Status: Confirmed => Won't Fix

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

Title:
  Need support of Qualcomm WCN6856

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-firmware source package in Focal:
  Incomplete
Status in linux-oem-5.13 source package in Focal:
  Fix Released
Status in linux-oem-5.14 source package in Focal:
  Fix Released
Status in linux source package in Hirsute:
  Won't Fix
Status in linux-firmware source package in Hirsute:
  Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux-oem-5.14 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  Incomplete
Status in linux-firmware source package in Impish:
  Confirmed
Status in linux-oem-5.13 source package in Impish:
  Invalid
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Qualcomm WCN685x is not supported yet.

  [Fix]

  Qualcomm WCN685x support are mostly available in linux-next and mainline
  with one patch currently in kvalo/ath tree, and 3 additional in review.

  [Test Case]

  Test hardware connectivity, stability with basic checkbox tests:

$ lspci -nnk | grep Network -A 3
:02:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev
01)
  Subsystem: Foxconn International, Inc. Device [105b:e0b8]
  Kernel driver in use: ath11k_pci
  Kernel modules: ath11k_pci

  [Where problems could occur]

  While this introduces a new hardware, it might need further
  polishments.

  [Other Info]

  WCN685x WiFi 6E capability is still under development and is moved to
  next milestone for oem projects. Firmware blobs for both WiFi and
  Bluetooth are also needed and will be SRUed when a formal release is
  made.

  == original bug report ==

  Wireless Driver support: PCI\VEN_17CB&DEV_1103&SUBSYS_E0B8105B&REV_01
  BT driver support: USB\VID_0489&PID_E0C9&REV_0001

  Wireless Driver support: PCI\VEN_17CB&DEV_1103&REV_01
  BT driver support: USB\VID_0489&PID_E0CC&REV_0001

  
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
  Already landed to mainline kernel v5.14-rc1.

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


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

[Kernel-packages] [Bug 1938748] Re: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on F-oracle-5.4 / H-oracle-5.11 ARM64

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on
  F-oracle-5.4 / H-oracle-5.11 ARM64

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-oracle source package in Focal:
  New
Status in linux-oracle source package in Hirsute:
  Won't Fix

Bug description:
  Issue found on 5.11.0-1015.16~20.04.1 with instance
  VM.Standard.A1.Flex-4c.8m

==
FAIL: test_320_config_arm_pan (__main__.KernelSecurityConfigTest)
Ensure PAN for arm processors is set
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 2756, in test_320_config_arm_pan
self.assertKernelConfig(config_name, expected)
  File "./test-kernel-security.py", line 214, in assertKernelConfig
self.assertKernelConfigSet(name)
  File "./test-kernel-security.py", line 201, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: ARM64_SW_TTBR0_PAN option was expected to be set in the 
kernel config

--
Ran 125 tests in 26.030s

FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1938748/+subscriptions


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

[Kernel-packages] [Bug 1937133] Re: devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute (KeyError: 'flavour')

[Brian Murray]

The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.

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

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

Title:
  devlink_port_split from ubuntu_kernel_selftests.net fails on hirsute
  (KeyError: 'flavour')

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Hirsute:
  Won't Fix

Bug description:
  
  Failing on hirsute/linux 5.11.0-26.28  host s2lp4

  Not a regression as this is also failing on 5.11.0-24.25


  17:16:32 DEBUG| [stdout] # selftests: net: devlink_port_split.py
  17:16:32 DEBUG| [stdout] # Traceback (most recent call last):
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 283, in 
  17:16:32 DEBUG| [stdout] # main()
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 256, in main
  17:16:32 DEBUG| [stdout] # ports = devlink_ports(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 70, in __init__
  17:16:32 DEBUG| [stdout] # self.if_names = devlink_ports.get_if_names(dev)
  17:16:32 DEBUG| [stdout] #   File 
"/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py",
 line 64, in get_if_names
  17:16:32 DEBUG| [stdout] # if ports[port]['flavour'] == 'physical':
  17:16:32 DEBUG| [stdout] # KeyError: 'flavour'
  17:16:32 DEBUG| [stdout] not ok 44 selftests: net: devlink_port_split.py # 
exit=1

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


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