date:20220412

Hi Jeff,
  Although now we can load the module manually when install with ISO.
But it is impossible for infiniband PXE installation. Therefore if there has a 
method to load the module automatically during installation or the future 
release can add the module into modprobe list?

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

Title:
  The infiniband port can not display during ubuntu server 22.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  New

Bug description:
  1.Fresh install the ubuntu server 22.04 on Lenovo server with
  "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI
  Adapter" and "infiniband mode"

  2.The network port about infiniband(ibX) can not be found.

  3.The network port can be found after finish the installation.

  The other info:
  The network port(ib0/ib1) can be detected during RHEL 8.5 installation

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


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

[Kernel-packages] [Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation

Fail to run apport-collect, would you please check the sosreport
firstly?

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

Title:
  The infiniband port can not display during ubuntu server 22.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  New

Bug description:
  1.Fresh install the ubuntu server 22.04 on Lenovo server with
  "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI
  Adapter" and "infiniband mode"

  2.The network port about infiniband(ibX) can not be found.

  3.The network port can be found after finish the installation.

  The other info:
  The network port(ib0/ib1) can be detected during RHEL 8.5 installation

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


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

[Kernel-packages] [Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation

Sorry for the following inaccurate decription:
3.The network port can be found after finish the installation.
-->The IB device can not be seen directly after the installation, it still need 
install package "rdma-core" (The package can not be found in the ISO image, 
install it via command "apt install rdma-core"), after check the package , it 
will generate /etc/rdma/modules/infiniband.conf and the config file will load 
ib_ipoib automatically when OS boot.

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

Title:
  The infiniband port can not display during ubuntu server 22.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  New

Bug description:
  1.Fresh install the ubuntu server 22.04 on Lenovo server with
  "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI
  Adapter" and "infiniband mode"

  2.The network port about infiniband(ibX) can not be found.

  3.The network port can be found after finish the installation.

  The other info:
  The network port(ib0/ib1) can be detected during RHEL 8.5 installation

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


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

[Kernel-packages] [Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation

Hi Jeff,
  The IB device can be seen by installer subiquity after load ib_ipoib manually.

** Attachment added: "ib network port"
   
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1968716/+attachment/5580263/+files/infiniband.jpg

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

Title:
  The infiniband port can not display during ubuntu server 22.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  New

Bug description:
  1.Fresh install the ubuntu server 22.04 on Lenovo server with
  "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI
  Adapter" and "infiniband mode"

  2.The network port about infiniband(ibX) can not be found.

  3.The network port can be found after finish the installation.

  The other info:
  The network port(ib0/ib1) can be detected during RHEL 8.5 installation

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


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

[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic

2022-04-12 Thread Hui Wang

Will check jammy today. I remember Juerg and Vicamo did sth on jammy
several days ago.

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

Title:
  alsa/sdw: Fix the audio issue on a Dell machine without internal mic

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

Bug description:
  SRU template for linux-firmware
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current asoc driver
  can't work on this machine, the speaker and headset couldn't work.

  [Fix]
  Backport a tplg file which is specific to this mahcine

  [Test]
  Install the patched linux-firmware and boot the latest oem-5.14 kernel
  on the machine, check dmesg, it loads the correct tplg, and
  test speaker and headset, all work well.

  [Where problems could occur]
  This SRU is adding a new tplg file, it has no chance to introduce
  a regression.

  SRU template for linux
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current soc driver
  can't work on this machine, it will load a wrong tplg without this patch,
  and the speaker and headset couldn't work.

  [Fix]
  Backport one patch from upstream.

  [Test]
  Boot the patched kernel on the machine, check dmesg, it loads the
  correct tplg, and test speaker and headset, all work well.

  [Where problems could occur]
  If it could introduce regression, it will be on the sdw codec matching
  for adl machines, then it will make the driver load wrong tplg and make
  output device and input device not work anymore. But this possibility
  is very low, we already tested the patch on some dell adl machines, no
  regression found.

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


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

[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04

2022-04-12 Thread xiaochun Lee

Yes, We have a monitor that plugged into the VGA port. Sorry to let you
confused, the KVM console here means the XCC console, not a actual KVM
device. In this bug we reported, the VGA port connected monitor show
nothing, but XCC console can get the output data.

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

Title:
[Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal
(black screen) when install Ubuntu 22.04

Status in linux package in Ubuntu:
Confirmed

Bug description:
Description:
When we install Ubuntu 22.04, the physical VGA displayer show black screen.
It can only show rarely boot logs just for few seconds after kebyboard Enter
key be pressed to install Ubuntu OS, and then the physical VGA displayer keeps
black screen, but the XCC remote KVM monitor can show the boot log and the GUI
interface.

Produce Steps:
1. Connect a physical VGA displayer.
2. Fresh install Ubuntu22.04 on a server that integrated Matrox MGA
G200-family.
3. When the install menu comes out, press keyboard Enter key, the
physical VGA displayer just get the signal for few seconds and then the monitor
go to black screen.

Configuration:
Systems：Lenovo SR590, SR650, SR630 with magag200 as GFX
OS:jammy-live-server20220405-amd64.iso
CPU:Intel(R) Xeon(R) Bronze 3104 CPU @ 1.70GHz
UEFI:3.30 (Build ID: IVE178D)
XCC:1.30 (Build ID: PDL114N)
HDD:1.00TB 7.2K 6Gbps SATA 3.5" HD

Actual results:
The VGA display keep the black screen, during Ubuntu 22.04 installation.

Expected results:
The VGA display is OK when install the Ubuntu 22.04 in a server that
integrated Matrox MGA G200-family video processor

Additional info:
1. The issue can be reproduced 100% in the server that integrated
Matrox MGA G200-family platforms.
2. Both UEFI mode and legacy mode are failed.
3. After we finish installing Ubuntu OS through XCC remote KVM monitor,
and reboot the system, the physical VGA displayer still show nothing after a
few seconds.
4. We did more tests, modified the cmdline of the kernel, add
"nomodeset", the VGA displayer display well.
5. This issue could be found on both Intel and AMD platforms , which
have onboard video chip as mgag200, also called pilot 4.
6. Upstream kernel patch
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc1=147696720eca12ae48d020726208b9a61cdd80bc
(drm/mgag200: Select clock in PLL update functions) probalby resovle the issue
on BIOS legacy mode.

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

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

[Kernel-packages] [Bug 1968791] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580238/+files/Lsusb-v.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580244/+files/PulseList.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1968791/+attachment/5580246/+files/UdevDb.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580247/+files/WifiSyslog.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580241/+files/ProcEnviron.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580239/+files/ProcCpuinfo.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580242/+files/ProcInterrupts.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580243/+files/ProcModules.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1968791/+attachment/5580245/+files/RfKill.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580240/+files/ProcCpuinfoMinimal.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] acpidump.txt

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580248/+files/acpidump.txt

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

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] Lsusb-t.txt

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580237/+files/Lsusb-t.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1968791/+attachment/5580232/+files/CRDA.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580234/+files/IwConfig.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] Lspci-vt.txt

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580236/+files/Lspci-vt.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1968791/+attachment/5580235/+files/Lspci.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580233/+files/CurrentDmesg.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540SAA.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540SAA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: X
  dmi.product.name: X540SAA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Kernel-packages] [Bug 1968791] Re: Fan stopped after resume from sleep

apport information

** Tags added: apport-collected focal

** Description changed:

  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.21
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  cahimira   1008 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2022-02-05 (66 days ago)
+ InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
+  Bus 001 Device 005: ID 13d3:3423 IMC Networks 
+  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. X540SAA
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
+ RelatedPackageVersions:
+  linux-restricted-modules-5.13.0-39-generic N/A
+  linux-backports-modules-5.13.0-39-generic  N/A
+  linux-firmware 1.187.29
+ Tags:  focal
+ Uname: Linux 5.13.0-39-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/20/2017
+ dmi.bios.release: 5.6
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: X540SAA.304
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: X540SAA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540SAA.304:bd01/20/2017:br5.6:svnASUSTeKCOMPUTERINC.:pnX540SAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540SAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
+ dmi.product.family: X
+ dmi.product.name: X540SAA
+ dmi.product.sku: ASUS-NotebookSKU
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1968791/+attachment/5580231/+files/AlsaInfo.txt

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cahimira   1008 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2022-02-05 (66 days ago)
  InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 005: ID 13d3:3423 IMC Networks 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540SAA
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=7c0d36db-2ff4-4d64-9392-b992146b9fa3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.187.29
  Tags:  focal
  Uname: Linux 5.13.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/20/2017

[Kernel-packages] [Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04

Just to be clear, when you say "Physical" do you have an actual monitor
plugged into the VGA port, or are you using a KVM or remote KVM (not the
XCC console, but an actual KVM device).

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

Title:
[Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal
(black screen) when install Ubuntu 22.04

Status in linux package in Ubuntu:
Confirmed

Actual results:
The VGA display keep the black screen, during Ubuntu 22.04 installation.

Expected results:
The VGA display is OK when install the Ubuntu 22.04 in a server that
integrated Matrox MGA G200-family video processor

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

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

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

apport-collect 1968716

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

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

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

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

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

Title:
  The infiniband port can not display during ubuntu server 22.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  New

Bug description:
  1.Fresh install the ubuntu server 22.04 on Lenovo server with
  "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI
  Adapter" and "infiniband mode"

  2.The network port about infiniband(ibX) can not be found.

  3.The network port can be found after finish the installation.

  The other info:
  The network port(ib0/ib1) can be detected during RHEL 8.5 installation

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


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

[Kernel-packages] [Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation

Adding a kernel task, two possible issues:
1: installer env is missing a driver
2: if the driver is loaded, does subiquity see and manage the device?

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

Title:
  The infiniband port can not display during ubuntu server 22.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  New

Bug description:
  1.Fresh install the ubuntu server 22.04 on Lenovo server with
  "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI
  Adapter" and "infiniband mode"

  2.The network port about infiniband(ibX) can not be found.

  3.The network port can be found after finish the installation.

  The other info:
  The network port(ib0/ib1) can be detected during RHEL 8.5 installation

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


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

[Kernel-packages] [Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation

can you boot the installer, drop to a shell before starting install,
load ib_ipoib, and then does the installer see the IB device?

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

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

Title:
  The infiniband port can not display during ubuntu server 22.04
  installation

Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  New

Bug description:
  1.Fresh install the ubuntu server 22.04 on Lenovo server with
  "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI
  Adapter" and "infiniband mode"

  2.The network port about infiniband(ibX) can not be found.

  3.The network port can be found after finish the installation.

  The other info:
  The network port(ib0/ib1) can be detected during RHEL 8.5 installation

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


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

[Kernel-packages] [Bug 1968751] Re: Devlink wasn't enabled from common config

2022-04-12 Thread Luke Nowakowski-Krijger

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

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

Title:
  Devlink wasn't enabled from common config

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

Bug description:
  
  * Explain the feature

  A pull request was submitted for March SRU at:

  https://code.launchpad.net/~bodong-wang/ubuntu/+source/linux-
  bluefield/+git/version-seeds/+merge/416211

  However, CONFIG_NET_DEVLINK was mistakenly removed when merging. This
  breaks all switchdev configurations.

   
  * How to test

  Any devlink command, e.g:
  # devlink dev eswitch show pci/:03:00.0

  * What it could break
  N/A

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


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

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

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

apport-collect 1968791

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

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

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

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

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2

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


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

[Kernel-packages] [Bug 1968791] [NEW] Fan stopped after resume from sleep

Public bug reported:

Fan never works again when the OS resume from sleep to RAM.
It happens only if the PC is running without AC.
When the PC is running with AC, all works fine.
---
Kernel: 5.13.0-39-generic
Ubuntu version: 20.04.4
Driver: intel_cpufreq
Motherboard: ASUS

Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
pwm1 <--- value: -1
pwm1_enable <--- value: 2

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

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

Title:
  Fan stopped after resume from sleep

Status in linux package in Ubuntu:
  New

Bug description:
  Fan never works again when the OS resume from sleep to RAM.
  It happens only if the PC is running without AC.
  When the PC is running with AC, all works fine.
  ---
  Kernel: 5.13.0-39-generic
  Ubuntu version: 20.04.4
  Driver: intel_cpufreq
  Motherboard: ASUS
  
  Files in "/sys/devices/platform/asus-nb-wmi/hwmon/hwmon5/":
  pwm1 <--- value: -1
  pwm1_enable <--- value: 2

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


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

[Kernel-packages] [Bug 1968749] Re: focal/linux-azure: Enable missing config options

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

Title:
focal/linux-azure: Enable missing config options

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

Bug description:
SRU Justification

[Impact]

focal/linux-azure is missing a number of config options compared to
impish/linux-azure. This kernel is also missing 2 patches that
significantly impact network performance.

From Microsoft:
We tested this kernel. The P0P1 test cases are finished. Below are we found.
P2 test cases are still running. I will update you when they are finished.

1. From dmesg, we can see following lines. Could you check why it has these
messages and if the messages impact the system?
[3.341802] squashfs: SQUASHFS error: Xattrs in filesystem, these will be
ignored
[3.346056] unable to read xattr id index table

2. The kernel hasn't backport Michael's SRIOV performance improvement
patches. The network performance is not expected.
Here are the patches:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=37200078ed6aa2ac3c88a01a64996133dccfdd34

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=8d21732475c637c7efcdb91dc927a4c594e97898

3. It is failed to create raid 0 using below command.
# mdadm --create /dev/md0 --level 0 --raid-devices 16
/dev/sd[abcdghijklmnopqr][1-5]
mdadm: Defaulting to version 1.2 metadata
mdadm: RUN_ARRAY failed: Invalid argument

From dmesg, it has following lines:
[ 235.830712] md: personality for level 0 is not loaded!
[ 235.830733] md: md0 stopped.

I see many raid related configuration is not set. Could you check the raid
related and other configuration?
# cat /boot/config-5.4.0-1076-azure | grep RAID
CONFIG_RAID_ATTRS=m
# CONFIG_BLK_DEV_3W__RAID is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_MEGARAID_SAS=y
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_DM_RAID is not set
CONFIG_BCM_SBA_RAID=m
CONFIG_DMA_ENGINE_RAID=y
CONFIG_RAID6_PQ=m
CONFIG_RAID6_PQ_BENCHMARK=y

[Test Case]

Microsoft tested

[Where things could go wrong]

There should be little chance of regression given that these are
config options.

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

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

2022-04-12 Thread dann frazier

Any objection to dropping flash-kernel from ARM cloud images starting w/
jammy+1?

-- 
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/master/functions#L787
  [8]

[Kernel-packages] [Bug 1968751] Re: Devlink wasn't enabled from common config

2022-04-12 Thread Luke Nowakowski-Krijger

** Also affects: linux-bluefield (Ubuntu Focal)
   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/1968751

Title:
  Devlink wasn't enabled from common config

Status in linux-bluefield package in Ubuntu:
  New
Status in linux-bluefield source package in Focal:
  New

Bug description:
  
  * Explain the feature

  A pull request was submitted for March SRU at:

  https://code.launchpad.net/~bodong-wang/ubuntu/+source/linux-
  bluefield/+git/version-seeds/+merge/416211

  However, CONFIG_NET_DEVLINK was mistakenly removed when merging. This
  breaks all switchdev configurations.

   
  * How to test

  Any devlink command, e.g:
  # devlink dev eswitch show pci/:03:00.0

  * What it could break
  N/A

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


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

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

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

apport-collect 1968774

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

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

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

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

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

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

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

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

Title:
  LRMv6: add multi-architecture support

Status in linux package in Ubuntu:
  Incomplete
Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-restricted-modules source package in Focal:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux-restricted-modules source package in Impish:
  New

Bug description:
  Add multi-architecture support to LRM. This allows nvidia-graphics-
  drivers to offer architecture combinations via kernel-versions and for
  individual LRM packages to opt-in to those architectures on a per
  flavour basis.

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


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

[Kernel-packages] [Bug 1968774] Re: LRMv6: add multi-architecture support

2022-04-12 Thread Andy Whitcroft

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

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

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

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

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

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

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

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

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

Title:
  LRMv6: add multi-architecture support

Status in linux package in Ubuntu:
  Incomplete
Status in linux-restricted-modules package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Incomplete
Status in linux-restricted-modules source package in Bionic:
  New
Status in linux source package in Focal:
  Incomplete
Status in linux-restricted-modules source package in Focal:
  New
Status in linux source package in Impish:
  Incomplete
Status in linux-restricted-modules source package in Impish:
  New

Bug description:
  Add multi-architecture support to LRM. This allows nvidia-graphics-
  drivers to offer architecture combinations via kernel-versions and for
  individual LRM packages to opt-in to those architectures on a per
  flavour basis.

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


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

[Kernel-packages] [Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04

** Changed in: linux (Ubuntu Jammy)
 Assignee: Jeff Lane (bladernr) => Michael Reed (mreed8855)

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

Title:
  Include DPC Fixes in Ubuntu 22.04 and 20.04

Status in dellserver:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]
  Recovery from DownPort Containment events fail and the NVMe endpoint is not 
accessible in some scenarios.

  [Fix]

  These are some of the DPC fixes which help in handling some of the
  failure cases of DownPort Containment events.

  Upstream kernel patches to be included into Ubuntu 22.04 and into
  Ubuntu 20.04.5:

  Already in Jammy as of Ubuntu-5.15.0-1.1
  PCI/portdrv: Enable Bandwidth Notification only if port supports it
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4

  Not yet pulled
  PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884

  [Test Case]

  [Other Info]
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241

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


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

[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

2022-04-12 Thread Lucas Kanashiro

@family-gan are you saying this is an issue in Ubuntu Impish (21.10)? It
seems to be already fixed in supported releases. Could you share any
steps to reproduce it? If you consider the issue you are facing
different than the one discussed in this bug please consider filing a
separate bug.

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

Title:
  SSH fails with connection timed out - in VPN and hangs here "expecting
  SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS

Status in linux package in Ubuntu:
  Invalid
Status in openconnect package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Invalid
Status in openconnect source package in Xenial:
  Confirmed

Bug description:
  Hello Team,

  SSH timeout issue, once connect to VPN.

  Environment

  ==
  Dell XPS 9570 
  Ubuntu 16.04.6 Xenial Xerus)
  kernel - 4.15.0-55-generic

  $dpkg -l | grep -i openssh
  ii  openssh-client 1:7.2p2-4ubuntu2.8  --> 
  ii  openssh-server 1:7.2p2-4ubuntu2.8  
  ii  openssh-sftp-server  1:7.2p2-4ubuntu2.8

  
  VPN tunnel info 
  
  vpn0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:IP  P-t-P:xx  Mask:255.255.252.0
inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1406  Metric:1
RX packets:962 errors:0 dropped:0 overruns:0 frame:0
TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:87839 (87.8 KB)  TX bytes:238740 (238.7 KB)

  Issue
  
  Unable to connect to any host via ssh or sftp after VPN connection 

  Tried 
  =

  Reinstalled the openssh-client package and still no luck. May I know
  why the default cipher is not taking/hanging? Please let me know .
  There were no recent changes.

  
  Workaround
  ===
  Able to connect to ssh / sftp $ssh -c aes128-ctr   user@IP

  
  Below is the debug ssh client logs ===
  ==

  $ssh -vvv  user@ip
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug2: resolving "IP" port 22
  debug2: ssh_connect_direct: needpriv 0
  debug1: Connecting to IP [IP] port 22.
  debug1: Connection established.
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_rsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_dsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519 type -1
  debug1: key_load_public: No such file or directory
  debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
  debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 
Ubuntu-4ubuntu0.3
  debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to IP:22 as 'user'
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
  debug2: host key algorithms: 
ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ssh-ed25519-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
  debug2: MACs ctos:

[Kernel-packages] [Bug 1968774] [NEW] LRMv6: add multi-architecture support

2022-04-12 Thread Andy Whitcroft

Public bug reported:

Add multi-architecture support to LRM. This allows nvidia-graphics-
drivers to offer architecture combinations via kernel-versions and for
individual LRM packages to opt-in to those architectures on a per
flavour basis.

** Affects: linux-restricted-modules (Ubuntu)
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

** Changed in: linux-restricted-modules (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  LRMv6: add multi-architecture support

Status in linux-restricted-modules package in Ubuntu:
  In Progress

Bug description:
  Add multi-architecture support to LRM. This allows nvidia-graphics-
  drivers to offer architecture combinations via kernel-versions and for
  individual LRM packages to opt-in to those architectures on a per
  flavour basis.

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


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

[Kernel-packages] [Bug 1968771] [NEW] Impish update: upstream stable patchset 2022-04-12

2022-04-12 Thread 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-04-12

Ported from the following upstream stable releases:
v5.10.103, v5.15.26

   from git://git.kernel.org/

cgroup/cpuset: Fix a race between cpuset_attach() and cpu hotplug
btrfs: tree-checker: check item_size for inode_item
btrfs: tree-checker: check item_size for dev_item
clk: jz4725b: fix mmc0 clock gating
vhost/vsock: don't check owner in vhost_vsock_stop() while releasing
parisc/unaligned: Fix fldd and fstd unaligned handlers on 32-bit kernel
parisc/unaligned: Fix ldw() and stw() unalignment handlers
KVM: x86/mmu: make apf token non-zero to fix bug
drm/amdgpu: disable MMHUB PG for Picasso
drm/i915: Correctly populate use_sagv_wm for all pipes
sr9700: sanity check for packet length
USB: zaurus: support another broken Zaurus
CDC-NCM: avoid overflow in sanity checking
x86/fpu: Correct pkru/xstate inconsistency
tee: export teedev_open() and teedev_close_context()
optee: use driver internal tee_context for some rpc
ping: remove pr_err from ping_lookup
perf data: Fix double free in perf_session__delete()
bnx2x: fix driver load from initrd
bnxt_en: Fix active FEC reporting to ethtool
hwmon: Handle failure to register sensor with thermal zone correctly
bpf: Do not try bpf_msg_push_data with len 0
selftests: bpf: Check bpf_msg_push_data return value
bpf: Add schedule points in batch ops
io_uring: add a schedule point in io_add_buffers()
net: __pskb_pull_tail() & pskb_carve_frag_list() drop_monitor friends
tipc: Fix end of loop tests for list_for_each_entry()
gso: do not skip outer ip header in case of ipip and net_failover
openvswitch: Fix setting ipv6 fields causing hw csum failure
drm/edid: Always set RGB444
net/mlx5e: Fix wrong return value on ioctl EEPROM query failure
net/sched: act_ct: Fix flow table lookup after ct clear or switching zones
net: ll_temac: check the return value of devm_kmalloc()
net: Force inlining of checksum functions in net/checksum.h
nfp: flower: Fix a potential leak in nfp_tunnel_add_shared_mac()
netfilter: nf_tables: fix memory leak during stateful obj update
net/smc: Use a mutex for locking "struct smc_pnettable"
surface: surface3_power: Fix battery readings on batteries without a serial 
number
udp_tunnel: Fix end of loop test in udp_tunnel_nic_unregister()
net/mlx5: Fix possible deadlock on rule deletion
net/mlx5: Fix wrong limitation of metadata match on ecpf
net/mlx5e: kTLS, Use CHECKSUM_UNNECESSARY for device-offloaded packets
spi: spi-zynq-qspi: Fix a NULL pointer dereference in zynq_qspi_exec_mem_op()
regmap-irq: Update interrupt clear register for proper reset
RDMA/rtrs-clt: Fix possible double free in error case
RDMA/rtrs-clt: Move free_permit from free_clt to rtrs_clt_close
configfs: fix a race in configfs_{,un}register_subsystem()
RDMA/ib_srp: Fix a deadlock
tracing: Have traceon and traceoff trigger honor the instance
iio: adc: men_z188_adc: Fix a resource leak in an error handling path
iio: adc: ad7124: fix mask used for setting AIN_BUFP & AIN_BUFM bits
iio: imu: st_lsm6dsx: wait for settling time in st_lsm6dsx_read_oneshot
iio: Fix error handling for PM
sc16is7xx: Fix for incorrect data being transmitted
ata: pata_hpt37x: disable primary channel on HPT371
Revert "USB: serial: ch341: add new Product ID for CH341A"
usb: gadget: rndis: add spinlock for rndis response list
tracefs: Set the group ownership in apply_options() not parse_options()
USB: serial: option: add support for DW5829e
USB: serial: option: add Telit LE910R1 compositions
usb: dwc3: pci: Fix Bay Trail phy GPIO mappings
usb: dwc3: gadget: Let the interrupt handler disable bottom halves.
xhci: re-initialize the HC during resume if HCE was set
xhci: Prevent futile URB re-submissions due to incorrect return value.
driver core: Free DMA range map when device is released
RDMA/cma: Do not change route.addr.src_addr outside state checks
thermal: int340x: fix memory leak in int3400_notify()
riscv: fix oops caused by irqsoff latency tracer
tty: n_gsm: fix encoding of control signal octet bit DV
tty: n_gsm: fix proper link termination after failed open
tty: n_gsm: fix NULL pointer access due to DLCI release
tty: n_gsm: fix wrong tty control line for flow control
tty: n_gsm: fix deadlock in gsmtty_open()
gpio: tegra186: Fix chip_data type confusion
memblock: use kfree() to release kmalloced memblock regions
mm/filemap: Fix handling of THPs in generic_file_buffered_read()
cgroup-v1: Correct privileges check in release_agent writes
selinux: fix misuse of mutex_is_locked()

[Kernel-packages] [Bug 1968387] Re: ubuntu-fan fails to set https_proxy when running the "docker" dep8 test on autopkgtest.u.c

2022-04-12 Thread Launchpad Bug Tracker

This bug was fixed in the package ubuntu-fan - 0.12.16

---
ubuntu-fan (0.12.16) jammy; urgency=medium

  * d/t/docker: Don't use "https://; for $https_proxy.  Set
HTTPS_PROXY for docker.service as well. (LP: #1968387)

 -- Sergio Durigan Junior   Fri, 08 Apr
2022 21:02:22 -0400

** Changed in: ubuntu-fan (Ubuntu Jammy)
   Status: In Progress => Fix Released

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

Title:
  ubuntu-fan fails to set https_proxy when running the "docker" dep8
  test on autopkgtest.u.c

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Focal:
  In Progress
Status in ubuntu-fan source package in Impish:
  In Progress
Status in ubuntu-fan source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  ubuntu-fan currently fails to properly set the $https_proxy variable
  when running the "docker" dep8 test on autopkgtest.u.c.

  At the time of this writing this is a major problem on Focal because
  ubuntu-fan is blocking docker.io from migrating:

  Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: 
request canceled while waiting for connection (Client.Timeout exceeded while 
awaiting headers)
  FAIL: error on docker test
  local docker test: docker pull ubuntu failure!
  local docker test: skipping test.
  autopkgtest [03:44:06]: test docker: ---]
  autopkgtest [03:44:06]: test docker:  - - - - - - - - - - results - - - - - - 
- - - -
  docker   FAIL non-zero exit status 1

  [Test Plan]

  The dep8 test (named "docker") shall pass when performed in the
  autopkgtest.u.c. infra.

  [Where problems could occur]

  This is a very specific issue on how a dep8 test from the package
  interacts with autopkgtest.u.c, so there is really no way that a
  regression can be caused by fixing this problem.

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


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

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

2022-04-12 Thread Julian Andres Klode

** No longer affects: grub2-unsigned (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/1967562

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

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


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

[Kernel-packages] [Bug 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC

2022-04-12 Thread Zachary Tahenakos

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

Title:
  [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
  causes Bus Fatal Error when rebooting system with BCM5720 NIC

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

Bug description:
  SRU Justification:

  [IMPACT]

  This is being reported by a hardware partner as it is being noticed a
  lot both in their internal testing teams and also being reported with
  some frequency by customers who are seeing these messages in their
  logs and thus it is generating an unusualy high volume of support
  calls from the field.

  In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
  upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
  Upstream, these errors were discovered and that patch was reverted
  (see Fix Below).  We carry the revert commit in all subsequent Focal
  HWE kernels starting at 5.12, but the fix was never pulled back into
  Focal 5.4.

  according to the hardware partner:

  the following error messages are observed when rebooting a machine
  that uses the BCM5720 chipset, which is a widely used 1GbE controller
  found on LOMs and OCP NICs as well as many PCIe NIC models.

  [  146.429212] shutdown[1]: Rebooting.
  [  146.435151] kvm: exiting hardware virtualization
  [  146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is 
called outbound_intr_mask:0x4009
  [  148.088133] [qede_unload:2236(eno12409)]Link is down
  [  148.183618] qede :31:00.1: Ending qede_remove successfully
  [  148.518541] [qede_unload:2236(eno12399)]Link is down
  [  148.625066] qede :31:00.0: Ending qede_remove successfully
  [  148.762067] ACPI: Preparing to enter system sleep state S5
  [  148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 5
  [  148.803731] {1}[Hardware Error]: event severity: recoverable
  [  148.810191] {1}[Hardware Error]:  Error 0, type: fatal
  [  148.816088] {1}[Hardware Error]:   section_type: PCIe error
  [  148.822391] {1}[Hardware Error]:   port_type: 0, PCIe end point
  [  148.829026] {1}[Hardware Error]:   version: 3.0
  [  148.834266] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
  [  148.841140] {1}[Hardware Error]:   device_id: :04:00.0
  [  148.847309] {1}[Hardware Error]:   slot: 0
  [  148.852077] {1}[Hardware Error]:   secondary_bus: 0x00
  [  148.857876] {1}[Hardware Error]:   vendor_id: 0x14e4, device_id: 0x165f
  [  148.865145] {1}[Hardware Error]:   class_code: 02
  [  148.870845] {1}[Hardware Error]:   aer_uncor_status: 0x0010, 
aer_uncor_mask: 0x0001
  [  148.879842] {1}[Hardware Error]:   aer_uncor_severity: 0x000ef030
  [  148.886575] {1}[Hardware Error]:   TLP Header: 4001 030f 90028090 

  [  148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask: 
0x0001
  [  148.902795] tg3 :04:00.0: AER:[20] UnsupReq   (First)
  [  148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer, 
aer_agent=Requester ID
  [  148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
  [  148.925558] tg3 :04:00.0: AER:   TLP Header: 4001 030f 
90028090 
  [  148.933984] reboot: Restarting system
  [  148.938319] reboot: machine restart

  The hardware partner did some bisection and observed the following:

  Kernel  version   Fatal Error
  5.4.0-42.46   No
  5.4.0-45.49   No
  5.4.0-47.51   No
  5.4.0-48.52   No
  5.4.0-51.56   No
  5.4.0-52.57   No
  5.4.0-53.59   No
  5.4.0-54.60   No
  5.4.0-58.64   No
  5.4.0-59.65   yes
  5.4.0-60.67   yes

  [FIX]
  The fix is to apply this patch from upstream:

  commit 9d3fcb28f9b9750b474811a2964ce022df56336e
  Author: Josef Bacik 
  Date:   Tue Mar 16 22:17:48 2021 -0400

  Revert "PM: ACPI: reboot: Use S5 for reboot"

  This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.

  This patch causes a panic when rebooting my Dell Poweredge r440.  I do
  not have the full panic log as it's lost at that stage of the reboot and
  I do not have a serial console.  Reverting this patch makes my system
  able to reboot again.

  Example:
  
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471

  The hardware partner has preemptively pulled our 5.4 tree, applied the
  fix and tested it in their labs and determined that this does resolve
  the issue.

  [TEST CASE]
  Install the patched kernel on a machine that uses a BCM5720 LOM and reboot 
the machine and see that the errors no longer appear.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

2022-04-12 Thread Brian Murray

** Tags added: rls-jj-incoming

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

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in grub2 source package in Impish:
  New
Status in linux source package in Impish:
  Invalid
Status in grub2 source package in Jammy:
  New
Status in linux source package in Jammy:
  Invalid

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release:

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

2022-04-12 Thread Heinrich Schuchardt

On riscv64 we cannot boot without the LoadFile2 protocol. So the short
term fix of forcing to 0 must be architecture specific. Check for
__riscv not defined.

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

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

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


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

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

2022-04-12 Thread Heinrich Schuchardt

** Tags added: fr-2245

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

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

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


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

[Kernel-packages] [Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS

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

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

Title:
  NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup
  failed if SR-IOV is disabled in BIOS

Status in dellserver:
  Won't Fix
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory 
space for GPUs.
  Multiple error messages in kernel.log file.

  Summary:
  * Dell prefers to set SRIOV to disabled in bios globally
  * This bug does not occur IF:
  SRIOV is enabled in BIOS OR
  "pci=realloc=off" is passed to the kernel at boot time
  * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not 
affect systems with NVIDIA A100-40GB GPUs

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


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

[Kernel-packages] [Bug 1968749] Re: focal/linux-azure: Enable missing config options

** Description changed:

SRU Justification

[Impact]

focal/linux-azure is missing a number of config options compared to
- impish/linux-azure.
+ impish/linux-azure. This kernel is also missing 2 patches that
+ significantly impact network performance.

From Microsoft:
We tested this kernel. The P0P1 test cases are finished. Below are we found.
P2 test cases are still running. I will update you when they are finished.

2. The kernel hasn't backport Michael's SRIOV performance improvement
patches. The network performance is not expected.
Here are the patches:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=37200078ed6aa2ac3c88a01a64996133dccfdd34

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=8d21732475c637c7efcdb91dc927a4c594e97898

From dmesg, it has following lines:
[ 235.830712] md: personality for level 0 is not loaded!
[ 235.830733] md: md0 stopped.

[Test Case]

Microsoft tested

[Where things could go wrong]

There should be little chance of regression given that these are config
options.

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

Title:
focal/linux-azure: Enable missing config options

Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Focal:
In Progress

Bug description:
SRU Justification

[Impact]

focal/linux-azure is missing a number of config options compared to
impish/linux-azure. This kernel is also missing 2 patches that
significantly impact network performance.

From Microsoft:
We tested this kernel. The P0P1 test cases are finished. Below are we found.
P2 test cases are still running. I will update you when they are finished.

2. The kernel hasn't backport Michael's SRIOV performance improvement
patches. The network performance is not expected.
Here are the patches:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=37200078ed6aa2ac3c88a01a64996133dccfdd34

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=8d21732475c637c7efcdb91dc927a4c594e97898

From dmesg, it has following lines:
[ 235.830712] md: personality for level 0 is not loaded!
[ 235.830733] md: md0 stopped.

[Test Case]

Microsoft tested

[Where things could go wrong]

There should be little chance of regression given that these are
config options.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

2022-04-12 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1967562

** Tags added: iso-testing

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

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

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


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

[Kernel-packages] [Bug 1966841] Re: alsa/sdw: Fix the audio issue on a Dell machine without internal mic

2022-04-12 Thread Timo Aaltonen

I don't see the tplg file in jammy yet?

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

Title:
  alsa/sdw: Fix the audio issue on a Dell machine without internal mic

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

Bug description:
  SRU template for linux-firmware
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current asoc driver
  can't work on this machine, the speaker and headset couldn't work.

  [Fix]
  Backport a tplg file which is specific to this mahcine

  [Test]
  Install the patched linux-firmware and boot the latest oem-5.14 kernel
  on the machine, check dmesg, it loads the correct tplg, and
  test speaker and headset, all work well.

  [Where problems could occur]
  This SRU is adding a new tplg file, it has no chance to introduce
  a regression.

  SRU template for linux
  [Impact]
  we have a Dell ADL laptop which has sdw audio, but there is no camera
  and no internal digital mic in this machine, the current soc driver
  can't work on this machine, it will load a wrong tplg without this patch,
  and the speaker and headset couldn't work.

  [Fix]
  Backport one patch from upstream.

  [Test]
  Boot the patched kernel on the machine, check dmesg, it loads the
  correct tplg, and test speaker and headset, all work well.

  [Where problems could occur]
  If it could introduce regression, it will be on the sdw codec matching
  for adl machines, then it will make the driver load wrong tplg and make
  output device and input device not work anymore. But this possibility
  is very low, we already tested the patch on some dell adl machines, no
  regression found.

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


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

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

2022-04-12 Thread Dimitri John Ledkov

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

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2 (Ubuntu)
Milestone: None => ubuntu-22.04

** Changed in: grub2-signed (Ubuntu)
Milestone: None => ubuntu-22.04

** Changed in: grub2-unsigned (Ubuntu)
Milestone: None => ubuntu-22.04

** Tags added: rls-jj-incoming

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

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

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


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

[Kernel-packages] [Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

2022-04-12 Thread Taihsiang Ho

Since it seems a grub issue, I reported the issue to qatracker of daily
build to make the release team aware of this issue, and hopefully the
information will be helpful before releasing RC.

http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246802/testcases/1697/results

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

Title:
  jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade

Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in grub2-unsigned package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in subiquity package in Ubuntu:
  Invalid

Bug description:
  = Description =
  Platforms: Ampere Mt. Jade Altra (bizzy), Cavium thunderX crb2s (recht)
  Image: Jammy Beta (220330)

  I setup my pxe server to provision jammy beta and got the following
  kernel panic message after grub stage:

  log from console log

  [1.176614] integrity: Couldn't parse dbx signatures: -74^M
  [1.371630] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)^M
  [1.379891] CPU: 42 PID: 1 Comm: swapper/0 Not tainted 5.15.0-23-generic 
#23-Ubuntu^M
  [1.387535] Hardware name: WIWYNN Mt.Jade Server System 
B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 
2021/05/26^M
  [1.400215] Call trace:^M
  [1.402649]  dump_backtrace+0x0/0x1ec^M
  [1.406310]  show_stack+0x24/0x30^M
  [1.409614]  dump_stack_lvl+0x68/0x84^M
  [1.413271]  dump_stack+0x18/0x34^M
  [1.416573]  panic+0x18c/0x39c^M
  [1.419616]  mount_block_root+0x160/0x210^M
  [1.423622]  mount_root+0x12c/0x14c^M
  [1.427097]  prepare_namespace+0x140/0x1a0^M
  [1.431182]  kernel_init_freeable+0x1c8/0x214^M
  [1.435527]  kernel_init+0x30/0x160^M
  [1.439006]  ret_from_fork+0x10/0x20^M
  [1.442573] SMP: stopping secondary CPUs^M
  [1.447323] Kernel Offset: 0x55263ee9 from 0x8800^M
  [1.453404] PHYS_OFFSET: 0x8000^M
  [1.456879] CPU features: 0x85c1,a3302e42^M
  [1.461225] Memory Limit: none^M
  [1.464271] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0) ]---^M

  = Steps to Reproduce =
  1. Followed this guide to setup the pxe server 
https://discourse.ubuntu.com/t/netbooting-the-live-server-installer-via-uefi-pxe-on-arm-aarch64-arm64-and-x86-64-amd64/19240
 with the jammy beta image (220330) 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso
  1-1. You may use this script to perform the set-up 
https://github.com/tai271828/ubuntu-autoinstall-pxe-server by invoking: `sudo 
./setup-pxe-server.sh --url 
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-live-server-arm64.iso`
  2. Boot the system via PXE
  3. Select Ubuntu at Grub menu

  = Expected Result =
  The image is loaded to the system locally via PXE, and subiquity is launched

  = Actual Result =
  Console log simply shows nothing for 10 seconds and then the kernel panic 
shows up.

  = Additional Information =
  - If we install via the virtual CD of the server, subiquity could be launched 
and the installation process completes successfully.
  - MAAS could deploy Jammy to the Mt. Jade server as well.

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


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

[Kernel-packages] [Bug 1968751] [NEW] Devlink wasn't enabled from common config

2022-04-12 Thread Bodong Wang

Public bug reported:


* Explain the feature

A pull request was submitted for March SRU at:

https://code.launchpad.net/~bodong-wang/ubuntu/+source/linux-
bluefield/+git/version-seeds/+merge/416211

However, CONFIG_NET_DEVLINK was mistakenly removed when merging. This
breaks all switchdev configurations.

 
* How to test

Any devlink command, e.g:
# devlink dev eswitch show pci/:03:00.0

* What it could break
N/A

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

Title:
  Devlink wasn't enabled from common config

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  
  * Explain the feature

  A pull request was submitted for March SRU at:

  https://code.launchpad.net/~bodong-wang/ubuntu/+source/linux-
  bluefield/+git/version-seeds/+merge/416211

  However, CONFIG_NET_DEVLINK was mistakenly removed when merging. This
  breaks all switchdev configurations.

   
  * How to test

  Any devlink command, e.g:
  # devlink dev eswitch show pci/:03:00.0

  * What it could break
  N/A

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


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

[Kernel-packages] [Bug 1967924] Re: One overlayfs fix has not been backported to the 5.13 branch

2022-04-12 Thread Andrew Vagin

Any update?

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

Title:
  One overlayfs fix has not been backported to the 5.13 branch

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  The next patch has not been ported to the the 5.13 branch:

  $ git show Ubuntu-azure-5.8-5.8.0-1033.35_20.04.1~656
  commit 5f5716d1f7ece06c66d7d8145dd6b3a5886b3e56
  Author: Alexander Mikhalitsyn 
  Date:   Mon Apr 26 10:11:00 2021 +0200

  UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from 
map_files
  
  BugLink: https://bugs.launchpad.net/bugs/1857257

  ...

  Fixes: d24b8a5 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
  underlay")

  
  But it isn't in the 5.13 branch:

  $ git log --pretty=oneline origin/azure-5.13-next fs/overlayfs/file.c 
  1e6145d8708c831d2aa5c26aa15eb98e1a1683b9 ovl: fix use after free in struct 
ovl_aio_req
  7b5bda27d1fc4d7bde20cf6ed203fe88c458169a ovl: fix IOCB_DIRECT if underlying 
fs doesn't support direct IO
  1626e7f7ab7eb74e142fec7fe6b7c9614972a56b ovl: fix deadlock in splice write
  1443bc4a25ca84d60d39a8ae1dc6215abdd637a4 UBUNTU: SAUCE: overlayfs: allow with 
shiftfs as underlay

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


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

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

2022-04-12 Thread Louis Bouchard

** Also affects: grub2 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

** Also affects: grub2 (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid
Status in grub2 source package in Impish:
  New
Status in linux source package in Impish:
  Invalid
Status in grub2 source package in Jammy:
  New
Status in linux source package in Jammy:
  Invalid

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19

[Kernel-packages] [Bug 1967130] Re: rcu_sched detected stalls on CPUs/tasks

2022-04-12 Thread Dimitri John Ledkov

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

** Changed in: linux-riscv (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  rcu_sched detected stalls on CPUs/tasks

Status in linux-riscv package in Ubuntu:
  Fix Committed

Bug description:
  When running the riscv64 live installer
  (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-
  live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly
  see rcu_sched stalls related to accessing the UEFI runtime:

  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched 
detected stalls on CPUs/tasks:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu:   3-...0: (3 
GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, 
t=15002 jiffies, g=155853, q=1286)
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1
state:R  running task stack:0 pid: 3715 ppid: 2 flags:0x0008
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq 
efi_call_rts
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] 
__schedule+0x226/0x644

  uname -a:
  Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 
2022 riscv64 riscv64 riscv64 GNU/Linux
  --- 
  ProblemType: Bug
  Architecture: riscv64
  DistroRelease: Ubuntu 22.04
  Package: linux-image-generic 5.15.0.1004.4
  PackageArchitecture: riscv64
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   LANG=C.UTF-8
  Uname: Linux 5.15.0-1004-generic riscv64
  UserGroups: N/A
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1968749] [NEW] focal/linux-azure: Enable missing config options

Public bug reported:

SRU Justification

[Impact]

focal/linux-azure is missing a number of config options compared to
impish/linux-azure.

>From Microsoft:
We tested this kernel. The P0P1 test cases are finished. Below are we found. P2 
test cases are still running. I will update you when they are finished.

1. From dmesg, we can see following lines. Could you check why it has these 
messages and if the messages impact the system?
[3.341802] squashfs: SQUASHFS error: Xattrs in filesystem, these will be 
ignored
[3.346056] unable to read xattr id index table

2. The kernel hasn't backport Michael's SRIOV performance improvement patches. 
The network performance is not expected.
Here are the patches:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=37200078ed6aa2ac3c88a01a64996133dccfdd34
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=8d21732475c637c7efcdb91dc927a4c594e97898

3. It is failed to create raid 0 using below command.
# mdadm --create /dev/md0 --level 0 --raid-devices 16 
/dev/sd[abcdghijklmnopqr][1-5]
mdadm: Defaulting to version 1.2 metadata
mdadm: RUN_ARRAY failed: Invalid argument

>From dmesg, it has following lines:
[  235.830712] md: personality for level 0 is not loaded!
[  235.830733] md: md0 stopped.

I see many raid related configuration is not set.  Could you check the raid 
related and other configuration?
# cat /boot/config-5.4.0-1076-azure | grep RAID
CONFIG_RAID_ATTRS=m
# CONFIG_BLK_DEV_3W__RAID is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
CONFIG_MEGARAID_SAS=y
# CONFIG_SCSI_PMCRAID is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID10 is not set
# CONFIG_MD_RAID456 is not set
# CONFIG_DM_RAID is not set
CONFIG_BCM_SBA_RAID=m
CONFIG_DMA_ENGINE_RAID=y
CONFIG_RAID6_PQ=m
CONFIG_RAID6_PQ_BENCHMARK=y

[Test Case]

Microsoft tested

[Where things could go wrong]

There should be little chance of regression given that these are config
options.

** Affects: linux-azure (Ubuntu)
 Importance: Medium
 Status: Fix Released

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


** Tags: bot-stop-nagging

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

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

** Tags added: bot-stop-nagging

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

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

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

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

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

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

Title:
  focal/linux-azure: Enable missing config options

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure source package in Focal:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  focal/linux-azure is missing a number of config options compared to
  impish/linux-azure.

  From Microsoft:
  We tested this kernel. The P0P1 test cases are finished. Below are we found. 
P2 test cases are still running. I will update you when they are finished.

  1. From dmesg, we can see following lines. Could you check why it has these 
messages and if the messages impact the system?
  [3.341802] squashfs: SQUASHFS error: Xattrs in filesystem, these will be 
ignored
  [3.346056] unable to read xattr id index table

  2. The kernel hasn't backport Michael's SRIOV performance improvement 
patches. The network performance is not expected.
  Here are the patches:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=37200078ed6aa2ac3c88a01a64996133dccfdd34
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.18-rc2=8d21732475c637c7efcdb91dc927a4c594e97898

  3. It is failed to create raid 0 using below command.
  # mdadm --create /dev/md0 --level 0 --raid-devices 16 
/dev/sd[abcdghijklmnopqr][1-5]
  mdadm: Defaulting to version 1.2 metadata
  mdadm: RUN_ARRAY failed: Invalid argument

  From dmesg, it has following lines:
  [  235.830712] md: personality for level 0 is not loaded!
  [  235.830733] md: md0 stopped.

  I see many raid related configuration is not set.  Could you check the raid 
related and other configuration?
  # cat /boot/config-5.4.0-1076-azure | grep RAID
  CONFIG_RAID_ATTRS=m
  # CONFIG_BLK_DEV_3W__RAID is not set
  # CONFIG_SCSI_AACRAID is not set
  # CONFIG_MEGARAID_NEWGEN is not set
  # CONFIG_MEGARAID_LEGACY is not set
  CONFIG_MEGARAID_SAS=y
  #

[Kernel-packages] [Bug 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology

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

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

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

Title:
  linux-azure: Fix NUMA node assignment when kernel boots with custom
  NUMA topology

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
  Invalid
Status in linux-azure source package in Focal:
  Fix Released
Status in linux-hwe-5.11 source package in Focal:
  In Progress
Status in linux-azure source package in Impish:
  Fix Released
Status in linux-hwe-5.11 source package in Impish:
  Invalid
Status in linux-azure source package in Jammy:
  Fix Released
Status in linux-hwe-5.11 source package in Jammy:
  Invalid

Bug description:
  SRU Justification

  [Impact]

  When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
  driver should only set an online NUMA node on the device. This can happen
  during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
  
  This patch also fixes the case where kernel is booting with "numa=off".

  Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and
  support PCI_BUS_RELATIONS2")

  [Test Case]

  Microsoft tested.

  [Where things could go wrong]

  NUMA node assignments could be wrong.

  [Other Info]

  SF: #00323281

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


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

[Kernel-packages] [Bug 1949770] Re: Enable arm64 for Hyper-V guests

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

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

Title:
  Enable arm64 for Hyper-V guests

Status in linux-azure package in Ubuntu:
  Fix Committed
Status in linux-meta-azure package in Ubuntu:
  In Progress
Status in linux-signed-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Hirsute:
  Fix Released
Status in linux-meta-azure source package in Hirsute:
  Fix Released
Status in linux-signed-azure source package in Hirsute:
  Fix Released
Status in linux-azure source package in Impish:
  Fix Released
Status in linux-meta-azure source package in Impish:
  Fix Released
Status in linux-signed-azure source package in Impish:
  Fix Released
Status in linux-azure source package in Jammy:
  Fix Committed
Status in linux-meta-azure source package in Jammy:
  In Progress
Status in linux-signed-azure source package in Jammy:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Since linux-azure can also be used for local Hyper-V guests on Windows
  10 Pro running on arm64 platforms, enable arm64 build for this kernel
  as well.

  [Test Case]

  Boot an arm64 VM on a machine running Win10Pro with Hyper-V.

  [Where things could go wrong]

  Some of the patches touch common PCI code. Device detection could be
  impacted.

  [Other info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

2022-04-12 Thread Anurag Kashyap

I have ho laptop and after the suspend. Not able to open computer nonkeys work 
each and every time need to shutdown and open. 
How to fix this?? Need help

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

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-
  image-5.0.0-1070-oem-osp1". But with this old kernel I run into
  different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

2022-04-12 Thread Louis Bouchard

So testing with Fedora's boot/efi/EFI/fedora/grubx64.efi in place of the
Ubuntu version solves the problem.

So it is indeed the situation that you describe in comment #15

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

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

2022-04-12 Thread Louis Bouchard

Hi xnox,

Thanks for the reply. I'll test both options and report to you here.

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

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU

[Kernel-packages] [Bug 1955655] Re: kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted Virtualization( SEV) is enabled without setting swiotlb boot param

2022-04-12 Thread Dimitri John Ledkov

I believe this is still related to lack of rhboot upstreaming patches to
grub to use highmem allocations; such that lowmem remains unused; and
thus SEV/SWIOTLB can be used "normally".

It is likely the difference you see is due to fedora's grub patches.

It would be interesting, if you could unpack & use fedora's kernel with
ubuntu's grub, and see if fedora's kernel starts failing when booted via
ubuntu's grub?

Or vice-versa; unpack and use ubuntu's kernel on fedora with fedora's
grub to observe it working fine.

That would help eliminate differences of grub between the distros with
the same kernels.

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

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

Title:
  kernel-5.13.0-23-generic : Unable to boot when Secure Encrypted
  Virtualization( SEV) is enabled without setting swiotlb boot param

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While investigating LP: #1955395 by using the -generic kernel image,
  it appeared that it is impossible to boot the kernel unless the boot
  parameter swiotlb is set to 512M (swiotlb=262144).

  Wnen not set, the kernel tries to adjust the bounce buffer to 1024Mb
  it fails and later trigger a kernel panic with the following trace :

  $ grep TLB /tmp/console.log
  [0.003665] software IO TLB: SWIOTLB bounce buffer size adjusted to 1024MB
  [0.034219] kvm-guest: KVM setup pv remote TLB flush
  [0.037063] software IO TLB: Cannot allocate buffer
  [0.223009] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.223634] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.297424] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.297424] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.018860] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.019552] software IO TLB: No low mem
  [1.451497] Kernel panic - not syncing: Can not allocate SWIOTLB buffer 
earlier and can't now provide you with the DMA bounce buffer
  [1.491589] ---[ end Kernel panic - not syncing: Can not allocate SWIOTLB 
buffer earlier and can't now provide you with the DMA bounce buffer ]---

  The SWIOTLB adjustment comes from the following kernel commit :
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e998879d4fb7991856916972168cf27c0d86ed12

  For some reason, the LowMem allocation fails (as seen by the "software
  IO TLB: No low mem" msg),hence the SWIOTLB adjustment cannot be
  completed.

  When booting with the swiotlb=262144 value, we get the following output :
  $ grep TLB /tmp/console.log

  [0.050908] kvm-guest: KVM setup pv remote TLB flush
  [0.308896] Last level iTLB entries: 4KB 512, 2MB 255, 4MB 127
  [0.309494] Last level dTLB entries: 4KB 512, 2MB 255, 4MB 127, 1GB 0
  [0.373162] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
  [0.373162] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
  [1.071136] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
  [1.071837] software IO TLB: mapped [mem 
0x5bebe000-0x7bebe000] (512MB)
  [1.529804] software IO TLB: Memory encryption is active and system is 
using DMA bounce buffers

  
  For comparaison, the Fedora 34 kernel (5.15.4-101.fc34.x86_64) with the same 
adjustment mechanism does correctly adjust the SWIOTLB bounce buffer, without 
the need to set the swiotlb= value at boot time.

  The SWIOTLB buffer adjustment has been introduced in kernel 5.11.

  We can make SEV enabled resources available for testing if needed.

  ...Louis
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 23 13:32 seq
   crw-rw 1 root audio 116, 33 Dec 23 13:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Scaleway SCW-ENT1-S
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-23-generic 
root=UUID=1f577236-6bf2-48ef-998a-ba45f71aca7f ro console=tty1 console=ttyS0 
swiotlb=262144
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19

[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]

New fix proposed in:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: mutter (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
  KMS update: CRTC property (GAMMA_LUT) not found]

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Screen can't turn back on by clicking keyboard after screen off by meta + l 
key.
  Try to do VT switch can make the screen back, some error poped when I try to 
wake up screen.

  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not 
found
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid 
argument
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-03-31 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  Tags: wayland-session jammy third-party-packages
  Uname: Linux 5.15.0-23-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29

** Changed in: linux (Ubuntu Bionic)
   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/1967013

Title:
  Bionic update: upstream stable patchset 2022-03-29

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-03-29

  Ported from the following upstream stable releases:
  v4.14.266, v4.19.229
  v4.14.267, v4.19.230
  v4.14.268, v4.19.231

     from git://git.kernel.org/

  moxart: fix potential use-after-free on remove path
  x86/mm, mm/hwpoison: Fix the unmap kernel 1:1 pages check condition
  UBUNTU: upstream stable to v4.14.266, v4.19.229
  integrity: check the return value of audit_log_start()
  ima: Remove ima_policy file before directory
  ima: Allow template selection with ima_template[_fmt]= after ima_hash=
  mmc: sdhci-of-esdhc: Check for error num after setting mask
  net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs
  NFS: Fix initialisation of nfs_client cl_flags field
  NFSD: Clamp WRITE offsets
  NFSv4 only print the label when its queried
  nfs: nfs4clinet: check the return value of kstrdup()
  NFSv4.1: Fix uninitialised variable in devicenotify
  NFSv4 remove zero number of fs_locations entries error check
  NFSv4 expose nfs_parse_server_name function
  scsi: target: iscsi: Make sure the np under each tpg is unique
  usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
  net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
  Revert "net: axienet: Wait for PhyRstCmplt after core reset"
  ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
  ARM: dts: meson: Fix the UART compatible strings
  staging: fbtft: Fix error path in fbtft_driver_module_init()
  ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
  usb: f_fs: Fix use-after-free for epfile
  bonding: pair enable_port with slave_arr_updates
  ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path
  net: do not keep the dst cache when uncloning an skb dst and its metadata
  net: fix a memleak when uncloning an skb dst and its metadata
  tipc: rate limit warning for received illegal binding update
  net: amd-xgbe: disable interrupts during pci removal
  vt_ioctl: fix array_index_nospec in vt_setactivate
  vt_ioctl: add array_index_nospec to VT_ACTIVATE
  n_tty: wake up poll(POLLRDNORM) on receiving data
  usb: ulpi: Move of_node_put to ulpi_dev_release
  usb: ulpi: Call of_node_put correctly
  usb: dwc3: gadget: Prevent core from processing stale TRBs
  USB: gadget: validate interface OS descriptor requests
  usb: gadget: rndis: check size of RNDIS_MSG_SET command
  USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
  USB: serial: option: add ZTE MF286D modem
  USB: serial: ch341: add support for GW Instek USB2.0-Serial devices
  USB: serial: cp210x: add NCR Retail IO box id
  USB: serial: cp210x: add CPI Bulk Coin Recycler id
  seccomp: Invalidate seccomp mode to catch death failures
  hwmon: (dell-smm) Speed up setting of fan speed
  perf: Fix list corruption in perf_cgroup_switch()
  net: bridge: fix stale eth hdr pointer in br_dev_xmit
  UBUNTU: upstream stable to v4.14.267, v4.19.230
  Makefile.extrawarn: Move -Wunaligned-access to W=1
  net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
  serial: parisc: GSC: fix build when IOSAPIC is not set
  parisc: Fix data TLB miss in sba_unmap_sg
  parisc: Fix sglist access in ccio-dma.c
  btrfs: send: in case of IO error log it
  net: ieee802154: at86rf230: Stop leaking skb's
  selftests/zram: Skip max_comp_streams interface on newer kernel
  selftests/zram01.sh: Fix compression ratio calculation
  selftests/zram: Adapt the situation that /dev/zram0 is being used
  ax25: improve the incomplete fix to avoid UAF and NPD bugs
  vfs: make freeze_super abort when sync_filesystem returns error
  quota: make dquot_quota_sync return errors from ->sync_fs
  Revert "module, async: async_synchronize_full() on module init iff async is 
used"
  iwlwifi: fix use-after-free
  drm/radeon: Fix backlight control on iMac 12,1
  xfrm: Don't accidentally set RTO_ONLINK in decode_session4()
  taskstats: Cleanup the use of task->exit_code
  vsock: remove vsock from connected table when connect is

[Kernel-packages] [Bug 1967582] Re: Focal update: v5.4.181 upstream stable release

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

Title:
  Focal update: v5.4.181 upstream stable release

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

Bug description:
  SRU Justification

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

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

  Makefile.extrawarn: Move -Wunaligned-access to W=1
  HID:Add support for UGTABLET WP5540
  Revert "svm: Add warning message for AVIC IPI invalid target"
  serial: parisc: GSC: fix build when IOSAPIC is not set
  parisc: Drop __init from map_pages declaration
  parisc: Fix data TLB miss in sba_unmap_sg
  parisc: Fix sglist access in ccio-dma.c
  btrfs: send: in case of IO error log it
  platform/x86: ISST: Fix possible circular locking dependency detected
  selftests: rtc: Increase test timeout so that all tests run
  net: ieee802154: at86rf230: Stop leaking skb's
  selftests/zram: Skip max_comp_streams interface on newer kernel
  selftests/zram01.sh: Fix compression ratio calculation
  selftests/zram: Adapt the situation that /dev/zram0 is being used
  ax25: improve the incomplete fix to avoid UAF and NPD bugs
  vfs: make freeze_super abort when sync_filesystem returns error
  quota: make dquot_quota_sync return errors from ->sync_fs
  nvme: fix a possible use-after-free in controller reset during load
  nvme-tcp: fix possible use-after-free in transport error_recovery work
  nvme-rdma: fix possible use-after-free in transport error_recovery work
  drm/amdgpu: fix logic inversion in check
  Revert "module, async: async_synchronize_full() on module init iff async is 
used"
  ftrace: add ftrace_init_nop()
  module/ftrace: handle patchable-function-entry
  arm64: module: rework special section handling
  arm64: module/ftrace: intialize PLT at load time
  iwlwifi: fix use-after-free
  drm/radeon: Fix backlight control on iMac 12,1
  ext4: check for out-of-order index extents in ext4_valid_extent_entries()
  ext4: check for inconsistent extents between index and leaf block
  ext4: prevent partial update of the extent blocks
  taskstats: Cleanup the use of task->exit_code
  dmaengine: at_xdmac: Start transfer for cyclic channels in issue_pending
  vsock: remove vsock from connected table when connect is interrupted by a 
signal
  mmc: block: fix read single on recovery logic
  iwlwifi: pcie: fix locking when "HW not ready"
  iwlwifi: pcie: gen2: fix locking when "HW not ready"
  netfilter: nft_synproxy: unregister hooks on init error path
  net: dsa: lan9303: fix reset on probe
  net: ieee802154: ca8210: Fix lifs/sifs periods
  ping: fix the dif and sdif check in ping_lookup
  bonding: force carrier update when releasing slave
  drop_monitor: fix data-race in dropmon_net_event / trace_napi_poll_hit
  bonding: fix data-races around agg_select_timer
  libsubcmd: Fix use-after-free for realloc(..., 0)
  ALSA: hda: Fix regression on forced probe mask option
  ALSA: hda: Fix missing codec probe on Shenker Dock 15
  ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw()
  ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw_range()
  powerpc/lib/sstep: fix 'ptesync' build error
  mtd: rawnand: gpmi: don't leak PM reference in error path
  block/wbt: fix negative inflight counter when remove scsi device
  NFS: LOOKUP_DIRECTORY is also ok with symlinks
  NFS: Do not report writeback errors in nfs_getattr()
  mtd: rawnand: qcom: Fix clock sequencing in qcom_nandc_probe()
  mtd: rawnand: brcmnand: Fixed incorrect sub-page ECC status
  scsi: lpfc: Fix pt2pt NVMe PRLI reject LOGO loop
  EDAC: Fix calculation of returned address and next offset in edac_align_ptr()
  net: sched: limit TC_ACT_REPEAT loops
  dmaengine: sh: rcar-dmac: Check for error num after setting mask
  copy_process(): Move fd_install() out of sighand->siglock critical section
  i2c: brcmstb: fix support for DSL and CM variants
  Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj
  KVM: x86/pmu: Use AMD64_RAW_EVENT_MASK for PERF_TYPE_RAW
  ARM: OMAP2+: hwmod: Add of_node_put() before break
  ARM: OMAP2+: adjust the location of put_device() call in omapdss_init_of
  irqchip/sifive-plic: Add missing thead,c900-plic match string
  netfilter: conntrack: don't refresh sctp entries in closed state
  arm64: dts: meson-gx: add ATF BL32 reserved-memory region
  arm64: dts: meson-g12:

[Kernel-packages] [Bug 1965591] Re: Focal update: v5.4.179 upstream stable release

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

Title:
  Focal update: v5.4.179 upstream stable release

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

Bug description:
  SRU Justification

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

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

  moxart: fix potential use-after-free on remove path
  Linux 5.4.179
  UBUNTU: upstream stable to v5.4.179

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


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

[Kernel-packages] [Bug 1966118] Re: Focal update: v5.4.180 upstream stable release

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

Title:
  Focal update: v5.4.180 upstream stable release

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

Bug description:
  SRU Justification

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

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

  integrity: check the return value of audit_log_start()
  ima: Remove ima_policy file before directory
  ima: Allow template selection with ima_template[_fmt]= after ima_hash=
  ima: Do not print policy rule with inactive LSM labels
  mmc: sdhci-of-esdhc: Check for error num after setting mask
  net: phy: marvell: Fix RGMII Tx/Rx delays setting in 88e1121-compatible PHYs
  net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs
  NFS: Fix initialisation of nfs_client cl_flags field
  NFSD: Clamp WRITE offsets
  NFSD: Fix offset type in I/O trace points
  NFSv4 only print the label when its queried
  nfs: nfs4clinet: check the return value of kstrdup()
  NFSv4.1: Fix uninitialised variable in devicenotify
  NFSv4 remove zero number of fs_locations entries error check
  NFSv4 expose nfs_parse_server_name function
  drm: panel-orientation-quirks: Add quirk for the 1Netbook OneXPlayer
  net: sched: Clarify error message when qdisc kind is unknown
  scsi: target: iscsi: Make sure the np under each tpg is unique
  scsi: qedf: Fix refcount issue when LOGO is received during TMF
  scsi: myrs: Fix crash in error case
  PM: hibernate: Remove register_nosave_region_late()
  usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
  net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
  KVM: nVMX: eVMCS: Filter out VM_EXIT_SAVE_VMX_PREEMPTION_TIMER
  riscv: fix build with binutils 2.38
  ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
  ARM: socfpga: fix missing RESET_CONTROLLER
  nvme-tcp: fix bogus request completion when failing to send AER
  ACPI/IORT: Check node revision for PMCG resources
  PM: s2idle: ACPI: Fix wakeup interrupts handling
  net: bridge: fix stale eth hdr pointer in br_dev_xmit
  perf probe: Fix ppc64 'perf probe add events failed' case
  ARM: dts: meson: Fix the UART compatible strings
  staging: fbtft: Fix error path in fbtft_driver_module_init()
  ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
  usb: f_fs: Fix use-after-free for epfile
  misc: fastrpc: avoid double fput() on failed usercopy
  ixgbevf: Require large buffers for build_skb on 82599VF
  bonding: pair enable_port with slave_arr_updates
  ipmr,ip6mr: acquire RTNL before calling ip[6]mr_free_table() on failure path
  nfp: flower: fix ida_idx not being released
  net: do not keep the dst cache when uncloning an skb dst and its metadata
  net: fix a memleak when uncloning an skb dst and its metadata
  veth: fix races around rq->rx_notify_masked
  net: mdio: aspeed: Add missing MODULE_DEVICE_TABLE
  tipc: rate limit warning for received illegal binding update
  net: amd-xgbe: disable interrupts during pci removal
  vt_ioctl: fix array_index_nospec in vt_setactivate
  vt_ioctl: add array_index_nospec to VT_ACTIVATE
  n_tty: wake up poll(POLLRDNORM) on receiving data
  eeprom: ee1004: limit i2c reads to I2C_SMBUS_BLOCK_MAX
  net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
  usb: ulpi: Move of_node_put to ulpi_dev_release
  usb: ulpi: Call of_node_put correctly
  usb: dwc3: gadget: Prevent core from processing stale TRBs
  usb: gadget: udc: renesas_usb3: Fix host to USB_ROLE_NONE transition
  USB: gadget: validate interface OS descriptor requests
  usb: gadget: rndis: check size of RNDIS_MSG_SET command
  usb: gadget: f_uac2: Define specific wTerminalType
  USB: serial: ftdi_sio: add support for Brainboxes US-159/235/320
  USB: serial: option: add ZTE MF286D modem
  USB: serial: ch341: add support for GW Instek USB2.0-Serial devices
  USB: serial: cp210x: add NCR Retail IO box id
  USB: serial: cp210x: add CPI Bulk Coin Recycler id
  seccomp: Invalidate seccomp mode to catch death failures
  hwmon: (dell-smm) Speed up setting of fan speed
  scsi: lpfc: Remove NVMe support if kernel has NVME_FC disabled
  perf: Fix list corruption in perf_cgroup_switch()
  Linux 5.4.180
  UBUNTU: upstream stable to v5.4.180

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1968701] Status changed to Confirmed

This change was made by a bot.

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

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

Title:
  [amdgpu] GPU freezes sometimes after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Sometimes (but not always) the GPU fails to wake up properly from
  suspend. Sometimes the laptop will work correctly.

  The user (using X.org) will experience a black screen and an apparent
  freeze. If one waits long enough (tens of seconds - up to a few
  minutes), there will be very slow updates of the screen display
  (typically a lock screen) and some intermittent corruption.

  CAPS LOCK works One can change to a VT, but there can be a long delay
  until the system responds. Once in a VT, the system can be restarted
  properly.

  H/W: Lenovo P14s Gen2 AMD (5850U). I didn't experience this bug on
  Impish Indri, it surfaced after installing Jammy. I'm using X.org (KDE
  Plasma).

  Attaching a trace from a failed resume.

  Very likely related / the same upstream bug:
  https://gitlab.freedesktop.org/drm/amd/-/issues/1850

  I also get similar Fence fallback timer messages in log until
  rebooted:

  Apr 12 12:33:36 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:36 catonthemove kernel: [drm] Fence fallback timer expired on 
ring gfx 
  Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on 
ring gfx 
  Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0 
  Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on 
ring gfx 
  Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on 
ring sdma0

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ville  1890 F pulseaudio
   /dev/snd/pcmC1D0p:   ville  1890 F...m pulseaudio
   /dev/snd/controlC2:  ville  1890 F pulseaudio
   /dev/snd/controlC0:  ville  1890 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Tue Apr 12 12:55:10 2022
  InstallationDate: Installed on 2021-12-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 
(20211013)
  MachineType: LENOVO 21A0CTO1WW
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro 
resume=UUID=e12c5a05-a085-4ccc-bbf1-8cd5f6511d99
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-03-31 (11 days ago)
  dmi.bios.date: 03/01/2022
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET45W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET45W(1.15):bd03/01/2022:br1.15:efr1.15:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1968223] Re: Impish update: upstream stable patchset 2022-04-07

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

Title:
  Impish update: upstream stable patchset 2022-04-07

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-04-07

  Ported from the following upstream stable releases:
  v5.10.102, v5.15.25

     from git://git.kernel.org/

  drm/nouveau/pmu/gm200-: use alternate falcon reset sequence
  mm: memcg: synchronize objcg lists with a dedicated spinlock
  fs/proc: task_mmu.c: don't read mapcount for migration entry
  scsi: lpfc: Fix mailbox command failure during driver initialization
  HID:Add support for UGTABLET WP5540
  Revert "svm: Add warning message for AVIC IPI invalid target"
  serial: parisc: GSC: fix build when IOSAPIC is not set
  parisc: Drop __init from map_pages declaration
  parisc: Fix data TLB miss in sba_unmap_sg
  parisc: Fix sglist access in ccio-dma.c
  mmc: block: fix read single on recovery logic
  mm: don't try to NUMA-migrate COW pages that have other uses
  PCI: hv: Fix NUMA node assignment when kernel boots with custom NUMA topology
  parisc: Add ioread64_lo_hi() and iowrite64_lo_hi()
  btrfs: send: in case of IO error log it
  platform/x86: touchscreen_dmi: Add info for the RWC NANOTE P8 AY07J 2-in-1
  platform/x86: ISST: Fix possible circular locking dependency detected
  selftests: rtc: Increase test timeout so that all tests run
  kselftest: signal all child processes
  net: ieee802154: at86rf230: Stop leaking skb's
  selftests/zram: Skip max_comp_streams interface on newer kernel
  selftests/zram01.sh: Fix compression ratio calculation
  selftests/zram: Adapt the situation that /dev/zram0 is being used
  selftests: openat2: Print also errno in failure messages
  selftests: openat2: Add missing dependency in Makefile
  selftests: openat2: Skip testcases that fail with EOPNOTSUPP
  selftests: skip mincore.check_file_mmap when fs lacks needed support
  ax25: improve the incomplete fix to avoid UAF and NPD bugs
  vfs: make freeze_super abort when sync_filesystem returns error
  quota: make dquot_quota_sync return errors from ->sync_fs
  scsi: pm8001: Fix use-after-free for aborted TMF sas_task
  scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task
  nvme: fix a possible use-after-free in controller reset during load
  nvme-tcp: fix possible use-after-free in transport error_recovery work
  nvme-rdma: fix possible use-after-free in transport error_recovery work
  drm/amdgpu: fix logic inversion in check
  x86/Xen: streamline (and fix) PV CPU enumeration
  Revert "module, async: async_synchronize_full() on module init iff async is 
used"
  gcc-plugins/stackleak: Use noinstr in favor of notrace
  random: wake up /dev/random writers after zap
  iwlwifi: fix use-after-free
  drm/radeon: Fix backlight control on iMac 12,1
  drm/i915/opregion: check port number bounds for SWSCI display power state
  vsock: remove vsock from connected table when connect is interrupted by a 
signal
  drm/i915/gvt: Make DRM_I915_GVT depend on X86
  iwlwifi: pcie: fix locking when "HW not ready"
  iwlwifi: pcie: gen2: fix locking when "HW not ready"
  selftests: netfilter: fix exit value for nft_concat_range
  netfilter: nft_synproxy: unregister hooks on init error path
  ipv6: per-netns exclusive flowlabel checks
  net: dsa: lan9303: fix reset on probe
  net: dsa: lantiq_gswip: fix use after free in gswip_remove()
  net: ieee802154: ca8210: Fix lifs/sifs periods
  ping: fix the dif and sdif check in ping_lookup
  bonding: force carrier update when releasing slave
  drop_monitor: fix data-race in dropmon_net_event / trace_napi_poll_hit
  net_sched: add __rcu annotation to netdev->qdisc
  bonding: fix data-races around agg_select_timer
  libsubcmd: Fix use-after-free for realloc(..., 0)
  dpaa2-eth: Initialize mutex used in one step timestamping path
  perf bpf: Defer freeing string after possible strlen() on it
  selftests/exec: Add non-regular to TEST_GEN_PROGS
  ALSA: hda/realtek: Add quirk for Legion Y9000X 2019
  ALSA: hda/realtek: Fix deadlock by COEF mutex
  ALSA: hda: Fix regression on forced probe mask option
  ALSA: hda: Fix missing codec probe on Shenker Dock 15
  ASoC: ops: Fix stereo change notifications in snd_soc_put_volsw()
  ASoC: ops:

[Kernel-packages] [Bug 1966021] Re: Impish update: upstream stable patchset 2022-03-22

Skipped "audit: improve audit queue handling when "audit=1" on cmdline"
since that was already picked before.

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

Title:
  Impish update: upstream stable patchset 2022-03-22

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-03-22

  Ported from the following upstream stable releases:
  v5.10.99, v5.15.22
  v5.10.100, v5.15.23

     from git://git.kernel.org/

  selinux: fix double free of cond_list on error paths
  audit: improve audit queue handling when "audit=1" on cmdline
  ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
  ASoC: ops: Reject out of bounds values in snd_soc_put_volsw_sx()
  ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
  ALSA: usb-audio: Correct quirk for VF0770
  ALSA: hda: Fix UAF of leds class devs at unbinding
  ALSA: hda: realtek: Fix race at concurrent COEF updates
  ALSA: hda/realtek: Add quirk for ASUS GU603
  ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte X570 ALC1220 
quirks
  ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus Master (newer 
chipset)
  ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus Xtreme after 
reboot from Windows
  btrfs: fix deadlock between quota disable and qgroup rescan worker
  drm/nouveau: fix off by one in BIOS boundary checking
  drm/amd/display: Force link_rate as LINK_RATE_RBR2 for 2018 15" Apple Retina 
panels
  nvme-fabrics: fix state check in nvmf_ctlr_matches_baseopts()
  mm/debug_vm_pgtable: remove pte entry from the page table
  mm/pgtable: define pte_index so that preprocessor could recognize it
  mm/kmemleak: avoid scanning potential huge holes
  block: bio-integrity: Advance seed correctly for larger interval sizes
  dma-buf: heaps: Fix potential spectre v1 gadget
  IB/hfi1: Fix AIP early init panic
  memcg: charge fs_context and legacy_fs_context
  RDMA/cma: Use correct address when leaving multicast group
  RDMA/ucma: Protect mc during concurrent multicast leaves
  IB/rdmavt: Validate remote_addr during loopback atomic tests
  RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
  RDMA/mlx4: Don't continue event handler after memory allocation failure
  iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping()
  iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
  spi: bcm-qspi: check for valid cs before applying chip select
  spi: mediatek: Avoid NULL pointer crash in interrupt
  spi: meson-spicc: add IRQ check in meson_spicc_probe
  spi: uniphier: fix reference count leak in uniphier_spi_probe()
  net: ieee802154: hwsim: Ensure proper channel selection at probe time
  net: ieee802154: mcr20a: Fix lifs/sifs periods
  net: ieee802154: ca8210: Stop leaking skb's
  net: ieee802154: Return meaningful error codes from the netlink helpers
  net: macsec: Fix offload support for NETDEV_UNREGISTER event
  net: macsec: Verify that send_sci is on when setting Tx sci explicitly
  net: stmmac: dump gmac4 DMA registers correctly
  net: stmmac: ensure PTP time register reads are consistent
  drm/i915/overlay: Prevent divide by zero bugs in scaling
  ASoC: fsl: Add missing error handling in pcm030_fabric_probe
  ASoC: xilinx: xlnx_formatter_pcm: Make buffer bytes multiple of period bytes
  ASoC: cpcap: Check for NULL pointer after calling of_get_child_by_name
  ASoC: max9759: fix underflow in speaker_gain_control_put()
  pinctrl: intel: Fix a glitch when updating IRQ flags on a preconfigured line
  pinctrl: intel: fix unexpected interrupt
  pinctrl: bcm2835: Fix a few error paths
  scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe
  nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed client.
  gve: fix the wrong AdminQ buffer queue index check
  bpf: Use VM_MAP instead of VM_ALLOC for ringbuf
  selftests/exec: Remove pipe from TEST_GEN_FILES
  selftests: futex: Use variable MAKE instead of make
  tools/resolve_btfids: Do not print any commands when building silently
  rtc: cmos: Evaluate century appropriate
  Revert "fbcon: Disable accelerated scrolling"
  UBUNTU: updateconfigs for FRAMEBUFFER_CONSOLE_LEGACY_ACCELERATION
  fbcon: Add option to enable legacy hardware acceleration
  perf stat:

[Kernel-packages] [Bug 1967439] Re: Impish update: upstream stable patchset 2022-03-31

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

Title:
  Impish update: upstream stable patchset 2022-03-31

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-03-31

  Ported from the following upstream stable releases:
  v5.10.101, v5.15.24

     from git://git.kernel.org/

  integrity: check the return value of audit_log_start()
  ima: Remove ima_policy file before directory
  ima: Allow template selection with ima_template[_fmt]= after ima_hash=
  mmc: sdhci-of-esdhc: Check for error num after setting mask
  can: isotp: fix potential CAN frame reception race in isotp_rcv()
  net: phy: marvell: Fix RGMII Tx/Rx delays setting in 88e1121-compatible PHYs
  net: phy: marvell: Fix MDI-x polarity setting in 88e1118-compatible PHYs
  NFS: Fix initialisation of nfs_client cl_flags field
  NFSD: Clamp WRITE offsets
  NFSD: Fix offset type in I/O trace points
  tracing: Propagate is_signed to expression
  NFS: change nfs_access_get_cached to only report the mask
  NFSv4 only print the label when its queried
  nfs: nfs4clinet: check the return value of kstrdup()
  NFSv4.1: Fix uninitialised variable in devicenotify
  NFSv4 remove zero number of fs_locations entries error check
  NFSv4 expose nfs_parse_server_name function
  NFSv4 handle port presence in fs_location server string
  x86/perf: Avoid warning for Arch LBR without XSAVE
  drm: panel-orientation-quirks: Add quirk for the 1Netbook OneXPlayer
  net: sched: Clarify error message when qdisc kind is unknown
  powerpc/fixmap: Fix VM debug warning on unmap
  scsi: target: iscsi: Make sure the np under each tpg is unique
  scsi: ufs: ufshcd-pltfrm: Check the return value of devm_kstrdup()
  scsi: qedf: Add stag_work to all the vports
  scsi: qedf: Fix refcount issue when LOGO is received during TMF
  scsi: pm8001: Fix bogus FW crash for maxcpus=1
  scsi: ufs: Treat link loss as fatal error
  scsi: myrs: Fix crash in error case
  PM: hibernate: Remove register_nosave_region_late()
  usb: dwc2: gadget: don't try to disable ep0 in dwc2_hsotg_suspend
  perf: Always wake the parent event
  nvme-pci: add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs
  net: stmmac: dwmac-sun8i: use return val of readl_poll_timeout()
  KVM: eventfd: Fix false positive RCU usage warning
  KVM: nVMX: eVMCS: Filter out VM_EXIT_SAVE_VMX_PREEMPTION_TIMER
  KVM: nVMX: Also filter MSR_IA32_VMX_TRUE_PINBASED_CTLS when eVMCS
  KVM: SVM: Don't kill SEV guest if SMAP erratum triggers in usermode
  KVM: VMX: Set vmcs.PENDING_DBG.BS on #DB in STI/MOVSS blocking shadow
  riscv: fix build with binutils 2.38
  ARM: dts: imx23-evk: Remove MX23_PAD_SSP1_DETECT from hog group
  ARM: dts: Fix boot regression on Skomer
  ARM: socfpga: fix missing RESET_CONTROLLER
  nvme-tcp: fix bogus request completion when failing to send AER
  ACPI/IORT: Check node revision for PMCG resources
  drm/rockchip: vop: Correct RK3399 VOP register fields
  ARM: dts: Fix timer regression for beagleboard revision c
  ARM: dts: meson: Fix the UART compatible strings
  ARM: dts: meson8: Fix the UART device-tree schema validation
  ARM: dts: meson8b: Fix the UART device-tree schema validation
  staging: fbtft: Fix error path in fbtft_driver_module_init()
  ARM: dts: imx6qdl-udoo: Properly describe the SD card detect
  phy: xilinx: zynqmp: Fix bus width setting for SGMII
  ARM: dts: imx7ulp: Fix 'assigned-clocks-parents' typo
  usb: f_fs: Fix use-after-free for epfile
  gpio: aggregator: Fix calling into sleeping GPIO controllers
  drm/vc4: hdmi: Allow DBLCLK modes even if horz timing is odd.
  misc: fastrpc: avoid double fput() on failed usercopy
  netfilter: ctnetlink: disable helper autoassign
  arm64: dts: meson-g12b-odroid-n2: fix typo 'dio2133'
  ixgbevf: Require large buffers for build_skb on 82599VF
  drm/panel: simple: Assign data from panel_dpi_probe() correctly
  gpio: sifive: use the correct register to read output values
  bonding: pair enable_port with slave_arr_updates
  net: dsa: mv88e6xxx: don't use devres for mdiobus
  net: dsa: ar9331: register the mdiobus under devres
  net: dsa: bcm_sf2: don't use devres for mdiobus
  net: dsa: felix: don't use devres for mdiobus
  net: dsa: lantiq_gswip: don't use

[Kernel-packages] [Bug 1968701] [NEW] [amdgpu] GPU freezes sometimes after suspend

2022-04-12 Thread Ville Aakko

Public bug reported:

Hi,

Sometimes (but not always) the GPU fails to wake up properly from
suspend. Sometimes the laptop will work correctly.

The user (using X.org) will experience a black screen and an apparent
freeze. If one waits long enough (tens of seconds - up to a few
minutes), there will be very slow updates of the screen display
(typically a lock screen) and some intermittent corruption.

CAPS LOCK works One can change to a VT, but there can be a long delay
until the system responds. Once in a VT, the system can be restarted
properly.

H/W: Lenovo P14s Gen2 AMD (5850U). I didn't experience this bug on
Impish Indri, it surfaced after installing Jammy. I'm using X.org (KDE
Plasma).

Attaching a trace from a failed resume.

Very likely related / the same upstream bug:
https://gitlab.freedesktop.org/drm/amd/-/issues/1850

I also get similar Fence fallback timer messages in log until rebooted:

Apr 12 12:33:36 catonthemove kernel: [drm] Fence fallback timer expired on ring 
sdma0 
Apr 12 12:33:36 catonthemove kernel: [drm] Fence fallback timer expired on ring 
gfx 
Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on ring 
sdma0 
Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on ring 
gfx 
Apr 12 12:33:37 catonthemove kernel: [drm] Fence fallback timer expired on ring 
sdma0 
Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on ring 
sdma0 
Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on ring 
gfx 
Apr 12 12:33:38 catonthemove kernel: [drm] Fence fallback timer expired on ring 
sdma0

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ville  1890 F pulseaudio
 /dev/snd/pcmC1D0p:   ville  1890 F...m pulseaudio
 /dev/snd/controlC2:  ville  1890 F pulseaudio
 /dev/snd/controlC0:  ville  1890 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Tue Apr 12 12:55:10 2022
InstallationDate: Installed on 2021-12-30 (102 days ago)
InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release amd64 (20211013)
MachineType: LENOVO 21A0CTO1WW
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro 
resume=UUID=e12c5a05-a085-4ccc-bbf1-8cd5f6511d99
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-03-31 (11 days ago)
dmi.bios.date: 03/01/2022
dmi.bios.release: 1.15
dmi.bios.vendor: LENOVO
dmi.bios.version: R1MET45W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21A0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET45W(1.15):bd03/01/2022:br1.15:efr1.15:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
dmi.product.family: ThinkPad P14s Gen 2a
dmi.product.name: 21A0CTO1WW
dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
dmi.product.version: ThinkPad P14s Gen 2a
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy uec-images

** Attachment added: "A trace from a failed resume"
   
https://bugs.launchpad.net/bugs/1968701/+attachment/5579839/+files/amdgputrace.log

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

Title:
  [amdgpu] GPU freezes sometimes after suspend

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  Sometimes (but not always) the GPU fails to wake up properly from
  suspend. Sometimes the laptop will work correctly.

  The user (using X.org) will experience a black screen and an apparent
  freeze. If one waits long enough (tens of seconds - up to a few
  minutes), there will be very slow updates of the screen display
  (typically a lock screen) and some intermittent corruption.

  CAPS LOCK works One can change to a VT, but there can be a long delay
  until the system responds. Once in a VT, the system can be restarted
  properly.

  H/W: Lenovo P14s Gen2 AMD (5850U). I didn't experience this bug on
  Impish Indri, it surfaced after installing Jammy. I'm using X.org (KDE
  Plasma).

  Attaching a trace from a failed resume.

  Very likely related / the same upstream bug:

[Kernel-packages] [Bug 1965589] Re: Impish update: upstream stable patchset 2022-03-18

Skipped "net: sched: fix use-after-free in tc_new_tfilter()" as this was
already applied for CVE-2022-1055.

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

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

Title:
  Impish update: upstream stable patchset 2022-03-18

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

Bug description:
  SRU Justification

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

     upstream stable patchset 2022-03-18
     from git://git.kernel.org/

  PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
  net: ipa: use a bitmap for endpoint replenish_enabled
  net: ipa: prevent concurrent replenish
  KVM: x86: Forcibly leave nested virt when SMM state is toggled
  net/mlx5e: Fix handling of wrong devices during bond netevent
  net/mlx5: Use del_timer_sync in fw reset flow of halting poll
  net/mlx5: E-Switch, Fix uninitialized variable modact
  ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
  net: amd-xgbe: ensure to reset the tx_timer_active flag
  net: amd-xgbe: Fix skb data length underflow
  fanotify: Fix stale file descriptor in copy_event_to_user()
  net: sched: fix use-after-free in tc_new_tfilter()
  rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()
  cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
  af_packet: fix data-race in packet_setsockopt / packet_setsockopt
  tcp: add missing tcp_skb_can_collapse() test in tcp_shift_skb_data()
  selftests: mptcp: fix ipv6 routing setup
  net/mlx5e: Fix module EEPROM query
  net/mlx5: Fix offloading with ESWITCH_IPV4_TTL_MODIFY_ENABLE
  net/mlx5e: Don't treat small ceil values as unlimited in HTB offload
  i40e: Fix reset path while removing the driver
  UBUNTU: upstream stable to v5.10.97, v5.15.20
  UBUNTU: upstream stable to v5.10.98, v5.15.21

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


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

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

2022-04-12 Thread Ubuntu SRU Bot

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

snapd/2.54.3+20.04.1ubuntu0.2 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available

Thanks for the bug report. Please be careful to report only one issue
per bug report.

When you have trouble with the USB not booting, that's usually a bad
copy of the ISO on the USB or a slightly faulty thumb drive. Very
common. Always have a different thumb drive handy to try.

I suggest the best place to start is with Ubuntu 22.04
(http://cdimage.ubuntu.com/daily-live/current/). If you have trouble
with that then we would like to know ASAP.

If you want to stick with 20.04 instead then please try 20.04.4
(https://ubuntu.com/download/desktop) and choose a single issue to
discuss, presumably the first issue you face.


** No longer affects: xorg-server (Ubuntu)

** No longer affects: nvidia-graphics-drivers-450 (Ubuntu)

** Package changed: mutter (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Ubuntu 20.04.3 boots to black screen, no TTY available

Status in gdm:
  New
Status in gnome-session:
  New
Status in grub:
  New
Status in os-prober-efi/trunk:
  New
Status in shim:
  New
Status in subiquity:
  New
Status in tty:
  New
Status in Ubuntu:
  Incomplete

Bug description:
  A fresh attempted install failed utterly, just as 20.04.1 failed two
  years ago.  Has anyone been paying attention?

  Ubuntu 20.04.3 burned just now to a USB stick and attempted to be
  installed.

  The first fail was that the stick booted to a couple of impenetrable
  boot-time messages and hung.  Really.  I'm not making this up.  It
  didn't just open the installer, as it should.

  The second fail was having just to guess that rebooting and trying
  another GRUB menu option might work and give that a try.  Really.  I'm
  not making this up, either.  The installer was entirely incapable of
  providing any direction

  The third failure was that the installer was incapable of detecting
  the video configuration and proceeding accordingly.  This is 20.04.3,
  the third attempt at getting this right, and it still fails.

  The fourth fail was an error message insisting on a designation of
  where root should be, even after the destination partition already had
  been specified.

  The fifth failure was that no obvious means existed to satisfy the
  installer about the root specification, which of course already had
  been made by specifying the destination partition.  All one could do
  was to see whether a context menu existed for any object on the screen
  that might possibly drill down through a few layers to something
  approximating what the content of the error message suggested.

  The sixth failure was that no GRUB menu appeared during boot,
  notwithstanding that the EFI system partition had clearly been
  identified in the installer.

  The seventh failure was that the machine booted only to a black screen
  with a non-blinking _ midway toward the upper left.  No login
  screen/display manager.  No GUI at all.  Just this little _.

  The eighth failure was that Ctrl-alt-f2, ctrl-alt-f5-f12 have no
  effect.  No TTY is available.  There is no way whatsoever to interact
  with the system.

  Expected behavior:  The software would install and the computer would
  work.

  Actual behavior:  The installer bricked my workstation.

  Obviously, no debug information is available BECAUSE THE SOFTWARE
  FAILED.  This post is being made from a borrowed Windows laptop.

  Any thoughts about how to get a working system would be appreciated.
  I am not optimistic about the prospects for 22.04.

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1068.71~18.04.32)

2022-04-12 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-meta-gke-5.4 
(5.4.0.1068.71~18.04.32) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
snapd/2.54.3+18.04.2ubuntu0.2 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available

** No longer affects: wayland (Ubuntu)

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: xorg (Ubuntu)

** No longer affects: grub2 (Ubuntu)

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

Title:
  Ubuntu 20.04.3 boots to black screen, no TTY available

Status in gdm:
  New
Status in gnome-session:
  New
Status in grub:
  New
Status in os-prober-efi/trunk:
  New
Status in shim:
  New
Status in subiquity:
  New
Status in tty:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  A fresh attempted install failed utterly, just as 20.04.1 failed two
  years ago.  Has anyone been paying attention?

  Ubuntu 20.04.3 burned just now to a USB stick and attempted to be
  installed.

  The first fail was that the stick booted to a couple of impenetrable
  boot-time messages and hung.  Really.  I'm not making this up.  It
  didn't just open the installer, as it should.

  The second fail was having just to guess that rebooting and trying
  another GRUB menu option might work and give that a try.  Really.  I'm
  not making this up, either.  The installer was entirely incapable of
  providing any direction

  The third failure was that the installer was incapable of detecting
  the video configuration and proceeding accordingly.  This is 20.04.3,
  the third attempt at getting this right, and it still fails.

  The fourth fail was an error message insisting on a designation of
  where root should be, even after the destination partition already had
  been specified.

  The fifth failure was that no obvious means existed to satisfy the
  installer about the root specification, which of course already had
  been made by specifying the destination partition.  All one could do
  was to see whether a context menu existed for any object on the screen
  that might possibly drill down through a few layers to something
  approximating what the content of the error message suggested.

  The sixth failure was that no GRUB menu appeared during boot,
  notwithstanding that the EFI system partition had clearly been
  identified in the installer.

  The seventh failure was that the machine booted only to a black screen
  with a non-blinking _ midway toward the upper left.  No login
  screen/display manager.  No GUI at all.  Just this little _.

  The eighth failure was that Ctrl-alt-f2, ctrl-alt-f5-f12 have no
  effect.  No TTY is available.  There is no way whatsoever to interact
  with the system.

  Expected behavior:  The software would install and the computer would
  work.

  Actual behavior:  The installer bricked my workstation.

  Obviously, no debug information is available BECAUSE THE SOFTWARE
  FAILED.  This post is being made from a borrowed Windows laptop.

  Any thoughts about how to get a working system would be appreciated.
  I am not optimistic about the prospects for 22.04.

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


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

[Kernel-packages] [Bug 1896137] Re: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"

2022-04-12 Thread Leonard/Janis

This issue arises whenever system-logind access the `/sys/power/disk`
file.  Reproduce using `cat /sys/power/disk` and you'll find

kernel: Lockdown: cat: hibernation is restricted; see man
kernel_lockdown.7

in the kernel log.  This is per-se harmless but does flood the log with
garbage.

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

Title:
  syslog flooded with "Lockdown: systemd-logind: hibernation is
  restricted; see man kernel_lockdown.7"

Status in linux package in Ubuntu:
  Expired

Bug description:
  When I close the lid on my laptop, syslog goes crazy with the message

  systemd-logind: hibernation is restricted; see man kernel_lockdown.7

  repeated ad infinitum, using up all the CPU and GBs of disk space.  I
  am not even trying to hibernate; everything in /etc/systemd/login.conf
  is commented out.  So nothing much should happen when I close the lid,
  but systemd is trying to kill me with these messages.  I am running
  Ubuntu 20.04.

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


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

[Kernel-packages] [Bug 1968617] Re: uc22 no serial console on rpi

2022-04-12 Thread Juerg Haefliger

enable_uart=1 disappeared from config.txt. Looks like snapd is junking
it :-(


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

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

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

Title:
  uc22 no serial console on rpi

Status in linux-raspi package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  New

Bug description:
  The current uc22 beta image (2022-04-11) shows nothing on the serial
  console during boot, nor does it allow console-conf over serial
  console.

  I've double checked with jammy, focal, and uc20 and my serial console
  is working fine with all of those images on this same device (an
  rpi3b+) but with uc22 I don't see any output at all.

  Kernel version:
  Linux ubuntu 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:25:49 UTC 
2022 armv7l armv7l armv7l GNU/Linux

  One thing I did notice, is that I do not see a ttyS0 device, which
  appears to be what it's expecting to use for the serial console

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


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

[Kernel-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts

2022-04-12 Thread Timo Aaltonen

oem-5.14 is still missing verification

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

Title:
  Bolt doesn't work with native USB4 hosts

Status in OEM Priority Project:
  New
Status in bolt package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.17 package in Ubuntu:
  In Progress
Status in bolt source package in Focal:
  Fix Released
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Fix Committed
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in bolt source package in Impish:
  Fix Released
Status in linux source package in Impish:
  Won't Fix
Status in linux-oem-5.14 source package in Impish:
  Invalid
Status in linux-oem-5.17 source package in Impish:
  Invalid
Status in bolt source package in Jammy:
  Fix Released
Status in linux source package in Jammy:
  In Progress
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  In Progress

Bug description:
  [SRU Justification]

  [Impact]

   * AMD Yellow Carp provides integrated USB4 host controllers
   * When plugging in a Thunderbolt3 or USB4 device, users are unable to 
authorize it using the GUI due to an error message: "parent not authorized, 
deferring"

  [Test Plan]

  AMD Yellow Carp Host (issue this bug is about)
  --
   * Plug in USB4 device or TBT3 to AMD Yellow Carp host
   * Ensure that PCI topology has populated
   * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0"
   * Try to run `boltctl enroll $UUID`

  Alpine Ridge / Titan Ridge host (discrete controller)
  --
  Start out on a host with discrete controller (Alpine Ridge or Titan Ridge)
  1. sudo boltctl forget -a
  2. Plug in dock
  3. Make sure 'boltctl list' enumerates dock.
  4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value 
dependent upon host)
     - If 0; try to manually enroll using 'boltctl enroll $UUID'
     - If 1; ensure that device automatically enrolled with bolt.

  GUI Check
  -
  Ensure that devices show up in the Settings GUI and are now able to authorize.
  Note: for AMD platforms enumerating PCIe devices is a separate problem from 
BOLT handled by kernel tasks.  GUI check is only about "authorization".

  [Where problems could occur]

   * Intel USB4 or TBT3 hosts also use bolt.  They could have a problem with 
the new version of bolt.
   * This is very unlikely however since there is a through test suite, and up 
until now the entire industry has been using bolt on Intel controllers for a 
long time.
   * There haven't been any significant bugs reported upstream or in Ubuntu 
since 0.9.1 release.

  [Other Info]
   * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in 
many cases they are automatically authorized to an iommu DMA policy.
   * It is fixed in bolt 0.9.1 or later release.
   * To solve the SRU, will backport 0.9.1 release from Impish.
   * I did look into backporting just the commit(s) for fixing this, but it's 
not a trivial backport.  Quoting the changelog 
(https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): 
"Additionally the unique_id of said host controller changes with every boot, 
which breaks one of the fundamental assumptions in boltd".

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


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

[Kernel-packages] [Bug 1964850] Re: Choppy trackpad/USB mouse behavior with oem-1023 or above kernel version

2022-04-12 Thread Timo Aaltonen

please verify this soon

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

Title:
  Choppy trackpad/USB mouse behavior with oem-1023 or above kernel
  version

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

Bug description:
  [SRU Justfication]

  [Impact]

  Disjoint trackpad/mouse path found on PSR capable panels.

  [Fix]

  Two fixes from v5.17-rc6 that only turns off vblank IRQs when PSR is not
  enabled, originally for commit f94cf1cb1796 ("drm/amdgpu/display: set
  vblank_disable_immediate for DC") that was being backported to LTS stable
  5.15.y, and therefore oem-5.14.

  [Test Case]

  Simply move the mouse around.

  [Where problems could occur]

  This follows for AMD platforms, the power-saving performance may not be
  as good as before, but while we don't have such energy-saving
  certificate program for AMD yet, this would become something to be fully
  addressed in the future.

  [Other Info]

  These fixes have been applied to v5.15.27, and oem-5.14 currently has
  v5.15.25 in -1028, therefore only oem-5.14 is nominated, but probably
  they will still be included through stable patch backport in the next
  release.

  == original bug report ==

  Observed choppy issue for touchpad on HP Lockheed with OEM-1025 kernel, and 
can't smoothly drag USB mouse if connected.
  Rolled back to OEM-1023 kernel and observed the same issues.
  Can't reproduce the issue with OEM-1022 kernel.

  Bisect identified the problematic commits below,
    021e2c1f6143 drm/amdgpu/display: set vblank_disable_immediate for DC
    1a4dd5a679da drm/amd/display: check top_pipe_to_program pointer

  Reverting above 2 commits on the top of oem-5.14-5.14.0-1025.27,
  touchpad or USB mouse back to normal working behavior on HP Lockheed
  and we don't see choppy trackpad/mouse issue.

  $ git log --oneline -5
  62e596025e1e (HEAD -> fm_oem-5.14-next) Revert "drm/amd/display: check 
top_pipe_to_program pointer"
  82cab088605f Revert "drm/amdgpu/display: set vblank_disable_immediate for DC"
  165041ee003c (tag: Ubuntu-oem-5.14-5.14.0-1025.27, origin/oem-5.14-next) 
UBUNTU: Ubuntu-oem-5.14-5.14.0-1025.27
  8bdd3e2ea820 UBUNTU: [Config] Update config to match upstream stable release
  43f3b8b56abe UBUNTU: debian/dkms-versions -- update from kernel-versions 
(main/2022.02.21)

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


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

[Kernel-packages] [Bug 1968631] Re: regression in jammy kernel 5.15 for module ath9k

2022-04-12 Thread Juerg Haefliger

This might be related since it shows ath9k symbols:

[   11.077358] 

[   11.077361] UBSAN: invalid-load in 
/build/linux-9H675w/linux-5.15.0/net/mac80211/status.c:1164:21
[   11.077364] load of value 255 is not a valid value for type '_Bool'
[   11.077366] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.15.0-25-generic 
#25-Ubuntu
[   11.077369] Hardware name: ASUSTeK COMPUTER INC. X550LA/X550LA, BIOS 
X550LA.508 05/14/2014
[   11.077370] Call Trace:
[   11.077371]  
[   11.077374]  show_stack+0x52/0x58
[   11.077379]  dump_stack_lvl+0x4a/0x5f
[   11.077384]  dump_stack+0x10/0x12
[   11.077386]  ubsan_epilogue+0x9/0x45
[   11.077388]  __ubsan_handle_load_invalid_value.cold+0x44/0x49
[   11.077391]  ieee80211_tx_status_ext.cold+0x4e/0x5f [mac80211]
[   11.077448]  ieee80211_tx_status+0x72/0xa0 [mac80211]
[   11.077475]  ath_txq_unlock_complete+0x12d/0x160 [ath9k]
[   11.077483]  ath_tx_edma_tasklet+0xef/0x4c0 [ath9k]
[   11.077491]  ? del_timer_sync+0x6c/0xb0
[   11.077494]  ath9k_tasklet+0x14e/0x290 [ath9k]
[   11.077501]  tasklet_action_common.constprop.0+0xc0/0xf0
[   11.077505]  tasklet_action+0x22/0x30
[   11.077507]  __do_softirq+0xd9/0x2e3
[   11.077511]  irq_exit_rcu+0x8c/0xb0
[   11.077514]  common_interrupt+0x8a/0xa0
[   11.077519]  
[   11.077519]  
[   11.077520]  asm_common_interrupt+0x1e/0x40
[   11.077523] RIP: 0010:cpuidle_enter_state+0xd9/0x620
[   11.077527] Code: 3d e4 5b 5e 5c e8 d7 ad 6c ff 49 89 c7 0f 1f 44 00 00 31 
ff e8 28 ba 6c ff 80 7d d0 00 0f 85 5d 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 
0f 88 69 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e3 03 00 00
[   11.077529] RSP: 0018:a5ff000bbe28 EFLAGS: 0246
[   11.077532] RAX: 94b5d6eb0f00 RBX: c5feffc8 RCX: 
[   11.077533] RDX:  RSI: 0002 RDI: 
[   11.077534] RBP: a5ff000bbe78 R08: 00029442c2c7 R09: 4e20
[   11.077535] R10: 0009 R11: 071c71c71c71c71c R12: a50d3600
[   11.077537] R13: 0001 R14: 0001 R15: 00029442c2c7
[   11.077539]  ? cpuidle_enter_state+0xc8/0x620
[   11.077542]  cpuidle_enter+0x2e/0x40
[   11.077544]  cpuidle_idle_call+0x13e/0x1e0
[   11.077546]  do_idle+0x83/0xf0
[   11.077548]  cpu_startup_entry+0x20/0x30
[   11.077550]  start_secondary+0x12a/0x180
[   11.077553]  secondary_startup_64_no_verify+0xc2/0xcb
[   11.077557]  
[   11.077558] 


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

Title:
  regression in jammy kernel 5.15 for module ath9k

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wireless connection is unstable with kernel 5.15 in jammy release.

  the following line is in my log,

  ath: phy0: DMA failed to stop in 10 ms AR_CR=0x0024
  AR_DIAG_SW=0x0220 DMADBG_7=0x6100

  the bug appears to no longer be present in kernel 5.17.2 from the
  mainline kernel ppa.

  lsb_release -rd output:

  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  1871 F pulseaudio
   /dev/snd/controlC1:  david  1871 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 11 18:05:36 2022
  InstallationDate: Installed on 2022-02-01 (69 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: ASUSTeK COMPUTER INC. X550LA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=eb3fe525-e2d6-4de4-aa48-57ebb0fa0881 ro libata.noacpi=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)
  dmi.bios.date: 05/14/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.508
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor:

[Kernel-packages] [Bug 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug

2022-04-12 Thread Juerg Haefliger

** Tags added: kern-2931

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

Title:
  rtl8761b usb bluetooth doesn't work following reboot until
  unplug/replug

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip.
  0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio

  USB adapter very often stops working, can't connect or find other
  bluetooth devices. The adapter can't work even after reboots.

  The following entries appear in the log:
  апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout
  апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout
  апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout

  Firmware loaded correctly, but something is not working.
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a 
hci_rev=000b lmp_ver=0a lmp_subver=8761
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 
version=1
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_fw.bin
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading 
rtl_bt/rtl8761bu_config.bin
  апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814

  1) I use:
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04
  2) linux-firmware: 20220329.git681281e4-0ubuntu1
  3) What you expected to happen? I expect a well working bluetooth adapter.
  4) What happened instead? My bluetooth adapter may work, may not. The adapter 
may stop finding and connecting to other devices.

  I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1
  I've downloaded Windows's archive 
http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab
  I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and 
replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted 
rtl8761bu_config.bin
  After I changed firmware my usb dongle work fine.

  Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other 
correct version?
  Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate 
packages. I will remove the RTL8761B firmware package and put them manually.

  bluetoothctl --version
  bluetoothctl: 5.64

  hci0:   Type: Primary  Bus: USB
  BD Address: 00:E0:4C:FC:E2:03  ACL MTU: 1021:6  SCO MTU: 255:12
  UP RUNNING
  RX bytes:5751 acl:49 sco:0 events:489 errors:0
  TX bytes:219114 acl:398 sco:0 commands:83 errors:0
  Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
  Link policy: RSWITCH HOLD SNIFF PARK
  Link mode: PERIPHERAL ACCEPT
  Name: 'desktop'
  Class: 0x7c0104
  Service Classes: Rendering, Capturing, Object Transfer, Audio, 
Telephony
  Device Class: Computer, Desktop workstation
  HCI Version: 5.1 (0xa)  Revision: 0x97b
  LMP Version: 5.1 (0xa)  Subversion: 0xec43
  Manufacturer: Realtek Semiconductor Corporation (93)

  rfkill list
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  Realtek's worker updated these bad firmware.
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80

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


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

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

2022-04-12 Thread Steve Beattie

All work for this report has been completed, I believe the linux and
linux-meta tasks can be closed out as well.

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

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

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

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

Status in acpi-call package in Ubuntu:
  Fix Released
Status in apt package in Ubuntu:
  Invalid
Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in bcmwl package in Ubuntu:
  Fix Released
Status in dahdi-linux package in Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dm-writeboost package in Ubuntu:
  Fix Released
Status in evdi package in Ubuntu:
  Fix Released
Status in gost-crypto package in Ubuntu:
  Fix Released
Status in iptables-netflow package in Ubuntu:
  Fix Released
Status in liblzf package in Ubuntu:
  Fix Released
Status in lime-forensics package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-meta package in Ubuntu:
  Fix Released
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in openafs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  Fix Released
Status in r8168 package in Ubuntu:
  Fix Released
Status in rtl8812au package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in update-manager package in Ubuntu:
  Invalid
Status in v4l2loopback package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Fix Released
Status in virtualbox-hwe package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in acpi-call source package in Focal:
  Fix Released
Status in backport-iwlwifi-dkms source package in Focal:
  Fix Released
Status in bcmwl source package in Focal:
  Fix Released
Status in dahdi-linux source package in Focal:
  Fix Released
Status in dm-writeboost source package in Focal:
  Fix Released
Status in evdi source package in Focal:
  Fix Released
Status in gost-crypto source package in Focal:
  Fix Released
Status in iptables-netflow source package in Focal:
  Fix Released
Status in liblzf source package in Focal:
  Fix Released
Status in lime-forensics source package in Focal:
  Fix Released
Status in lttng-modules source package in Focal:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Focal:
  Fix Released
Status in oss4 source package in Focal:
  Fix Released
Status in r8168 source package in Focal:
  Fix Released
Status in rtl8812au source package in Focal:
  Fix Released
Status in sysdig source package in Focal:
  Fix Released
Status in v4l2loopback source package in Focal:
  Fix Released
Status in virtualbox source package in Focal:
  Fix Released
Status in virtualbox-hwe source package in Focal:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released

Bug description:
  Whilst discussing

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering

2022-04-12 Thread Amir Tzin

Hi Dan,

Those test are ASAP which uses steering as its infrastructure thus this
test set when configured to run with software steering verifies the
functionality.

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

Title:
  [Jammy, mlx5, ConnectX-7] add CX7 support for software steering

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Add support for software steering on cx7

  [Test Case]
  configure software steering on cx7 setup
  run asap testing 
  (reference https://github.com/Mellanox/ovs-tests)
   

  [Regression Potential]
  TBD

  [Other Info]

  Feature patchset: 
  All patches are cleanly applied on Jamy master-next beside 
  these two who add minor conflicts due to context difference.
  net/mlx5: Introduce software defined steering capabilities
  net/mlx5: DR, Add support for matching on
   

  #fixes
  624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF
  0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte
  9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately

  
  #CX7 SMFS support
  6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering
  638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1
  75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in 
HW spec
  bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE 
in STEv1
  11659ef8d28e net/mlx5: DR, Remove unneeded comments
  5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length 
(IHL)

  
  #dependencies:
  60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX
  8348b71ccd92 net/mlx5: Introduce software defined steering capabilities

  #depencecies:
  #SW STEERING DEBUG DUMP
  aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports 
it
  4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it
  cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers
  f59464e257bd net/mlx5: DR, Add support for matching on 
geneve_tlv_option_0_exist field
  09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1
  8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs
  0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters
  b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount
  e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type
  9222f0b27da2 net/mlx5: DR, Add support for dumping steering info
  7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param
  89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value
  08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node
  32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher
  c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_"
  84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher

  
  58a606dba708 net/mlx5: Introduce new uplink destination type

  455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param
  9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately

  #SW STEERING SF
  515ce2ffa621 net/mlx5: DR, init_next_match only if needed
  5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset'
  1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32
  11a45def2e19 net/mlx5: DR, Add support for SF vports
  c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs
  ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport 
caps
  dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0
  7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing 
MLX5_VPORT_UPLINK
  f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16
  c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1

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


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

[Kernel-packages] [Bug 1949186] Re: Missing Linux Kernel mitigations for 'SSB - Speculative Store Bypass' hardware vulnerabilities

2022-04-12 Thread Steve Beattie

Hi Ammar, apologies for the delayed followup, what is the version of the
kernel that you are seeing this with? I.E. what is the output of running
the command 'cat /proc/version_signature' where this is showing up?

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

Title:
  Missing Linux Kernel mitigations for 'SSB - Speculative Store Bypass'
  hardware vulnerabilities

Status in linux-aws package in Ubuntu:
  New

Bug description:
  The Greenbone Security Assistant reporting me the following:
  Summary
  The remote host is missing one or more known mitigation(s) on Linux Kernel
side for the referenced 'SSB - Speculative Store Bypass' hardware 
vulnerabilities.
  Detection Result

  The Linux Kernel on the remote host is missing the mitigation for the
  "spec_store_bypass" hardware vulnerabilities as reported by the sysfs
  interface:

  sysfs file checked| Kernel status 
(SSH response)
  

  /sys/devices/system/cpu/vulnerabilities/spec_store_bypass | Vulnerable

  Notes on the "Kernel status / SSH response" column:
  - sysfs file missing: The sysfs interface is available but the sysfs file for 
this specific vulnerability is missing. This means the kernel doesn't know this 
vulnerability yet and is not providing any mitigation which means the target 
system is vulnerable.
  - Strings including "Mitigation:", "Not affected" or "Vulnerable" are 
reported directly by the Linux Kernel.
  - All other strings are responses to various SSH commands.

  Product Detection Result
  Product

  cpe:/a:linux:kernel
  Method

  Detection of Linux Kernel mitigation status for hardware vulnerabilities 
(OID: 1.3.6.1.4.1.25623.1.0.108765)
  Log

  View details of product detection
  Detection Method
  Checks previous gathered information on the mitigation status reported
by the Linux Kernel.
  Details:

  Missing Linux Kernel mitigations for 'SSB - Speculative Store Bypass' ...
  OID: 1.3.6.1.4.1.25623.1.0.108842

  Version used: 2021-07-07T02:00:46Z

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


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

[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore

The change which introduces the issue also exists in
Impish(5.13.0-40.45) and would need the same fix. For Focal the fix
would be included in upstream stable v5.4.183 but that would not make it
into next cycle.

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

Title:
  xfrm interface cannot be changed anymore

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

Bug description:
  [Impact]

  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135

  It has been fixed upstream by this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0

  [Test Case]

  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
  root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#

  [Regression Potential]

  The patch is trivial, the potential regressions are low.

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


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

[Kernel-packages] [Bug 1968591] Re: xfrm interface cannot be changed anymore

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

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

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

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

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

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1968591

Title:
  xfrm interface cannot be changed anymore

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

Bug description:
  [Impact]

  An xfrm interface cannot be changed any more since Ubuntu-hwe-5.4-5.4.0-105. 
In fact, the regression has been introduced by this backport:
  https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=13a02539b135

  It has been fixed upstream by this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d0d95a1c2b0

  [Test Case]

  root@dut-vm:~# ip link add foo type xfrm if_id 1234 dev lo
  root@dut-vm:~# ip link change foo type xfrm if_id 1234 dev ntfp1
  Error: if_id must be non zero.
  root@dut-vm:~# uname -a
  Linux dut-vm 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  root@dut-vm:~#

  [Regression Potential]

  The patch is trivial, the potential regressions are low.

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


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

[Kernel-packages] [Bug 1967493] Re: pl2303 serial adapter not recognized

2022-04-12 Thread Po-Hsu Lin

Hello,
Maybe your PL2303 is using another chip,
can you please upload the dmesg output with this device attached?
Also the output of the following command with it connected:

lsusb -v

And in case you're using a PL2303GS chip, here is a test kernel:
https://people.canonical.com/~phlin/kernel/pl2303gs/

Which includes:
https://github.com/torvalds/linux/commit/5b6ab28d06780c87320ceade61698bb6719c85db

Thanks

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

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

Title:
  pl2303 serial adapter not recognized

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

Bug description:
  Hi

  After upgrading the Linux kernel from 5.11.0-27 to 5.13.0-37 a device
  that uses a pl2303 usb serial chip no longer works.

  This seems very similar to bug 1959110, and according to that it
  should be fixed, but somehow it's not.

  # uname -a
  Linux GAU23LD04 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15 
15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

  # journalctl -b -k -g pl2303 -o cat
  usbcore: registered new interface driver pl2303
  usbserial: USB Serial support registered for pl2303
  pl2303 1-12:1.0: pl2303 converter detected
  pl2303 1-12:1.0: unknown device type, please report to 
linux-...@vger.kernel.org

  # udevadm info /sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0 
  P: /devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
  L: 0
  E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
  E: DEVTYPE=usb_interface
  E: PRODUCT=67b/2303/300
  E: TYPE=0/0/0
  E: INTERFACE=255/0/0
  E: MODALIAS=usb:v067Bp2303d0300dc00dsc00dp00icFFisc00ip00in00
  E: SUBSYSTEM=usb
  E: USEC_INITIALIZED=56177916
  E: ID_VENDOR_FROM_DATABASE=Prolific Technology, Inc.
  E: ID_MODEL_FROM_DATABASE=PL2303 Serial Port
  E: ID_PATH=pci-:00:14.0-usb-0:12:1.0
  E: ID_PATH_TAG=pci-_00_14_0-usb-0_12_1_0
  E: ID_MM_TTY_MANUAL_SCAN_ONLY=1

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


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

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

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

apport-collect 1968311

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

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

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

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

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

Title:
  Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I tried installing multiple times, with the Beta version and daily
  2022-04-05. I was afraid it was driver related so I tried with and
  without installing 3rd party software.

  After unlocking the drive, I can watch what services are starting - it
  freezes right after "Started Thunderbolt system service." After a
  while it says "[drm]  CPU pipe a FIFO underrun." It always
  freezes at the same point and never boots.

  Jammy Jellyfish installed on EXT4 booted just fine on the Dell XPS 13.

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


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

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

2022-04-12 Thread Ubuntu SRU Bot

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

snapd/2.54.3+20.04.1ubuntu0.2 (amd64)
r8168/8.048.00-1ubuntu0.20.04.2 (amd64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1966499] Re: Recent 5.13 kernel has broken KVM support

** Changed in: linux (Ubuntu Impish)
   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/1966499

Title:
  Recent 5.13 kernel has broken KVM support

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

Bug description:
  [Impact]
  This is caused by commit 08335308 "KVM: x86: check PIR even for vCPUs
  with disabled APICv", this patch needs 7e1901f6c "KVM: VMX: prepare
  sync_pir_to_irr for running with APICv disabled" otherwise if APICv
  is disabled in this vcpu it will trigger warning messages in
  vmx_sync_pir_to_irr() of vmx.c:
  WARN_ON(!vcpu->arch.apicv_active);

  With warnings like:
  [ cut here ]
  WARNING: CPU: 13 PID: 6997 at arch/x86/kvm/vmx/vmx.c:6336 
vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel]
  ? xfer_to_guest_mode_work+0xe2/0x110
  Modules linked in: vhost_net vhost vhost_iotlb tap xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat 
nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter nf_tables 
nfnetlink bridge stp llc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm joydev input_leds ioatdma rapl 
intel_cstate efi_pstore ipmi_si mei_me mei mac_hid acpi_pad
  vcpu_run+0x4d/0x220 [kvm]
  acpi_power_meter sch_fq_codel ipmi_devintf ipmi_msghandler msr ip_tables 
x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid mgag200 
i2c_algo_bit drm_kms_helper crct10dif_pclmul syscopyarea crc32_pclmul 
sysfillrect sysimgblt ghash_clmulni_intel fb_sys_fops ixgbe cec aesni_intel 
rc_core crypto_simd xfrm_algo cryptd drm ahci dca i2c_i801 xhci_pci mdio 
libahci i2c_smbus lpc_ich xhci_pci_renesas wmi
  CPU: 13 PID: 6997 Comm: qemu-system-x86 Tainted: G W I 5.13.0-39-generic 
#44-Ubuntu
  Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS 
SE5C610.86B.01.01.1008.031920151331 03/19/2015
  kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm]
  RIP: 0010:vmx_sync_pir_to_irr+0x9e/0xc0 [kvm_intel]
  Code: e8 47 f5 18 00 8b 93 00 03 00 00 89 45 ec 83 e2 20 85 d2 74 dc 48 8b 55 
f0 65 48 2b 14 25 28 00 00 00 75 1d 48 8b 5d f8 c9 c3 <0f> 0b eb 87 f0 80 4b 39 
40 8b 93 00 03 00 00 8b 45 ec 83 e2 20 eb
  RSP: 0018:ae4d8d107c98 EFLAGS: 00010046
  RAX:  RBX: 99c552942640 RCX: 99c5043a72f0
  RDX: 99c552942640 RSI: 0001 RDI: 99c552942640
  RBP: ae4d8d107cb0 R08: 99c86f6a7140 R09: 00027100
  R10: 4228 R11: 000a R12: 99c552942640
  R13:  R14: ae4d8d1a63e0 R15: 99c552942640
  FS: 7f6ae9be7640() GS:99c86f68() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2:  CR3: 00010b8a6006 CR4: 001726e0
  Call Trace:
  
  kvm_vcpu_ioctl+0x243/0x5e0 [kvm]
  vcpu_enter_guest+0x383/0xf50 [kvm]
  ? xfer_to_guest_mode_work+0xe2/0x110
  ? kvm_vm_ioctl+0x364/0x730 [kvm]
  ? __fget_files+0x86/0xc0
  vcpu_run+0x4d/0x220 [kvm]
  __x64_sys_ioctl+0x91/0xc0
  do_syscall_64+0x61/0xb0
  ? fput+0x13/0x20
  ? exit_to_user_mode_prepare+0x37/0xb0
  ? syscall_exit_to_user_mode+0x27/0x50
  ? do_syscall_64+0x6e/0xb0
  ? syscall_exit_to_user_mode+0x27/0x50
  ? do_syscall_64+0x6e/0xb0
  ? do_syscall_64+0x6e/0xb0
  ? do_syscall_64+0x6e/0xb0
  entry_SYSCALL_64_after_hwframe+0x44/0xae
  RIP: 0033:0x7f6aebce1a2b
  Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 
1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 
c3 48 8b 0d d5 f3 0f 00 f7 d8 64 89 01 48
  RSP: 002b:7f6ae8ffe3f8 EFLAGS: 0246 ORIG_RAX: 0010
  RAX: ffda RBX: ae80 RCX: 7f6aebce1a2b
  RDX:  RSI: ae80 RDI: 000c
  RBP: 557d3b429b90 R08: 557d3a4ebff0 R09: 
  kvm_arch_vcpu_ioctl_run+0xc5/0x4f0 [kvm]
  R10: 0001 R11: 0246 R12: 
  R13: 0001 R14: 3000 R15: 
  
  ---[ end trace 5b722d71a78069b1 ]---

  This warning message will be flooding in system log files and
  eventually eat up all the disk space then crash the server.

  This issue will gone by either reverting it or adding the fixes below.

  Reference:
  
https://patchwork.kernel.org/project/kvm/patch/2028072531.1534938-1-pbonz...@redhat.com/

  [Fixes]
  * 0b8f11737 KVM: Add infrastructure and macro to mark VM as bugged
  * 673692735 KVM: x86: Use KVM_BUG/KVM_BUG_ON to handle bugs that are fatal to 
the VM
  * 7e1901f6c

[Kernel-packages] [Bug 1954832] Re: sctp: account for stream padding for reconf chunk

2022-04-12 Thread Steve Beattie

This has been fixed in all affected Ubuntu kernels, closing.

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

** Information type changed from Private Security to Public Security

** Changed in: linux (Ubuntu)
   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/1954832

Title:
  sctp: account for stream padding for reconf chunk

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  The missing account for stream padding may lead to the use of more buffer 
than was allocated buffer, causing a BUG_ON.

  [Potential regression]
  SCTP flows may stop working.

  [Test case]
  Run a privately shared test case.

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


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

[Kernel-packages] [Bug 1968235] Re: [i915] Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz

** Tags added: i915

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

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

Title:
  [i915] Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz

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

Bug description:
  I recently started using a Cable-Matters-201355 with my XPS 9380 (8th
  Gen TB3).  The dock supports dual 4K DP @ 60Hz via thunderbolt with PD
  input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4
  high speed lanes to get dual 60Hz)

  Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel
  output) however go blank just as wayland starts up.

  Unplugging one of them allows the other to appear at 3840x2160@60Hz,
  after which I have to execute the following process to get both up and
  running.

  1) Change the refresh rate of the active display to 30Hz, apply in Screen 
Display settings dialog
  2) Plug the 2nd monitor in; At this point both appear in Screen Display 
dialog @60Hz, but the 2nd remains blank
  3) Change both to 30Hz, apply; At this point the 2nd screen turns on
  4) Change both to 60Hz, apply; At this point both are working at 60Hz, my 
desired end state

  Inspection of edid seems fine (below), other than the DisplaySize
  showing 27" instead of 32". Monitors are identical.

  Previously, I might be able to script my steps above using xrandr, but
  that seems to no longer be the case with 21.10 and wayland. I seem to
  be limited to the Screen Display dialog.

  Since I can fix by simply re-applying the settings, it seems like a
  bug on startup.  If I could find a CLI option to allow me to script
  this somehow, that workaround would be just fine for myself.

  Lid open/closed, power via the 201344 or direct via other TB-PD port
  has no impact.

  Here's hoping for a bugfix in 22.04 or at least a way to script the
  display configuration.

  $ cat /sys/class/drm/card0-DP-4/edid | parse-edid
  Checksum Correct

  Section "Monitor"
   Identifier "LG HDR 4K"
   ModelName "LG HDR 4K"
   VendorName "GSM"
   # Monitor Manufactured week 5 of 2021
   # EDID version 1.4
   # Digital Display
   DisplaySize 600 340
   Gamma 2.20
   Option "DPMS" "true"
   Horizsync 30-135
   VertRefresh 56-61
   # Maximum pixel clock is 560MHz
   #Not giving standard mode: 1152x864, 60Hz
   #Not giving standard mode: 1280x1024, 60Hz
   #Not giving standard mode: 1280x720, 60Hz
   #Not giving standard mode: 1600x900, 60Hz
   #Not giving standard mode: 1920x1080, 60Hz
   #Not giving standard mode: 1280x800, 60Hz

   #Extension block found. Parsing...
   Modeline "Mode 6" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
   Modeline "Mode 0" 519.38 3840 3864 3880 3896 2160 2214 2219  +hsync 
-vsync
   Modeline "Mode 1" 266.64 3840 3848 3992 4000 2160 2214 2219  +hsync 
-vsync
   Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
   Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync 
+vsync
   Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
   Modeline "Mode 5" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
   Modeline "Mode 7" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync 
-vsync
   Option "PreferredMode" "Mode 6"
  EndSection

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


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

[Kernel-packages] [Bug 1968311] Re: Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13)

** Tags added: jammy

** Package changed: xorg (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/1968311

Title:
  Jammy Jellyfish beta doesn't boot with zfs + encryption (Dell XPS 13)

Status in linux package in Ubuntu:
  New

Bug description:
  I tried installing multiple times, with the Beta version and daily
  2022-04-05. I was afraid it was driver related so I tried with and
  without installing 3rd party software.

  After unlocking the drive, I can watch what services are starting - it
  freezes right after "Started Thunderbolt system service." After a
  while it says "[drm]  CPU pipe a FIFO underrun." It always
  freezes at the same point and never boots.

  Jammy Jellyfish installed on EXT4 booted just fine on the Dell XPS 13.

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


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

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

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

apport-collect 1968235

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

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

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

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

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

Title:
  [i915] Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz

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

Bug description:
  I recently started using a Cable-Matters-201355 with my XPS 9380 (8th
  Gen TB3).  The dock supports dual 4K DP @ 60Hz via thunderbolt with PD
  input. (HBR3 compliant USB-C Dock (DSC/DP1.4 support) that uses all 4
  high speed lanes to get dual 60Hz)

  Both displays boot mirrored when powered up (Dell Logo, Grub, Kernel
  output) however go blank just as wayland starts up.

  Unplugging one of them allows the other to appear at 3840x2160@60Hz,
  after which I have to execute the following process to get both up and
  running.

  1) Change the refresh rate of the active display to 30Hz, apply in Screen 
Display settings dialog
  2) Plug the 2nd monitor in; At this point both appear in Screen Display 
dialog @60Hz, but the 2nd remains blank
  3) Change both to 30Hz, apply; At this point the 2nd screen turns on
  4) Change both to 60Hz, apply; At this point both are working at 60Hz, my 
desired end state

  Inspection of edid seems fine (below), other than the DisplaySize
  showing 27" instead of 32". Monitors are identical.

  Previously, I might be able to script my steps above using xrandr, but
  that seems to no longer be the case with 21.10 and wayland. I seem to
  be limited to the Screen Display dialog.

  Since I can fix by simply re-applying the settings, it seems like a
  bug on startup.  If I could find a CLI option to allow me to script
  this somehow, that workaround would be just fine for myself.

  Lid open/closed, power via the 201344 or direct via other TB-PD port
  has no impact.

  Here's hoping for a bugfix in 22.04 or at least a way to script the
  display configuration.

  $ cat /sys/class/drm/card0-DP-4/edid | parse-edid
  Checksum Correct

  Section "Monitor"
   Identifier "LG HDR 4K"
   ModelName "LG HDR 4K"
   VendorName "GSM"
   # Monitor Manufactured week 5 of 2021
   # EDID version 1.4
   # Digital Display
   DisplaySize 600 340
   Gamma 2.20
   Option "DPMS" "true"
   Horizsync 30-135
   VertRefresh 56-61
   # Maximum pixel clock is 560MHz
   #Not giving standard mode: 1152x864, 60Hz
   #Not giving standard mode: 1280x1024, 60Hz
   #Not giving standard mode: 1280x720, 60Hz
   #Not giving standard mode: 1600x900, 60Hz
   #Not giving standard mode: 1920x1080, 60Hz
   #Not giving standard mode: 1280x800, 60Hz

   #Extension block found. Parsing...
   Modeline "Mode 6" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
   Modeline "Mode 0" 519.38 3840 3864 3880 3896 2160 2214 2219  +hsync 
-vsync
   Modeline "Mode 1" 266.64 3840 3848 3992 4000 2160 2214 2219  +hsync 
-vsync
   Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync 
+vsync
   Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync 
+vsync
   Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
   Modeline "Mode 5" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
   Modeline "Mode 7" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync 
-vsync
   Option "PreferredMode" "Mode 6"
  EndSection

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


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

[Kernel-packages] [Bug 1968235] Re: Dual DP 4K @60Hz requires toggling to 30Hz and back to 60Hz