[Kernel-packages] [Bug 1966147] Re: 5.13.0-37.42 terrible sound via usb

[vinz]

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

Thank **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/1966147

Title:
  5.13.0-37.42 terrible sound via usb

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  updated yesterday to kernel 5.13.0-37.42 and sound from usb is awfully
  distorted, while from bluetooth and hdmi is unaltered.

  reverted to 5.13.0-35.40 via grub and sound via usb is back to normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  vinz   2684 F pulseaudio
   /dev/snd/controlC2:  vinz   2684 F pulseaudio
   /dev/snd/controlC1:  vinz   2684 F pulseaudio
   /dev/snd/controlC0:  vinz   2684 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-10-24 (518 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic 
root=UUID=fcdf975b-fa37-4978-8a4b-e452f2f74512 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-37-generic N/A
   linux-backports-modules-5.13.0-37-generic  N/A
   linux-firmware 1.201.5
  Tags:  impish
  Uname: Linux 5.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-27 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F30
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Stefan Bader]

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

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
  next packet size") landed in 5.13.0-35 introduced regression to USB
  audio device.

  It's because this patch introduced the available frame size check, but
  the conversion forgot to initialize the temporary variable properly.

  A workaround is to modify /etc/pulse/daemon.conf, set the
  default-sample-rate to 48000, uncomment it by removing the semicolon
  at the beginning of the line. And restart pulseaudio with: 
systemctl --user restart pulseaudio.service

  [Fix]
  * 23939115 ALSA: usb-audio: Fix packet size calculation regression
  This patch can be cherry-picked into Impish kernel, and it's already in
  the master-next branch of Jammy tree.

  [Test]
  Test kernels built with 5.13.0-37 + this patch, can be found in:
  * Focal-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
  * Impish-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/

  Both kernels were tested by affected users and they're working as
  expected.

  [Where problems could occur]
  If this patch is incorrect, it might affect USB audio devices.

  
  [Original Bug Report]
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966969] Re: linux-aws: Xen: Issues with detaching volume

[Stefan Bader]

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

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

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

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

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

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

Title:
  linux-aws: Xen: Issues with detaching volume

Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Impish:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  We are observing issue with the secondary volume stuck in detaching. This is 
observed with the latest Canonical, Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, 
amd64 focal image build on 2022-03-08 and Xen instance type( for eg : m4, t2 
instance type )
  AMI in eu-west-1 : ami-0f4ffbcba23a6c434
  AMI in us-east-1 : ami-021feb4aa3b3c59c3

  When terminating an instance with a stuck volume the shutdown process is 
interrupted by a xen task hanging:
  [ 847.895334] INFO: task xenwatch:188 blocked for more than 483 seconds.
  [ 847.901573] Not tainted 5.13.0-1017-aws #19~20.04.1-Ubuntu
  [ 847.907144] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 847.914462] task:xenwatch state:D stack: 0 pid: 188 ppid: 2 flags:0x4000
  [ 847.914467] Call Trace:
  [ 847.914469] 
  [ 847.914472] __schedule+0x2ee/0x900
  [ 847.914478] schedule+0x4f/0xc0
  [ 847.914479] schedule_preempt_disabled+0xe/0x10
  [ 847.914482] __mutex_lock.isra.0+0x183/0x4d0
  [ 847.914486] __mutex_lock_slowpath+0x13/0x20
  [ 847.914487] mutex_lock+0x32/0x40
  [ 847.914489] del_gendisk+0x90/0x200
  [ 847.914493] xlvbd_release_gendisk+0x72/0xc0
  [ 847.914499] blkback_changed+0x101/0x210
  [ 847.914502] xenbus_otherend_changed+0x8f/0x130
  [ 847.914507] backend_changed+0x13/0x20
  [ 847.914510] xenwatch_thread+0xa6/0x180
  [ 847.914513] ? wait_woken+0x80/0x80
  [ 847.914517] ? test_reply.isra.0+0x40/0x40
  [ 847.914520] kthread+0x12b/0x150
  [ 847.914523] ? set_kthread_struct+0x40/0x40
  [ 847.914525] ret_from_fork+0x22/0x30
  [ 847.914531] 

  this looks like it's waiting on a xen block device to be released.

  Following steps used to reproduce the issue:
  * Created a m4,t2(xen) instance with the latest ami for latest Canonical, 
Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, amd64
  * Created a filesystem on volume
  * Mounted volume through OS
  * Unmounted volume in OS
  * Detached volume from AWS console
  * Volume gets stuck.

  We at the internal team observed this commit upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05d69d950d9d84218fc9beafd02dea1f6a70e09e

  [...] and a del_gendisk from the block device release
  method, which will deadlock.

  It has a Fixes: tag referring to a commit from 5.13 so this could be
  the root-cause. While testing, we observed this commit is fixing the
  issue.

  [Test Plan]

  Amazon tested

  [Where things could go wrong]

  Detaching volumes could fail in new and bizarre ways

  [Other Info]

  SF: #00331175

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


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

[Kernel-packages] [Bug 1967223] [NEW] nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Amol Dhamale]

Public bug reported:

Firefox window crashes and any newly open window clones infinitely

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.13.0-35-generic
Date: Sun Mar 13 11:55:57 2022
DuplicateSignature: 
dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23:
 error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state 
*)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct 
drm_plane_state *)’ [-Werror=incompatible-pointer-types]
InstallationDate: Installed on 2021-03-24 (371 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageVersion: 460.73.01-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, 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.6
SourcePackage: nvidia-graphics-drivers-460
Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module failed 
to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-460 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module
  failed to build

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  New

Bug description:
  Firefox window crashes and any newly open window clones infinitely

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.13.0-35-generic
  Date: Sun Mar 13 11:55:57 2022
  DuplicateSignature: 
dkms:nvidia-dkms-460:460.73.01-0ubuntu0.20.04.1:/var/lib/dkms/nvidia/460.73.01/build/nvidia-drm/nvidia-drm-crtc.c:311:23:
 error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state 
*)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct 
drm_plane_state *)’ [-Werror=incompatible-pointer-types]
  InstallationDate: Installed on 2021-03-24 (371 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageVersion: 460.73.01-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, 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.6
  SourcePackage: nvidia-graphics-drivers-460
  Title: nvidia-dkms-460 460.73.01-0ubuntu0.20.04.1: nvidia kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

[Andy Chi]

** Tags added: originate-from-1966018 stella

** Tags added: originate-from-1966011

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  
https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Kernel-packages] [Bug 1966870] Re: Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs

[Christian Ehrhardt ]

FYI for a different test I upgraded the system to Impish and on the
5.13.0-39-generic there neither of the two kernel bugs happens.

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

Title:
  Focal 20.04.4 5.13.0-27-generic crashing disabling CPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi I'm facing the following crash now two times in a row while runnign the 
same
  test - so somewhat reproducible it seems:

  [ 1444.399448] BUG: kernel NULL pointer dereference, address: 0008
  [ 1444.431172] #PF: supervisor write access in kernel mode
  [ 1444.454715] #PF: error_code(0x0002) - not-present page
  [ 1444.478052] PGD 0 P4D 0
  [ 1444.489448] Oops: 0002 [#1] SMP PTI
  [ 1444.505120] CPU: 6 PID: 26233 Comm: chcpu Tainted: PW  O  
5.13.0-27-generic #29~20.04.1-Ubuntu
  [ 1444.549884] Hardware name: HP ProLiant DL360 Gen9/ProLiant DL360 Gen9, 
BIOS P89 01/22/2018
  [ 1444.587322] RIP: 0010:blk_mq_hctx_notify_dead+0xc7/0x190
  [ 1444.611352] Code: 04 49 8d 54 05 08 4c 01 e8 48 8b 48 08 48 39 ca 74 66 48 
8b 48 08 48 39 ca 74 21 48 8b 3a 48 8b 4d c8 48 8b 72 08 48 89 7d c8 <4c> 89 77 
08 48 89 0e 48 89 71 08 48 89 12 48 89 50 10 41 0f b7 84
  [ 1444.696490] RSP: 0018:bf5d818dbbf0 EFLAGS: 00010282
  [ 1444.720510] RAX: df5d7fb788c0 RBX:  RCX: 
bf5d818dbbf0
  [ 1444.752719] RDX: df5d7fb788c8 RSI:  RDI: 

  [ 1444.784978] RBP: bf5d818dbc28 R08:  R09: 
bf5d818dbae8
  [ 1444.816712] R10: 0001 R11: 0001 R12: 
983d939b
  [ 1444.848844] R13: df5d7fb788c0 R14: bf5d818dbbf0 R15: 
0005
  [ 1444.881389] FS:  7f1c8fe88580() GS:9844dfb8() 
knlGS:
  [ 1444.918201] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1444.944633] CR2: 0008 CR3: 00064ddf6006 CR4: 
001706e0
  [ 1444.977001] Call Trace:
  [ 1444.988071]  ? blk_mq_exit_hctx+0x160/0x160
  [ 1445.007037]  cpuhp_invoke_callback+0x179/0x430
  [ 1445.027179]  cpuhp_invoke_callback_range+0x44/0x80
  [ 1445.048737]  _cpu_down+0x109/0x310
  [ 1445.064062]  cpu_down+0x36/0x60
  [ 1445.077882]  cpu_device_down+0x16/0x20
  [ 1445.094741]  cpu_subsys_offline+0xe/0x10
  [ 1445.112439]  device_offline+0x8e/0xc0
  [ 1445.129064]  online_store+0x4c/0x90
  [ 1445.144835]  dev_attr_store+0x17/0x30
  [ 1445.161307]  sysfs_kf_write+0x3e/0x50
  [ 1445.177856]  kernfs_fop_write_iter+0x138/0x1c0
  [ 1445.198036]  new_sync_write+0x117/0x1b0
  [ 1445.215386]  vfs_write+0x185/0x250
  [ 1445.230649]  ksys_write+0x67/0xe0
  [ 1445.245565]  __x64_sys_write+0x1a/0x20
  [ 1445.262448]  do_syscall_64+0x61/0xb0
  [ 1445.278585]  ? do_syscall_64+0x6e/0xb0
  [ 1445.295940]  ? asm_exc_page_fault+0x8/0x30
  [ 1445.314969]  entry_SYSCALL_64_after_hwframe+0x44/0xae
  [ 1445.338356] RIP: 0033:0x7f1c8fda30a7
  [ 1445.355062] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24
  [ 1445.440161] RSP: 002b:7fffed1c4418 EFLAGS: 0246 ORIG_RAX: 
0001
  [ 1445.474829] RAX: ffda RBX: 0040 RCX: 
7f1c8fda30a7
  [ 1445.507219] RDX: 0001 RSI: 559369f25869 RDI: 
0004
  [ 1445.539438] RBP: 7f1c8fe88500 R08:  R09: 
7fffed1c43c0
  [ 1445.572547] R10:  R11: 0246 R12: 
0004
  [ 1445.604842] R13: 7fffed1c4420 R14: 559369f25869 R15: 
0001
  [ 1445.636897] Modules linked in: vhost_net tap ebtable_filter ebtables veth 
nbd xt_comment zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) 
zcommon(PO) znvpair(PO) spl(O) vhost_vsock vmw_vsock_virtio_transport_common 
vhost vhost_iotlb vsock xt_MASQUERADE xt_conntrack xt_CHECKSUM ipt_REJECT 
nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle 
iptable_nat nf_tables ip6table_filter ip6_tables iptable_filter bpfilter bridge 
stp llc nfnetlink_cttimeout nfnetlink openvswitch nsh nf_conncount nf_nat 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 uio_pci_generic uio nls_iso8859_1 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr 
intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
rpcrdma kvm_intel sunrpc kvm rdma_ucm ib_iser libiscsi scsi_transport_iscsi 
rapl ib_umad rdma_cm ib_ipoib intel_cstate efi_pstore iw_cm ib_cm hpilo ioatdma 
acpi_ipmi acpi_tad ipmi_si mac_hid acpi_power_meter sch_fq_codel ipmi_devintf 
ipmi_msghandler msr
  [ 1445.636951]  ip_tables x_tables autofs4 btrfs blake2b_generic 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ib_uverbs 
ib

[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

[Chris Halse Rogers]

Thanks for that bisect.

Annoyingly, that commit doesn't cherry-pick cleanly onto 5.15, but I'll
see if I can munge it up to test.

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

Title:
  [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1966634] Re: fingerprint sensor driver detected but hidden option to login with fingerprint in gnome-settings

[Matěj Valášek]

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

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

Title:
  fingerprint sensor driver detected but hidden option to login with
  fingerprint in gnome-settings

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  this is output of my lsusb command:
  matej@matej-laptop:~$ lsusb
  Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit 
Ethernet Adapter
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 003: ID 06cb:00f0 Synaptics, Inc. 
  Bus 003 Device 002: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
  Bus 003 Device 004: ID 045e:0737 Microsoft Corp. Compact Optical Mouse 500
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 002: ID 30c9:000f Luxvisions Innotech Limited HP HD Camera
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

   it is this device: Bus 003 Device 003: ID 06cb:00f0 Synaptics, Inc.
  on windows 11 on my dual boot system works just fine

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matej  2133 F pulseaudio
   /dev/snd/pcmC1D0c:   matej  2133 F...m pulseaudio
   /dev/snd/pcmC1D0p:   matej  2133 F...m pulseaudio
   /dev/snd/controlC0:  matej  2133 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 28 09:28:06 2022
  InstallationDate: Installed on 2022-03-23 (4 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210502)
  MachineType: HP HP EliteBook 845 G8 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-37-generic 
root=UUID=e3adb113-cca4-4316-9c3b-edc124da9ca4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-37-generic N/A
   linux-backports-modules-5.13.0-37-generic  N/A
   linux-firmware 1.201.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/11/2022
  dmi.bios.release: 8.3
  dmi.bios.vendor: HP
  dmi.bios.version: T82 Ver. 01.08.03
  dmi.board.name: 8895
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 43.2A.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 67.42
  dmi.modalias: 
dmi:bvnHP:bvrT82Ver.01.08.03:bd02/11/2022:br8.3:efr67.42:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.2A.00:cvnHP:ct10:cvr:sku48R69EA#BCM:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 845 G8 Notebook PC
  dmi.product.sku: 48R69EA#BCM
  dmi.sys.vendor: HP

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


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

[Kernel-packages] [Bug 1961546] Re: init freezes when >1 display connected on rocket lake PC

[Felix Miata]

Original problem continues with kernel 5.15.0-23, but there is more than
a screenful of fb output in what appears to be 1024x768 mode before
lockup on switch to i915. Xorg is working normally with only one
connected display.

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

Title:
  init freezes when >1 display connected on rocket lake PC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  # apt-cache policy linux-image-5.15.0-18-generic
  linux-image-5.15.0-18-generic:
Installed: 5.15.0-18.18
Candidate: 5.15.0-18.18
Version table:
   *** 5.15.0-18.18 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  # lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  To reproduce: try to boot with more than one connected display on Intel 
Rocket Lake PC (e.g. Asus B560-M with i5-11400)
  Actual results: init stops around the time KMS should engage
  Expected results: boots normally

  Upstream bugs fixed:
  https://gitlab.freedesktop.org/drm/intel/-/issues/4762
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006166 fixed in 5.16.10 & 
5.17rc4
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D17p', '/dev/snd/pcmC0D16p', '/dev/snd/pcmC0D15p', 
'/dev/snd/pcmC0D14p', '/dev/snd/pcmC0D13p', '/dev/snd/pcmC0D12p', 
'/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', 
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
   Bus 001 Device 004: ID 046d:c404 Logitech, Inc. TrackMan Wheel
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUS System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=LABEL=tm8p17ub2204 noresume 
ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 video=1440x900@60 5
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-18-generic N/A
   linux-backports-modules-5.15.0-18-generic  N/A
   linux-firmware 20220217.git6342082c-0ubuntu1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 10/27/2021
  dmi.bios.release: 12.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1203
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B560M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1203:bd10/27/2021:br12.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB560M-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Kernel-packages] [Bug 1967215] [NEW] Support new ids in 510

[Bin Li]

Public bug reported:

In 510.54 nvidia couldn't be installed in below platforms.

10de:1fb6
10de:1fb7
10de:2438
10de:24b9
10de:24ba
10de:25ba

** Affects: oem-priority
 Importance: Critical
 Assignee: jeremyszu (os369510)
 Status: In Progress

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority originate-from-1966673 originate-from-1966833 
originate-from-1966839 originate-from-1967195 sutton

** Tags added: oem-priority originate-from-1966833 sutton

** Tags added: originate-from-1967195

** Tags added: originate-from-1966673

** Tags added: originate-from-1966839

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

Title:
  Support new ids in 510

Status in OEM Priority Project:
  In Progress
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  In 510.54 nvidia couldn't be installed in below platforms.

  10de:1fb6
  10de:1fb7
  10de:2438
  10de:24b9
  10de:24ba
  10de:25ba

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


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

[Kernel-packages] [Bug 1967205] 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/1967205

Title:
  Lenovo laptop doesn't wake from sleep with kernel newer than
  5.13.0-27-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue: When closing the lid, my Lenovo 6 laptop goes to sleep, but
  when opening the lid the laptop will not wake from sleep when using a
  kernel newer than 5.13.0-27-generic. Pressing keys or the power button
  also does not wake the laptop from sleep.

  Expected behavior: The laptop should wake from sleep when opening the
  laptop lid when using the newest kernel.

  Steps to reproduce:
  1. Boot laptop using kernel 5.13.0-27-generic
  2. Close lid to put laptop to sleep
  3. Open laptop lid and see laptop resume from sleep
  4. Boot laptop with kernel newer than 5.13.0-27-generic
  5. Close lid to put laptop to sleep
  6. Open laptop lid and see laptop never resumes from sleep

  Work around: Hold the power button until laptop powers off. Press the
  power button again to power on the laptop

  Release: Ubuntu 21.10
  Machine: Lenovo Yoga 6 laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-39-generic 5.13.0-39.44
  ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cale   1963 F pulseaudio
   /dev/snd/controlC2:  cale   1963 F pulseaudio
   /dev/snd/controlC0:  cale   1963 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 21:50:57 2022
  InstallationDate: Installed on 2021-12-06 (114 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 82ND
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=5f98fca4-658f-4f22-8c2b-f320c086f693 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.201.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6CN10WW(V1.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 6 13ALC6
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6CN10WW(V1.03):bd05/28/2021:br1.10:efr1.10:svnLENOVO:pn82ND:pvrYoga613ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrYoga613ALC6:skuLENOVO_MT_82ND_BU_idea_FM_Yoga613ALC6:
  dmi.product.family: Yoga 6 13ALC6
  dmi.product.name: 82ND
  dmi.product.sku: LENOVO_MT_82ND_BU_idea_FM_Yoga 6 13ALC6
  dmi.product.version: Yoga 6 13ALC6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1925421] Re: arm64 support

[Khaled El Mously]

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

** No longer affects: linux-gcp (Ubuntu Groovy)

** No longer affects: linux-gcp (Ubuntu Hirsute)

** No longer affects: linux-gcp (Ubuntu Impish)

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

Title:
  arm64 support

Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  Fix Released
Status in linux-oracle-5.4 package in Ubuntu:
  Invalid
Status in linux-oracle-5.8 package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  New
Status in linux-oracle source package in Bionic:
  Invalid
Status in linux-oracle-5.4 source package in Bionic:
  Fix Released
Status in linux-oracle-5.8 source package in Bionic:
  New
Status in linux-gcp source package in Focal:
  New
Status in linux-oracle source package in Focal:
  Fix Released
Status in linux-oracle-5.4 source package in Focal:
  Invalid
Status in linux-oracle-5.8 source package in Focal:
  Fix Released
Status in linux-oracle source package in Groovy:
  Fix Released
Status in linux-oracle-5.4 source package in Groovy:
  Invalid
Status in linux-oracle-5.8 source package in Groovy:
  Fix Committed
Status in linux-oracle source package in Hirsute:
  Fix Released
Status in linux-oracle-5.4 source package in Hirsute:
  Invalid
Status in linux-oracle-5.8 source package in Hirsute:
  Invalid
Status in linux-oracle source package in Impish:
  Fix Released
Status in linux-oracle-5.4 source package in Impish:
  Invalid
Status in linux-oracle-5.8 source package in Impish:
  Invalid

Bug description:
  See
  https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view
  for more info

  
  [Impact]
  No support for arm64 currently

  
  [Fix]
  Add arm64 support, including hardware support patches

  [Test]
  Confirm that it boots on desired arm64 hardware, as well as VMs

  [Regression Potential]
  This was never working on arm64 so there should be no risk of regression.
  The requested changes included some refactorings of early memory 
initialization code (all arches) so this presents a small risk. The changes 
were tested on arm64 as well amd64.

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


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

[Kernel-packages] [Bug 1967205] Re: Lenovo laptop doesn't wake from sleep with kernel newer than 5.13.0-27-generic

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Lenovo laptop doesn't wake from sleep with kernel newer than
  5.13.0-27-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Issue: When closing the lid, my Lenovo 6 laptop goes to sleep, but
  when opening the lid the laptop will not wake from sleep when using a
  kernel newer than 5.13.0-27-generic. Pressing keys or the power button
  also does not wake the laptop from sleep.

  Expected behavior: The laptop should wake from sleep when opening the
  laptop lid when using the newest kernel.

  Steps to reproduce:
  1. Boot laptop using kernel 5.13.0-27-generic
  2. Close lid to put laptop to sleep
  3. Open laptop lid and see laptop resume from sleep
  4. Boot laptop with kernel newer than 5.13.0-27-generic
  5. Close lid to put laptop to sleep
  6. Open laptop lid and see laptop never resumes from sleep

  Work around: Hold the power button until laptop powers off. Press the
  power button again to power on the laptop

  Release: Ubuntu 21.10
  Machine: Lenovo Yoga 6 laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-39-generic 5.13.0-39.44
  ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cale   1963 F pulseaudio
   /dev/snd/controlC2:  cale   1963 F pulseaudio
   /dev/snd/controlC0:  cale   1963 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 21:50:57 2022
  InstallationDate: Installed on 2021-12-06 (114 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 82ND
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=5f98fca4-658f-4f22-8c2b-f320c086f693 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-generic N/A
   linux-backports-modules-5.13.0-39-generic  N/A
   linux-firmware 1.201.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2021
  dmi.bios.release: 1.10
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6CN10WW(V1.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 6 13ALC6
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6CN10WW(V1.03):bd05/28/2021:br1.10:efr1.10:svnLENOVO:pn82ND:pvrYoga613ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrYoga613ALC6:skuLENOVO_MT_82ND_BU_idea_FM_Yoga613ALC6:
  dmi.product.family: Yoga 6 13ALC6
  dmi.product.name: 82ND
  dmi.product.sku: LENOVO_MT_82ND_BU_idea_FM_Yoga 6 13ALC6
  dmi.product.version: Yoga 6 13ALC6
  dmi.sys.vendor: LENOVO

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


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

[Kernel-packages] [Bug 1967205] [NEW] Lenovo laptop doesn't wake from sleep with kernel newer than 5.13.0-27-generic

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Issue: When closing the lid, my Lenovo 6 laptop goes to sleep, but when
opening the lid the laptop will not wake from sleep when using a kernel
newer than 5.13.0-27-generic. Pressing keys or the power button also
does not wake the laptop from sleep.

Expected behavior: The laptop should wake from sleep when opening the
laptop lid when using the newest kernel.

Steps to reproduce:
1. Boot laptop using kernel 5.13.0-27-generic
2. Close lid to put laptop to sleep
3. Open laptop lid and see laptop resume from sleep
4. Boot laptop with kernel newer than 5.13.0-27-generic
5. Close lid to put laptop to sleep
6. Open laptop lid and see laptop never resumes from sleep

Work around: Hold the power button until laptop powers off. Press the
power button again to power on the laptop

Release: Ubuntu 21.10
Machine: Lenovo Yoga 6 laptop

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-39-generic 5.13.0-39.44
ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  cale   1963 F pulseaudio
 /dev/snd/controlC2:  cale   1963 F pulseaudio
 /dev/snd/controlC0:  cale   1963 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 21:50:57 2022
InstallationDate: Installed on 2021-12-06 (114 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: LENOVO 82ND
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic 
root=UUID=5f98fca4-658f-4f22-8c2b-f320c086f693 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-39-generic N/A
 linux-backports-modules-5.13.0-39-generic  N/A
 linux-firmware 1.201.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2021
dmi.bios.release: 1.10
dmi.bios.vendor: LENOVO
dmi.bios.version: H6CN10WW(V1.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga 6 13ALC6
dmi.ec.firmware.release: 1.10
dmi.modalias: 
dmi:bvnLENOVO:bvrH6CN10WW(V1.03):bd05/28/2021:br1.10:efr1.10:svnLENOVO:pn82ND:pvrYoga613ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrYoga613ALC6:skuLENOVO_MT_82ND_BU_idea_FM_Yoga613ALC6:
dmi.product.family: Yoga 6 13ALC6
dmi.product.name: 82ND
dmi.product.sku: LENOVO_MT_82ND_BU_idea_FM_Yoga 6 13ALC6
dmi.product.version: Yoga 6 13ALC6
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug impish wayland-session
-- 
Lenovo laptop doesn't wake from sleep with kernel newer than 5.13.0-27-generic
https://bugs.launchpad.net/bugs/1967205
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 1966066] Re: audio from external sound card is distorted

[Po-Hsu Lin]

Patch sent: 
https://lists.ubuntu.com/archives/kernel-team/2022-March/129063.html


** Description changed:

+ [Impact]
+ Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
+ next packet size") landed in 5.13.0-35 introduced regression to USB
+ audio device.
+ 
+ It's because this patch introduced the available frame size check, but
+ the conversion forgot to initialize the temporary variable properly.
+ 
+ A workaround is to modify /etc/pulse/daemon.conf, set the
+ default-sample-rate to 48000, uncomment it by removing the semicolon
+ at the beginning of the line. And restart pulseaudio with: 
+   systemctl --user restart pulseaudio.service
+ 
+ [Fix]
+ * 23939115 ALSA: usb-audio: Fix packet size calculation regression
+ This patch can be cherry-picked into Impish kernel, and it's already in
+ the master-next branch of Jammy tree.
+ 
+ [Test]
+ Test kernels built with 5.13.0-37 + this patch, can be found in:
+ * Focal-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
+ * Impish-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/
+ 
+ Both kernels were tested by affected users and they're working as
+ expected.
+ 
+ [Where problems could occur]
+ If this patch is incorrect, it might affect USB audio devices.
+ 
+ 
+ [Original Bug Report]
  The sound card is a Focusrite Scarlett 2i2.
  
  The sound is distorted everywhere.
  
  Sound via HDMI works.
  
  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
  
  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Commit d215f63d49da ("ALSA: usb-audio: Check available frames for the
  next packet size") landed in 5.13.0-35 introduced regression to USB
  audio device.

  It's because this patch introduced the available frame size check, but
  the conversion forgot to initialize the temporary variable properly.

  A workaround is to modify /etc/pulse/daemon.conf, set the
  default-sample-rate to 48000, uncomment it by removing the semicolon
  at the beginning of the line. And restart pulseaudio with: 
systemctl --user restart pulseaudio.service

  [Fix]
  * 23939115 ALSA: usb-audio: Fix packet size calculation regression
  This patch can be cherry-picked into Impish kernel, and it's already in
  the master-next branch of Jammy tree.

  [Test]
  Test kernels built with 5.13.0-37 + this patch, can be found in:
  * Focal-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/focal/
  * Impish-5.13 - 
https://people.canonical.com/~phlin/kernel/lp-1966066-usb-audio/impish/

  Both kernels were tested by affected users and they're working as
  expected.

  [Where problems could occur]
  If this patch is incorrect, it might affect USB audio devices.

  
  [Original Bug Report]
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Po-Hsu Lin]

** Changed in: linux-signed-hwe-5.13 (Ubuntu Impish)
   Status: Confirmed => Invalid

** Tags added: 5.13 impish

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Po-Hsu Lin]

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

** Also affects: linux-signed-hwe-5.13 (Ubuntu Jammy)
   Importance: Undecided
   Status: Confirmed

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

** Changed in: linux-signed-hwe-5.13 (Ubuntu Jammy)
   Status: Confirmed => Invalid

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Invalid
Status in linux source package in Jammy:
  Fix Committed
Status in linux-signed-hwe-5.13 source package in Jammy:
  Invalid

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Po-Hsu Lin]

User feedback from comment #23, bug 1966147 and bug 1966997 shows
positive test result with both F-5.13 / I-5.13 test kernel in comment
#22.

I will SRU this patch.

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Launchpad Bug Tracker]

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

** Changed in: linux-signed-hwe-5.13 (Ubuntu Impish)
   Status: New => Confirmed

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Launchpad Bug Tracker]

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

** 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-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Po-Hsu Lin]

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

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

** Also affects: linux-signed-hwe-5.13 (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  audio from external sound card is distorted

Status in linux package in Ubuntu:
  Confirmed
Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed
Status in linux source package in Impish:
  In Progress
Status in linux-signed-hwe-5.13 source package in Impish:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966147] Re: 5.13.0-37.42 terrible sound via usb

[Po-Hsu Lin]

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

Hi vinz,
that's awesome,
I will mark this one as a dup of bug 1966066 and move your test result there.
Thanks for testing!

** This bug has been marked a duplicate of bug 1966066
   audio from external sound card is distorted

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

Title:
  5.13.0-37.42 terrible sound via usb

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  updated yesterday to kernel 5.13.0-37.42 and sound from usb is awfully
  distorted, while from bluetooth and hdmi is unaltered.

  reverted to 5.13.0-35.40 via grub and sound via usb is back to normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  vinz   2684 F pulseaudio
   /dev/snd/controlC2:  vinz   2684 F pulseaudio
   /dev/snd/controlC1:  vinz   2684 F pulseaudio
   /dev/snd/controlC0:  vinz   2684 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-10-24 (518 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic 
root=UUID=fcdf975b-fa37-4978-8a4b-e452f2f74512 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-37-generic N/A
   linux-backports-modules-5.13.0-37-generic  N/A
   linux-firmware 1.201.5
  Tags:  impish
  Uname: Linux 5.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-27 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F30
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1966997] Re: Sound glitching since kernel image 5.13.0-37

[Po-Hsu Lin]

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

Thanks for testing! I will mark this as a dup of bug 1966066


** This bug has been marked a duplicate of bug 1966066
   audio from external sound card is distorted

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

Title:
  Sound glitching since kernel image 5.13.0-37

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the update of linux-image-5.13.0-37, there is a lot of audio
  glitching, using linux-image-5.13.0-35 or before doesnt has the issue,
  my sound card is a Texas Instruments PCM2900C Audio CODEC

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-lowlatency 5.13.0.39.48
  ProcVersionSignature: Ubuntu 5.13.0-39.44-lowlatency 5.13.19
  Uname: Linux 5.13.0-39-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cjdg   4045 F pulseaudio
   /dev/snd/pcmC2D0p:   cjdg   4045 F...m pulseaudio
   /dev/snd/controlC1:  cjdg   4045 F pulseaudio
   /dev/snd/controlC0:  cjdg   4045 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Mar 29 13:21:54 2022
  HibernationDevice: RESUME=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 
resume_offset=34816
  InstallationDate: Installed on 2021-04-29 (334 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-UD3
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-lowlatency 
root=UUID=5bf8e992-a5cc-4b4b-b331-69111d42c8f3 ro quiet splash 
resume=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 resume_offset=34816 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-lowlatency N/A
   linux-backports-modules-5.13.0-39-lowlatency  N/A
   linux-firmware1.201.5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-14 (165 days ago)
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-970A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd10/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: GA-970A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1958620] Re: [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

[Joe Barnett]

If I didn't get my good/bad confused on the reverse bisection, this
appears to be the commit that fixes it:

5ac860cc52540df8bca27e0bb25b6744df67e8f0 is the first bad commit
commit 5ac860cc52540df8bca27e0bb25b6744df67e8f0
Author: Ville Syrjälä 
Date:   Thu Mar 3 21:12:06 2022 +0200

drm/i915: Fix DBUF bandwidth vs. cdclk handling

Make the dbuf bandwidth min cdclk calculations match the spec
more closely. Supposedly the arbiter can only guarantee an equal
share of the total bandwidth of the slice to each active plane
on that slice. So we take the max bandwidth of any of the planes
on each slice and multiply that by the number of active planes
on the slice to get a worst case estimate on how much bandwidth
we require.

Signed-off-by: Ville Syrjälä 
Link: 
https://patchwork.freedesktop.org/patch/msgid/20220303191207.27931-9-ville.syrj...@linux.intel.com
Reviewed-by: Stanislav Lisovskiy 

 drivers/gpu/drm/i915/display/intel_bw.c| 157 -
 drivers/gpu/drm/i915/display/intel_bw.h|  10 +-
 drivers/gpu/drm/i915/display/intel_cdclk.c |  67 +---
 drivers/gpu/drm/i915/display/intel_cdclk.h |   2 +
 4 files changed, 147 insertions(+), 89 deletions(-)


** Attachment added: "bisect log 2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+attachment/5574955/+files/bisect

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

Title:
  [Dell XPS 15 9575] Flickering white/black screen once KMS comes up

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This looks like a regression from the 5.13.0-20-generic kernel to the
  5.15.0-17-generic kernel. The display works fine under efifb, but as
  soon as the DRM drivers are loaded and KMS kicks in the display is
  replaced by black with flickering white (apparently when what would be
  on the output changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-17-generic 5.15.0-17.17
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  7134 F pipewire-media-
   /dev/snd/seq:chris  7133 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 21 17:07:08 2022
  InstallationDate: Installed on 2021-06-26 (208 days ago)
  InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622)
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic 
root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-20-generic N/A
   linux-backports-modules-5.13.0-20-generic  N/A
   linux-firmware 1.204
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago)
  dmi.bios.date: 07/07/2019
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.1
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1967188

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

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

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

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

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

Title:
  Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but
  after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly
  after boot. I am aware that there was a bug which is fixed in current
  kernels. But I believe this bug is different.

  I am running KDE Neon which is based on Ubuntu 20.04, but I have also
  tested this with Kubuntu 20.04. Both running with current HWE-Kernel
  5.13.0.39.44~20.04.24 I would also liked to have tested it with
  current 22.04 daily iso's but I could not get a booting live image
  with multisystem.

  What is the difference to the formerly known bugs: It is possible to
  get the Trackpoint working by sending the system into suspend and
  waking it up again. After this the Trackpoint works without a problem.
  So the problem might have something to do with the driver not
  correctly loaded at boot, but this is done correctly when the system
  wakes up from suspend.

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


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

[Kernel-packages] [Bug 1967188] [NEW] Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but after suspend

[Mark]

Public bug reported:

I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly
after boot. I am aware that there was a bug which is fixed in current
kernels. But I believe this bug is different.

I am running KDE Neon which is based on Ubuntu 20.04, but I have also
tested this with Kubuntu 20.04. Both running with current HWE-Kernel
5.13.0.39.44~20.04.24 I would also liked to have tested it with current
22.04 daily iso's but I could not get a booting live image with
multisystem.

What is the difference to the formerly known bugs: It is possible to get
the Trackpoint working by sending the system into suspend and waking it
up again. After this the Trackpoint works without a problem. So the
problem might have something to do with the driver not correctly loaded
at boot, but this is done correctly when the system wakes up from
suspend.

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


** Tags: lenovo systemd-boot thinkpad trackpoint

** Tags added: lenovo systemd-boot thinkpad

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

Title:
  Trackpoint not working on Thinkpad X1 tablet Gen 2 after boot, but
  after suspend

Status in linux package in Ubuntu:
  New

Bug description:
  I have Thinkpad X1 Gen 2 and the Trackpoint is not working directly
  after boot. I am aware that there was a bug which is fixed in current
  kernels. But I believe this bug is different.

  I am running KDE Neon which is based on Ubuntu 20.04, but I have also
  tested this with Kubuntu 20.04. Both running with current HWE-Kernel
  5.13.0.39.44~20.04.24 I would also liked to have tested it with
  current 22.04 daily iso's but I could not get a booting live image
  with multisystem.

  What is the difference to the formerly known bugs: It is possible to
  get the Trackpoint working by sending the system into suspend and
  waking it up again. After this the Trackpoint works without a problem.
  So the problem might have something to do with the driver not
  correctly loaded at boot, but this is done correctly when the system
  wakes up from suspend.

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


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

[Kernel-packages] [Bug 1967186] 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/1967186

Title:
  ezcap u2 card error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a ezcap u3 internal hdmi capture and displays this message,
  also takes upt to 5 minutes to boot, i tried on windows and works
  well, if i unplug it, boot normally

  This is the message..

  usb 11-1: Failed to query (GET_DEF) UVC control 11 on unit 1: -32
  (exp. 2).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-lowlatency 5.13.0.39.48
  ProcVersionSignature: Ubuntu 5.13.0-39.44-lowlatency 5.13.19
  Uname: Linux 5.13.0-39-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  cjdg   4203 F pulseaudio
   /dev/snd/controlC2:  cjdg   4203 F pulseaudio
   /dev/snd/controlC1:  cjdg   4203 F pulseaudio
   /dev/snd/controlC0:  cjdg   4203 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 16:54:18 2022
  HibernationDevice: RESUME=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 
resume_offset=34816
  InstallationDate: Installed on 2021-04-29 (335 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-UD3
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-lowlatency 
root=UUID=5bf8e992-a5cc-4b4b-b331-69111d42c8f3 ro threadirqs quiet splash 
resume=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 resume_offset=34816 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-lowlatency N/A
   linux-backports-modules-5.13.0-39-lowlatency  N/A
   linux-firmware1.201.5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-14 (167 days ago)
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-970A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd10/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: GA-970A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1967186] [NEW] ezcap u2 card error

[Cristian Delgado]

Public bug reported:

I have a ezcap u3 internal hdmi capture and displays this message, also
takes upt to 5 minutes to boot, i tried on windows and works well, if i
unplug it, boot normally

This is the message..

usb 11-1: Failed to query (GET_DEF) UVC control 11 on unit 1: -32 (exp.
2).

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-lowlatency 5.13.0.39.48
ProcVersionSignature: Ubuntu 5.13.0-39.44-lowlatency 5.13.19
Uname: Linux 5.13.0-39-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  cjdg   4203 F pulseaudio
 /dev/snd/controlC2:  cjdg   4203 F pulseaudio
 /dev/snd/controlC1:  cjdg   4203 F pulseaudio
 /dev/snd/controlC0:  cjdg   4203 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Mar 30 16:54:18 2022
HibernationDevice: RESUME=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 
resume_offset=34816
InstallationDate: Installed on 2021-04-29 (335 days ago)
InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
MachineType: Gigabyte Technology Co., Ltd. GA-970A-UD3
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-lowlatency 
root=UUID=5bf8e992-a5cc-4b4b-b331-69111d42c8f3 ro threadirqs quiet splash 
resume=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 resume_offset=34816 
vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-39-lowlatency N/A
 linux-backports-modules-5.13.0-39-lowlatency  N/A
 linux-firmware1.201.5
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-10-14 (167 days ago)
dmi.bios.date: 10/22/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7
dmi.board.name: GA-970A-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd10/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: GA-970A-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug impish

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

Title:
  ezcap u2 card error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a ezcap u3 internal hdmi capture and displays this message,
  also takes upt to 5 minutes to boot, i tried on windows and works
  well, if i unplug it, boot normally

  This is the message..

  usb 11-1: Failed to query (GET_DEF) UVC control 11 on unit 1: -32
  (exp. 2).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-lowlatency 5.13.0.39.48
  ProcVersionSignature: Ubuntu 5.13.0-39.44-lowlatency 5.13.19
  Uname: Linux 5.13.0-39-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  cjdg   4203 F pulseaudio
   /dev/snd/controlC2:  cjdg   4203 F pulseaudio
   /dev/snd/controlC1:  cjdg   4203 F pulseaudio
   /dev/snd/controlC0:  cjdg   4203 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 16:54:18 2022
  HibernationDevice: RESUME=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 
resume_offset=34816
  InstallationDate: Installed on 2021-04-29 (335 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-UD3
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-lowlatency 
root=UUID=5bf8e992-a5cc-4b4b-b331-69111d42c8f3 ro threadirqs quiet splash 
resume=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 resume_offset=34816 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-lowlatency N/A
   linux-backports-modules-5.13.0-39-lowlatency  N/A
   linux-firmware1.201.5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-14 (167 days ago)
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-970A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd10/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-UD3:p

[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

[Jeff Lane]

This one is causing the kernel build to fail after pulling all of these
into our 5.15 tree:

1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly


Is there a missing patch in this set that perhaps sets up this one?

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

Title:
  [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04
  kernel. These patches got accepted by the upstream and please find the
  corresponding commit IDs as below:

  334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
  22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
  d44b5fefb22e scsi: mpi3mr: Fix memory leaks
  21401408ddeb scsi: mpi3mr: Update the copyright year
  999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
  b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
  191a3ef58634 scsi: mpi3mr: Fix hibernation issue
  04b27e538d50 scsi: mpi3mr: Update MPI3 headers
  6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
  580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event
  3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
  5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes
  c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0
  a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling
  c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers
  afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
  95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events
  78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event
  c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic
  c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation
  b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware
  c0b00a931e5e scsi: mpi3mr: Add IOC reinit function
  fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner
  59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2
  e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1
  a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout
  2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version
  13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds
  4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s
  ba68779a518d scsi: mpi3mr: Do access status validation before adding devices
  17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device
  ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2
  d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1
  fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status
  a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave()
  9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits
  30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf()
  97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through 
sysfs
  1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly
  76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info()
  92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI
  69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
  aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings
  62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch
  a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc()
  f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error
  2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr()
  d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check
  d3d61f9c8c2d scsi: mpi3mr: Fix a double free
  7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang
  9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints

  
  Thanks,
  Sumit

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Jeremy]

Same here. High pitched sound modulated by sine wave every 2 seconds.

48000 sampling rate doesn't work for me, either.

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

Title:
  audio from external sound card is distorted

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

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1967178] [NEW] Overlays are not loaded on boot, manual loading doesn't work either

[Skyler Mäntysaari]

Public bug reported:

No dmesg messages related to overlays, and fan doesn't spin on the PoE+
hat.

dtoverlay -v rpi-poe-plus results in:

DTOVERLAY[debug]: using platform 'bcm2711'
DTOVERLAY[debug]: overlay map loaded
run_cmd: which dtoverlay-pre >/dev/null 2>&1 && dtoverlay-pre
DTOVERLAY[debug]: loading file 'rpi-poe-plus.dtbo'
DTOVERLAY[debug]: wrote 2938 bytes to '/tmp/.dtoverlays/0_rpi-poe-plus.dtbo'
DTOVERLAY[debug]: wrote 2938 bytes to 
'/sys/kernel/config/device-tree/overlays/0_rpi-poe-plus/dtbo'
* Failed to apply overlay '0_rpi-poe-plus' (kernel)
run_cmd: which dtoverlay-post >/dev/null 2>&1 && dtoverlay-post

raspinfo:
https://gist.github.com/samip5/399886441d3345fadc869d1702f37155

Related Github thread:
https://github.com/raspberrypi/firmware/issues/1710

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-raspi 5.13.0.1022.27
ProcVersionSignature: Ubuntu 5.13.0-1022.24-raspi 5.13.19
Uname: Linux 5.13.0-1022-raspi aarch64
ApportVersion: 2.20.11-0ubuntu71
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: unknown
Date: Wed Mar 30 23:07:48 2022
ImageMediaBuild: 20220223
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 xHCI 
USB 3.0 Controller
Lsusb:
 Bus 002 Device 002: ID 0bc2:231b Seagate RSS LLC Expansion
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
 |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 BCM2708 FB
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 
smsc95xx.macaddr=E4:5F:01:1B:32:93 vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 
elevator=deadline rootwait fixrtc cgroup_enable=cpuset cgroup_enable=memory 
cgroup_memory=1 swapaccount=1
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-1022-raspi N/A
 linux-backports-modules-5.13.0-1022-raspi  N/A
 linux-firmware 1.201.5
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-raspi
StagingDrivers: bcm2835_codec snd_bcm2835 bcm2835_mmal_vchiq vc_sm_cma 
bcm2835_isp bcm2835_v4l2
UpgradeStatus: Upgraded to impish on 2022-03-26 (3 days ago)
acpidump:

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


** Tags: apport-bug arm64 arm64-image impish raspi-image staging uec-images

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

Title:
  Overlays are not loaded on boot, manual loading doesn't work either

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  No dmesg messages related to overlays, and fan doesn't spin on the
  PoE+ hat.

  dtoverlay -v rpi-poe-plus results in:

  DTOVERLAY[debug]: using platform 'bcm2711'
  DTOVERLAY[debug]: overlay map loaded
  run_cmd: which dtoverlay-pre >/dev/null 2>&1 && dtoverlay-pre
  DTOVERLAY[debug]: loading file 'rpi-poe-plus.dtbo'
  DTOVERLAY[debug]: wrote 2938 bytes to '/tmp/.dtoverlays/0_rpi-poe-plus.dtbo'
  DTOVERLAY[debug]: wrote 2938 bytes to 
'/sys/kernel/config/device-tree/overlays/0_rpi-poe-plus/dtbo'
  * Failed to apply overlay '0_rpi-poe-plus' (kernel)
  run_cmd: which dtoverlay-post >/dev/null 2>&1 && dtoverlay-post

  raspinfo:
  https://gist.github.com/samip5/399886441d3345fadc869d1702f37155

  Related Github thread:
  https://github.com/raspberrypi/firmware/issues/1710

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-raspi 5.13.0.1022.27
  ProcVersionSignature: Ubuntu 5.13.0-1022.24-raspi 5.13.19
  Uname: Linux 5.13.0-1022-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: arm64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  Date: Wed Mar 30 23:07:48 2022
  ImageMediaBuild: 20220223
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805/806 
xHCI USB 3

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

[Ubuntu SRU Bot]

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

bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.3 (amd64)
xtables-addons/unknown (ppc64el)
lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64)
dm-writeboost/unknown (arm64)


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

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

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1966997] Re: Sound glitching since kernel image 5.13.0-37

[Cristian Delgado]

Both solutions worked, changing the sample rate, and installed the
patch!

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

Title:
  Sound glitching since kernel image 5.13.0-37

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since the update of linux-image-5.13.0-37, there is a lot of audio
  glitching, using linux-image-5.13.0-35 or before doesnt has the issue,
  my sound card is a Texas Instruments PCM2900C Audio CODEC

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-lowlatency 5.13.0.39.48
  ProcVersionSignature: Ubuntu 5.13.0-39.44-lowlatency 5.13.19
  Uname: Linux 5.13.0-39-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  cjdg   4045 F pulseaudio
   /dev/snd/pcmC2D0p:   cjdg   4045 F...m pulseaudio
   /dev/snd/controlC1:  cjdg   4045 F pulseaudio
   /dev/snd/controlC0:  cjdg   4045 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Mar 29 13:21:54 2022
  HibernationDevice: RESUME=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 
resume_offset=34816
  InstallationDate: Installed on 2021-04-29 (334 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-UD3
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-lowlatency 
root=UUID=5bf8e992-a5cc-4b4b-b331-69111d42c8f3 ro quiet splash 
resume=UUID=7a2c1228-23b3-4579-90e4-ba6e209dd9d4 resume_offset=34816 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-39-lowlatency N/A
   linux-backports-modules-5.13.0-39-lowlatency  N/A
   linux-firmware1.201.5
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-14 (165 days ago)
  dmi.bios.date: 10/22/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-970A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd10/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: GA-970A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1965002] Re: AWS: Hibernate resume crashes when platform changes

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 5.4.0-1071.76

---
linux-aws (5.4.0-1071.76) focal; urgency=medium

  * focal/linux-aws: 5.4.0-1071.76 -proposed tracker (LP: #1966242)

  * AWS: Hibernate resume crashes when platform changes (LP: #1965002)
- PM: hibernate: Allow ACPI hardware signature to be honoured
- PM: hibernate: Honour ACPI hardware signature by default for virtual 
guests

  [ Ubuntu: 5.4.0-107.121 ]

  * focal/linux: 5.4.0-107.121 -proposed tracker (LP: #1966275)
  * CVE-2022-27666
- esp: Fix possible buffer overflow in ESP transformation
  * CVE-2022-1055
- net: sched: fix use-after-free in tc_new_tfilter()
  * Pick fixup from v5.4.176 upstream stable release to address cert
failure with clock jitter test in NUC7i3DNHE (LP: #1964204)
- Bluetooth: refactor malicious adv data check

 -- Tim Gardner   Mon, 28 Mar 2022 08:40:36
-0600

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

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

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

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

Title:
  AWS: Hibernate resume crashes when platform changes

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

Bug description:
  SRU Justification

  [Impact]

  At present, if a virt instance is hibernated and restarted in a
  different environment, the instance will crash. We have seen
  situations where customers have to enable support cases to recover an
  instance. The proposed patch is supposed to enable the kernel to
  detect the change and reboot the instance instead of crashing. In the
  ACPI specification; there is a 'hardware signature' field in the ACPI
  tables, and the OS can reboot cleanly if/when that signature changes,
  instead of attempting the resume and crashing.

  [Fix]
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=74d9
  
https://lore.kernel.org/lkml/9099d8903e9b2b16daec712acc9aa533fe84d102.ca...@infradead.org/T/#u

  [Test Case]

  Hibernate an AWS instance, resume on a different platform. Positive
  test results from Amazon engineers.

  [Where things could go wrong]

  Resume currently crashes when a hibernated instance is migrated to a
  new machine. It can't get much worse, unless the initial hibernate
  fails.

  [Other Info]

  SF: #00330794

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


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

[Kernel-packages] [Bug 1966147] Re: 5.13.0-37.42 terrible sound via usb

[vinz]

Hi Po-Hsu Lin,

I have installed 5.13.0-37-generic #42+lp1966066 as per steps above and
I can confirm that it fixes the issue.

Thank 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/1966147

Title:
  5.13.0-37.42 terrible sound via usb

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  updated yesterday to kernel 5.13.0-37.42 and sound from usb is awfully
  distorted, while from bluetooth and hdmi is unaltered.

  reverted to 5.13.0-35.40 via grub and sound via usb is back to normal.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  vinz   2684 F pulseaudio
   /dev/snd/controlC2:  vinz   2684 F pulseaudio
   /dev/snd/controlC1:  vinz   2684 F pulseaudio
   /dev/snd/controlC0:  vinz   2684 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2020-10-24 (518 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic 
root=UUID=fcdf975b-fa37-4978-8a4b-e452f2f74512 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-37-generic N/A
   linux-backports-modules-5.13.0-37-generic  N/A
   linux-firmware 1.201.5
  Tags:  impish
  Uname: Linux 5.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-01-27 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F30
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS ULTRA
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS ULTRA
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Kernel-packages] [Bug 1965618] Re: linux-azure: Focal 5.4 arm64 support

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2022-March/128987.html

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

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

Title:
  linux-azure: Focal 5.4 arm64 support

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

Bug description:
  SRU Justification

  [Impact]

  Focal linux-azure does not support arm64

  [Fix]

  Backport/cherry-pick approximately 100 patches to support arm64 on
  hyperv

  [Where things could go wrong]

  A number of the patches reorganize hyperv CPU support. Therefore amd64
  could be affected.

  [Other Info]

  SF: #00310705

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


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

[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules/4.15.0-176.185)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted linux-restricted-modules 
(4.15.0-176.185) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-450-server/450.172.01-0ubuntu0.18.04.1 (amd64)
nvidia-graphics-drivers-470/470.103.01-0ubuntu0.18.04.1 (amd64)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#linux-restricted-modules

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

Thank you!

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

Title:
  Packaging resync

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

Bug description:
  Ongoing packing resyncs.

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


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

[Kernel-packages] [Bug 1967166] Re: Azure: not enough RAM under 4GB for CVM

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2022-March/129045.html

** Tags added: bot-stop-nagging

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

Title:
  Azure: not enough RAM under 4GB for CVM

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

Bug description:
  SRU Justification

  [Impact]
  Can you please include one more patchset for the "no enough RAM under 4GB" 
issue for the v5.13 kernel (and v5.15 kernel):
  https://lwn.net/ml/linux-kernel/20220209122302.213882-2-ltyker...@gmail.com/
  https://lwn.net/ml/linux-kernel/20220209122302.213882-3-ltyker...@gmail.com/

  Without the two patches, currently the 5.13 kernel (and 5.15 kernel)
  can't boot as a CVM guest on Azure. :-(

  The background is: currently an Azure host only provides about 900 MB
  memory below the 4GB boundary while the swiotlb code (which is
  required by the CVM patchset) needs to allocate memory of a size of
  MIN(1GB, 6% of the total memory). There will be an Azure host update,
  with which the host will provide about 3GB memory below the 4GB
  boundary, but we still need to wait a few more weeks to know the ETA.
  Currently the above two patches can work around the issue from the
  guest side.

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  These patches could affect non-CVM instances.

  [Other Info]

  SF: #00323683

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


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

[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

[Jeff Lane]

Linux Next
334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
d44b5fefb22e scsi: mpi3mr: Fix memory leaks
21401408ddeb scsi: mpi3mr: Update the copyright year
999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
191a3ef58634 scsi: mpi3mr: Fix hibernation issue
04b27e538d50 scsi: mpi3mr: Update MPI3 headers
6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event

5.17 Mainline
3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes
c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0
a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling
c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers
afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events
78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event
c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic
c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation
b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware
c0b00a931e5e scsi: mpi3mr: Add IOC reinit function
fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner
59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2
e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1
a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout
2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version
13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds
4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s
ba68779a518d scsi: mpi3mr: Do access status validation before adding devices
17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device
ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2
d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1
fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status
a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave()
9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits

5.16 Mainline
30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf()
1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly
76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info()

Ubuntu-5.15.0 - no need to pull
97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through 
sysfs
92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI
69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings
62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch
a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc()
f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error
2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr()
d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check
d3d61f9c8c2d scsi: mpi3mr: Fix a double free
7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang
9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints

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

Title:
  [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04
  kernel. These patches got accepted by the upstream and please find the
  corresponding commit IDs as below:

  334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
  22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
  d44b5fefb22e scsi: mpi3mr: Fix memory leaks
  21401408ddeb scsi: mpi3mr: Update the copyright year
  999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
  b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
  191a3ef58634 scsi: mpi3mr: Fix hibernation issue
  04b27e538d50 scsi: mpi3mr: Update MPI3 headers
  6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
  580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event
  3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
  5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes
  c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0
  a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling
  c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers
  afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
  95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events
  78b76a0768ef scsi: mpi3mr: Support Prepare for Res

[Kernel-packages] [Bug 1966671] Re: package linux-firmware 1.187.26 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal

[Marc Deslauriers]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package linux-firmware 1.187.26 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting a removal

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Remove this package is not possible.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.26
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  sirenux1758 F pulseaudio
   /dev/snd/controlC2:  sirenux1758 F pulseaudio
   /dev/snd/controlC1:  sirenux1758 F pulseaudio
   /dev/snd/controlC0:  sirenux1758 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Mar 28 12:37:44 2022
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.187.26
   Removing linux-image-generic-hwe-20.04 (5.13.0.30.33~20.04.17) ...
   dpkg: error processing package linux-firmware (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2022-01-19 (67 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IwConfig:
   lono wireless extensions.
   
   enp27s0   no wireless extensions.
  MachineType: Micro-Star International Co., Ltd MS-7B07
  PackageArchitecture: all
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic 
root=UUID=c0e47fc1-d36a-4d49-a7fb-c934c673b142 ro quiet splash vt.handoff=7
  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.26 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting a 
removal
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2018
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A320M PRO-VH PLUS (MS-7B07)
  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:bvnAmericanMegatrendsInc.:bvr3.C0:bd11/06/2018:br5.13:svnMicro-StarInternationalCo.,Ltd:pnMS-7B07:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VHPLUS(MS-7B07):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B07
  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/1966671/+subscriptions


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

[Kernel-packages] [Bug 1967166] [NEW] Azure: not enough RAM under 4GB for CVM

[Tim Gardner]

Public bug reported:

SRU Justification

[Impact]
Can you please include one more patchset for the "no enough RAM under 4GB" 
issue for the v5.13 kernel (and v5.15 kernel):
https://lwn.net/ml/linux-kernel/20220209122302.213882-2-ltyker...@gmail.com/
https://lwn.net/ml/linux-kernel/20220209122302.213882-3-ltyker...@gmail.com/

Without the two patches, currently the 5.13 kernel (and 5.15 kernel)
can't boot as a CVM guest on Azure. :-(

The background is: currently an Azure host only provides about 900 MB
memory below the 4GB boundary while the swiotlb code (which is required
by the CVM patchset) needs to allocate memory of a size of MIN(1GB, 6%
of the total memory). There will be an Azure host update, with which the
host will provide about 3GB memory below the 4GB boundary, but we still
need to wait a few more weeks to know the ETA. Currently the above two
patches can work around the issue from the guest side.

[Test Case]

Microsoft tested

[Where things could go wrong]

These patches could affect non-CVM instances.

[Other Info]

SF: #00323683

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

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

** Affects: linux-azure (Ubuntu Jammy)
 Importance: Undecided
 Status: Fix Committed

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

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

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

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

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

** Changed in: linux-azure (Ubuntu Impish)
 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/1967166

Title:
  Azure: not enough RAM under 4GB for CVM

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

Bug description:
  SRU Justification

  [Impact]
  Can you please include one more patchset for the "no enough RAM under 4GB" 
issue for the v5.13 kernel (and v5.15 kernel):
  https://lwn.net/ml/linux-kernel/20220209122302.213882-2-ltyker...@gmail.com/
  https://lwn.net/ml/linux-kernel/20220209122302.213882-3-ltyker...@gmail.com/

  Without the two patches, currently the 5.13 kernel (and 5.15 kernel)
  can't boot as a CVM guest on Azure. :-(

  The background is: currently an Azure host only provides about 900 MB
  memory below the 4GB boundary while the swiotlb code (which is
  required by the CVM patchset) needs to allocate memory of a size of
  MIN(1GB, 6% of the total memory). There will be an Azure host update,
  with which the host will provide about 3GB memory below the 4GB
  boundary, but we still need to wait a few more weeks to know the ETA.
  Currently the above two patches can work around the issue from the
  guest side.

  [Test Case]

  Microsoft tested

  [Where things could go wrong]

  These patches could affect non-CVM instances.

  [Other Info]

  SF: #00323683

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


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

[Kernel-packages] [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

[Jeff Lane]

** Tags added: servcert-230

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

Title:
  [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04
  kernel. These patches got accepted by the upstream and please find the
  corresponding commit IDs as below:

  334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
  22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
  d44b5fefb22e scsi: mpi3mr: Fix memory leaks
  21401408ddeb scsi: mpi3mr: Update the copyright year
  999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
  b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
  191a3ef58634 scsi: mpi3mr: Fix hibernation issue
  04b27e538d50 scsi: mpi3mr: Update MPI3 headers
  6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
  580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event
  3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
  5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes
  c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0
  a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling
  c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers
  afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
  95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events
  78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event
  c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic
  c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation
  b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware
  c0b00a931e5e scsi: mpi3mr: Add IOC reinit function
  fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner
  59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2
  e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1
  a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout
  2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version
  13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds
  4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s
  ba68779a518d scsi: mpi3mr: Do access status validation before adding devices
  17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device
  ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2
  d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1
  fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status
  a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave()
  9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits
  30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf()
  97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through 
sysfs
  1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly
  76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info()
  92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI
  69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
  aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings
  62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch
  a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc()
  f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error
  2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr()
  d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check
  d3d61f9c8c2d scsi: mpi3mr: Fix a double free
  7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang
  9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints

  
  Thanks,
  Sumit

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


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

[Kernel-packages] [Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp

[Lexi Haley]

(The change to 'confirmed' because it 'affects multiple users' is
misleading; Because I didn't submit this, and am now being effectively
"double counted", perhaps I should remove myself as 'an affected
user'

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

Title:
  Enable CONFIG_UNICODE for linux-gcp

Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Focal:
  Confirmed

Bug description:
  See https://lists.ubuntu.com/archives/kernel-
  team/2022-March/128565.html

  NOTE: This config is enabled in other gcp kernels and in non-gcp
  kernels.

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


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

[Kernel-packages] [Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp

[Launchpad Bug Tracker]

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

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

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

Title:
  Enable CONFIG_UNICODE for linux-gcp

Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Focal:
  Confirmed

Bug description:
  See https://lists.ubuntu.com/archives/kernel-
  team/2022-March/128565.html

  NOTE: This config is enabled in other gcp kernels and in non-gcp
  kernels.

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


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

[Kernel-packages] [Bug 1964527] Re: Enable CONFIG_UNICODE for linux-gcp

[Launchpad Bug Tracker]

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

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

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

Title:
  Enable CONFIG_UNICODE for linux-gcp

Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Focal:
  Confirmed

Bug description:
  See https://lists.ubuntu.com/archives/kernel-
  team/2022-March/128565.html

  NOTE: This config is enabled in other gcp kernels and in non-gcp
  kernels.

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


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

[Kernel-packages] [Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-impish

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

Title:
  audit: improve audit queue handling when "audit=1" on cmdline

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

Bug description:
  SRU Justification

  [Impact]
  When an admin enables audit at early boot via the "audit=1" kernel
  command line the audit queue behavior is slightly different; the
  audit subsystem goes to greater lengths to avoid dropping records,
  which unfortunately can result in problems when the audit daemon is
  forcibly stopped for an extended period of time.

  [Fix]
  upstream discussion:
  
https://lore.kernel.org/all/cahc9vhqgx070poxzk_pusawgzppdqvpezvfybse2dnryrbw...@mail.gmail.com/T/
  upstream commit:
  f26d04331360d42dbd6b58448bd98e4edbfbe1c5

  [Test]
  configurations:
  auditctl -b 64
  auditctl --backlog_wait_time 6
  auditctl -r 0
  auditctl -w /root/aaa  -p wrx
  shell scripts：
  #!/bin/bash
  i=0
  while [ $i -le 66 ]
  do
  touch /root/aaa
let i++
  done
  mandatory conditions:
  add "audit=1" to the cmdline, and kill -19 pid_number(for /sbin/auditd).

  As long as we keep the audit_hold_queue non-empty, flush the hold
  queue will fall into an infinite loop.

  This could also trigger soft lockup when it drops into a infinite loop, e.g.
  kernel: [   94.186433] watchdog: BUG: soft lockup - CPU#2 stuck for 11s! 
[kauditd:34]
  kernel: [   94.187736] Modules linked in: xfs iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_
  conntrack libcrc32c iptable_filter isofs xt_cgroup xt_tcpudp iptable_mangle 
ip_tables x_tables sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc aesni_intel aes_x86_64 pp
  dev crypto_simd glue_helper joydev vmwgfx ttm cryptd vmw_balloon 
drm_kms_helper intel_rapl_perf input_leds psmouse drm fb_sys_fops syscopyarea 
vmxnet3 sysfillrect parport_pc parport m
  ac_hid shpchp i2c_piix4 vmw_vsock_vmci_transport vsock sysimgblt vmw_vmci 
serio_raw mptspi mptscsih mptbase scsi_transport_spi pata_acpi floppy autofs4
  kernel: [   94.187757] CPU: 2 PID: 34 Comm: kauditd Not tainted 
4.15.0-171-generic #180~16.04.1-Ubuntu
  kernel: [   94.187757] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS
   6.00 11/12/2020
  kernel: [   94.187800]  skb_queue_head+0x47/0x50
  kernel: [   94.187803]  kauditd_rehold_skb+0x18/0x20
  kernel: [   94.187805]  kauditd_send_queue+0xcd/0x100
  kernel: [   94.187806]  ? kauditd_retry_skb+0x20/0x20
  kernel: [   94.187808]  ? kauditd_send_multicast_skb+0x80/0x80
  kernel: [   94.187809]  kauditd_thread+0xa7/0x240
  kernel: [   94.187812]  ? wait_woken+0x80/0x80
  kernel: [   94.187815]  kthread+0x105/0x140
  kernel: [   94.187817]  ? auditd_reset+0x90/0x90
  kernel: [   94.187818]  ? kthread_bind+0x40/0x40
  kernel: [   94.187820]  ret_from_fork+0x35/0x40

  [Other Info]
  SF: #00330803

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


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

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

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2022-03-30 11:40 EDT---
With the fix being available for focal, impish and jammy, we can close the bug.
Changing IBM BZ status to: ==> CLOSED

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

Title:
  [UBUNTU 21.10] s390/cio: verify the driver availability for path_event
  call

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  Description:   s390/cio: verify the driver availability for path_event call
  Symptom:   If no driver is attached to a device or the driver does not
 provide the path_event function, an FCES path-event on this
 device could end up in a kernel-panic.
  Problem:   There can be path-event generated for devices which are not
 bound to any drivers. And this is not verified before 
callback. 
  Solution:  Make sure the driver is available before the callback.
  Reproduction:  -
  Upstream-ID:   dd9cb842fa9d90653a9b48aba52f89c069f3bc50
  Problem-ID:196414
  Distros:   Ubuntu 21.10 and higher
  Preventive:yes
  Reported:  -
  SupportTicket: -
  Reference: -
  Date:  2022-02-14
  Author:Vineeth Vijayan 
  Component: kernel

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


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

[Kernel-packages] [Bug 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"

[EdwardO]

Thanks for the support.

Indeed pipewire is part of the issue. Although installing kubuntu-
desktop does not force pipewire (according to
https://packages.ubuntu.com/jammy/kubuntu-desktop ), I may have enabled
it wrongly while getting Wayland screensharing to work with the
following:

sudo apt install xdg-desktop-portal-gnome gnome-remote-desktop  #
installs pipewire

systemctl --user enable pipewire-media-session
systemctl --user start pipewire-media-session
systemctl --user restart xdg-desktop-portal-gnome

This must have been what caused audio to break
(aside - I'd be happy to know the supported steps for xdg-portal sharing when 
upgrading to 22.04)

Thanks to your pointer I managed to fix it:
* recover the (wired) audio by installing wireplumber: this fixed half-setup 
pipewire situation.
* fix bluetooth by installing libspa-0.2-bluetooth (and restart bluetooth & 
wireplumber)
(see 
https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1826833.html)
So, closing this, and if it is considered an unsupported solution, sorry for 
taking your time!

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

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

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

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

Title:
  Bluetooth fails to connect "br-connection-profile-unavailable"

Status in bluez package in Ubuntu:
  Invalid
Status in pipewire package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  How to reproduce:

  > bluetoothctl scan on
  Discovery started
  ...
  > bluetoothctl connect 94:DB:56:8E:0B:96
  Attempting to connect to 94:DB:56:8E:0B:96
  Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable

  > systemctl status bluetooth
  bluetooth.service - Bluetooth service
   Loaded: loaded
  ...
  mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: 
src/service.c:btd_service_connect() a2dp-sink profile connect failed for 
94:DB:56:8E:0B:96: Protocol not available

  Notes:
  kernel-5.15, bluez-5.64
  Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
  Dell Precision 3560
  Unfortunately I did not test before upgrade to 22.04.
  Tried installing pipewire-pulse, blueman, but this is lower-level.
  There are reports of similar errors popping up in Arch and Manjaro recently:
  https://bbs.archlinux.org/viewtopic.php?id=270465
  https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Mar 25 12:56:34 2022
  InstallationDate: Installed on 2022-03-04 (21 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Precision 3560
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES 
nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago)
  dmi.bios.date: 09/13/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.2
  dmi.board.name: 095HH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22:
  dmi.product.family: Precision
  dmi.product.name: Precision 3560
  dmi.product.sku: 0A22
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 44:E5:17:BC:00:DD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:24189 acl:41 sco:0 events:519 errors:0
TX bytes:8252 acl:33 sco:0 commands:239 errors:0
  modified.conffile..etc.cron.daily.apport: [deleted]

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


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

[Kernel-packages] [Bug 1964983] Re: IPU6 camera has no function on Andrews MLK

[You-Sheng Yang]

SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-March/129032.html (oem-5.14, jammy)

** Description changed:

+ [SRU Justification]
+ 
+ [Impact]
+ 
+ New Andrews MLK equips yet another new I2C sensor and takes a few
+ driver updates to function normally.
+ 
+ [Fix]
+ 
+ Upstream driver commit:
+ 
https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e
+ 
+ [Test Case]
+ 
+ To verify by following steps:
+ 
+   1. disable secure boot
+   2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
+   3. $ sudo add-apt-repository ppa:kchsieh/ipu6
+   4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer
+   6. $ sudo apt install libipu6ep
+   7. $ sudo apt install libcamhal-ipu6ep-common
+   8. $ sudo apt install libcamhal-ipu6ep0
+   9. $ sudo apt install libgsticamerainterface-1.0-1
+  10. $ sudo apt install gstreamer1.0-icamera
+  11. $ sudo vim /etc/v4l2-relayd
+ -FORMAT=YUY2
+ +FORMAT=NV12
+  12. $ sudo reboot
+ 
+ [Where problems could occur]
+ 
+ Intel IPU6 platform is still under development and is not capable of
+ advanced power management features and may still suffer from stability
+ issues.
+ 
+ [Other Info]
+ 
+ Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and
+ will depend on previous SRU proposal in bug 1955383
+ (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html).
+ Nomination for generic-5.17 and oem-5.17 is still under planning.
+ 
+ == original bug description ==
+ 
  The new platform uses yet another ov sensor OV02C10.
  
  Prerequisites:
  * kernel fix: 
https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e
  * ipu6-camera-bins: 
https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc
  * ipu6-camera-hal: 
https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe
  * icamerasrc: 
https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932

** Changed in: linux-oem-5.17 (Ubuntu Jammy)
   Status: In Progress => Confirmed

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

Title:
  IPU6 camera has no function on Andrews MLK

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

Bug description:
  [SRU Justification]

  [Impact]

  New Andrews MLK equips yet another new I2C sensor and takes a few
  driver updates to function normally.

  [Fix]

  Upstream driver commit:
  
https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e

  [Test Case]

  To verify by following steps:

1. disable secure boot
2. $ sudo add-apt-repository ppa:canonical-hwe-team/intermediate-kernel
3. $ sudo add-apt-repository ppa:kchsieh/ipu6
4. $ sudo apt install linux-oem-5.14 version 5.14.0-9029-oem or newer
6. $ sudo apt install libipu6ep
7. $ sudo apt install libcamhal-ipu6ep-common
8. $ sudo apt install libcamhal-ipu6ep0
9. $ sudo apt install libgsticamerainterface-1.0-1
   10. $ sudo apt install gstreamer1.0-icamera
   11. $ sudo vim /etc/v4l2-relayd
  -FORMAT=YUY2
  +FORMAT=NV12
   12. $ sudo reboot

  [Where problems could occur]

  Intel IPU6 platform is still under development and is not capable of
  advanced power management features and may still suffer from stability
  issues.

  [Other Info]

  Nomination for 5.15 is necessary for oem-5.14 to hwe-5.15 migration and
  will depend on previous SRU proposal in bug 1955383
  (https://lists.ubuntu.com/archives/kernel-team/2022-March/128922.html).
  Nomination for generic-5.17 and oem-5.17 is still under planning.

  == original bug description ==

  The new platform uses yet another ov sensor OV02C10.

  Prerequisites:
  * kernel fix: 
https://github.com/intel/ipu6-drivers/commit/778819bef3d8ac8d6b24342372e006b7b43e381e
  * ipu6-camera-bins: 
https://github.com/intel/ipu6-camera-bins/commit/7cc1dc2d9ab2b0766e034edf808d751bd25b42cc
  * ipu6-camera-hal: 
https://github.com/intel/ipu6-camera-hal/commit/b9b56de11de70b7c4520595176e4831bacf4a7fe
  * icamerasrc: 
https://github.com/intel/icamerasrc/commit/a35978264002acaad72bb9956238ccaef3743932

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


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

[Kernel-packages] [Bug 1966969] Re: linux-aws: Xen: Issues with detaching volume

[Tim Gardner]

Patches submitted: https://lists.ubuntu.com/archives/kernel-
team/2022-March/129029.html

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

Title:
  linux-aws: Xen: Issues with detaching volume

Status in linux-aws package in Ubuntu:
  New

Bug description:
  SRU Justification

  [Impact]

  We are observing issue with the secondary volume stuck in detaching. This is 
observed with the latest Canonical, Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, 
amd64 focal image build on 2022-03-08 and Xen instance type( for eg : m4, t2 
instance type )
  AMI in eu-west-1 : ami-0f4ffbcba23a6c434
  AMI in us-east-1 : ami-021feb4aa3b3c59c3

  When terminating an instance with a stuck volume the shutdown process is 
interrupted by a xen task hanging:
  [ 847.895334] INFO: task xenwatch:188 blocked for more than 483 seconds.
  [ 847.901573] Not tainted 5.13.0-1017-aws #19~20.04.1-Ubuntu
  [ 847.907144] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 847.914462] task:xenwatch state:D stack: 0 pid: 188 ppid: 2 flags:0x4000
  [ 847.914467] Call Trace:
  [ 847.914469] 
  [ 847.914472] __schedule+0x2ee/0x900
  [ 847.914478] schedule+0x4f/0xc0
  [ 847.914479] schedule_preempt_disabled+0xe/0x10
  [ 847.914482] __mutex_lock.isra.0+0x183/0x4d0
  [ 847.914486] __mutex_lock_slowpath+0x13/0x20
  [ 847.914487] mutex_lock+0x32/0x40
  [ 847.914489] del_gendisk+0x90/0x200
  [ 847.914493] xlvbd_release_gendisk+0x72/0xc0
  [ 847.914499] blkback_changed+0x101/0x210
  [ 847.914502] xenbus_otherend_changed+0x8f/0x130
  [ 847.914507] backend_changed+0x13/0x20
  [ 847.914510] xenwatch_thread+0xa6/0x180
  [ 847.914513] ? wait_woken+0x80/0x80
  [ 847.914517] ? test_reply.isra.0+0x40/0x40
  [ 847.914520] kthread+0x12b/0x150
  [ 847.914523] ? set_kthread_struct+0x40/0x40
  [ 847.914525] ret_from_fork+0x22/0x30
  [ 847.914531] 

  this looks like it's waiting on a xen block device to be released.

  Following steps used to reproduce the issue:
  * Created a m4,t2(xen) instance with the latest ami for latest Canonical, 
Ubuntu EKS Node OS (k8s_1.19), 20.04 LTS, amd64
  * Created a filesystem on volume
  * Mounted volume through OS
  * Unmounted volume in OS
  * Detached volume from AWS console
  * Volume gets stuck.

  We at the internal team observed this commit upstream:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05d69d950d9d84218fc9beafd02dea1f6a70e09e

  [...] and a del_gendisk from the block device release
  method, which will deadlock.

  It has a Fixes: tag referring to a commit from 5.13 so this could be
  the root-cause. While testing, we observed this commit is fixing the
  issue.

  [Test Plan]

  Amazon tested

  [Where things could go wrong]

  Detaching volumes could fail in new and bizarre ways

  [Other Info]

  SF: #00331175

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


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

[Kernel-packages] [Bug 1967131] Re: CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic

[Nobuto Murata]

Thank you Stefan for the prompt response. I'm marking this as Invalid
for the time being assuming the value was intended.

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

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

Title:
  CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic

Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  -kvm flavor has CONFIG_NR_CPUS=64 although -generic has
  CONFIG_NR_CPUS=8192 these days.

  It will be a problem especially when launching a VM on top of a
  hypervisor with more than 64 CPU threads available. Then the guest can
  only use up to 64 vCPUs even when more vCPUs are allocated by a
  hypervisor.

  I've checked the latest available package for Jammy, but there was no change 
around CONFIG_NR_CPUS.
  https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3

  $ lsb_release -r
  Release:20.04

  $ dpkg -S /boot/config*
  linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic
  linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm

  $ grep CONFIG_NR_CPUS /boot/config*
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64

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


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

[Kernel-packages] [Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline

[Ubuntu Kernel Bot]

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

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

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


** Tags added: verification-needed-bionic

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

Title:
  audit: improve audit queue handling when "audit=1" on cmdline

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

Bug description:
  SRU Justification

  [Impact]
  When an admin enables audit at early boot via the "audit=1" kernel
  command line the audit queue behavior is slightly different; the
  audit subsystem goes to greater lengths to avoid dropping records,
  which unfortunately can result in problems when the audit daemon is
  forcibly stopped for an extended period of time.

  [Fix]
  upstream discussion:
  
https://lore.kernel.org/all/cahc9vhqgx070poxzk_pusawgzppdqvpezvfybse2dnryrbw...@mail.gmail.com/T/
  upstream commit:
  f26d04331360d42dbd6b58448bd98e4edbfbe1c5

  [Test]
  configurations:
  auditctl -b 64
  auditctl --backlog_wait_time 6
  auditctl -r 0
  auditctl -w /root/aaa  -p wrx
  shell scripts：
  #!/bin/bash
  i=0
  while [ $i -le 66 ]
  do
  touch /root/aaa
let i++
  done
  mandatory conditions:
  add "audit=1" to the cmdline, and kill -19 pid_number(for /sbin/auditd).

  As long as we keep the audit_hold_queue non-empty, flush the hold
  queue will fall into an infinite loop.

  This could also trigger soft lockup when it drops into a infinite loop, e.g.
  kernel: [   94.186433] watchdog: BUG: soft lockup - CPU#2 stuck for 11s! 
[kauditd:34]
  kernel: [   94.187736] Modules linked in: xfs iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_
  conntrack libcrc32c iptable_filter isofs xt_cgroup xt_tcpudp iptable_mangle 
ip_tables x_tables sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc aesni_intel aes_x86_64 pp
  dev crypto_simd glue_helper joydev vmwgfx ttm cryptd vmw_balloon 
drm_kms_helper intel_rapl_perf input_leds psmouse drm fb_sys_fops syscopyarea 
vmxnet3 sysfillrect parport_pc parport m
  ac_hid shpchp i2c_piix4 vmw_vsock_vmci_transport vsock sysimgblt vmw_vmci 
serio_raw mptspi mptscsih mptbase scsi_transport_spi pata_acpi floppy autofs4
  kernel: [   94.187757] CPU: 2 PID: 34 Comm: kauditd Not tainted 
4.15.0-171-generic #180~16.04.1-Ubuntu
  kernel: [   94.187757] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS
   6.00 11/12/2020
  kernel: [   94.187800]  skb_queue_head+0x47/0x50
  kernel: [   94.187803]  kauditd_rehold_skb+0x18/0x20
  kernel: [   94.187805]  kauditd_send_queue+0xcd/0x100
  kernel: [   94.187806]  ? kauditd_retry_skb+0x20/0x20
  kernel: [   94.187808]  ? kauditd_send_multicast_skb+0x80/0x80
  kernel: [   94.187809]  kauditd_thread+0xa7/0x240
  kernel: [   94.187812]  ? wait_woken+0x80/0x80
  kernel: [   94.187815]  kthread+0x105/0x140
  kernel: [   94.187817]  ? auditd_reset+0x90/0x90
  kernel: [   94.187818]  ? kthread_bind+0x40/0x40
  kernel: [   94.187820]  ret_from_fork+0x35/0x40

  [Other Info]
  SF: #00330803

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


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

[Kernel-packages] [Bug 1967141] Re: [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)

[Frank Heimes]

** Also affects: ubuntu-z-systems
   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/1967141

Title:
  [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps
  core (openssl-ibmca)

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Summary
  ===

  New IBM HW with Crypto Accelerator cards attached
  Kernel level: 5.14 
  Core dump when configuring the ibmca engine with libica = libica.so.4 in the 
openssl.cnf file in the engine section.
  The problem only occurs with OpenSSL 3.0 and is immediately reproducible.

  
  Details
  ===
  HINT: To be able to receive core dump files at all it is needed to change the 
/etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read
DefaultLimitCORE=infinity:infinity

  On a system with ibmca engine configured system wide, when trying to
  use the libica.so.4 to support the ibmca engine the sshd daemon dumps
  core upon the first login attempt.

  # openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
   [RSA, DSA, DH]

  
  Debug Data
  ==
  core dump file in the attachments.
   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.14.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Edit /etc/systemd/system.conf file to allow core dumps:
  Change the line DefaultLimitCORE=0:infinity
  to read DefaultLimitCORE=infinity:infinity
  2.) run: systemctl daemon-reload
   systemctl restart systemd-coredump.socket
  3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl 
script
  4.) Edit the /etc/pki/tls file near the end to contain the line
  to back the ibmca engine by the libica.so.4 library as outlined in the
  /usr/share/doc/openssl-ibmca/README.md file
  5.) Run: openssl engine -c
  6.) Keep the current session open for subsequently stepping back to the
  original openssl.cnf!
  7.) Open up a new ssh session to the system under test
  and watch the login to fail with broken pipe
  8.) On the remaining session, run
  coreumpctl list / coredumpctl dump
   
  Userspace tool common name: openssl-ibmca 

  Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace tool obtained from project website:  na

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


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

[Kernel-packages] [Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering

[dann frazier]

Amir, I've prepared a test build with that additional commit added. Can
you run it through your test suite and report back? The kernel team will
take that testing into account to determine whether or not a kernel
feature freeze exception can be granted.

sudo apt-add-repository ppa:dannf/lp1966194
sudo apt install linux-modules-extra-5.15.0-23.23-generic

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

Title:
  [Jammy, mlx5, ConnectX-7] add CX7 support for software steering

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  Add support for software steering on cx7

  [Test Case]
  configure software steering on cx7 setup
  run asap testing 
  (reference https://github.com/Mellanox/ovs-tests)
   

  [Regression Potential]
  TBD

  [Other Info]

  Feature patchset: 
  All patches are cleanly applied on Jamy master-next beside 
  these two who add minor conflicts due to context difference.
  net/mlx5: Introduce software defined steering capabilities
  net/mlx5: DR, Add support for matching on
   

  #fixes
  624bf42c2e39 net/mlx5: DR, Fix querying eswitch manager vport for ECPF
  0aec12d97b20 net/mlx5: DR, Fix slab-out-of-bounds in mlx5_cmd_dr_create_fte
  9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately

  
  #CX7 SMFS support
  6862c787c7e8 net/mlx5: DR, Add support for ConnectX-7 steering
  638a07f1090e net/mlx5: DR, Refactor ste_ctx handling for STE v0/1
  75a3926ca6a4 net/mlx5: DR, Rename action modify fields to reflect naming in 
HW spec
  bdc3ab5795a6 net/mlx5: DR, Fix handling of different actions on the same STE 
in STEv1
  11659ef8d28e net/mlx5: DR, Remove unneeded comments
  5c422bfad2fb net/mlx5: DR, Add support for matching on Internet Header Length 
(IHL)

  
  #dependencies:
  60dc0ef674ec net/mlx5: VLAN push on RX, pop on TX
  8348b71ccd92 net/mlx5: Introduce software defined steering capabilities

  #depencecies:
  #SW STEERING DEBUG DUMP
  aa36c94853b2 net/mlx5: Set SMFS as a default steering mode if device supports 
it
  4ff725e1d4ad net/mlx5: DR, Ignore modify TTL if device doesn't support it
  cc2295cd54e4 net/mlx5: DR, Improve steering for empty or RX/TX-only matchers
  f59464e257bd net/mlx5: DR, Add support for matching on 
geneve_tlv_option_0_exist field
  09753babaf46 net/mlx5: DR, Support matching on tunnel headers 0 and 1
  8c2b4fee9c4b net/mlx5: DR, Add misc5 to match_param structs
  0f2a6c3b9219 net/mlx5: Add misc5 flow table match parameters
  b54128275ef8 net/mlx5: DR, Warn on failure to destroy objects due to refcount
  e3a0f40b2f90 net/mlx5: DR, Add support for UPLINK destination type
  9222f0b27da2 net/mlx5: DR, Add support for dumping steering info
  7766c9b922fe net/mlx5: DR, Add missing reserved fields to dr_match_param
  89cdba3224f0 net/mlx5: DR, Add check for flex parser ID value
  08fac109f7bb net/mlx5: DR, Rename list field in matcher struct to list_node
  32e9bd585307 net/mlx5: DR, Remove unused struct member in matcher
  c3fb0e280b4c net/mlx5: DR, Fix lower case macro prefix "mlx5_" to "MLX5_"
  84dfac39c61f net/mlx5: DR, Fix error flow in creating matcher

  
  58a606dba708 net/mlx5: Introduce new uplink destination type

  455832d49666 net/mlx5: DR, Fix check for unsupported fields in match param
  9091b821aaa4 net/mlx5: DR, Handle eswitch manager and uplink vports separately

  #SW STEERING SF
  515ce2ffa621 net/mlx5: DR, init_next_match only if needed
  5dde00a73048 net/mlx5: DR, Fix typo 'offeset' to 'offset'
  1ffd498901c1 net/mlx5: DR, Increase supported num of actions to 32
  11a45def2e19 net/mlx5: DR, Add support for SF vports
  c0e90fc2ccaa net/mlx5: DR, Support csum recalculation flow table on SFs
  ee1887fb7cdd net/mlx5: DR, Align error messages for failure to obtain vport 
caps
  dd4acb2a0954 net/mlx5: DR, Add missing query for vport 0
  7ae8ac9a5820 net/mlx5: DR, Replace local WIRE_PORT macro with the existing 
MLX5_VPORT_UPLINK
  f9f93bd55ca6 net/mlx5: DR, Fix vport number data type to u16
  c228dce26222 net/mlx5: DR, Fix code indentation in dr_ste_v1

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


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

[Kernel-packages] [Bug 1967131] Re: CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic

[Stefan Bader]

Naming this derivative kernel "kvm" was not the best idea in hindsight.
It was done to achieve fast booting guest images. Towards that goal
everything was streamlined and part of that is keeping per-cpu
structures smaller by limiting the number of CPUs.

The generic kernel (which should be installed via the linux-generic
meta-package) can run as a VM guest but for that has the downside of
pulling in some bigger dependent packages (linux-firmware, crda, linux-
modules-extra, ...). To avoid that there is the linux-virtual meta-
package which will only pull in the kernel and a sub-set of kernel
modules (without linux-modules-extra) and the other dependencies. That
reduces its on-disk footprint.

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

Title:
  CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  -kvm flavor has CONFIG_NR_CPUS=64 although -generic has
  CONFIG_NR_CPUS=8192 these days.

  It will be a problem especially when launching a VM on top of a
  hypervisor with more than 64 CPU threads available. Then the guest can
  only use up to 64 vCPUs even when more vCPUs are allocated by a
  hypervisor.

  I've checked the latest available package for Jammy, but there was no change 
around CONFIG_NR_CPUS.
  https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3

  $ lsb_release -r
  Release:20.04

  $ dpkg -S /boot/config*
  linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic
  linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm

  $ grep CONFIG_NR_CPUS /boot/config*
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64

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


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

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

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2022-03-30 10:26 EDT---
This problem has been fixed with with openssl-ibmca 2.2.3:

* openssl-ibmca 2.2.3
- Fix PKEY segfault with OpenSSL 3.0

This 2.2.3 release has been made specifically to fix this bug, so you can 
choose between the following commit
https://github.com/opencryptoki/openssl-ibmca/commit/93a12d3f3d401247c13ea3f4f47dc3d10fbb6f7b

or a package upgrade to 2.2.3 to fix this.

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

Title:
  [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps
  core (openssl-ibmca)

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Summary
  ===

  New IBM HW with Crypto Accelerator cards attached
  Kernel level: 5.14 
  Core dump when configuring the ibmca engine with libica = libica.so.4 in the 
openssl.cnf file in the engine section.
  The problem only occurs with OpenSSL 3.0 and is immediately reproducible.

  
  Details
  ===
  HINT: To be able to receive core dump files at all it is needed to change the 
/etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read
DefaultLimitCORE=infinity:infinity

  On a system with ibmca engine configured system wide, when trying to
  use the libica.so.4 to support the ibmca engine the sshd daemon dumps
  core upon the first login attempt.

  # openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
   [RSA, DSA, DH]

  
  Debug Data
  ==
  core dump file in the attachments.
   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.14.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Edit /etc/systemd/system.conf file to allow core dumps:
  Change the line DefaultLimitCORE=0:infinity
  to read DefaultLimitCORE=infinity:infinity
  2.) run: systemctl daemon-reload
   systemctl restart systemd-coredump.socket
  3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl 
script
  4.) Edit the /etc/pki/tls file near the end to contain the line
  to back the ibmca engine by the libica.so.4 library as outlined in the
  /usr/share/doc/openssl-ibmca/README.md file
  5.) Run: openssl engine -c
  6.) Keep the current session open for subsequently stepping back to the
  original openssl.cnf!
  7.) Open up a new ssh session to the system under test
  and watch the login to fail with broken pipe
  8.) On the remaining session, run
  coreumpctl list / coredumpctl dump
   
  Userspace tool common name: openssl-ibmca 

  Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace tool obtained from project website:  na

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


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

[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2

[ahjohannessen]

It seems like something has happened with regards to zfs 2.1.4 by
looking at https://code.launchpad.net/ubuntu/+source/zfs-linux

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

Title:
  zfs-linux upstream at 2.1.4, jammy has 2.1.2

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I know Jammy is in freeze

  zfs upstream is now at 2.1.3, which has a lovely set of fixes for
  issues I have noticed (such as zfs complaining when waking for sleep,
  and also patches to support 5.16 better and also for the support of
  5.17.)

  Please peruse the large number of important patches, which will make 
supporting this in LTS much easier:
  https://github.com/openzfs/zfs/pull/13063

  
  I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs 
built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev 
systems, and it works beautifully.

  I have attached the debian dir I put on top of the 2.1.3 source
  release which I used to generate debs for this release, which I have
  tested on a server and client desktop x86_64 machine running Ubuntu
  Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues.

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


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

[Kernel-packages] [Bug 1964827] Re: zfs-linux upstream at 2.1.4, jammy has 2.1.2

[ahjohannessen]

+1

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

Title:
  zfs-linux upstream at 2.1.4, jammy has 2.1.2

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I know Jammy is in freeze

  zfs upstream is now at 2.1.3, which has a lovely set of fixes for
  issues I have noticed (such as zfs complaining when waking for sleep,
  and also patches to support 5.16 better and also for the support of
  5.17.)

  Please peruse the large number of important patches, which will make 
supporting this in LTS much easier:
  https://github.com/openzfs/zfs/pull/13063

  
  I'm running a version of https://launchpad.net/~jonathonf/+archive/ubuntu/zfs 
built for 2.1.3 on Ubuntu mainline kernel 5.17-rc8 on multiple Jammy-dev 
systems, and it works beautifully.

  I have attached the debian dir I put on top of the 2.1.3 source
  release which I used to generate debs for this release, which I have
  tested on a server and client desktop x86_64 machine running Ubuntu
  Jammy 22.04 (as of March 14, 2022). I am having no zfs related issues.

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


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

[Kernel-packages] [Bug 1967141] [NEW] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)

[bugproxy]

Public bug reported:

---Problem Description---
Summary
===

New IBM HW with Crypto Accelerator cards attached
Kernel level: 5.14 
Core dump when configuring the ibmca engine with libica = libica.so.4 in the 
openssl.cnf file in the engine section.
The problem only occurs with OpenSSL 3.0 and is immediately reproducible.


Details
===
HINT: To be able to receive core dump files at all it is needed to change the 
/etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read
  DefaultLimitCORE=infinity:infinity

On a system with ibmca engine configured system wide, when trying to use
the libica.so.4 to support the ibmca engine the sshd daemon dumps core
upon the first login attempt.

# openssl engine -c
(dynamic) Dynamic engine loading support
(ibmca) Ibmca hardware engine support
 [RSA, DSA, DH]


Debug Data
==
core dump file in the attachments.
 
Contact Information = christian.r...@de.ibm.com 
 
---uname output---
Linux system 5.14.
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
1.) Edit /etc/systemd/system.conf file to allow core dumps:
Change the line DefaultLimitCORE=0:infinity
to read DefaultLimitCORE=infinity:infinity
2.) run: systemctl daemon-reload
 systemctl restart systemd-coredump.socket
3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl script
4.) Edit the /etc/pki/tls file near the end to contain the line
to back the ibmca engine by the libica.so.4 library as outlined in the
/usr/share/doc/openssl-ibmca/README.md file
5.) Run: openssl engine -c
6.) Keep the current session open for subsequently stepping back to the
original openssl.cnf!
7.) Open up a new ssh session to the system under test
and watch the login to fail with broken pipe
8.) On the remaining session, run
coreumpctl list / coredumpctl dump
 
Userspace tool common name: openssl-ibmca 

Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x 
 
The userspace tool has the following bit modes: 64bit 

Userspace tool obtained from project website:  na

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-197386 severity-critical 
targetmilestone-inin---

** Tags added: architecture-s39064 bugnameltc-197386 severity-critical
targetmilestone-inin---

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps
  core (openssl-ibmca)

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Summary
  ===

  New IBM HW with Crypto Accelerator cards attached
  Kernel level: 5.14 
  Core dump when configuring the ibmca engine with libica = libica.so.4 in the 
openssl.cnf file in the engine section.
  The problem only occurs with OpenSSL 3.0 and is immediately reproducible.

  
  Details
  ===
  HINT: To be able to receive core dump files at all it is needed to change the 
/etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read
DefaultLimitCORE=infinity:infinity

  On a system with ibmca engine configured system wide, when trying to
  use the libica.so.4 to support the ibmca engine the sshd daemon dumps
  core upon the first login attempt.

  # openssl engine -c
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
   [RSA, DSA, DH]

  
  Debug Data
  ==
  core dump file in the attachments.
   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.14.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Edit /etc/systemd/system.conf file to allow core dumps:
  Change the line DefaultLimitCORE=0:infinity
  to read DefaultLimitCORE=infinity:infinity
  2.) run: systemctl daemon-reload
   systemctl restart systemd-coredump.socket
  3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl 
script
  4.) Edit the /etc/pki/tls file near the end to contain the line
  to back the ibmca engine by the libica.so.4 library as outlined in the
  /usr/share/doc/openssl-ibmca/README.md file
  5.) Run: openssl engine -c
  6.) Keep the current session open for subsequently stepping back to the
  original openssl.cnf!
  7.) Open up a new ssh session to the system under test
  and watch the login to fail with broken pipe
  8.) On the remaining session, run
  coreumpctl list / coredumpctl dump
   
  Userspace tool common name: openssl-ibmca 

  Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace tool obtained from p

[Kernel-packages] [Bug 1967141] [NEW] [UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core (openssl-ibmca)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

---Problem Description---
Summary
===

New IBM HW with Crypto Accelerator cards attached
Kernel level: 5.14 
Core dump when configuring the ibmca engine with libica = libica.so.4 in the 
openssl.cnf file in the engine section.
The problem only occurs with OpenSSL 3.0 and is immediately reproducible.


Details
===
HINT: To be able to receive core dump files at all it is needed to change the 
/etc/systemd/system.conf file entry DefaultLimitCORE=0:infinity to read
  DefaultLimitCORE=infinity:infinity

On a system with ibmca engine configured system wide, when trying to use
the libica.so.4 to support the ibmca engine the sshd daemon dumps core
upon the first login attempt.

# openssl engine -c
(dynamic) Dynamic engine loading support
(ibmca) Ibmca hardware engine support
 [RSA, DSA, DH]


Debug Data
==
core dump file in the attachments.
 
Contact Information = christian.r...@de.ibm.com 
 
---uname output---
Linux system 5.14.
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
1.) Edit /etc/systemd/system.conf file to allow core dumps:
Change the line DefaultLimitCORE=0:infinity
to read DefaultLimitCORE=infinity:infinity
2.) run: systemctl daemon-reload
 systemctl restart systemd-coredump.socket
3.) Run the /usr/share/doc/openssl-ibmca/ibmca-engine-opensslconfig perl script
4.) Edit the /etc/pki/tls file near the end to contain the line
to back the ibmca engine by the libica.so.4 library as outlined in the
/usr/share/doc/openssl-ibmca/README.md file
5.) Run: openssl engine -c
6.) Keep the current session open for subsequently stepping back to the
original openssl.cnf!
7.) Open up a new ssh session to the system under test
and watch the login to fail with broken pipe
8.) On the remaining session, run
coreumpctl list / coredumpctl dump
 
Userspace tool common name: openssl-ibmca 

Userspace rpm: openssl-ibmca-2.2.2-1.el9.s390x 
 
The userspace tool has the following bit modes: 64bit 

Userspace tool obtained from project website:  na

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-197386 severity-critical 
targetmilestone-inin---
-- 
[UBUNTU 22.04] ibmca engine with libica = libica.so.4 - sshd dumps core 
(openssl-ibmca)
https://bugs.launchpad.net/bugs/1967141
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 1946463] Re: Ubuntu 20.04.3 default crashkernel size insufficient for kdump

[Frank Heimes]

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

This is now fixed in jammy and onward ... (LP#1877533)

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)

** Changed in: ubuntu-z-systems
   Status: New => Fix Released

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

Title:
  Ubuntu 20.04.3 default crashkernel size insufficient for kdump

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Unable to take a dump using kdump on host, service is enabled and correctly 
configured.
  "[6.110044] Kernel panic - not syncing: System is deadlocked on memory

  ---uname output---
  Linux ilzlnx3.tuc.stglabs.ibm.com 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 
19:07:49 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = S/390 
   
  ---System Hang---
   Once the kdump is unsuccessful, I have to load it from the HMC.
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Trigger kdump with a crash by:
  sysctl -w kernel.sysrq=1
  echo c > /proc/sysrq-trigger
   
  *Additional Instructions for vanessa.ba...@ibm.com , finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

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


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

[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Released

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

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

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in kdump-tools package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Invalid
Status in kdump-tools source package in Focal:
  Invalid
Status in makedumpfile source package in Focal:
  Won't Fix
Status in kdump-tools source package in Groovy:
  Invalid
Status in makedumpfile source package in Groovy:
  Won't Fix

Bug description:
  Description:
  In case the volume containing the root filesystem is encrypted using LUKS2 
the memory used while unlocking the volume may exceed the size allocated to the 
kdump kernel. This will lead to a failure while processing kdump and the dump 
file will not be stored. Unfortunately, this condition may not be detected by a 
client before a problem occurs.
  The request is to have the kdump package installation script check for LUKS2 
encryption (more precisely for Argon2i PBKDF, which is the root cause of the 
high memory usage). If the condition is met, the installation procedure should 
increase the crashkernel parameter to a higher value (>=512M)or issue a 
warning, if the system memory is insufficient to reserve enough crashkernel 
memory.

  Business Case:
  Pervasive Encryption and Secure Execution require encryption of the 
filesystems in order to keep customer data secure at all times. With the 
increasing usage of these technologies, the number of kdump will rise too, 
typically at inconvenient times, when the kdump is triggered due to a real 
customer issue.
  With the suggested change, the number of customer complaints and effort to 
handle them will be reduced.

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


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

[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system

[Yao Wei]

Can confirm that 5.14.0-9031.34+exp.62 fixed this bug. cold-boot 50
times by script and BT can scan normally in all reboots.

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

Title:
  WCN6856 BT keep in OFF state after coldboot system

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-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Triaged
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New

Bug description:
  [Reproduce Steps]
  1.Insert WCN6856 card to SUT.
  2.Press power button to power on SUT.
  3.Clean install Ubuntu 20.04.
  4.Check BT function after installation is complete.
  5.Coldboot system and check the BT function.
  6.Repeat step5, Issue occur.
  7.Only found with CB, can't reproduce on WB.

  [Results]
   Expected Result
   BT function work normally.
   Actual Result
   BT has no function. Can't turn ON BT function. Need CB to recover BT 
function.
   "WB" and "swicth tab" cannot restore the BT function.

  [Others]
  Wifi function work normally.

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


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

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

[bugproxy]

--- Comment From boris.m...@de.ibm.com 2022-03-30 09:22 EDT---
With the bug being fixed (in kdump-tools - 1:1.6.10ubuntu1) we can close this 
item.
Changing IBM bugzilla status to: ==> CLOSED

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

Title:
  [20.10 FEAT] Increase the crashkernel setting if the root volume is
  luks2-encrypted

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kdump-tools package in Ubuntu:
  Fix Released
Status in makedumpfile package in Ubuntu:
  Invalid
Status in kdump-tools source package in Focal:
  Invalid
Status in makedumpfile source package in Focal:
  In Progress
Status in kdump-tools source package in Groovy:
  Invalid
Status in makedumpfile source package in Groovy:
  Won't Fix

Bug description:
  Description:
  In case the volume containing the root filesystem is encrypted using LUKS2 
the memory used while unlocking the volume may exceed the size allocated to the 
kdump kernel. This will lead to a failure while processing kdump and the dump 
file will not be stored. Unfortunately, this condition may not be detected by a 
client before a problem occurs.
  The request is to have the kdump package installation script check for LUKS2 
encryption (more precisely for Argon2i PBKDF, which is the root cause of the 
high memory usage). If the condition is met, the installation procedure should 
increase the crashkernel parameter to a higher value (>=512M)or issue a 
warning, if the system memory is insufficient to reserve enough crashkernel 
memory.

  Business Case:
  Pervasive Encryption and Secure Execution require encryption of the 
filesystems in order to keep customer data secure at all times. With the 
increasing usage of these technologies, the number of kdump will rise too, 
typically at inconvenient times, when the kdump is triggered due to a real 
customer issue.
  With the suggested change, the number of customer complaints and effort to 
handle them will be reduced.

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


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

-- 
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:
  Invalid
Status in juju:
  Triaged
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 1967130] Re: rcu_sched detected stalls on CPUs/tasks

[Heinrich Schuchardt]

efi: Make efi_rts_work accessible to efi page fault handler
https://lore.kernel.org/all/20200318090253.ga32...@duo.ucw.cz/T/#mcbd236122ec0ae61f1ee9c22b8d7910ffc2276a0
addressed a similar issue on x86.

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

Title:
  rcu_sched detected stalls on CPUs/tasks

Status in linux-riscv package in Ubuntu:
  New

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

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

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

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


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

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

[Heinrich Schuchardt]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1967130/+attachment/5574773/+files/dmesg

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

Title:
  rcu_sched detected stalls on CPUs/tasks

Status in linux-riscv package in Ubuntu:
  New

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

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

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

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


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

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

[Heinrich Schuchardt]

apport information

** Tags added: apport-collected

** Description changed:

  When running the riscv64 live installer
  (https://cdimage.ubuntu.com/ubuntu-server/daily-live/20220330/jammy-
  live-server-riscv64.iso) on the SiFive Unmatched board we reproducibly
  see rcu_sched stalls related to accessing the UEFI runtime:
  
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451647] rcu: INFO: rcu_sched 
detected stalls on CPUs/tasks:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451673] rcu:   3-...0: (3 
GPs behind) idle=d03/1/0x4000 softirq=85648/85648 fqs=7326 
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451698](detected by 0, 
t=15002 jiffies, g=155853, q=1286)
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451712] Task dump for CPU 3:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451720] task:kworker/u8:1
state:R  running task stack:0 pid: 3715 ppid: 2 flags:0x0008
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451750] Workqueue: efi_rts_wq 
efi_call_rts
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451777] Call Trace:
  Mar 30 11:50:47 ubuntu-server kernel: [ 1313.451782] [] 
__schedule+0x226/0x644
  
  uname -a:
  Linux ubuntu-server 5.15.0-1004-generic #4-Ubuntu SMP Wed Feb 9 18:17:33 UTC 
2022 riscv64 riscv64 riscv64 GNU/Linux
+ --- 
+ ProblemType: Bug
+ Architecture: riscv64
+ DistroRelease: Ubuntu 22.04
+ Package: linux-image-generic 5.15.0.1004.4
+ PackageArchitecture: riscv64
+ ProcEnviron:
+  TERM=vt220
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+ Uname: Linux 5.15.0-1004-generic riscv64
+ UserGroups: N/A
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1967130/+attachment/5574772/+files/Dependencies.txt

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

Title:
  rcu_sched detected stalls on CPUs/tasks

Status in linux-riscv package in Ubuntu:
  New

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

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

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

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


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

[Kernel-packages] [Bug 1967131] [NEW] CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic

[Nobuto Murata]

Public bug reported:

-kvm flavor has CONFIG_NR_CPUS=64 although -generic has
CONFIG_NR_CPUS=8192 these days.

It will be a problem especially when launching a VM on top of a
hypervisor with more than 64 CPU threads available. Then the guest can
only use up to 64 vCPUs even when more vCPUs are allocated by a
hypervisor.

I've checked the latest available package for Jammy, but there was no change 
around CONFIG_NR_CPUS.
https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3

$ lsb_release -r
Release:20.04

$ dpkg -S /boot/config*
linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic
linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm

$ grep CONFIG_NR_CPUS /boot/config*
/boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192
/boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192
/boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192
/boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192
/boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2
/boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512
/boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64
/boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64

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

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

Title:
  CONFIG_NR_CPUS=64 in -kvm is too low compared to -generic

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  -kvm flavor has CONFIG_NR_CPUS=64 although -generic has
  CONFIG_NR_CPUS=8192 these days.

  It will be a problem especially when launching a VM on top of a
  hypervisor with more than 64 CPU threads available. Then the guest can
  only use up to 64 vCPUs even when more vCPUs are allocated by a
  hypervisor.

  I've checked the latest available package for Jammy, but there was no change 
around CONFIG_NR_CPUS.
  https://launchpad.net/ubuntu/+source/linux-kvm/5.15.0-1003.3

  $ lsb_release -r
  Release:20.04

  $ dpkg -S /boot/config*
  linux-modules-5.4.0-105-generic: /boot/config-5.4.0-105-generic
  linux-modules-5.4.0-1059-kvm: /boot/config-5.4.0-1059-kvm

  $ grep CONFIG_NR_CPUS /boot/config*
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_BEGIN=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_RANGE_END=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS_DEFAULT=8192
  /boot/config-5.4.0-105-generic:CONFIG_NR_CPUS=8192
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_BEGIN=2
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_RANGE_END=512
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS_DEFAULT=64
  /boot/config-5.4.0-1059-kvm:CONFIG_NR_CPUS=64

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


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

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

[Heinrich Schuchardt]

Public bug reported:

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

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

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

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


** Tags: apport-collected jammy riscv64

** Attachment added: "kern.log"
   https://bugs.launchpad.net/bugs/1967130/+attachment/5574771/+files/kern.log

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

Title:
  rcu_sched detected stalls on CPUs/tasks

Status in linux-riscv package in Ubuntu:
  New

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

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

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

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


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

[Kernel-packages] [Bug 1967120] Re: touchpad suddenly stopped working

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => linux-signed-hwe-5.13 (Ubuntu)

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

Title:
  touchpad suddenly stopped working

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

Bug description:
  i turned my computer on and the touchpad wasnt working. It doesnt recognize 
any input.
  hp pavilion x360 convertible model 14dy-0022ns

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 30 13:25:52 2022
  InstallationDate: Installed on 2021-11-26 (124 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1967120] [NEW] touchpad suddenly stopped working

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

i turned my computer on and the touchpad wasnt working. It doesnt recognize any 
input.
hp pavilion x360 convertible model 14dy-0022ns

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 30 13:25:52 2022
InstallationDate: Installed on 2021-11-26 (124 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal
-- 
touchpad suddenly stopped working
https://bugs.launchpad.net/bugs/1967120
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux-signed-hwe-5.13 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 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

[Simon Tatham]

I don't really know what information I should be reporting about my
hardware. My first guess is that the output of 'lspci -v' relating to
the video device might be useful, so here it is:

00:02.0 VGA compatible controller: Intel Corporation Device 4c8a (rev 04) (prog-
if 00 [VGA controller])
DeviceName: Onboard - Video
Subsystem: ASUSTeK Computer Inc. Device 8694
Flags: bus master, fast devsel, latency 0, IRQ 145
Memory at 60 (64-bit, non-prefetchable) [size=16M]
Memory at 40 (64-bit, prefetchable) [size=256M]
I/O ports at 5000 [size=64]
Expansion ROM at 000c [virtual] [disabled] [size=128K]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

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

Title:
  Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

Status in linux-signed-oem-5.14 package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has
  been working fine for me (and supported the network device on my
  reasonably recent PC, which 20.04's default kernel didn't). But the
  5.13 and 5.14 kernels all hang on boot.

  If I edit the GRUB boot commands to let me see the boot messages, the
  hang occurs immediately after printing the message

  [1.044456] fb0: switching to inteldrmfb from EFI VGA

  I can boot this kernel fine if I add 'nomodeset' to the kernel command
  line. But then I get unusably low screen resolution. Instead, my
  workaround is to manually select a 5.11 kernel from the GRUB menu on
  every boot.

  I'm not able to provide a full set of kernel messages from a failed
  boot attempt, because of course the kernel doesn't boot to a point
  where I can save them to a file. But I attach a screenshot of the last
  screenful of messages before the hang, in case those are useful. I'll
  also attach dmesg logs from a successful boot of the 5.14 kernel with
  nomodeset, and from a boot of the 5.11 kernel which gives me full
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 30 12:47:47 2022
  InstallationDate: Installed on 2013-06-01 (3223 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312

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


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

[Kernel-packages] [Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

[Simon Tatham]

** Attachment added: "dmesg.success.5.11.0-46-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574752/+files/dmesg.success.5.11.0-46-generic.txt

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

Title:
  Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

Status in linux-signed-oem-5.14 package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has
  been working fine for me (and supported the network device on my
  reasonably recent PC, which 20.04's default kernel didn't). But the
  5.13 and 5.14 kernels all hang on boot.

  If I edit the GRUB boot commands to let me see the boot messages, the
  hang occurs immediately after printing the message

  [1.044456] fb0: switching to inteldrmfb from EFI VGA

  I can boot this kernel fine if I add 'nomodeset' to the kernel command
  line. But then I get unusably low screen resolution. Instead, my
  workaround is to manually select a 5.11 kernel from the GRUB menu on
  every boot.

  I'm not able to provide a full set of kernel messages from a failed
  boot attempt, because of course the kernel doesn't boot to a point
  where I can save them to a file. But I attach a screenshot of the last
  screenful of messages before the hang, in case those are useful. I'll
  also attach dmesg logs from a successful boot of the 5.14 kernel with
  nomodeset, and from a boot of the 5.11 kernel which gives me full
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 30 12:47:47 2022
  InstallationDate: Installed on 2013-06-01 (3223 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312

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


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

[Kernel-packages] [Bug 1967123] Re: Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

[Simon Tatham]

** Attachment added: "dmesg.nomodeset.5.14.0-1031-oem.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1967123/+attachment/5574751/+files/dmesg.nomodeset.5.14.0-1031-oem.txt

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

Title:
  Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

Status in linux-signed-oem-5.14 package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has
  been working fine for me (and supported the network device on my
  reasonably recent PC, which 20.04's default kernel didn't). But the
  5.13 and 5.14 kernels all hang on boot.

  If I edit the GRUB boot commands to let me see the boot messages, the
  hang occurs immediately after printing the message

  [1.044456] fb0: switching to inteldrmfb from EFI VGA

  I can boot this kernel fine if I add 'nomodeset' to the kernel command
  line. But then I get unusably low screen resolution. Instead, my
  workaround is to manually select a 5.11 kernel from the GRUB menu on
  every boot.

  I'm not able to provide a full set of kernel messages from a failed
  boot attempt, because of course the kernel doesn't boot to a point
  where I can save them to a file. But I attach a screenshot of the last
  screenful of messages before the hang, in case those are useful. I'll
  also attach dmesg logs from a successful boot of the 5.14 kernel with
  nomodeset, and from a boot of the 5.11 kernel which gives me full
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 30 12:47:47 2022
  InstallationDate: Installed on 2013-06-01 (3223 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312

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


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

[Kernel-packages] [Bug 1967123] [NEW] Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

[Simon Tatham]

Public bug reported:

I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has
been working fine for me (and supported the network device on my
reasonably recent PC, which 20.04's default kernel didn't). But the 5.13
and 5.14 kernels all hang on boot.

If I edit the GRUB boot commands to let me see the boot messages, the
hang occurs immediately after printing the message

[1.044456] fb0: switching to inteldrmfb from EFI VGA

I can boot this kernel fine if I add 'nomodeset' to the kernel command
line. But then I get unusably low screen resolution. Instead, my
workaround is to manually select a 5.11 kernel from the GRUB menu on
every boot.

I'm not able to provide a full set of kernel messages from a failed boot
attempt, because of course the kernel doesn't boot to a point where I
can save them to a file. But I attach a screenshot of the last screenful
of messages before the hang, in case those are useful. I'll also attach
dmesg logs from a successful boot of the 5.14 kernel with nomodeset, and
from a boot of the 5.11 kernel which gives me full functionality.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 30 12:47:47 2022
InstallationDate: Installed on 2013-06-01 (3223 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: linux-signed-oem-5.14
UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312

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


** Tags: amd64 apport-bug focal

** Attachment added: "kernelcrash.jpeg"
   
https://bugs.launchpad.net/bugs/1967123/+attachment/5574747/+files/kernelcrash.jpeg

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

Title:
  Hang on boot after 'fb0: switching to inteldrmfb from EFI VGA'

Status in linux-signed-oem-5.14 package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 20.04 with HWE kernels. The 5.11 kernel stream has
  been working fine for me (and supported the network device on my
  reasonably recent PC, which 20.04's default kernel didn't). But the
  5.13 and 5.14 kernels all hang on boot.

  If I edit the GRUB boot commands to let me see the boot messages, the
  hang occurs immediately after printing the message

  [1.044456] fb0: switching to inteldrmfb from EFI VGA

  I can boot this kernel fine if I add 'nomodeset' to the kernel command
  line. But then I get unusably low screen resolution. Instead, my
  workaround is to manually select a 5.11 kernel from the GRUB menu on
  every boot.

  I'm not able to provide a full set of kernel messages from a failed
  boot attempt, because of course the kernel doesn't boot to a point
  where I can save them to a file. But I attach a screenshot of the last
  screenful of messages before the hang, in case those are useful. I'll
  also attach dmesg logs from a successful boot of the 5.14 kernel with
  nomodeset, and from a boot of the 5.11 kernel which gives me full
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
  ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 30 12:47:47 2022
  InstallationDate: Installed on 2013-06-01 (3223 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: linux-signed-oem-5.14
  UpgradeStatus: Upgraded to focal on 2020-08-31 (575 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2013-06-02T15:20:08.886312

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Bruce Walton]

5.13.0-39-generic still has this problem.  Focusrite 2i2

I suppose the test patch for -37 will not work for this case.


Might need to roll back to 5.4 generic, cannot have this device offline.

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

Title:
  audio from external sound card is distorted

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

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1967116

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

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

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

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

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

Title:
  [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04
  kernel. These patches got accepted by the upstream and please find the
  corresponding commit IDs as below:

  334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
  22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
  d44b5fefb22e scsi: mpi3mr: Fix memory leaks
  21401408ddeb scsi: mpi3mr: Update the copyright year
  999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
  b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
  191a3ef58634 scsi: mpi3mr: Fix hibernation issue
  04b27e538d50 scsi: mpi3mr: Update MPI3 headers
  6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
  580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event
  3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
  5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes
  c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0
  a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling
  c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers
  afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
  95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events
  78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event
  c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic
  c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation
  b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware
  c0b00a931e5e scsi: mpi3mr: Add IOC reinit function
  fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner
  59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2
  e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1
  a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout
  2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version
  13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds
  4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s
  ba68779a518d scsi: mpi3mr: Do access status validation before adding devices
  17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device
  ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2
  d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1
  fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status
  a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave()
  9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits
  30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf()
  97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through 
sysfs
  1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly
  76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info()
  92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI
  69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
  aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings
  62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch
  a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc()
  f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error
  2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr()
  d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check
  d3d61f9c8c2d scsi: mpi3mr: Fix a double free
  7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang
  9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints

  
  Thanks,
  Sumit

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


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

[Kernel-packages] [Bug 1967116] [NEW] [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

[Sumit Saxena]

Public bug reported:

Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04
kernel. These patches got accepted by the upstream and please find the
corresponding commit IDs as below:

334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
d44b5fefb22e scsi: mpi3mr: Fix memory leaks
21401408ddeb scsi: mpi3mr: Update the copyright year
999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
191a3ef58634 scsi: mpi3mr: Fix hibernation issue
04b27e538d50 scsi: mpi3mr: Update MPI3 headers
6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event
3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes
c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0
a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling
c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers
afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode
95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events
78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event
c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic
c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation
b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware
c0b00a931e5e scsi: mpi3mr: Add IOC reinit function
fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner
59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2
e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1
a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout
2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version
13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds
4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s
ba68779a518d scsi: mpi3mr: Do access status validation before adding devices
17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device
ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2
d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1
fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status
a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave()
9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits
30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf()
97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through 
sysfs
1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly
76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info()
92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI
69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request
aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings
62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch
a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc()
f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error
2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr()
d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check
d3d61f9c8c2d scsi: mpi3mr: Fix a double free
7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang
9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints


Thanks,
Sumit

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

** Summary changed:

- [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches Edit[Ubuntu 
22.04] mpi3mr: Request to include latest bug fixes
+ [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

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

Title:
  [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes

Status in linux package in Ubuntu:
  New

Bug description:
  Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04
  kernel. These patches got accepted by the upstream and please find the
  corresponding commit IDs as below:

  334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning
  22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0
  d44b5fefb22e scsi: mpi3mr: Fix memory leaks
  21401408ddeb scsi: mpi3mr: Update the copyright year
  999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size
  b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever
  191a3ef58634 scsi: mpi3mr: Fix hibernation issue
  04b27e538d50 scsi: mpi3mr: Update MPI3 headers
  6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count
  580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event
  3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments
  5867b8569e64 scsi: mpi3mr: Fix some spell

[Kernel-packages] [Bug 1954438] Re: rtw89 driver lack pre/post suspend handling

[Pirouette Cacahuète]

With latest rtw89 from github and current Jammy beta, I can suspend /
resume without a hack.

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

Title:
  rtw89 driver lack pre/post suspend handling

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Thanks to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967
  we now have rtw89 in the 5.13.0-22+ kernels on 21.10.

  Because of lockdowns, I have not had the need to far to move away my
  laptop since I received it and make use of suspend/resume, until
  yesterday.

  On my system it turns out suspend/resume fails unless you unload both
  rtw89_pci and rtw89_core modules.

  Upstream documents and provides a systemd integration script to take
  care of that:
  
https://github.com/lwfinger/rtw89/blob/ff7e9c5655b139b7436cc91c6371b9687326c623/suspend_rtw89

  BIOS Information
  Vendor: LENOVO
  Version: R1MET42W (1.12 )
  Release Date: 09/29/2021
  Address: 0xE
  Runtime Size: 128 kB
  ROM Size: 32 MB
  Characteristics:
  PCI is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  Boot from CD is supported
  Selectable boot is supported
  EDD is supported
  3.5"/720 kB floppy services are supported (int 13h)
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  CGA/mono video services are supported (int 10h)
  ACPI is supported
  USB legacy is supported
  BIOS boot specification is supported
  Targeted content distribution is supported
  UEFI is supported
  BIOS Revision: 1.12
  Firmware Revision: 1.12

  System Information
  Manufacturer: LENOVO
  Product Name: 21A0CTO1WW
  Version: ThinkPad P14s Gen 2a
  Wake-up Type: Power Switch
  SKU Number: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  Family: ThinkPad P14s Gen 2a
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  HibernationDevice: RESUME=auto
  InstallationDate: Installed on 2012-11-03 (3324 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: LENOVO 21A0CTO1WW
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-23-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-23-generic N/A
   linux-backports-modules-5.13.0-23-generic  N/A
   linux-firmware 1.201.3
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-23-generic x86_64
  UpgradeStatus: Upgraded to impish on 2021-10-08 (63 days ago)
  UserGroups: adm cdrom dialout dip disk docker libvirt libvirtd lpadmin 
plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 09/29/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET42W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.12
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET42W(1.12):bd09/29/2021:br1.12:efr1.12:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

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


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

Re: [Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[uniomni]

Changing sample rate did not work for me. Only downgrading the kernel as
described works for the moment.

On Wed, 30 Mar 2022, 9:30 pm Hampus Lundberg, <1966...@bugs.launchpad.net>
wrote:

> Setting the default-sample-rate to 48000 in daemon.conf has not worked
> for me.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1966215).
> https://bugs.launchpad.net/bugs/1966066
>
> Title:
>   audio from external sound card is distorted
>
> Status in linux-signed-hwe-5.13 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   The sound card is a Focusrite Scarlett 2i2.
>
>   The sound is distorted everywhere.
>
>   Sound via HDMI works.
>
>   Seen others having the same problem:
>   (Edit because of previously wrong link here)
> https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card
>
>   ubuntu release: Ubuntu 20.04.4 LTS
>   package name involved in bug: linux-image-5.13.0-37-generic
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
>   ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
>   Uname: Linux 5.13.0-35-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu27.21
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Mar 23 12:56:02 2022
>   InstallationDate: Installed on 2020-12-18 (459 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   SourcePackage: linux-signed-hwe-5.13
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions
>
>

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

Title:
  audio from external sound card is distorted

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

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966066] Re: audio from external sound card is distorted

[Hampus Lundberg]

Setting the default-sample-rate to 48000 in daemon.conf has not worked
for me.

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

Title:
  audio from external sound card is distorted

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

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1966680] Re: Revert drm/amd/pm: enable ASPM by default

[Timo Aaltonen]

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

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

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

Title:
  Revert drm/amd/pm: enable ASPM by default

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

Bug description:
  [Impact]
  With WX3200 and 20.04d kernel the unit freezes on resume

  [Fix]
  commit 0064b0ce85bb ("drm/amd/pm: enable ASPM by default") enabled ASPM
  by default but a variety of hardware configurations it turns out that this
  caused a regression.

  Multiple SKUs with wx3200&rx540 gpus encounter the resume&hange issue.
  Before the real fix is landed, revert commit 0064b0ce85bb first.

  [Test Case]
  1. plug wx3200 on the adl machine and make it as a output.
  2. suspend&resume machine
  3. check if machine could resume successfully

  [Where problems could occur]
  Low, don't make AMDGPU ASPM by default.

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


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

[Kernel-packages] [Bug 1967078] 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/1967078

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] VarLogDistupgradeAptlog.txt

[Scott Testerman]

apport information

** Attachment added: "VarLogDistupgradeAptlog.txt"
   
https://bugs.launchpad.net/bugs/1967078/+attachment/5574699/+files/VarLogDistupgradeAptlog.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/1967078

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] VarLogDistupgradeApttermlog.txt

[Scott Testerman]

apport information

** Attachment added: "VarLogDistupgradeApttermlog.txt"
   
https://bugs.launchpad.net/bugs/1967078/+attachment/5574700/+files/VarLogDistupgradeApttermlog.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/1967078

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] VarLogDistupgradeLspcitxt.txt

[Scott Testerman]

apport information

** Attachment added: "VarLogDistupgradeLspcitxt.txt"
   
https://bugs.launchpad.net/bugs/1967078/+attachment/5574701/+files/VarLogDistupgradeLspcitxt.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/1967078

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] VarLogDistupgradeMainlog.txt

[Scott Testerman]

apport information

** Attachment added: "VarLogDistupgradeMainlog.txt"
   
https://bugs.launchpad.net/bugs/1967078/+attachment/5574702/+files/VarLogDistupgradeMainlog.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/1967078

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

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

[Scott Testerman]

apport information

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

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] VarLogDistupgradeAptHistorylog.txt

[Scott Testerman]

apport information

** Attachment added: "VarLogDistupgradeAptHistorylog.txt"
   
https://bugs.launchpad.net/bugs/1967078/+attachment/5574697/+files/VarLogDistupgradeAptHistorylog.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/1967078

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] VarLogDistupgradeAptclonesystemstate.tar.gz

[Scott Testerman]

apport information

** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz"
   
https://bugs.launchpad.net/bugs/1967078/+attachment/5574698/+files/VarLogDistupgradeAptclonesystemstate.tar.gz

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

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] Dependencies.txt

[Scott Testerman]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1967078/+attachment/5574694/+files/Dependencies.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/1967078

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

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

[Scott Testerman]

apport information

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

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  Package: ubuntu-release-upgrader-core 1:22.04.7
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Tags:  jammy dist-upgrade
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  _MarkForUpload: True

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


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

[Kernel-packages] [Bug 1967078] Re: Firefox snap install fails due to disabled networking in upgrade process

[Scott Testerman]

apport information

** Tags added: apport-collected dist-upgrade

** Description changed:

  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
  dmi.bios.date: 04/25/2008
  dmi.bios.release: 2.23
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB7WW (2.17 )
  dmi.board.name: 6465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 6465CTO
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu79
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CrashDB: ubuntu
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-03-30 (0 days ago)
+ InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
+ Package: ubuntu-release-upgrader-core 1:22.04.7
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
+ Tags:  jammy dist-upgrade
+ Uname: Linux 5.15.0-23-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ VarLogDistupgradeXorgFixuplog:
+  INFO:root:/usr/bin/do-release-upgrade running
+  INFO:root:No xorg.conf, exiting
+ _MarkForUpload: True

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

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 202

[Kernel-packages] [Bug 1967078] [NEW] Firefox snap install fails due to disabled networking in upgrade process

[Scott Testerman]

Public bug reported:

Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
snap due to disabled networking.  Prior to the snap installation
attempt, networking is disabled as part of the regular do-release-
upgrade process.  Although networking is enabled again, and a link is
restored, later in the process, name resolution typically fails until
the system is rebooted following completion of the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-23-generic 5.15.0-23.23
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott   959 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Mar 30 04:28:02 2022
HotplugNewDevices:
 
HotplugNewMounts:
 
InstallationDate: Installed on 2022-03-30 (0 days ago)
InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: LENOVO 6465CTO
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-23-generic N/A
 linux-backports-modules-5.15.0-23-generic  N/A
 linux-firmware 20220314.gitcd01f857-0ubuntu2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
 monitor will print the received events for:
 UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 04:28:26.684: The udisks-daemon is running (name-owner :1.10).
UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago)
dmi.bios.date: 04/25/2008
dmi.bios.release: 2.23
dmi.bios.vendor: LENOVO
dmi.bios.version: 7LETB7WW (2.17 )
dmi.board.name: 6465CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
dmi.product.family: ThinkPad T61
dmi.product.name: 6465CTO
dmi.product.version: ThinkPad T61
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug jammy

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

Title:
  Firefox snap install fails due to disabled networking in upgrade
  process

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox
  snap due to disabled networking.  Prior to the snap installation
  attempt, networking is disabled as part of the regular do-release-
  upgrade process.  Although networking is enabled again, and a link is
  restored, later in the process, name resolution typically fails until
  the system is rebooted following completion of the upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-23-generic 5.15.0-23.23
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott   959 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 30 04:28:02 2022
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2022-03-30 (0 days ago)
  InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  MachineType: LENOVO 6465CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220314.gitcd01f857-0ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   04:28:26.684: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: Upgraded to ja

[Kernel-packages] [Bug 1967067] Re: WCN6856 BT keep in OFF state after coldboot system

[You-Sheng Yang]

Included in following kernels in 
https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/intermediate-kernel：
* linux-unstable/jammy version 5.17.0-9006.6+exp.9
* linux-oem-5.17/jammy version 5.17.0-9003.3+exp.5
* linux/jammy version 5.15.0-9024.24+exp.18
* linux-oem-5.14/focal version 5.14.0-9031.34+exp.62

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

Title:
  WCN6856 BT keep in OFF state after coldboot system

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-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Triaged
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New

Bug description:
  [Reproduce Steps]
  1.Insert WCN6856 card to SUT.
  2.Press power button to power on SUT.
  3.Clean install Ubuntu 20.04.
  4.Check BT function after installation is complete.
  5.Coldboot system and check the BT function.
  6.Repeat step5, Issue occur.
  7.Only found with CB, can't reproduce on WB.

  [Results]
   Expected Result
   BT function work normally.
   Actual Result
   BT has no function. Can't turn ON BT function. Need CB to recover BT 
function.
   "WB" and "swicth tab" cannot restore the BT function.

  [Others]
  Wifi function work normally.

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


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

[Kernel-packages] [Bug 1967074] [NEW] nvidia-kernel-source-510 510.54-0ubuntu0.20.04.1: nvidia kernel module failed to build

[Vivian]

Public bug reported:

Nvidia Drivers no longer install.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-510 (not installed)
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.13.0-39-generic
Date: Wed Mar 30 11:17:53 2022
DuplicateSignature: 
dkms:nvidia-kernel-source-510:510.54-0ubuntu0.20.04.1:clang: error: unsupported 
option '-dumpspecs'
InstallationDate: Installed on 2022-03-25 (4 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageVersion: 510.54-0ubuntu0.20.04.1
Python3Details: /usr/bin/python3.8, Python 3.8.10, 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.6
SourcePackage: nvidia-graphics-drivers-510
Title: nvidia-kernel-source-510 510.54-0ubuntu0.20.04.1: nvidia kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-510 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  nvidia-kernel-source-510 510.54-0ubuntu0.20.04.1: nvidia kernel module
  failed to build

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  Nvidia Drivers no longer install.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-kernel-source-510 (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.13.0-39-generic
  Date: Wed Mar 30 11:17:53 2022
  DuplicateSignature: 
dkms:nvidia-kernel-source-510:510.54-0ubuntu0.20.04.1:clang: error: unsupported 
option '-dumpspecs'
  InstallationDate: Installed on 2022-03-25 (4 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageVersion: 510.54-0ubuntu0.20.04.1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, 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.6
  SourcePackage: nvidia-graphics-drivers-510
  Title: nvidia-kernel-source-510 510.54-0ubuntu0.20.04.1: nvidia kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Kernel-packages] [Bug 1967069] [NEW] Enable headset mic on Lenovo P360

[Kai-Heng Feng]

Public bug reported:

[Impact]
Headset microphone can't be detected when headset is plugged to front
panel port.

[Fix]
Apply Realtek ALC897 quirk to enable headset mic.

[Test]
Once the fix is applied, the headset mic can be detected and it also
works.

[Where problems could occur]
Audio quirk which applies to only one specific system, so there's no
chance to regress existing systems.

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

** Affects: linux (Ubuntu)
 Importance: Low
 Status: Confirmed

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

** Affects: linux (Ubuntu Focal)
 Importance: Undecided
 Status: Won't Fix

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

** Affects: linux (Ubuntu Jammy)
 Importance: Low
 Status: Confirmed

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


** Tags: oem-priority originate-from-1964059 sutton

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

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

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

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

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

** Changed in: linux (Ubuntu Focal)
   Status: New => Won't Fix

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

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

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

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

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

** Tags added: oem-priority originate-from-1964059 sutton

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

Title:
  Enable headset mic on Lenovo P360

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-5.14 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.14 source package in Focal:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in linux-oem-5.14 source package in Jammy:
  Invalid

Bug description:
  [Impact]
  Headset microphone can't be detected when headset is plugged to front
  panel port.

  [Fix]
  Apply Realtek ALC897 quirk to enable headset mic.

  [Test]
  Once the fix is applied, the headset mic can be detected and it also
  works.

  [Where problems could occur]
  Audio quirk which applies to only one specific system, so there's no
  chance to regress existing systems.

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


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

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

[Ubuntu Kernel Bot]

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

apport-collect 1967067

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

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

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

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

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

Title:
  WCN6856 BT keep in OFF state after coldboot system

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-oem-5.17 package in Ubuntu:
  New
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.14 source package in Focal:
  Triaged
Status in linux-oem-5.17 source package in Focal:
  Invalid
Status in linux source package in Jammy:
  Incomplete
Status in linux-oem-5.14 source package in Jammy:
  Invalid
Status in linux-oem-5.17 source package in Jammy:
  New

Bug description:
  [Reproduce Steps]
  1.Insert WCN6856 card to SUT.
  2.Press power button to power on SUT.
  3.Clean install Ubuntu 20.04.
  4.Check BT function after installation is complete.
  5.Coldboot system and check the BT function.
  6.Repeat step5, Issue occur.
  7.Only found with CB, can't reproduce on WB.

  [Results]
   Expected Result
   BT function work normally.
   Actual Result
   BT has no function. Can't turn ON BT function. Need CB to recover BT 
function.
   "WB" and "swicth tab" cannot restore the BT function.

  [Others]
  Wifi function work normally.

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


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

[Kernel-packages] [Bug 1965723] Re: audit: improve audit queue handling when "audit=1" on cmdline

[gerald.yang]

Thanks a lot for the help Kleber

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

Title:
  audit: improve audit queue handling when "audit=1" on cmdline

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

Bug description:
  SRU Justification

  [Impact]
  When an admin enables audit at early boot via the "audit=1" kernel
  command line the audit queue behavior is slightly different; the
  audit subsystem goes to greater lengths to avoid dropping records,
  which unfortunately can result in problems when the audit daemon is
  forcibly stopped for an extended period of time.

  [Fix]
  upstream discussion:
  
https://lore.kernel.org/all/cahc9vhqgx070poxzk_pusawgzppdqvpezvfybse2dnryrbw...@mail.gmail.com/T/
  upstream commit:
  f26d04331360d42dbd6b58448bd98e4edbfbe1c5

  [Test]
  configurations:
  auditctl -b 64
  auditctl --backlog_wait_time 6
  auditctl -r 0
  auditctl -w /root/aaa  -p wrx
  shell scripts：
  #!/bin/bash
  i=0
  while [ $i -le 66 ]
  do
  touch /root/aaa
let i++
  done
  mandatory conditions:
  add "audit=1" to the cmdline, and kill -19 pid_number(for /sbin/auditd).

  As long as we keep the audit_hold_queue non-empty, flush the hold
  queue will fall into an infinite loop.

  This could also trigger soft lockup when it drops into a infinite loop, e.g.
  kernel: [   94.186433] watchdog: BUG: soft lockup - CPU#2 stuck for 11s! 
[kauditd:34]
  kernel: [   94.187736] Modules linked in: xfs iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_
  conntrack libcrc32c iptable_filter isofs xt_cgroup xt_tcpudp iptable_mangle 
ip_tables x_tables sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
pcbc aesni_intel aes_x86_64 pp
  dev crypto_simd glue_helper joydev vmwgfx ttm cryptd vmw_balloon 
drm_kms_helper intel_rapl_perf input_leds psmouse drm fb_sys_fops syscopyarea 
vmxnet3 sysfillrect parport_pc parport m
  ac_hid shpchp i2c_piix4 vmw_vsock_vmci_transport vsock sysimgblt vmw_vmci 
serio_raw mptspi mptscsih mptbase scsi_transport_spi pata_acpi floppy autofs4
  kernel: [   94.187757] CPU: 2 PID: 34 Comm: kauditd Not tainted 
4.15.0-171-generic #180~16.04.1-Ubuntu
  kernel: [   94.187757] Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS
   6.00 11/12/2020
  kernel: [   94.187800]  skb_queue_head+0x47/0x50
  kernel: [   94.187803]  kauditd_rehold_skb+0x18/0x20
  kernel: [   94.187805]  kauditd_send_queue+0xcd/0x100
  kernel: [   94.187806]  ? kauditd_retry_skb+0x20/0x20
  kernel: [   94.187808]  ? kauditd_send_multicast_skb+0x80/0x80
  kernel: [   94.187809]  kauditd_thread+0xa7/0x240
  kernel: [   94.187812]  ? wait_woken+0x80/0x80
  kernel: [   94.187815]  kthread+0x105/0x140
  kernel: [   94.187817]  ? auditd_reset+0x90/0x90
  kernel: [   94.187818]  ? kthread_bind+0x40/0x40
  kernel: [   94.187820]  ret_from_fork+0x35/0x40

  [Other Info]
  SF: #00330803

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


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