[Kernel-packages] [Bug 1945565] Re: [SRU] Revert amdgpu/renoir firmware

[Bin Li]

On Thinkpad renoir platform, after upgraded the linux-firmware from 1.187.17 to 
1.187.19, this issue is fixed.
kernel: 5.13.0-1014-oem 

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

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

Title:
  [SRU] Revert amdgpu/renoir firmware

Status in OEM Priority Project:
  New
Status in linux-firmware package in Ubuntu:
  Won't Fix
Status in linux-firmware source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  The USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA 
Dongle after the system resumed from S3.

  [Fix]
  Revert below change, this issue is gone.

  commit a543b9c1bfd12e60d962acd48108234481a8581f
  Author: Alex Deucher 
  Date:   Thu Jul 1 12:23:11 2021 +0800

  amdgpu: update renoir firmware from 21.20

  BugLink: https://bugs.launchpad.net/bugs/1934014

  From internal git commit:
  8b05e03570818d047d7ea0a7388c89c4192fd20b

  Signed-off-by: Alex Deucher 
  Signed-off-by: Josh Boyer 
  (backported from commit 56ef642160203f8be7e1334feca4a76852c74bc0)
  [khfeng: Squashed multiple updates into one commit]
  Signed-off-by: Kai-Heng Feng 
  Signed-off-by: Timo Aaltonen 

  [Test]
  Verify S3 on renoir's platforms.

  [Where problems could occur]
  Renoir based systems can't resume from s2idle.

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


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

[Kernel-packages] [Bug 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

[Sujith Pandel]

Hi Michael,

Driver version check
Install and boot
12hr stress test
12hr reboot loop

All these tests went fine with the above proposed kernel. Please help
include the updates into SRU.

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

Title:
  Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Focal:
  New
Status in linux source package in Hirsute:
  New
Status in linux source package in Impish:
  Confirmed

Bug description:
  [Impact]
  This is a feature request to update the mpt3sas driver to latest version in 
upstream 38.100.00.00 in Ubuntu 21.10 and Ubuntu 20.04.
  This will allow users to use fixes and enhancements that landed upstream in 
5.14. For this reason,
  Broadcom and Dell have requested to pull these patches to update the
  mpt3sas driver to the current upstream version.

  I could see both Ubuntu 21.10 and 20.04 HWE has mpt3sas driver
  v36.100.00.00, following are the commit ID's to update to 38.100.00.00

  [Fixes]
  8b3c803529 scsi: mpt3sas: Signedness bug in _base_get_diag_triggers()
  39718fe7ad scsi: mpt3sas: Fix spelling mistake in Kconfig "compatiblity" -> 
"compatibility"
  bfb3f00c06 scsi: mpt3sas: Simplify bool comparison
  d309ae0732 scsi: mpt3sas: Fix ReplyPostFree pool allocation
  664f0dce20 scsi: mpt3sas: Add support for shared host tagset for CPU hotplug
  688c1a0a13 scsi: mpt3sas: Additional diagnostic buffer query interface
  446b5f3d3f scsi: mpt3sas: Update driver version to 37.100.00.00

  8278807abd scsi: core: Add scsi_device_busy() wrapper
  020b0f0a31 scsi: core: Replace sdev->device_busy with sbitmap

  e015e0ded1 scsi: mpt3sas: Fix misspelling of _base_put_smid_default_atomic()
  2111ba8781 scsi: mpt3sas: Move a little data from the stack onto the heap
  cf9e575e62 scsi: mpt3sas: Fix a bunch of potential naming doc-rot
  54cb88dc30 scsi: mpt3sas: Fix a couple of misdocumented functions/params
  782a1ab33f scsi: mpt3sas: Fix some kernel-doc misnaming issues
  a50bd64616 scsi: mpt3sas: Do not use GFP_KERNEL in atomic context
  a1c4d77413 scsi: mpt3sas: Replace unnecessary dynamic allocation with a 
static one
  d6adc251dd scsi: mpt3sas: Force PCIe scatterlist allocations to be within 
same 4 GB region
  7dd847dae1 scsi: mpt3sas: Force chain buffer allocations to be within same 4 
GB region
  970ac2bb70 scsi: mpt3sas: Force sense buffer allocations to be within same 4 
GB region
  58501fd937 scsi: mpt3sas: Force reply buffer allocations to be within same 4 
GB region
  2e4e858732 scsi: mpt3sas: Force reply post buffer allocations to be within 
same 4 GB region
  c569de899b scsi: mpt3sas: Force reply post array allocations to be within 
same 4 GB region
  37067b9793 scsi: mpt3sas: Update driver version to 37.101.00.00

  a8d548b0b3 scsi: mpt3sas: Fix a few kernel-doc issues
  3401ecf7fc scsi: mpt3sas: Fix error return code of mpt3sas_base_attach()

  206a3afa94 scsi: mpt3sas: Fix a typo
  4c51f95696 scsi: mpt3sas: Only one vSES is present even when IOC has multi 
vSES
  c0629d70ca scsi: mpt3sas: Fix endianness for ActiveCablePowerRequirement
  3c8604691d scsi: mpt3sas: Block PCI config access from userspace during reset
  16660db3fc scsi: mpt3sas: Fix out-of-bounds warnings in _ctl_addnl_diag_query
  3ad0b1da0d scsi: mpt3sas: Fix two kernel-doc headers
  2910a4a9e9 scsi: mpt3sas: Documentation cleanup
  e2fac6c44a scsi: mpt3sas: Fix deadlock while cancelling the running firmware 
event
  19a622c39a scsi: mpt3sas: Handle firmware faults during first half of IOC init
  a0815c45c8 scsi: mpt3sas: Handle firmware faults during second half of IOC 
init

  f2b1e9c6f8 scsi: core: Introduce scsi_build_sense()

  84a84cc6af scsi: mpt3sas: Fix fall-through warnings for Clang
  cf750be8e6 scsi: mpt3sas: Fix Coverity reported issue
  d6c2ce435f scsi: mpt3sas: Fix error return value in _scsih_expander_add()

  Note:
  We have  already posted patch to update  driver version to 38.100.00.00
  Other patches are already available in upstream .

  [Testing]
  Load the driver
  Run IO

  [Regression Risk]
  No extra test cases are needed, normal regression test cases such as driver 
load & running IOs are enough.

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


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

[Kernel-packages] [Bug 1946425] [NEW] Ubuntu 20.04.3 went to sleep, then crashed

[Robert Pearson]

Public bug reported:

When I move the mouse and clicked it displayed a black-and-white Ubuntu
emblem for 0.4s then nothing. Broken from 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Fri Oct  8 00:22:37 2021
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Ubuntu 20.04.3 went to sleep, then crashed

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

Bug description:
  When I move the mouse and clicked it displayed a black-and-white
  Ubuntu emblem for 0.4s then nothing. Broken from 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Fri Oct  8 00:22:37 2021
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1939052] Re: No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s Gen2

[Hui Wang]

The fix was merged to mainline kernel. Now SRU the fix to ubuntu
kernels.


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

** Also affects: linux (Ubuntu Impish)
   Importance: Medium
   Status: Confirmed

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

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

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and
  13s Gen2

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

Bug description:
  All 3 models need the appropriate HDA verbs sent to properly
  initialize the sound hardware.

  Additionally, the Legion 15IMHG05 needs automute disabled otherwise
  speaker output will not return after removing headphones.

  The good news is that I have working patches for all 3.

  However, the 13s Gen2 reportedly has some weirdness on the volume
  control. I don't have this model of laptop so there's not a lot I can
  do. It seems tuning the volume up and down using the keys on the
  keyboard can jump the volume up and down in large increments. Volume
  adjustments via a GUI do not have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-25-generic 5.11.0-25.27
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hiryu  7243 F pulseaudio
   /dev/snd/controlC0:  hiryu  7243 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug  5 10:17:57 2021
  InstallationDate: Installed on 2021-04-23 (104 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 82K6
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=825f1536-7d58-4097-9779-e5df2db0a6eb ro quiet splash 
nvidia-drm.modeset=0 resume=/dev/mapper/swap thinkpad_acpi.fan_control=1 
bluetooth.disable_ertm acpi_backlight=video vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-25-generic N/A
   linux-backports-modules-5.11.0-25-generic  N/A
   linux-firmware 1.197.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2021
  dmi.bios.release: 1.33
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1CN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ITHg6
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1CN33WW:bd07/18/2021:br1.33:efr1.33:svnLENOVO:pn82K6:pvrLegion716ITHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ITHg6:
  dmi.product.family: Legion 7 16ITHg6
  dmi.product.name: 82K6
  dmi.product.sku: LENOVO_MT_82K6_BU_idea_FM_Legion 7 16ITHg6
  dmi.product.version: Legion 7 16ITHg6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1944575] Re: Acer Aspire 5 issue when headphone plug in before login

[Hui Wang]

Hi Bijay,

If you add "options snd-hda-intel dmic_detect=0" to the
/etc/modprobe.d/alsa-base.conf, plug the headset and reboot, could you
still reproduce this issue? (this testing will force to use legacy hda
audio driver instead of sof audio driver).

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

Title:
  Acer Aspire 5 issue when headphone plug in before login

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Acer Aspire A515-56-57XR with ALC255 when headphone is plugged in before 
login causes few issues. I will list them below:
  - When headphones are plugged in and if I restart/shutdown-turn on the laptop 
and log in it does not detect headphones microphone at all and internal 
microphone is selected by default.
  - For output device headphones are plugged in but left/right channel is 
merged into both channels
  - To fix this need to re-plug the headphones/earphones and the issue goes 
away or after a restart/shutdown plug in only after logging in.
  - This issue does not occur when log off and log in only after a restart or 
cold boot from a shutdown while headphones/earphones are left plugged in.

  In another similar thread to this lots of other issues were fixed and they 
have been already merged into official kernel now. I will put a link to it 
below for reference. Looking to fix this issue now.
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bijay  2343 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-04-19 (156 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:a061 Quanta Computer, Inc. HD User Facing
   Bus 001 Device 003: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-56
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=9c557228-52d9-4013-9bdb-4e16712575d1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-34-generic N/A
   linux-backports-modules-5.11.0-34-generic  N/A
   linux-firmware 1.187.16
  Tags:  focal
  Uname: Linux 5.11.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 05/26/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: Type2 - Board Chassis Location
  dmi.board.name: Iris_TL
  dmi.board.vendor: TGL
  dmi.board.version: V1.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.12
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.12:bd05/26/2021:br1.12:efr1.12:svnAcer:pnAspireA515-56:pvrV1.12:sku:rvnTGL:rnIris_TL:rvrV1.12:cvnAcer:ct10:cvrV1.12:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-56
  dmi.product.sku: 
  dmi.product.version: V1.12
  dmi.sys.vendor: Acer

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


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

[Kernel-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues

[Hui Wang]

** Changed in: alsa-ucm-conf (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: alsa-ucm-conf (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: alsa-ucm-conf (Ubuntu Impish)
   Status: New => In Progress

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

Title:
  Acer Aspire 5 sound driver issues

Status in alsa-ucm-conf package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in alsa-ucm-conf source package in Hirsute:
  In Progress
Status in linux source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  In Progress
Status in alsa-ucm-conf source package in Impish:
  In Progress
Status in linux source package in Impish:
  Fix Released
Status in pulseaudio source package in Impish:
  Fix Released

Bug description:
  SRU Justification for alsa-ucm-conf:

  [Impact]
  On the machines with the sof audio driver, users could adjust the input
  volume from UI, but this only adjusts the "Capture Volume",  the "Mic
  Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture
  Volume" to max, the recorded volume is still very low.

  [Fix]
  Backport a upstream patch, the patch adds the "Mic Boost" into the
  ucm

  [Test]
  plug a headset, make sure the headset-mic is the active input device,
  adjust the input volume to %20, open a terminal and run alsamixer,
  check the "Capture Volume" and "Mic Boost" value, then adjust the
  input volume to 80%, check those values and we could see both values
  are changed.

  [Where problems could occur]
  This patch could make the parse of input volume control fail, then
  the input volume can't be changed anymore when users adjust the
  volume from UI. But this possibility is very low, I tested this patch
  on many lenovo and dell machines with sof audio driver, all worked
  well.

  

  SRU Justification for pulseaudio:

  [Impact]
  On the machines with the sof audio driver, after booting up, the
  active output device is speaker by default, we adjust the output
  volume to 100%, then we plug a headphone, and adjust the output
  volume from 100% to 20%, now in theory, the speaker's volume is
  100%, the headphone's volume is 20%. We plugout the headphone,
  the active output device becomes speaker and we expect the volume
  changes to 100%, but the output volume for speaker is 20%.

  [Fix]
  Backport a upstream patch, this patch is already in the pulseaudio-15.0,
  so impish already has this fix. Only hirsute and focal need to backport
  this patch.

  [Test]
  adjust speaker's volume to 80%, then plug headphone and adjust headphone's
  volume to 20%, unplug the headphone, the speaker's volume becomes to 80%,
  plug the headphone, the headphone's volume becomes to 20%.

  [Where problems could occur]
  The patch writes the output volume to hardware immediately when switching
  output device on the machines with sof audio driver, this could introduce
  pop noise when changing the output device, but this possibility is very
  low, I tested the patch on many lenovo and dell machines with sof audio 
driver,
  all worked as expected and have no pop noise when switching output device.

  

  The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels
  with stable update already, but it is not merged to ubuntu 5.4.0
  kernel yet, so I sent this SRU for the focal kernel.

  [Impact]
  Users plug headphone and Mic to the audio jacks, but the system
  can't detect them, and couldn't output sound through headphone and
  record sound through Mic.

  [Fix]
  Backport a upstream patch, this will set the Mic to auto-detection
  mode and set the headphone to left location.

  [Test]
  Plug a headset to the headset audio jack, both headphone and mic
  could be detected. And output the sound to headphone, could hear
  the sound, record the sound through Mic, the sound could be recorded.

  [Where problems could occur]
  The patch is specific to Acer Aspire 5 machine, if it could introduce
  regression, it will make the audio like internal mic and internal spk
  stop working. But this possibility is very low.

  Hello,

  There seems to be lots of 

[Kernel-packages] [Bug 1946128] Re: ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid signature"

[Po-Hsu Lin]

So this looks like a intermittent network (key server) issue, I will
close this bug and remove the hint. Thanks.

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

Title:
  ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart
  / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid
  signature"

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-aws-5.11 package in Ubuntu:
  Invalid

Bug description:
  linux-aws-5.11 5.11.0-1020.21~20.04.2

  5 ubuntu_lxc tests (api_test.py / lxc-test-apparmor-mount / lxc-test-
  autostart / lxc-test-no-new-privs / lxc-test-unpriv) failed on 4
  instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small

  All failures are identical:

  Downloading the image index
  ERROR: Invalid signature for /tmp/tmp.u1JHG6CYmL/index.asc

  
  I do not see the same failures when run manually.

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


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

[Kernel-packages] [Bug 1946128] Re: ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid signature"

[Po-Hsu Lin]

Retested on these failing instances and they all passed without any
issue.


** Description changed:

  linux-aws-5.11 5.11.0-1020.21~20.04.2
  
- ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge,
- i3en.24xlarge, t2.small
+ 5 ubuntu_lxc tests (api_test.py / lxc-test-apparmor-mount / lxc-test-
+ autostart / lxc-test-no-new-privs / lxc-test-unpriv) failed on 4
+ instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small
  
  All failures are identical:
  
- CmdError: Command  
failed, rc=1, Command returned non-zero exit status
- CmdError: Command  failed, 
rc=1, Command returned non-zero exit status
- CmdError: Command  
failed, rc=1, Command returned non-zero exit status
- CmdError: Command  failed, 
rc=2, Command returned non-zero exit status
+ Downloading the image index
+ ERROR: Invalid signature for /tmp/tmp.u1JHG6CYmL/index.asc
+ 
  
  I do not see the same failures when run manually.

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

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

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

Title:
  ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart
  / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid
  signature"

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-aws-5.11 package in Ubuntu:
  Invalid

Bug description:
  linux-aws-5.11 5.11.0-1020.21~20.04.2

  5 ubuntu_lxc tests (api_test.py / lxc-test-apparmor-mount / lxc-test-
  autostart / lxc-test-no-new-privs / lxc-test-unpriv) failed on 4
  instances; a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small

  All failures are identical:

  Downloading the image index
  ERROR: Invalid signature for /tmp/tmp.u1JHG6CYmL/index.asc

  
  I do not see the same failures when run manually.

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


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

[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal

[Mauricio Faria de Oliveira]

Ian,

Do you/team have contacts in here or AWS that could help with that?

I think that other lines of investigation now, after our findings
and apparent inconsistencies, would be based on speculation, and
we're better trying to get real information/logs from the system
with AWS Support.

cheers,
Mauricio

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

Title:
  Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
  r5.metal

Status in linux-aws package in Ubuntu:
  New

Bug description:
  When creating an r5.metal instance on AWS, the default kernel is
  bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
  aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.

  If I remove these patches the instance correctly boots the 4.15 kernel

  https://lists.ubuntu.com/archives/kernel-
  team/2021-September/123963.html

  With that being said, after successfully updating to the 4.15 without
  those patches applied, I can then upgrade to a 4.15 kernel with the
  above patches included, and the instance will boot properly.

  This problem only appears on metal instances, which uses NVME instead
  of XVDA devices.

  AWS instances also use the 'discard' mount option with ext4, thought
  maybe there could be a race condition between ext4 discard and journal
  flush.  Removed 'discard' from mount options and rebooted 5.4 kernel
  prior to 4.15 kernel installation, but still wouldn't boot after
  installing the 4.15 kernel.

  I have been unable to capture a stack trace using 'aws get-console-
  output'. After enabling kdump I was unable to replicate the failure.
  So there must be some sort of race with either ext4 and/or nvme.

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


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

[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal

[Mauricio Faria de Oliveira]

Today I wanted to try and instrument the boot process a bit,
since we have no serial console in the nitro metal instances.

I was looking for pstore_blk (hoping we could panic_on_warn
or panic_on_oops), but it's only available in 5.8+ it seems.)

So I decided to start with grub, and keep a progress variable
in grubenv, and use grub-reboot to boot 4.15.0-1113-aws _once_
(as it's expected to fail), then (force) stop and start again,
and check grubenv in 5.4.0-*-aws (which works.)

Interestingly, in one of such attempts 4.15.0-1113-aws WORKED.

In another attempt, I could see the progress variable for the
4.15 _and_ 5.14 kernels, so it seems that grub booted 4.15
but it didn't make it to the fully booted system. (i.e., grub
seems to be working correctly.)

In the other attempts I noticed that once we try to boot 4.15,
the system seems to become weird and not react quickly even
to the 'Force stop' method (after you try 'Stop' that doesn't
work.)

...

So, since 4.15 worked/booted once, and the systems seem weird,
and Ian just posted that he had a different result/questioned
previous result (ie, it might well be a _different_ result),
I wonder if somehow this particular instance type is acting up.

Given that 4.15 worked/booted ~20 times under kexec, it's not
unreasonable to consider there might be something going on in
normal boot.

I think we should probably engage AWS Support to try and ask
for a console log using an internally available method (seen
it elsewhere iirc), and also to clarify differences in boot
disk among instace types r5.metal (fail), r5d.metal (works),
and r5d.24xlarge (works) -- they all have EBS/nvme as '/'.

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

Title:
  Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
  r5.metal

Status in linux-aws package in Ubuntu:
  New

Bug description:
  When creating an r5.metal instance on AWS, the default kernel is
  bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
  aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.

  If I remove these patches the instance correctly boots the 4.15 kernel

  https://lists.ubuntu.com/archives/kernel-
  team/2021-September/123963.html

  With that being said, after successfully updating to the 4.15 without
  those patches applied, I can then upgrade to a 4.15 kernel with the
  above patches included, and the instance will boot properly.

  This problem only appears on metal instances, which uses NVME instead
  of XVDA devices.

  AWS instances also use the 'discard' mount option with ext4, thought
  maybe there could be a race condition between ext4 discard and journal
  flush.  Removed 'discard' from mount options and rebooted 5.4 kernel
  prior to 4.15 kernel installation, but still wouldn't boot after
  installing the 4.15 kernel.

  I have been unable to capture a stack trace using 'aws get-console-
  output'. After enabling kdump I was unable to replicate the failure.
  So there must be some sort of race with either ext4 and/or nvme.

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


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

[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal

[Ian May]

Just want to add an update.  I haven't been able to replicate
successfully booting 4.15.0-1113-aws from 5.4.0-1058-aws, so I'm
questioning whether I made a mistake the time I thought it was
successful.

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

Title:
  Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
  r5.metal

Status in linux-aws package in Ubuntu:
  New

Bug description:
  When creating an r5.metal instance on AWS, the default kernel is
  bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
  aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.

  If I remove these patches the instance correctly boots the 4.15 kernel

  https://lists.ubuntu.com/archives/kernel-
  team/2021-September/123963.html

  With that being said, after successfully updating to the 4.15 without
  those patches applied, I can then upgrade to a 4.15 kernel with the
  above patches included, and the instance will boot properly.

  This problem only appears on metal instances, which uses NVME instead
  of XVDA devices.

  AWS instances also use the 'discard' mount option with ext4, thought
  maybe there could be a race condition between ext4 discard and journal
  flush.  Removed 'discard' from mount options and rebooted 5.4 kernel
  prior to 4.15 kernel installation, but still wouldn't boot after
  installing the 4.15 kernel.

  I have been unable to capture a stack trace using 'aws get-console-
  output'. After enabling kdump I was unable to replicate the failure.
  So there must be some sort of race with either ext4 and/or nvme.

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


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

[Kernel-packages] [Bug 1945376] Re: [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the laptop

[Adam]

The only ic2 from Log I can see is i2c_hid i2c-ELAN9008:00: supply vddl
not found, using dummy regulator.

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

Title:
  [Asus ZenBook Flip UX363EA] Touchpad stops working after closing the
  laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad on my Asus ZenBook flip always stops working after I
  close the laptop! I have to restart the computer to make working
  again.

  Appreciate your support.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-36.40-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Sep 29 08:55:00 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Iris Xe Graphics [1043:1362]
  InstallationDate: Installed on 2021-03-14 (198 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX363EA_UX371EA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=ef0e66b2-d067-4bd4-9041-1a7a7a84d600 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX363EA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX363EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX363EA.306:bd01/20/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX363EA_UX371EA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnUX363EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: ZenBook UX363EA_UX371EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Kernel-packages] [Bug 1946393] [NEW] Fix byte count on fragmented packets in tc ct action

[Bodong Wang]

Public bug reported:

* Explain the bug
 
First fragmented packets (frag offset = 0) byte len is zeroed 
when stolen by ip_defrag(). And since act_ct update the stats
only afterwards (at end of execute), bytes aren't correctly
accounted for such packets. 
 
* How to test
 
Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices)
Enable HW offload and configure connection tracking OpenFlow rules as below
e.g:
ovs-ofctl del-flows br-ovs
ovs-ofctl add-flow br-ovs arp,actions=normal
ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"

Run fragmented icmp ping traffic (e.g ping -s 2000)

dump ovs rules (ovs-appctl dpctl/dump-flows), observe byte count on frag=first 
rule:
ct_state(-trk),recirc_id(0),in_port(2),eth_type(0x0800),ipv4(proto=1,frag=first),
 packets:10, bytes:13960, used:1.370s, actions:ct(zone=1),recirc(0x1)

bytes would be zero if bug occurs.

* What it could break.
 
NA

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

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

Title:
  Fix byte count on fragmented packets in tc ct action

Status in linux-bluefield package in Ubuntu:
  New

Bug description:
  * Explain the bug
   
  First fragmented packets (frag offset = 0) byte len is zeroed 
  when stolen by ip_defrag(). And since act_ct update the stats
  only afterwards (at end of execute), bytes aren't correctly
  accounted for such packets. 
   
  * How to test
   
  Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices)
  Enable HW offload and configure connection tracking OpenFlow rules as below
  e.g:
  ovs-ofctl del-flows br-ovs
  ovs-ofctl add-flow br-ovs arp,actions=normal
  ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new 
actions=ct(commit),normal"
  ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est, actions=normal"

  Run fragmented icmp ping traffic (e.g ping -s 2000)

  dump ovs rules (ovs-appctl dpctl/dump-flows), observe byte count on 
frag=first rule:
  
ct_state(-trk),recirc_id(0),in_port(2),eth_type(0x0800),ipv4(proto=1,frag=first),
 packets:10, bytes:13960, used:1.370s, actions:ct(zone=1),recirc(0x1)

  bytes would be zero if bug occurs.

  * What it could break.
   
  NA

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


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

[Kernel-packages] [Bug 1945590] Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Stephan Rohde]

@Andrea,

not sure if it helps to investigate. I have same issue on my E14 Gen2
with ubuntu 21.10

5.14.10-051410 (mainline) -> kernel panic
5.14.9-051409  (mainline) -> kernel panic
5.13.0-18  (impish)   -> kernel panic
5.13.0-17  (impish)   -> kernel panic
5.11.0-38  the last working one

Stephan

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Pietro]

Thanks to you!

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

[paul janssen]

Also tried kernel parameter watchdog_thresh=20, same problem

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

Title:
  kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

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

Bug description:
  Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad
  performance and very unresponsive to user input on Lenovo laptop
  Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G).

  When this happens you can read this kind of messages on journal:

  ---
  root@alumne-1-58:~# journalctl | grep "BUG: soft"
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 23s! [prometheus-node:4220]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 22s! [swapper/1:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 21s! [swapper/0:0]
  jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck 
for 22s! [swapper/2:0]
  jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 23s! [lxd:3975]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck 
for 23s! [swapper/2:0]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [irq/138-iwlwifi:1044]
  jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [irq/138-iwlwifi:1044]
  jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  root@alumne-1-58:~#
  ---

  Usually if you reboot everything works fine but it's very annoying
  when happens.

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


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

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

[paul janssen]

Since I was not to use "Also affects distribution/package" functionality, I add 
the following links of very simular bugreports in distro's other than Ubuntu:
* https://bugs.archlinux.org/task/71575
* https://bugs.archlinux.org/task/70236
* https://bbs.archlinux.org/viewtopic.php?id=264127
* https://forum.manjaro.org/t/soft-lockup-during-boot/64257

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

Title:
  kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

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

Bug description:
  Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad
  performance and very unresponsive to user input on Lenovo laptop
  Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G).

  When this happens you can read this kind of messages on journal:

  ---
  root@alumne-1-58:~# journalctl | grep "BUG: soft"
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 23s! [prometheus-node:4220]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 22s! [swapper/1:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 21s! [swapper/0:0]
  jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck 
for 22s! [swapper/2:0]
  jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 23s! [lxd:3975]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck 
for 23s! [swapper/2:0]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [irq/138-iwlwifi:1044]
  jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [irq/138-iwlwifi:1044]
  jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  root@alumne-1-58:~#
  ---

  Usually if you reboot everything works fine but it's very annoying
  when happens.

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Andrea Righi]

OK, so at least we know that it's a mainline issue. I'll investigate a
bit and will keep you informed. Thank you so much for all the tests!

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Pietro]

@Andrea I have disabled secure boot and tried mainline kernel 5.13.19
and 5.14.10, same kernel panic

** Attachment added: "photo_2021-10-07_20-39-03.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+attachment/5531349/+files/photo_2021-10-07_20-39-03.jpg

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946229] Re: ZTE Modem USB stick not recognized

[Josue Gomes]

Tried with 21.10 (live) and it also works:

ubuntu@ubuntu:~$ lsb_release -rd
Description:Ubuntu Impish Indri (development branch)
Release:21.10
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.13.0-16-generic #16-Ubuntu SMP Fri Sep 3 14:53:27 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux
ubuntu@ubuntu:~$ 


[Thu Oct  7 11:56:37 2021] usb 1-3: new high-speed USB device number 13 using 
xhci_hcd
[Thu Oct  7 11:56:38 2021] usb 1-3: New USB device found, idVendor=19d2, 
idProduct=1588, bcdDevice= 0.00
[Thu Oct  7 11:56:38 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, 
SerialNumber=5
[Thu Oct  7 11:56:38 2021] usb 1-3: Product: ZTE Mobile Broadband Station
[Thu Oct  7 11:56:38 2021] usb 1-3: Manufacturer: ZTE,Incorporated
[Thu Oct  7 11:56:38 2021] usb 1-3: SerialNumber: 1234567890ABCDEF
[Thu Oct  7 11:56:38 2021] usb-storage 1-3:1.0: USB Mass Storage device detected
[Thu Oct  7 11:56:38 2021] scsi host4: usb-storage 1-3:1.0
[Thu Oct  7 11:56:38 2021] usb 1-3: USB disconnect, device number 13
[Thu Oct  7 11:56:39 2021] usb 1-3: new high-speed USB device number 14 using 
xhci_hcd
[Thu Oct  7 11:56:39 2021] usb 1-3: New USB device found, idVendor=19d2, 
idProduct=1589, bcdDevice= 0.00
[Thu Oct  7 11:56:39 2021] usb 1-3: New USB device strings: Mfr=10, Product=11, 
SerialNumber=13
[Thu Oct  7 11:56:39 2021] usb 1-3: Product: ZTE Mobile Broadband Station
[Thu Oct  7 11:56:39 2021] usb 1-3: Manufacturer: ZTE,Incorporated
[Thu Oct  7 11:56:39 2021] usb 1-3: SerialNumber: 1234567890ABCDEF
[Thu Oct  7 11:56:39 2021] cdc_ether 1-3:1.0 usb0: register 'cdc_ether' at 
usb-:00:14.0-3, ZTE CDC Ethernet Device, 8a:1e:14:d0:ad:91

[Thu Oct  7 11:56:39 2021] option 1-3:1.2: GSM modem (1-port) converter detected
[Thu Oct  7 11:56:39 2021] usb 1-3: GSM modem (1-port) converter now attached 
to ttyUSB0
[Thu Oct  7 11:56:39 2021] option 1-3:1.3: GSM modem (1-port) converter detected
[Thu Oct  7 11:56:39 2021] usb 1-3: GSM modem (1-port) converter now attached 
to ttyUSB1
[Thu Oct  7 11:56:39 2021] option 1-3:1.4: GSM modem (1-port) converter detected
[Thu Oct  7 11:56:39 2021] usb 1-3: GSM modem (1-port) converter now attached 
to ttyUSB2
[Thu Oct  7 11:56:39 2021] option 1-3:1.5: GSM modem (1-port) converter detected
[Thu Oct  7 11:56:39 2021] usb 1-3: GSM modem (1-port) converter now attached 
to ttyUSB3
[Thu Oct  7 11:56:39 2021] usb-storage 1-3:1.6: USB Mass Storage device detected
[Thu Oct  7 11:56:39 2021] scsi host4: usb-storage 1-3:1.6
[Thu Oct  7 11:56:40 2021] scsi 4:0:0:0: CD-ROMZTE  USB SCSI 
CD-ROM  2.31 PQ: 0 ANSI: 0 CCS
[Thu Oct  7 11:56:40 2021] scsi 4:0:0:1: Direct-Access ZTE  MMC Storage 
 2.31 PQ: 0 ANSI: 0 CCS
[Thu Oct  7 11:56:40 2021] sr 4:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy

[Thu Oct  7 11:57:17 2021] sr 4:0:0:0: Attached scsi CD-ROM sr0
[Thu Oct  7 11:57:17 2021] sr 4:0:0:0: Attached scsi generic sg3 type 5
[Thu Oct  7 11:57:17 2021] sd 4:0:0:1: Attached scsi generic sg4 type 0
[Thu Oct  7 11:57:17 2021] sd 4:0:0:1: [sdd] 0 512-byte logical blocks: (0 B/0 
B)
[Thu Oct  7 11:57:17 2021] sd 4:0:0:1: [sdd] 0-byte physical blocks
[Thu Oct  7 11:57:17 2021] sd 4:0:0:1: [sdd] Test WP failed, assume Write 
Enabled
[Thu Oct  7 11:57:17 2021] sd 4:0:0:1: [sdd] Asking for cache data failed
[Thu Oct  7 11:57:17 2021] sd 4:0:0:1: [sdd] Assuming drive cache: write through
[Thu Oct  7 11:57:54 2021] sd 4:0:0:1: [sdd] Attached SCSI removable disk

[Thu Oct  7 11:58:31 2021] ISO 9660 Extensions: Microsoft Joliet Level 1
[Thu Oct  7 11:58:31 2021] ISOFS: changing to secondary root

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

Title:
  ZTE Modem USB stick not recognized

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ~$ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  
  Linux ubuntu-dev 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

  ZTE Modem USB stick is not recognized. Fails with 'rejecting I/O to
  dead device' error.

  [qua out  6 09:47:20 2021] usb 1-3: new high-speed USB device number 19 using 
xhci_hcd
  [qua out  6 09:47:20 2021] usb 1-3: New USB device found, idVendor=19d2, 
idProduct=1588, bcdDevice= 0.00
  [qua out  6 09:47:20 2021] usb 1-3: New USB device strings: Mfr=2, Product=3, 
SerialNumber=5
  [qua out  6 09:47:20 2021] usb 1-3: Product: ZTE Mobile Broadband Station
  [qua out  6 09:47:20 2021] usb 1-3: Manufacturer: ZTE,Incorporated
  [qua out  6 09:47:20 2021] usb 1-3: SerialNumber: 1234567890ABCDEF
  [qua out  6 09:47:20 2021] usb-storage 1-3:1.0: USB Mass Storage device 
detected
  [qua out  6 09:47:20 2021] scsi host4: usb-storage 1-3:1.0
  [qua out  6 09:47:21 2021] usb 1-3: USB disconnect, device number 19
  [qua out  6 09:47:21 2021] usb 1-3: new high-speed USB device number 20 using 
xhci_hcd
  [qua out  6 09:47:22 2021] usb 1-3: New USB 

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Andrea Righi]

Maybe disable secure boot from the BIOS? Test kernels can't be signed,
so I guess that's the only way...

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946383] [NEW] Fix missing recording from headset mic

[Kai-Heng Feng]

Public bug reported:

[Impact] 
When using headset mic to record, the beginning of 2 seconds period is
not recorded.

[Fix]
Skip shutup routines for the codec. The shutup routines somehow
interferes headset mic recording.

[Test]
External headset mic no longer records blank period once the patch is
applied.

[Where problems could occur]
Shutup routines are mainly for outputs like headphone and speakers.
Since the patch is using a rather generic match for both ALC236 and
ALC256, many systems might start to observe pop sound from the audio
outputs.

** Affects: hwe-next
 Importance: Undecided
 Status: New

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

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

** Affects: linux-oem-5.13 (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: linux-oem-5.14 (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed


** Tags: oem-priority originate-from-1942149 stella

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

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

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

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

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

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

** Changed in: linux-oem-5.14 (Ubuntu Focal)
   Status: New => Confirmed

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

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

** Tags added: oem-priority originate-from-1942149 stella

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

Title:
  Fix missing recording from headset mic

Status in HWE Next:
  New
Status in linux-oem-5.13 package in Ubuntu:
  Invalid
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux-oem-5.13 source package in Focal:
  Confirmed
Status in linux-oem-5.14 source package in Focal:
  Confirmed

Bug description:
  [Impact] 
  When using headset mic to record, the beginning of 2 seconds period is
  not recorded.

  [Fix]
  Skip shutup routines for the codec. The shutup routines somehow
  interferes headset mic recording.

  [Test]
  External headset mic no longer records blank period once the patch is
  applied.

  [Where problems could occur]
  Shutup routines are mainly for outputs like headphone and speakers.
  Since the patch is using a rather generic match for both ALC236 and
  ALC256, many systems might start to observe pop sound from the audio
  outputs.

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


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

[Kernel-packages] [Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64

[Kleber Sacilotto de Souza]

** Tags added: sru-20210927

** Summary changed:

- cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64
+ cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64

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

Title:
  cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on amd64/ARM64

Status in ubuntu-kernel-tests:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in linux source package in Focal:
  Confirmed

Bug description:
  This issue can be found on both ThunderX and Moonshot ARM64

  <<>>
  incrementing stop
  Name:   cpuhotplug04
  Date:   Thu Jul 11 08:34:50 UTC 2019
  Desc:   Does it prevent us from offlining the last CPU?

  sh: echo: I/O error
  cpuhotplug04 1 TFAIL: Could not offline cpu0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=9 cstime=4
  <<>>

  Steps to run this test:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-25-generic 4.18.0-25.26
  ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 06:57 seq
   crw-rw 1 root audio 116, 33 Jul 11 06:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jul 11 08:28:42 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-25-generic N/A
   linux-backports-modules-4.18.0-25-generic  N/A
   linux-firmware 1.175.6
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

[Łukasz Zemczak]

** Changed in: linux-aws (Ubuntu Impish)
   Importance: Undecided => Critical

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

Title:
  impish:linux 5.13 panic during systemd autotest

Status in Release Notes for Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Impish:
  New

Bug description:
  Found this when running the systemd autopkgtest on linux-aws
  5.13.0-1004.5 (apparently it seems to affect nested kvm only):

  systemd-testsuite login: [   70.235559] int3:  [#1] SMP NOPTI
  [   70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted 
5.13.0-1004-aws #5-Ubuntu
  [   70.237852] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.14.0-2 04/01/2014
  [   70.237864] RIP: 0010:kmem_cache_alloc+0x57/0x240
  [   70.237875] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 
c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7
  [   70.237994] RSP: 0018:aabd001cfd78 EFLAGS: 0286
  [   70.239655] RAX: 97e8411da400 RBX: 1000 RCX: 
0400
  [   70.239670] RDX: 0001 RSI: 0cc0 RDI: 
97e8411da400
  [   70.239679] RBP: aabd001cfdb8 R08:  R09: 
9802
  [   70.239688] R10:  R11:  R12: 
97e8411da400
  [   70.239696] R13: 97e8411da400 R14: 0cc0 R15: 
b2737cf0
  [   70.239705] FS:  7fc6fc243380() GS:97e85c00() 
knlGS:
  [   70.239713] CS:  0010 DS:  ES:  CR0: 80050033
  [   70.239720] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 
06f0
  [   70.239727] Call Trace:
  [   70.239733]  getname_flags.part.0+0x30/0x1b0
  [   70.239741]  getname+0x35/0x50
  [   70.239746]  do_sys_openat2+0x64/0x150
  [   70.239753]  __x64_sys_openat+0x55/0x90
  [   70.239759]  do_syscall_64+0x61/0xb0
  [   70.239766]  ? do_syscall_64+0x6e/0xb0
  [   70.239772]  ? do_sync_core+0x26/0x30
  [   70.239779]  ? flush_smp_call_function_queue+0x119/0x190
  [   70.239786]  ? exit_to_user_mode_prepare+0x37/0xb0
  [   70.239793]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   70.239800]  ? irqentry_exit+0x19/0x30
  [   70.239807]  ? sysvec_call_function+0x4e/0x90
  [   70.239813]  ? asm_sysvec_call_function+0xa/0x20
  [   70.239819]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   70.239826] RIP: 0033:0x7fc6fca946e4
  [   70.239834] Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 16 d2 f7 ff 44 8b 54 
24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 4
  [   70.239845] RSP: 002b:7ffc9699f1a0 EFLAGS: 0293 ORIG_RAX: 
0101
  [   70.240063] RAX: ffda RBX:  RCX: 
7fc6fca946e4
  [   70.240075] RDX: 00080802 RSI: 556e8d5885d0 RDI: 
ff9c
  [   70.240085] RBP: 556e8d5885d0 R08:  R09: 

  [   70.240095] R10:  R11: 0293 R12: 
00080802
  [   70.240104] R13:  R14: 556e8d59dd90 R15: 
fffa
  [   70.240113] Modules linked in: btrfs blake2b_generic zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raidy
  [   70.281001] ---[ end trace 044cf87b8c867a36 ]---
  [   70.281099] RIP: 0010:kmem_cache_alloc+0x57/0x240
  [   70.281107] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 
c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7
  [   70.281115] RSP: 0018:aabd001cfd78 EFLAGS: 0286
  [   70.281132] RAX: 97e8411da400 RBX: 1000 RCX: 
0400
  [   70.281138] RDX: 0001 RSI: 0cc0 RDI: 
97e8411da400
  [   70.281143] RBP: aabd001cfdb8 R08:  R09: 
9802
  [   70.281148] R10:  R11:  R12: 
97e8411da400
  [   70.281154] R13: 97e8411da400 R14: 0cc0 R15: 
b2737cf0
  [   70.281159] FS:  7fc6fc243380() GS:97e85c00() 
knlGS:
  [   70.281173] CS:  0010 DS:  ES:  CR0: 80050033
  [   70.281178] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 
06f0
  [   70.281183] Kernel panic - not syncing: Fatal exception in interrupt
  [   70.282418] Kernel Offset: 0x3140 from 0x8100 (relocation 
range: 0x8000-0xbfff)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1946001/+subscriptions


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

[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

[paul janssen]

Same same, after upgrade from 5.8 to 5.11.
Soft lockups during boot, long boot time, and after that a very slow machine.
My machine is also Intel Celeron based, like the previous reports.

After login into the desktop environment, the "atop" program shows that almost 
all cpu time is spent in irq, where this normally is close to 0 percent. (see 
attachment)
Login in was hard because not all keyboard input was processed.
The "old" ubuntu is still working as expected (see attachment).

See attachment for logs.

I tried the following:
* Ubuntu Live image on usb: same problem
* Fedora Live image on usb: same problem
* wait until the boot process comes through and collect the logs (kernel 
params: nomodeset debug verbose)
* perform an apt-get upgrade; apt-get update, reboot, problem still present
* fsck , all was okay.
* tried kernel parameter intel_idle.max_cstate=1 
(https://wiki.archlinux.org/title/Intel_graphics#Baytrail_complete_freeze), 
same problem
* tried kernel parameter noapic (following a hunch), same problem




** Attachment added: "dmesg, lshw ,lspci, syslog, screenshot atop"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1931001/+attachment/5531320/+files/logs.zip

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

Title:
  kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!

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

Bug description:
  Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad
  performance and very unresponsive to user input on Lenovo laptop
  Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G).

  When this happens you can read this kind of messages on journal:

  ---
  root@alumne-1-58:~# journalctl | grep "BUG: soft"
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [swapper/3:0]
  may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 23s! [prometheus-node:4220]
  may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 23s! [swapper/0:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 22s! [swapper/1:0]
  jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 22s! [swapper/0:0]
  jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck 
for 21s! [swapper/0:0]
  jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck 
for 22s! [swapper/2:0]
  jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck 
for 23s! [lxd:3975]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck 
for 23s! [swapper/2:0]
  jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [irq/138-iwlwifi:1044]
  jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 23s! [irq/138-iwlwifi:1044]
  jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck 
for 22s! [irq/138-iwlwifi:1044]
  root@alumne-1-58:~#
  ---

  Usually if you reboot everything works fine but it's very annoying
  when happens.

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


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

[Kernel-packages] [Bug 1946001] Re: impish:linux 5.13 panic during systemd autotest

[Andrea Righi]

Update: apparently CONFIG_KFENCE can only reduce the probability to
trigger the bug, so it's not a reliable fix. According to all the traces
that we got the soft lockup is always happening to any SLUB allocation
function (__kmalloc, kmem_cache_alloc, and similar), and the instruction
pointer is on a static branch call. And static branches are used only by
KFENCE in SLUB, hence the test of disabling KFENCE.

** Summary changed:

- impish:linux-aws 5.13 panic during systemd autotest
+ impish:linux 5.13 panic during systemd autotest

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

Title:
  impish:linux 5.13 panic during systemd autotest

Status in Release Notes for Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Impish:
  New

Bug description:
  Found this when running the systemd autopkgtest on linux-aws
  5.13.0-1004.5 (apparently it seems to affect nested kvm only):

  systemd-testsuite login: [   70.235559] int3:  [#1] SMP NOPTI
  [   70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted 
5.13.0-1004-aws #5-Ubuntu
  [   70.237852] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.14.0-2 04/01/2014
  [   70.237864] RIP: 0010:kmem_cache_alloc+0x57/0x240
  [   70.237875] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 
c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7
  [   70.237994] RSP: 0018:aabd001cfd78 EFLAGS: 0286
  [   70.239655] RAX: 97e8411da400 RBX: 1000 RCX: 
0400
  [   70.239670] RDX: 0001 RSI: 0cc0 RDI: 
97e8411da400
  [   70.239679] RBP: aabd001cfdb8 R08:  R09: 
9802
  [   70.239688] R10:  R11:  R12: 
97e8411da400
  [   70.239696] R13: 97e8411da400 R14: 0cc0 R15: 
b2737cf0
  [   70.239705] FS:  7fc6fc243380() GS:97e85c00() 
knlGS:
  [   70.239713] CS:  0010 DS:  ES:  CR0: 80050033
  [   70.239720] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 
06f0
  [   70.239727] Call Trace:
  [   70.239733]  getname_flags.part.0+0x30/0x1b0
  [   70.239741]  getname+0x35/0x50
  [   70.239746]  do_sys_openat2+0x64/0x150
  [   70.239753]  __x64_sys_openat+0x55/0x90
  [   70.239759]  do_syscall_64+0x61/0xb0
  [   70.239766]  ? do_syscall_64+0x6e/0xb0
  [   70.239772]  ? do_sync_core+0x26/0x30
  [   70.239779]  ? flush_smp_call_function_queue+0x119/0x190
  [   70.239786]  ? exit_to_user_mode_prepare+0x37/0xb0
  [   70.239793]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   70.239800]  ? irqentry_exit+0x19/0x30
  [   70.239807]  ? sysvec_call_function+0x4e/0x90
  [   70.239813]  ? asm_sysvec_call_function+0xa/0x20
  [   70.239819]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   70.239826] RIP: 0033:0x7fc6fca946e4
  [   70.239834] Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 16 d2 f7 ff 44 8b 54 
24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 4
  [   70.239845] RSP: 002b:7ffc9699f1a0 EFLAGS: 0293 ORIG_RAX: 
0101
  [   70.240063] RAX: ffda RBX:  RCX: 
7fc6fca946e4
  [   70.240075] RDX: 00080802 RSI: 556e8d5885d0 RDI: 
ff9c
  [   70.240085] RBP: 556e8d5885d0 R08:  R09: 

  [   70.240095] R10:  R11: 0293 R12: 
00080802
  [   70.240104] R13:  R14: 556e8d59dd90 R15: 
fffa
  [   70.240113] Modules linked in: btrfs blake2b_generic zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raidy
  [   70.281001] ---[ end trace 044cf87b8c867a36 ]---
  [   70.281099] RIP: 0010:kmem_cache_alloc+0x57/0x240
  [   70.281107] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 
c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7
  [   70.281115] RSP: 0018:aabd001cfd78 EFLAGS: 0286
  [   70.281132] RAX: 97e8411da400 RBX: 1000 RCX: 
0400
  [   70.281138] RDX: 0001 RSI: 0cc0 RDI: 
97e8411da400
  [   70.281143] RBP: aabd001cfdb8 R08:  R09: 
9802
  [   70.281148] R10:  R11:  R12: 
97e8411da400
  [   70.281154] R13: 97e8411da400 R14: 0cc0 R15: 
b2737cf0
  [   70.281159] FS:  7fc6fc243380() GS:97e85c00() 
knlGS:
  [   70.281173] CS:  0010 DS:  ES:  CR0: 80050033
  [   70.281178] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 
06f0
  [   70.281183] Kernel panic - not syncing: Fatal exception in interrupt
  [   70.282418] Kernel Offset: 0x3140 from 0x8100 (relocation 
range: 

[Kernel-packages] [Bug 1946001] Re: impish:linux-aws 5.13 panic during systemd autotest

[Dimitri John Ledkov]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: linux-aws (Ubuntu Impish)
Milestone: None => ubuntu-21.10

** Tags added: rls-ff-incoming

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

Title:
  impish:linux-aws 5.13 panic during systemd autotest

Status in Release Notes for Ubuntu:
  New
Status in linux-aws package in Ubuntu:
  New
Status in linux-aws source package in Impish:
  New

Bug description:
  Found this when running the systemd autopkgtest on linux-aws
  5.13.0-1004.5 (apparently it seems to affect nested kvm only):

  systemd-testsuite login: [   70.235559] int3:  [#1] SMP NOPTI
  [   70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted 
5.13.0-1004-aws #5-Ubuntu
  [   70.237852] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.14.0-2 04/01/2014
  [   70.237864] RIP: 0010:kmem_cache_alloc+0x57/0x240
  [   70.237875] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 
c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7
  [   70.237994] RSP: 0018:aabd001cfd78 EFLAGS: 0286
  [   70.239655] RAX: 97e8411da400 RBX: 1000 RCX: 
0400
  [   70.239670] RDX: 0001 RSI: 0cc0 RDI: 
97e8411da400
  [   70.239679] RBP: aabd001cfdb8 R08:  R09: 
9802
  [   70.239688] R10:  R11:  R12: 
97e8411da400
  [   70.239696] R13: 97e8411da400 R14: 0cc0 R15: 
b2737cf0
  [   70.239705] FS:  7fc6fc243380() GS:97e85c00() 
knlGS:
  [   70.239713] CS:  0010 DS:  ES:  CR0: 80050033
  [   70.239720] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 
06f0
  [   70.239727] Call Trace:
  [   70.239733]  getname_flags.part.0+0x30/0x1b0
  [   70.239741]  getname+0x35/0x50
  [   70.239746]  do_sys_openat2+0x64/0x150
  [   70.239753]  __x64_sys_openat+0x55/0x90
  [   70.239759]  do_syscall_64+0x61/0xb0
  [   70.239766]  ? do_syscall_64+0x6e/0xb0
  [   70.239772]  ? do_sync_core+0x26/0x30
  [   70.239779]  ? flush_smp_call_function_queue+0x119/0x190
  [   70.239786]  ? exit_to_user_mode_prepare+0x37/0xb0
  [   70.239793]  ? irqentry_exit_to_user_mode+0x9/0x20
  [   70.239800]  ? irqentry_exit+0x19/0x30
  [   70.239807]  ? sysvec_call_function+0x4e/0x90
  [   70.239813]  ? asm_sysvec_call_function+0xa/0x20
  [   70.239819]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [   70.239826] RIP: 0033:0x7fc6fca946e4
  [   70.239834] Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 16 d2 f7 ff 44 8b 54 
24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 4
  [   70.239845] RSP: 002b:7ffc9699f1a0 EFLAGS: 0293 ORIG_RAX: 
0101
  [   70.240063] RAX: ffda RBX:  RCX: 
7fc6fca946e4
  [   70.240075] RDX: 00080802 RSI: 556e8d5885d0 RDI: 
ff9c
  [   70.240085] RBP: 556e8d5885d0 R08:  R09: 

  [   70.240095] R10:  R11: 0293 R12: 
00080802
  [   70.240104] R13:  R14: 556e8d59dd90 R15: 
fffa
  [   70.240113] Modules linked in: btrfs blake2b_generic zstd_compress raid10 
raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raidy
  [   70.281001] ---[ end trace 044cf87b8c867a36 ]---
  [   70.281099] RIP: 0010:kmem_cache_alloc+0x57/0x240
  [   70.281107] Code: 08 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 c7 45 
c8 00 00 00 00 e8 d6 bb ff ff 49 89 c4 48 85 c0 0f 84 cd 00 00 00 cc <0a> 7
  [   70.281115] RSP: 0018:aabd001cfd78 EFLAGS: 0286
  [   70.281132] RAX: 97e8411da400 RBX: 1000 RCX: 
0400
  [   70.281138] RDX: 0001 RSI: 0cc0 RDI: 
97e8411da400
  [   70.281143] RBP: aabd001cfdb8 R08:  R09: 
9802
  [   70.281148] R10:  R11:  R12: 
97e8411da400
  [   70.281154] R13: 97e8411da400 R14: 0cc0 R15: 
b2737cf0
  [   70.281159] FS:  7fc6fc243380() GS:97e85c00() 
knlGS:
  [   70.281173] CS:  0010 DS:  ES:  CR0: 80050033
  [   70.281178] CR2: 7fc6f9249000 CR3: 03c5c000 CR4: 
06f0
  [   70.281183] Kernel panic - not syncing: Fatal exception in interrupt
  [   70.282418] Kernel Offset: 0x3140 from 0x8100 (relocation 
range: 0x8000-0xbfff)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1946001/+subscriptions


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

[Kernel-packages] [Bug 1946149] Re: Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on r5.metal

[Ian May]

Thanks for the in-depth update Mauricio!  Is there any investigation
you'd like me to specifically target?

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

Title:
  Bionic/linux-aws Boot failure downgrading from Bionic/linux-aws-5.4 on
  r5.metal

Status in linux-aws package in Ubuntu:
  New

Bug description:
  When creating an r5.metal instance on AWS, the default kernel is
  bionic/linux-aws-5.4(5.4.0-1056-aws), when changing to bionic/linux-
  aws(4.15.0-1113-aws) the machine fails to boot the 4.15 kernel.

  If I remove these patches the instance correctly boots the 4.15 kernel

  https://lists.ubuntu.com/archives/kernel-
  team/2021-September/123963.html

  With that being said, after successfully updating to the 4.15 without
  those patches applied, I can then upgrade to a 4.15 kernel with the
  above patches included, and the instance will boot properly.

  This problem only appears on metal instances, which uses NVME instead
  of XVDA devices.

  AWS instances also use the 'discard' mount option with ext4, thought
  maybe there could be a race condition between ext4 discard and journal
  flush.  Removed 'discard' from mount options and rebooted 5.4 kernel
  prior to 4.15 kernel installation, but still wouldn't boot after
  installing the 4.15 kernel.

  I have been unable to capture a stack trace using 'aws get-console-
  output'. After enabling kdump I was unable to replicate the failure.
  So there must be some sort of race with either ext4 and/or nvme.

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


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

[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P

[You-Sheng Yang]

SRU v2:
* https://lists.ubuntu.com/archives/kernel-team/2021-October/124678.html 
(oem-5.13)
* https://lists.ubuntu.com/archives/kernel-team/2021-October/124690.html 
(oem-5.14)

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

Title:
  Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P

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

Bug description:
  [SRU Justfication]

  [Impact]

  Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into
  Intel processors. As a result, their driver may have to be revised
  across processor generations.

  [Fix]

  This depends on a few changes set to address all issues on supporting:
  * PCI [8086:7af0] Subsystem [8086:4090] (AX211)
    * WiFi: iwlwifi-so-a0-gf-a0-*
    * BT: intel/ibt-1040-0041.* (ADL-S)
    * BT: intel/ibt-0040-0041.* (ADL-P)
  * PCI [8086:7af0] Subsystem [8086:4070] (AX201)
    * WiFi: iwlwifi-so-a0-hr-b0-*
    * BT: intel/ibt-1040-4150.*
    * BT: intel/ibt-0040-4150.*
  * PCI [8086:7af0] Subsystem [8086:0aaa] (9462)
    * WiFi: iwlwifi-so-a0-jf-b0-*
    * BT: intel/ibt-1040-1020.*

  AX201 wifi firmware for ADL platforms will be available with FW
  API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices"
  will be required. Depending fixes are pulled as well.

  For reset of them, 3 additional commits for iwlwifi, also in mainline
  now, are required.

  The last patch for 9462 Bluetooth is still under review at the time of
  writing. This is the only patch that is not yet in unstable.

  [Test Case]

  Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth
  is working.

  [Where problems could occur]

  While this is a new generation, we may have common issues like power
  consumption, network throughput, suspend/resume issues.

  [Other Info]

  Intel is to release the corresponding firmware blobs next week. These
  are verified with pre-released firmware.

  == original bug report ==

  * PCI [8086:7af0] Subsystem [8086:4090] (AX211)
    * WiFi: iwlwifi-so-a0-gf-a0-*
    * BT: intel/ibt-1040-0041.sfi
  * PCI [8086:7af0] Subsystem [8086:4070] (AX201)
    * WiFi: iwlwifi-so-a0-hr-b0-*
    * BT: ibt-1040-4150.sfi
  * PCI [8086:7af0] Subsystem [8086:0264] (9462)
    * WiFi: iwlwifi-so-a0-jf-b0-*
    * BT: intel/ibt-1040-1020.*
* BT: intel/ibt-0040-1020.*

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


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

[Kernel-packages] [Bug 1838575] Re: passthrough devices cause >17min boot delay

[Colin Ian King]

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

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

Title:
  passthrough devices cause >17min boot delay

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

Bug description:
  Adding passthrough devices to a guest introduces a boot delay of > 17
  minutes. During this time libvirt reports the guest to be "paused".
  The delay does not seem to scale with the # of hostdevs - that is, 1
  hostdev causes about a 17min delay, while 16 only bumps that up to
  ~18min. Removing all hostdevs avoids the delay.

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


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

[Kernel-packages] [Bug 1943185] Re: Fix AMD GPIO-based power button

[Timo Aaltonen]

included in -1003.3

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

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

Title:
   Fix AMD GPIO-based power button

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Fix Released

Bug description:
  [Impact]

   Power button or other wake up sources connected to GPIO may not wake
  up idle AMD systems.

  [Fix]

   Enable and disable power management wakeup mode, which is disabled by
  default, accordingly.

   The patch series can be found @ https://lore.kernel.org/linux-
  gpio/20210831120613.1514899-1-basavaraj.nati...@amd.com/

  [Test]

   This is requested by AMD.

  [Where problems could occur]

   Only AMD systems that require GPIOs as wake sources will be affected,
  i.e. amd_gpio_irq_set_wake with "on != 0", but this is intended
  behaviour.

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


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

[Kernel-packages] [Bug 1946368] [NEW] HDMI output freezes under current/proposed impish kernels

[Dave Jones]

Public bug reported:

Under the current (5.13.0-1007.8) or proposed (5.13.0-1008.9) kernels
for the Ubuntu Pi pre-installed desktop impish release, the HDMI output
occasionally freezes. A known workaround at this time is to change the
following line in /boot/firmware/config.txt:

dtoverlay=vc4-kms-v3d

To the following:

dtoverlay=vc4-fkms-v3d

In other words, to use the "fake" KMS overlay (fkms) instead of the
"full" KMS overlay (kms).

I've been unable to determine a reliable method of guaranteeing a
freeze, but it appears to occur much more readily when video playback is
occurring, and when other interactions (especially moving windows
around, minimizing, restoring) occurs simultaneously.  Display suspend
also periodically causes the same hang, which made me suspect this might
be related to #1944397 but it appears that had a separate cause (now
resolved).

The following dmesg outputs have been observed immediately after the
display hang; this one from 1007.8:

[  513.762138] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[  513.762288] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] co
mmit wait timed out 
[  513.762381] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] 
*ERROR* [CRTC:76:crtc-3] flip_
done timed out  
[  524.002211] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[  524.002404] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] 
*ERROR* [PLANE:205:plane-25
] commit wait timed out
[  534.242499] [drm:drm_crtc_commit_wait [drm]] *ERROR* flip_done timed out
[  534.242657] vc4-drm gpu: [drm] *ERROR* Timed out waiting for commit
[  534.250685] [ cut here ]
[  534.250701] refcount_t: underflow; use-after-free.
[  534.250735] WARNING: CPU: 1 PID: 120 at lib/refcount.c:87 
refcount_dec_not_one+0xa0/0xbc
[  534.250758] Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg 
hci_uart btqca btrtl btbcm
 btintel bnep snd_soc_hdmi_codec vc4 btsdio snd_soc_core input_leds bluetooth 
snd_compress snd_bcm2835(C)
 snd_pcm_dmaengine ecdh_generic ecc snd_pcm brcmfmac snd_seq_midi 
snd_seq_midi_event bcm2835_codec(C) bcm
2835_isp(C) bcm2835_v4l2(C) brcmutil snd_rawmidi v4l2_mem2mem 
bcm2835_mmal_vchiq(C) videobuf2_dma_contig 
videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 snd_seq 
videobuf2_common videodev snd_seq_devi
ce mc snd_timer vc_sm_cma(C) raspberrypi_hwmon snd bcm2835_gpiomem rpivid_mem 
uio_pdrv_genirq uio sch_fq_
codel ip_tables x_tables autofs4 btrfs blake2b_generic xor xor_neon 
zstd_compress hid_generic usbhid raid
6_pq libcrc32c dm_mirror dm_region_hash dm_log spidev dwc2 v3d roles udc_core 
gpu_sched crct10dif_ce i2c_
brcmstb i2c_bcm2835 spi_bcm2835 drm_kms_helper syscopyarea xhci_pci 
xhci_pci_renesas sysfillrect sysimgbl
t fb_sys_fops cec drm phy_generic ac97_bus aes_arm64 
[  534.251066] CPU: 1 PID: 120 Comm: kworker/1:2 Tainted: GWC
5.13.0-1007-raspi #8-Ubuntu
[  534.251076] Hardware name: Raspberry Pi 400 Rev 1.1 (DT)
[  534.251083] Workqueue: events drm_mode_rmfb_work_fn [drm]
[  534.251239] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--)
[  534.251248] pc : refcount_dec_not_one+0xa0/0xbc
[  534.251257] lr : refcount_dec_not_one+0xa0/0xbc
[  534.251265] sp : 8000118cbb50
[  534.251269] x29: 8000118cbb50 x28: 6cf7ee894400 x27: 6cf80502e000
[  534.251285] x26: 6cf80502e000 x25: 0006 x24: 6cf7ee94c500
[  534.251300] x23: a94dff246018 x22: 6cf833068880 x21: 6cf805027c80
[  534.251314] x20: 6cf88ead75ac x19: 6cf88ead7400 x18: 
[  534.251328] x17:  x16: a94e0a243314 x15: 
[  534.251342] x14:  x13: 0030 x12: 800010035000
[  534.251356] x11: a94e0b30dfd0 x10: f000 x9 : a94e09d09f54
[  534.251370] x8 : efff x7 : a94e0b30dfd0 x6 : 
[  534.251384] x5 : 6cf8b799f948 x4 :  x3 : 0027
[  534.251397] x2 :  x1 :  x0 : 6cf800abec80
[  534.251411] Call trace:
[  534.251416]  refcount_dec_not_one+0xa0/0xbc
[  534.251424]  vc4_bo_dec_usecnt+0x2c/0x120 [vc4]
[  534.251473]  vc4_cleanup_fb+0x3c/0x4c [vc4]
[  534.251518]  drm_atomic_helper_cleanup_planes+0x74/0xa0 [drm_kms_helper]
[  534.251604]  vc4_atomic_commit_tail+0x24c/0x36c [vc4]
[  534.251648]  commit_tail+0xac/0x190 [drm_kms_helper]
[  534.251723]  drm_atomic_helper_commit+0x168/0x380 [drm_kms_helper]
[  534.251796]  drm_atomic_commit+0x58/0x70 [drm]
[  534.251936]  atomic_remove_fb+0x2a8/0x2f4 [drm]
[  534.252073]  drm_framebuffer_remove+0x164/0x18c [drm]
[  534.252209]  drm_mode_rmfb_work_fn+0x50/0x70 [drm]
[  534.252346]  process_one_work+0x200/0x4d0
[  534.252359]  worker_thread+0x2c8/0x470
[  534.252367]  kthread+0x12c/0x140
[  534.252374]  ret_from_fork+0x10/0x3c
[  

[Kernel-packages] [Bug 1940564] Re: Azure kernels fail to boot on some large Azure instance types

[Tim Gardner]

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

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

Title:
  Azure kernels fail to boot on some large Azure instance types

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-5.4 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-5.4 source package in Bionic:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-5.4 source package in Focal:
  New
Status in linux source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure-5.4 source package in Hirsute:
  New
Status in linux source package in Impish:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure-5.4 source package in Impish:
  New

Bug description:
  [Impact]

  Azure kernels fail to boot on large Azure instance types.

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1940564] Re: Azure kernels fail to boot on some large Azure instance types

[Tim Gardner]

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

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

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

Title:
  Azure kernels fail to boot on some large Azure instance types

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure-5.4 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux-azure-5.4 source package in Bionic:
  New
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  Fix Committed
Status in linux-azure-5.4 source package in Focal:
  New
Status in linux source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux-azure-5.4 source package in Hirsute:
  New
Status in linux source package in Impish:
  In Progress
Status in linux-azure source package in Impish:
  In Progress
Status in linux-azure-5.4 source package in Impish:
  New

Bug description:
  [Impact]

  Azure kernels fail to boot on large Azure instance types.

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

[Sebastian Heiden]

The latest Ubuntu 21.10 install still comes with zfs-kmod-2.0.3, which
prevents the system from booting in the first place.

Installing zfs-dkms via the recovery mode, which updates the zfs-kmod to
version 2.0.6, fixed the issue for me.

I hope that the release image of Ubuntu 21.10 will ship with zfs-
kmod-2.0.6 in the kernel by default.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

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

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

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


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

[Kernel-packages] [Bug 1940564] Re: bionic linux Ubuntu-4.15.0-155.162 fails to boot on some large Azure instance types

[Tim Gardner]

** Summary changed:

- bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3
+ bionic linux Ubuntu-4.15.0-155.162 fails to boot on some large Azure instance 
types

** Summary changed:

- bionic linux Ubuntu-4.15.0-155.162 fails to boot on some large Azure instance 
types
+ linux-azure fails to boot on some large Azure instance types

** Description changed:

  [Impact]
  
- bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure
- Standard_D48_v3
+ Azure kernels fail to boot on large Azure instance types.
  
  [Fix]
  
  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"
  
  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.
  
  [Test Plan]
  
  Install and boot on an Azure Standard_D48_v3 instance.
  
  [Where problems could occur]
  
  iscsi requests could hang

** Summary changed:

- linux-azure fails to boot on some large Azure instance types
+ Azure kernels fail to boot on some large Azure instance types

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

Title:
  Azure kernels fail to boot on some large Azure instance types

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux-azure source package in Impish:
  In Progress

Bug description:
  [Impact]

  Azure kernels fail to boot on large Azure instance types.

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1940564] Re: bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure Standard_D48_v3

[Tim Gardner]

This appears to be an issue with all instance types with large numbers
of CPUs. focal/linux-azure fails on Standard_M416s_v2.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure
  Standard_D48_v3

Status in linux package in Ubuntu:
  In Progress
Status in linux-azure package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Focal:
  In Progress
Status in linux-azure source package in Focal:
  In Progress
Status in linux source package in Hirsute:
  In Progress
Status in linux-azure source package in Hirsute:
  In Progress
Status in linux source package in Impish:
  In Progress
Status in linux-azure source package in Impish:
  In Progress

Bug description:
  [Impact]

  bionic linux Ubuntu-4.15.0-155.162 fails to boot on Azure
  Standard_D48_v3

  [Fix]

  revert 10b9a1068ba301b6458a308c749eb0b93951010c ("scsi: core: Cap
  scsi_host cmd_per_lun at can_queue") from "UBUNTU: upstream stable to
  v4.14.240, v4.19.198"

  This commit originates from an unreleased kernel (5.14-rc1). According
  to the commit log it purports to head off possible future problems. It
  does not appear to address a specific bug. It has been backported to
  4.14.y and 4.19.y.

  [Test Plan]

  Install and boot on an Azure Standard_D48_v3 instance.

  [Where problems could occur]

  iscsi requests could hang

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


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

[Kernel-packages] [Bug 1945845] Re: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted

[Timo Aaltonen]

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

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

Title:
  package linux-firmware 1.187.16 failed to install/upgrade: unable to
  open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not
  permitted

Status in linux-firmware package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  linux-firmware:
Installed: 1.187.16
Candidate: 1.187.17
Version table:
   1.187.17 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
   *** 1.187.16 100
  100 /var/lib/dpkg/status
   1.187 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages

  Installation failed during system update.

  Unpacking libgl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.2) over 
(21.0.3-0ubuntu
  0.3~20.04.1) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-hJ8TxR/47-linux-firmware_1.187.17_all.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.16
  ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2654 F pulseaudio
curts  3716 F pulseaudio
   /dev/snd/controlC0:  gdm2654 F pulseaudio
curts  3716 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Oct  1 19:32:59 2021
  Dependencies:
   
  ErrorMessage: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2021-02-21 (222 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IwConfig:
   lono wireless extensions.
   
   enp42s0   no wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: Micro-Star International Co., Ltd. MS-7C91
  PackageArchitecture: all
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz 
root=UUID=7A200ADA-3790-4EBA-8897-FF422F2FB377 quiet splash rootflags=subvol=@
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  RfKill:
   
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to 
open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.50
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG B550 GAMING EDGE WIFI (MS-7C91)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.50:bd01/14/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550GAMINGEDGEWIFI(MS-7C91):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C91
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

[Kernel-packages] [Bug 1946304] Re: amdgpu: Add initial firmware for navi24 Beige Goby

[Timo Aaltonen]

devel series shouldn't be marked wontfix, new fw is always needed in
there.. luckily it has it already

** Changed in: linux-firmware (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  amdgpu: Add initial firmware for navi24 Beige Goby

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  In Progress

Bug description:
  - This GPU is needed for AMD R21M-P50-50
  - amdgpu upstream driver already landed kernel v5.14.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c?h=v5.14#n1216
 [git.kernel.org]
  /* BEIGE_GOBY */
  {0x1002, 0x7420, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7421, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7422, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x7423, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},
  {0x1002, 0x743F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_BEIGE_GOBY},

  - linux-firmware is being under reviewed in
  https://lore.kernel.org/linux-
  
firmware/cadnq5_nnubczwd66tcutevyajrw5x2q2+kurtqws4ahzopw...@mail.gmail.com/T/#u

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


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

[Kernel-packages] [Bug 1945932] Re: Fix A yellow screen pops up in an instant (< 1 second) and then disappears before loading the system

[Timo Aaltonen]

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

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

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

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

Title:
  Fix A yellow screen pops up in an instant (< 1 second) and then
  disappears before loading the system

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-oem-5.14 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:
  In Progress
Status in linux-oem-5.14 source package in Focal:
  New
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-oem-5.14 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
Status in linux-oem-5.14 source package in Impish:
  Invalid

Bug description:
  [Impact]
  *** this issue happen with secure boot on and issue gone when secure boot is 
off***

  After the BIOS loading screen, a yellow screen pops up in an instant
  (< 1 second) and then disappears. Attached a demo video.

  [Fix]
  do what intel_color_commit() does to make sure the bottom color state
  matches whatever out hardware readout produced.
  Ref. https://patchwork.freedesktop.org/patch/456170/?series=95171=1

  [Test]
  1. Power on the system
  2. Check if any unusual screen shows before and after the system loading 
screen.
  3. No unusual screen shows before and after the system loading screen

  [Regression Potential]
  Medium, maintainer still not totally sure what should do about color 
management
  features here in general.

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


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

[Kernel-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels

[Christian Ehrhardt ]

Not sure if it will pass build, review or be acceptable as SRU since it is so 
low impact.
But the fix was so trivial that after all this time I'd feel bad to keep it 
as-is.

So I've prepared an MP to fix it
https://code.launchpad.net/~paelzer/ubuntu/+source/iproute2/+git/iproute2/+merge/409821

And a PPA with a test build
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4676/+packages


** Tags added: server-todo

** Changed in: iproute2 (Ubuntu Bionic)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

** Description changed:

+ [Impact]
+ 
+  * The filter on label names does not match the intention
+by upstream nor the description in the man page
+ 
+  * Fix by backporting upstream fix that strengthens the check
+ 
+ [Test Plan]
+ 
+ Bad case:
+ root@b:~# ip addr add 1.1.1.1 label test1 dev eth0
+ "dev" (eth0) must match "label" (test1).
+ root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0
+ root@b:~# ip addr show dev eth0 | grep test
+ inet 1.1.1.1/32 scope global eth0-test
+ 
+ With the fix it should look like:
+ root@i:~# ip addr add 1.1.1.1 label test1 dev eth0
+ "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon.
+ root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0
+ "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a 
colon.
+ root@i:~# ip addr show dev eth0 | grep test
+ 
+ [Where problems could occur]
+ 
+  * While the fix indeed "corrects" behavior I must say that if someone 
+relied on the non-intended behavior it would now break e.g. his 
+scripting or automation.
+ 
+ [Other Info]
+  
+  * It was too easy to fix and too long dormant to ignore it further,
+but if the SRU team says this is too much regression risk relative to 
+the gain we will mark it Won't Fix based on that decision.
+ 
+ 
+ ---
+ 
  ip-address(8) manpage states:
  
-   label NAME
- Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.
+   label NAME
+ Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.
  
  But you can omit the colon, "ip addr add" is ONLY checking the label is
  prefixed with the device:
  
  # ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).
  
  # ip addr add 1.1.1.2 label eth0-test2 dev eth0
  
  # ip addr add 1.1.1.3 label eth0:test3 dev eth0
- 
  
  Now ifconfig becomes confused about eth0-test2:
  
  # ifconfig eth0-test2
  eth0-test2: error fetching interface information: Device not found
  
  # ifconfig eth0:test3
- eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c  
-   inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
-   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
-   Interrupt:171 
+ eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c
+   inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
+   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
+   Interrupt:171
  
  And daemons like ntpd also log errors about the interface with the
  illegal label:
  
  ntpd[7570]: eth0-test3: getting interface flags: No such device
-   ## => many of this error per minute until:
+   ## => many of this error per minute until:
  ntpd[7570]: Too many errors.  Shutting up.
  
- 
- So, I think ip addr show disallow adding address with illegal (as stated by 
his own documentation) labels, it must also check for the colon following the 
dev name.
+ So, I think ip addr show disallow adding address with illegal (as stated
+ by his own documentation) labels, it must also check for the colon
+ following the dev name.
  
  Version: 4.3.0-1ubuntu3

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

Title:
  "ip addr add" permits illegal labels

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * The filter on label names does not match the intention
 by upstream nor the description in the man page

   * Fix by backporting upstream fix that strengthens the check

  [Test Plan]

  Bad case:
  root@b:~# ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).
  root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0
  root@b:~# ip addr show dev eth0 | grep test
  inet 1.1.1.1/32 scope global eth0-test

  With the fix it should look like:
  root@i:~# ip addr add 1.1.1.1 label test1 dev eth0
  "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon.
  root@i:~# ip addr 

[Kernel-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels

[Christian Ehrhardt ]

SRU template added

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

Title:
  "ip addr add" permits illegal labels

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * The filter on label names does not match the intention
 by upstream nor the description in the man page

   * Fix by backporting upstream fix that strengthens the check

  [Test Plan]

  Bad case:
  root@b:~# ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).
  root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0
  root@b:~# ip addr show dev eth0 | grep test
  inet 1.1.1.1/32 scope global eth0-test

  With the fix it should look like:
  root@i:~# ip addr add 1.1.1.1 label test1 dev eth0
  "label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon.
  root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0
  "label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a 
colon.
  root@i:~# ip addr show dev eth0 | grep test

  [Where problems could occur]

   * While the fix indeed "corrects" behavior I must say that if someone 
 relied on the non-intended behavior it would now break e.g. his 
 scripting or automation.

  [Other Info]
   
   * It was too easy to fix and too long dormant to ignore it further,
 but if the SRU team says this is too much regression risk relative to 
 the gain we will mark it Won't Fix based on that decision.

  
  ---

  ip-address(8) manpage states:

    label NAME
  Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.

  But you can omit the colon, "ip addr add" is ONLY checking the label
  is prefixed with the device:

  # ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).

  # ip addr add 1.1.1.2 label eth0-test2 dev eth0

  # ip addr add 1.1.1.3 label eth0:test3 dev eth0

  Now ifconfig becomes confused about eth0-test2:

  # ifconfig eth0-test2
  eth0-test2: error fetching interface information: Device not found

  # ifconfig eth0:test3
  eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c
    inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
    UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    Interrupt:171

  And daemons like ntpd also log errors about the interface with the
  illegal label:

  ntpd[7570]: eth0-test3: getting interface flags: No such device
    ## => many of this error per minute until:
  ntpd[7570]: Too many errors.  Shutting up.

  So, I think ip addr show disallow adding address with illegal (as
  stated by his own documentation) labels, it must also check for the
  colon following the dev name.

  Version: 4.3.0-1ubuntu3

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


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

[Kernel-packages] [Bug 1946353] [NEW] package linux-image-generic-hwe-20.04 5.11.0.37.41~20.04.16 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befor

[Matt Phillips]

Public bug reported:

Trying to install a package using Ubuntu Software catalogue, and the
installation was interrupted by a message saying that "E: dpkg was
interrupted, you must manually run 'dpkg --configure -a' to correct the
problem." I tried to run this command in Terminal, but it wouldn't work,
so I searched online for a solution and found that some people had a
similar message appear (the same as above but with 'sudo' appearing
before 'dpkg' at the start of the command line - see
https://askubuntu.com/questions/163200/e-dpkg-was-interrupted-run-sudo-
dpkg-configure-a).  I tried this, and some error messages came up.

Full details shown on Terminal after trying command 'sudo dpkg --configure -a':
dpkg: dependency problems prevent configuration of linux-generic-hwe-20.04:
 linux-generic-hwe-20.04 depends on linux-headers-generic-hwe-20.04 (= 
5.11.0.37.41~20.04.16); however:
  Version of linux-headers-generic-hwe-20.04 on system is 5.11.0.36.40~20.04.15.

dpkg: error processing package linux-generic-hwe-20.04 (--configure):
 dependency problems - leaving unconfigured
Setting up linux-image-5.11.0-37-generic (5.11.0-37.41~20.04.2) ...
I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.11.0-36-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.11.0-36-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.11.0-37-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.11.0-37-generic
Setting up linux-modules-extra-5.11.0-37-generic (5.11.0-37.41~20.04.2) ...
dpkg: error processing package linux-image-generic-hwe-20.04 (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
Setting up linux-modules-5.11.0-37-generic (5.11.0-37.41~20.04.2) ...
Processing triggers for linux-image-5.11.0-37-generic (5.11.0-37.41~20.04.2) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.11.0-37-generic
Error! Your kernel headers for kernel 5.11.0-37-generic cannot be found.
Please install the linux-headers-5.11.0-37-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.11.0-37-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.11.0-37-generic
Found initrd image: /boot/initrd.img-5.11.0-37-generic
Found linux image: /boot/vmlinuz-5.11.0-36-generic
Found initrd image: /boot/initrd.img-5.11.0-36-generic
Found linux image: /boot/vmlinuz-5.11.0-34-generic
Found initrd image: /boot/initrd.img-5.11.0-34-generic
Adding boot menu entry for UEFI Firmware Settings
done
Errors were encountered while processing:
 linux-generic-hwe-20.04
 linux-image-generic-hwe-20.04

Due to the error messages that are shown above, I followed some other
instructions given on the forum page (linked above), i.e. I used the
command 'sudo apt-get install -f'.  This came up with the following:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libfprint-2-tod1 libllvm10 linux-headers-5.11.0-34-generic
  linux-hwe-5.11-headers-5.11.0-34 linux-image-5.11.0-34-generic
  linux-modules-5.11.0-34-generic linux-modules-extra-5.11.0-34-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  linux-headers-5.11.0-37-generic linux-headers-generic-hwe-20.04
  linux-hwe-5.11-headers-5.11.0-37
The following NEW packages will be installed
  linux-headers-5.11.0-37-generic linux-hwe-5.11-headers-5.11.0-37
The following packages will be upgraded:
  linux-headers-generic-hwe-20.04
1 to upgrade, 2 to newly install, 0 to remove and 81 not to upgrade.
2 not fully installed or removed.
Need to get 0 B/13.2 MB of archives.
After this operation, 90.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package linux-hwe-5.11-headers-5.11.0-37.
(Reading database ... 209271 files and directories currently installed.)
Preparing to unpack 
.../linux-hwe-5.11-headers-5.11.0-37_5.11.0-37.41~20.04.2_all.deb ...
Unpacking linux-hwe-5.11-headers-5.11.0-37 (5.11.0-37.41~20.04.2) ...
Selecting previously unselected package linux-headers-5.11.0-37-generic.
Preparing to unpack 
.../linux-headers-5.11.0-37-generic_5.11.0-37.41~20.04.2_amd64.deb ...
Unpacking linux-headers-5.11.0-37-generic (5.11.0-37.41~20.04.2) ...
Preparing to unpack 
.../linux-headers-generic-hwe-20.04_5.11.0.37.41~20.04.16_amd64.deb ...
Unpacking linux-headers-generic-hwe-20.04 (5.11.0.37.41~20.04.16) over 
(5.11.0.36.40~20.04.15) ...
Setting up linux-hwe-5.11-headers-5.11.0-37 (5.11.0-37.41~20.04.2) ...
Setting up linux-headers-5.11.0-37-generic 

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

[Timo Aaltonen]

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

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

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

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

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

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

Title:
  Fix incorrect keyboard backlight behaviours

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
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:
  New

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

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

  [Test]
   This is requested by AMD.

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

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


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

[Kernel-packages] [Bug 1941010] Re: add AMD DID for s2idle

[Timo Aaltonen]

please file against the right kernel so these won't get lost

** Package changed: linux (Ubuntu) => linux-oem-5.13 (Ubuntu)

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

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

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

Title:
  add AMD DID for s2idle

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

Bug description:
  [Impact]
   An DID AMDI007 is added to support s2idle.

  [Fix]
  Below commit adds the ID.
  
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=f0c6225531e4a9e43e51c5f7b02089bdd725c734

  [Test]
   We didn't receive h/w yet, and this is requested by AMD.

  [Where problems could occur]
   The changes are specific to the new ID and will not impact original
   behaviors.

  Mario Limonciello (1):
ACPI: PM: Add support for upcoming AMD uPEP HID AMDI007

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


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

[Kernel-packages] [Bug 1946128] Re: ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid signature"

[Po-Hsu Lin]

bah, it just passed with another retry.
I will give them another shot on our jenkins.

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

Title:
  ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart
  / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid
  signature"

Status in ubuntu-kernel-tests:
  New
Status in linux-aws-5.11 package in Ubuntu:
  New

Bug description:
  linux-aws-5.11 5.11.0-1020.21~20.04.2

  ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge,
  i3en.24xlarge, t2.small

  All failures are identical:

  CmdError: Command  
failed, rc=1, Command returned non-zero exit status
  CmdError: Command  failed, 
rc=1, Command returned non-zero exit status
  CmdError: Command  
failed, rc=1, Command returned non-zero exit status
  CmdError: Command  failed, 
rc=2, Command returned non-zero exit status

  I do not see the same failures when run manually.

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


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

[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute

[Po-Hsu Lin]

Hi Krzysztof,
Thanks for reporting this.
I have these failing instances (Standard_B1ms, Standard_D48_v3) in your comment 
#21 retested with updated code. The Standard_B1ms will pass without any error. 
But Standard_D48_v3 will fail with bug 1946201 instead.

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

Title:
  memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
Status in linux source package in Impish:
  Confirmed

Bug description:
  This failure could be found in the LTP test suite on a Moonshot ARM64
  node with B-4.15, but sometimes it will pass if you try to run it
  manually. (Sometimes not.)

  <<>>
  tag=memcg_test_3 stime=1563249678
  cmdline="memcg_test_3"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s
  Test timeouted, sending SIGKILL!
  tst_test.c:1140: INFO: If you are running on slow machine, try exporting 
LTP_TIMEOUT_MUL > 1
  tst_test.c:1141: BROK: Test killed! (timeout?)

  Summary:
  passed   0
  failed   0
  skipped  0
  warnings 0
  tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: 
unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: 
EPERM
  <<>>

  
  When it fails, the attempt to remove files will fail, and most of the 
cgroup_fj_* test will fail:
* cgroup_fj_function_memory
* cgroup_fj_stress_memory_10_3_each
* cgroup_fj_stress_memory_10_3_none
* cgroup_fj_stress_memory_10_3_one
* cgroup_fj_stress_memory_1_200_each
* cgroup_fj_stress_memory_1_200_none
* cgroup_fj_stress_memory_1_200_one
* cgroup_fj_stress_memory_200_1_each
* cgroup_fj_stress_memory_200_1_none
* cgroup_fj_stress_memory_200_1_one
* cgroup_fj_stress_memory_2_2_each
* cgroup_fj_stress_memory_2_2_none
* cgroup_fj_stress_memory_2_2_one
* cgroup_fj_stress_memory_2_9_each
* cgroup_fj_stress_memory_2_9_none
* cgroup_fj_stress_memory_2_9_one
* cgroup_fj_stress_memory_3_3_each
* cgroup_fj_stress_memory_3_3_none
* cgroup_fj_stress_memory_3_3_one
* cgroup_fj_stress_memory_4_4_each
* cgroup_fj_stress_memory_4_4_none
* cgroup_fj_stress_memory_4_4_one

  Steps to run this:
git clone --depth=1 https://github.com/linux-test-project/ltp.git
cd ltp; make autotools; ./configure; make; sudo make install
echo "memcg_test_3memcg_test_3" > /tmp/jobs
sudo /opt/ltp/runltp -f /tmp/jobs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 03:46 seq
   crw-rw 1 root audio 116, 33 Jul 16 03:46 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 16 04:16:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1946128] Re: ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid signature"

[Po-Hsu Lin]

With a manual test this seems to be using the correct key server:
hkp://keyserver.ubuntu.com:80

But I can't figure out why this is just failing on these 4 instances;
a1.medium, c6g.8xlarge, i3en.24xlarge, t2.small but pass with others in
the AWS cloud for the moment. Might need to ask our lxc expert for this.

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

Title:
  ubuntu_lxc: api_test.py / lxc-test-apparmor-mount / lxc-test-autostart
  / lxc-test-no-new-privs / lxc-test-unpriv failing with "ERROR: Invalid
  signature"

Status in ubuntu-kernel-tests:
  New
Status in linux-aws-5.11 package in Ubuntu:
  New

Bug description:
  linux-aws-5.11 5.11.0-1020.21~20.04.2

  ubuntu_lxc test fails on 4 instances; a1.medium, c6g.8xlarge,
  i3en.24xlarge, t2.small

  All failures are identical:

  CmdError: Command  
failed, rc=1, Command returned non-zero exit status
  CmdError: Command  failed, 
rc=1, Command returned non-zero exit status
  CmdError: Command  
failed, rc=1, Command returned non-zero exit status
  CmdError: Command  failed, 
rc=2, Command returned non-zero exit status

  I do not see the same failures when run manually.

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


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

[Kernel-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/iproute2/+git/iproute2/+merge/409821

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

Title:
  "ip addr add" permits illegal labels

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ip-address(8) manpage states:

label NAME
  Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.

  But you can omit the colon, "ip addr add" is ONLY checking the label
  is prefixed with the device:

  # ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).

  # ip addr add 1.1.1.2 label eth0-test2 dev eth0

  # ip addr add 1.1.1.3 label eth0:test3 dev eth0
  

  Now ifconfig becomes confused about eth0-test2:

  # ifconfig eth0-test2
  eth0-test2: error fetching interface information: Device not found

  # ifconfig eth0:test3
  eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c  
inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
Interrupt:171 

  And daemons like ntpd also log errors about the interface with the
  illegal label:

  ntpd[7570]: eth0-test3: getting interface flags: No such device
## => many of this error per minute until:
  ntpd[7570]: Too many errors.  Shutting up.

  
  So, I think ip addr show disallow adding address with illegal (as stated by 
his own documentation) labels, it must also check for the colon following the 
dev name.

  Version: 4.3.0-1ubuntu3

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Pietro]

@Andrea 
Just this morning I installed Mainline (https://github.com/bkw777/mainline) to 
install the latest available kernel, the problem is that with SecureBoot I 
can't boot because the kernel is not signed. 
How can I do?

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1662620] Re: "ip addr add" permits illegal labels

[Christian Ehrhardt ]

Hi,
I come by trying to clear out a few old bugs that might still need to be 
resolved (or can be closed by now).

Even though this one seems to be forgotten by everyone so far it has
been fixed.

Bionic (affected)
root@b:~# ip addr add 1.1.1.1 label test1 dev eth0
"dev" (eth0) must match "label" (test1).
root@b:~# ip addr add 1.1.1.1 label eth0-test dev eth0
root@b:~# ip addr show dev eth0 | grep test
inet 1.1.1.1/32 scope global eth0-test


Impish (fixed)
root@i:~# ip addr add 1.1.1.1 label test1 dev eth0
"label" (test1) must match "dev" (eth0) or be prefixed by "dev" with a colon.
root@i:~# ip addr add 1.1.1.1 label eth0-test dev eth0
"label" (eth0-test) must match "dev" (eth0) or be prefixed by "dev" with a 
colon.
root@i:~# ip addr show dev eth0 | grep test

This was effectively fixed by
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=cad73425d8813

Which is in since v4.18.0

That version is in >=20.04 as well as in 18.04-backports.

 iproute2 | 3.12.0-2  | trusty   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 iproute2 | 3.12.0-2ubuntu1.2 | trusty-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 iproute2 | 4.3.0-1ubuntu3| xenial   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 iproute2 | 4.3.0-1ubuntu3.16.04.5| xenial-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 iproute2 | 4.15.0-2ubuntu1   | bionic   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 iproute2 | 4.15.0-2ubuntu1.1 | bionic-security  | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 iproute2 | 4.15.0-2ubuntu1.3 | bionic-updates   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 iproute2 | 4.18.0-1ubuntu2~ubuntu18.04.1 | bionic-backports | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 iproute2 | 5.5.0-1ubuntu1| focal| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 iproute2 | 5.10.0-4ubuntu1   | hirsute  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 iproute2 | 5.10.0-4ubuntu1   | impish   | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x


Thereby the active release that still is affected is Bionic (unless you use 
bionic-backports which already have 4.18).

I think to fix this in bionic is only prio-low since it is mostly a cosmetic.
Since it is fixed in newer releases there isn't more work to be done to drive 
this to conclusion for future releases.

@Nahuel - I can only beg your pardon that this was dormant for so long
:-/

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

** Changed in: iproute2 (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: iproute2 (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: iproute2 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  "ip addr add" permits illegal labels

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ip-address(8) manpage states:

label NAME
  Each address may be tagged with a label string.  In order to preserve 
compatibility with Linux-2.0 net aliases, this string must coincide with the 
name of the device or must be prefixed with the device name followed by colon.

  But you can omit the colon, "ip addr add" is ONLY checking the label
  is prefixed with the device:

  # ip addr add 1.1.1.1 label test1 dev eth0
  "dev" (eth0) must match "label" (test1).

  # ip addr add 1.1.1.2 label eth0-test2 dev eth0

  # ip addr add 1.1.1.3 label eth0:test3 dev eth0
  

  Now ifconfig becomes confused about eth0-test2:

  # ifconfig eth0-test2
  eth0-test2: error fetching interface information: Device not found

  # ifconfig eth0:test3
  eth0:test3 Link encap:Ethernet  HWaddr b0:d5:cc:fe:1d:7c  
inet addr:1.1.1.3  Bcast:0.0.0.0  Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
Interrupt:171 

  And daemons like ntpd also log errors about the interface with the
  illegal label:

  ntpd[7570]: eth0-test3: getting interface flags: No such device
## => many of this error per minute until:
  ntpd[7570]: Too many errors.  Shutting up.

  
  So, I think ip addr show disallow adding address with illegal (as stated by 
his own documentation) labels, it must also check for the colon following the 
dev name.

  Version: 4.3.0-1ubuntu3

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Andrea Righi]

ok, another interesting test to do would be to see what happens with a
mainline kernel (just to see if the problem is a mainline issue or if
it's limited to the Ubuntu kernel).

Can you try to do a test with this kernel?

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.19/

^ This is basically the latest 5.13 mainline kernel with the Ubuntu
config, but no special Ubuntu patches applied.

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Pietro]

@Andrea
I just tried, the difference is I don't get an error message like before, but 
the PC gets stuck with the Lenovo logo with no sign of loading, I couldn't see 
any output.
I went back to kernel 5.11, I remain available for other tests

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Andrea Righi]

@Pietro, thanks for reporting this.

Can you do a test with the kernel that is currently in impish-proposed
(5.13.0-18.18)? See https://wiki.ubuntu.com/Testing/EnableProposed on
how to enable proposed (for this you need to upgrade from 21.04, then
enable proposed, install 5.13.0-18.18, then reboot). 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/1945590

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

[Kleber Sacilotto de Souza]

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

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

Title:
  Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled

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

Bug description:
  I installed the Ubuntu 21.10 beta and as soon as I boot I get the
  kernel panic that I am attaching.

  I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
  5.13 kernel I get the same problem, disabling the trackpad and
  trackpoint in the bios the problem disappears.

  Everything works with the 5.11 kernel.
  I remain available for further details and sorry for my lack of experience.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-16-generic 5.13.0-16.16
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pietro 1810 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 30 10:26:10 2021
  InstallationDate: Installed on 2021-09-29 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20TA0033IX
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-16-generic N/A
   linux-backports-modules-5.13.0-16-generic  N/A
   linux-firmware 1.201
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
  dmi.bios.date: 09/02/2021
  dmi.bios.release: 1.43
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1EET43W(1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TA0033IX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E14 Gen 2
  dmi.product.name: 20TA0033IX
  dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
  dmi.product.version: ThinkPad E14 Gen 2
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1941044] Re: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 due to the presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pn

[You-Sheng Yang]

IWL_22000_UCODE_API_MAX:
* oem-5.14: 64
* oem-5.13: will be 64 in 1933938
* hwe-5.11: 59
* oem-5.10: 59

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

Title:
  ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with
  upgrade to linux-firmware 1.187.16 due to the presence of
  '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm'

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Focal:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS

  $ uname -r
  5.11.0-27-generic

  $ apt-cache policy linux-firmware
  linux-firmware:
Installed: 1.187.16

  $ ip a
  1: lo
  2: enp0s31f6

  Device:
  Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725]

  WiFi adapter disappears from network manager and
  > ip a
  following update to 
  > linux-firmware 1.187.16
  and a restart

  Able to confirm this package is the problem as the issue can be reversed by 
downgrading to
  > linux-firmware 1.187.15

  Our organisation has had at least one other identical device experience the 
same issue before
  > apt-mark hold linux-firmware
  was pushed out.

  Happy to supply any other information or logs on request.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.16
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  logansymons   7485 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 25 18:10:49 2021
  Dependencies:
   
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20W0005AAU
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic 
root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7
  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
  RfKill:
   0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET41W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0005AAU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0005AAU
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1941044] Re: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 due to the presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pn

[You-Sheng Yang]

Affected fw from bug 1933415:

* AX201
iwlwifi-Qu-b0-hr-b0-59.ucode
iwlwifi-Qu-b0-hr-b0-63.ucode

* 9560
iwlwifi-Qu-b0-jf-b0-59.ucode
iwlwifi-Qu-b0-jf-b0-63.ucode

* AX201
iwlwifi-Qu-c0-hr-b0-59.ucode
iwlwifi-Qu-c0-hr-b0-63.ucode

* 9560
iwlwifi-Qu-c0-jf-b0-59.ucode
iwlwifi-Qu-c0-jf-b0-63.ucode

* AX201
iwlwifi-QuZ-a0-hr-b0-59.ucode
iwlwifi-QuZ-a0-hr-b0-63.ucode

* 9560
iwlwifi-QuZ-a0-jf-b0-59.ucode
iwlwifi-QuZ-a0-jf-b0-63.ucode

* AX200
iwlwifi-cc-a0-59.ucode
iwlwifi-cc-a0-63.ucode

* AX210:
iwlwifi-ty-a0-gf-a0-59.ucode
iwlwifi-ty-a0-gf-a0-63.ucode

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

Title:
  ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with
  upgrade to linux-firmware 1.187.16 due to the presence of
  '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm'

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Focal:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS

  $ uname -r
  5.11.0-27-generic

  $ apt-cache policy linux-firmware
  linux-firmware:
Installed: 1.187.16

  $ ip a
  1: lo
  2: enp0s31f6

  Device:
  Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725]

  WiFi adapter disappears from network manager and
  > ip a
  following update to 
  > linux-firmware 1.187.16
  and a restart

  Able to confirm this package is the problem as the issue can be reversed by 
downgrading to
  > linux-firmware 1.187.15

  Our organisation has had at least one other identical device experience the 
same issue before
  > apt-mark hold linux-firmware
  was pushed out.

  Happy to supply any other information or logs on request.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.16
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  logansymons   7485 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 25 18:10:49 2021
  Dependencies:
   
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20W0005AAU
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic 
root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7
  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
  RfKill:
   0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET41W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0005AAU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0005AAU
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO

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


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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [i915] In Display Setting it is showing UnKnown Device and maximum
  resolution setting is set to 1024x768 and when i am requesting to
  update a driver it is saying Drivers are already updated

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Display Setting it is showing UnKnown Device and maximum resolution
  setting is set to 1024x768 and when i am requesting to update a driver
  it is saying Drivers are already updated

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  7 13:55:32 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:339a]
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=46918b1f-e034-4313-8da7-d5df94db823e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2013
  dmi.bios.release: 2.90
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: MXL330027R
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL330027R
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:skuD8C62UT#ABA:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.product.sku: D8C62UT#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Kernel-packages] [Bug 1946341] Re: In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers a

[Daniel van Vugt]

Thanks for the bug report. GNOME is using 1024x768 because that's the
maximum resolution reported by the kernel. The kernel would report that
if it is unable to detect your monitor properly.

If you can, please try a different monitor cable and use a digital
monitor connection.

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

** Summary changed:

- In Display Setting it is showing UnKnown Device and maximum resolution 
setting is set to 1024x768 and when i am requesting to update a driver it is 
saying Drivers are already updated
+ [i915] In Display Setting it is showing UnKnown Device and maximum resolution 
setting is set to 1024x768 and when i am requesting to update a driver it is 
saying Drivers are already updated

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

Title:
  [i915] In Display Setting it is showing UnKnown Device and maximum
  resolution setting is set to 1024x768 and when i am requesting to
  update a driver it is saying Drivers are already updated

Status in linux package in Ubuntu:
  New

Bug description:
  In Display Setting it is showing UnKnown Device and maximum resolution
  setting is set to 1024x768 and when i am requesting to update a driver
  it is saying Drivers are already updated

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  7 13:55:32 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:339a]
  InstallationDate: Installed on 2021-10-07 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=46918b1f-e034-4313-8da7-d5df94db823e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2013
  dmi.bios.release: 2.90
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: MXL330027R
  dmi.board.name: 339A
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL330027R
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:skuD8C62UT#ABA:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Pro 6300 MT
  dmi.product.sku: D8C62UT#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Kernel-packages] [Bug 1944080] Re: [fan-network] Race-condition between "apt update" and dhcp request causes cloud-init error

[Canonical Juju QA Bot]

** Changed in: juju
Milestone: 2.9.16 => 2.9.17

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

Title:
  [fan-network] Race-condition between "apt update" and dhcp request
  causes cloud-init error

Status in OpenStack rabbitmq-server charm:
  New
Status in juju:
  In Progress
Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  Hi,

  Using manual provider on top of VMWare.

  Juju: 2.9.14
  VM: Focal
  Containers: Bionic

  I've noticed that, in a given Focal host, 2x Bionic containers may
  have different behavior: one successfully completes cloud-init whereas
  the other fails. The failed container errors at "apt update" in cloud-
  init with:

  Err:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Something wicked happened resolving 'PROXY_IP:' (-9 - Address family 
for hostname not supported)
  (Likely this is the line where it breaks: 
https://github.com/Debian/apt/blob/766b24b7f7484751950c76bc66d3d6cdeaf949a5/methods/connect.cc#L436)

  Failed container, full cloud-init-output.log: 
https://pastebin.canonical.com/p/hKNw49mvJP/
  Successful container, full cloud-init-output.log: 
https://pastebin.canonical.com/p/P6MZdQPrWd/
  Host syslog: https://pastebin.canonical.com/p/jjMmWRFd9y/

  I can see that, on the host, dnsmasq served the FAN IP to the broken
  container after the "apt-update" was called.

  - FAILED CONTAINER -:
  Sep 19 13:02:14 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 
252.252.15.198 00:16:3e:da:dd:c4 
  apt-update on cloud-init was ran:
  Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at 
Sun, 19 Sep 2021 13:02:13 +. Up 3.90 seconds.

  
  - SUCCESSFUL CONTAINER -:
  Sep 19 13:09:40 lma-stack-2 dnsmasq-dhcp[1243]: DHCPOFFER(fan-252) 
252.252.15.253 00:16:3e:d7:6b:ef 
  apt-update on cloud-init was ran:
  Cloud-init v. 21.2-3-g899bfaa9-0ubuntu2~18.04.1 running 'modules:config' at 
Sun, 19 Sep 2021 13:10:10 +. Up 35.99 seconds.

  In the case of the Failed Container, the DHCPOFFER arrived 1s after
  the "apt update" was requested, whereas the Successful Container
  logged a DHCPOFFER 30s before the "apt update".

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1944080/+subscriptions


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

[Kernel-packages] [Bug 1946231] Re: esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)

[Florian Baumgartner]

some more information:
 - I was able to reproduce the problem on a different computer.
 - flashing an ESP32 Devel board which is based on the cp210x instead of the 
ch341 works.

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

Title:
  esp8266 flashing stopped working with kernel 5.11.0-37-generic (ch341)

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

Bug description:
  the esp8266 development boards like wemos D1 mini have an integrated
  usb-uart converter  which allows to flash/monitor/debug the esp8266 by
  usb cable and a tool called esptool on linux, which is either
  standalone (esptool package) or integrated into some IDE (platformio +
  visio)

  dmesg output:
  [   46.614510] usbcore: registered new interface driver usbserial_generic
  [   46.614523] usbserial: USB Serial support registered for generic
  [   46.615912] usbcore: registered new interface driver ch341
  [   46.615925] usbserial: USB Serial support registered for ch341-uart
  [   46.615938] ch341 1-9:1.0: ch341-uart converter detected
  [   46.616332] usb 1-9: ch341-uart converter now attached to ttyUSB0

  This convenient flashing method worked without issues up to kernel
  5.11.0-36-generic and stopped working with 5.11.0-37-generic. The
  issue remains the same whether I use the esptool package or the
  version bundled with platformio,

  >> esptool --chip esp8266 --port /dev/ttyUSB0 --baud 115200 write_flash 
0x firmware.bin
  esptool.py v2.8
  Serial port /dev/ttyUSB0
  
Connecting_._._._._._._

  A fatal error occurred: Failed to connect to ESP8266: Timed out
  waiting for packet header

  
  The communication to the esp8266 still seems to work, but the flash process 
includes some additional DTR/RTS magic in the beginning to switch the esp into 
flash mode before transmitting the data. My impression is that this DTR/RTS 
process might be broken. I can flash an esp with an external UART (some dongle) 
and manually triggering the flash mode. I tried with several cables, esps, ... 

  Booting the older kernel (5.11.0-36-generic) solves the issue ...
  There seems to be an update to the ch341 from kernel -36 to -37, but
  it is beyond my knowledge whether there is any connection.

  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  6 14:59:58 2021
  InstallationDate: Installed on 2020-08-29 (403 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken

[Colin Ian King]

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

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

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

Title:
  Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken

Status in zfs-linux package in Ubuntu:
  Confirmed
Status in zfs-linux source package in Focal:
  Fix Committed

Bug description:
  == SRU Justification Focal ==

  [Impact]

  https://github.com/openzfs/zfs/issues/12462

  Ubuntu 20.04.2 LTS
  Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu
  zfs-0.8.3-1ubuntu12.12
  zfs-kmod-2.0.2-1ubuntu5

  Trying to run zfs send | receive and getting an error:

  # zfs send  'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive 
 -s -F 'nas/rpool_backup/home'
  cannot receive: failed to read from stream
  cannot receive new filesystem stream: dataset does not exist

  This used to work before the recent Ubuntu kernel update from 5.8 to 5.11
  Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2

  Ubuntu updates that broke it:

  Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 
5.11.0.25.27~20.04.10), linux-
  image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), 
linux-generic-hwe-20.04
  :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10)

  Sending the zfs send part to a file works, but then sending the file
  to zfs receive also fails. The dump file size seems reasonable but the
  contents may not be correct.

  [Test Plan]

  1. create test pool and backup pool

  sudo zpool create pool /dev/vdb1
  sudo zpool create backup  /dev/vdc1

  2. populate pool with some files and create some snapshots

  sudo  zfs snapshot pool@now1

  create some more files etc, make another snapshot

  sudo  zfs snapshot pool@now2

  3. perform send/recv using -s option:

  sudo zfs send pool@now1 | sudo zfs receive -vFs backup
  sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup

  Without the fix, the -s option on the receive fails. With the fix it
  works fine.  Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and
  2.x kernel ZFS drivers.

  [Where problems could occur]

  The main fix nullifies the deprecated  action_handle option so that
  it's not checked, this allows 0.8.x userspace it to be forwardly
  compatible with 2.x kernel ZFS and also since it is deprecated in
  0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the
  risk with patch action_handle is very small.

  Included in the fix is a send/recv upstream bug fix 
4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes 
send/recv more resilient by making  zfs receive to always unmount and remount 
the
  destination, regardless of whether the stream is a new stream or a
  resumed stream.  The change is upstream for ~10 months and has minimal impact 
on current recv functionality.

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


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

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware 

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

[Alin]

apport information

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

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

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated 

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware 

[Kernel-packages] [Bug 1946341] [NEW] In Display Setting it is showing UnKnown Device and maximum resolution setting is set to 1024x768 and when i am requesting to update a driver it is saying Drivers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In Display Setting it is showing UnKnown Device and maximum resolution
setting is set to 1024x768 and when i am requesting to update a driver
it is saying Drivers are already updated

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-37.41-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct  7 13:55:32 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:339a]
InstallationDate: Installed on 2021-10-07 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Hewlett-Packard HP Compaq Pro 6300 MT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=46918b1f-e034-4313-8da7-d5df94db823e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.asset.tag: MXL330027R
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL330027R
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300MT:pvr:skuD8C62UT#ABA:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 MT
dmi.product.sku: D8C62UT#ABA
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu wayland-session
-- 
In Display Setting it is showing UnKnown Device and maximum resolution setting 
is set to 1024x768 and when i am requesting to update a driver it is saying 
Drivers are already updated
https://bugs.launchpad.net/bugs/1946341
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware 

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware 

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware 

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware 

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

[Alin]

apport information

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

Title:
  ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a
  normal state. There are no background activities that affect the
  booting process or after. The settings in BIOS are to default.

  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu
  the process is noticeable slow, even dragging a terminal window is
  slow. Linux Mint is faster, although starting a CPU benchmark will
  quickly show the slowness.

  Windows 10 does not have any issues.

  I suspect that it remains at 800 MHz.

  

  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700
  512GB SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.

  Kernel: 5.11.0-37-generic

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480

  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80

  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities


  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   

[Kernel-packages] [Bug 1946323] Re: ASUS D700TA with Intel i7-10700 sometimes remains at 800 MHz

[Alin]

apport information

** Tags added: apport-collected focal

** Description changed:

  Sometimes the system is very slow, in terms of how fast applications
  work. After I reboot, maybe a few times, the system returns to a normal
  state. There are no background activities that affect the booting
  process or after. The settings in BIOS are to default.
  
  Note that this is happening only in Ubuntu and Linux Mint. On Ubuntu the
  process is noticeable slow, even dragging a terminal window is slow.
  Linux Mint is faster, although starting a CPU benchmark will quickly
  show the slowness.
  
  Windows 10 does not have any issues.
  
  I suspect that it remains at 800 MHz.
  
  
  
  Configuration: Desktop ASUS D700TA Intel Core (10th Gen) i7-10700 512GB
  SSD 8GB ​using Ubuntu 20 or Linux Mint or Win 10.
  
  Kernel: 5.11.0-37-generic
  
  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
  480
  
  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 
  80
  
  Architecture:x86_64
  CPU op-mode(s):  32-bit, 64-bit
  Byte Order:  Little Endian
  Address sizes:   39 bits physical, 48 bits virtual
  CPU(s):  16
  On-line CPU(s) list: 0-15
  Thread(s) per core:  2
  Core(s) per socket:  8
  Socket(s):   1
  NUMA node(s):1
  Vendor ID:   GenuineIntel
  CPU family:  6
  Model:   165
  Model name:  Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
  Stepping:5
  CPU MHz: 2900.000
  CPU max MHz: 4800,
  CPU min MHz: 800,
  BogoMIPS:5799.77
  Virtualization:  VT-x
  L1d cache:   256 KiB
  L1i cache:   256 KiB
  L2 cache:2 MiB
  L3 cache:16 MiB
  NUMA node0 CPU(s):   0-15
  Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
  Vulnerability L1tf:  Not affected
  Vulnerability Mds:   Not affected
  Vulnerability Meltdown:  Not affected
  Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass 
disabled via prctl and seccomp
  Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and 
__user pointer sanitization
  Vulnerability Spectre v2:Mitigation; Enhanced IBRS, IBPB conditional, 
RSB filling
  Vulnerability Srbds: Not affected
  Vulnerability Tsx async abort:   Not affected
  Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep 
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 s
  ​s ht tm pbe syscall nx pdpe1gb rdtscp lm 
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nons
  ​top_tsc cpuid aperfmperf pni pclmulqdq 
dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm p
  ​cid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
   ​cpuid_fault epb invpcid_single ssbd ibrs 
ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept
  ​_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 
erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xs
  ​avec xgetbv1 xsaves dtherm ida arat pln pts 
hwp hwp_notify hwp_act_window hwp_epp pku ospke md_clear flush_l
  ​1d arch_capabilities
  
  
  
  cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
  Report errors and bugs to cpuf...@vger.kernel.org, please.
  analyzing CPU 0:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 0
   ​CPUs which need to have their frequency coordinated by software: 0
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 829 MHz.
  analyzing CPU 1:
   ​driver: intel_pstate
   ​CPUs which run at the same hardware frequency: 1
   ​CPUs which need to have their frequency coordinated by software: 1
   ​maximum transition latency: 4294.55 ms.
   ​hardware limits: 800 MHz - 4.80 GHz
   ​available cpufreq governors: performance, powersave
   ​current policy: frequency should be within 800 MHz and 4.80 GHz.
   ​The governor "powersave" may decide which speed to use
   ​within this range.
   ​current CPU frequency is 800 MHz.
  
  ...
  
  analyzing CPU 

[Kernel-packages] [Bug 1889110] Re: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. "

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Dimitri John Ledkov (xnox)

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

Title:
  zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than
  120 seconds. "

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  ZFS filesystem becomes unresponsive and subsequent NFS shares
  unresponsive. ESXi sees all paths down.

  See this error 3 times in a row.

  
  [184383.479511] INFO: task txg_sync:4307 blocked for more than 120 seconds.   

  
  [184383.479565]   Tainted: P  IO  5.4.0-42-generic #46-Ubuntu 

  
  [184383.479607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.   

  [184383.479655] txg_syncD0  4307  2 0x80004000

  
  [184383.479658] Call Trace:   

  
  [184383.479670]  __schedule+0x2e3/0x740   

  
  [184383.479673]  schedule+0x42/0xb0   

  
  [184383.479676]  schedule_timeout+0x152/0x2f0 

  
  [184383.479683]  ? __next_timer_interrupt+0xe0/0xe0   

  
  [184383.479685]  io_schedule_timeout+0x1e/0x50

  
  [184383.479697]  __cv_timedwait_common+0x15e/0x1c0 [spl]  

  
  [184383.479702]  ? wait_woken+0x80/0x80   

  
  [184383.479710]  __cv_timedwait_io+0x19/0x20 [spl]

  
  [184383.479816]  zio_wait+0x11b/0x230 [zfs]   

  
  [184383.479905]  ? __raw_spin_unlock+0x9/0x10 [zfs]   

  
  [184383.479983]  dsl_pool_sync+0xbc/0x410 [zfs]   

  
  [184383.480069]  spa_sync_iterate_to_convergence+0xe0/0x1c0 [zfs] 

  
  [184383.480156]  spa_sync+0x312/0x5b0 [zfs]   

  
  [184383.480245]  txg_sync_thread+0x27a/0x310 [zfs]

  
  [184383.480334]  ? txg_dispatch_callbacks+0x100/0x100 [zfs]   

  
  [184383.480344]  thread_generic_wrapper+0x83/0xa0 [spl]   
   

[Kernel-packages] [Bug 1943918] Re: iwlwifi version 63.c04f3485.0 fails to load

[You-Sheng Yang]

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

** This bug has been marked a duplicate of bug 1941044
   ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade 
to linux-firmware 1.187.16 due to the presence of 
'/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm'

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

Title:
  iwlwifi version 63.c04f3485.0 fails to load

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

Bug description:
  I have Intel WiFi 6E AX210. Using the default 20.04 kernel 5.10 I get wifi to 
work after removing /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
  https://bugzilla.kernel.org/show_bug.cgi?id=212371
  This kernel is loading 59.601f3a66.0 version of iwlwifi driver.
  When using 5.13.0-1012-oem the kernel tries to load 63.c04f3485.0 which 
doesn't work

  [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: enabling device ( -> 
0002)
  [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: api flags index 2 larger 
than supported by driver
  [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 0.0.2.25
  [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: loaded firmware version 
63.c04f3485.0 ty-a0-gf-a0-63.ucode op_mode iwlmvm
  [fre sep 17 07:38:34 2021] iwlwifi :72:00.0: Detected Intel(R) Wi-Fi 6 
AX210 160MHz, REV=0x420
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: SecBoot CPU1 Status: 0x77a3, 
CPU2 Status: 0xb03
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: UMAC PC: 0x8047df60
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: LMAC PC: 0x0
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: WRT: Collecting data: ini 
trigger 13 fired (delay=0ms).
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: Loaded firmware version: 
63.c04f3485.0 ty-a0-gf-a0-63.ucode
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | 
ADVANCED_SYSASSERT  
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | trm_hw_status0
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | trm_hw_status1
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | branchlink2
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | interruptlink1
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | interruptlink2
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | data1
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | data2
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | data3
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | beacon time
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | tsf low
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | tsf hi
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | time gp1
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | time gp2
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | uCode revision 
type
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | uCode version 
major
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | uCode version 
minor
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | hw version
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | board version
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | hcmd
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr0
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr1
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr2
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr3
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | isr4
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | last cmd Id
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | wait_event
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_control
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_duration
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_mhvalid
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | l2p_addr_match
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | lmpm_pmg_sel
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | timestamp
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | flow_handler
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: Start IWL Error Log Dump:
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: Status: 0x, count: 7
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x201013F2 | 
ADVANCED_SYSASSERT
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x | umac branchlink1
  [fre sep 17 07:38:35 2021] iwlwifi :72:00.0: 0x8045CF40 | umac branchlink2
  [fre sep 17 07:38:35 2021] iwlwifi 

[Kernel-packages] [Bug 1888202] Re: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  the upgrade process assumes ZFS-utils is not configured and has exit
  code 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  AptOrdering:
   gir1.2-webkit2-4.0:amd64: Install
   gir1.2-javascriptcoregtk-4.0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul 20 10:22:00 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-05-15 (1526 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-24 (56 days ago)

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


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

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

[You-Sheng Yang]

This caused bug 1941044, bug 1943918, and bug 1946222 in Focal. Also bug
1922406 in Hirsute.

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

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

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

Bug description:
  [SRU Justification]

  [Impact]

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

  [Fix]

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

  [Test Case]

  1. disconnect/connect stress

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

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

  2. suspend/resume stress

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

  [Where problems could occur]

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

  [Other Info]

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

  == original bug description ==

  [Reproduce steps]

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

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

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

[55/1757]
  kernel: iwlwifi :03:00.0: 

[Kernel-packages] [Bug 1945180] Re: vrf: fix refcnt leak with vxlan slaves

[Kleber Sacilotto de Souza]

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

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

Title:
  vrf: fix refcnt leak with vxlan slaves

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

Bug description:
  [Impact]

  There are cases, where deleting a VRF device can hang waiting for the refcnt 
to drop to 0, with the message: 
unregister_netdevice: waiting for vrf1 to become free. Usage count = 1

  This is fixed upstream with commit b87b04f5019e ("ipv4: Fix device
  used for dst_alloc with local routes"), included in linux v5.13. The
  original patch, which has introduced the bug, is included in linux
  v4.10.

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

  [Test Case]

  The upstream patch includes a test case, which describe how to
  reproduce the bug.

  [Regression Potential]

  The patch affects ipv4 routing. It is straightforward, it links new
  dst to a vrf device instead of the loopback if needed.

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


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

[Kernel-packages] [Bug 1791143] Re: Suggestion to make zfsutils-linux a snap

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Dimitri John Ledkov (xnox)

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

Title:
  Suggestion to make zfsutils-linux a snap

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  This circumvents the need to keep it on the same major version
  throughout the LTS cycle. LXD is doing snaps, perhaps for zfs this is
  the best approach as well.

  Xenial still has zfsutils on generation 0.6, with the module on 0.7.
  Even when patches are applied as needed that approach has its
  limitations. E.g. the Bionic cycle might possibly see 2 major zfs
  releases, who'll say.

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


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

[Kernel-packages] [Bug 1920956] Re: ZFS module cannot be loaded after Kernel 5.4.0-67-generic release AND if the system has zfs-dkms and spl-dkms packages installed

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Dimitri John Ledkov (xnox)

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

Title:
  ZFS module cannot be loaded after Kernel 5.4.0-67-generic release AND
  if the system has zfs-dkms and spl-dkms packages installed

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  WARNING: The current bug will only occur under the following
  conditions:

  1- You have a system running on Bionic Release (18.04). Other systems seems 
to be unaffected for now;
  2- This system have 'spl-dkms' and 'zfs-dkms' packages installed. This 
triggers both SPL and ZFS to be recompiled from source if we have a new Kernel 
Image being installed;
  3- You didn't patched your system kernel to either 
"linux-modules-5.4.0-67-generic" or "linux-modules-5.4.0-1039-aws". You are 
running an earlier kernel version, which can be from 5.3.0-XXX or 5.4.0-60 for 
example and you need to upgrade your system to the latest 'kernel-image' 
release.

  ALTERNATIVELY:
  1- When creating a new OS image based on the Bionic and it's already running 
kernel 5.4.0-67 or 5.4.0-1030-aws, you decide to install 'spl-dkms' and 
'zfs-dkms'. 

  SCENARIO:
  We have systems running on Xenial, Bionic, and Focal Fossa releases. We also 
have the 'Unattended Upgrades' on and we use ZFS.

  Every time that Ubuntu releases kernel updates, they are updated on
  our systems and both the new kernel and its modules will be active on
  the next reboot. Or if you run your workload on AWS and uses Canonical
  images, this is happening also on the image tagged as
  'ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20210224' on
  AWS Ireland / eu-west-1 Region (AMI ID = ami-0d75330b9efa7072d) for
  fresh installs.

  Some days ago, Ubuntu releases a new Linux Kernel update for the 5.4.0
  release, and this is happening on both "linux-
  modules-5.4.0-67-generic" and "linux-modules-5.4.0-1039-aws" (this
  might be true on GKE, Azure and other public cloud providers kernel
  releases, but I didn't test them).

  I have noticed that both EC2 instances that were rebooted after the
  kernel upgrade or if we are baking a new OS image based on the latest
  Canonical images I was unable to get the ZFS module loaded. The error
  message is showed below:

  $ sudo modprobe zfs
  modprobe: ERROR: could not insert 'zfs': Invalid argument

  When checking the 'dmesg', we can see the errors below (or even when
  booting up if you have the 'zfs-load-module.service' active on your
  system).

  [   51.358828] icp: disagrees about version of symbol __kstat_create
  [   51.358830] icp: Unknown symbol __kstat_create (err -22)
  [   51.358925] icp: disagrees about version of symbol __kstat_install
  [   51.358927] icp: Unknown symbol __kstat_install (err -22)
  [   79.196638] icp: disagrees about version of symbol __kstat_delete
  [   79.196643] icp: Unknown symbol __kstat_delete (err -22)
  [   79.196687] icp: disagrees about version of symbol __kstat_create
  [   79.196689] icp: Unknown symbol __kstat_create (err -22)
  [   79.196765] icp: disagrees about version of symbol __kstat_install
  [   79.196766] icp: Unknown symbol __kstat_install (err -22)

  On Bionic release, both th ZFS and the SPL modules comes with version
  '0.7.5'.

  $ dpkg -l |grep 0.7.5-1ubuntu16.9
  ii  libnvpair1linux  0.7.5-1ubuntu16.9   
amd64Solaris name-value library for Linux
  ii  libuutil1linux   0.7.5-1ubuntu16.9   
amd64Solaris userland utility library for Linux
  ii  libzfs2linux 0.7.5-1ubuntu16.9   
amd64OpenZFS filesystem library for Linux
  ii  libzpool2linux   0.7.5-1ubuntu16.9   
amd64OpenZFS pool library for Linux
  ii  zfs-dkms 0.7.5-1ubuntu16.9   all  
OpenZFS filesystem kernel modules for Linux
  ii  zfs-initramfs0.7.5-1ubuntu16.9   all  
OpenZFS root filesystem capabilities for Linux - initramfs
  ii  zfs-zed  0.7.5-1ubuntu16.9   
amd64OpenZFS Event Daemon
  ii  zfsutils-linux   0.7.5-1ubuntu16.9   
amd64command-line tools to manage OpenZFS filesystems

  On systems running kernel 5.4.0 already have the modules compiled on
  version 0.8.1, which can vary depending on the active kernel.

  (test) wbraga@bastion-host-i-07c42966be34bd44e:~$ modinfo zfs |head -2
  filename:   /lib/modules/5.3.0-1030-aws/kernel/zfs/zfs.ko
  version:0.8.1-1ubuntu14.4
  (test) wbraga@bastion-host-i-07c42966be34bd44e:~$ modinfo spl |head -2
  filename:   /lib/modules/5.3.0-1030-aws/kernel/zfs/spl.ko
  version:0.8.1-1ubuntu14.4
  (test) 

[Kernel-packages] [Bug 1907854] Re: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Dimitri John Ledkov (xnox)

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

Title:
  package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  After update zfsutils-linux, the update process tries to mount zfs
  file in /mnt but since in /mnt there are another disk mount fails
  with:

  Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ...
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  zfs-import-scan.service is a disabled or a static unit, not starting it.
  Job for zfs-mount.service failed because the control process exited with 
error code.
  See "systemctl status zfs-mount.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript zfs-mount, action "start" failed.

  ● zfs-mount.service - Mount ZFS filesystems
   Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 
8ms ago
 Docs: man:zfs(8)
  Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, 
status=1/FAILURE)
 Main PID: 177294 (code=exited, status=1/FAILURE)

  dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems...
  dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, 
code=exited, status=1/FAILURE
  dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 
'exit-code'.
  dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: zfsutils-linux 0.8.3-1ubuntu12.5
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.13
  AptOrdering:
   python3-aptdaemon.gtk3widgets:amd64: Install
   aptdaemon:amd64: Install
   python3-aptdaemon:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Dec 11 20:56:40 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-03-24 (261 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-19 (206 days ago)

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


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

[Kernel-packages] [Bug 1881748] Re: Slow ZFS Diff with very large datasets

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
 Assignee: Colin Ian King (colin-king) => Dimitri John Ledkov (xnox)

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

Title:
  Slow ZFS Diff with very large datasets

Status in zfs-linux package in Ubuntu:
  Incomplete

Bug description:
  When running zfs diff it can take a couple hours in an environment
  with lots of files/directories.

  Is it possible to pull in this patch:
  https://github.com/openzfs/zfs/pull/10391

  To address that issue?

  Using ubuntu 20.04 at the moment.

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


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

[Kernel-packages] [Bug 1901336] Re: package zfsutils-linux 0.8.1-1ubuntu14.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status

[Colin Ian King]

This bug report required some extra information that has not been
supplied for nearly a year. I am marking this as Won't Fix. If this is
still and issue please reopen the issue.

** Changed in: zfs-linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  package zfsutils-linux 0.8.1-1ubuntu14.4 failed to install/upgrade:
  installed zfsutils-linux package post-installation script subprocess
  returned error exit status 1

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm updating to 20.04.1 and received this error. I was seeing this
  error when trying to update using apt-get prior to this on 19.10. One
  of the suggested problems was around lxd usage. I'm not using lxd but
  I am using docker, so I don't know if there is something with that or
  not.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfsutils-linux 0.8.1-1ubuntu14.4
  ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18
  Uname: Linux 5.3.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  Date: Sat Oct 24 17:40:51 2020
  ErrorMessage: installed zfsutils-linux package post-installation script 
subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4ubuntu0.1
  SourcePackage: zfs-linux
  Title: package zfsutils-linux 0.8.1-1ubuntu14.4 failed to install/upgrade: 
installed zfsutils-linux package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2020-10-24 (0 days ago)

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


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

[Kernel-packages] [Bug 1932329] Re: Benchmark if we can compress kernel modules

[Colin Ian King]

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

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

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

Title:
  Benchmark if we can compress kernel modules

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Symbol: MODULE_COMPRESS_ZSTD [=n]
  Type  : bool

  = Impacts to measure and observe =

  == Disk space ==

  * Inspect linux-modules-* and linux-modules-extra* deb package
  Installed-Size and Download-Size changes, i.e.

  $ apt show linux-modules-5.8.0-53-generic linux-modules-
  extra-5.8.0-53-generic  | grep -e Package: -e Size:

  Package: linux-modules-5.8.0-53-generic
  Installed-Size: 81.5 MB
  Download-Size: 15.5 MB

  Package: linux-modules-extra-5.8.0-53-generic
  Installed-Size: 215 MB
  Download-Size: 41.5 MB

  In theory, there should not be a significant change in the Download-
  size. It is desired that there is a significant reduction in
  Installed-Size. Modules take up about 300MB and normally one has upto
  three kernel version installed, resulting in about of 1GB of disk
  space that one constantly pays for.

  == Boot Speed ==

  In theory, boot speed may either improve or regress. It depends if
  disk IO is slower than decompression speed, meaning loading compressed
  modules is faster.

  Also one has to observe the changes in the initrd size. zstd(zstd)
  compression may result in slight growth, which shouldn't impact boot
  speed too much.

  = Outcomes =

  If installed size savings can be achieved without regressing bootspeed
  we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default.

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


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

[Kernel-packages] [Bug 1943817] Re: Realtek 8852 wifi kernel module is missing

[Pirouette Cacahuète]

Can we hope that the rtw89 dkms package be at least available in the
repos for 21.10 ?

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

Title:
  Realtek 8852 wifi kernel module is missing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Just got a Thinkpad with Realtek 8852a wifi card. I installed Impish daily 
(kernel 5.13).
  Not recognized.
  The firmware is natively present in firmware folder, /rtw89/rtw8852a_fw.bin .

  But the kernel module is not loaded and in fact no module is loadable!
  sudo modprobe rtw8[completion] does not return this wifi card's module.

  So I did run for:
  https://github.com/lwfinger/rtw89
  and it does work but needs to be done for each kernel upgrade...

  Note that Bluetooth was natively ok.

  I tried 5.14 Ubuntu kernel from unstable ppa but same issue.

  lspci
  03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8852
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  fthx   2333 F pulseaudio
   /dev/snd/controlC1:  fthx   2333 F pulseaudio
   /dev/snd/controlC0:  fthx   2333 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-09-15 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910)
  MachineType: LENOVO 21AVFR
  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 amdgpu
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-9-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9.9-generic 5.14.1
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9-generic N/A
   linux-backports-modules-5.14.0-9-generic  N/A
   linux-firmware1.199
  Tags:  impish
  Uname: Linux 5.14.0-9-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: 06/21/2021
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET39W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21AVFR
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21AVFR
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1615405] Re: zfs share doesn't work

[Colin Ian King]

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

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

Title:
  zfs share doesn't work

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I'm testing on Ubuntu 16.04 with the included zol 0.6.5.

  I have also reported this bug here:
  https://github.com/zfsonlinux/zfs/issues/4999

  zfs share and zfs share -a just don't work. zfs set sharesmb=on
  pool/dataset works fine. I discovered that the shares are listed in
  /etc/dfs/sharetab but don't work. If I reboot or anything and try to
  share them again with zfs share, it will not work. net usershare list
  displays nothing. And of course because of this all shares are lost on
  every reboot.

  Despite a dataset having the sharesmb=on value set, it will not share
  with zfs share -a and if I use zfs share pool/dataset it says: cannot
  share 'pool/dataset': filesystem already shared, when net usershare
  list shows nothing**. Samba is running and the shares appear in
  /etc/dfs/sharetab, not that that is helping me.

  I've detailed a bunch of stuff at serverfault... if that's not good
  enough, I can bring some of it over here:

  http://serverfault.com/questions/797938/ubuntu-xenial-16-04-zfs-share-
  command-doesnt-work-for-smb-shares

  System/package informatiom

  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu12
Candidate: 0.6.5.6-0ubuntu12
Version table:
   *** 0.6.5.6-0ubuntu12 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://ca.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu12
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Aug 21 12:11:47 2016
  InstallationDate: Installed on 2016-05-26 (87 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.zfs: [modified]
  mtime.conffile..etc.default.zfs: 2016-07-12T22:45:19.830513

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


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

[Kernel-packages] [Bug 1914221] Re: dev test in ubuntu_stress_smoke_test hang with G-5.8 lowlatency

[Colin Ian King]

** Changed in: stress-ng
   Status: New => Invalid

** Changed in: ubuntu-kernel-tests
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

** Changed in: stress-ng
 Assignee: Colin Ian King (colin-king) => (unassigned)

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

Title:
  dev test in ubuntu_stress_smoke_test hang with G-5.8 lowlatency

Status in Stress-ng:
  Invalid
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Issue found on Groovy 5.8.0-42.47 lowlatency kernel with node
  "spitfire" on Intel cloud.

  Reproduce rate: 2/2

  The ubuntu_stress_smoke_test hang with the dev test on it:

   dentry STARTING
   dentry RETURNED 0
   dentry PASSED
   dev STARTING
   Timer expired (2100 sec.), nuking pid 15918
  ERROR   ubuntu_stress_smoke_test.stress-smoke-test  
ubuntu_stress_smoke_test.stress-smoke-test  timestamp=1612262460
localtime=Feb 02 10:41:00   Test timeout expired, rc=15

  However, this issue didn't happen on this node with Groovy 5.8 generic
  kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1914221/+subscriptions


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

[Kernel-packages] [Bug 1723948] Re: error -lock in zfs send

[Colin Ian King]

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

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

Title:
  error -lock in zfs send

Status in Native ZFS for Linux:
  New
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  zfs send stop working. the process did not produce output. checked by
  mbuffer log

  in kernel.log: 
  Oct 15 07:25:53 zfs-cis kernel: [479439.151281] INFO: task zfs:8708 blocked 
for more than 120 seconds.
  Oct 15 07:25:53 zfs-cis kernel: [479439.156980]   Tainted: P   OE 
  4.4.0-96-generic #119-Ubuntu
  Oct 15 07:25:53 zfs-cis kernel: [479439.162688] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Oct 15 07:25:53 zfs-cis kernel: [479439.173974] zfs D 
88197bd77318 0  8708   8141 0x
  Oct 15 07:25:53 zfs-cis kernel: [479439.173981]  88197bd77318 
810c3dc2 8820374cf000 881b645ff000
  Oct 15 07:25:53 zfs-cis kernel: [479439.173985]  88197bd78000 
00792c6d 882030aa4ac8 
  Oct 15 07:25:53 zfs-cis kernel: [479439.173989]  88101dac1840 
88197bd77330 8183f165 882030aa4a00
  Oct 15 07:25:53 zfs-cis kernel: [479439.173993] Call Trace:
  Oct 15 07:25:53 zfs-cis kernel: [479439.174006]  [] ? 
__wake_up_common+0x52/0x90
  Oct 15 07:25:53 zfs-cis kernel: [479439.174023]  [] 
schedule+0x35/0x80
  Oct 15 07:25:53 zfs-cis kernel: [479439.174045]  [] 
taskq_wait_id+0x60/0xb0 [spl]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174051]  [] ? 
wake_atomic_t_function+0x60/0x60
  Oct 15 07:25:53 zfs-cis kernel: [479439.174115]  [] ? 
dump_write+0x230/0x230 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174178]  [] 
spa_taskq_dispatch_sync+0x92/0xd0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174223]  [] 
dump_bytes+0x51/0x70 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174267]  [] 
dump_write+0x11e/0x230 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174311]  [] 
backup_cb+0x633/0x850 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174356]  [] 
traverse_visitbp+0x47a/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174365]  [] ? 
spl_kmem_alloc+0xaf/0x190 [spl]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174409]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174462]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174503]  [] 
traverse_dnode+0x7f/0xe0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174542]  [] 
traverse_visitbp+0x6cc/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174579]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174616]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174653]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174690]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174726]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174762]  [] 
traverse_visitbp+0x5c0/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174799]  [] 
traverse_dnode+0x7f/0xe0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174835]  [] 
traverse_visitbp+0x865/0x960 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174871]  [] 
traverse_impl+0x1ae/0x410 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174908]  [] ? 
dmu_recv_end_check+0x210/0x210 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174944]  [] 
traverse_dataset+0x52/0x60 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.174981]  [] ? 
dmu_recv_end_check+0x210/0x210 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175017]  [] 
dmu_send_impl+0x409/0x560 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175060]  [] 
dmu_send_obj+0x172/0x1e0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175129]  [] 
zfs_ioc_send+0xe9/0x2c0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175143]  [] ? 
strdup+0x3b/0x60 [spl]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175207]  [] 
zfsdev_ioctl+0x44b/0x4e0 [zfs]
  Oct 15 07:25:53 zfs-cis kernel: [479439.175218]  [] 
do_vfs_ioctl+0x29f/0x490
  Oct 15 07:25:53 zfs-cis kernel: [479439.175225]  [] ? 
_do_fork+0xec/0x360
  Oct 15 07:25:53 zfs-cis kernel: [479439.175232]  [] 
SyS_ioctl+0x79/0x90
  Oct 15 07:25:53 zfs-cis kernel: [479439.175242]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71

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


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

[Kernel-packages] [Bug 1940083] Re: zfs send encrypt causes kernel NULL pointer dereference

[Colin Ian King]

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

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

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

Title:
  zfs send encrypt causes kernel NULL pointer dereference

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  zfs send -I works well:

  # uname -a
  Linux sdeziel-desktop 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 
15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  # zfs send -I data/simon/musique@laptop-2020-11-30 data/simon/musique@o | wc 
-c
  5660616
  # dmesg -c
  #

  but when sending encrypted data sets, some snapshot combinations cause
  problem:

  # zfs send -wI data/simon/musique@laptop-2020-11-30 data/simon/musique@o | wc 
-c
  # # hung as nothing is written to the pipe.

  # dmesg -c
  [ 1179.862792] BUG: kernel NULL pointer dereference, address: 0030
  [ 1179.862798] #PF: supervisor read access in kernel mode
  [ 1179.862801] #PF: error_code(0x) - not-present page
  [ 1179.862803] PGD 0 P4D 0 
  [ 1179.862806] Oops:  [#5] SMP PTI
  [ 1179.862809] CPU: 1 PID: 13834 Comm: zfs Tainted: P  D   IO  
5.11.0-27-generic #29~20.04.1-Ubuntu
  [ 1179.862813] Hardware name:  /D54250WYK, BIOS 
WYLPT10H.86A.0054.2019.0902.1752 09/02/2019
  [ 1179.862815] RIP: 0010:dmu_dump_write+0x22c/0x320 [zfs]
  [ 1179.862922] Code: d0 48 89 43 58 49 8b 45 60 48 89 43 38 49 8b 45 68 48 89 
43 40 49 8b 45 70 48 89 43 48 49 8b 45 78 48 89 43 50 e9 9f fe ff ff <49> 8b 45 
30 45 85 c0 74 39 48 85 c0 78 04 80 4b 31 02 48 8d 53 70
  [ 1179.862924] RSP: 0018:a51ae62678f0 EFLAGS: 00010206
  [ 1179.862927] RAX: d1141450686f75df RBX: 952730fdde00 RCX: 

  [ 1179.862929] RDX: 80f7 RSI: 0013 RDI: 
952730fddf38
  [ 1179.862931] RBP: a51ae6267938 R08: 0100 R09: 
0002
  [ 1179.862933] R10: 80f7 R11: 0002 R12: 
a51ae6267ab8
  [ 1179.862935] R13:  R14: 0002 R15: 

  [ 1179.862937] FS:  7fa6a03ac7c0() GS:95298fa8() 
knlGS:
  [ 1179.862939] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1179.862941] CR2: 0030 CR3: 00025a648001 CR4: 
001706e0
  [ 1179.862943] Call Trace:
  [ 1179.862945]  ? wait_woken+0x80/0x80
  [ 1179.862951]  do_dump+0x5da/0x900 [zfs]
  [ 1179.863035]  ? spl_kmem_free+0x28/0x30 [spl]
  [ 1179.863046]  dmu_send_impl+0xdf6/0x1570 [zfs]
  [ 1179.863129]  ? dbuf_rele_and_unlock+0x32e/0x6d0 [zfs]
  [ 1179.863204]  ? dbuf_rele+0x3d/0x50 [zfs]
  [ 1179.863279]  ? dmu_buf_rele+0xe/0x10 [zfs]
  [ 1179.863354]  dmu_send_obj+0x24c/0x360 [zfs]
  [ 1179.863435]  ? mze_find+0xd4/0xf0 [zfs]
  [ 1179.863551]  zfs_ioc_send+0x11d/0x2c0 [zfs]
  [ 1179.863665]  ? zfs_ioc_send+0x2c0/0x2c0 [zfs]
  [ 1179.863778]  zfsdev_ioctl_common+0x679/0x930 [zfs]
  [ 1179.863892]  ? __kmalloc_node+0x40d/0x4e0
  [ 1179.863899]  zfsdev_ioctl+0x57/0xe0 [zfs]
  [ 1179.864008]  __x64_sys_ioctl+0x91/0xc0
  [ 1179.864012]  do_syscall_64+0x38/0x90
  [ 1179.864018]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 1179.864023] RIP: 0033:0x7fa6a09a050b
  [ 1179.864026] Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
  [ 1179.864028] RSP: 002b:7ffdb9687fb8 EFLAGS: 0246 ORIG_RAX: 
0010
  [ 1179.864032] RAX: ffda RBX: 55dd6be41f60 RCX: 
7fa6a09a050b
  [ 1179.864033] RDX: 7ffdb968b5c0 RSI: 5a1c RDI: 
0003
  [ 1179.864035] RBP: 7ffdb968b580 R08: 5a1c R09: 
0003
  [ 1179.864037] R10: 0009 R11: 0246 R12: 
7ffdb968b5c0
  [ 1179.864038] R13: 55dd6be41f70 R14:  R15: 
0001
  [ 1179.864041] Modules linked in: vhost_vsock 
vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm nf_log_ipv6 
ip6table_filter ip6table_nat ip6t_rpfilter ip6table_mangle ip6table_raw 
ip6_tables nf_log_ipv4 nf_log_common xt_owner xt_LOG xt_conntrack 
iptable_filter xt_MASQUERADE xt_nat xt_tcpudp iptable_nat nf_nat iptable_mangle 
iptable_raw bpfilter nls_iso8859_1 zfs(PO) zunicode(PO) zzstd(O) zlua(O) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) intel_rapl_msr spl(O) 
intel_rapl_common snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
x86_pkg_temp_thermal snd_hda_codec_hdmi intel_powerclamp coretemp snd_hda_intel 
snd_intel_dspcfg mei_hdcp kvm_intel soundwire_intel at24 
soundwire_generic_allocation kvm soundwire_cadence snd_hda_codec snd_hda_core 
soundwire_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_soc_core 
rapl snd_usb_audio snd_compress ac97_bus 

[Kernel-packages] [Bug 1941044] Re: ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade to linux-firmware 1.187.16 due to the presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pn

[You-Sheng Yang]

** Summary changed:

- ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade 
to linux-firmware 1.187.16
+ ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade 
to linux-firmware 1.187.16 due to the presence of 
'/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm'

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

Title:
  ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with
  upgrade to linux-firmware 1.187.16 due to the presence of
  '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm'

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Focal:
  Triaged

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS

  $ uname -r
  5.11.0-27-generic

  $ apt-cache policy linux-firmware
  linux-firmware:
Installed: 1.187.16

  $ ip a
  1: lo
  2: enp0s31f6

  Device:
  Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725]

  WiFi adapter disappears from network manager and
  > ip a
  following update to 
  > linux-firmware 1.187.16
  and a restart

  Able to confirm this package is the problem as the issue can be reversed by 
downgrading to
  > linux-firmware 1.187.15

  Our organisation has had at least one other identical device experience the 
same issue before
  > apt-mark hold linux-firmware
  was pushed out.

  Happy to supply any other information or logs on request.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.16
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  logansymons   7485 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 25 18:10:49 2021
  Dependencies:
   
  IwConfig:
   lono wireless extensions.
   
   enp0s31f6  no wireless extensions.
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20W0005AAU
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic 
root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7
  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
  RfKill:
   0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N34ET41W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20W0005AAU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 2i
  dmi.product.name: 20W0005AAU
  dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i
  dmi.product.version: ThinkPad T14 Gen 2i
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1946222] Re: presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' in the 'linux-firmware' package causes Intel AX210 wifi to cease functioning

[You-Sheng Yang]

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

** This bug has been marked a duplicate of bug 1941044
   ax210 [8086:2725] subsystem [8086:0020] wifi adapter disappears with upgrade 
to linux-firmware 1.187.16 due to the presence of 
'/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm'

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

Title:
  presence of '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' in the 'linux-
  firmware' package causes Intel AX210 wifi to cease functioning

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' exists (after a fresh OS
  installation & after updates to the 'linux-firmware' package)--wifi
  fails to function:

  $ lspci -knn | grep Net -A3
  93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 
1a)
Subsystem: Intel Corporation Device [8086:4020]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  
  $ dmesg | grep iwlwifi
  [2.390962] iwlwifi :93:00.0: enabling device ( -> 0002)
  [2.412571] iwlwifi :93:00.0: api flags index 2 larger than supported 
by driver
  [2.412585] iwlwifi :93:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
93.8.63.28
  [2.412827] iwlwifi :93:00.0: loaded firmware version 59.601f3a66.0 
ty-a0-gf-a0-59.ucode op_mode iwlmvm
  [2.433308] iwlwifi :93:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
  [2.582482] iwlwifi :93:00.0: loaded PNVM version 0x324cd670
  [2.830634] iwlwifi :93:00.0: Timeout waiting for PNVM load!
  [2.830639] iwlwifi :93:00.0: Failed to start RT ucode: -110
  [2.830643] iwlwifi :93:00.0: iwl_trans_send_cmd bad state = 1
  [3.034634] iwlwifi :93:00.0: firmware didn't ACK the reset - continue 
anyway
  [3.046824] iwlwifi :93:00.0: Failed to run INIT ucode: -110



  When '/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm' is deleted, or renamed--
  wifi works:

  $ lspci -knn | grep Net -A3
  93:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 
1a)
Subsystem: Intel Corporation Device [8086:4020]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

  
  $ dmesg | grep iwlwifi
  [3.425668] iwlwifi :93:00.0: enabling device ( -> 0002)
  [3.436377] iwlwifi :93:00.0: api flags index 2 larger than supported 
by driver
  [3.436392] iwlwifi :93:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 
93.8.63.28
  [3.436634] iwlwifi :93:00.0: loaded firmware version 59.601f3a66.0 
ty-a0-gf-a0-59.ucode op_mode iwlmvm
  [3.459053] iwlwifi :93:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, 
REV=0x420
  [3.698849] iwlwifi :93:00.0: base HW address: a0:e7:0b:5a:ec:77
  [3.716331] iwlwifi :93:00.0 wlp147s0: renamed from wlan0


  --1--
  $ lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  --2--
  $ apt-cache policy linux-firmware
  linux-firmware:
Installed: 1.187.17
Candidate: 1.187.17
Version table:
   *** 1.187.17 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.187 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages

  --3--
  Expectation: Intel AX210 wifi works without having to perform extra steps to 
rename/delete files after linux-firmware package updates

  --4--
  Reality: Intel AX210 wifi does not work without performing extra steps to 
rename/delete files after linux-firmware package updates 


  I have no idea where the .pnvm file is coming from as it is not
  present in the files provided by Intel at
  
https://www.intel.com/content/www/us/en/support/articles/05511/wireless.html


  Please consider removing the .pnvm files from all versions of the
  'linux-firmware' package... currently found in these versions:

  1 pnvm file - https://packages.ubuntu.com/focal-updates/all/linux-
  firmware/filelist

  2 pnvm files - https://packages.ubuntu.com/impish/all/linux-
  firmware/filelist

  
  The pnvm file is not present in the Ubuntu 2104 (Hirsute) linux-firmware 
package and the AX210 wifi works perfectly well on that platform but it fails 
to function on 20.04 (Focal), where the pnvm is present, and will likely also 
fail in 21.10 (Impish).

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


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