[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout

[Po-Hsu Lin]

I found this is failing on X-4.4 as well. Since it's an ESM series now I
don't think we will fix it.

** Also affects: linux (Ubuntu Xenial)
   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/1932966

Title:
  kvm_unit_tests: emulator test fails on 4.15 kernel, timeout

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Our Bionic 4.15 kernel lacks of movups/movupd emulation support.

  With the following commit added into the emulator test in
  ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu 
Date: Wed Apr 21 16:12:57 2021 -0700

x86: add movups/movupd sse testcases to emulator.c

Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for 
movups/movupd").

Signed-off-by: Jacob Xu 
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini 

  It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd 
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490 
RSP=0051b470
R8 =000a R9 =03f8 R10=000d 
R11=
R12=e000 R13= R14=d000 
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010   00c09300 DPL=0 DS [-WA]
CS =0008   00a09b00 DPL=0 CS64 [-RA]
SS =0010   00c09300 DPL=0 DS [-WA]
DS =0010   00c09300 DPL=0 DS [-WA]
FS =0010   00c09300 DPL=0 DS [-WA]
GS =0010 0051a510  00c09300 DPL=0 DS [-WA]
LDT=   8200 DPL=0 LDT
TR =0080 0041207a  8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2= 
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03 
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)

  [Fix]
  * 29916968c48691 kvm: Add emulation for movups/movupd

  This patch can be cherry-picked into Bionic.

  It can fix our test failure plus, as mentioned in the commit message,
  emulation failures with openbsd as guest and with Windows 10 with
  intel HD graphics pass through.

  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/

  Run the emulator test from ubuntu_kvm_unit_tests, with this patch
  applied it will pass without any issue:
...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to 
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)

  [Where problems could occur]
  I didn't see any other patch that claims to be a fix of this one in
  the upstream tree. The problem I think of for the moment is that we
  might see other failures when using this in the future.


  [Original Bug Report]
  Found this on B/KVM, current cycle (sru-20210531):

  18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
  18:27:11 DEBUG| 

[Kernel-packages] [Bug 1894017] Re: Keyboard not working

[cipibad]

In my case it was the same behavior, but the cause was a kernel boot
parameter(acpi=noirq).

Added details on how I found it here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/comments/9

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

Title:
  Keyboard not working

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The laptop keyboard doesn't work at login or in the de. If I
  ctrl+alt+F3 from an external usb keyboard to a terminal the laptop
  keyboard works. An external usb keyboard works everywhere. The
  laptop's keyboard does work everywhere with the previous kernel
  5.4.0.42.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55
  Uname: Linux 5.4.0-45-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Sep  3 03:09:49 2020
  InstallationDate: Installed on 2019-08-07 (392 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency 
root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-lowlatency N/A
   linux-backports-modules-5.4.0-45-lowlatency  N/A
   linux-firmware   1.187.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago)
  dmi.bios.date: 03/13/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.57
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.30:bd03/13/2018:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.57:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.sku: M0B61EA#ACQ
  dmi.product.version: 097710405F00010420180
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1894012] Re: touchpad and keyboard

[cipibad]

In my case the keyboard on the laptop was working on GRUB/Recovery mode
but not on normal run.

I compared the kernel modules on the both runs and also did insmod/rmmod
to have the same list without any difference.

Then I went and compare kernel cmdline (/proc/cmdline) and update
arguments one by one and found the one causing the issue!

In my case it was acpi=noirq parameter to kernel boot. Removed it and
now both keyboard and touchpad are working properly.

** Attachment removed: "dmi.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+attachment/5521755/+files/dmi.txt

** Attachment removed: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+attachment/5521777/+files/version.log

** Attachment removed: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+attachment/5521756/+files/lspci-vnvn.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/1894012

Title:
  touchpad and keyboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I reinstalled Ubuntu on 20.04 version in my laptop on an SSD and the
  keyboard and touch-pad stopped working

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-45-generic 5.4.0-45.49
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jorge  1551 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  3 00:47:37 2020
  InstallationDate: Installed on 2020-09-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: CHUWI INNOVATION LIMITED AeroBook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic 
root=UUID=4259a678-3627-47b0-81a7-b8449ea7222c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-45-generic N/A
   linux-backports-modules-5.4.0-45-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YZ-BI-133-X133KR110-KJ66B-106-N
  dmi.board.asset.tag: Default string
  dmi.board.name: AeroBook
  dmi.board.vendor: CHUWI INNOVATION LIMITED
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: CHUWI INNOVATION LIMITED
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-133-X133KR110-KJ66B-106-N:bd09/20/2019:svnCHUWIINNOVATIONLIMITED:pnAeroBook:pvrDefaultstring:rvnCHUWIINNOVATIONLIMITED:rnAeroBook:rvrDefaultstring:cvnCHUWIINNOVATIONLIMITED:ct10:cvrDefaultstring:
  dmi.product.family: YZ106
  dmi.product.name: AeroBook
  dmi.product.sku: YZ106
  dmi.product.version: Default string
  dmi.sys.vendor: CHUWI INNOVATION LIMITED

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


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

[Kernel-packages] [Bug 1941030] Re: [Fujitsu Lifebook U7411] Screen Flickers

[Daniel van Vugt]

Thanks but unfortunately that's still missing any evidence of what has
hung. Please remember step 1 in comment #4 which is "Wait 10 seconds"
before rebooting. It may also help to use this to reboot:

  Alt + PrtScn + {R,E,I,S,U,B}

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

Title:
  [Fujitsu Lifebook U7411] Screen Flickers

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

Bug description:
  After the laptop goes to sleep mode, it starts to flicker when i try
  to use the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 25 10:10:33 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Client Computing Limited Device [1e26:0050]
  InstallationDate: Installed on 2021-08-18 (6 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7411
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=2ef2e3af-1c99-45d0-8bdf-5c9bd7e07ab9 ro quiet splash pcie_aspm=off 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/28/2021
  dmi.bios.release: 2.21
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.21
  dmi.board.name: FJNB2E7
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: A3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.21:bd06/28/2021:br2.21:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7411:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:
  dmi.product.family: LIFEBOOK-FPCA
  dmi.product.name: LIFEBOOK U7411
  dmi.product.sku: SK01
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Kernel-packages] [Bug 1942160] Re: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms

[Alex Tu]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  VMD PCI-E bridges on ADL-M/P/S use new device IDs and therefore not
  covered by previous LTR reset fix in bug 1896598.

  [Fix]

  Additional entires to vmd_bridge_tbl in drivers/pci/quirks.c is
  requierd:
  * ADL-M: [8086:464d]
  * ADL-P: [8086:51b0]
  * ADL-S: [8086:7ab4]

  [Test Case]

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  ...
  1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode])
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express])
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+

  [Where problems could occur]

  This will reset zeroed PCI_LTR_MAX_SNOOP_LAT and PCI_LTR_MAX_NOSNOOP_LAT
  values to a fixed 3145728ns that is used on Windows. Devices might want
  to set itself to a smaller value, but while this is not yet correctly
  supported by VMD controller driver, so the device power consumption
  might be little worse than ideal.

  [Other Info]

  VMD ASPM was first supported for Tiger Lake cpus, so all kernel versions
  newer than 5.6 should have already the supporting function. This patch
  targets Alder Lake cpus that are supported since 5.10-oem and on.

  == original bug report ==

  * ADL-M:

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05)
  Kernel driver in use: pcieport
  1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device 
[8086:f1aa] (rev 03)
  Subsystem: Intel Corporation Device [8086:390f]
  Kernel driver in use: nvme
  Kernel modules: nvme

  * ADL-P:

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  * ADL-S:

  $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)'
  1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
  1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express])
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384, 
https://bugs.launchpad.net/bugs/1896598.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1100 F pulseaudio
  CasperMD5CheckResult: skip
  Dependencies:

  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-04-06 (146 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0032 Intel Corp.
   Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.16+staging.11 [origin: unknown]
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem 
root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-9010-oem N/A
   

[Kernel-packages] [Bug 1940629] Re: Support Jasper Lake

[Andy Chi]

Install 1.9.1-1ubuntu0.6 on focal and test on Jasper Lake CPU. Below is
log from thermald.

● thermald.service - Thermal Daemon Service
 Loaded: loaded (/lib/systemd/system/thermald.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Wed 2021-09-01 12:22:23 CST; 6min ago
   Main PID: 651 (thermald)
  Tasks: 2 (limit: 9167)
 Memory: 5.9M
 CGroup: /system.slice/thermald.service
 └─651 /usr/sbin/thermald --systemd --dbus-enable --adaptive


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

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

Title:
  Support Jasper Lake

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

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

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


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

[Kernel-packages] [Bug 1940204] Re: AMDGPU: Fix System hang after resume from suspend

[koba]

Verified with 5.13-oem-1011.

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

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

Title:
  AMDGPU: Fix System hang after resume from suspend

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

Bug description:
  [Impact]
  With AMD-GPU and don't use it as a display output,
  After multiple Suspend, system would hang.

  [Fix]
  Disable BACO for polaris12 series.
  BACO allow the graphics cards on Linux to support S4 / hibernation support. 

  [Test Case]
  1. Must plug AMD GPU and don't use it as display output
  2. Plug DP/HDMI on iGPU.
  3. Suspend machine.
  4. check if system hangs.

  [Where problems could occur]
  Disable BACO would cause higher power consumption.

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


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

Re: [Kernel-packages] [Bug 1941030] Re: [Fujitsu Lifebook U7411] Screen Flickers

[Urpan Adhikari]

Hi Daniel,

It just happened right now.

FYI

On Mon, Aug 30, 2021 at 1:56 PM Urpan Adhikari 
wrote:

> Hi Daniel,
>
> Surprisingly, it's not happening at the moment. I will keep monitoring and
> send the log if/when it happens.
> 2 of my office colleagues are also using the same laptop and were
> experiencing the issue. let me also check with them if they are facing the
> same issue after the grub update.
>
> Thanks lot for your help and support
>
> On Mon, Aug 30, 2021 at 1:05 PM Daniel van Vugt <
> 1941...@bugs.launchpad.net> wrote:
>
>> Thanks but that doesn't seem to show a hang. That log shows the system
>> just shut down cleanly.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1941030
>>
>> Title:
>>   [Fujitsu Lifebook U7411] Screen Flickers
>>
>> Status in linux-hwe-5.11 package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   After the laptop goes to sleep mode, it starts to flicker when i try
>>   to use the laptop.
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: xorg 1:7.7+19ubuntu14
>>   ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
>>   Uname: Linux 5.11.0-27-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu27.18
>>   Architecture: amd64
>>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>>   CasperMD5CheckResult: skip
>>   CompositorRunning: None
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Wed Aug 25 10:10:33 2021
>>   DistUpgraded: Fresh install
>>   DistroCodename: focal
>>   DistroVariant: ubuntu
>>   ExtraDebuggingInterest: Yes, if not too technical
>>   GraphicsCard:
>>Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA
>> controller])
>>  Subsystem: Fujitsu Client Computing Limited Device [1e26:0050]
>>   InstallationDate: Installed on 2021-08-18 (6 days ago)
>>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
>> (20210209.1)
>>   MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7411
>>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic
>> root=UUID=2ef2e3af-1c99-45d0-8bdf-5c9bd7e07ab9 ro quiet splash
>> pcie_aspm=off vt.handoff=7
>>   SourcePackage: xorg
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 06/28/2021
>>   dmi.bios.release: 2.21
>>   dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
>>   dmi.bios.version: Version 2.21
>>   dmi.board.name: FJNB2E7
>>   dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
>>   dmi.board.version: A3
>>   dmi.chassis.type: 10
>>   dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
>>   dmi.modalias:
>> dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.21:bd06/28/2021:br2.21:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7411:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:
>>   dmi.product.family: LIFEBOOK-FPCA
>>   dmi.product.name: LIFEBOOK U7411
>>   dmi.product.sku: SK01
>>   dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED
>>   version.compiz: compiz N/A
>>   version.libdrm2: libdrm2 2.4.105-3~20.04.1
>>   version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
>>   version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
>>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
>>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
>> 2:2.99.917+git20200226-1
>>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
>> 1:1.0.16-1
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1941030/+subscriptions
>>
>>


** Attachment added: "prevboot_after_reboot.txt"
   
https://bugs.launchpad.net/bugs/1941030/+attachment/5522065/+files/prevboot_after_reboot.txt

** Attachment added: "prevboot_before_reboot.txt"
   
https://bugs.launchpad.net/bugs/1941030/+attachment/5522066/+files/prevboot_before_reboot.txt

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

Title:
  [Fujitsu Lifebook U7411] Screen Flickers

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

Bug description:
  After the laptop goes to sleep mode, it starts to flicker when i try
  to use the laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 25 10:10:33 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  

[Kernel-packages] [Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected

[Chris Chiu]

There's so build problem with 5.14.0-rc1. Could you try
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.13/? Thanks.

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

Title:
  Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock
  connected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  My laptop run well with last 5.4 linux kernel even if I connect my
  thunderbolt dock.

  When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock
  and 2 monitors connected, the kernel panic after 3 or 4 seconds.
  Without the dock, he work fine.

  After a lot of try, I was able to boot sometime on 5.11 with the dock, but 
randomly and only if I only connect 1 extra monitor (I usually use two).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jmaillar   1988 F pulseaudio
   /dev/snd/controlC1:  jmaillar   1988 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  MachineType: Dell Inc. Precision 7530
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.15
  Tags:  focal
  Uname: Linux 5.11.0-27-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-20 (483 days ago)
  UserGroups: adm audio cdrom dip disk input kismet kvm libvirt libvirtd 
lpadmin lxd netdev plugdev sambashare sudo systemd-network users vboxusers 
video wireshark
  _MarkForUpload: True
  dmi.bios.date: 05/25/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.1
  dmi.board.name: 0425K7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.1:bd05/25/2021:br1.16:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0831
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345

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


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

[Kernel-packages] [Bug 1942271] [NEW] Spontaneous NVIDIA panic

[Kevin McMurtrie]

Public bug reported:

All graphics and USB devices spontaneously halted.
SSH, networking, and filesystems remained working.
Xorg stuck and can not exit even after ABRT signal.
"shutdown" command never completed.


Aug 31 18:17:12 fuel kernel: [ 3494.973431] BUG: unable to handle page fault 
for address: 00020018
Aug 31 18:17:12 fuel kernel: [ 3494.973436] #PF: supervisor read access in 
kernel mode
Aug 31 18:17:12 fuel kernel: [ 3494.973438] #PF: error_code(0x) - 
not-present page
Aug 31 18:17:12 fuel kernel: [ 3494.973439] PGD 0 P4D 0 
Aug 31 18:17:12 fuel kernel: [ 3494.973442] Oops:  [#1] SMP NOPTI
Aug 31 18:17:12 fuel kernel: [ 3494.973444] CPU: 2 PID: 33911 Comm: chrome 
Tainted: P   OE 5.11.0-31-generic #33-Ubuntu
Aug 31 18:17:12 fuel kernel: [ 3494.973447] Hardware name: Gigabyte Technology 
Co., Ltd. Default string/X99P-SLI-CF, BIOS F25b 03/13/2018
Aug 31 18:17:12 fuel kernel: [ 3494.973448] RIP: 0010:_nv028963rm+0x35/0x90 
[nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.973792] Code: 57 10 31 c0 48 85 d2 74 2e 48 
8b 4f 08 31 c0 48 85 c9 74 0d 48 63 41 14 48 89 d6 48 29 c6 48 89 f0 48 3b 57 
18 48 89 07 74 1b <48> 8b 42 08 48 89 47 10 b8 01 00 00 00 48 83 c4 08 c3 66 0f 
1f 84
Aug 31 18:17:12 fuel kernel: [ 3494.973795] RSP: 0018:b11742f43bd0 EFLAGS: 
00010203
Aug 31 18:17:12 fuel kernel: [ 3494.973797] RAX: 00020010 RBX: 
9c819c336c30 RCX: 9c7e48cec978
Aug 31 18:17:12 fuel kernel: [ 3494.973798] RDX: 00020010 RSI: 
00020010 RDI: 9c7cf6695d20
Aug 31 18:17:12 fuel kernel: [ 3494.973800] RBP: 9c7cf6695d20 R08: 
0020 R09: 9c7cf6695d28
Aug 31 18:17:12 fuel kernel: [ 3494.973801] R10:  R11: 
 R12: 9c7d3d867738
Aug 31 18:17:12 fuel kernel: [ 3494.973802] R13: 9c7e1c027060 R14: 
9c7cf6695d98 R15: 9c819c336c30
Aug 31 18:17:12 fuel kernel: [ 3494.973804] FS:  () 
GS:9c8bcfc8() knlGS:
Aug 31 18:17:12 fuel kernel: [ 3494.973806] CS:  0010 DS:  ES:  CR0: 
80050033
Aug 31 18:17:12 fuel kernel: [ 3494.973807] CR2: 00020018 CR3: 
0006dcc10005 CR4: 003706e0
Aug 31 18:17:12 fuel kernel: [ 3494.973809] DR0:  DR1: 
 DR2: 
Aug 31 18:17:12 fuel kernel: [ 3494.973810] DR3:  DR6: 
fffe0ff0 DR7: 0400
Aug 31 18:17:12 fuel kernel: [ 3494.973811] Call Trace:
Aug 31 18:17:12 fuel kernel: [ 3494.973814]  ? _nv035844rm+0xa8/0xe0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.974111]  ? _nv014655rm+0x2ee/0x770 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.974414]  ? _nv037695rm+0xb3/0x150 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.974719]  ? _nv037694rm+0x297/0x4e0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975018]  ? _nv037689rm+0x60/0x70 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975317]  ? _nv037690rm+0x7b/0xb0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975618]  ? _nv036056rm+0x40/0xe0 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.975840]  ? _nv000699rm+0x68/0x80 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976092]  ? 
rm_cleanup_file_private+0xea/0x160 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976341]  ? fsnotify+0x23c/0x2f0
Aug 31 18:17:12 fuel kernel: [ 3494.976347]  ? nvidia_close+0x156/0x320 [nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976539]  ? nvidia_frontend_close+0x2f/0x50 
[nvidia]
Aug 31 18:17:12 fuel kernel: [ 3494.976728]  ? __fput+0x9f/0x250
Aug 31 18:17:12 fuel kernel: [ 3494.976731]  ? fput+0xe/0x10
Aug 31 18:17:12 fuel kernel: [ 3494.976733]  ? task_work_run+0x6d/0xa0
Aug 31 18:17:12 fuel kernel: [ 3494.976738]  ? do_exit+0x233/0x3e0
Aug 31 18:17:12 fuel kernel: [ 3494.976742]  ? do_group_exit+0x3b/0xb0
Aug 31 18:17:12 fuel kernel: [ 3494.976744]  ? __x64_sys_exit_group+0x18/0x20
Aug 31 18:17:12 fuel kernel: [ 3494.976747]  ? do_syscall_64+0x38/0x90
Aug 31 18:17:12 fuel kernel: [ 3494.976749]  ? 
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Aug 31 18:17:12 fuel kernel: [ 3494.976754] Modules linked in: ipt_REJECT 
nf_reject_ipv4 xt_multiport nft_compat nft_counter nf_tables libcrc32c 
nfnetlink ccm md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc 
snd_hda_codec_hdmi intel_rapl_msr intel_rapl_common snd_hda_codec_realtek 
snd_hda_codec_generic zfs(PO) ledtrig_audio snd_hda_intel snd_intel_dspcfg 
soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec 
x86_pkg_temp_thermal zunicode(PO) intel_powerclamp snd_hda_core zzstd(O) 
snd_hwdep coretemp soundwire_bus zlua(O) snd_soc_core kvm_intel nls_iso8859_1 
zavl(PO) icp(PO) snd_compress ac97_bus snd_pcm_dmaengine snd_pcm kvm 
snd_seq_midi zcommon(PO) snd_seq_midi_event znvpair(PO) crct10dif_pclmul spl(O) 
joydev input_leds snd_rawmidi ghash_clmulni_intel snd_seq snd_seq_device 
aesni_intel snd_timer crypto_simd cryptd glue_helper snd rapl mei_me 
intel_cstate efi_pstore mxm_wmi mei soundcore intel_wmi_thunderbolt mac_hid 

[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[Launchpad Bug Tracker]

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

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

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1933388] Re: SR-IOV broken in Ubuntu 20.04.2 LTS

[Launchpad Bug Tracker]

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

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

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

Title:
  SR-IOV broken in Ubuntu 20.04.2 LTS

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  SR-IOV does not work since Ubuntu Server 18.04.2 LTS, once the HWE
  kernel (4.18.0-15 generic x86_64)) has been installed on that version.
  Please also see ticket:
  https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1818400

  This bug report was created for Ubuntu 20.04.02 LTS, since the kernel
  for the previous bug report is no longer being supported and a
  developer requested us to make a new bug report for the new Ubuntu
  version...

  Environment:
  Windows Server 2019
  Fresh Hyper-V generation 2 VM (configuration version 9.0)
  SR-IOV enabled on the virtual switch (Intel I350-T2 physical network adapter)
  SR-IOV enabled on the virtual network card of the VM

  Steps to reproduce:
  Install Ubuntu Server 20.04.2 LTS
  Verify SR-IOV is enabled in the Networking tab of the Hyper-V manager

  Check SR-IOV status in the Networking tab of the Hyper-V manager. It
  will show status degraded (SR-IOV not operational)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-1033-azure 5.8.0-1033.35~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-1033.35~20.04.1-azure 5.8.18
  Uname: Linux 5.8.0-1033-azure x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jun 23 23:00:26 2021
  InstallationDate: Installed on 2020-09-15 (281 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-azure-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Ubuntu SRU Bot]

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

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, ppc64el, arm64)
evdi/1.9.1-1ubuntu4~20.04.1 (ppc64el)
linux-hwe-5.8/5.8.0-64.72 (amd64, ppc64el, arm64, s390x)


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-hwe-5.8

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

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

[jazir malik]

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

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

Title:
  Touchpad not working with ASUS TUF F15

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

Bug description:
  == SRU Justification ==

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

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

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

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

  == Original Bug Report ==

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

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

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

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

  Output of xinput

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

  Output of lspci

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

[Kernel-packages] [Bug 1942260] [NEW] compress firmware in /lib/firmware

[Glenn Washburn]

Public bug reported:

Some facts:
 - The linux kernel has supported loading xz compressed firmware since 5.3
 - The size of /lib/firmware in impish is ~650Mb (and growing)
 - The compressed size of firmware could be ~230Mb

It would be nice to install compressed firmware to save space.

Here are the plans from the Fedora project:
https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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

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

Title:
  compress firmware in /lib/firmware

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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


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

[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update

[Mike E.]

Just to add a little more information, I have the same issue with a HP
ProBook 450 G6 with an i7-8565U processor.  I am running 20.04 and have
had to stick with the 5.8.0-55-generic kernel because anything newer
(e.g. 5.8.0-59-generic) causes this bug to rear its ugly head.  I can
set GRUB_CMDLINE_LINUX_DEFAULT="nomodeset" in the /etc/default/grub file
and get the main monitor to display, but then external monitors no
longer work.

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

Title:
  Black screen on boot after stable update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system
  boots into black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-18-generic 5.11.0-18.19
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 1374 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 26 11:55:00 2021
  InstallationDate: Installed on 2021-05-02 (55 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HP HP Pavilion Laptop 15-eg0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic 
root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-18-generic N/A
   linux-backports-modules-5.11.0-18-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2021
  dmi.bios.release: 15.12
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 87CB
  dmi.board.vendor: HP
  dmi.board.version: 34.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 34.27
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg0xxx
  dmi.product.sku: 2Q2T4EA#AKD
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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


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

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-hwe-5.11 
(5.11.0.34.36~20.04.13) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/245.4-4ubuntu3.11 (s390x, ppc64el, amd64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (ppc64el, amd64, arm64)
nvidia-graphics-drivers-340/340.108-0ubuntu5.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-hwe-5.11

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Impish:
  Incomplete

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

  [   11.581774] R10: 0006 R11: 0246 R12: 
7f7fb47683fe
  [   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 
5624b2096cd0
  [   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel 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 hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear ast drm_vram_helper 
i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul drm_kms_helper crc32_pclmul 
syscopyarea sysfillrect 

[Kernel-packages] [Bug 1923335] Re: [i915] At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 and later)

[Norbert]

This version work for me.

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

Title:
  [i915] At shutdown the spinner logo disappears and a second later it
  comes back frozen for a while (in kernel 5.11 and later)

Status in linux package in Ubuntu:
  Won't Fix
Status in plymouth package in Ubuntu:
  In Progress
Status in plymouth package in Fedora:
  Unknown

Bug description:
  At shutdown the spinner logo disapear and a scond later it comes back and 
stay for 15sec. When I remove "splash" from the grub commandline the shutdown 
is fast (no extra 15 sec.). I can't find any hints in the log. It seem to 
happen after the log stopped.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-01-29 (71 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210129)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:568c Realtek Semiconductor Corp. Integrated 
Webcam HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5580
  Package: plymouth 0.9.5-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=469b1c18-e632-4872-a47c-7b36bce081dc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Tags:  wayland-session hirsute
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 5.11.0-13-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: 09/25/2020
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.2
  dmi.board.name: 00C013
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.2:bd09/25/2020:br1.18:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn00C013:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5580
  dmi.product.sku: 07A8
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1925261] Re: memory leak on AWS kernels when using docker

[Paul Friel]

Tim,

We are running Ubuntu 18.04 with the 5.3.0-1030-aws kernel because that
is the last Ubuntu provided AMI (ubuntu-
bionic-18.04-amd64-server-20200716) that does not contain this kernel
bug. I tried installing the latest supported Ubuntu 18.04 kernel again
yesterday (5.4.0-1055-aws) and verified that the bug still exists.

Today I confirmed that installing the linux-image-5.11.0-1016-aws focal
kernel from https://packages.ubuntu.com/focal-updates/linux-
image-5.11.0-1016-aws on a Ubuntu 18.04 instance does fix this issue for
us. My understanding from https://ubuntu.com/about/release-cycle#ubuntu-
kernel-release-cycle is this configuration isn't really
supported/suggested though, right? We would prefer to use the fully
supported Ubuntu 18.04 AWS kernel if possible.

Thanks,
Paul

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

Title:
  memory leak on AWS kernels when using docker

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

Bug description:
  Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu
  AMI was released which has the "5.3.0-1032-aws" kernel we have been
  hitting a 100% repro memory leak that causes our app that is running
  under docker to be OOM killed.

  The scenario is that we have an app running in a docker container and
  it occasionally catches a crash happening within itself and when that
  happens it creates another process which triggers a gdb dump of that
  parent app. Normally this works fine but under these specific kernels
  it causes the memory usage to grow and grow until it hits the maximum
  allowed memory for the container at which point the container is
  killed.

  I have tested using several of the latest available Ubuntu AMIs
  including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which
  has the "5.4.0-1045-aws" kernel and the bug still exists.

  I also tested a bunch of the mainline kernels and found the fix was
  introduced for this memory leak in the v5.9-rc4 kernel
  (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES).

  Do you all have any idea if or when that set of changes will be
  backported into a supported kernel for Ubuntu 18.04 or 20.04?

  Release we are running:
  root@:~# lsb_release -rd
  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  Docker / containerd.io versions:
  - containerd.io: 1.4.4-1
  - docker-ce: 5:20.10.5~3-0~ubuntu-bionic

  Latest supported kernel I tried which still sees the memory leak:
  root@hostname:~# apt-cache policy linux-aws
  linux-aws:
    Installed: 5.4.0.1045.27
    Candidate: 5.4.0.1045.27
    Version table:
   *** 5.4.0.1045.27 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu 
bionic-updates/main amd64 Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   4.15.0.1007.7 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 
Packages

  Thanks,
  Paul

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


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

[Kernel-packages] [Bug 1941955] Re: New upstream release 2021.08.28

[Launchpad Bug Tracker]

This bug was fixed in the package wireless-regdb - 2021.08.28-0ubuntu1

---
wireless-regdb (2021.08.28-0ubuntu1) impish; urgency=medium

  * New upstream version 2021.08.28 (LP: #1941955)

 -- Seth Forshee   Sat, 28 Aug 2021 11:56:48 -0500

** Changed in: wireless-regdb (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  New upstream release 2021.08.28

Status in wireless-regdb package in Ubuntu:
  Fix Released
Status in wireless-regdb source package in Bionic:
  In Progress
Status in wireless-regdb source package in Focal:
  In Progress
Status in wireless-regdb source package in Hirsute:
  In Progress
Status in wireless-regdb source package in Impish:
  Fix Released

Bug description:
  [Impact]

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

  [Test Case]

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

  [Where problems could occur]

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

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


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

[Kernel-packages] [Bug 1940629] Re: Support Jasper Lake

[Brian Murray]

Hello Andy, or anyone else affected,

Accepted thermald into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/1.9.1-1ubuntu0.6 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Support Jasper Lake

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

Bug description:
  [Impact]

   * Support thermald on Jasper Lake CPU.

   *

  [Test Plan]

   * Use a machine with a Jasper Lake cpu.

   * systemctl status thermald

   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware.

  [Other Info]
   
   * https://github.com/intel/thermal_daemon/issues/309

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


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

[Kernel-packages] [Bug 1942181] Re: Add support for AlderLake CPUs

[Brian Murray]

Hello Colin, or anyone else affected,

Accepted thermald into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/1.9.1-1ubuntu0.6 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: thermald (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  Add support for AlderLake CPUs

Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Focal:
  Fix Committed
Status in thermald source package in Hirsute:
  New
Status in thermald source package in Impish:
  In Progress

Bug description:
  [Impact]

   * Support thermald on AlderLake CPUs.

  [Test Plan]

   * Use a machine with a AlderLake CPUs
   * systemctl status thermald
   * Status of thermald should be `running`

  [Where problems could occur]

   * This change is to support Jasper Lake in thermald, which won't
  impact other hardware because the changes match on the CPU model ID.

  [Other Info]

  Supported added with:
   * 
https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4
   * 
https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2

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


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

Re: [Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

[cedric]

Hi,

This one works correctly.

Regards

Cédric

On 8/31/21 5:33 PM, Chris Chiu wrote:
> Thanks. We still have 3~4 versions to try and make sure which commit cause 
> the panic.
> Please try https://people.canonical.com/~mschiu77/lp1941773/989b27104a97/ and 
> let me know the result. Thanks.
>

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

Title:
  kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do not know how to find information to help debug.
  The laptop is lenovo E15 with latest BIOS 1.13

  kubuntu 21.04

  laptop boots correctly with 5.13.8 and trackpad works.
  with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (13 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (14 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline

[Frank Heimes]

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Fix Committed

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

** No longer affects: linux (Ubuntu Hirsute)

** No longer affects: linux (Ubuntu Impish)

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

Title:
  CryptoExpress EP11 cards are going offline

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

Bug description:
  SRU Justification:

  [Impact]

  * With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
  go offline in case of unknown error indications from the hardware.

  * This does not only lead to a software fallback, but can also lead to errors 
and crashes,
if certain crypto operations are currently ongoing.

  * A rework of the AP bus and zcrypt device driver, as it was done in
  5.11, fixes the situation.

  * From the below range of commits, the last 1/3 are the ones that fix the 
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.

  * In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with 
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above), 
the risk would increase,
increased effort to maintain and less test coverage.

  [Fix]

  * The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4 
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618

  [Test Case]

  * An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and 
accelerator mode.

  * Run stress test on these three CryptoExpress adapters.

  * IBM has such stress tests and ran these based on a patched Ubuntu 20.04 
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.

  * Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.

  * An application exists that generates such messages and thus tests
  these error paths.

  * Canonical's focus will mainly be on regression testing.

  [Regression Potential]

  * Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.

  * But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)

  * The crypto-specific tools (located at the s390-tools package) may no longer 
work with this patched driver.
But this got tested by IBM with the result that the changes are fully 
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control 
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly 
covered by this patch set.

  * The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).

  * Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or 
example memory leaks.
However, this is not unique to this patch set, it the same for upstream, 
Hirsute and Impish (and other distros).

  * The patches are all upstream and all needed upstream commits could just be 
cherry-picked,
hence no modifications were needed.

  * So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see 
comment below) for further testing.

  * This patch set was also tested on 5.11, where two issues were found
  that are already part of this set.

  [Other]

  * I iterated through all commits and found that that the latest ones got 
upstream with 5.13,
hence Impish includes all commits needed and is not affected!

  * Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not 
affected!

  * But non of the commits could be found in current Focal master-next (aot: 
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
  __

  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with 

[Kernel-packages] [Bug 1931565] Re: pull in latest thermald bug fixes into thermald

[Brian Murray]

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

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

Title:
  pull in latest thermald bug fixes into thermald

Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Focal:
  Fix Released
Status in thermald source package in Hirsute:
  Fix Released

Bug description:
  == SRU Justification [ HIRSUTE ] ==

  The upstream thermald 2.4.6 has been released with some more bug fixes
  that are pertinent to H/W available in older releases such as Hirsute.
  These fix a variety of issues found on H/W in the field and such as
  over-throttling, handling alternate ACPI object names for B0D4,
  handling trip zones which may have wrong settings and disabling the
  legacy rapl cdev when rapl-mmio is available.

  == The fixes ==

  Pull in these fixes:

  From 2.4.6:

  commit 273a53a11da2a7302ad7a5bc7e3bf04f221ce4e2
  Author: Srinivas Pandruvada 
  Date:   Mon Jun 7 16:47:47 2021 -0700

  Use Adaptive PPCC limits for RAPL MMIO

  Set the correct device name as RAPL-MSR so that RAPL-MMIO can
  also set the correct default power limits.

  commit 2dd67300448fa4a2aa8f3e00ee5b604c73a1f7d9
  Author: Srinivas Pandruvada 
  Date:   Mon Jun 7 16:45:14 2021 -0700

  Increase power limit for disabled RAPL-MMIO

  Increase 100W to 200W as some desktop platform already have limit
  more than 100W.

  commit 3de1004a49d0d157573bbdc1097b2fbed056879f
  Author: Srinivas Pandruvada 
  Date:   Sun Jun 6 19:19:15 2021 -0700

  Special case for default PSVT

  When there are no adaptive tables and only one default PSVT table
  is present with just one entry with MAX type. Add one additional
  entry as done for non default case.

  From 2.4.5:

  commit 301a89284e9d74a9a1f8315c1673a548dcacda8c
  Author: Srinivas Pandruvada 
  Date:   Sat May 29 10:50:44 2021 -0700

  Set a very high RAPL MSR PL1 with --adaptive

  After upgrading Dell Latitude 5420, again noticed performance degradation.
  The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we
  disable MSR RAPL with --adaptive option, it is not getting disabled. So
  MSR RAPL limits still playing role.

  To fix that set a very high MSR RAPL PL1 limit so that it never causes
  throttling. All throttling with --adaptive option is done using RAPL-MMIO.

  From 2.4.4:

  commit ea4491971059259e46daad10ae850d3d530b02f2
  Author: Srinivas Pandruvada 
  Date:   Thu Mar 11 10:06:15 2021 -0800

  Fix error for condition names

  The current code caps the max name as the last condition name,
  which is "Power_Slider". So any condition more than 56 will be
  printing error, with "Power_Slider" as condition name. For example
  for condition = 57:
  Unsupported condition 57 (Power_slider)

  This is confusing during debug, so print "UNKNOWN" for condition
  name 56.

  commit 9115f2fb0b296a22a62908f2718ca873af2a452f
  Author: Srinivas Pandruvada 
  Date:   Tue Mar 9 16:36:13 2021 -0800

  This is confusing during debug, so print "UNKNOWN" for condition
  name 56.

  commit 9115f2fb0b296a22a62908f2718ca873af2a452f
  Author: Srinivas Pandruvada 
  Date:   Tue Mar 9 16:36:13 2021 -0800

  Check for alternate names for B0D4 device

  B0D4 can be named as TCPU or B0D4. So search for both names
  if failed to find one.

  commit 660ee6f1f6351e6c291c0699147231be402c2bb8
  Author: Srinivas Pandruvada 
  Date:   Tue Mar 9 16:33:08 2021 -0800

  Delete all trips from zones before psvt install

  Initially zones has all the trips from sysfs, which may have wrong
  settings. Instead of deleting only for matched psvt zones, delete
  for all zones. In this way only zones which are in PSVT will be
  present.

  commit 1ad03424f7f3d339521635f08377b323375b2747
  Author: Srinivas Pandruvada 
  Date:   Tue Mar 9 11:36:27 2021 -0800

  Disable legacy rapl cdev when rapl-mmio is in use

  Explicitly disable legacy rapl based on MSR interface when rapl-mmio
  is in use. This will prevent PL1/PL2 power limit from MSR based rapl,
  which may not be the correct one.

  commit 45832e16290fec7353513b1ce03533b73b18f0c6
  Author: Colin Ian King 
  Date:   Thu Mar 18 11:22:38 2021 +

  Fix spelling mistakes found using codespell

  There are a handful of spelling mistakes in comments and literal
  strings found by codespell. Fix these.

  Signed-off-by: Colin Ian King 

  == Test plan ==

  Actually this is problematic as the changes affect different H/W in
  different ways and testing to touch all these changes requires full
  CPU exercising to try and trip thermal overrun.

  test plan is as follows:

  1. install -proposed thermald, run with debug logging enabled
  2. run 

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

[Northwest Grid]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1942008/+attachment/5521926/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521923/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

[Ubuntu SRU Bot]

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

glibc/2.33-0ubuntu5 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#linux-meta-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:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic

[alex dekker]

Installed linux-image-5.11.0-34-generic from proposed. It seems to fix
the issue with graphics distortion from the decryption prompt onwards.
Unfortunately it doesn't work very well after that. There is a message
on the screen about something having failed and automatic reporting
being enabled. There is no desktop. If I log in, there are no NICs, so
something  is fundamentally wrong.

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

Title:
  Wobbly graphics on built-in display since linux-
  image-5.11.0-22-generic

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

Bug description:
  == SRU Justification ==

  [Impact]
  Wobbly graphics after a kernel update. 

  [Fix]
  Older panels may require more bandwidth then advertised, so we need to
  use max params for them.

  [Test]
  Multiple users tested with positive result.

  [Where problems could occur]
  This patch reverts to the old behavior, which is to use max parameters,
  for older panels. If there's any new panel reports with older DP
  version, this might change the behavior on it.

  == Original Bug Report ==

  Lenovo laptop with Intel + Nvidia graphics.

  Since booting from  linux-image-5.11.0-22-generic, the built-in display is 
unusable, with wobbling horizontal stripes from the disk decryption prompt 
onwards:
  https://www.youtube.com/watch?v=LyRTuPzCe2I
  HDMI output works fine.

  If I boot from linux-image-5.11.0-18-generic instead, all is well.
  If I use Recovery mode with linux-image-5.11.0-22-generic and continue 
bootup, it's usable but there's no HDMI output.

  I think others may be having this issue too:
  
https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base#

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-22-generic 5.11.0-22.23
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   1598 F pulseaudio
   /dev/snd/controlC0:  alex   1598 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul 17 09:50:31 2021
  InstallationDate: Installed on 2021-01-03 (194 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 80DU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-22-generic N/A
   linux-backports-modules-5.11.0-22-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN31WW(V1.14)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80DU
  dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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


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

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

[Northwest Grid]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1942008/+attachment/5521927/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521925/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521928/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

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

** Description changed:

- Installed Kubuntu from the 20.04.1 LTS ISO. Shutdown, reboot, wake from
- sleep worked fine. Update to 20.04.2 caused issues where it wouldn't
+ Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake from
+ sleep worked fine. Updates for 20.04.2 caused issues where it wouldn't
  wake from sleep, rebooting hangs, and never actually shutdowns for the
  reboot, and shutdown causes an audible hardware clicking noise
  (somewhere to the left side of the computer underneath the keyboard) and
  corrupts the BIOS. The corrupted BIOS causes the computer to not boot at
  all and I have to do a BIOS reset via CMOS (Hold the power button for
  2-3 sec while pressing the WIN+v keys until it begins to boot). This
  gets more difficult each time it's done, where I have to wait longer
  before trying it and it seems to take longer to work. I have tried
  shutdown from the GUI menu, from the log-out menu, from Konsole, and
  from a TTY (CTRL+ALT+F2).
  
  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
- --- 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  kah1382 F pulseaudio
-  /dev/snd/controlC1:  kah1382 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kah1382 F pulseaudio
+  /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
-  linux-restricted-modules-5.11.0-27-generic N/A
-  linux-backports-modules-5.11.0-27-generic  N/A
-  linux-firmware 1.187.16
+  linux-restricted-modules-5.11.0-27-generic N/A
+  linux-backports-modules-5.11.0-27-generic  N/A
+  linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  

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

[Northwest Grid]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521924/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1942008] Re: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep

[Northwest Grid]

Chris Guiver (guiverc):
You are correct. I was mistaken about which ISO version I used. Thanks for 
pointing that out and your response.

** Description changed:

  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake from
  sleep worked fine. Updates for 20.04.2 caused issues where it wouldn't
  wake from sleep, rebooting hangs, and never actually shutdowns for the
  reboot, and shutdown causes an audible hardware clicking noise
  (somewhere to the left side of the computer underneath the keyboard) and
  corrupts the BIOS. The corrupted BIOS causes the computer to not boot at
  all and I have to do a BIOS reset via CMOS (Hold the power button for
  2-3 sec while pressing the WIN+v keys until it begins to boot). This
  gets more difficult each time it's done, where I have to wait longer
  before trying it and it seems to take longer to work. I have tried
  shutdown from the GUI menu, from the log-out menu, from Konsole, and
  from a TTY (CTRL+ALT+F2).
+ 
+ I also have tried reinstalling a couple of times.
  
  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: 

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

[Northwest Grid]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521922/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521916/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521914/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521913/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1942008/+attachment/5521915/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521920/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1942008] Lsusb.txt

[Northwest Grid]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1942008/+attachment/5521917/+files/Lsusb.txt

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

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521921/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521919/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1942008/+attachment/5521912/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

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

[Northwest Grid]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521918/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-27-generic N/A
   linux-backports-modules-5.11.0-27-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-27-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: 08/31/2009
  dmi.bios.release: 15.51
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Quanta
  dmi.board.version: 18.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 24.66
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.sku: NV022UA#ABA
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

[Kernel-packages] [Bug 1942008] Re: Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs, won't wake from sleep

[Northwest Grid]

apport information

** Tags added: apport-collected focal

** Description changed:

  Installed Kubuntu from the 20.04.1 LTS ISO. Shutdown, reboot, wake from
  sleep worked fine. Update to 20.04.2 caused issues where it wouldn't
  wake from sleep, rebooting hangs, and never actually shutdowns for the
  reboot, and shutdown causes an audible hardware clicking noise
  (somewhere to the left side of the computer underneath the keyboard) and
  corrupts the BIOS. The corrupted BIOS causes the computer to not boot at
  all and I have to do a BIOS reset via CMOS (Hold the power button for
  2-3 sec while pressing the WIN+v keys until it begins to boot). This
  gets more difficult each time it's done, where I have to wait longer
  before trying it and it seems to take longer to work. I have tried
  shutdown from the GUI menu, from the log-out menu, from Konsole, and
  from a TTY (CTRL+ALT+F2).
  
  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.18
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kah1382 F pulseaudio
+  /dev/snd/controlC1:  kah1382 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2021-08-18 (13 days ago)
+ InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
+ MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic 
root=UUID=a99a5c85-bf23-4afe-b6aa-eb4f086dcbbb ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-27-generic N/A
+  linux-backports-modules-5.11.0-27-generic  N/A
+  linux-firmware 1.187.16
+ Tags:  focal
+ Uname: Linux 5.11.0-27-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: 08/31/2009
+ dmi.bios.release: 15.51
+ dmi.bios.vendor: Hewlett-Packard
+ dmi.bios.version: F.33
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 3624
+ dmi.board.vendor: Quanta
+ dmi.board.version: 18.42
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Quanta
+ dmi.chassis.version: N/A
+ dmi.ec.firmware.release: 24.66
+ dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd08/31/2009:br15.51:efr24.66:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrRev1:rvnQuanta:rn3624:rvr18.42:cvnQuanta:ct10:cvrN/A:
+ dmi.product.family: 103C_5335KV
+ dmi.product.name: HP Pavilion dv7 Notebook PC
+ dmi.product.sku: NV022UA#ABA
+ dmi.product.version: Rev 1
+ dmi.sys.vendor: Hewlett-Packard

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1942008/+attachment/5521911/+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/1942008

Title:
  Kubuntu 20.04.2 update causes shutdown corrupt bios, reboot hangs,
  won't wake from sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installed Kubuntu from the 20.04.2 LTS ISO. Shutdown, reboot, wake
  from sleep worked fine. Updates for 20.04.2 caused issues where it
  wouldn't wake from sleep, rebooting hangs, and never actually
  shutdowns for the reboot, and shutdown causes an audible hardware
  clicking noise (somewhere to the left side of the computer underneath
  the keyboard) and corrupts the BIOS. The corrupted BIOS causes the
  computer to not boot at all and I have to do a BIOS reset via CMOS
  (Hold the power button for 2-3 sec while pressing the WIN+v keys until
  it begins to boot). This gets more difficult each time it's done,
  where I have to wait longer before trying it and it seems to take
  longer to work. I have tried shutdown from the GUI menu, from the log-
  out menu, from Konsole, and from a TTY (CTRL+ALT+F2).

  I also have tried reinstalling a couple of times.

  Computer specs:
  Host: HP Pavilion dv7-2180us Notebook PC Rev 1
  Kernel: 5.8.0-59-generic
  Resolution: 1600x900
  CPU: Intel Core 2 Quad Q9000 (4) @ 2.001GHz
  GPU: AMD ATI Mobility Radeon HD 4650/5165
  Memory: 6 GB
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kah1382 F pulseaudio
   /dev/snd/controlC1:  kah1382 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-18 (13 days ago)
  InstallationMedia: Kubuntu 

[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline

[Frank Heimes]

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

** Changed in: ubuntu-z-systems
   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/1939618

Title:
  CryptoExpress EP11 cards are going offline

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

Bug description:
  SRU Justification:

  [Impact]

  * With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
  go offline in case of unknown error indications from the hardware.

  * This does not only lead to a software fallback, but can also lead to errors 
and crashes,
if certain crypto operations are currently ongoing.

  * A rework of the AP bus and zcrypt device driver, as it was done in
  5.11, fixes the situation.

  * From the below range of commits, the last 1/3 are the ones that fix the 
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.

  * In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with 
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above), 
the risk would increase,
increased effort to maintain and less test coverage.

  [Fix]

  * The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4 
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618

  [Test Case]

  * An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and 
accelerator mode.

  * Run stress test on these three CryptoExpress adapters.

  * IBM has such stress tests and ran these based on a patched Ubuntu 20.04 
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.

  * Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.

  * An application exists that generates such messages and thus tests
  these error paths.

  * Canonical's focus will mainly be on regression testing.

  [Regression Potential]

  * Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.

  * But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)

  * The crypto-specific tools (located at the s390-tools package) may no longer 
work with this patched driver.
But this got tested by IBM with the result that the changes are fully 
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control 
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly 
covered by this patch set.

  * The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).

  * Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or 
example memory leaks.
However, this is not unique to this patch set, it the same for upstream, 
Hirsute and Impish (and other distros).

  * The patches are all upstream and all needed upstream commits could just be 
cherry-picked,
hence no modifications were needed.

  * So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see 
comment below) for further testing.

  * This patch set was also tested on 5.11, where two issues were found
  that are already part of this set.

  [Other]

  * I iterated through all commits and found that that the latest ones got 
upstream with 5.13,
hence Impish includes all commits needed and is not affected!

  * Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not 
affected!

  * But non of the commits could be found in current Focal master-next (aot: 
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
  __

  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline

[Kleber Sacilotto de Souza]

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

Title:
  CryptoExpress EP11 cards are going offline

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

  * With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
  go offline in case of unknown error indications from the hardware.

  * This does not only lead to a software fallback, but can also lead to errors 
and crashes,
if certain crypto operations are currently ongoing.

  * A rework of the AP bus and zcrypt device driver, as it was done in
  5.11, fixes the situation.

  * From the below range of commits, the last 1/3 are the ones that fix the 
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.

  * In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with 
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above), 
the risk would increase,
increased effort to maintain and less test coverage.

  [Fix]

  * The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4 
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618

  [Test Case]

  * An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and 
accelerator mode.

  * Run stress test on these three CryptoExpress adapters.

  * IBM has such stress tests and ran these based on a patched Ubuntu 20.04 
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.

  * Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.

  * An application exists that generates such messages and thus tests
  these error paths.

  * Canonical's focus will mainly be on regression testing.

  [Regression Potential]

  * Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.

  * But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)

  * The crypto-specific tools (located at the s390-tools package) may no longer 
work with this patched driver.
But this got tested by IBM with the result that the changes are fully 
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control 
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly 
covered by this patch set.

  * The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).

  * Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or 
example memory leaks.
However, this is not unique to this patch set, it the same for upstream, 
Hirsute and Impish (and other distros).

  * The patches are all upstream and all needed upstream commits could just be 
cherry-picked,
hence no modifications were needed.

  * So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see 
comment below) for further testing.

  * This patch set was also tested on 5.11, where two issues were found
  that are already part of this set.

  [Other]

  * I iterated through all commits and found that that the latest ones got 
upstream with 5.13,
hence Impish includes all commits needed and is not affected!

  * Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not 
affected!

  * But non of the commits could be found in current Focal master-next (aot: 
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
  __

  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

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


-- 
Mailing 

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

[sparks71]

Which kernel should I test?
Please be more precise.

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

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

  [Fix]

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

  [Test Case]

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

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

  [Where problems could occur]

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

  == original bug report ==

  Hello, I use Ubuntu 20.04.2 LTS.

  The kernel was recently updated to 5.11

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

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

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

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

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

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

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

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

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

  dmesg:

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

  In the ath10k mailing list I 

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Colin Ian King]

Potential workaround/fix attached

** Patch added: "kernel patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215/+attachment/5521900/+files/0001-ACPICA-detect-and-handle-invalid-op_type-before-call.patch

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Impish:
  Incomplete

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

  [   11.581774] R10: 0006 R11: 0246 R12: 
7f7fb47683fe
  [   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 
5624b2096cd0
  [   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel msr ip_tables 
x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx 

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

[Ubuntu SRU Bot]

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

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (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-gkeop

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

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

[Ubuntu SRU Bot]

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

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (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:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

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

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Fix Intel IPU6 camera sensor HM11b1 brightness

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

Bug description:
  Intel has released fix for HM11B1 sensor on IPU6 platform for its brightness 
problem in 
https://github.com/intel/ipu6-drivers/commit/eca28d1aa048216dc034b134e65e1b47602ee4a6
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1832 F pulseaudio
  CasperMD5CheckResult: skip
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-mewtwo+X82
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-08-13 (6 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. Latitude 9420
  Package: linux-oem-5.13 (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1010-oem 
root=UUID=090b1bdb-5d69-4cb9-a704-e1fffed1e366 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-1010-oem N/A
   linux-backports-modules-5.13.0-1010-oem  N/A
   linux-firmware   1.187.16+staging.11
  Tags:  focal
  Uname: Linux 5.13.0-1010-oem x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  dmi.bios.date: 01/25/2021
  dmi.bios.release: 89.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 89.5.23
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr89.5.23:bd01/25/2021:br89.5:svnDellInc.:pnLatitude9420:pvr:sku0A32:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9420
  dmi.product.sku: 0A32
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Touchpad not working with ASUS TUF F15

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

Bug description:
  == SRU Justification ==

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

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

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

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

  == Original Bug Report ==

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

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

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

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

  Output of xinput

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

  Output of lspci

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

[Kernel-packages] [Bug 1937252] Re: e1000e: add handshake with the Intel CSME to support S0ix

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  e1000e: add handshake with the Intel CSME to support S0ix

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

Bug description:
  [SRU Justification]

  [Impact]

  These improves power consumption on some e1000e platforms.

  [Fix]

  3 fixes in thread https://www.spinics.net/lists/netdev/msg755279.html
  (now in netdev/net-next.git).

  [Test Case]

  These fixes solves two issues that the first one is the power
  consumption would be lower to 1.651W from 2.032W when device enters
  sleep state. The second is I219 may now enter ultra lower power mode
  after resumed from s2idle.

  [Where problems could occur]

  While these fixes are still not in mainline but net-next, expecting some
  more stability fix when necessary.

  == original bug description ==

  Intel is doing some improvement for the Corp ME + S0ix support.

  Currently, this patch series have been landed in nextdev, net-next
  tree.

  e1000e: Additional PHY power saving in S0ix
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3ad3e28cb203309fb29022dea41cd65df0583632

  e1000e: Add polling mechanism to indicate CSME DPG exit
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=ef407b86d3cc7ab7ad37658c1c7a094cb8f3b6b4

  e1000e: Add handshake with the CSME to support S0ix
  
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3e55d231716ea361b1520b801c6778c4c48de102

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


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

[Kernel-packages] [Bug 1937978] Re: New device IDs for Intel ADL-M

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  New device IDs for Intel ADL-M

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

Bug description:
  [Impact]
  Some ADL IDs are added after v5.13, need to backport them to OEM-5.13 kernel.

  [Fix]
  9fb3cad02517 mfd: intel-lpss: Add Intel Alder Lake-M PCI IDs
  854955ae96db mtd: spi-nor: intel-spi: Add support for Intel Alder Lake-M SPI 
serial flash
  a59c7b6c6ff6 platform/x86: intel-hid: add Alder Lake ACPI device ID

  [Test]
  Don't have h/w yet, so not tested.

  [Where problems could occur]
  Only adding new IDs, won't impact old platforms.

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


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

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

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

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

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

Bug description:
  SRU justification:

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1936708] Re: Wobbly graphics on built-in display since linux-image-5.11.0-22-generic

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Wobbly graphics on built-in display since linux-
  image-5.11.0-22-generic

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

Bug description:
  == SRU Justification ==

  [Impact]
  Wobbly graphics after a kernel update. 

  [Fix]
  Older panels may require more bandwidth then advertised, so we need to
  use max params for them.

  [Test]
  Multiple users tested with positive result.

  [Where problems could occur]
  This patch reverts to the old behavior, which is to use max parameters,
  for older panels. If there's any new panel reports with older DP
  version, this might change the behavior on it.

  == Original Bug Report ==

  Lenovo laptop with Intel + Nvidia graphics.

  Since booting from  linux-image-5.11.0-22-generic, the built-in display is 
unusable, with wobbling horizontal stripes from the disk decryption prompt 
onwards:
  https://www.youtube.com/watch?v=LyRTuPzCe2I
  HDMI output works fine.

  If I boot from linux-image-5.11.0-18-generic instead, all is well.
  If I use Recovery mode with linux-image-5.11.0-22-generic and continue 
bootup, it's usable but there's no HDMI output.

  I think others may be having this issue too:
  
https://askubuntu.com/questions/1351188/weird-graphical-glitches-appears-only-on-integrated-display-on-any-ubuntu-base#

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-22-generic 5.11.0-22.23
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   1598 F pulseaudio
   /dev/snd/controlC0:  alex   1598 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sat Jul 17 09:50:31 2021
  InstallationDate: Installed on 2021-01-03 (194 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 80DU
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-22-generic N/A
   linux-backports-modules-5.11.0-22-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-05-22 (55 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN31WW(V1.14)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN31WW(V1.14):bd08/18/2014:br1.49:efr1.49:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80DU
  dmi.product.sku: LENOVO_MT_80DU_BU_idea_FM_Lenovo Y70-70 Touch
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1939541] Re: ALSA: hda/cs8409: Add support for dolphin

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  ALSA: hda/cs8409: Add support for dolphin

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  Dolphin devices have CS8409 HDA Bridge connected to two CS42L42 codecs.
  Codec 1 supports Headphone and Headset Mic. Codec 2 supports Line Out.

  [Fix]

  In order to support multiple CS42L42 codecs connected to a CS8409 HDA
  Bridge, a changeset of 27 patches is proposed to
  
https://patchwork.kernel.org/project/alsa-devel/cover/20210811185654.6837-1-vita...@opensource.cirrus.com/
  (now in linux-next), as well as two additional patches in
  
https://lore.kernel.org/lkml/20210812183433.6330-1-vita...@opensource.cirrus.com/
  that fixes pop sounds at insertion of earphone jack and reboot. The
  second patch of the latter changeset is on hold because of another fix
  series that deprecates the reboot_notify callback of HD-audio by
  forcibly doing runtime-suspend at shutdown.

  A Ubuntu sauced patch is also added to enable the now stand alone
  module snd-hda-codec-cs8409.

  [Test Case]

  Test on oem dolphin platform, as well as previous cs8409 platforms with
  one single codec.

  [Where problems could occur]

  While this is the first platform we have multiple codecs connected to
  a CS8409 HDA bridge, we may still have further stability or acoustic
  quality issues as we had for previous cirrus platforms.

  [Other Info]

  This also fixes default sample rate problem that was previously fixed by
  a oem-only package oem-fix-audio-cirrus-default-sample-rate.

  == original bug report ==

  Dolphin devices have CS8409 HDA Bridge connected to two CS42L42 codecs.
  Codec 1 supports Headphone and Headset Mic.
  Codec 2 supports Line Out.

  Features:
   - Front and Read Jacks appear as separate jacks; Removal or connection
     of on jack should not affect the connection of the other.
   - Front Jack only shows up on jack detection.
   - Rear Jack is Phantom Jack.
   - Separate Volume Controls for each Jack

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


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

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

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

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

Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  In Progress
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.13 source package in Impish:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

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

  [Fix]

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

  [Test Case]

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

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

  [Where problems could occur]

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

  == original bug report ==

  Hello, I use Ubuntu 20.04.2 LTS.

  The kernel was recently updated to 5.11

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

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

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

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

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

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

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

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

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

  dmesg:

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

[Kernel-packages] [Bug 1940610] Re: Fix mic noise on HP ProBook 445 G8

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
   Fix mic noise on HP ProBook 445 G8

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

Bug description:
  [Impact]
  There's mic noise on HP ProBook 445 G8.

  [Fix]
  Limit mic boost to make the audio capture crystal clear.

  [Test]
  $ arecord -f dat test
  $ aplay test
  With the fix, the mic noise is gone.

  [Where problems could occur]
  If someone would like to let others hear the noise in Zoom, this will
  deprive of their pleasure.

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


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

[Kernel-packages] [Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-focal

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

Title:
  Fix  Intel AC9560 BT function cannot turn on if BT turn off before S3
  entry

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

Bug description:
  [Impact]
  1. On Troy JSL platform, add AC9560
  2. Enter Settings -> Bluetooth menu
  3. Default Bluetooth option is ON, try to toggle the BT option to OFF
  4. Into suspend mode(S3) and resume the system
  5. Enter BT settings and try to turn on BT,
  6. BT function cannot enabled until reboot.

  [Fix]
  Turn off the msft ext only for AC9560.
  Maintainer thought Intel should take care this and reject this workaround.
  https://marc.info/?l=linux-bluetooth=162938546804458=2

  Intel is working on this issue and sru the workaround for the
  schedule.

  [Test]
  Verified with the bellow steps 10 times.
  1. On Troy JSL and add AC9560
  2. Turn off BT
  3. suspend the machine 10 times.
  4. turn on BT and works well.

  [Regression Potential]
  Medium, it's a workaround to turn off the MSFT ext only for ac9560.

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


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

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Colin Ian King]

** Bug watch added: bugs.acpica.org/ #1545
   https://bugs.acpica.org/show_bug.cgi?id=1545

** Also affects: linux via
   https://bugs.acpica.org/show_bug.cgi?id=1545
   Importance: Unknown
   Status: Unknown

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Impish:
  Incomplete

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

  [   11.581774] R10: 0006 R11: 0246 R12: 
7f7fb47683fe
  [   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 
5624b2096cd0
  [   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel 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 

[Kernel-packages] [Bug 1938697] Re: Kernel driver support issue between 5.4.0-74-generic and 5.4.0-80-generic

[Chris Chiu]

Thanks for result of the 5.4.0-75. Now the range can be narrowed down.
The strange thing is there's no r8169 related modification between 74 to
75. So it's not that easy to identify which commit commit the problem. I
build a modified 74 version to help. Can you try the kernel in
https://people.canonical.com/~mschiu77/lp1938697/74_118/? Thanks

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

Title:
  Kernel driver support issue between  5.4.0-74-generic and
  5.4.0-80-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have found an issue after upgrading my Kernel from 5.4.0-74-generic
  to 5.4.0-80-generic on Ubuntu 20.04.

  It appears that support for the second ethernet port on my Lenovo
  m90n-1 has been dropped or isn't working as expected.  After upgrading
  to 5.4.0-80-generic my second ethernet port

  Both ethernet ports use the r8169 driver.  If I switch back to the
  previous kernel 5.4.0-74-generic.  The second ethernet port is usable
  again.

  I did attempt under 5.4.0-80-generic to see if I could get an error
  message.  When the driver attempts to discover the second ethernet
  port the following error is thrown.

 "unknown chip XID fcf"

  Support output below:

  
  --- Before update.

  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-74-generic x86_64)

  root@lenovo-test-3:~# lshw -c network
*-network DISABLED
 description: Wireless interface
 product: Cannon Point-LP CNVi [Wireless-AC]
 vendor: Intel Corporation
 physical id: 14.3
 bus info: pci@:00:14.3
 logical name: wlo1
 version: 30
 serial: 54:8d:5a:ab:41:77
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-74-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
 resources: irq:16 memory:a141c000-a141
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 15
 serial: 98:fa:9b:c9:eb:c6
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.1.144 latency=0 
link=yes multicast=yes port=MII speed=1Gbit/s
 resources: irq:19 ioport:4000(size=256) memory:a1304000-a1304fff 
memory:a130-a1303fff
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:04:00.0
 logical name: enp4s0
 version: 1b
 serial: 98:fa:9b:c9:eb:c7
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=r8169 
firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII
 resources: irq:19 ioport:3000(size=256) memory:a1204000-a1204fff 
memory:a120-a1203fff

  
  --- After update

  root@lenovo-test-3:~# uname -r
  5.4.0-80-generic

  root@lenovo-test-3:~# lshw -c network
*-network DISABLED
 description: Wireless interface
 product: Cannon Point-LP CNVi [Wireless-AC]
 vendor: Intel Corporation
 physical id: 14.3
 bus info: pci@:00:14.3
 logical name: wlo1
 version: 30
 serial: 54:8d:5a:ab:41:77
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress msix bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.4.0-80-generic firmware=46.6bf1df06.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
 resources: irq:16 memory:a141c000-a141
*-network
 description: Ethernet interface
 product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
 vendor: Realtek Semiconductor Co., Ltd.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: enp2s0
 version: 15
 serial: 98:fa:9b:c9:eb:c6
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Colin Ian King]

I suspect the op_type in the dispatcher call status =
acpi_gbl_op_type_dispatch[op_type]  is out of range.

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

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

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

  [   11.581774] R10: 0006 R11: 0246 R12: 
7f7fb47683fe
  [   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 
5624b2096cd0
  [   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel 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 hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear ast drm_vram_helper 
i2c_algo_bit drm_ttm_helper ttm 

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

[Ubuntu SRU Bot]

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

backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (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:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Colin Ian King]

Original source ./drivers/acpi/acpica/dswexec.c in acpi_ds_exec_end_op

if (ACPI_SUCCESS(status)) {
/*
 * Dispatch the request to the appropriate interpreter 
handler
 * routine. There is one routine per opcode "type" 
based upon the
 * number of opcode arguments and return type.
 */
status =
acpi_gbl_op_type_dispatch[op_type] (walk_state);
} else {


.. disassembled:


if (!(walk_state->op_info->flags & AML_NO_OPERAND_RESOLVE)) {
 683:   48 8b 83 10 04 00 00mov0x410(%rbx),%rax
 68a:   f6 40 11 40 testb  $0x40,0x11(%rax)
 68e:   74 21   je 6b1 
 * Dispatch the request to the appropriate interpreter 
handler
 * routine. There is one routine per opcode "type" 
based upon the
 * number of opcode arguments and return type.
 */
status =
acpi_gbl_op_type_dispatch[op_type] (walk_state);
 690:   44 89 f0mov%r14d,%eax
 693:   41 80 fe 0b cmp$0xb,%r14b
 697:   77 28   ja 6c1 
 699:   48 8b 04 c5 00 00 00mov0x0(,%rax,8),%rax
 6a0:   00
 6a1:   48 89 dfmov%rbx,%rdi
 6a4:   e8 00 00 00 00  call   6a9 
 6a9:   41 89 c4mov%eax,%r12d
 6ac:   e9 8f 00 00 00  jmp740 
[walk_state->
 6b1:   0f b6 43 0d movzbl 0xd(%rbx),%eax
 num_operands - 1]),
 6b5:   8d 50 fflea-0x1(%rax),%edx
[walk_state->
 6b8:   48 63 d2movslq %edx,%rdx
 6bb:   48 83 fa 09 cmp$0x9,%rdx
 6bf:   76 02   jbe6c3 
 6c1:   0f 0b   ud2

^^ crash on 0f 0b ud2 instruction

>From https://mudongliang.github.io/x86/html/file_module_x86_id_318.html
ud2 does:

"Generates an invalid opcode. This instruction is provided for software
testing to explicitly generate an invalid opcode. The opcode for this
instruction is reserved for this purpose.

Other than raising the invalid opcode exception, this instruction is the
same as the NOP instruction."

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

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

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  

[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

[Chris Chiu]

Thanks. We still have 3~4 versions to try and make sure which commit cause the 
panic.
Please try https://people.canonical.com/~mschiu77/lp1941773/989b27104a97/ and 
let me know the result. Thanks.

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

Title:
  kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I do not know how to find information to help debug.
  The laptop is lenovo E15 with latest BIOS 1.13

  kubuntu 21.04

  laptop boots correctly with 5.13.8 and trackpad works.
  with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (13 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-12 (14 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Package: linux (not installed)
  Tags:  hirsute
  Uname: Linux 5.13.8-051308-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

[Ian May]

Found on: bionic/linux-aws: 4.15.0-.118

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

Title:
  cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15

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

Bug description:
  [Impact]
  Test case cfs_bandwidth01 in LTP sched test suite is a reproducer
  of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix
  enqueue_task_fair warning).

  This test triggers a warning on our 4.15 kernel:
   LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5)
   [ cut here ]
   rq->tmp_alone_branch != >leaf_cfs_rq_list
   WARNING: CPU: 0 PID: 0 at 
/build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 
unthrottle_cfs_rq+0x16f/0x200
   Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel 
kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl 
lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy 
virtio_net i2c_piix4
   CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu
   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 
04/01/2014
   RIP: 0010:unthrottle_cfs_rq+0x16f/0x200
   RSP: 0018:989ebfc03e80 EFLAGS: 00010082
   RAX:  RBX: 989eb4c6ac00 RCX: 
   RDX: 0005 RSI: acb63c4d RDI: 0046
   RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20
   R10:  R11: 0001 R12: 989eb57fe400
   R13: 989ebfc21900 R14: 0001 R15: 0001
   FS: () GS:989ebfc0() knlGS:
   CS: 0010 DS:  ES:  CR0: 80050033
   CR2: 55593258d618 CR3: 7a044000 CR4: 06f0
   DR0:  DR1:  DR2: 
   DR3:  DR6: fffe0ff0 DR7: 0400
   Call Trace:
   
   distribute_cfs_runtime+0xc3/0x110
   sched_cfs_period_timer+0xff/0x220
   ? sched_cfs_slack_timer+0xd0/0xd0
   __hrtimer_run_queues+0xdf/0x230
   hrtimer_interrupt+0xa0/0x1d0
   smp_apic_timer_interrupt+0x6f/0x140
   apic_timer_interrupt+0x90/0xa0
   
   RIP: 0010:native_safe_halt+0x12/0x20
   RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11
   RAX: abbc9280 RBX:  RCX: 
   RDX:  RSI:  RDI: 
   RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00
   R10:  R11: 7fff R12: 
   R13:  R14:  R15: 
   ? __sched_text_end+0x1/0x1
   default_idle+0x20/0x100
   arch_cpu_idle+0x15/0x20
   default_idle_call+0x23/0x30
   do_idle+0x172/0x1f0
   cpu_startup_entry+0x73/0x80
   rest_init+0xae/0xb0
   start_kernel+0x4dc/0x500
   x86_64_start_reservations+0x24/0x26
   x86_64_start_kernel+0x74/0x77
   secondary_startup_64+0xa5/0xb0
   Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 
db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 
43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00
   ---[ end trace b6b9a70bc2945c0c ]---

  [Fix]
  Base on the test case description, we will need these fixes:
    * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning
    * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more
    * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list
    * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path
    * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair()

  Backport needed for Bionic since we're missing some new variables /
  coding style changes introduced in the following commits (and their
  corresponding fixes):
    * 97fb7a0a8944bd sched: Clean up and harmonize the coding style of the 
scheduler code base
    * 9f68395333ad7f sched/pelt: Add a new runnable average signal
    * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs
    * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq

  I have also searched in the upstream tree to see if there is any other
  commit claim to be a fix of these but didn't see any.

  [Test]
  Test kernel can be found here:
  https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/

  With these patches applied, the test can pass without triggering this
  warning.

  

[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline

[Kleber Sacilotto de Souza]

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

** Changed in: linux (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/1939618

Title:
  CryptoExpress EP11 cards are going offline

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  * With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
  go offline in case of unknown error indications from the hardware.

  * This does not only lead to a software fallback, but can also lead to errors 
and crashes,
if certain crypto operations are currently ongoing.

  * A rework of the AP bus and zcrypt device driver, as it was done in
  5.11, fixes the situation.

  * From the below range of commits, the last 1/3 are the ones that fix the 
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.

  * In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with 
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above), 
the risk would increase,
increased effort to maintain and less test coverage.

  [Fix]

  * The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4 
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618

  [Test Case]

  * An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and 
accelerator mode.

  * Run stress test on these three CryptoExpress adapters.

  * IBM has such stress tests and ran these based on a patched Ubuntu 20.04 
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.

  * Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.

  * An application exists that generates such messages and thus tests
  these error paths.

  * Canonical's focus will mainly be on regression testing.

  [Regression Potential]

  * Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.

  * But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)

  * The crypto-specific tools (located at the s390-tools package) may no longer 
work with this patched driver.
But this got tested by IBM with the result that the changes are fully 
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control 
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly 
covered by this patch set.

  * The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).

  * Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or 
example memory leaks.
However, this is not unique to this patch set, it the same for upstream, 
Hirsute and Impish (and other distros).

  * The patches are all upstream and all needed upstream commits could just be 
cherry-picked,
hence no modifications were needed.

  * So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see 
comment below) for further testing.

  * This patch set was also tested on 5.11, where two issues were found
  that are already part of this set.

  [Other]

  * I iterated through all commits and found that that the latest ones got 
upstream with 5.13,
hence Impish includes all commits needed and is not affected!

  * Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not 
affected!

  * But non of the commits could be found in current Focal master-next (aot: 
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
  __

  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just unpack it and apply with quilt.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle

[Ian May]

Found on: bionic/linux-aws: 4.15.0-.118

** Tags added: aws

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

Title:
  ubuntu_seccomp 11-basic-basic_errors failure on X/oracle

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oracle package in Ubuntu:
  New
Status in linux source package in Xenial:
  Incomplete
Status in linux-oracle source package in Xenial:
  New
Status in linux source package in Bionic:
  Incomplete
Status in linux-oracle source package in Bionic:
  New

Bug description:
  Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test
  from ubuntu_seccomp on all Oracle cloud instances:

   batch name: 11-basic-basic_errors
   test mode:  c
   test type:  basic
  Test 11-basic-basic_errors%%001-1 result:   FAILURE 11-basic-basic_errors 
rc=255

  Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK.
  Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this 
looks like regression.

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


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

[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel

[Saša Marjanović]

** Changed in: linux (Ubuntu Hirsute)
   Status: Fix Committed => 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/1937897

Title:
  GPIO error logs in start and dmesg after update of kernel

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Hirsute:
  Fix Released
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  After upgrade kernel to 5.11.0-25 which introduce some ODM patches from 
AAEON, user encounters below errors
  [   5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  [Fix]
  AAEON provides a patch to check the BFPI version before loading the driver.
  Which fixes the issue introduced by
  Hirsute:
 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices
  Impish:
 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices

  
  [Test]
  Verified by AAEON.

  [Where problems could occur]
  It adds a check while probing the driver, should have no impact to normal 
user.

  =

  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

     5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
    *-core
     description: Motherboard
     product: TUF GAMING B550M-PLUS (WI-FI)
     vendor: ASUSTeK COMPUTER INC.
     physical id: 0
     version: Rev X.0x
     serial: 201176738701636
     slot: Default string
   *-firmware
    description: BIOS
    vendor: American Megatrends Inc.
    physical id: 0
    version: 2403
    date: 06/16/2021
    size: 64KiB
    capacity: 16MiB
    capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

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


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

[Kernel-packages] [Bug 1934424] Re: kernel NULL pointer dereference during xen hibernation

[Tim Gardner]

A workaround is to completely 'down' the network before hibernation. The
patches as suggested by Francis Ginther had only 4 failures in 2500
hibernation cycles.

** Description changed:

+ SRU Justification
+ 
+ [Impact]
+ 
  Encountered the following panic while doing hibernation/resume testing
  with linux-aws 5.8 on Focal on an m3.xlarge (xen) instance type:
  
  [  594.291317] ACPI: Hardware changed while hibernated, success doubtful!
  [  594.411609] BUG: kernel NULL pointer dereference, address: 01f4
  [  594.424658] #PF: supervisor write access in kernel mode
  [  594.424660] #PF: error_code(0x0002) - not-present page
- [  594.424661] PGD 0 P4D 0 
+ [  594.424661] PGD 0 P4D 0
  [  594.424665] Oops: 0002 [#1] SMP PTI
  [  594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 
5.8.0-1036-aws #38~20.04.1-Ubuntu
  [  594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [  594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
  [  594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 
58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f b1 
17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90
  [  594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046
  [  594.424680] RAX:  RBX: 8883bcc0d000 RCX: 
0e02
  [  594.424681] RDX: 0001 RSI:  RDI: 
01f4
  [  594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 
005a
  [  594.424683] R10: c94e3910 R11:  R12: 
0206
  [  594.424684] R13: ea000ee42d40 R14:  R15: 
0001
  [  594.424686] FS:  7f65ba055980() GS:8883c0ac() 
knlGS:
  [  594.424687] CS:  0010 DS:  ES:  CR0: 80050033
  [  594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 
001606e0
  [  594.424692] Call Trace:
  [  594.424699]  xennet_start_xmit+0x158/0x570
  [  594.424704]  dev_hard_start_xmit+0x91/0x1f0
  [  594.424706]  ? validate_xmit_skb+0x300/0x340
  [  594.424710]  sch_direct_xmit+0x113/0x340
  [  594.424712]  __dev_queue_xmit+0x57c/0x8e0
  [  594.424714]  ? neigh_add_timer+0x37/0x60
  [  594.424716]  dev_queue_xmit+0x10/0x20
  [  594.424717]  neigh_resolve_output+0x112/0x1c0
  [  594.424721]  ip_finish_output2+0x19b/0x590
  [  594.424723]  __ip_finish_output+0xc8/0x1e0
  [  594.424725]  ip_finish_output+0x2d/0xb0
  [  594.424728]  ip_output+0x7a/0xf0
  [  594.424730]  ? __ip_finish_output+0x1e0/0x1e0
  [  594.424732]  ip_local_out+0x3d/0x50
  [  594.424734]  ip_send_skb+0x19/0x40
  [  594.424737]  udp_send_skb.isra.0+0x165/0x390
  [  594.424739]  udp_sendmsg+0xb0e/0xd50
  [  594.424742]  ? ip_reply_glue_bits+0x50/0x50
  [  594.424747]  ? delete_from_swap_cache+0x6a/0x90
  [  594.424750]  ? _cond_resched+0x19/0x30
  [  594.424754]  ? aa_sk_perm+0x43/0x1b0
  [  594.424757]  inet_sendmsg+0x65/0x70
  [  594.424759]  ? security_socket_sendmsg+0x35/0x50
  [  594.424760]  ? inet_sendmsg+0x65/0x70
  [  594.424764]  sock_sendmsg+0x5e/0x70
  [  594.424766]  __sys_sendto+0x113/0x190
  [  594.424770]  ? __secure_computing+0x42/0xe0
  [  594.424774]  ? syscall_trace_enter+0x10d/0x280
  [  594.424777]  __x64_sys_sendto+0x29/0x30
  [  594.424781]  do_syscall_64+0x49/0xc0
  [  594.424783]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  594.424785] RIP: 0033:0x7f65baee4844
  [  594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 
24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 
f0 ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b
  [  594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 
002c
  [  594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 
7f65baee4844
  [  594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 
0010
  [  594.424792] RBP:  R08: 560426541678 R09: 
0010
  [  594.424793] R10: 0040 R11: 0293 R12: 

  [  594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: 

  [  594.424796] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs 
msdos xfs libcrc32c dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd 
psmouse cryptd input_leds glue_helper serio_raw floppy sch_fq_codel drm 
ip_tables x_tables autofs4
  [  594.424813] CR2: 01f4
  [  594.424821] ---[ end trace bb5f35055c1a8060 ]---
  [  594.424822] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
  [  594.424824] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 
58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f b1 
17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90
  [  594.424824] RSP: 0018:c94e3848 EFLAGS: 00010046
  [  594.424825] RAX:  RBX: 8883bcc0d000 RCX: 
0e02
  

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

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-5.4 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-5.4 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-hwe source package in Focal:
  Invalid
Status in linux-hwe-5.4 source package in Focal:
  Invalid

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

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

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


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

[Kernel-packages] [Bug 1934424] Re: kernel NULL pointer dereference during xen hibernation

[Launchpad Bug Tracker]

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

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

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

Title:
  kernel NULL pointer dereference during xen hibernation

Status in linux-aws package in Ubuntu:
  Confirmed

Bug description:
  SRU Justification

  [Impact]

  Encountered the following panic while doing hibernation/resume testing
  with linux-aws 5.8 on Focal on an m3.xlarge (xen) instance type:

  [  594.291317] ACPI: Hardware changed while hibernated, success doubtful!
  [  594.411609] BUG: kernel NULL pointer dereference, address: 01f4
  [  594.424658] #PF: supervisor write access in kernel mode
  [  594.424660] #PF: error_code(0x0002) - not-present page
  [  594.424661] PGD 0 P4D 0
  [  594.424665] Oops: 0002 [#1] SMP PTI
  [  594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 
5.8.0-1036-aws #38~20.04.1-Ubuntu
  [  594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [  594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
  [  594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 
58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f b1 
17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90
  [  594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046
  [  594.424680] RAX:  RBX: 8883bcc0d000 RCX: 
0e02
  [  594.424681] RDX: 0001 RSI:  RDI: 
01f4
  [  594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 
005a
  [  594.424683] R10: c94e3910 R11:  R12: 
0206
  [  594.424684] R13: ea000ee42d40 R14:  R15: 
0001
  [  594.424686] FS:  7f65ba055980() GS:8883c0ac() 
knlGS:
  [  594.424687] CS:  0010 DS:  ES:  CR0: 80050033
  [  594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 
001606e0
  [  594.424692] Call Trace:
  [  594.424699]  xennet_start_xmit+0x158/0x570
  [  594.424704]  dev_hard_start_xmit+0x91/0x1f0
  [  594.424706]  ? validate_xmit_skb+0x300/0x340
  [  594.424710]  sch_direct_xmit+0x113/0x340
  [  594.424712]  __dev_queue_xmit+0x57c/0x8e0
  [  594.424714]  ? neigh_add_timer+0x37/0x60
  [  594.424716]  dev_queue_xmit+0x10/0x20
  [  594.424717]  neigh_resolve_output+0x112/0x1c0
  [  594.424721]  ip_finish_output2+0x19b/0x590
  [  594.424723]  __ip_finish_output+0xc8/0x1e0
  [  594.424725]  ip_finish_output+0x2d/0xb0
  [  594.424728]  ip_output+0x7a/0xf0
  [  594.424730]  ? __ip_finish_output+0x1e0/0x1e0
  [  594.424732]  ip_local_out+0x3d/0x50
  [  594.424734]  ip_send_skb+0x19/0x40
  [  594.424737]  udp_send_skb.isra.0+0x165/0x390
  [  594.424739]  udp_sendmsg+0xb0e/0xd50
  [  594.424742]  ? ip_reply_glue_bits+0x50/0x50
  [  594.424747]  ? delete_from_swap_cache+0x6a/0x90
  [  594.424750]  ? _cond_resched+0x19/0x30
  [  594.424754]  ? aa_sk_perm+0x43/0x1b0
  [  594.424757]  inet_sendmsg+0x65/0x70
  [  594.424759]  ? security_socket_sendmsg+0x35/0x50
  [  594.424760]  ? inet_sendmsg+0x65/0x70
  [  594.424764]  sock_sendmsg+0x5e/0x70
  [  594.424766]  __sys_sendto+0x113/0x190
  [  594.424770]  ? __secure_computing+0x42/0xe0
  [  594.424774]  ? syscall_trace_enter+0x10d/0x280
  [  594.424777]  __x64_sys_sendto+0x29/0x30
  [  594.424781]  do_syscall_64+0x49/0xc0
  [  594.424783]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  594.424785] RIP: 0033:0x7f65baee4844
  [  594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 
24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 
f0 ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b
  [  594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 
002c
  [  594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 
7f65baee4844
  [  594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 
0010
  [  594.424792] RBP:  R08: 560426541678 R09: 
0010
  [  594.424793] R10: 0040 R11: 0293 R12: 

  [  594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: 

  [  594.424796] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs 
msdos xfs libcrc32c dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd 
psmouse cryptd input_leds glue_helper serio_raw floppy sch_fq_codel drm 
ip_tables x_tables autofs4
  [  594.424813] CR2: 01f4
  [  594.424821] ---[ end trace bb5f35055c1a8060 ]---
  [  594.424822] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
  [  594.424824] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 
58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 

[Kernel-packages] [Bug 1942223] Re: Amazon EC2 hibernate fails in xen-netfront

[Tim Gardner]

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

** This bug has been marked a duplicate of bug 1934424
   kernel NULL pointer dereference during xen hibernation

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

Title:
  Amazon EC2 hibernate fails in xen-netfront

Status in linux package in Ubuntu:
  New

Bug description:
  [Impact]

  The xen-netfront module can crash during hibernation if the network
  has not been disabled.

  [ 594.291317] ACPI: Hardware changed while hibernated, success doubtful!
  [ 594.411609] BUG: kernel NULL pointer dereference, address: 01f4
  [ 594.424658] #PF: supervisor write access in kernel mode
  [ 594.424660] #PF: error_code(0x0002) - not-present page
  [ 594.424661] PGD 0 P4D 0
  [ 594.424665] Oops: 0002 [#1] SMP PTI
  [ 594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 
5.8.0-1036-aws #38~20.04.1-Ubuntu
  [ 594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [ 594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
  [ 594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 
58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f b1 
17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90
  [ 594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046
  [ 594.424680] RAX:  RBX: 8883bcc0d000 RCX: 
0e02
  [ 594.424681] RDX: 0001 RSI:  RDI: 
01f4
  [ 594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 
005a
  [ 594.424683] R10: c94e3910 R11:  R12: 
0206
  [ 594.424684] R13: ea000ee42d40 R14:  R15: 
0001
  [ 594.424686] FS: 7f65ba055980() GS:8883c0ac() 
knlGS:
  [ 594.424687] CS: 0010 DS:  ES:  CR0: 80050033
  [ 594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 
001606e0
  [ 594.424692] Call Trace:
  [ 594.424699] xennet_start_xmit+0x158/0x570
  [ 594.424704] dev_hard_start_xmit+0x91/0x1f0
  [ 594.424706] ? validate_xmit_skb+0x300/0x340
  [ 594.424710] sch_direct_xmit+0x113/0x340
  [ 594.424712] __dev_queue_xmit+0x57c/0x8e0
  [ 594.424714] ? neigh_add_timer+0x37/0x60
  [ 594.424716] dev_queue_xmit+0x10/0x20
  [ 594.424717] neigh_resolve_output+0x112/0x1c0
  [ 594.424721] ip_finish_output2+0x19b/0x590
  [ 594.424723] __ip_finish_output+0xc8/0x1e0
  [ 594.424725] ip_finish_output+0x2d/0xb0
  [ 594.424728] ip_output+0x7a/0xf0
  [ 594.424730] ? __ip_finish_output+0x1e0/0x1e0
  [ 594.424732] ip_local_out+0x3d/0x50
  [ 594.424734] ip_send_skb+0x19/0x40
  [ 594.424737] udp_send_skb.isra.0+0x165/0x390
  [ 594.424739] udp_sendmsg+0xb0e/0xd50
  [ 594.424742] ? ip_reply_glue_bits+0x50/0x50
  [ 594.424747] ? delete_from_swap_cache+0x6a/0x90
  [ 594.424750] ? _cond_resched+0x19/0x30
  [ 594.424754] ? aa_sk_perm+0x43/0x1b0
  [ 594.424757] inet_sendmsg+0x65/0x70
  [ 594.424759] ? security_socket_sendmsg+0x35/0x50
  [ 594.424760] ? inet_sendmsg+0x65/0x70
  [ 594.424764] sock_sendmsg+0x5e/0x70
  [ 594.424766] __sys_sendto+0x113/0x190
  [ 594.424770] ? __secure_computing+0x42/0xe0
  [ 594.424774] ? syscall_trace_enter+0x10d/0x280
  [ 594.424777] __x64_sys_sendto+0x29/0x30
  [ 594.424781] do_syscall_64+0x49/0xc0
  [ 594.424783] entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 594.424785] RIP: 0033:0x7f65baee4844
  [ 594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 
24 28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 
f0 ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b
  [ 594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 
002c
  [ 594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 
7f65baee4844
  [ 594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 
0010
  [ 594.424792] RBP:  R08: 560426541678 R09: 
0010
  [ 594.424793] R10: 0040 R11: 0293 R12: 

  [ 594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: 

  [ 594.424796] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs msdos 
xfs libcrc32c dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd 
psmouse cryptd input_leds glue_helper serio_raw floppy sch_fq_codel drm 
ip_tables x_tables autofs4
  [ 594.424813] CR2: 01f4
  [ 594.424821] ---[ end trace bb5f35055c1a8060 ]---
  [ 594.424822] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
  [ 594.424824] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 
58 0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f b1 
17 75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90
  [ 594.424824] RSP: 0018:c94e3848 

[Kernel-packages] [Bug 1942223] [NEW] Amazon EC2 hibernate fails in xen-netfront

[Tim Gardner]

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

Public bug reported:

[Impact]

The xen-netfront module can crash during hibernation if the network has
not been disabled.

[ 594.291317] ACPI: Hardware changed while hibernated, success doubtful!
[ 594.411609] BUG: kernel NULL pointer dereference, address: 01f4
[ 594.424658] #PF: supervisor write access in kernel mode
[ 594.424660] #PF: error_code(0x0002) - not-present page
[ 594.424661] PGD 0 P4D 0
[ 594.424665] Oops: 0002 [#1] SMP PTI
[ 594.424668] CPU: 3 PID: 362 Comm: systemd-timesyn Not tainted 5.8.0-1036-aws 
#38~20.04.1-Ubuntu
[ 594.424669] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
[ 594.424675] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
[ 594.424678] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 
0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f b1 17 
75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90
[ 594.424679] RSP: 0018:c94e3848 EFLAGS: 00010046
[ 594.424680] RAX:  RBX: 8883bcc0d000 RCX: 0e02
[ 594.424681] RDX: 0001 RSI:  RDI: 01f4
[ 594.424682] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a
[ 594.424683] R10: c94e3910 R11:  R12: 0206
[ 594.424684] R13: ea000ee42d40 R14:  R15: 0001
[ 594.424686] FS: 7f65ba055980() GS:8883c0ac() 
knlGS:
[ 594.424687] CS: 0010 DS:  ES:  CR0: 80050033
[ 594.424688] CR2: 01f4 CR3: 0003b99f0001 CR4: 001606e0
[ 594.424692] Call Trace:
[ 594.424699] xennet_start_xmit+0x158/0x570
[ 594.424704] dev_hard_start_xmit+0x91/0x1f0
[ 594.424706] ? validate_xmit_skb+0x300/0x340
[ 594.424710] sch_direct_xmit+0x113/0x340
[ 594.424712] __dev_queue_xmit+0x57c/0x8e0
[ 594.424714] ? neigh_add_timer+0x37/0x60
[ 594.424716] dev_queue_xmit+0x10/0x20
[ 594.424717] neigh_resolve_output+0x112/0x1c0
[ 594.424721] ip_finish_output2+0x19b/0x590
[ 594.424723] __ip_finish_output+0xc8/0x1e0
[ 594.424725] ip_finish_output+0x2d/0xb0
[ 594.424728] ip_output+0x7a/0xf0
[ 594.424730] ? __ip_finish_output+0x1e0/0x1e0
[ 594.424732] ip_local_out+0x3d/0x50
[ 594.424734] ip_send_skb+0x19/0x40
[ 594.424737] udp_send_skb.isra.0+0x165/0x390
[ 594.424739] udp_sendmsg+0xb0e/0xd50
[ 594.424742] ? ip_reply_glue_bits+0x50/0x50
[ 594.424747] ? delete_from_swap_cache+0x6a/0x90
[ 594.424750] ? _cond_resched+0x19/0x30
[ 594.424754] ? aa_sk_perm+0x43/0x1b0
[ 594.424757] inet_sendmsg+0x65/0x70
[ 594.424759] ? security_socket_sendmsg+0x35/0x50
[ 594.424760] ? inet_sendmsg+0x65/0x70
[ 594.424764] sock_sendmsg+0x5e/0x70
[ 594.424766] __sys_sendto+0x113/0x190
[ 594.424770] ? __secure_computing+0x42/0xe0
[ 594.424774] ? syscall_trace_enter+0x10d/0x280
[ 594.424777] __x64_sys_sendto+0x29/0x30
[ 594.424781] do_syscall_64+0x49/0xc0
[ 594.424783] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 594.424785] RIP: 0033:0x7f65baee4844
[ 594.424788] Code: 42 3f f7 ff 44 8b 4c 24 2c 4c 8b 44 24 20 89 c5 44 8b 54 24 
28 48 8b 54 24 18 b8 2c 00 00 00 48 8b 74 24 10 8b 7c 24 08 0f 05 <48> 3d 00 f0 
ff ff 77 30 89 ef 48 89 44 24 08 e8 68 3f f7 ff 48 8b
[ 594.424789] RSP: 002b:7ffe9b5fd3a0 EFLAGS: 0293 ORIG_RAX: 
002c
[ 594.424790] RAX: ffda RBX: 7ffe9b5fd4e0 RCX: 7f65baee4844
[ 594.424791] RDX: 0030 RSI: 7ffe9b5fd3f0 RDI: 0010
[ 594.424792] RBP:  R08: 560426541678 R09: 0010
[ 594.424793] R10: 0040 R11: 0293 R12: 
[ 594.424794] R13: 7ffe9b5fd3e4 R14: 0068 R15: 
[ 594.424796] Modules linked in: btrfs blake2b_generic xor raid6_pq ufs msdos 
xfs libcrc32c dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd 
psmouse cryptd input_leds glue_helper serio_raw floppy sch_fq_codel drm 
ip_tables x_tables autofs4
[ 594.424813] CR2: 01f4
[ 594.424821] ---[ end trace bb5f35055c1a8060 ]---
[ 594.424822] RIP: 0010:_raw_spin_lock_irqsave+0x23/0x40
[ 594.424824] Code: 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 54 9c 58 
0f 1f 44 00 00 49 89 c4 fa 66 0f 1f 44 00 00 31 c0 ba 01 00 00 00  0f b1 17 
75 07 4c 89 e0 41 5c 5d c3 89 c6 e8 e9 d1 56 ff 66 90
[ 594.424824] RSP: 0018:c94e3848 EFLAGS: 00010046
[ 594.424825] RAX:  RBX: 8883bcc0d000 RCX: 0e02
[ 594.424826] RDX: 0001 RSI:  RDI: 01f4
[ 594.424826] RBP: c94e3850 R08: 8883b90b5ec0 R09: 005a
[ 594.424827] R10: c94e3910 R11:  R12: 0206
[ 594.424827] R13: ea000ee42d40 R14:  R15: 0001
[ 594.424828] FS: 7f65ba055980() GS:8883c0ac() 
knlGS:
[ 594.424829] 

[Kernel-packages] [Bug 1939855] Re: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands

[Kleber Sacilotto de Souza]

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

Title:
  [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with
  ethtool specific register commands

Status in dellserver:
  Incomplete
Status in focal package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in focal source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  When we run the command, ethtool -d  with Intel cards (ice 
driver), the kernel crashes because of the ice driver.
  The same works fine with HWE kernel (5.11). Here, we do not see any crash.

  [FIXES]

  ice: Fix bad register reads
  The "ethtool -d" handler reads registers in the ice_regs_dump_list array
  and returns read values back to the userspace.

  commitID:  1fba4a8a92706c89716449b1aab1b6879f438d34

  https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
  
next.git/commit/drivers/net/ethernet/intel/ice?id=1fba4a8a92706c89716449b1aab1b6879f438d34

  [TESTING]

  Install Focal on a system with an E810 network device.
  Ensure the network device has an IP address and has connectivity
  Run ethtool -d 
  Expected result: Prints a register dump for the specified network device

  [REGRESSION RISK]

  The regression risk is low

  [OTHER INFO]

  I have added the fix, built the kernel and tested the fix.

  
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e810_ethtool_fix_next

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


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

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

[Kleber Sacilotto de Souza]

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

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

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

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

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

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem-5.10 source package in Bionic:
  Invalid
Status in linux-oem-5.13 source package in Bionic:
  Invalid
Status in linux source package in Focal:
  Fix Committed
Status in linux-oem-5.10 source package in Focal:
  In Progress
Status in linux-oem-5.13 source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.13 source package in Hirsute:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-oem-5.10 source package in Impish:
  Invalid
Status in linux-oem-5.13 source package in Impish:
  Invalid

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1941669] Re: alsa: the soundwire audio doesn't work on the Dell TGL-H machines

[Kleber Sacilotto de Souza]

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

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

Title:
  alsa: the soundwire audio doesn't work on the Dell TGL-H machines

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

Bug description:
  These 2 patches were merged to upstream kernel from v5.12, no need to
  send them to impish/oem-5.13/unstable kernels. And this patch is
  already in the oem-5.10 kernel, for focal kernel, since focal kernel
  doesn't support soundwire audio, these 2 patches are useless for focal
  kernel.

  
  [Impact]
  The Dell precision 5760 is a TGL-H machine, and it has soundwire audio
  design, when running the hirsute kernel, the audio driver fails to
  load sof-firmware, then the whole audio fails to initialize and fails
  to work.

  [Fix]
  Backport 2 patches, these will remove hardcoded firmware name and
  allow load firmware according to the firmware name defined by pciid

  [Test]
  Booting the patched kernel, check dmesg, there is no errors about
  loading audio sof-firmware, playsound to spk and headphone, all worked
  well, record sound from internal mic and external mic, all worked well.

  [Where problems could occur]
  The patch remove the hardcoded firmware for all TGL soundwire machines,
  this could make the TGL soundwire machines fail to load the
  sof-firmware then the whole audio fail to work. But this possibiliy is
  low, since we tested the patches on different TGL soundwire machines,
  all worked well.

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


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

[Kernel-packages] [Bug 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM

[Kleber Sacilotto de Souza]

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

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

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

Title:
  e1000e blocks the boot process when it tried to write checksum to its
  NVM

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

Bug description:
  [Impact]
  While probing e1000e, it checks its NVM checksum, and write correct checksum 
back if the checksum is not correct. But for recent GBE update for security, 
its NVM could be written once for MAC address during production, so write 
checksum during driver probing is not allowed and would block the boot process.

  [Fix]
  Intel provides a fix for it.
  
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20210718041031.3619696-1-sasha.nef...@intel.com/

  [Test]
  Verified on a Dell machine which has wrong NVM checksum.

  [Where problems could occur]
  From what Intel told us, the checksum isn't correct is not a big deal, we 
could ignore it and it won't lead to any issues.

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


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

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Paolo Pisati]

** Attachment added: "DSDT dump"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215/+attachment/5521894/+files/dsdt.dat

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

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

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

  [   11.581774] R10: 0006 R11: 0246 R12: 
7f7fb47683fe
  [   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 
5624b2096cd0
  [   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel 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 hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear ast drm_vram_helper 
i2c_algo_bit 

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1052.55~18.04.17)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-meta-gke-5.4 
(5.4.0.1052.55~18.04.17) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/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:
  Confirmed
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Invalid
Status in linux-azure-edge source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1941669] Re: alsa: the soundwire audio doesn't work on the Dell TGL-H machines

[Stefan Bader]

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

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

Title:
  alsa: the soundwire audio doesn't work on the Dell TGL-H machines

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

Bug description:
  These 2 patches were merged to upstream kernel from v5.12, no need to
  send them to impish/oem-5.13/unstable kernels. And this patch is
  already in the oem-5.10 kernel, for focal kernel, since focal kernel
  doesn't support soundwire audio, these 2 patches are useless for focal
  kernel.

  
  [Impact]
  The Dell precision 5760 is a TGL-H machine, and it has soundwire audio
  design, when running the hirsute kernel, the audio driver fails to
  load sof-firmware, then the whole audio fails to initialize and fails
  to work.

  [Fix]
  Backport 2 patches, these will remove hardcoded firmware name and
  allow load firmware according to the firmware name defined by pciid

  [Test]
  Booting the patched kernel, check dmesg, there is no errors about
  loading audio sof-firmware, playsound to spk and headphone, all worked
  well, record sound from internal mic and external mic, all worked well.

  [Where problems could occur]
  The patch remove the hardcoded firmware for all TGL soundwire machines,
  this could make the TGL soundwire machines fail to load the
  sof-firmware then the whole audio fail to work. But this possibiliy is
  low, since we tested the patches on different TGL soundwire machines,
  all worked well.

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


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

[Kernel-packages] [Bug 1936771] Re: disable “CONFIG_HISI_DMA” config for ubuntu version

[Kleber Sacilotto de Souza]

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

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

Title:
  disable “CONFIG_HISI_DMA” config for ubuntu version

Status in kunpeng920:
  In Progress
Status in kunpeng920 ubuntu-20.04 series:
  In Progress
Status in kunpeng920 ubuntu-20.04-hwe series:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Committed
Status in linux source package in Hirsute:
  Fix Committed
Status in linux source package in Impish:
  In Progress

Bug description:
  [Impact]
  Setup soft RAID5 on kunpeng920 machine and system will crash because of 
hisi_dma timeout. This issue can be reproduced with all Ubuntu kernel with 
hisi_dma.

  [Test Plan]
  Setup soft RAID5 and wait for few seconds. Kernel will crash.

  [Regression Risk]
  CONFIG_HISI_DMA only affects kunpeng920 platform. Minimal risk for other 
platform, and full regression test is needed on kunpeng920.

  ===
  [Bug Description]
  disable “CONFIG_HISI_DMA” config for ubuntu version

  [Steps to Reproduce]
  1)
  2)
  3)

  [Actual Results]
  this module cause some error

  [Expected Results]
  ok
  [Reproducibility]

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

  [Resolution]

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


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

[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected

[Kleber Sacilotto de Souza]

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

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

Title:
  Dell XPS 17 (9710) PCI/internal sound card not detected

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

Bug description:
  This patch is for soundwire audio, and only ubuntu 5.11-generic
  and later kernels support soundwire audio driver, so this patch is not
  sent to groovy and focal kernels.

  For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM
  project, it is not urgent to merge this patch to OEM kenrels, after
  the patch is in the hirsute and impish kernels, the oem kernels will
  have this patch when syncing with generic kernels.

  [Impact]
  On the Dell XPS 17 (9710) machine, the audio card is not detected when
  booting hirsute or impish kernels. So the audio doesn't work on this
  machine with ubuntu linux 21.04 or 21.10.

  [Fix]
  Backport a upstream patch, this will set the correct codec config
  for this machine: rt711 for headset, dual rt1308 for spks and rt715
  for internal mic.

  [Test]
  Booting up with the patched kernel, the audio card is detected, test
  internal speaker and internal mic, all work well, plug a headset,
  the headphone and external mic work well too.

  
  [Where problems could occur]
  This change only applis to the Dell machines with the 
  DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the
  regression, it will make the audio (speaker, internal mic and headset)
  can't work anymore on the Dell machine with that PRODUCT_SKU, but this
  possibility is very low, and we tested the patch on the machine, so
  far no regression is found.

  
  No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 
20.10 or 21.04  .  Can connect via USB headset and audio will work.   Tried 
suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not 
work. Currently running 21.04 with proposed.

  Have tried hirsute-proposed (5.11.0-24-generic) with no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
  Uname: Linux 5.11.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mblack 1698 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 12 11:21:27 2021
  InstallationDate: Installed on 2021-07-07 (4 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.0
  dmi.board.name: 012MMP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9710
  dmi.product.sku: 0A5D
  dmi.sys.vendor: Dell Inc.

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


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

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

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

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

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


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

[Kernel-packages] [Bug 1940610] Re: Fix mic noise on HP ProBook 445 G8

[Kleber Sacilotto de Souza]

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

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

Title:
   Fix mic noise on HP ProBook 445 G8

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

Bug description:
  [Impact]
  There's mic noise on HP ProBook 445 G8.

  [Fix]
  Limit mic boost to make the audio capture crystal clear.

  [Test]
  $ arecord -f dat test
  $ aplay test
  With the fix, the mic noise is gone.

  [Where problems could occur]
  If someone would like to let others hear the noise in Zoom, this will
  deprive of their pleasure.

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


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

[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel

[Kleber Sacilotto de Souza]

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

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

Title:
  GPIO error logs in start and dmesg after update of kernel

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

Bug description:
  [Impact]
  After upgrade kernel to 5.11.0-25 which introduce some ODM patches from 
AAEON, user encounters below errors
  [   5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  [Fix]
  AAEON provides a patch to check the BFPI version before loading the driver.
  Which fixes the issue introduced by
  Hirsute:
 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices
  Impish:
 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON 
devices

  
  [Test]
  Verified by AAEON.

  [Where problems could occur]
  It adds a check while probing the driver, should have no impact to normal 
user.

  =

  After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error
  to gpio:

     5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with 
zero lines
  [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to 
register, -22
  [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22

  On pc:

  description: Desktop Computer
  product: System Product Name (SKU)
  vendor: ASUS
  version: System Version
  serial: System Serial Number
  width: 64 bits
  capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32
  configuration: boot=normal chassis=desktop family=To be filled by O.E.M. 
sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4
    *-core
     description: Motherboard
     product: TUF GAMING B550M-PLUS (WI-FI)
     vendor: ASUSTeK COMPUTER INC.
     physical id: 0
     version: Rev X.0x
     serial: 201176738701636
     slot: Default string
   *-firmware
    description: BIOS
    vendor: American Megatrends Inc.
    physical id: 0
    version: 2403
    date: 06/16/2021
    size: 64KiB
    capacity: 16MiB
    capabilities: pci apm upgrade shadowing cdboot bootselect 
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
   *-memory

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


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

[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline

[Frank Heimes]

Pull request submitted to kernel team's mailing list:
https://lists.ubuntu.com/archives/kernel-team/2021-August/thread.html#123711
changing status to 'In Progress'.

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

** Changed in: ubuntu-z-systems
   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/1939618

Title:
  CryptoExpress EP11 cards are going offline

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

  * With current focal kernels IBM Z CryptoExpress adapters in EP11 mode
  go offline in case of unknown error indications from the hardware.

  * This does not only lead to a software fallback, but can also lead to errors 
and crashes,
if certain crypto operations are currently ongoing.

  * A rework of the AP bus and zcrypt device driver, as it was done in
  5.11, fixes the situation.

  * From the below range of commits, the last 1/3 are the ones that fix the 
issue mentioned here
and the others are pre-requisites to get the relevant ones applied.

  * In theory the patch set could have been made smaller,
but with the cost that the code would be a mix between old and new, with 
maybe some new code snippets,
hence it would divert from what's upstream accepted (in 5.11 and above), 
the risk would increase,
increased effort to maintain and less test coverage.

  [Fix]

  * The SRU request was created as pull request,
so please pull f904c400c9c4^..f6d9ab1de03a (means starting at f904c400c9c4 
{incl.} to head/f6d9ab1de03a {incl.})
from here: https://code.launchpad.net/~fheimes/+git/lp1939618

  [Test Case]

  * An Ubuntu Server 20.04 on IBM Z or LinuxONE installation is required,
with ideally three attached CryptoExpress adapters running in CCA, EP11 and 
accelerator mode.

  * Run stress test on these three CryptoExpress adapters.

  * IBM has such stress tests and ran these based on a patched Ubuntu 20.04 
kernel.
The tests come with a specially focus on error path tests,
since this patch set mainly focuses on doing a better error patch handling.

  * Note: A a new config option for the zcrypt driver was introduced
that enables the possibility to inject erroneous messages.

  * An application exists that generates such messages and thus tests
  these error paths.

  * Canonical's focus will mainly be on regression testing.

  [Regression Potential]

  * Like with all modification there is a certain risk of regressions,
especially with bigger patch sets.

  * But the modifications here are limited to the s390x platform,
and there again largely to the s390x hardware crypto stack and driver
(CryptoExpress adapter) which is optional hardware.
(See the diff stat in the comment below.)

  * The crypto-specific tools (located at the s390-tools package) may no longer 
work with this patched driver.
But this got tested by IBM with the result that the changes are fully 
backward compatible.
The 'older' s390 tools package (from focal) can just not show and control 
the new (config state) feature,
but the functionality covered by the older s390 tools package is utterly 
covered by this patch set.

  * The core of this patch set went into the 5.11 kernel upstream,
hence is in hirsute (and has also been picked by other distros).

  * Since this patch set is a rework of the AP bus and zcrypt driver code,
it may now show new errors that were never thrown before, like for or 
example memory leaks.
However, this is not unique to this patch set, it the same for upstream, 
Hirsute and Impish (and other distros).

  * The patches are all upstream and all needed upstream commits could just be 
cherry-picked,
hence no modifications were needed.

  * So the commits were not only tested by IBM upfront,
but a patched focal master-next kernel is also available as PPA (see 
comment below) for further testing.

  * This patch set was also tested on 5.11, where two issues were found
  that are already part of this set.

  [Other]

  * I iterated through all commits and found that that the latest ones got 
upstream with 5.13,
hence Impish includes all commits needed and is not affected!

  * Looks like all commits, expect three, are even upstream with 5.11,
but the missing three came in on top via upstream stable,
hence Hirsute master-next includes all commits needed too and is also not 
affected!

  * But non of the commits could be found in current Focal master-next (aot: 
5.4.0-84),
the first commits from this set started to land with 5.7,
hence this SRU request is for focal only.
  __

  Here is the backport against current git for ubuntu 20.04.
  It is a zip file with a patches subdir and all the patches in there together 
with a series file. So just 

[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze

[Francisco Z]

I have the same problem in my hp g4 250 laptop, adding: options
rtw88_pci disable_aspm=1 to that file /etc/modprobe.d/rtw88_pci.conf
fixed the freezes, but it happends in every linux distro using kernel
5.11+

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

Title:
  rtw88_8821ce causes freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card.
  Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic 
kernel,and it works "well" for both WiFi and Bluetooth.
  However, this module (driver) causes frequent freezes, randomly but usually 
within a few minutes of running (thus very soon after boot): screen display 
remains frozen, no response to either keyboard or mouse input. All I can do is 
to hold the power button to power off, then reboot.

  After reboot, I do not see any crash reports, nor logs about the freeze.
  Please let me know if I should try to collect some info, and how.

  For now I use the DKMS module/driver from
    https://github.com/tomaspinho/rtl8821ce
  (having blacklisted rtw88_8821ce), and it seems to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-16-generic 5.11.0-16.17
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  psz1189 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  8 16:58:19 2021
  InstallationDate: Installed on 2021-04-23 (14 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera
   Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protempo Ltd L116HTN6SPW
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-16-generic N/A
   linux-backports-modules-5.11.0-16-generic  N/A
   linux-firmware 1.197
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2020
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: L116HTN6SPW
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Protempo Ltd

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


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

[Kernel-packages] [Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device

[Stefan Bader]

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

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

Title:
  Drivers: hv: vmbus: Fix duplicate CPU assignments within a device

Status in linux-azure package in Ubuntu:
  Incomplete
Status in linux-azure source package in Focal:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Customers have degraded network performance on Hyper-V/Azure

  This is a request to pick up a patch from the upstream, the patch
  fixes an issue with Ubuntu as a hyper-v and Azure guest. This patch
  need to get picked up for 20.04, 18.04. The link to the upstream patch
  follows:

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

  Description of issue and solution:

  The vmbus module uses a rotational algorithm to assign target CPUs to
  a device's channels. Depending on the timing of different device's channel
  offers, different channels of a device may be assigned to the same CPU.

  For example on a VM with 2 CPUs, if NIC A and B's channels are offered
  in the following order, NIC A will have both channels on CPU0, and
  NIC B will have both channels on CPU1 -- see below. This kind of
  assignment causes RSS load that is spreading across different channels
  to end up on the same CPU.

  Timing of channel offers:
  NIC A channel 0
  NIC B channel 0
  NIC A channel 1
  NIC B channel 1

  VMBUS ID 14: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic 
network adapter
  Device_ID = {cab064cd-1f31-47d5-a8b4-9d57e320cccd}
  Sysfs path: /sys/bus/vmbus/devices/cab064cd-1f31-47d5-a8b4-9d57e320cccd
  Rel_ID=14, target_cpu=0
  Rel_ID=17, target_cpu=0

  VMBUS ID 16: Class_ID = {f8615163-df3e-46c5-913f-f2d2f965ed0e} - Synthetic 
network adapter
  Device_ID = {244225ca-743e-4020-a17d-d7baa13d6cea}
  Sysfs path: /sys/bus/vmbus/devices/244225ca-743e-4020-a17d-d7baa13d6cea
  Rel_ID=16, target_cpu=1
  Rel_ID=18, target_cpu=1

  Update the vmbus CPU assignment algorithm to avoid duplicate CPU
  assignments within a device.

  The new algorithm iterates num_online_cpus + 1 times.
  The existing rotational algorithm to find "next NUMA & CPU" is still here.
  But if the resulting CPU is already used by the same device, it will try
  the next CPU.
  In the last iteration, it assigns the channel to the next available CPU
  like the existing algorithm. This is not normally expected, because
  during device probe, we limit the number of channels of a device to
  be <= number of online CPUs.

  [Test Plan]

  This could be tough to test as the patch fixes a race condition.

  [Where problems could occur]

  Network performance issues could persist.

  [Other Info]

  SF:#00315347

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


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

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

[Kleber Sacilotto de Souza]

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

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

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

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Hirsute:
  Fix Committed

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

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

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

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

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

  SRU Justifications:
  ===
  [Impact]
  External displays not working on Thinkpad T490 with ThinkPad Thunderbolt
  3 Dock

  [Fix]
  Some SKL systems DP output fails when AUX timeout of LTTPR detection.
  Disable the LTTPR detection until GLK to fix the link training.

  [Test]
  Verified on hardware, external DP work fine.
  Also tested on I+N GPU laptop and a iGPU only laptop, all displays with dock 
are good.

  [Where problems could occur]
  It may break output of external DP.

  This patch from 5.12-rc5, only Hirsute kernel is SRUed.

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


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

[Kernel-packages] [Bug 1942215] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Paolo Pisati]

Full dmesg with proper indentation is available here:

https://paste.ubuntu.com/p/qbhf4fTMdQ/

FWTS --dump tarball is here:

https://people.canonical.com/~ppisati/vough-acpi.tgz

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

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

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

  [   11.581774] R10: 0006 R11: 0246 R12: 
7f7fb47683fe
  [   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 
5624b2096cd0
  [   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel msr ip_tables 
x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 
async_raid6_recov async_memcpy async_pq 

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

[Ubuntu Kernel Bot]

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

apport-collect 1942215

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

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

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

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

** Tags added: impish

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

Title:
  OOPs on boot: invalid opcode:  [#1] SMP NOPTI

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

Bug description:
  Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
  boot on vought we get this:

  ...
  [   11.502916] invalid opcode:  [#1] SMP NOPTI
  [   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
  [   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
  [   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
  [   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
  [   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
  [   11.513428] RAX:  RBX: 8f08a7573800 RCX: 
0040
  [   11.514972] RDX:  RSI: 91ea9980 RDI: 
02cb
  [   11.516100] RBP: aaeca1a77710 R08:  R09: 
8f08a8c84af0
  [   11.517479] R10:  R11: 0003 R12: 

  [   11.518985] R13: 8f08a8c84af0 R14:  R15: 

  [   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
  [   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 
007706e0
  [   11.524924] DR0:  DR1:  DR2: 

  [   11.526221] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   11.527636] PKRU: 5554
  [   11.528820] Call Trace:
  [   11.529807]  acpi_ps_parse_loop+0x587/0x660
  [   11.531198]  acpi_ps_parse_aml+0x1af/0x552
  [   11.532595]  acpi_ps_execute_method+0x208/0x2ca
  [   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
  [   11.535361]  acpi_evaluate_object+0x18e/0x3b4
  [   11.536736]  acpi_evaluate_dsm+0xb3/0x120
  [   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
  [   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
  [   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
  [   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
  [   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
  [   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
  [   11.546116]  acpi_device_probe+0x49/0x170
  [   11.547431]  really_probe+0x245/0x4c0
  [   11.548749]  driver_probe_device+0xf0/0x160
  [   11.550064]  device_driver_attach+0xab/0xb0
  [   11.551387]  __driver_attach+0xb2/0x140
  [   11.552692]  ? device_driver_attach+0xb0/0xb0
  [   11.554001]  bus_for_each_dev+0x7e/0xc0
  [   11.555326]  driver_attach+0x1e/0x20
  [   11.556630]  bus_add_driver+0x135/0x1f0
  [   11.557917]  driver_register+0x95/0xf0
  [   11.559226]  acpi_bus_register_driver+0x39/0x50
  [   11.560139]  nfit_init+0x168/0x1000 [nfit]
  [   11.561230]  ? 0xc0649000
  [   11.562442]  do_one_initcall+0x46/0x1d0
  [   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
  [   11.564846]  do_init_module+0x62/0x290
  [   11.565768]  load_module+0xaa6/0xb40
  [   11.566811]  __do_sys_finit_module+0xc2/0x120
  [   11.567825]  __x64_sys_finit_module+0x18/0x20
  [   11.568747]  do_syscall_64+0x61/0xb0
  [   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
  [   11.570680]  ? __x64_sys_mmap+0x33/0x40
  [   11.571606]  ? do_syscall_64+0x6e/0xb0
  [   11.572442]  ? asm_exc_page_fault+0x8/0x30
  [   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   11.574392] RIP: 0033:0x7f7fb45d670d
  [   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
  [   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
  [   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 
7f7fb45d670d
  [   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 
0006
  [   11.580712] RBP: 0002 R08:  R09: 

[Kernel-packages] [Bug 1942215] [NEW] OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI

[Paolo Pisati]

Public bug reported:

Using latest Impish kernel 5.13.0-15.15 from ckt/bootstrap PPA, upon
boot on vought we get this:

...
[   11.502916] invalid opcode:  [#1] SMP NOPTI
[   11.504249] CPU: 95 PID: 1472 Comm: systemd-udevd Not tainted 
5.13.0-15-generic #15-Ubuntu
[   11.505734] Hardware name: Intel Corporation S2600WFD/S2600WFD, BIOS 
SE5C620.86B.0D.01.0395.022720191340 02/27/2019
[   11.507260] RIP: 0010:acpi_ds_exec_end_op+0x187/0x774
[   11.508771] Code: 77 28 48 8b 04 c5 00 9b ea 91 48 89 df ff d0 0f 1f 00 41 
89 c4 e9 8f 00 00 00 0f b6 43 0d 8d 50 ff 48 63 d2 48 83 fa 09 76 02 <0f> 0b 83 
c0 6c 0f b7 7b 0a 48 89 da 48 98 48 8d 34 c3 e8 c0 3c 01
[   11.511898] RSP: 0018:aaeca1a776e0 EFLAGS: 00010286
[   11.513428] RAX:  RBX: 8f08a7573800 RCX: 0040
[   11.514972] RDX:  RSI: 91ea9980 RDI: 02cb
[   11.516100] RBP: aaeca1a77710 R08:  R09: 8f08a8c84af0
[   11.517479] R10:  R11: 0003 R12: 
[   11.518985] R13: 8f08a8c84af0 R14:  R15: 
[   11.520425] FS:  7f7fb403ed00() GS:8f348d5c() 
knlGS:
[   11.521931] CS:  0010 DS:  ES:  CR0: 80050033
[   11.523424] CR2: 7f7fb38d1918 CR3: 000129b6a002 CR4: 007706e0
[   11.524924] DR0:  DR1:  DR2: 
[   11.526221] DR3:  DR6: fffe0ff0 DR7: 0400
[   11.527636] PKRU: 5554
[   11.528820] Call Trace:
[   11.529807]  acpi_ps_parse_loop+0x587/0x660
[   11.531198]  acpi_ps_parse_aml+0x1af/0x552
[   11.532595]  acpi_ps_execute_method+0x208/0x2ca
[   11.533972]  acpi_ns_evaluate+0x34e/0x4f0
[   11.535361]  acpi_evaluate_object+0x18e/0x3b4
[   11.536736]  acpi_evaluate_dsm+0xb3/0x120
[   11.537943]  ? acpi_evaluate_dsm+0xb3/0x120
[   11.539214]  nfit_intel_shutdown_status+0xed/0x1b0 [nfit]
[   11.540603]  acpi_nfit_add_dimm+0x3cb/0x670 [nfit]
[   11.541990]  acpi_nfit_register_dimms+0x141/0x460 [nfit]
[   11.543377]  acpi_nfit_init+0x54f/0x620 [nfit]
[   11.544755]  acpi_nfit_add+0x192/0x1f0 [nfit]
[   11.546116]  acpi_device_probe+0x49/0x170
[   11.547431]  really_probe+0x245/0x4c0
[   11.548749]  driver_probe_device+0xf0/0x160
[   11.550064]  device_driver_attach+0xab/0xb0
[   11.551387]  __driver_attach+0xb2/0x140
[   11.552692]  ? device_driver_attach+0xb0/0xb0
[   11.554001]  bus_for_each_dev+0x7e/0xc0
[   11.555326]  driver_attach+0x1e/0x20
[   11.556630]  bus_add_driver+0x135/0x1f0
[   11.557917]  driver_register+0x95/0xf0
[   11.559226]  acpi_bus_register_driver+0x39/0x50
[   11.560139]  nfit_init+0x168/0x1000 [nfit]
[   11.561230]  ? 0xc0649000
[   11.562442]  do_one_initcall+0x46/0x1d0
[   11.563701]  ? kmem_cache_alloc_trace+0x11c/0x240
[   11.564846]  do_init_module+0x62/0x290
[   11.565768]  load_module+0xaa6/0xb40
[   11.566811]  __do_sys_finit_module+0xc2/0x120
[   11.567825]  __x64_sys_finit_module+0x18/0x20
[   11.568747]  do_syscall_64+0x61/0xb0
[   11.569694]  ? syscall_exit_to_user_mode+0x27/0x50
[   11.570680]  ? __x64_sys_mmap+0x33/0x40
[   11.571606]  ? do_syscall_64+0x6e/0xb0
[   11.572442]  ? asm_exc_page_fault+0x8/0x30
[   11.573395]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[   11.574392] RIP: 0033:0x7f7fb45d670d
[   11.575373] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48
[   11.577496] RSP: 002b:7ffe815a56d8 EFLAGS: 0246 ORIG_RAX: 
0139
[   11.578573] RAX: ffda RBX: 5624b212e410 RCX: 7f7fb45d670d
[   11.579646] RDX:  RSI: 7f7fb47683fe RDI: 0006
[   11.580712] RBP: 0002 R08:  R09: 
[   11.581774] R10: 0006 R11: 0246 R12: 7f7fb47683fe
[   11.582847] R13: 5624b2090bf0 R14: 5624b208f940 R15: 5624b2096cd0
[   11.583907] Modules linked in: nfit(+) mac_hid sch_fq_codel 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 hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear ast drm_vram_helper 
i2c_algo_bit drm_ttm_helper ttm crct10dif_pclmul drm_kms_helper crc32_pclmul 
syscopyarea sysfillrect ghash_clmulni_intel sysimgblt aesni_intel fb_sys_fops 
cec crypto_simd rc_core i40e cryptd drm i2c_i801 ahci xhci_pci lpc_ich 
i2c_smbus xhci_pci_renesas libahci wmi
[   11.589096] ---[ end trace c51e80930ce46555 ]---
...

and reboot fails to restart the board.

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

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


** Tags: impish

-- 
You received this bug notification because you are a member of 

[Kernel-packages] [Bug 1936682] Re: Fix kernel panic caused by legacy devices on AMD platforms

[Kleber Sacilotto de Souza]

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

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

Title:
  Fix kernel panic caused by legacy devices on AMD platforms

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

Bug description:
  [Impact]
  When a legacy device is only 32bit DMA capable and it's in the same
  IOMMU group with iommu_v2 capable devices, the device in question will
  be forced to use identity mapping and triggers kernel panic on DMA
  operation because it can't do 64bit DMA.

  [Fix]
  Keep swiotlb enabled so legacy devices can do 64bit DMA. This is also
  how Intel and ARM64 platforms deal with legacy devices.

  [Test]
  Boot an affected system. Kernel panic in Realtek WiFi driver's probe
  routine.

  After the patch is applied, the system can work normally.

  [Where problems could occur]
  The default swiotlb uses 64MB memory, so if the system doesn't have any
  legacy device, there are 64MB ram less for the system to use.

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


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